Bug 924914 - Multiple screen saver unlock dialogs since 4.10 release
Summary: Multiple screen saver unlock dialogs since 4.10 release
Keywords:
Status: CLOSED DUPLICATE of bug 919835
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-workspace
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-22 19:48 UTC by John Florian
Modified: 2013-03-25 12:21 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-03-23 00:47:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description John Florian 2013-03-22 19:48:55 UTC
Description of problem:
Ever since the upgrade to KDE SC 4.10 the screen saver/locker feature has been working differently and not in a improved way.  I have a four-headed system, driven by an NVIDIA Corporation G98 [Quadro NVS 420] and use xinerama.  Since this upgrade, the screen saver now seems to run four independent instances, one for each screen, rather than one instance showing across all four.  When I interrupt the screen locker, I get four of the unlock dialogs, again one for each screen.  These too are obviously independent because only one shows the password being entered.  The screen saver animations, when running, all start at about the same time, but have some lag between them, so I know this isn't one of those mirrored view modes.  Lastly, about 25% of the time the unlock dialog does not have input focus without being first clicked on, which is kind of annoying and, again different from 4.9.x and earlier releases.

Version-Release number of selected component (if applicable):
kde-workspace-4.10.1-2.fc18.src.rpm

How reproducible:
always

Expected results:
I would expect a single screen saver animation and single unlock dialog.


Additional info:
While I'd much prefer using the nouveau driver, I've never been able to find a way to make this work with more than two heads, thus I must use their proprietary driver.

Comment 1 Kevin Kofler 2013-03-23 00:47:12 UTC
It doesn't seem driver-specific anyway, we already have a report of this issue.

*** This bug has been marked as a duplicate of bug 919835 ***

Comment 2 John Florian 2013-03-25 12:21:43 UTC
Glad to hear it's not driver specific.  My apologies for not successfully finding the duplicate before posting this one -- my searches failed me.


Note You need to log in before you can comment on or make changes to this bug.