[opensuse] Serious problem with screensaver in leap-15.1
Hello all, With several freshly installed opensuse-leap-15.1 systems with KDE, I have the problem that the screen saver won't lock the screen while a different virtual terminal is active. I have searched the net, but was not able to find something similar. How to reproduce: I have configured the screen saver to 1 minute and require the password after 5 seconds. While the screen saver in not active, simply press CTL-ALT-F2 to activate the second virtual terminal and wait for several minutes. When switching back to the desktop, the expected situation would be that the screen saver is active and only the password screen is visible. The actual behavior is when switching back, all the open applications (possibly showing confidential data) are visible for about one second. Then the screen starts to dim. And due to the setting of 5 seconds for password requirement, one can stop the screen saver just by typing some key or moving the mouse. I feel like this is a serious problem. Below are two outputs from journalctl. The first shows a failed lock. The second shows a successful lock due to virtual terminals were not switched. Any hints how to track the root of the problem or how to get the desired behaviour? Fail: Mar 11 08:53:19 raven.inka.de ksmserver[2476]: lock called Mar 11 08:53:19 raven.inka.de ksmserver[2476]: Lock window Id: 23068918 Mar 11 08:53:19 raven.inka.de ksmserver[2476]: CreateNotify: 23068918 Mar 11 08:53:19 raven.inka.de ksmserver[2476]: CreateNotify: 111149059 Mar 11 08:53:19 raven.inka.de kscreenlocker_greet[13048]: Qt: Session management error: networkIdsList argument is NULL Mar 11 09:02:19 raven.inka.de org_kde_powerdevil[2518]: powerdevil: Kbd backlight brightness value: 0 Mar 11 09:04:37 raven.inka.de org_kde_powerdevil[2518]: powerdevil: ACTIVE SESSION PATH CHANGED: "/org/freedesktop/login1/session/_33" Mar 11 09:04:37 raven.inka.de org_kde_powerdevil[2518]: powerdevil: Current session is now active Mar 11 09:04:38 raven.inka.de ksmserver[2476]: CreateNotify: 113246211 Mar 11 09:04:38 raven.inka.de kcminit[13164]: Initializing "kcm_input" : "kcminit_mouse" Mar 11 09:04:38 raven.inka.de kcminit[13164]: kcm_input: Using X11 backend Mar 11 09:04:38 raven.inka.de ksmserver[2476]: CreateNotify: 113246212 Mar 11 09:04:38 raven.inka.de kwin_x11[2479]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 22505, resource id: 113246212, major code: 18 (ChangeProperty), minor code: 0 Mar 11 09:04:38 raven.inka.de ksmserver[2476]: CreateNotify: 111149063 Mar 11 09:04:38 raven.inka.de ksmserver[2476]: CreateNotify: 111149075 Mar 11 09:04:38 raven.inka.de ksmserver[2476]: CreateNotify: 111149084 Mar 11 09:04:38 raven.inka.de ksmserver[2476]: CreateNotify: 111149086 Mar 11 09:04:38 raven.inka.de kscreenlocker_greet[13048]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/openSUSEdefault/contents/images/" Mar 11 09:04:38 raven.inka.de kscreenlocker_greet[13048]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/openSUSEdefault/contents/images/" Mar 11 09:04:38 raven.inka.de kscreenlocker_greet[13048]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/openSUSEdefault/contents/images/" Success: Mar 11 09:10:04 raven.inka.de ksmserver[2476]: lock called Mar 11 09:10:04 raven.inka.de ksmserver[2476]: Lock window Id: 23068923 Mar 11 09:10:04 raven.inka.de ksmserver[2476]: CreateNotify: 23068923 Mar 11 09:10:04 raven.inka.de ksmserver[2476]: CreateNotify: 111149059 Mar 11 09:10:04 raven.inka.de kscreenlocker_greet[13234]: Qt: Session management error: networkIdsList argument is NULL Mar 11 09:10:04 raven.inka.de ksmserver[2476]: CreateNotify: 111149063 Mar 11 09:10:04 raven.inka.de ksmserver[2476]: CreateNotify: 111149075 Mar 11 09:10:04 raven.inka.de ksmserver[2476]: CreateNotify: 111149084 Mar 11 09:10:05 raven.inka.de ksmserver[2476]: CreateNotify: 111149086 Mar 11 09:10:05 raven.inka.de kscreenlocker_greet[13234]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/openSUSEdefault/contents/images/" Mar 11 09:10:05 raven.inka.de kscreenlocker_greet[13234]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/openSUSEdefault/contents/images/" Mar 11 09:10:05 raven.inka.de kscreenlocker_greet[13234]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/openSUSEdefault/contents/images/" Mar 11 09:10:05 raven.inka.de kscreenlocker_greet[13234]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/openSUSEdefault/contents/images/" Mar 11 09:10:05 raven.inka.de kscreenlocker_greet[13234]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/openSUSEdefault/contents/images/" Mar 11 09:10:05 raven.inka.de kscreenlocker_greet[13234]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/openSUSEdefault/contents/images/" Mar 11 09:10:05 raven.inka.de kscreenlocker_greet[13234]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/openSUSEdefault/contents/images/" Mar 11 09:10:05 raven.inka.de kscreenlocker_greet[13234]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/openSUSEdefault/contents/images/" Mar 11 09:10:05 raven.inka.de kscreenlocker_greet[13234]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/openSUSEdefault/contents/images/" Mar 11 09:10:05 raven.inka.de ksmserver[2476]: CreateNotify: 111149098 Mar 11 09:10:05 raven.inka.de ksmserver[2476]: CreateNotify: 111149100 Mar 11 09:10:05 raven.inka.de ksmserver[2476]: MapNotify: 111149098 Mar 11 09:10:05 raven.inka.de kscreenlocker_greet[13234]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/openSUSEdefault/contents/images/" Mar 11 09:10:05 raven.inka.de kscreenlocker_greet[13234]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/openSUSEdefault/contents/images/" Mar 11 09:10:05 raven.inka.de kscreenlocker_greet[13234]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/openSUSEdefault/contents/images/" Mar 11 09:10:05 raven.inka.de kscreenlocker_greet[13234]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/openSUSEdefault/contents/images/" Mar 11 09:10:05 raven.inka.de kscreenlocker_greet[13234]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/openSUSEdefault/contents/images/" Mar 11 09:10:05 raven.inka.de kscreenlocker_greet[13234]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/openSUSEdefault/contents/images/" Mar 11 09:10:05 raven.inka.de ksmserver[2476]: CreateNotify: 111149102 Mar 11 09:10:05 raven.inka.de kscreenlocker_greet[13234]: UdevQt: unable to create udev monitor connection Mar 11 09:10:05 raven.inka.de kscreenlocker_greet[13234]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) -- Josef Wolf jw@raven.inka.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 11.03.20 um 09:38 schrieb Josef Wolf:
The actual behavior is when switching back, all the open applications (possibly showing confidential data) are visible for about one second. Then the screen starts to dim. And due to the setting of 5 seconds for password requirement, one can stop the screen saver just by typing some key or moving the mouse.
This is misleading behaviour. Switching to console pauses a running music player (clementine). It also causes the behaviour you described. I am also interested in why this happens. As a short-term fix i would suggest not using the "5 seconds pause" for asking the password. thal -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Thanks for your reply, Alex! On Wed, Mar 11, 2020 at 11:50:44AM +0100, Alex Bihlmaier wrote:
Am 11.03.20 um 09:38 schrieb Josef Wolf:
The actual behavior is when switching back, all the open applications (possibly showing confidential data) are visible for about one second. Then the screen starts to dim. And due to the setting of 5 seconds for password requirement, one can stop the screen saver just by typing some key or moving the mouse.
This is misleading behaviour. Switching to console pauses a running music player (clementine). It also causes the behaviour you described.
I don't even have clementine installed. I have never ever started any music player on those systems. Even with a running music player, I'd expect the screen saver to work properly.
As a short-term fix i would suggest not using the "5 seconds pause" for asking the password.
This avoids that the lock procedure be stopped by mouse movement or something. The last state of the desktop is still shown for about one second on a lightly loaded system. On a heavy loaded systems, I'v seen considerable longer times until the screen starts to fade. Swap maybe... -- Josef Wolf jw@raven.inka.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Content-ID:
On Wed, Mar 11, 2020 at 11:50:44AM +0100, Alex Bihlmaier wrote:
Am 11.03.20 um 09:38 schrieb Josef Wolf:
...
This avoids that the lock procedure be stopped by mouse movement or something. The last state of the desktop is still shown for about one second on a lightly loaded system. On a heavy loaded systems, I'v seen considerable longer times until the screen starts to fade. Swap maybe...
I have two laptops with XFCE on 15.1, and on one I get the full open desktop on return from terminal, and on the other I get the login screen. If I click on my user and type password, I get my desktop intact. Otherwise, I can login on a different user. But no screensaver triggers - but I have not waited long enough, anyway. This depends on the display manager aka login manager. The working laptop has "gdm" (and what appears is wayland) and xfce further on. The "non working" laptop has "sddm". - -- Cheers Carlos E. R. (from openSUSE Leap 15.1 x86_64 (Minas Tirith)) -----BEGIN PGP SIGNATURE----- iJIEAREIADoWIQQt/vKEw5659AgM/X2NrxRtxRYzXAUCXmloYRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJEI2vFG3FFjNcx6gA/RuZRNLuZ4KiBAxyq+zP /oPQcGAViQzr55nLeZ8fp9RaAP9o3CD21W6zB6ptVW9eLNpoJCddIXIq2qQlFl1Q E91VTw== =YF2o -----END PGP SIGNATURE-----
On Wed, Mar 11, 2020 at 11:38:25PM +0100, Carlos E. R. wrote:
This depends on the display manager aka login manager. The working laptop has "gdm" (and what appears is wayland) and xfce further on. The "non working" laptop has "sddm".
Thanks for confirming and the additional information, Carlos! A quick check on two boxes shosw that they both are running sddm. I can't check the other ones, since I have no net access to them ATM. Thus, choosing a different display manager would be a temporary workaround? Is it possible to increase debug output in sddm to further track down the real problem? -- Josef Wolf jw@raven.inka.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2020-03-12 a las 08:26 +0100, Josef Wolf escribió:
On Wed, Mar 11, 2020 at 11:38:25PM +0100, Carlos E. R. wrote:
This depends on the display manager aka login manager. The working laptop has "gdm" (and what appears is wayland) and xfce further on. The "non working" laptop has "sddm".
Thanks for confirming and the additional information, Carlos!
A quick check on two boxes shosw that they both are running sddm. I can't check the other ones, since I have no net access to them ATM.
Thus, choosing a different display manager would be a temporary workaround?
Or definitive. Each one has different features, and apparently gdm has the feature of "blocking the session" on change of "seat", without using the screensaver for that. If you are using KDE you could try kdm.
Is it possible to increase debug output in sddm to further track down the real problem?
It may be a missing feature. Maybe sddm expects the screensaver to do it, and they don't do it right yet. Notice that entering the password on the screen saver is faster than what gdm does, as you have to enter the user first. - -- Cheers Carlos E. R. (from openSUSE Leap 15.0 x86_64 (Minas Tirith)) -----BEGIN PGP SIGNATURE----- iJIEAREIADoWIQQt/vKEw5659AgM/X2NrxRtxRYzXAUCXmoEtRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJEI2vFG3FFjNcN+4BAKAwln5tL5XVSg23KA/n vxLKQ7CTYX1F8sUKnKH06/lyAPsFU2TytxPPUrSp794exdsztJqFJeuQSmXOtA5B bfcK7Q== =Bnag -----END PGP SIGNATURE-----
On Thu, Mar 12, 2020 at 10:45:25AM +0100, Carlos E. R. wrote:
El 2020-03-12 a las 08:26 +0100, Josef Wolf escribió:
On Wed, Mar 11, 2020 at 11:38:25PM +0100, Carlos E. R. wrote:
This depends on the display manager aka login manager. The working laptop has "gdm" (and what appears is wayland) and xfce further on. The "non working" laptop has "sddm".
Thanks for confirming and the additional information, Carlos!
A quick check on two boxes shosw that they both are running sddm. I can't check the other ones, since I have no net access to them ATM.
Thus, choosing a different display manager would be a temporary workaround?
Or definitive. Each one has different features, and apparently gdm has the feature of "blocking the session" on change of "seat", without using the screensaver for that.
Did take a while to understand how a missing bug can be considered to be a feature ;-)
From the perspective of a user, it is not obvious that different components are involved to provide the "lock screen" feature. So, from user-perspective, I'd call it "bug".
If you are using KDE you could try kdm.
Thanks for the suggestion! Have installed it now. How would I actually activate it? I can't see any configuration option in the system settings...
Notice that entering the password on the screen saver is faster than what gdm does, as you have to enter the user first.
Yes, that's annoying. One more missing feature ;-) -- Josef Wolf jw@raven.inka.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/03/2020 11.28, Josef Wolf wrote:
On Thu, Mar 12, 2020 at 10:45:25AM +0100, Carlos E. R. wrote:
El 2020-03-12 a las 08:26 +0100, Josef Wolf escribió:
On Wed, Mar 11, 2020 at 11:38:25PM +0100, Carlos E. R. wrote:
This depends on the display manager aka login manager. The working laptop has "gdm" (and what appears is wayland) and xfce further on. The "non working" laptop has "sddm".
Thanks for confirming and the additional information, Carlos!
A quick check on two boxes shosw that they both are running sddm. I can't check the other ones, since I have no net access to them ATM.
Thus, choosing a different display manager would be a temporary workaround?
Or definitive. Each one has different features, and apparently gdm has the feature of "blocking the session" on change of "seat", without using the screensaver for that.
Did take a while to understand how a missing bug can be considered to be a feature ;-)
From the perspective of a user, it is not obvious that different components are involved to provide the "lock screen" feature. So, from user-perspective, I'd call it "bug".
You can try bugzilla, of course, but it may be an upstream design issue.
If you are using KDE you could try kdm.
Thanks for the suggestion! Have installed it now. How would I actually activate it? I can't see any configuration option in the system settings...
update-alternatives. There is a CLI command and a YaST module.
Notice that entering the password on the screen saver is faster than what gdm does, as you have to enter the user first.
Yes, that's annoying. One more missing feature ;-)
The idea is that it may be a different person who is coming by, and he has another account. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.0 x86_64 (Minas Tirith))
On Thu, Mar 12, 2020 at 11:46:05AM +0100, Carlos E. R. wrote:
On 12/03/2020 11.28, Josef Wolf wrote:
From the perspective of a user, it is not obvious that different components are involved to provide the "lock screen" feature. So, from user-perspective, I'd call it "bug".
You can try bugzilla, of course, but it may be an upstream design issue.
While this might be an upstream design bug and/or feature, it should not be installed that way by default.
If you are using KDE you could try kdm.
Thanks for the suggestion! Have installed it now. How would I actually activate it? I can't see any configuration option in the system settings...
update-alternatives.
There is a CLI command and a YaST module.
I'll try that. Thanks!
Notice that entering the password on the screen saver is faster than what gdm does, as you have to enter the user first.
Yes, that's annoying. One more missing feature ;-)
The idea is that it may be a different person who is coming by, and he has another account.
Umm. Other display managers provide something like a "new session" button, which this different person can hit in this situation. -- Josef Wolf jw@raven.inka.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/03/2020 12.26, Josef Wolf wrote:
On Thu, Mar 12, 2020 at 11:46:05AM +0100, Carlos E. R. wrote:
On 12/03/2020 11.28, Josef Wolf wrote:
From the perspective of a user, it is not obvious that different components are involved to provide the "lock screen" feature. So, from user-perspective, I'd call it "bug". You can try bugzilla, of course, but it may be an upstream design issue. While this might be an upstream design bug and/or feature, it should not be installed that way by default.
If you are using KDE you could try kdm. Thanks for the suggestion! Have installed it now. How would I actually activate it? I can't see any configuration option in the system settings... update-alternatives.
There is a CLI command and a YaST module. I'll try that. Thanks!
Notice that entering the password on the screen saver is faster than what gdm does, as you have to enter the user first. Yes, that's annoying. One more missing feature ;-) The idea is that it may be a different person who is coming by, and he has another account. Umm. Other display managers provide something like a "new session" button, which this different person can hit in this situation.
Well, each display manager can have different features. If all had the same, there would not be need for so many variants. -- Saludos/Cheers Carlos E. R. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Mar 11, 2020 at 11:38:25PM +0100, Carlos E. R. wrote:
This depends on the display manager aka login manager. The working laptop has "gdm" (and what appears is wayland) and xfce further on. The "non working" laptop has "sddm".
Ugh, this seems to be a long-standig problem, since ubuntu-18.04 shows the same problem when sddm is used. "zypper install gdm" wants to pull 254 additional packages, BTW. -- Josef Wolf jw@raven.inka.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/03/2020 08.33, Josef Wolf wrote:
On Wed, Mar 11, 2020 at 11:38:25PM +0100, Carlos E. R. wrote:
This depends on the display manager aka login manager. The working laptop has "gdm" (and what appears is wayland) and xfce further on. The "non working" laptop has "sddm". Ugh, this seems to be a long-standig problem, since ubuntu-18.04 shows the same problem when sddm is used.
"zypper install gdm" wants to pull 254 additional packages, BTW.
Not surprising, it is a gnome package. Try kdm instead. -- Saludos/Cheers Carlos E. R. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Mar 11, 2020 at 11:38:25PM +0100, Carlos E. R. wrote:
This depends on the display manager aka login manager. The working laptop has "gdm" (and what appears is wayland) and xfce further on. The "non working" laptop has "sddm".
I have tried "lightdm" and "kdm" as alternatives to "sddm" now. With all three of them, I see the same undesired (broken, IMHO) behaviour. So the problem doesn't seem to be tied to sddm... -- Josef Wolf jw@raven.inka.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/03/2020 12.48, Josef Wolf wrote:
This depends on the display manager aka login manager. The working laptop has "gdm" (and what appears is wayland) and xfce further on. The "non working" laptop has "sddm". I have tried "lightdm" and "kdm" as alternatives to "sddm" now. With all three of
On Wed, Mar 11, 2020 at 11:38:25PM +0100, Carlos E. R. wrote: them, I see the same undesired (broken, IMHO) behaviour.
So the problem doesn't seem to be tied to sddm...
Or rather, gdm people, seeing that the screen saver can't provide that feature, have taken it inside instead. -- Saludos/Cheers Carlos E. R. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Mar 12, 2020 at 12:56:38PM +0100, Carlos E.R. wrote:
On 12/03/2020 12.48, Josef Wolf wrote:
This depends on the display manager aka login manager. The working laptop has "gdm" (and what appears is wayland) and xfce further on. The "non working" laptop has "sddm". I have tried "lightdm" and "kdm" as alternatives to "sddm" now. With all three of
On Wed, Mar 11, 2020 at 11:38:25PM +0100, Carlos E. R. wrote: them, I see the same undesired (broken, IMHO) behaviour.
So the problem doesn't seem to be tied to sddm...
Or rather, gdm people, seeing that the screen saver can't provide that feature, have taken it inside instead.
Umm, don't believe that. Older KDM versions worked as expected. But I can't say, how old they need to be... BTW: I have three questions regarding bugzilla: 1. There's no "opensuse leap" in the "OS" pulldown menu. Should I use "SUSE Other" instead? 2. Is it OK to link to the archive of this thread? Or should all the information be duplicated on bugzilla? 3. The component would be "KDE Workspace (Plasma)"? -- Josef Wolf jw@raven.inka.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/03/2020 13.12, Josef Wolf wrote: ...
Umm, don't believe that. Older KDM versions worked as expected. But I can't say, how old they need to be...
I don't remember. It is new in gdm to me.
BTW: I have three questions regarding bugzilla: 1. There's no "opensuse leap" in the "OS" pulldown menu. Should I use "SUSE Other" instead?
Yes, there is. https://bugzilla.opensuse.org/index.cgi --> new https://bugzilla.opensuse.org/enter_bug.cgi?classification=openSUSE First, you must pick a product on which to enter a bug: openSUSE: openSUSE openSUSE Backports: openSUSE:Backports project in build.opensuse.org openSUSE Distribution: openSUSE Leap & Stable releases <===== openSUSE Tumbleweed: openSUSE Rolling Release openSUSE.org: The openSUSE project (not the distribution)
2. Is it OK to link to the archive of this thread? Or should all the information be duplicated on bugzilla?
All the information must be in the bugzilla, but you can add a link to the thread too.
3. The component would be "KDE Workspace (Plasma)"?
Start there, if not "other" -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.1 x86_64 (Minas Tirith))
On Thu, Mar 12, 2020 at 01:47:37PM +0100, Carlos E. R. wrote:
On 12/03/2020 13.12, Josef Wolf wrote:
BTW: I have three questions regarding bugzilla: 1. There's no "opensuse leap" in the "OS" pulldown menu. Should I use "SUSE Other" instead?
Yes, there is.
https://bugzilla.opensuse.org/index.cgi --> new https://bugzilla.opensuse.org/enter_bug.cgi?classification=openSUSE
First, you must pick a product on which to enter a bug: openSUSE: openSUSE openSUSE Backports: openSUSE:Backports project in build.opensuse.org openSUSE Distribution: openSUSE Leap & Stable releases <===== openSUSE Tumbleweed: openSUSE Rolling Release openSUSE.org: The openSUSE project (not the distribution)
Hmm... This is "Product". But on the "OS", there's no "Leap" or "15.x" tag I've chosen "OS:Linux", since it happens with ubuntu-18.04 also when kubuntu-desktop is installed and (the annoying) "gdm" is removed.
2. Is it OK to link to the archive of this thread? Or should all the information be duplicated on bugzilla? All the information must be in the bugzilla, but you can add a link to the thread too.
3. The component would be "KDE Workspace (Plasma)"? Start there, if not "other"
Here's the bug: https://bugzilla.opensuse.org/show_bug.cgi?id=1166496 -- Josef Wolf jw@raven.inka.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/03/2020 14.12, Josef Wolf wrote:
On Thu, Mar 12, 2020 at 01:47:37PM +0100, Carlos E. R. wrote:
On 12/03/2020 13.12, Josef Wolf wrote:
Here's the bug: https://bugzilla.opensuse.org/show_bug.cgi?id=1166496
Seems a good report to me :-) -- Saludos/Cheers Carlos E. R. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Mar 12, 2020 at 07:27:15PM +0100, Carlos E.R. wrote:
On 12/03/2020 14.12, Josef Wolf wrote:
On Thu, Mar 12, 2020 at 01:47:37PM +0100, Carlos E. R. wrote:
On 12/03/2020 13.12, Josef Wolf wrote:
Here's the bug: https://bugzilla.opensuse.org/show_bug.cgi?id=1166496
Seems a good report to me :-)
I had a lot of help from this list to create it :-)) -- Josef Wolf jw@raven.inka.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Mar 12, 2020 at 02:12:57PM +0100, Josef Wolf wrote:
Here's the bug: https://bugzilla.opensuse.org/show_bug.cgi?id=1166496
What does the comment in this bug mean? Shoud somebody (me?) duplicate the bug to the kde buglist? Can somebody give me a pointer to the KDE bug tracker? -- Josef Wolf jw@raven.inka.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Josef Wolf wrote:
On Thu, Mar 12, 2020 at 02:12:57PM +0100, Josef Wolf wrote:
Here's the bug: https://bugzilla.opensuse.org/show_bug.cgi?id=1166496
What does the comment in this bug mean? Shoud somebody (me?) duplicate the bug to the kde buglist? Can somebody give me a pointer to the KDE bug tracker?
Wolfgang is suggesting that when the problem occurs in openSUSE and Ubuntu both, it is unlikely to be an openSUSE-specific problem. Logging the issue at http://bugs.kde.org might be a good idea. -- Per Jessen, Zürich (1.0°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Josef Wolf
On Thu, Mar 12, 2020 at 12:56:38PM +0100, Carlos E.R. wrote:
On 12/03/2020 12.48, Josef Wolf wrote:
This depends on the display manager aka login manager. The working laptop has "gdm" (and what appears is wayland) and xfce further on. The "non working" laptop has "sddm". I have tried "lightdm" and "kdm" as alternatives to "sddm" now. With all three of
On Wed, Mar 11, 2020 at 11:38:25PM +0100, Carlos E. R. wrote: them, I see the same undesired (broken, IMHO) behaviour.
So the problem doesn't seem to be tied to sddm...
Or rather, gdm people, seeing that the screen saver can't provide that feature, have taken it inside instead.
Umm, don't believe that. Older KDM versions worked as expected. But I can't say, how old they need to be...
BTW: I have three questions regarding bugzilla: 1. There's no "opensuse leap" in the "OS" pulldown menu. Should I use "SUSE Other" instead? 2. Is it OK to link to the archive of this thread? Or should all the information be duplicated on bugzilla? 3. The component would be "KDE Workspace (Plasma)"?
you might try "xdm" I believe I read that kdm was depricated ??? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Mar 12, 2020 at 10:37:56AM -0400, Patrick Shanahan wrote:
you might try "xdm"
I believe I read that kdm was depricated ???
Yes, myself also read that kdm is no longer managed. Unfortunately, xdm also don't work... -- Josef Wolf jw@raven.inka.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/03/2020 16.03, Josef Wolf wrote:
On Thu, Mar 12, 2020 at 10:37:56AM -0400, Patrick Shanahan wrote:
you might try "xdm"
I believe I read that kdm was depricated ??? Yes, myself also read that kdm is no longer managed.
Unfortunately, xdm also don't work...
I did not remember that kdm was deprecated. What's the appropriate display manager for plasma, then? Any pdm out there? -- Saludos/Cheers Carlos E. R. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op donderdag 12 maart 2020 19:29:19 CET schreef Carlos E.R.:
On 12/03/2020 16.03, Josef Wolf wrote:
On Thu, Mar 12, 2020 at 10:37:56AM -0400, Patrick Shanahan wrote:
you might try "xdm"
I believe I read that kdm was depricated ???
Yes, myself also read that kdm is no longer managed.
Unfortunately, xdm also don't work...
I did not remember that kdm was deprecated. What's the appropriate display manager for plasma, then? Any pdm out there?
sddm, and has been since plasma5 is there.
-- Saludos/Cheers Carlos E. R.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/03/2020 19.33, Knurpht-openSUSE wrote:
Op donderdag 12 maart 2020 19:29:19 CET schreef Carlos E.R.:
On 12/03/2020 16.03, Josef Wolf wrote:
On Thu, Mar 12, 2020 at 10:37:56AM -0400, Patrick Shanahan wrote:
you might try "xdm"
I believe I read that kdm was depricated ???
Yes, myself also read that kdm is no longer managed.
Unfortunately, xdm also don't work...
I did not remember that kdm was deprecated. What's the appropriate display manager for plasma, then? Any pdm out there?
sddm, and has been since plasma5 is there.
Ah. That's what he had originally and suffers this problem. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.1 x86_64 (Minas Tirith))
* Carlos E.R.
On 12/03/2020 16.03, Josef Wolf wrote:
On Thu, Mar 12, 2020 at 10:37:56AM -0400, Patrick Shanahan wrote:
you might try "xdm"
I believe I read that kdm was depricated ??? Yes, myself also read that kdm is no longer managed.
Unfortunately, xdm also don't work...
I did not remember that kdm was deprecated. What's the appropriate display manager for plasma, then? Any pdm out there?
sddm is suggested but I believe all will work. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Alex Bihlmaier -
Carlos E. R. -
Carlos E.R. -
Josef Wolf -
Knurpht-openSUSE -
Patrick Shanahan -
Per Jessen