Bug 366920 – Crash in fs_module_create

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 366920 - Crash in fs_module_create


Summary:	Crash in fs_module_create


Status:	RESOLVED DUPLICATE of bug 373226

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

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

URL:
Whiteboard:

Duplicates:	378318 (view as bug list)
Depends on:
Blocks:

Reported:	2006-10-29 15:02 UTC by johnsonr
Modified:	2006-12-22 06:38 UTC

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

Description johnsonr 2006-10-29 15:02:16 UTC

Version: 2.16.1

What were you doing when the application crashed?
trying to save a file onto a floppy


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

Memory status: size: 72818688 vsize: 0 resident: 72818688 share: 0 rss: 23986176 rss_rlim: 0
CPU usage: start_time: 1162133925 rtime: 0 utime: 288 stime: 0 cutime:265 cstime: 0 timeout: 23 it_real_value: 0 frequency: 2

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

(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 -1227310912 (LWP 6346)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 79803

Thread 1 (Thread -1227310912 (LWP 6346))

#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 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 fs_module_create
from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
#11 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#12 fs_module_init
from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
#13 gnome_vfs_connect_to_server
from /usr/lib/libgnomevfs-2.so.0
#14 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#15 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#16 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#17 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#18 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#19 main
#0 __kernel_vsyscall

Comment 1 Paolo Maggi 2006-10-29 15:17:35 UTC

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!

It seems a crash in gnome-vfs.

Note that there is a bug in evolution (bug #361773) with a very similar stack trace.

Comment 2 Jens Granseuer 2006-11-23 22:30:45 UTC

*** Bug 378318 has been marked as a duplicate of this bug. ***

Comment 3 Nickolay V. Shmyrev 2006-12-22 06:38:40 UTC


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