Bug 391180 – crash in Open Folder:

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 391180 - crash in Open Folder:


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 356435

Product:	gnome-vfs
Classification:	Deprecated
Component:	Other
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	gnome-vfs maintainers
QA Contact:	gnome-vfs maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-31 03:16 UTC by male81
Modified:	2007-01-16 15:30 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description male81 2006-12-31 03:16:38 UTC

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 84987904 vsize: 0 resident: 84987904 share: 0 rss: 27820032 rss_rlim: 0
CPU usage: start_time: 1167534813 rtime: 0 utime: 1259 stime: 0 cutime:1196 cstime: 0 timeout: 63 it_real_value: 0 frequency: 56

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226978704 (LWP 8732)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 98183

Thread 1 (Thread -1226978704 (LWP 8732))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 __fsetlocking
from /lib/tls/i686/cmov/libc.so.6
#8 free
from /lib/tls/i686/cmov/libc.so.6
#9 g_free
from /usr/lib/libglib-2.0.so.0
#10 g_strfreev
from /usr/lib/libglib-2.0.so.0
#11 vfs_module_shutdown
from /usr/lib/gnome-vfs-2.0/modules/libfont-method.so
#12 gnome_vfs_method_get
from /usr/lib/libgnomevfs-2.so.0
#13 g_hash_table_lookup_extended
from /usr/lib/libglib-2.0.so.0
#14 g_hash_table_remove_all
from /usr/lib/libglib-2.0.so.0
#15 g_hash_table_destroy
from /usr/lib/libglib-2.0.so.0
#16 gnome_vfs_get_daemon_volume_monitor_type
from /usr/lib/libgnomevfs-2.so.0
#17 ??
#18 ??
#19 ??
#20 ??
from /usr/lib/libgnomevfs-2.so.0
#21 ??
#22 ??
#23 ??
#24 gnome_vfs_shutdown
from /usr/lib/libgnomevfs-2.so.0
#25 gnome_vfs_shutdown
from /usr/lib/libgnomevfs-2.so.0
#26 POA_Nautilus_MetafileMonitor__init
#27 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#28 ??
#0 __kernel_vsyscall

Comment 1 Christian Kirbach 2006-12-31 11:36:01 UTC

looks unique

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

please install the glib and gnome-vfs packages

Comment 2 André Klapper 2007-01-16 15:30:14 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

This issue has been fixed; the fix will be available in GNOME 2.16.3.

*** This bug has been marked as a duplicate of 356435 ***