Bug 449665 – crash in CD/DVD Creator: Trying to run a gnome-se...

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 449665 - crash in CD/DVD Creator: Trying to run a gnome-se...


Summary:	crash in CD/DVD Creator: Trying to run a gnome-se...


Status:	RESOLVED DUPLICATE of bug 365638

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-06-21 02:36 UTC by chilli.namesake
Modified:	2007-06-21 02:46 UTC

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

Description chilli.namesake 2007-06-21 02:36:33 UTC

What were you doing when the application crashed?
Trying to run a gnome-session remotely through Apple's X11


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

Memory status: size: 30347264 vsize: 0 resident: 30347264 share: 0 rss: 9560064 rss_rlim: 0
CPU usage: start_time: 1182393118 rtime: 0 utime: 30 stime: 0 cutime:27 cstime: 0 timeout: 3 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 -1226561872 (LWP 8233)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 142568

Thread 1 (Thread -1226561872 (LWP 8233))

#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 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 nautilus_directory_async_state_changed
#10 nautilus_directory_async_state_changed
#11 nautilus_directory_async_state_changed
#12 nautilus_directory_async_state_changed
#13 nautilus_undo_transaction_unregister_object
#14 nautilus_file_get_volume
#15 POA_Nautilus_MetafileMonitor__init
#16 POA_Nautilus_MetafileMonitor__init
#17 POA_Nautilus_MetafileMonitor__init
#18 POA_Nautilus_MetafileMonitor__init
#19 POA_Nautilus_MetafileMonitor__init
#20 POA_Nautilus_MetafileMonitor__init
#21 IOP_start_profiles
from /usr/lib/libORBit-2.so.0
#22 ORBit_OAObject_invoke
from /usr/lib/libORBit-2.so.0
#23 ORBit_small_invoke_adaptor
from /usr/lib/libORBit-2.so.0
#24 ORBit_recv_buffer_return_sys_exception
from /usr/lib/libORBit-2.so.0
#25 ORBit_recv_buffer_return_sys_exception
from /usr/lib/libORBit-2.so.0
#26 ORBit_skel_class_register
from /usr/lib/libORBit-2.so.0
#27 ORBit_handle_request
from /usr/lib/libORBit-2.so.0
#28 giop_connection_handle_input
from /usr/lib/libORBit-2.so.0
#29 link_connection_state_changed
from /usr/lib/libORBit-2.so.0
#30 link_io_add_watch_fd
from /usr/lib/libORBit-2.so.0
#31 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#32 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#33 g_main_context_iteration
from /usr/lib/libglib-2.0.so.0
#34 link_main_iteration
from /usr/lib/libORBit-2.so.0
#35 giop_recv_buffer_get
from /usr/lib/libORBit-2.so.0
#36 ORBit_small_invoke_stub
from /usr/lib/libORBit-2.so.0
#37 ORBit_small_invoke_stub_n
from /usr/lib/libORBit-2.so.0
#38 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#39 ??
#40 ??
#41 ??
#42 ??
#43 ??
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2007-06-21 02:46:18 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 365638 ***