Slackware live usb failing. Rescue?
 

I have a year old usb Slackware live disk that is failing. The unusual thing about this one is that it has wine(-4.0.1) on it The disk is old, but boots. This is the error It throws up the font error in X with an extra letter or two thrown in and exits.

Now I gather from comments at the time wine is no longer done for this live usb? I can't find wine on bear.alienbase.nl, where I would expect From the changeLog I see it was pulled out of 'optional' in 2017.

Is there a way I can get wine into some new live usb? Or repair the one I have?

My suggestion is that you create a new live USB, preferably using one of AlienBob's alternatives, and install his latest wine package (5.18).

I see no real errors in that output which would make your application fail.

On a year-old Slackware Live which you apparently never updated, it is probably not possible to wrap a recent wine package into a live module. My wine package for -current requires a really current -current. The libraries on your USB stick will be too old.

FYI, Slackware Live is always built from slackware-current. The iso2usb.sh script has a "-r" parameter which you can use to "refresh" the live content on your USB stick with the live modules on a more recent ISO image. That way you can update your Slackware Live to a recent slackware-current on which the wine 5.x will have more success.
The refresh will not touch your persistent data which is also stored on the USB stick.

Great! I have the script (somewhere sensible…) and I'll try it with the -r option. I didn't think the wine error was a big thing either. Wine usually declares a crisis, followed by a state of disaster, then starts normally :P

Multilib somehow got in there. I have a notion I rebuilt one of the isos with multilib, as it's a 32 bit program I need wine for. Then the isos all became squashfs systems. Back to the docs for me /Groan. And next time. I'll do a decent Backup. I had the USAB backed up, but ir was the version before I repurposed it.

Nice!! I've read the help file about the iso2usb script but somehow missed the '-r' option. This is great news and means *MUCH* easier keeping my flashdrive 'up to date' over completely erasing everything I've put on it to have the latest and greatest 'current live' put on it.

Thanks again for all you do and have done with this, Alien Bob!

/Some time Later…

I've been at this on and off. My ideal thing was to be

• Liveslak
• Multilib (available as an sxz only, but I could explode it if I can master unsquashfs and make an iso)
• wine (available as a txz, but I can explode it and make an iso out of it)
• XFCE

Now I lost the usb contents, so have to start over. The iso2usb script only accepts one iso. I ran it with the '-i' argument as the xfce iso, and all came up well. I tried to add to it, and failed. There's also the consideration that gcc & glibc have to be reinstalled for multilib, don't they? Is there a doc on doctoring live installs?

You will find it here.

You'll have to work on understanding how a Live OS works. Mine (and some others too) is essentially a set of squashfs modules that are loop-mounted and then layered on top of each other using a kernel driver called "overlayfs". The .sxz files are compressed squashfs modules and you should not try to make individual ISO images out of them. Add the .sxz modules to the ./addons or ./optional subdirectories of liveslak USB to respectively get them loaded and used everytyime you boot, or only when you explicitly tell it to.

Today i uploaded a new multilib module and also a new wine module. The multilib module contains my gcc and glibc packages as well as the set of -compat32 packages, and the wine module contains not just wine, but also its dependencies for slackware-current (FAudio and vkd3d).

.

Thank you - I'd actually got that far, and figured out to add sxzs, and where to add them. I stuck in a few sxzs, but I wasn't convinced I found them. Anyhow, armed with this knowledge, I'll try again, and mark this solved when I'm running. Allow me to pass compliments on the most advanced live usb I ever tried, and thanks for your reply. I'll update the wine and multilib sxzs.

As an aside, mksquashfs takes the prize for the most efficient multi-threaded app I have used. I have 2 cores = 4 threads, and mksquashfs works away @385-395% cpu under top! I've NEVER seen that before. It must be doing all the work in cache.

I grabbed the current wine and multilib, stored them in ~liveslak/addons and they got found for certain this time:).

As you might see there's more than a few errors. Now I know well that wine always throws a hissy fit before doing anything. It went out to lunch on this one, and I had to use Ctrl_C. Once the ~/.wine dir was there, it seemed less hysterical'
https://pastebin.com/7StQC2kx & https://pastebin.com/gdt8j9UE

Do these this hissy fits look ok to you? Oh, and btw it throws half a dozen 'blockdev not found' errors in the kernel boot stage. Is that important?

with the new wine versions, I noticed that I have to get past a lot of messages before I get the application window I want. Next time it seems to have quited down. So yes,I recognize that.

That is a useless and irrelevant kernel message that should have been patched away but no one cares. You can search the internet and find the discussion. Ignore the warnings.

Yes, indeed. What would we do without /dev/null - the write only memory. Back in the 1970s, someone in Signetics shoved a datasheet into their dataooks for the WOM - a hardware write only memory :D. Signetics "Released" it on April Fool's day in 1974. I digress.

Unfortunately I installed the only thing I needed wine for, and it pukes. I get the splash screen, then it and wine exits. https://pastebin.com/0EfXKGnM

I'll try the new wine on my base system which has that package installed before I go messing too much.

EDIT: I tried on my normal system, which works fine on wine-5.18. I also tried the alternative command from the Desktop fileBut that pukes thusly Even knowing there's Unix & windows escapes in there doesn't help me. I use strictly Unix commands. I also don't know how the 'L' in red got into the filename :o

Trying to debug this issue, I started with WINEDEBUG=+seh,+relay and trapped it, but forgot to log it. So I ran again with WINEDEBUG=+all, and excluding the log spam this is it. Is wine having issues with Unix file names? I removed the ~/.wine dir, but it's exactly the same.

Actually, this has gone way off topic. I reinstalled the usb and that was successful.Not rescue, but reinstall.

I'll post the wine error in a new software thread.

For anyone reading this, I solved the wine 'trap 14' error quite by accident.

I was out walking, then went back to try debugging it again. But the usb disk had ended up in the car. So I said:"Never mind - I'll just roll another" I have a 16G USB key. That worked fine!! All the silly wine hand wringing, but no errors. So the finger of suspicion points at my old USB disk.