Bug 391255 – crash after updating monitoring

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 391255 - crash after updating monitoring


Summary:	crash after updating monitoring


Status:	RESOLVED DUPLICATE of bug 320020

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

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

URL:
Whiteboard:	nautilus[debugsymbols]

Depends on:
Blocks:

Reported:	2006-12-31 10:53 UTC by Christian Kirbach
Modified:	2007-01-13 11:25 UTC

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

Description Christian Kirbach 2006-12-31 10:53:32 UTC

copied from bug 366364

Comment #13 from tom@tomzilla.org (points: 0) 
2006-12-30 20:05 UTC [reply] 
Here's the traceback with symbols

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

Memory status: size: 251375616 vsize: 251375616 resident: 35774464 share:
22130688 rss: 35774464 rss_rlim: -1
CPU usage: start_time: 1167508846 rtime: 196 utime: 174 stime: 22 cutime:0
cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47739263900192 (LWP 19230)]
0x00002b6b25e0aeef in waitpid () from /lib/libpthread.so.0

+ Trace 98242

Thread 1 (Thread 47739263900192 (LWP 19230))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 nautilus_directory_async_state_changed
at nautilus-directory-async.c line 1917
#4 vfs_file_monitor_add
at nautilus-vfs-directory.c line 105
#5 update_monitoring
at fm-tree-model.c line 1057
#6 update_monitoring_idle_callback
at fm-tree-model.c line 1423
#7 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#8 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#9 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#10 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#11 main
at nautilus-main.c line 372
#12 __libc_start_main
from /lib/libc.so.6
#13 _start
#0 waitpid
from /lib/libpthread.so.0

Comment 1 Christian Kirbach 2006-12-31 10:56:34 UTC

we have all symbols, confirming report

Tom, how did you trigger the crash?

Comment 2 tom 2006-12-31 16:16:49 UTC

I'm running Ubuntu Edgy on amd64.

I wanted look at the directory structure of my audio cd, created with k3b. When I first insert the disc up comes Sound Juicer, which is the default association in my distro. I close Sound Juicer. In the tree view of nautilus there are little triangles indicating that a directory can be viewed. I poked the little triangle next to the name of my audio cd. The little triangle turned downward and then the traceback.

I just tried it with a dvd -- it opens just fine.

Another music cd -- traceback again. It doesn't seem to be peculiar to discs created with k3b.

Comment 3 André Klapper 2007-01-12 02:36:47 UTC

christian: this is most probably a duplicate of bug 320020, what do you think?

Comment 4 Christian Kirbach 2007-01-13 11:25:47 UTC

considering the description on how to trigger, it is.



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