Hi,

Since Slackware 15 is in RCx stage, I'm always in fear of the arrival of the release.

Basic utilities like gv and geeqie are so buggy that gv crashes every a few minutes, and geeqie never will start. KDE5 cannot detect newly attached USB mass storage devices.

The most serious thing I know is that hibernation in KDE5 will not lock the screen first like KDE4 does, but only locks after resume, which always leaves a time window of more than a hundred ms for unauthorized read of the screen content.

Shall we give Slackware 15 RCx a little more time, or will the release have to come very soon?

Best,
guanx

I don't know for the KDE issue, but for geeqie i personally don't have any problems.
Did you try to run it from a terminal and see if it complains about something?
Are you testing on a fresh install or an old updated one?
There was a thread here not long ago (a couple of months?) regarding issues with geeqie not
running for some users, perhaps worth a look?

Maybe this one?
https://www.linuxquestions.org/quest...ie-4175690033/

I've not seen crashes recently with either of these. Tested again here on both 64-bit and 32-bit.

That'd be an issue to take up with the upstream developers. Perhaps it could make it into 5.23.5.

3 members found this post helpful.

guanx --

I had an issue with geeqie last week but I discovered that I had created unresolved library dependencies due to my messy mix of Slackware Live followed by an out-of-sync updates from Slackware Current.

Everything now works as expected after I found and removed Alien Bob's ffmpeg and freerdp and then reinstalled the official packages from current. ( see: https://www.linuxquestions.org/quest...7/#post6308860 )

I wonder ... does return any missing libraries ?

My only issue with gv is that I haven't figured out how to increase the size of the widgets on my 3840x2160 Laptop Monitor ...

hth.

-- kjh

[quote]
Shall we give Slackware 15 RCx a little more time, or will the release have to come very soon?
[/quote}

If my vote matters, sooner would be better

2 members found this post helpful.

I investigated this issue a bit and saw that people on other distros workaround by using systemd hooks on suspend to call loginctl lock-session.
In slackware there's elogind for session management and i saw it is possible to add custom hooks for pre/post operations on suspend, so you could
try hacking with that

https://wiki.gentoo.org/wiki/Elogind...ming.2Fthawing

I'll try when i have some time and report back

Perhaps this works to let elogind lock the desktop on suspend: https://gist.github.com/ryukinix/bd0...ae70e41b7c822b