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.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
FreeNX Server |
Invalid
|
Undecided
|
Unassigned | ||
gnome-desktop |
Invalid
|
Medium
|
|||
gnome-desktop (Ubuntu) |
Fix Released
|
Medium
|
Chris Coulson | ||
Karmic |
Fix Released
|
Medium
|
Chris Coulson |
Bug Description
I just installed karmic on my freenx server machine when g-s-d starts it throws the following error:
gnome-settings-
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-
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)
NonfreeKernelMo
Package: libxrandr2 2:1.3.0-2
ProcEnviron:
LANGUAGE=en_GB:en
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: libxrandr
Uname: Linux 2.6.31-14-generic x86_64
*** SRU stuff ***
Patch: http://
[Justification]
gnome-settings-
[Description of patch]
The patch just traps the BadRequest error generated from the unsupported X call in gnome-desktop, and sets a GError, allowing the calling application to handle it.
[Test case]
Run gnome-settings-
With gnome-desktop 2.28.1-0ubuntu2 - gnome-settings-
With gnome-desktop 2.28.1-0ubuntu3 - gnome-settings-
[Regression risk]
The regression risk is low, because:
- gnome_rr_screen_new will now return a NULL GnomeRRScreen pointer and set a GError when called on servers that don't have RANDR 1.2 (as opposed to crashing). There are already other failure conditions in gnome_rr_screen_new which will return the same result, so this does not break API, and applications using it already handle the error properly (in the case of gnome-settings-
- This technique for trapping errors was used previously. There were XRR calls in the Jaunty code which were only supported on RANDR >= 1.2. These were wrapped with gdk_error_
Related branches
tags: | added: crash |
Changed in libxrandr (Ubuntu): | |
status: | New → Confirmed |
Changed in gnome-settings-daemon: | |
status: | New → Confirmed |
Changed in freenx-server: | |
status: | New → Confirmed |
Changed in freenx-server: | |
status: | Confirmed → Invalid |
affects: | libxrandr (Ubuntu) → gnome-settings-daemon (Ubuntu) |
Changed in gnome-settings-daemon (Ubuntu): | |
assignee: | nobody → Ubuntu Desktop Bugs (desktop-bugs) |
importance: | Undecided → Medium |
Changed in gnome-settings-daemon: | |
status: | Confirmed → New |
Changed in gnome-desktop (Ubuntu): | |
status: | Confirmed → In Progress |
Changed in gnome-desktop (Ubuntu Karmic): | |
milestone: | none → karmic-updates |
tags: | added: regression-release |
affects: | gnome-settings-daemon → gnome-desktop |
Changed in gnome-desktop: | |
importance: | Undecided → Unknown |
status: | Invalid → Unknown |
Changed in gnome-desktop (Ubuntu Karmic): | |
status: | In Progress → Triaged |
Changed in gnome-desktop (Ubuntu): | |
status: | In Progress → Triaged |
Changed in gnome-desktop (Ubuntu Karmic): | |
status: | Triaged → Fix Committed |
Changed in gnome-desktop (Ubuntu): | |
status: | Triaged → Fix Committed |
tags: |
added: verification-done removed: verification-needed |
Changed in gnome-desktop: | |
importance: | Unknown → Medium |
Changed in gnome-desktop: | |
status: | Unknown → Invalid |
I can confirm this behavior. I just upgraded my system from jaunty to karmic, and I found that gnome-settings- daemon would not start when running a free-nx session. However, g-s-d started properly when I started a normal gnome session (no free-nx). Then I disabled the xrandr plug-in, and g-s-d was able to start in a free-nx session.