Screensaver doesn't start on Edgy

Bug #57013 reported by Don Scorgie
6
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: gnome-screensaver

In Edgy.

From the System menu, select "Quit...". Choose Lock screen. Alternatively, press the "Lock Screen" hotkey.

The screensaver fade happens, but then it stays black. No scrensaver turns on and its not possible to return to the desktop. Moving the mouse causes the cursor to appear, but no "Unlock" dialog.

If a terminal is open when locked, the area on-screen where the terminal would be changes the cursor into a text select cursor (vertical bar thing). Using nvidia binary blobs^W driver.

Revision history for this message
Don Scorgie (don-scorgie) wrote :
Download full text (72.0 KiB)

A little more information. Trapping the output from gnome-screensaver produces:

The program 'gnome-screensaver' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 1310 error_code 8 request_code 1 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Grabbing a backtrace from it (using sync and breaking on gdk_x_error). Sorry for the length:

Thread 1 (Thread -1221781840 (LWP 11602)):
#0 gdk_x_error (display=0x8073448, error=0xbfd94ab8) at gdkmain-x11.c:608
No locals.
#1 0xb78e88b9 in _XError () from /usr/lib/libX11.so.6
No symbol table info available.
#2 0xb78ea3bb in _XReply () from /usr/lib/libX11.so.6
No symbol table info available.
#3 0xb78e185e in XSync () from /usr/lib/libX11.so.6
No symbol table info available.
#4 0xb78e19c1 in XSetAfterFunction () from /usr/lib/libX11.so.6
No symbol table info available.
#5 0xb78e3ccc in XCreateWindow () from /usr/lib/libX11.so.6
No symbol table info available.
#6 0xb7be6d3a in IA__gdk_window_new (parent=0x8082860, attributes=0xbfd94ccc,
    attributes_mask=224) at gdkwindow-x11.c:868
        window = (GdkWindow *) 0x8082f80
        impl = (GdkWindowImplX11 *) 0x80c26e0
        screen = (GdkScreen *) 0x807e2a8
        visual = (GdkVisual *) 0x8080010
        xparent = 588
        xvisual = (Visual *) 0x8078c38
        xdisplay = (Display *) 0x8073448
        xid = <value optimized out>
        xattributes = {background_pixmap = 134996280, background_pixel = 0,
  border_pixmap = 3218689144, border_pixel = 0, bit_gravity = 1,
  win_gravity = 134724480, backing_store = -1209653221,
  backing_planes = 3086332992, backing_pixel = 134996272, save_under = 1,
  event_mask = 6520959, do_not_propagate_mask = -1209656709,
  override_redirect = 1, colormap = 44040268, cursor = 0}
        xattributes_mask = 11802
        class_hint = <value optimized out>
        x = <value optimized out>
        y = <value optimized out>
        depth = 24
        class = <value optimized out>
        title = <value optimized out>
        i = <value optimized out>
        __PRETTY_FUNCTION__ = "IA__gdk_window_new"
#7 0xb7e75eba in gtk_window_realize (widget=0x80be130) at gtkwindow.c:4332
        window = <value optimized out>
        parent_window = (GdkWindow *) 0x8082860
        attributes = {title = 0x0, event_mask = 196358, x = 132,
        xparent = 588
        xvisual = (Visual *) 0x8078c38
        xdisplay = (Display *) 0x8073448
        xid = <value optimized out>
        xattributes = {background_pixmap = 134996280, background_pixel = 0,
  border_pixmap = 3218689144, border_pixel = 0, bit_gravity = 1,
  win_gravity = 134724480, backing_store = -1209653221,
  backing_planes = 3086332992, backing_pixel = 134996272, save_under = 1,
  event_mask = 6520959, do_not_propagate_mask = -1209656709,
  override...

Revision history for this message
Vassilis Pandis (pandisv) wrote :

Can you please attach the output of 'lspci -vv' as well as your /etc/X11/xorg.conf file? Thanks.

Revision history for this message
Vassilis Pandis (pandisv) wrote :

And does switching to the 'nv' driver maybe solve the issue? (I have 'nv' here and I cannot reproduce your problem)

Changed in gnome-screensaver:
status: Unconfirmed → Needs Info
importance: Untriaged → Medium
Revision history for this message
Don Scorgie (don-scorgie) wrote :
Download full text (8.6 KiB)

Switching to nv driver solves the problem.

Switching to xinerama solves the problem.

Removing the second screen resolves the problem.

Sigh. I'll file a bug with nvidia about it :(

FWIW, I've attached my xorg.conf (which is pretty messy) and the output of lspci -vv is:

00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge
        Subsystem: ASUSTeK Computer Inc. A7V8X motherboard
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
        Latency: 0
        Region 0: Memory at f0000000 (32-bit, prefetchable) [size=128M]
        Capabilities: [80] AGP version 3.5
                Status: RQ=32 Iso- ArqSz=0 Cal=2 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3+ Rate=x4,x8
                Command: RQ=32 ArqSz=0 Cal=2 SBA+ AGP+ GART64- 64bit- FW- Rate=x8
        Capabilities: [c0] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge (prog-if 00 [Normal decode])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
        Latency: 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        Memory behind bridge: dd000000-dfefffff
        Prefetchable memory behind bridge: dff00000-efffffff
        Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
        BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-
        Capabilities: [80] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
        Subsystem: ASUSTeK Computer Inc. A7V8X-X motherboard
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32, Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 169
        Region 4: I/O ports at d800 [size=32]
        Capabilities: [80] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
        Subsystem: ASUSTeK Computer Inc. A7V8X-X motherboard
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32, Cache Line Size: 32 bytes
        Interrupt: pin B routed to...

Read more...

Revision history for this message
Vassilis Pandis (pandisv) wrote :

From what I hear the nvidia drivers are incompatible with the current Xorg in edgy. Hold on before you file a new bug, this should be somewhere (but I can't find it)...

Revision history for this message
Vassilis Pandis (pandisv) wrote :

I'm not sure if this is really a duplicate - we can only tell after nvidia release their drivers for 7.1. But it could be related to bug 55802 ...

Changed in gnome-screensaver:
status: Needs Info → Confirmed
Revision history for this message
Ralf Nieuwenhuijsen (ralf-nieuwenhuijsen) wrote :

I have the same issue with the new nvidia drivers (from the Ubuntu repositories).
So it's not fixed. All other opengl stuff is working though!

Revision history for this message
Ralf Nieuwenhuijsen (ralf-nieuwenhuijsen) wrote :

It is silly though! Without direct rendering half the opengl screensavers cause a crash, and with direct rendering they don't work.

Revision history for this message
Don Scorgie (don-scorgie) wrote :

Hi,

Sorry, I forgot I filed this bug. I filed another bug upstream, which resulted in a fix being committed (for my issue) in gnome-screensaver 2.16.1. The upload at:
https://lists.ubuntu.com/archives/edgy-changes/2006-October/006980.html

Fixes the issue for me (GNOME bug is bug #361320 - http://bugzilla.gnome.org/show_bug.cgi?id=361320).

Revision history for this message
Ralf Nieuwenhuijsen (ralf-nieuwenhuijsen) wrote :

Latest updates + reboot fixes this issue for me...

before that, it was exactly as you described. So i'm closing this bug... i hope thats ok with you?

Changed in xorg-server:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.