| 2009-10-18 08:22:17 |
mabawsa |
bug |
|
|
added bug |
| 2009-10-18 08:22:17 |
mabawsa |
attachment added |
|
stack trace for g-s-d with xrandr plugin enabled http://launchpadlibrarian.net/33867982/gdb-gsd-xrand-enabled.txt |
|
| 2009-10-18 08:22:17 |
mabawsa |
attachment added |
|
Dependencies.txt http://launchpadlibrarian.net/33867983/Dependencies.txt |
|
| 2009-10-18 08:22:17 |
mabawsa |
attachment added |
|
XsessionErrors.txt http://launchpadlibrarian.net/33867984/XsessionErrors.txt |
|
| 2009-10-18 08:23:24 |
mabawsa |
bug task added |
|
freenx-server |
|
| 2009-10-18 08:24:20 |
mabawsa |
bug task added |
|
gnome-settings-daemon |
|
| 2009-10-18 11:58:50 |
Bryce Harrington |
tags |
amd64 apport-bug |
amd64 apport-bug crash |
|
| 2009-10-23 19:28:14 |
Erik Reuter |
libxrandr (Ubuntu): status |
New |
Confirmed |
|
| 2009-10-23 19:28:34 |
Erik Reuter |
gnome-settings-daemon: status |
New |
Confirmed |
|
| 2009-10-23 19:28:44 |
Erik Reuter |
freenx-server: status |
New |
Confirmed |
|
| 2009-10-23 19:29:55 |
Erik Reuter |
nominated for series |
|
Ubuntu Karmic |
|
| 2009-10-23 21:50:22 |
Chris Coulson |
freenx-server: status |
Confirmed |
Invalid |
|
| 2009-10-23 21:50:49 |
Chris Coulson |
affects |
libxrandr (Ubuntu) |
gnome-settings-daemon (Ubuntu) |
|
| 2009-10-23 21:50:49 |
Chris Coulson |
gnome-settings-daemon (Ubuntu): importance |
Undecided |
Medium |
|
| 2009-10-23 21:50:49 |
Chris Coulson |
gnome-settings-daemon (Ubuntu): assignee |
|
Ubuntu Desktop Bugs (desktop-bugs) |
|
| 2009-10-23 21:51:05 |
Chris Coulson |
gnome-settings-daemon: status |
Confirmed |
New |
|
| 2009-10-23 22:00:47 |
Chris Coulson |
affects |
gnome-settings-daemon (Ubuntu) |
gnome-desktop (Ubuntu) |
|
| 2009-10-23 22:00:47 |
Chris Coulson |
gnome-desktop (Ubuntu): assignee |
Ubuntu Desktop Bugs (desktop-bugs) |
Chris Coulson (chrisccoulson) |
|
| 2009-10-23 22:01:13 |
Chris Coulson |
gnome-settings-daemon: status |
New |
Invalid |
|
| 2009-10-23 22:27:39 |
Chris Coulson |
gnome-desktop (Ubuntu): status |
Confirmed |
In Progress |
|
| 2009-10-23 23:34:33 |
Stéphane Graber |
bug task added |
|
gnome-desktop (Ubuntu Karmic) |
|
| 2009-10-23 23:36:24 |
Chris Coulson |
gnome-desktop (Ubuntu Karmic): milestone |
|
karmic-updates |
|
| 2009-10-23 23:36:53 |
Chris Coulson |
tags |
amd64 apport-bug crash |
amd64 apport-bug crash regression-release |
|
| 2009-10-31 00:41:16 |
Chris Coulson |
attachment added |
|
gnome-desktop_2.28.1-0ubuntu3.debdiff http://launchpadlibrarian.net/34734843/gnome-desktop_2.28.1-0ubuntu3.debdiff |
|
| 2009-10-31 01:03:21 |
Chris Coulson |
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 |
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
*** SRU stuff ***
[Justification]
gnome-settings-daemon crashes at startup on X servers which don't support RANDR 1.2. This is a regression from Jaunty
[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-daemon with each version of gnome-desktop.
With gnome-desktop 2.28.1-0ubuntu2 - gnome-settings-daemon will crash
With gnome-desktop 2.28.1-0ubuntu3 - gnome-settings-daemon will not crash
[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. 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-daemon, the xrandr plugin just stops loading).
- 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_trap_{push,pop} in Jaunty, but it seems this got omitted when the code was changed this cycle. |
|
| 2009-10-31 01:05:03 |
Chris Coulson |
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
*** SRU stuff ***
[Justification]
gnome-settings-daemon crashes at startup on X servers which don't support RANDR 1.2. This is a regression from Jaunty
[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-daemon with each version of gnome-desktop.
With gnome-desktop 2.28.1-0ubuntu2 - gnome-settings-daemon will crash
With gnome-desktop 2.28.1-0ubuntu3 - gnome-settings-daemon will not crash
[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. 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-daemon, the xrandr plugin just stops loading).
- 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_trap_{push,pop} in Jaunty, but it seems this got omitted when the code was changed this cycle. |
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
*** SRU stuff ***
[Justification]
gnome-settings-daemon crashes at startup on X servers which don't support RANDR 1.2. This is a regression from Jaunty
[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-daemon with each version of gnome-desktop.
With gnome-desktop 2.28.1-0ubuntu2 - gnome-settings-daemon will crash
With gnome-desktop 2.28.1-0ubuntu3 - gnome-settings-daemon will not crash
[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-daemon, the xrandr plugin just stops loading).
- 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_trap_{push,pop} in Jaunty, but it seems this got omitted when the code was changed this cycle.
|
|
| 2009-10-31 01:05:57 |
Chris Coulson |
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
*** SRU stuff ***
[Justification]
gnome-settings-daemon crashes at startup on X servers which don't support RANDR 1.2. This is a regression from Jaunty
[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-daemon with each version of gnome-desktop.
With gnome-desktop 2.28.1-0ubuntu2 - gnome-settings-daemon will crash
With gnome-desktop 2.28.1-0ubuntu3 - gnome-settings-daemon will not crash
[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-daemon, the xrandr plugin just stops loading).
- 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_trap_{push,pop} in Jaunty, but it seems this got omitted when the code was changed this cycle.
|
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
*** SRU stuff ***
Patch: http://launchpadlibrarian.net/34734843/gnome-desktop_2.28.1-0ubuntu3.debdiff
[Justification]
gnome-settings-daemon crashes at startup on X servers which don't support RANDR 1.2. This is a regression from Jaunty
[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-daemon with each version of gnome-desktop.
With gnome-desktop 2.28.1-0ubuntu2 - gnome-settings-daemon will crash
With gnome-desktop 2.28.1-0ubuntu3 - gnome-settings-daemon will not crash
[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-daemon, the xrandr plugin just stops loading).
- 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_trap_{push,pop} in Jaunty, but it seems this got omitted when the code was changed this cycle.
|
|
| 2009-10-31 01:14:09 |
Chris Coulson |
attachment removed |
gnome-desktop_2.28.1-0ubuntu3.debdiff http://launchpadlibrarian.net/34734843/gnome-desktop_2.28.1-0ubuntu3.debdiff |
|
|
| 2009-10-31 01:14:33 |
Chris Coulson |
attachment added |
|
gnome-desktop_2.28.1-0ubuntu3.debdiff http://launchpadlibrarian.net/34736555/gnome-desktop_2.28.1-0ubuntu3.debdiff |
|
| 2009-10-31 01:15:06 |
Chris Coulson |
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
*** SRU stuff ***
Patch: http://launchpadlibrarian.net/34734843/gnome-desktop_2.28.1-0ubuntu3.debdiff
[Justification]
gnome-settings-daemon crashes at startup on X servers which don't support RANDR 1.2. This is a regression from Jaunty
[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-daemon with each version of gnome-desktop.
With gnome-desktop 2.28.1-0ubuntu2 - gnome-settings-daemon will crash
With gnome-desktop 2.28.1-0ubuntu3 - gnome-settings-daemon will not crash
[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-daemon, the xrandr plugin just stops loading).
- 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_trap_{push,pop} in Jaunty, but it seems this got omitted when the code was changed this cycle.
|
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
*** SRU stuff ***
Patch: http://launchpadlibrarian.net/34736555/gnome-desktop_2.28.1-0ubuntu3.debdiff
[Justification]
gnome-settings-daemon crashes at startup on X servers which don't support RANDR 1.2. This is a regression from Jaunty
[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-daemon with each version of gnome-desktop.
With gnome-desktop 2.28.1-0ubuntu2 - gnome-settings-daemon will crash
With gnome-desktop 2.28.1-0ubuntu3 - gnome-settings-daemon will not crash
[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-daemon, the xrandr plugin just stops loading).
- 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_trap_{push,pop} in Jaunty, but it seems this got omitted when the code was changed this cycle.
|
|
| 2009-10-31 01:41:31 |
Chris Coulson |
affects |
gnome-settings-daemon |
gnome-desktop |
|
| 2009-10-31 01:43:19 |
Chris Coulson |
bug watch added |
|
https://bugzilla.gnome.org/show_bug.cgi?id=600188 |
|
| 2009-10-31 01:43:19 |
Chris Coulson |
gnome-desktop: importance |
Undecided |
Unknown |
|
| 2009-10-31 01:43:19 |
Chris Coulson |
gnome-desktop: status |
Invalid |
Unknown |
|
| 2009-10-31 01:43:19 |
Chris Coulson |
gnome-desktop: remote watch |
|
GNOME Bug Tracker #600188 |
|
| 2009-10-31 01:43:42 |
Chris Coulson |
gnome-desktop (Ubuntu Karmic): status |
In Progress |
Triaged |
|
| 2009-10-31 01:44:04 |
Chris Coulson |
gnome-desktop (Ubuntu): status |
In Progress |
Triaged |
|
| 2009-11-03 10:13:32 |
Sebastien Bacher |
gnome-desktop (Ubuntu Karmic): status |
Triaged |
Fix Committed |
|
| 2009-11-03 10:13:37 |
Sebastien Bacher |
gnome-desktop (Ubuntu): status |
Triaged |
Fix Committed |
|
| 2009-11-03 10:29:59 |
Martin Pitt |
gnome-desktop (Ubuntu): milestone |
karmic-updates |
lucid-alpha-1 |
|
| 2009-11-03 10:30:53 |
Martin Pitt |
tags |
amd64 apport-bug crash regression-release |
amd64 apport-bug crash regression-release verification-needed |
|
| 2009-11-03 10:31:03 |
Martin Pitt |
removed subscriber Ubuntu Sponsors for main |
|
|
|
| 2009-11-03 13:54:42 |
Stéphane Graber |
tags |
amd64 apport-bug crash regression-release verification-needed |
amd64 apport-bug crash regression-release verification-done |
|
| 2009-11-03 13:55:54 |
Launchpad Janitor |
gnome-desktop (Ubuntu Karmic): status |
Fix Committed |
Fix Released |
|
| 2009-11-03 13:56:18 |
Martin Pitt |
gnome-desktop (Ubuntu Karmic): status |
Fix Released |
Fix Committed |
|
| 2009-11-03 13:56:26 |
Martin Pitt |
gnome-desktop (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2009-11-03 16:25:46 |
Matthias |
removed subscriber Matthias |
|
|
|
| 2009-11-09 10:12:14 |
Launchpad Janitor |
gnome-desktop (Ubuntu Karmic): status |
Fix Committed |
Fix Released |
|
| 2009-12-02 20:02:22 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/gnome-desktop |
|
| 2009-12-02 21:16:08 |
Julien Thomas |
removed subscriber Julien Thomas |
|
|
|
| 2010-09-15 23:58:57 |
Bug Watch Updater |
gnome-desktop: importance |
Unknown |
Medium |
|
| 2011-02-26 19:41:34 |
Bug Watch Updater |
gnome-desktop: status |
Unknown |
Invalid |
|
| 2011-02-26 19:59:16 |
Aurimas Fišeras |
removed subscriber Aurimas Fišeras |
|
|
|
