GNOME Bugzilla – Bug 587544
crash in File Management: Opening nautilus prefs.
Last modified: 2009-07-08 11:36:14 UTC
Version: 2.24.2 What were you doing when the application crashed? Opening nautilus prefs. Distribution: Fedora release 10 (Cambridge) Gnome Release: 2.24.3 2009-01-16 (Red Hat, Inc) BugBuddy Version: 2.24.2 System: Linux 2.6.27.24-170.2.68.fc10.i686 #1 SMP Wed May 20 23:10:16 EDT 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Bluecurve Memory status: size: 42127360 vsize: 42127360 resident: 19427328 share: 14647296 rss: 19427328 rss_rlim: 18446744073709551615 CPU usage: start_time: 1246469818 rtime: 55 utime: 51 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus-file-management-properties' [?1034h[Thread debugging using libthread_db enabled] [New Thread 0xb8071780 (LWP 23578)] 0x0017a416 in __kernel_vsyscall ()
+ Trace 216283
Thread 1 (Thread 0xb8071780 (LWP 23578))
The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (110 sec old) --------------------- info: 0, warning: 0, error: 3 Done info: 0, warning: 0, error: 3 Done info: 0, warning: 5, error: 14 Done info: 0, warning: 5, error: 14 Done info: 0, warning: 5, error: 15 Done info: 0, warning: 5, error: 14 Done [ConvConfHandler] isPreferred contentType: multipart/x-mixed-replace [Wed, 01 Jul 2009 17:35:25 GMT] FATAL An error occurred when content is loaded. [TypeError] doc.location is null --------------------------------------------------
This may well be a dup. of one I reported via BugBuddy a couple of days ago under 'phoenix@fnxweb.com', but bugzilla wasn't terribly responsive at the time so I don't know if if it got through, and I can't for the life of me get any combo. of the search pages to report anything raised by me under either email address :-/ Some more info. on this crash as I delved into the debugger to get to the bottom of it; this is similar to stuff that's been reported over the years, but it's always been (AFAICS) a user c*ck-up that's caused the fault). It's down to unchecked pointers when fetching prefs. In this case, I had the following gconf entries: <entry name="default_folder_viewer" mtime="1005256235" muser="neil" type="int" value="0"></entry> <entry name="preview_sound" mtime="1012655762" muser="neil" type="int" value="1"></entry> These are (now?) apparently supposed to be of type string, and so the fetch fails, but the NULL returned is then dereferenced anyway. Note that these values *were not knowingly set manually* by be, they can only have been set by nautilus itself at some point in the (maybe distant) past. It seems to me that a basic pointer check and humane error message to the user would get past this. Having found the names of the offending prefs. in the debugger, I used gconf-editor to clear them back the the current defaults, and all is now well.
Yeah, this is due to a configuration problem from some time ago, it should be solved in more recent versions of Nautilus; closing as OBSOLETE.