Bug 368462 – crash in CD/DVD Creator: Browsing network servers...

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 368462 - crash in CD/DVD Creator: Browsing network servers...


Summary:	crash in CD/DVD Creator: Browsing network servers...


Status:	RESOLVED DUPLICATE of bug 348161

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-10-31 18:52 UTC by eric.mundstock
Modified:	2006-11-02 18:49 UTC

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

Description eric.mundstock 2006-10-31 18:52:23 UTC

What were you doing when the application crashed?
Browsing network servers with nautilus.


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

Memory status: size: 84697088 vsize: 0 resident: 84697088 share: 0 rss: 30695424 rss_rlim: 0
CPU usage: start_time: 1162313751 rtime: 0 utime: 851 stime: 0 cutime:798 cstime: 0 timeout: 53 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 -1226709328 (LWP 4786)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 81095

Thread 1 (Thread -1226709328 (LWP 4786))

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

Comment 1 Behdad Esfahbod 2006-10-31 19:18:15 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 367701 ***

Comment 2 Karsten Bräckelmann 2006-10-31 22:38:03 UTC

Actually, it's the same as this issue... :)

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

Comment 3 Behdad Esfahbod 2006-11-02 18:49:48 UTC

Ah, sorry, didn't see you already reduped this one.

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