Bug 370833 – crash in CD/DVD Creator: Opening a folder.

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 370833 - crash in CD/DVD Creator: Opening a folder.


Summary:	crash in CD/DVD Creator: Opening a folder.


Status:	RESOLVED DUPLICATE of bug 350975

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-05 02:44 UTC by bugbuddy
Modified:	2006-11-05 04:06 UTC

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

Description bugbuddy 2006-11-05 02:44:31 UTC

What were you doing when the application crashed?
Opening a folder.


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Permissive
Accessibility: Disabled
----------- .xsession-errors ---------------------
(glom:3669): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed
(glom:3669): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed
Unable to connect to yum-updatesd...
Unable to connect to yum-updatesd...
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x0 specified for 0x1202a9d ().
(Gecko:3038): Gtk-CRITICAL **: gtk_widget_reparent: assertion `widget->parent != NULL' failed
Unable to connect to yum-updatesd...
Max failures exceeded, exiting now
** (nautilus:2842): CRITICAL **: nautilus_file_get_uri: assertion `NAUTILUS_IS_FILE (file)' failed
** (bug-buddy:3823): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Memory status: size: 91049984 vsize: 0 resident: 91049984 share: 0 rss: 20824064 rss_rlim: 0
CPU usage: start_time: 1162687622 rtime: 0 utime: 563 stime: 0 cutime:496 cstime: 0 timeout: 67 it_real_value: 0 frequency: 0

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 -1208706304 (LWP 2842)]
(no debugging symbols found)
0x009de402 in __kernel_vsyscall ()

+ Trace 83045

Thread 1 (Thread -1208706304 (LWP 2842))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 g_str_hash
from /lib/libglib-2.0.so.0
#5 g_hash_table_lookup
from /lib/libglib-2.0.so.0
#6 nautilus_file_get_uri
#7 nautilus_file_get_uri
#8 nautilus_directory_async_state_changed
#9 nautilus_directory_async_state_changed
#10 nautilus_undo_transaction_unregister_object
#11 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#12 g_cclosure_marshal_VOID__ENUM
#13 nautilus_marshal_BOOLEAN__POINTER
#14 nautilus_marshal_BOOLEAN__POINTER
#15 eel_read_entire_file_async
from /usr/lib/libeel-2.so.2
#16 gnome_vfs_async_get_job_limit
from /usr/lib/libgnomevfs-2.so.0
#17 gnome_vfs_async_get_job_limit
from /usr/lib/libgnomevfs-2.so.0
#18 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#19 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#20 g_main_context_check
from /lib/libglib-2.0.so.0
#21 g_main_loop_run
from /lib/libglib-2.0.so.0
#22 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#23 POA_Nautilus_MetafileMonitor__init
#24 __libc_start_main
from /lib/libc.so.6
#25 g_cclosure_marshal_VOID__ENUM
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-11-05 04:06:35 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 350975 ***