GNOME Bugzilla – Bug 338129
no preference in the Gnome Desktop preferences is accessible
Last modified: 2007-02-04 09:44:54 UTC
Distribution: Ubuntu 6.06 (dapper) Package: control-center Severity: Normal Version: GNOME2.14.1 unspecified Gnome-Distributor: Ubuntu Synopsis: no preference in the Gnome Desktop preferences is accessible Bugzilla-Product: control-center Bugzilla-Component: Assistive Technology Preferences Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.14.0) Description: Description of the crash: no preference in the Gnome Desktop preferences is accessible, the application crashes when clicking on a icon Steps to reproduce the crash: 1. open desktop preferences 2. click on any preference you want to edit Expected Results: opens the window related to the preference How often does this happen? always Additional Information: text given on the terminal : (gnome-control-center:7511): Gdk-CRITICAL **: gdk_screen_get_display: assertion `GDK_IS_SCREEN (screen)' failed Debugging Information: Backtrace was generated from '/usr/bin/gnome-control-center' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912582406576 (LWP 7515)] (no debugging symbols found) 0x00002aaaabeb3094 in waitpid () from /lib/libpthread.so.0
+ Trace 67575
Thread 1 (Thread 46912582406576 (LWP 7515))
------- Bug created by bug-buddy at 2006-04-11 19:29 -------
Confirming, the same happens on ALTLinux, control-center 2.14.1.
If this is still a problem, can you please get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
(In reply to comment #2) > If this is still a problem, can you please get us a stack trace with debugging > symbols? Please see http://live.gnome.org/GettingTraces for more information on > how to do so. Thanks in advance! > I use Ubuntu 6.10 now. I have not seen this bug since.
Thanks, I'll close the bug for now, then. Feel free to reopen if it happens again with a current release.