Wine AppImage 9.8 - Failed to load libvulkan.so.1

[jp734]

Hello All. I'm very very novice when it comes to WINE and having trouble running a program.

First, the system: Bionic64 with NVidia K620 using 340.107 driver.

So, I installed WINE using quickpet. Then I tried installing the 64 bit windows program and it wouldn't let me UNLESS I load the 32bit compatibility SFS which didn't make any sense to me since I'm installing a 64 bit. After loading the 32 bit compatibility, it went thru the installation process but I got the error message (see Screenshot 12) and it rolled back and deleted all the files it installed.

Second attempt was using the Wine AppImage 9.8. This time, the installation finished with an error (see Screenshot 13) but it kept all the files. When I ran the program, it failed to load libvulkan.so.1 and crashed. After doing some digging, I saw a post saying I also need to install the vulkan driver for my card. Folder /usr/lib has files libvulkan_intel.so, libvulkan_radeon.so and libvulkan.so.1 but nothing for nvidia nor nouveau. What do I need to install to fix this issue? The are only three vulkan files I can and have installed using the PPM: mesa-vulkan-drivers, vulkan-utils and libvulkan1

Thanks in advance

[mikewalsh]

@jp734 :-

Hm. O-kayyy.....

First off, it would give us a better idea of what's going on if you could tell us what Windows program you're trying to run? Thanks. Although WINE is getting better & better with each new release, it's still got a long way to go before it can guarantee 100% compatibility with every Windows program ever built. Personally, I rather doubt that day will come.....not during MY lifetime, anyway.

There's WINE AppImages, and.....there's WINE AppImages. I know that may not make a lot of sense, but up till a certain point in fairly recent WINE development - and it's really been accelerating in recent years - WINE basically always ran in 32-bit mode.....largely for compatibility reasons with the huge pool of "legacy", 32-bit Windows applications.

It's only recently that certain folks in the AppImage packaging community have been getting their shit together & including all the SySWOW64 stuff required to correctly run native 64-bit Windows applications. The more experienced packagers will now include not only 32-bit AND 64-bit "modes", but also the compatibility stuff required to run the 32-bit "mode" correctly under a 64-bit Linux host (which is the case for most distros, since there are very few pure 32-bit Linux distros left). Even so, additional DLLs still occasionally have to be added in Windows, just as dependencies have to be added under Linux.....it's always been something of a "black art"!

===========================

Take a gander at the AppImage-based WINE-'portable' packages I put together. The guy I source the AppImages from - one mmtrt, over at Github - really knows his stuff, and puts a lot of care & effort into ensuring his builds run perfectly. In addition to this, I've scripted the portables to link into Puppy in all the right places, as well as running the configuration stuff in the right sequence. You just click on the 'LINK' script, and wait for it to do its stuff. It'll tell you when everything's set-up & ready to go.

You can find the 'portables' here:-

https://www.forum.puppylinux.com/viewtopic.php?t=10955

You'll find the download link in big, hard to miss lettering near the bottom of post #1. I'd advise sticking with the 9-series for now, so go with v9.20. It's quite early days for the 10-series, and the WINE team are still working their way through a ton of bugs ATM. Despite being released AS "stable", it ain't.....not really. Not YET...

Just out of curiosity, where did you get the WINE 9.8 AppImage from? Let us know that, AND the program you're wanting to run, and we'll try and sort this one out if we can.

Mike.

[jp734]

Good FriYAY morning @mikewalsh - Thanks for the reply

I honestly can't remember where I downloaded the appimage 9.8 coz it's been a while. I've been wanting to try wine for a while and it's just now that I got the chance to. As far as the windows version I'm using, the default setting was set to Win10 (didn't even realize I can try different Windows version. Shows how newbie I am with Wine ), but I tried every version (95, XP, 7, 8, 10 and 11) and they all crashed with a failure to load libvulkan in the end. In wine configuration>libraries, there is an existing override loaded "winemenubuilder.exe". Any option with "native" caused it to crashed right away. The builtin only and disabled are the ones that looked like it would work but...no

The Windows program I'm trying to run is ProgeCAD

I've downloaded the 9.20 from the link you provided and will try and update you at a later time. Thanks again. And thank you for explaining the 32 bit. I understand now.

[jp734]

Had some free time today and was able to test 9.20 version. Unfortunately, it still did not work and I tried all Windows version. Still getting the libvulkan error message. It got me further than the 9.8 version though. I am now able to see the screen below. Also attached is the wine log file. Hope it helps.

[mikeslr]

Newer isn't always better. Especially with Wine which (a) has to be built to run under a bunch of LinuxOSes and (b) run lots of Windows programs. Few developers, few testers means much is left to 'fall thru the cracks' and to chance. Under Linux, it's always best to run applications built for Linux. Check for alternatives, e.g. https://alternativeto.net/software/prog ... form=linux. But if what you need is not available, best to check if the Windows program you want has been tested and rated and under which version of Wine. And if it's received a rating of 'garbage' or anything less than 'silver', check if there are alternative Windows programs with better ratings that might suffice.

