SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,099
Rep:
WINE and the latest -Current Updates.
Since installing the 21 May 2022, -current updates WINE has slowed to a crawl.
For years I've been running The American Heritage Electronic Dictionary in WINE. When started it flashes a splash screen for a second and then loads the program.
Since installing the aforementioned updates the splash screen stays up for a full 60 seconds and then finally disappears and the program is loaded.
It had been running perfectly with the 5.18-rc7 kernel, but I tried the 5.17.9 kernel. Didn't help.
Deleted the ~/.wine directory and started over. Didn't help.
Ran removepkg on WINE and tried two different packages. Didn't help.
Any suggestions would be appreciated.
Thanks.
Last edited by cwizardone; 05-24-2022 at 09:33 AM.
I'm on current and multilib, and I'm OK with wine programs. I'm not seeing the issue you are, but I'm on the 5.17.9 kernel. There was a package added...do you have it? I don't know if anything is compiled against it yet, though.
Installed WINE-7.9 an hour or so ago. Didn't make any difference.
-current is current up to the moment.
Geez. Hrm... Do you remember when the program stopped working? Were there any big updates then? It might be something that needs updating or adding to multilib. (Like if something is compiled against something else.)
Do you have another program you can run with WINE, just to see if it's working or you get the same error?
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,099
Original Poster
Rep:
Quote:
Originally Posted by rkelsen
I'm curious to know if there's any benefit to running -current in place of a fully patched/updated 15.0 at this point?
Are there any noticeable features or improvements which make putting up with these types of breakages a worthwhile prospect?
I looked through the ChangeLog, and nothing jumps out at me.
I'm asking out of genuine curiosity, it's not a "dig."
Good question!
Over the years I've learn a little here and there, but not a great deal of detail. That is unfortunate, but that is the way my mind seems to work. Learn what I need to know to fix the problem at hand and move on. A little knowledge here and a little there. Which why, to this day, when I read some of the packages descriptions they mean absolutely nothing to me as whoever wrote them assumes the reader has prior knowledge of the subject.
Which, in turn, as a "end user," is why I sometimes ask what some would think are dumb questions.
Anyway, being retired, I spend entirely too much time tinkering with the computer and following -current is one way to pass the time. If I were still employed with a "normal" lifestyle, I probably wouldn't have the time or interest. I need to start looking for a real job, but at my age, not likely.......
Last edited by cwizardone; 05-24-2022 at 02:31 PM.
Anyway, being retired, I spend entirely too much time tinkering with the computer and following -current is one way to pass the time.
Thanks for answering!
I think when I'm eventually in your shoes I'll be doing the same (hopefully PV will still be maintaining Slackware!). For now though, my time is almost entirely consumed by running a family and a business.
Wasn't asked, but I switched to current with the new computer...my motherboard and CPU wasn't supported by 14.2's kernel, so I used current. Then when 15.0 was released and the patches started up, I got lazy and didn't switch back.
I don't think this is a current issue. I think it's a WINE problem, and likely a regression. It's exactly like a reported bug. (Right now the only two things I"m using WINE for are Guild Wars 2 and Minecraft Dungeons. Both work fine.)
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,099
Original Poster
Rep:
Quote:
Originally Posted by garpu
......I don't think this is a current issue.......
Well, I would have to disagree.
The only change made to the system since the last time the dictionary worked properly was the installation of the 21 May -current updates.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.