GNOME Bugzilla – Bug 146645
gnome-background-properties crashes
Last modified: 2006-07-21 23:56:30 UTC
Distribution: Debian testing/unstable Package: control-center Severity: normal Version: 2.6.1 Synopsis: gnome-background-properties crashes Bugzilla-Product: control-center Bugzilla-Component: background Bugzilla-Version: 2.6.1 BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: Always you try to execute gnome-background-properties, it crashes Steps to reproduce the crash: 1. Add some backgrounds 2. Delete some of them 3. Try to execute gnome-background-properties Expected Results: It crashes always you try to execute gnome-background-properties How often does this happen? Always Additional Information: Backtrace was generated from '/usr/bin/gnome-background-properties' (no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 2657)] [New Thread 32769 (LWP 2659)] [New Thread 16386 (LWP 2660)] [New Thread 32771 (LWP 2661)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x409e4c0b in waitpid () from /lib/libpthread.so.0
+ Trace 48076
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-09 04:13 ------- Unknown version 2.6.1 in product control-center. Setting version to "1.4.0". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "control-center". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was inductancia@yahoo.es. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
*** Bug 147011 has been marked as a duplicate of this bug. ***
*** Bug 146987 has been marked as a duplicate of this bug. ***
*** Bug 146832 has been marked as a duplicate of this bug. ***
*** Bug 146718 has been marked as a duplicate of this bug. ***
*** Bug 146651 has been marked as a duplicate of this bug. ***
Other than the duplicates already marked, this appears to be a unique stack trace according to a query on the function name gnome_wp_pixbuf_center.
Hi, I have the same problem under debian/testing, with the same version of gnome-center. But my backtrace seems to be a bit different: Backtrace was generated from '/usr/bin/gnome-background-properties' (no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled][New Thread 16384 (LWP 702)] [New Thread 32769 (LWP 703)] [New Thread 16386 (LWP 704)] [New Thread 32771 (LWP 719)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x409dfc0b in waitpid () from /lib/libpthread.so.0
+ Trace 48634
I hope that will help you. Thanks.
A backtrace from a build with debugging symbols and such would help me more, since I am unable to reproduce this crash. And the last comment #7 is a different crash.
I was able to reproduce the exact cause of this bug, It's quite simple: Try to load a backround named ö.jpg (that's o with two dots, scandinavian char.) It's not UTF-8 on my machine but ISO-8859-1 or -15. If I rename the file to ö in UTF-8 it works fine. It seems that Gnome doesn't support my locale... nautilus always renames in UTF-8, so this bug might be related to more than just gnome-background-properties.
I'm not quite sure if the crash in comment #9 is really the same as comment #1. I have it also crashing at startup, and I know that I renamed some files which were added to the gnome-background-properties dialog. All files were in the same directory, and at first sight, none of them have special characters in their file name (some have spaces though, but no accents). I moved the whole directory away, and still it is crashing. Would the crash of comment #9 still happen if the files are deleted or moved to another place, so gnome-background-properties cannot find them anymore? I'm also wondering if the number of images could be related. I had about 150 in the dialog.
Same symptoms here, it crashes even if the file is (re)moved. With only one (ö.jpg) background, I can cleanly close the app though. But when starting it up it crashes again. You can "reset" the backgrounds list by removing ~/.gnome2/backgrounds.xml. The ö character appears as 'ö' in nautilus but as '\366' in the browser for gnome-background-properties. Oh, and when loading ö.jpg, it says "An error occurred while loading or saving configuration information for gnome-background-properties. Some of your configuration settings may not work properly." Clicking details gives "Text contains invalid UTF-8". Should have noticed that before, but when loading a whole dir full of images gnome-panel also crashes and I am saturated by error messages.
Created attachment 31215 [details] [review] fix local encoded filename in background capplet and libbackground This patch (for gnome 2.6 branch but it might apply on HEAD) fixes the problem. If applied, a new release of nautilus must also be done to get the fixes from libbackground.
*** Bug 151707 has been marked as a duplicate of this bug. ***
*** Bug 151641 has been marked as a duplicate of this bug. ***
*** Bug 148472 has been marked as a duplicate of this bug. ***
*** Bug 151820 has been marked as a duplicate of this bug. ***
*** Bug 152520 has been marked as a duplicate of this bug. ***
*** Bug 153510 has been marked as a duplicate of this bug. ***
*** Bug 155525 has been marked as a duplicate of this bug. ***
Could the patch be commited to Gnome 2.8 cvs please?
No. The patch doesn't solve the problem, it only works around the initial import. Since we must store the filename in UTF-8 in XML, this can't work, because there is no method for determining the encoding that the filename is actually in. It works for import, but the next time you run the capplet, the wallpaper may not show up in the list any longer, since we couldn't find the UTF-8 encoded version of the filename. There is no guarantee of what the actual filename encoding might be.
*** Bug 155831 has been marked as a duplicate of this bug. ***
*** Bug 156683 has been marked as a duplicate of this bug. ***
*** Bug 156214 has been marked as a duplicate of this bug. ***
*** Bug 156355 has been marked as a duplicate of this bug. ***
*** Bug 157307 has been marked as a duplicate of this bug. ***
*** Bug 157981 has been marked as a duplicate of this bug. ***
*** Bug 158484 has been marked as a duplicate of this bug. ***
*** Bug 158660 has been marked as a duplicate of this bug. ***
*** Bug 158930 has been marked as a duplicate of this bug. ***
*** Bug 160133 has been marked as a duplicate of this bug. ***
Removed offending filenames from XML file manually. Seems to be a good temporary fix :). Thanks for the help guys
*** Bug 155517 has been marked as a duplicate of this bug. ***
*** Bug 161034 has been marked as a duplicate of this bug. ***
*** Bug 161462 has been marked as a duplicate of this bug. ***
*** Bug 163270 has been marked as a duplicate of this bug. ***
*** Bug 158378 has been marked as a duplicate of this bug. ***
Is this the same as bug 146130? [No reports in 2.8, but marking 2.10 showstopper to make sure it is looked at.]
I tried with multiple desktop-backgrounds on the latest gnome build from CVS HEAD but wasn't able to replicate the bug. The gnome control center version is 2.9.5
*** Bug 166128 has been marked as a duplicate of this bug. ***
Dobey, couldn't you use G_FILENAME_ENCODINGS and or always try both the locale encoding and UTF-8? I think this is how nautilus treats filenames.
*** Bug 152191 has been marked as a duplicate of this bug. ***
*** Bug 166268 has been marked as a duplicate of this bug. ***
*** Bug 166598 has been marked as a duplicate of this bug. ***
*** Bug 166939 has been marked as a duplicate of this bug. ***
*** Bug 167910 has been marked as a duplicate of this bug. ***
*** Bug 167999 has been marked as a duplicate of this bug. ***
*** Bug 168036 has been marked as a duplicate of this bug. ***
*** Bug 168252 has been marked as a duplicate of this bug. ***
*** Bug 168588 has been marked as a duplicate of this bug. ***
The crash is "fixed" in CVS now. We just ignore non-utf8 filenames for now. I've opened a new bug to state that we don't handle invalid UTF-8 in filenames. This bug is now a duplicate of that. *** This bug has been marked as a duplicate of 168604 ***
*** Bug 168696 has been marked as a duplicate of this bug. ***
*** Bug 168770 has been marked as a duplicate of this bug. ***
*** Bug 170970 has been marked as a duplicate of this bug. ***
*** Bug 171263 has been marked as a duplicate of this bug. ***
*** Bug 172785 has been marked as a duplicate of this bug. ***
*** Bug 301007 has been marked as a duplicate of this bug. ***
*** Bug 301383 has been marked as a duplicate of this bug. ***
*** Bug 340525 has been marked as a duplicate of this bug. ***