Note for future reference: Testers do not test 'portable' Windows programs which often run better. Portables do not write to Window's registry and Wine's 'registry' is not identical to that.

As for checking and ProgeCAD in particular, open your web-browser to https://www.winehq.org/. At the Top-Right (2nd Line) of the web-page is a Search box. Type in ProgeCad and there will open another page containing all the links to information about it that has been reported. The first 'Unsponsored' link is https://appdb.winehq.org/objectManager. ... n&iId=2502. It reveals that the last test was in 2016, that of the 2016 version of ProgeCad which received a rating of 'Platinum' [FYI, the highest rating] under Wine 3.13. [If you left-click the either "2016" or "ProgeCad 2016 Professional" the tester's notes will appear, sometimes helpful if it didn't run OOTB.

The above Search also revealed the report of a problem with installation of the 2018 version of ProgeCad; but that was on a Mac, so it and the fix suggested didn't seem irrelevant.

Under these circumstances, I might suggest trying Mikewalsh's Wine 5.11 portable, https://www.forum.puppylinux.com/viewto ... 191#p68191; much closer to the 3.13 Wine version reported to have worked.

[mikewalsh]

@jp734 :-

Yah, as t'other Mike says, the progeCAD page entry:-

https://appdb.winehq.org/objectManager. ... n&iId=2502

...shows the very first submitted trial was rated "Garbage" (waste of time!) The next submission was rated as "Silver" (mostly works, but expect 'quirks').....and the last 3 were all rated "Platinum" (everything works).

What's this asking for, again? Is it libvulkan.dll, or is it libvulkan.so.1? If it's the latter, it needs adding via the PPM, or tracking down somewhere like https://pkgs.org. If it's the former, then the appropriate Windows DLL needs adding. There IS a WINE app for doing this, but it's so long since I've used it I can't remember what it's called! @mikeslr , can you refresh my memory, please?

Mike.

[mikeslr]

jp734's attached wine-debug.txt.zip indicated that libvulkan.so.1 was missing. pkgs.org suggested that libvulkan.so.1 would be found in debian's build of the Chromium web-browser. It can be found in Mikewalsh's Google-Chrome-portable, and likely any other 'Chromium-clone' you may already have. Also Skype and Zoom. It's too large to attach.

If this was a problem with a Linux application I suggest just dropping the libvulkan.so.1 file into /usr/lib or /usr/lib/x86_64-linux-gnu. Worth a try, but it may not work. Although it has the same name, it's not the Window's version; and even with the same name it may not be the version your Bionic64 can use. Edit: FWIW, I think you're in luck . These posts suggest it's a Linux problem: https://github.com/xinntao/Real-ESRGAN- ... ues/58#top and https://support.codeweavers.com/missing ... glibvulkan

When there was only 32-bit Wine applications you could use its (built-in or installable) Wine-tricks to install necessary libraries, if available. But Wine-tricks doesn't work under Wine64 or the new versions of Wine which are multi-architecture. And installing libraries into an AppImage is at best a PITA, at worst impossible. You have to extract the AppImage, place the lib in its proper location and then repackage the AppImage.

[jp734]

These are great information gentlemen. Thank you very much.

So to give you an update on what I did:
1. I wanted a fresh start so I created a new savefile
2. Installed the latest driver 570, downloaded from NVidia's website, for my discrete video card which is a Quadro K620. Installed succesfully with no errors
3. Made sure I have libvulkan.so.1 file in /usr/lib and I do. I've always had the file since my first post. It's a link that points to libvulkan.so.1.1.70
4. Ran vulkaninfo and created a report (see attached). Not sure what I'm reading but I'm guessing my video card supports vulkan

Tested and I got even more farther than the last time. I'm seeing more stuff on the screen. Not the final result we're aiming for but at least I feel we are on the right track. Still getting the failure to load libvulkan.so.1 (debug txt file uploaded last time)

My next step is to follow your advise to try Wine version 5 from the link you provided. Or maybe try the .pet again from quickpet. That's for tonight's goal.

#NeverGivingUp!

[mikeslr]

What architecture/version of ProgeCAD are you trying to run? I've been assuming --and you know what they say about that-- it was a 64bit. But this, https://www.progesoft.com/faq reveals that thru 2021 there were a 32-bit versions. If it's a 32-bit version there are other Wine possibilities, to wit those from version2013's archive of Wine pets including 3.13, https://version2013.yolasite.com/page1.php#wine-3.13 and my upgrade of Shinobar/The Japanese Team's 'old-style' Wine-portable SFS to 3.3, linked from here, viewtopic.php?p=279#p279,

To run 32-bit applications under a 64-bit Puppy, you must first load a 32-bit compatibility SFS. See this post, viewtopic.php?p=282#p282. IIRC, there may be one for Bionicpup64 available via its Menu>Setup>Quickpet. Or perhaps(?) peebee's 32bit-compat-s15pup64-22.12.sfs could be used. https://sourceforge.net/projects/spup/f ... 64/addons/. FWIW, his 64bit-compat.sfs worked under any 32 bit Puppy that was not 'user-merged'. Perhaps his 32bit Compatibility SFSes are as useful.

