Meaning of the kscreenlocker_greet "--ksldfd 35"?

Hello all,

The TOP show me the following command line to run the kscreenlock thing:

/usr/lib/kscreenlocker_greet --immediatelock --gracetime 5000 –ksldfd 35

The first two parameter/switches are rather clear, but what does mean the “–ksldfd 35”? I noticed that after I kill the process it restart with “34”.

I am having freezing problems with the locker, and still have no clue even about how to find out what is going wrong (no related messages or error logs).

Thank you.

Found out some information using “–help” in the command line

/usr/lib/kscreenlocker_greet --help
Usage: /usr/lib/kscreenlocker_greet [options]
Greeter for the KDE Plasma Workspaces Screen locker

Options:
-h, --help Displays help on commandline options.
–help-all Displays help including Qt specific options.
-v, --version Displays version information.
–testing Starts the greeter in testing mode
–theme Starts the greeter with the selected theme (only in Testing mode)
–immediateLock Lock immediately, ignoring any grace time etc.
–graceTime Delay till the lock user interface gets shown in milliseconds.
–nolock Don’t show any lock user interface.
–switchuser Default to the switch user UI.
–ksldfd File descriptor for connecting to ksld.

Hi - After you get the screen locker freezing up, are you able to get to a command line (either by restarting and opening Konsole, or switching to a virtual terminal with Ctrl+Alt+F1-7) and run sudo journalctl --since=-5m

That command would show you everything that hit the system journal (log) in the past 5 minutes - if you can match up the timing of when you experience the freeze-up with the time that events show up in the system journal, that would likely help a lot with knowing what system component is going wrong, and where to go from there.

Olá,

Yes, I can log in the TTY and get the logs (see bellow). The last lines before the locker freezes to death are also those about “kscreenlocker_greet”. In the terminal I am also able to kill the locker (only with -9). Then the locker respawn and work again (albeit the profile image appears square, not the usual round).

It is an annoyance but it is not a big problem, and I am still investigating (amateurish) possible reasons in my spare time. One difficulty is that it seems random, and I am unable to reproduce. Apart from this, the machine works very well all all the time which I believe reduces the chance to be a problem with hardware, such as fault memory or power. The last clue was perhaps something to do with different Qt libraries in the system?

Thank you for your answer. Bellow is a copy from a poster with the locking problem and more information.


“” I am having this problem in my (old) system since the upgrade to Leap 15.5. The screen lock freezes and I am unable to type anything. The mouse works, with the pointer visible and moving, but I cannot click anything and even the blinking cursor in the password box is frozen.

The unlock-session(s) in a terminal does not work. Killing the process kscreenlocker_g with only “kill ####” does not work and I have to do it with -9 (“kill -9 ####”). Then the process respawn and I am able to enter the password again.

The only messages I got related to the locker are these:

sudo journalctl | grep kscreenlocker
May 04 08:22:33 XXXX.site kscreenlocker_greet[10383]: Qt: Session management error: networkIdsList argument is NULL
May 04 08:22:34 XXXX.site kscreenlocker_greet[10383]: kf.kirigami: Failed to find a Kirigami platform plugin
May 04 08:22:35 XXXX.site kscreenlocker_greet[10383]: qt.virtualkeyboard.hunspell: Hunspell dictionary is missing for “en_GB” . Search paths (“/usr/share/qt5/qtvirtualkeyboard/hunspell”, “/usr/share/hunspell”, “/usr/share/myspell/dicts”)

Other error message is “gkr-pam: unable to locate daemon control file”, but this does not seems to be related. I have Nomachine running (remote access), but the freezes occurs with the server disabled. I used the “light-locker” a few times, and it seems that the problem did not occur.

Does anyone have any idea why this is happening, or were I can find more information about errors in the system logs? Is it possible to “reinstall” (clean) the kscreenlocker? I will be glad to give more information if necessary.

System info:
Operating System: openSUSE Leap 15.5
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 5.14.21-150500.55.52-default (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-3330 CPU @ 3.00GHz
Memory: 6,7 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 2500
Manufacturer: Gigabyte Technology Co., Ltd.

The system is in English, but the keyboard layout is Portuguese (BR).
The theme is Breeze, but the problem persists with the defaults.“”

Definitely not an expert in this category, but just wondering from seeing things like failing to find a plugin, missing dictionary, unable to locate control file, etc. makes me wonder if there are some things not included in the packaging done for openSUSE Leap?

It might be worth checking on the openSUSE forums as well to see if there is anyone else experiencing that issue on the software versions being used by Leap. That may generally be the best bet, as those software versions are quite out of date compared to upstream.

And it might be worth it to try reinstalling the plasma-desktop package (IIRC zypper install --force and then the package name on that version of Leap) in case there is some file that got randomly corrupted/replaced/etc.

Olá,

I checked these errors, and corrected the “Hunspell dictionary is missing for en_GB” with a copy of the require file. I am still looking for the “Qt: Session management error”, as Qt seems to be source of many freezing problems.

Thank you for your time and suggestions. I will keep trying to find a solution until the end of the year, when I will have more time to make a full backup and “go MS windows”, reinstalling the plasma-desktop package.