GNOME Bugzilla – Bug 469164
Critical warnings on startup
Last modified: 2007-08-28 18:51:17 UTC
Version: 2.19.90 Gtk-Message: Failed to load module "gnomebreakpad": libgnomebreakpad.so: nem lehet megnyitni megosztott objektum fájlt: Nincs ilyen fájl vagy könyvtár Gtk-Message: Failed to load module "gnomebreakpad": libgnomebreakpad.so: nem lehet megnyitni megosztott objektum fájlt: Nincs ilyen fájl vagy könyvtár (gnome-appearance-properties:18895): GLib-CRITICAL **: g_ascii_strcasecmp: assertion `s2 != NULL' failed (gnome-appearance-properties:18895): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed (gnome-appearance-properties:18895): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed (gnome-appearance-properties:18895): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed (gnome-appearance-properties:18895): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed (gnome-appearance-properties:18895): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed (gnome-appearance-properties:18895): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed (gnome-appearance-properties:18895): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed (gnome-appearance-properties:18895): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed (gnome-appearance-properties:18895): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed (gnome-appearance-properties:18895): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed (gnome-appearance-properties:18895): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL' failed Szegmens hiba Distribution: Fedora release 7.90 (Rawhide) Gnome Release: 2.19.6 2007-08-17 (Red Hat, Inc) BugBuddy Version: 2.18.0
Please, ask, what should I post from gdb.
Something what could help: ................................................ 0x0805e196 in gnome_wp_item_new () (gdb) step Single stepping until exit from function gnome_wp_item_new, which has no line number information. Program terminated with signal SIGSEGV, Segmentation fault. The program no longer exists.
I've figured out how to fix it: Workaround: Step 1.: Open Nautilus Step 2.: Choose a background from Edit > Backgrounds... and drag it to the desktop. Step 3.: Now you can use gnome-appearance-properties without crashing. But, please, take a look why is segfaulting if no default values are given.
You need bug-buddy 2.19, but Fedora has only 2.18, this is a known problem: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=251067
The first two messages are from missing bug-buddy, the rest is not.
Attila, I can't reproduce the critical warnings even with no background set. If you can still reproduce the problem, please start appearance-properties from the command line using G_DEBUG=fatal-criticals gdb gnome-appearance-properties (and make sure you have debugging symbols for control-center installed). Then run and continue until you hit the segmentation fault, and post the output of (gdb) bt full Thanks in advance.
Sorry, the error dissapeared. What I have noticed it is that the content of apps > desktop > gnome > background was totally empty when I had the errors. Now if I delete the keys, I have just: (gnome-appearance-properties:28754): GLib-CRITICAL **: g_ascii_strcasecmp: assertion `s2 != NULL' failed This doesn't seems to cause any problem anymore. (I have upgraded control-center to newest version.)
That is still a critical warning that should be fixed (and will cause deliberate crashes with development versions of Gnome), so it would be nice if you could provide the gdb trace anyway. Thanks.
GLib-CRITICAL **: g_ascii_strcasecmp: assertion `s2 != NULL' failed aborting... Program received signal SIGABRT, Aborted.
+ Trace 157554
Thread NaN (LWP 29089)
It seems very odd that set_toolbar_style() has value set to 0x6. It is set from the return value of gconf_client_get_string () which should always be NULL on error.
Do you need some other outputs as well?
If you can install the glib and gconf debug symbols as well, that would be helpful.
It smells of memory corruption of some sort, so it's probably going to be hard to pin down. Does Fedora apply any patches to the package?
Well, sorry guys, but I had a full system crash, so I've lost everything... :( I hope that someone else can jump into this bug auditing... :( I am very sad because of this...
I don't think we can do anything as long as noone can reproduce it. I'm closing it for that reason, but please reopen in case this happens again.