[jp734]

Good evening Gents,

I am shocked . Why? Because it is WORKING! And here is the weird part.

• Last WINE installed was the Portabe 9.20. Removed it using the script BUT did not delete the ProgeCAD I installed

• Installed WINE using Bionic64 quickpet, which is version 3.15 and the 32bit compatibility

• Tried installing ProgeCAD 64 bit. At first it will not install the Microsoft Visual c++ because it was set default to Windows 7. After setting to Win10, everything worked until it reached creating registry. That's when it stopped and rolled back the installation

Then I had the crazy idea of executing the program installed using the Portable 9.20 and to my surprise, IT WORKED! I did not see the libvulkan error anymore, but when I quit the program, I still get the crash report window. Needs a bit more fine-tuning.

#NeverGiveUp!

[mikewalsh]

@jp734 :-

Heh. Well, there ya go; shows that there's nowt logical or "expected" about WINE. That's NOT to say that the WINE team aren't doing a great job in the first place......but look at what it is they're having to try and emulate!

We all know there's nothing quite "normal" or "natural" about Windows in the first place.... Just my personal opinion, of course. A lot of the software written for Windows is good stuff, but the platform they're writing it to run ON is, at best, fickle.....

It's always been a case of "suck it and see" with WINE. You're making good progress.

Mike.

[jp734]

@mikewalsh

Thanks to both you and @mikeslr . You two led me to right directions.

The question I have now is, what else I can tinker with to see if I can make it even better?

[mikewalsh]

@jp734 :-

I suspect what's happened is this:-

The WINE-portables are designed to only 'link' into Puppy.....NOT to fully install. You have a directory in /root called .wine (note the "." in front of it; this is a 'hidden' directory). This is your WINE 'prefix', and is where WINE creates the emulated Windows file-system once it's run and set itself up.

Because you installed the repo version of WINE, this was a 'full' install. In other words, the /root/.wine directory is an actual directory. When you remove a WINE installation via the PPM, it removes the WINE components.....but it does NOT remove your 'prefix'. So; when you then 'installed' WINE-portable 9.20 via the 'LINK' script, it would have done everything it was meant to do, WITH ONE EXCEPTION; it would not have 'linked' the freshly-created .wine directory from the portable into /root.....because a sym-link CANNOT overwrite a standard directory.

An SFS package may have done so, because these work directly on the Puppy 'layering' file-system (older Pups used aufs, newer ones are now using overlayfs).....but even there I'm not at all certain. My set-up simply uses standard sym-links. 'Twould appear you must have created the progeCAD configuration stuff correctly within WINE's 'prefix', while you were running the older 3-series WINE from the repository, but for whatever reason it wouldn't actually fire up fully. Hardly surprising, since you were attempting to run a 2025 app under a 2016/17 build of WINE.

When you then 'installed' the WINE 9.20 portable, you were running a build of WINE that was also up-to-date.....so it was happy to run with the already-created progeCAD config stuff.

Make sense? Don't fret if it doesn't; WINE has been confusing people for many years.....and nearly every major distro seems to have its own unique way of installing/implementing it. (Just to muddy the waters further, like...)

===============================

Out of curiosity, are you wanting to use this for working with stuff already created under another build of progeCAD, or was this simply an experiment with something you found while browsing? I'm only asking, because for 3D/2D CAD stuff there is a Linux-native alternative (it's pretty good, too!) I'm talking about

FreeCAD

It's available as an AppImage for Linux.....and it runs OOTB under any Puppy from Bionicpup64 onwards. And because it's an AppImage, I've turned this one into a 'portable', too..!

viewtopic.php?t=13152

Just a thought, like. Entirely up to you, of course.....but I thought you might be interested enough to want to take a look.

Mike.

[mikeslr]

Just posting to commend Mikewalsh on his analysis.
And jp734, I like your "#NeverGiveUp!" attitude.

[jp734]

Hey @mikewalsh

It's actually the other way around. First I tried the Portable 9.2 and installed ProgeCAD. Then I removed the link and installed the wine.pet from Bionic. I then installed ProgeCAD again using the 3.15 version of wine but it rolled back the installation But I think it only rolled back ProgeCAD. The Gecko and Mono packages were kept plus the Visual c++ and possibly any other libraries and dll that were installed during the progecad installation process. Thats why I think it worked.

So, I'm using ProgeCAD (that was installed using the portable) on Wine 3.15. I did not link the portable to puppy again.

As far as using FREECAD or LibreCAD, I guess I could try. I do have a progecad license though and I think I could do so much more with it than those free ones. I just need to figure out how to make wine detect my usb key. I have to plug it in to activate my paid license and keep it plug in while using the program. And thats another challenge from what I'm finding out after doing some research. Oh well. #NeverGiveUp - my Wine motto

[edit] but whats really driving me is the windows BSOD and the W10 end of support in October