Bug 378699 – crash in CD/DVD Creator: une recherche sur mon di...

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 378699 - crash in CD/DVD Creator: une recherche sur mon di...


Summary:	crash in CD/DVD Creator: une recherche sur mon di...


Status:	RESOLVED DUPLICATE of bug 363856

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-24 02:25 UTC by th3_c0w
Modified:	2006-11-24 19:22 UTC

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

Description th3_c0w 2006-11-24 02:25:51 UTC

What were you doing when the application crashed?
une recherche sur mon disque en ntfs géré par ntfs3g


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

Memory status: size: 83718144 vsize: 0 resident: 83718144 share: 0 rss: 22933504 rss_rlim: 0
CPU usage: start_time: 1164323705 rtime: 0 utime: 486 stime: 0 cutime:438 cstime: 0 timeout: 48 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 -1227053392 (LWP 4717)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 88940

Thread 1 (Thread -1227053392 (LWP 4717))

#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 nautilus_file_get_uri
#5 nautilus_file_get_parent_uri
#6 fm_directory_view_bump_zoom_level
#7 fm_directory_view_bump_zoom_level
#8 fm_directory_view_bump_zoom_level
#9 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#10 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#11 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#12 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#13 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#14 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#15 POA_Nautilus_MetafileMonitor__init
#16 fm_directory_view_bump_zoom_level
#17 fm_directory_view_bump_zoom_level
#18 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#19 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#23 nautilus_directory_async_state_changed
#24 nautilus_marshal_BOOLEAN__POINTER
#25 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#26 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#29 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#30 nautilus_marshal_BOOLEAN__POINTER
#31 nautilus_marshal_BOOLEAN__POINTER
#32 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#33 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#34 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#35 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#36 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#37 POA_Nautilus_MetafileMonitor__init
#38 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#39 ??
#0 __kernel_vsyscall

Comment 1 Jens Granseuer 2006-11-24 19:22:53 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.

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 and attach it to the other bug? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!


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