GNOME Bugzilla – Bug 359487
update to latest xdgmime breaks gnome-vfs - I think
Last modified: 2007-02-07 08:40:44 UTC
Steps to reproduce: 1. Launch any application that uses gnome-vfs 2. Watch it segfault, or 3. Try opening a file with open file dialog, and watch it segfault Stack trace: (gdb) bt
+ Trace 74419
Other information: This problem is happening to me running gnome 2.16 on FreeBSD 6.2-PRERELEASE (stable branch) with gnome-vfs-2.16.1 specifically. I spent some time digging through the code to see what was going wrong, and I think this is what's happened: The new xdgmime code removed several calls to xdg_mime_init() from xdgmime.c, and from what I can figure out, gnome-vfs used to rely on these calls so that the alias_list global was initialised. Since it is now left uninitialised, gnome-vfs segfaults as soon as xdg_mime_unalias_mime_type is called from get_entry (gnome-vfs-mime-info.c:478). I'm afraid that I am not familiar enough with the code to come up with a patch (I don't even know if my conclusion is correct), sorry
I can confirm this problem. I am also running gnome 2.16 on FreeBSD 6.2-Prerelease. Reverting gnome-vfs-2.16.1 back to 2.16.0 fixes the problem.
I can confirm this also. $ uname -a FreeBSD syslaptop 6.1-RELEASE-p7 FreeBSD 6.1-RELEASE-p7 #0: Fri Sep 22 12:41:09 CDT 2006 DemonBob@syslaptop:/usr/obj/usr/src/sys/SYSLAPTOP i386 When i converted back to 2.16.0 everything went back to normal.
*** Bug 359488 has been marked as a duplicate of this bug. ***
Created attachment 74253 [details] [review] Fix crash on FreeBSD The problem is a symbol conflict between gnome-vfs and gtk+. If the private _xdg_mime functions are protected with XDG_PREFIX, then this problem will go away. This should be merged upstream into xdgmime as well.
The above patch for FreeBSD does fix the issue on Sun Solaris 2.8 + 2.9/SPARC as well.
What's the status of this as it's holding up GNOME adoption on Gentoo/FreeBSD? Is there anything I can do to help?
*** Bug 403978 has been marked as a duplicate of this bug. ***
*** Bug 404181 has been marked as a duplicate of this bug. ***
Commited. Thanks.