GNOME Bugzilla – Bug 317606
nautilus (xml ??) crash when umounting a USB key
Last modified: 2006-10-29 19:18:02 UTC
Steps to reproduce: It happens sometimes when umounting a usb key but it's not easily reproducable Stack trace: BACKTRACE : Using host libthread_db library "/lib/tls/libthread_db.so.1". Core was generated by `/opt/STools/gnome-2.10/bin/nautilus'.
+ Trace 63281
Thread 7 (process 29647)
Other information: Everything is from gnome 2.10.2 repository (nautilus, gnome-vfs, libxml2) hal is the latest from FC3
Thanks for your bug report! This looks extremely suspicious - gnome_vfs_mime_set_icon should definitly not further invoke anything, although it shouldn't have been called in the first place. Are you sure that you're not on GnomeVFS 2.8? Is this a home-brewn version of Nautilus? If not, please install some more packages: http://live.gnome.org/GettingTraces
Hmm. I'm not sure my level (I'm just an IT not a develooper) allows me to fully understand your question (Is it some sort of enigma for a future Grim Fandango II :-) ). What I know is : * I'm sure gnome-vfs is 2.10 *BUT, user was a former 2.8 user and it may have kept some 2.8 config files. But as far as I know, except for immodule or gtk engines, there's no pieces of code in config files (at least not for gnome-vfs/nautilus but maybe I'm wrong) Anyway, I just realized I slightly patched and reinstalled gnome-vfs . So the bug could have been a side effect of this : not exactly the same libgnomevfs in memory than on the filesystem, so a crash could occur next time the system has to reload it. If so, sorry for the bug, that's not a gnome one.
Opening a terminal and entering lsof | grep -e nautilus.*libgnomevfs while Nautilus is running should do the trick.
It gives me libgnomevfs-2.so.0.1000.1
I was rather interested in the prefix of this library path. While you're at it, maybe lsof | grep -e libgnomevfs should be better because it also tells us what the GnomeVFS daemon uses.
Please append the whole output of the above command.
To make it more readable, I did : lsof|grep gnomevfs|awk '{print $1" "$9}'|uniq gnome-ses /opt/STools/gnome-2.10/lib/libgnomevfs-2.so.0.1000.1 gnome-set /opt/STools/gnome-2.10/lib/libgnomevfs-2.so.0.1000.1 gnome-smp /opt/STools/gnome-2.10/lib/libgnomevfs-2.so.0.1000.1 gnome-pan /opt/STools/gnome-2.10/lib/libgnomevfs-2.so.0.1000.1 gnome-vol /opt/STools/gnome-2.10/lib/libgnomevfs-2.so.0.1000.1 wnck-appl /opt/STools/gnome-2.10/lib/libgnomevfs-2.so.0.1000.1 gnome-vfs /opt/STools/gnome-2.10/lib/libgnomevfs-2.so.0.1000.1 gpilot-ap /opt/STools/gnome-2.10/lib/libgnomevfs-2.so.0.1000.1 gnubiff /opt/STools/gnome-2.10/lib/libgnomevfs-2.so.0.1000.1 drivemoun /opt/STools/gnome-2.10/lib/libgnomevfs-2.so.0.1000.1 clock-app /opt/STools/gnome-2.10/lib/libgnomevfs-2.so.0.1000.1 notificat /opt/STools/gnome-2.10/lib/libgnomevfs-2.so.0.1000.1 mixer_app /opt/STools/gnome-2.10/lib/libgnomevfs-2.so.0.1000.1 gpilotd /opt/STools/gnome-2.10/lib/libgnomevfs-2.so.0.1000.1 thunderbi /opt/STools/gnome-2.10/lib/libgnomevfs-2.so.0.1000.1 gnome-ter /opt/STools/gnome-2.10/lib/libgnomevfs-2.so.0.1000.1 evolution /opt/STools/gnome-2.10/lib/libgnomevfs-2.so.0.1000.1 nautilus /opt/STools/gnome-2.10/lib/libgnomevfs-2.so.0.1000.1 firefox-b /opt/STools/gnome-2.10/lib/libgnomevfs-2.so.0.1000.1 evolution /opt/STools/gnome-2.10/lib/libgnomevfs-2.so.0.1000.1 soffice.b /opt/STools/gnome-2.10/lib/libgnomevfs-2.so.0.1000.1 I check user's config file. The only thing I found which seems related to gnomevfs is this entry in the saved_state file : ADD 503316551 "def" "/system/gnome_vfs" "IOR:01a2..... I wonder what kind of personal configuration of gnome-vfs is saved ? Anyway, this could be a "saved session" from his former 2.8 environment. (Even if I doubt it , since I ask users to delete their config files before migrating). Thank you for all your efforts, Christian, but I just recheck all my users bt, and this is definitively the only one with such a crash. So It's really not annoying. I posted more as an informational purpose (in case of stack dup)
definitely a crash in libxml2, reassigning is this still an issue with the latest version?
libxml2 version 2.4.13 ? This is from Jan 14 2002, and the reader API was started to be added to libxml2 in 2.4.29, huh ! Now for the crash I habe no contect information, xmlTextReaderGetAttribute do call xmlSplitQName2, its first argument is tested against NULL, the second argument is valid, I don't see how this can crash. Where on what instruction and what is the data provided ? As is this is useless to me sorry... Daniel
ool, can you please install the libxml and gnome-vfs debugging packages? please see http://live.gnome.org/GettingTraces
oll, any news on this (with regard to christian's latest comment)? thanks in advance!
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!