[Bug 310528] New: display locking conflicts on acer aspire 5684WLMi
https://bugzilla.novell.com/show_bug.cgi?id=310528 Summary: display locking conflicts on acer aspire 5684WLMi Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: openSUSE 10.2 Status: NEW Keywords: accessibility Severity: Major Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: olli@digger.org.ru QAContact: sndirsch@novell.com Found By: --- I've configured display lock in KDE & it works fine. Though currently I've found two locking applications running after my laptop lid close. The 1st ask for password & unvlocks, but then I see xlock random screen saver & it also asks for password. The password is not accepted, but is passing to current application under the lock. So I had a fun passing my password to another gaim user - gaim opened a popup when I was out of my workplace. Well, it's not a problem to change pass & to kill xlock from console session, but there're problems anyway: 1. Some application/package installed installs a hook in X on a lid close w/o checking KDE settings (how can I find that application, BTW - 'grep -r xlock /etc' ?). 2. The xlock in the situation above: 2.1 passes input to background app. 2.2 ignores that password is correct. The 2.2 is just annoying - need to switch to console & run 'killall xlock', but 2.1 is very dangerouse, for example I've sent my pass to some gaim user, but it could be, for example, fdisk opened in a console window.. I'm running open SeSE 10.2 on Acer Aspire 5684WLMi . What additional info should I provide to tight these problems w/ exact packages? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=310528 Olli Artemjev <olli@digger.org.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |olli@digger.org.ru Priority|P5 - None |P4 - Low -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=310528 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |behlert@novell.com Component|X11 Applications |Mobile Devices QAContact|sndirsch@novell.com |qa@suse.de -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=310528 Christian Zoz <zoz@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zoz@novell.com, sndirsch@novell.com AssignedTo|behlert@novell.com |hmacht@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=310528#c1 Holger Macht <hmacht@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |olli@digger.org.ru --- Comment #1 from Holger Macht <hmacht@novell.com> 2007-09-25 05:23:05 MST --- (In reply to comment #0 from Olli Artemjev)
I've configured display lock in KDE & it works fine. Though currently I've found two locking applications running after my laptop lid close. The 1st ask for password & unvlocks, but then I see xlock random screen saver & it also asks for password. The password is not accepted, but is passing to current application under the lock. So I had a fun passing my password to another gaim user - gaim opened a popup when I was out of my workplace. Well, it's not a problem to change pass & to kill xlock from console session, but there're problems anyway:
Does this happen always? Is kpowersave configured to lock the screen on lid close?
1. Some application/package installed installs a hook in X on a lid close w/o checking KDE settings (how can I find that application, BTW - 'grep -r xlock /etc' ?).
It's most likely the powersave daemon. Can you please check /etc/powersave/events:EVENT_BUTTON_LID_CLOSE and post the content?
2. The xlock in the situation above: 2.1 passes input to background app. 2.2 ignores that password is correct. The 2.2 is just annoying - need to switch to console & run 'killall xlock', but 2.1 is very dangerouse, for example I've sent my pass to some gaim user, but it could be, for example, fdisk opened in a console window..
I'm running open SeSE 10.2 on Acer Aspire 5684WLMi .
Does this happen always? What happens after exiting kpowersave? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=310528#c2 Holger Macht <hmacht@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|olli@digger.org.ru | Resolution| |INVALID --- Comment #2 from Holger Macht <hmacht@novell.com> 2007-11-07 05:52:59 MST --- No reply since some time. Closing as INVALID. Please reopen if you can provide the requested information. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com