Bug 369077 – crash in CD/DVD Creator: Using nautilus to browse...

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 369077 - crash in CD/DVD Creator: Using nautilus to browse...


Summary:	crash in CD/DVD Creator: Using nautilus to browse...


Status:	RESOLVED DUPLICATE of bug 356672

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-01 21:18 UTC by masonsimon+ubuntu
Modified:	2006-11-01 21:21 UTC

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

Description masonsimon+ubuntu 2006-11-01 21:18:52 UTC

What were you doing when the application crashed?
Using nautilus to browse a directory on a mounted FAT32 partition, which generally works fine.


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

Memory status: size: 89989120 vsize: 0 resident: 89989120 share: 0 rss: 28889088 rss_rlim: 0
CPU usage: start_time: 1162408902 rtime: 0 utime: 823 stime: 0 cutime:772 cstime: 0 timeout: 51 it_real_value: 0 frequency: 0

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

+ Trace 81610

Thread 1 (Thread -1226598736 (LWP 4838))

#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 fm_directory_view_bump_zoom_level
#11 gtk_tree_model_unref_node
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_tree_model_sort_convert_iter_to_child_iter
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_tree_model_unref_node
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_tree_model_iter_nth_child
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_tree_model_iter_nth_child
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_tree_model_iter_nth_child
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_tree_model_iter_nth_child
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_tree_row_reference_free
from /usr/lib/libgtk-x11-2.0.so.0
#19 _gtk_tree_selection_row_is_selectable
from /usr/lib/libgtk-x11-2.0.so.0
#20 _gtk_tree_selection_internal_select_node
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_tree_view_scroll_to_cell
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_tree_view_set_cursor_on_cell
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_tree_view_set_cursor
from /usr/lib/libgtk-x11-2.0.so.0
#24 fm_directory_view_bump_zoom_level
#25 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#26 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#27 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#28 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#29 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#30 POA_Nautilus_MetafileMonitor__init
#31 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#32 ??
#0 __kernel_vsyscall

Comment 1 Behdad Esfahbod 2006-11-01 21:21:42 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!
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 bug has been marked as a duplicate of 356672 ***