Bug 29223

Summary: LXQt displays an error dialogue: error starting xdg-screensaver lock
Product: Mageia Reporter: papoteur <yvesbrungard>
Component: RPM PackagesAssignee: papoteur <yvesbrungard>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: ouaurelien
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
URL: https://github.com/lxqt/lxqt/issues/2036
Whiteboard: MGA9TOO
Source RPM: lxqt-session-0.16.0-4.mga8.src.rpm CVE:
Status comment:

Description papoteur 2021-07-05 08:44:02 CEST
Description of problem:
I get sometimes an error dialogue:
Erreur lors du démarrage de "xdg-screensaver lock". Vérifier que vous avez un écran de verrouilalge/veille compatible avec xdg-screensaver installé et démarré.


Version-Release number of selected component (if applicable):
LXQt 0.16.0

How reproducible:
Since upgrade from Mageia 7.

Steps to Reproduce:
1. Wait
Comment 1 papoteur 2021-07-05 08:58:32 CEST
However
xdg-screensaver lock
works from a terminal
Comment 2 Aurelien Oudelet 2021-07-05 20:56:05 CEST
Hi, thanks reporting this.

This is due to have 2 lockers:
- light-locker from lightDM
- xscreensaver

LXQt seems to not be able to choose one.
Try removing xscreensaver and see if this still applies.

CC: (none) => ouaurelien

Comment 3 papoteur 2021-07-05 21:05:42 CEST
Good try, but:
rpm -q light-locker
le paquet light-locker n'est pas installé
Comment 4 Lewis Smith 2021-07-05 22:03:31 CEST
Running LxQt, 'ps' shows only one screensaver:
$ ps ax | grep saver
   6714 ?        S      0:00 /usr/bin/xscreensaver -no-splash
   6726 ?        SN     0:00 xscreensaver-systemd
 /usr/bin/xdg-screensaver*
 /usr/bin/xscreensaver*
So where does xdg-screensaver come from? It comes from xdg-utils.
But who is trying to start it, and why? In the menu Preferences, I see only an entry for Xscreensaver. It may be that Xscreensaver uses xdg-screensaver for the action:
 $ urpmq --requires xscreensaver | grep xdg
 xdg-utils
and
 $ urpmq --whatrequires xdg-utils | uniq | grep screensaver
 xscreensaver

And this is interesting:
 $ xdg-screensaver status
 enabled
even though it does not show in 'ps'.

Florian looks like our principle LxQt person, so assigning this to him. (I guessed the SRPM).
If you want Papoteur or myself to investigate further, please ask.

Source RPM: (none) => lxqt-session-0.16.0-4.mga8.src.rpm
CC: (none) => lewyssmith
Assignee: bugsquad => doktor5000

Comment 5 papoteur 2021-07-12 12:26:09 CEST
I tried:
Gestion de l'énergie (Energy management) / Inactivité (Idle), unchecking "Configurer le comportement en cas d'inactivité" (setting the behaviour when iddle).
Nothing new, even after e reboot.
The dialogue is displayed after each return from suspend/hibernation.
Comment 6 papoteur 2021-07-19 22:25:52 CEST
I reported the problem on LXQt side.
Probably for them.
https://github.com/lxqt/lxqt/issues/2036
Comment 7 Lewis Smith 2021-07-21 21:08:49 CEST
Thank you for doing that. Keep an eye on it.

URL: (none) => https://github.com/lxqt/lxqt/issues/2036
CC: lewyssmith => (none)

Comment 8 papoteur 2023-11-22 20:19:37 CET
This is still the case with Mageia 9.

Status: NEW => UPSTREAM
Version: 8 => Cauldron
Assignee: doktor5000 => yvesbrungard
Whiteboard: (none) => MGA9TOO

Comment 9 katnatek 2023-11-22 22:43:05 CET
with the packages on bug#32554 I don't see this error but I don't test before install that packages
Comment 10 katnatek 2023-11-22 22:43:49 CET
(In reply to katnatek from comment #9)
> with the packages on bug#32554 I don't see this error but I don't test
> before install that packages

Tested on Mageia 9 i586
Comment 11 katnatek 2023-12-06 00:30:32 CET
@papotur did you still have this issue or I can close the bug after change SRPM to lxqt-session-1.3.0-1.mga9?
Comment 12 katnatek 2023-12-06 00:31:20 CET
(In reply to katnatek from comment #11)
> @papotur did you still have this issue or I can close the bug after change
> SRPM to lxqt-session-1.3.0-1.mga9?

@papotur -> @papoteur
Comment 13 papoteur 2023-12-06 08:48:52 CET
This can be closed. I don't see it anymore.
Comment 14 papoteur 2023-12-06 08:49:10 CET
Closing

Resolution: (none) => FIXED
Status: UPSTREAM => RESOLVED