I have come up with a way to reproduce this crash. It seems to be
triggered by some GNOME functionality which may or may not be supported
in Ubuntu but is configured by Mandriva by default. (We switched
recently and mostly kept our home directories intact.)
Mandriva configures a bunch of file brow
It was already installed when I got the last backtrace.
[EMAIL PROTECTED]:~$ dpkg -l | grep dbg
ii libglib2.0-0-dbg 2.10.3-0ubuntu1The GLib
libraries and debugging symbols
ii libgnomevfs2-0-dbg 2.14.2-0ubuntu1GNOME virtual
file-system (debuggin
Could you get a backtrace with libgnomevfs2-0-dbg installed?
--
User-specific: Gnome file dialogs crash every time
https://launchpad.net/bugs/58962
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Got some debug info installed, though not quite enough. The dbg package
for libgtk-2.0 doesn't seem to include some of the module subdirectories
so I can't see what's going on in libgnome-vfs.so. Traceback with
partial symbols below.
What I can see is that we seem to be crashing while trying to u
I don't believe we are using any bookmarks.
--
User-specific: Gnome file dialogs crash every time
https://launchpad.net/bugs/58962
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thanks for your bug report. Do you use any remote bookmarks?
** Changed in: gtk+2.0 (Ubuntu)
Importance: Untriaged => Medium
Assignee: (unassigned) => Ubuntu Desktop Bugs
Status: Unconfirmed => Needs Info
--
User-specific: Gnome file dialogs crash every time
https://launchpad.net/
** Changed in: Ubuntu
Sourcepackagename: None => gtk+2.0
--
User-specific: Gnome file dialogs crash every time
https://launchpad.net/bugs/58962
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Looks like I left out some machine information: the machine is using the
i386 install (Pentium III 866MHz coppermine). Graphics card is an old
nvidia card, not using the proprietary driver at the moment. The exact
card probably doesn't matter because the crash reproduces in a VNC
session as long as
