Bug 406945 – crash in CD/DVD Creator: backing up from IOGEAR B...

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 406945 - crash in CD/DVD Creator: backing up from IOGEAR B...


Summary:	crash in CD/DVD Creator: backing up from IOGEAR B...


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-12 04:41 UTC by jwcox45
Modified:	2007-02-21 16:59 UTC

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

Description jwcox45 2007-02-12 04:41:28 UTC

What were you doing when the application crashed?
backing up from IOGEAR BOSS NAS appliance


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

Memory status: size: 235175936 vsize: 235175936 resident: 33730560 share: 21602304 rss: 33730560 rss_rlim: -1
CPU usage: start_time: 1041810699 rtime: 468 utime: 448 stime: 20 cutime:0 cstime: 0 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 47551594355280 (LWP 4507)]
(no debugging symbols found)
0x00002b3f73e68eef in waitpid () from /lib/libpthread.so.0

+ Trace 109984

Thread 1 (Thread 47551594355280 (LWP 4507))

#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 Christian Kirbach 2007-02-12 21:58:44 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.


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

Comment 2 André Klapper 2007-02-21 16:57:43 UTC

christian: the problem with the traces in bug 352592, bug 368958 and bug 368534 is that they are very generic. the traces do not exactly match each other, and alex (nautilus dev) told me that "it's hard to tell, would be nice to see the assert output". perhaps this is nitpicking, but i'd really like to try to keep nautilus bugzilla as clean as possible, because the nautilus-2.16 situation was already pretty critical a few months ago.

Comment 3 André Klapper 2007-02-21 16:59:09 UTC

jwcox45: 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 ***