Bug 402610 – 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 402610 - crash in Open Folder:


Summary:	crash in Open Folder:


Status:	RESOLVED INCOMPLETE

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

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

Reported:	2007-01-30 21:29 UTC by jorgevalenciag
Modified:	2007-05-23 18:31 UTC

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

Description jorgevalenciag 2007-01-30 21:29:21 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: 119218176 vsize: 0 resident: 119218176 share: 0 rss: 36110336 rss_rlim: 0
CPU usage: start_time: 1170114333 rtime: 0 utime: 7001 stime: 0 cutime:6456 cstime: 0 timeout: 545 it_real_value: 0 frequency: 2822

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

+ Trace 106661

Thread 1 (Thread -1227229520 (LWP 5034))

#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 gnome_vfs_uri_unref
from /usr/lib/libgnomevfs-2.so.0
#5 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#6 ??
#7 ??
#8 ??
#9 async_job_callback_map_destroy
from /usr/lib/libgnomevfs-2.so.0
#10 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#11 ??
#12 ??
#13 ??
#14 ??
from /usr/lib/libgthread-2.0.so.0
#15 ??
#16 ??
from /usr/lib/libglib-2.0.so.0
#17 ??
#18 g_slice_alloc
from /usr/lib/libglib-2.0.so.0
#19 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#20 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#21 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#22 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#23 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#24 POA_Nautilus_MetafileMonitor__init
#25 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#26 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-02-04 17:43:08 UTC

(looks like rhythmbox bug 366346)

Thanks for taking the time to report this bug.
Unfortunately, the 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.

Could you please help fixing this by installing some debugging packages [1], start Nautilus as normal, and try to reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance!

[1] Please install the following debug packages provided by Ubuntu: nautilus-dbg, libglib2.0-0-dbg, libgtk2.0-0-dbg, libpango1.0-0-dbg, libgnomevfs2-0-dbg, and libgnomeui-0-dbg.

More details can be found here: http://live.gnome.org/GettingTraces

Also, this bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.

Comment 2 Christian Kirbach 2007-03-21 17:15:56 UTC

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

Comment 3 Christian Kirbach 2007-03-21 17:17:04 UTC

yes looks like rhythmbox bug 366346 . there a developers believes gnome-vfs (which is crashing) is used in a wrong way. possibly nautilus is doing this, too.

however, we need debugging symbols. please see comment #1

Comment 4 Christian Kirbach 2007-05-23 18:31:56 UTC

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!