Bug 406297 – crash in CD/DVD Creator: browsing an NTFS harddri...

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 406297 - crash in CD/DVD Creator: browsing an NTFS harddri...


Summary:	crash in CD/DVD Creator: browsing an NTFS harddri...


Status:	RESOLVED DUPLICATE of bug 368534

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:	2007-02-10 04:28 UTC by onidraky
Modified:	2007-02-10 13:38 UTC

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

Description onidraky 2007-02-10 04:28:56 UTC

What were you doing when the application crashed?
browsing an NTFS harddrive


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

Memory status: size: 286990336 vsize: 286990336 resident: 52477952 share: 25395200 rss: 52477952 rss_rlim: -1
CPU usage: start_time: 1171055943 rtime: 10373 utime: 8609 stime: 1764 cutime:68855 cstime: 12289 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47162943679056 (LWP 5334)]
(no debugging symbols found)
0x00002ae4f683deef in waitpid () from /lib/libpthread.so.0

+ Trace 109443

Thread 1 (Thread 47162943679056 (LWP 5334))

#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 raise
from /lib/libc.so.6
#4 abort
from /lib/libc.so.6
#5 g_logv
from /usr/lib/libglib-2.0.so.0
#6 g_log
from /usr/lib/libglib-2.0.so.0
#7 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#8 fm_directory_view_bump_zoom_level
#9 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#13 fm_directory_view_bump_zoom_level
#14 g_source_get_current_time
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 POA_Nautilus_MetafileMonitor__init
#20 __libc_start_main
from /lib/libc.so.6
#21 ??
#22 ??
#23 ??
#0 waitpid
from /lib/libpthread.so.0

Comment 1 André Klapper 2007-02-10 13:38:30 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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