Takes a while to learn how to use Wine and to get things working properly.I have this issue with the app I use frequently and I need your help. Using Wine is almost like learning a new operating system. Go to the Wine web site and see what it says about a specific program and issues. What version of Windows you want Wine to mimic can affect how a program runs. Should download and install them as part of the initial config.Īlso, in Wine config->Drivers Select autodetect to get all the driver locations loaded in Wine.Ī lot of settup options in Wine config, so check them all. It will probably offer you a few more programs needed for Wine to run properly. When you get Wine installed and the Wine menu entries. Make sure you have the latest version of Wine.Īlso, look on the first post of the Wine topic for a added program that puts Wine entries in the menu. Sure you set Wine to mimic the correct version of Windows? exe was still complaining about libraries. Viber-try.png (16.84 KiB) Downloaded 667 times but just posting it in case this tips off any other ideas. Ultimately, I still think that the real clue of missing libs lies within the error message of the actual "Viber" executable file in the original post's screenshot, rather than the error message of the. In all above described instances, I tried it from outside of the savefile (where I had originally extracted it) as well as from inside of "/opt" but. Note that I moved the extracted dev folder into my "/opt" directory in the hope that the package's own built-in path structure might better align with Puppy's own "/" or "/root" structure. That lead to the error in the attached screenshot. Right clicked on the file and went to its properties with ROX, and allowed it to be executable. Tried to open that file: "Permission denied" as reported in terminal. deb package actually ships with a sktop file within its own /viber/usr/share/applications/ directory. (Currenlty I have both a symlink folder and a copied folder called "viber" living in the /usr/lib directory.) Tried the copied version with the name "lib" and "viber". Tried copying the "lib" folder right into /usr/lib. Tried naming the symlink folder that lives in /usr/lib both "lib" and "viber". Symlinked the "libs" folder into /usr/lib as per mikeslr's suggestion. It basically dumps into a folder in the exact location where you extract it. Ok, so further to my last suggestion, apparently not.ĭownloaded the. If so, perhaps just using a generic chat client such as pidgin and connecting via the api might do the trick. I don't know if they put their api out there in order to be able to connect in other ways. I'll try some of the suggested solutions if they're quick and dirty, but Viber is of pretty low priority for me, so it may not be worth the time suck.įor those interested (and to answer your question Semme) I got the package off of Viber's own site: The info you guys provided is more valuable than actually getting it to run in terms of me understanding Puppy's behaviours better. So as I understand it, there could be two problems:ġ.) Missing libraries (because Puppy is light weight and doesn't always include all libraries that a distro like Ubuntu does).Ģ.) Libraries are actually there, but this is a package aimed at Ubuntu, and Puppy simply has a different file structure, so the deb package is wired up to search for the libs along the Ubuntu directory regime. You can use the search engine here to find libraries and other ubuntu stuff: Ubuntu would have created a symlink to it named the version the application expected. Sometimes a newer version of the lib is present. Then if the application doesn't start, symlink the lib to /usr/lib. So, best to first download the missing deb and extract it. But sometimes even pfind fails and you have to browse to various likely subfolders in /usr/iib. Can't find the folder on Xenialpup64 right now. IIRC, the libs my end up in /usr/lib/x86_64-linux-gnu. Puppy's 64-bit operating systems still expect to find glibs in /usr/lib. Ubuntu packages 64-bit debs to run under Ubuntu 64. Puppy isn't Ubuntu even when it installs Ubuntu's debs. They may be buried somewhere and Puppy can't find them. Ldd will tell you what libraries are missing. But it also sometimes pays to look in /usr/share/applications for the application, open the file in geany and make sure you've got the name of the executable right. If you're not sure of "/path/to", type "which viber" in terminal. As semme told you, open a terminal and "ldd / path/to/viber/executable".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |