Mailinglist Archive: opensuse-bugs (15082 mails)

[bugzilla_noreply@xxxxxxxxxx]

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@xxxxxxxxxxxxxxxxxxxxxx
        ReportedBy: olli@xxxxxxxxxxxxx
         QAContact: sndirsch@xxxxxxxxxx
          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.