Bug 210892

Summary: gnome-screensaver hangs with dual-head setup
Product: [Fedora] Fedora Reporter: Jeff Needle <jneedle>
Component: gnome-screensaverAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: rawhideCC: bart.vanbrabant, jmccann
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 2.16.1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-12-07 23:21:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 207681    
Attachments:
Description Flags
xorg.conf
none
Output of gnome-screensaver --no-daemon --debug none

Description Jeff Needle 2006-10-16 14:37:35 UTC
Description of problem:
gnome-screensaver kicks in, blanks the screen, and one of the instances seems to
vanish.  Can't unlock screen except by killing the other instance of
gnome-screensaver.

Version-Release number of selected component (if applicable):
gnome-screensaver-2.16.0-7.fc6

How reproducible:
100% in my configuration

Steps to Reproduce:
1.My xorg.conf is attached
2.Launch xscreensaver
3.
  
Actual results:
screen 0 blank, no dialogue box to unlock
screen 1 exposed, but panel non-responsive (as if locked)

Expected results:
both screens display screensaver, keystroke presents dialogue box

Additional info:
strace of remaining gnome-screensaver process looks like this (fragment -
continues on)

# strace -p2478
Process 2478 attached - interrupt to quit
restart_syscall(<... resuming interrupted call ...>) = 0
stat64("/var/run", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
nanosleep({0, 200000000}, NULL)         = 0
stat64("/var/run", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
nanosleep({0, 150000000}, NULL)         = 0
stat64("/var/run", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat64("/var/run", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat64("/var/run", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat64("/var/run", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
nanosleep({0, 200000000}, NULL)         = 0
stat64("/var/run", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
nanosleep({0, 200000000}, NULL)         = 0
stat64("/var/run", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
nanosleep({0, 200000000}, NULL)         = 0
stat64("/var/run", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
nanosleep({0, 150000000}, NULL)         = 0
stat64("/var/run", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat64("/var/run", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat64("/var/run", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat64("/var/run", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
nanosleep({0, 200000000}, NULL)         = 0
stat64("/var/run", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
nanosleep({0, 200000000},  <unfinished ...>

Comment 1 Jeff Needle 2006-10-16 14:37:35 UTC
Created attachment 138579 [details]
xorg.conf

Comment 2 jmccann 2006-10-16 14:43:08 UTC
Looks like you are using Clone mode so it is probably this:
http://bugzilla.gnome.org/show_bug.cgi?id=354663

Comment 3 Jeff Needle 2006-10-16 14:51:49 UTC
Gack.  I don't know how Clone got set.  I'm using 2 different screens, :0.0 and
:0.1, so I guess it's ignoring that option.  Same behavior with Clone set to
off.  Also, not nVidia.  It's an ATI Technologies Inc Radeon RV200 LX [Mobility
FireGL 7800 M7].

Comment 4 jmccann 2006-10-16 14:55:31 UTC
Can you try running gnome-screensaver --no-daemon --debug and attach the output?

Comment 5 Jeff Needle 2006-10-16 15:18:07 UTC
Created attachment 138583 [details]
Output of gnome-screensaver --no-daemon --debug

Comment 6 jmccann 2006-10-16 15:24:13 UTC
Ah, then it is this one:
http://bugzilla.gnome.org/show_bug.cgi?id=358963

Which should be fixed in 2.16.1.

Comment 7 Jeff Needle 2006-10-16 17:41:15 UTC
Just tested 2.16.1 and indeed this does fix it.  Thanks for the quick response!

Comment 8 Matthias Clasen 2006-12-07 23:21:29 UTC
With 2.16.1 in dist-fc6-updates, I think we can close this now.