Gnome-panel won't start when run through NX session

Bug #352716 reported by Eric Schaffner
54
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

(1) Release

Description: Ubuntu jaunty (development branch)
Release: 9.04

(2) Package versions
freenx:
  Installed: 0.7.3+teambzr102-0freenxteam1
  Candidate: 0.7.3+teambzr102-0freenxteam1
gnome-panel:
  Installed: 1:2.26.0-0ubuntu5
  Candidate: 1:2.26.0-0ubuntu5

(3) I expect gnome-panel to run through an NX session.

(4) Prior to today's updates, the gnome panel displayed and ran without problems through an NX session. After applying today's updates, gnome panel crashes on start with the below error message. This occurs both with the FreeNX packages as well as the NoMachine packages:

Xlib: extension "Generic Event Extension" missing on display ":1000.0".
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
The program 'gnome-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 134 error_code 1 request_code 150 minor_code 8)
  (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.)

Related branches

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in gnome-panel (Ubuntu):
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Stéphane Graber (stgraber) wrote :

I can confirm the issue with current Intrepid.
gnome-panel ubuntu4 works correctly, ubuntu5 breaks NX.

Revision history for this message
Stéphane Graber (stgraber) wrote :

err, Launchpad was too fast on this one, couldn't stop it ... Of course it's jaunty and not intrepid :)

Revision history for this message
Stéphane Graber (stgraber) wrote :

Trying to debug with gdb doesn't really help as it's not a real crash where you get a backtrace ... the best I could get is:

63 in main.c
(gdb)

Xlib: extension "Generic Event Extension" missing on display ":1000.0".
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
70 in main.c

(gdb)
72 in main.c
(gdb)
73 in main.c
(gdb)
75 in main.c
(gdb)
80 in main.c
(gdb)
81 in main.c
(gdb)
The program 'gnome-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 112 error_code 1 request_code 150 minor_code 8)
  (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.)

Program exited with code 01.

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you install libglib2.0-0-dbg libgtk2.0-0-dbg gnome-panel-dbg run gdb gnome-panel
(gdb) break gdk_x_error
(gdb) run --sync

... get the crash

(gdb) bt full

and copy the log to the bug?

Revision history for this message
Sebastien Bacher (seb128) wrote :

That's due to the change for bug #192009, I commented on the upstream bug now

Changed in gnome-panel (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
paledread (chris-dunnz) wrote :

My gnome-panel also disappeared on one box where it is run under Openbox on an NXClient, with similar error messages to those above. Running the gdb procedure I get :

gdb gnome-panel
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(gdb) break gdk_x_error
Function "gdk_x_error" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (gdk_x_error) pending.
(gdb) run --sync
Starting program: /usr/bin/gnome-panel --sync
[Thread debugging using libthread_db enabled]
[New Thread 0xb6cdb750 (LWP 4788)]
Xlib: extension "Generic Event Extension" missing on display ":1048.0".
Xlib: extension "Generic Event Extension" missing on display ":1048.0".
Xlib: extension "Generic Event Extension" missing on display ":1048.0".
Xlib: extension "Generic Event Extension" missing on display ":1048.0".
Xlib: extension "Generic Event Extension" missing on display ":1048.0".
[Switching to Thread 0xb6cdb750 (LWP 4788)]

Breakpoint 1, gdk_x_error (display=0x98ab6a0, error=0xbfe4d9a8) at /build/buildd/gtk+2.0-2.16.0/gdk/x11/gdkmain-x11.c:614
614 /build/buildd/gtk+2.0-2.16.0/gdk/x11/gdkmain-x11.c: No such file or directory.
 in /build/buildd/gtk+2.0-2.16.0/gdk/x11/gdkmain-x11.c
(gdb) bt full
#0 gdk_x_error (display=0x98ab6a0, error=0xbfe4d9a8) at /build/buildd/gtk+2.0-2.16.0/gdk/x11/gdkmain-x11.c:614
No locals.
#1 0xb7f4ec95 in ?? () from /usr/lib/libbonoboui-2.so.0
No symbol table info available.
#2 0xb763ddb9 in _XError () from /usr/lib/libX11.so.6
No symbol table info available.
#3 0xb7645d76 in _XReply () from /usr/lib/libX11.so.6
No symbol table info available.
#4 0xb74848cb in ?? () from /usr/lib/libXrandr.so.2
No symbol table info available.
#5 0x080a1fd9 in panel_multiscreen_init () at panel-multiscreen.c:82
 screen = (GdkScreen *) 0x98c6108
 display = (GdkDisplay *) 0x98c3010
 i = 0
#6 0x0806328d in main (argc=2, argv=0xbfe4dcc4) at main.c:81
 context = <value optimized out>
 program = <value optimized out>
 app = <value optimized out>
 new_app = <value optimized out>
 gc = <value optimized out>
 l = <value optimized out>

Hope this helps.

Revision history for this message
l3iggs (l3iggs) wrote :

I see this bug too. +1 for a quick fix

Revision history for this message
RickB (rick-777) wrote :

Me too. There's a forum thread (which has a link to here):

http://ubuntuforums.org/showthread.php?p=6999116

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-panel - 1:2.26.0-0ubuntu6

---------------
gnome-panel (1:2.26.0-0ubuntu6) jaunty; urgency=low

  * debian/patches/27_handle_overlapping_monitors.patch,
    debian/patches/28_prefer_lvds_monitor.patch:
    - don't use those changes for jaunty, they create several issues and it's
      late in the cycle to work on those (lp: #192009, #352716)

 -- Sebastien Bacher <email address hidden> Mon, 06 Apr 2009 11:49:42 +0200

Changed in gnome-panel (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Michael Weck (mike-complexero) wrote :

This is still occurring for me with Jaunty 9.04 (stable):

freenx:
0.7.3+teambzr104-0freenxteam1

gnome-panel:
1:2.26.0-0ubuntu7

Revision history for this message
Miguel Branco (mpbbranco) wrote :

I could notice that the bug disappeared when I disable the Fast User switch and that consequently I had all my logout menu entries restored.

I guess this is somehow linked at the way the menu probes for checking if the FUS is set to appear.

Since then my remote logins on NX have been working fine, I m actually writing fron one right now.

If you don+ t know about FUS, do a search. FUS automatically disables other logout methods.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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