← Back to team overview

freenx-team team mailing list archive

[Bug 454487] Re: The program 'gnome-settings-daemon' received an X Window System error. During on a FreeNX server suring a session. The crash does not happen when xrandr plugin is disabled.

 

** Attachment added: "stack trace for g-s-d with xrandr plugin enabled"
   http://launchpadlibrarian.net/33867982/gdb-gsd-xrand-enabled.txt

** Attachment added: "Dependencies.txt"
   http://launchpadlibrarian.net/33867983/Dependencies.txt

** Attachment added: "XsessionErrors.txt"
   http://launchpadlibrarian.net/33867984/XsessionErrors.txt

** Also affects: freenx-server
   Importance: Undecided
       Status: New

** Also affects: gnome-settings-daemon
   Importance: Undecided
       Status: New

-- 
The program 'gnome-settings-daemon' received an X Window System error. During on a FreeNX server suring a session. The crash does not happen when xrandr plugin is disabled.
https://bugs.launchpad.net/bugs/454487
You received this bug notification because you are a member of FreeNX
Team, which is the registrant for FreeNX Server.

Status in FreeNX open source NX Server: New
Status in Gnome Settings Daemon: New
Status in “libxrandr” package in Ubuntu: New

Bug description:
I just installed karmic on my  freenx server machine when g-s-d starts it throws the following error:
gnome-settings-daemon 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-settings-daemon' 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 105 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.)

If I disable the xrandr plugin then the bug is not present (once bug 409621 is fixed).
This is a regression from Jaunty where the xrandr plugin worked.
I attach the the stack trace. If there is anything else I can do please let me know.

ProblemType: Bug
Architecture: amd64
Date: Sun Oct 18 17:10:18 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Beta amd64 (20090929.2)
NonfreeKernelModules: nvidia
Package: libxrandr2 2:1.3.0-2
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: libxrandr
Uname: Linux 2.6.31-14-generic x86_64