Bug 368280 – crash in Open 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 368280 - crash in Open Folder:


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 349840

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 13:22 UTC by samuele80
Modified:	2006-10-31 13:48 UTC

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

Description samuele80 2006-10-31 13:22:03 UTC

What were you doing when the application crashed?



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

Memory status: size: 42127360 vsize: 0 resident: 42127360 share: 0 rss: 12042240 rss_rlim: 0
CPU usage: start_time: 1162300906 rtime: 0 utime: 37 stime: 0 cutime:36 cstime: 0 timeout: 1 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 -1227327824 (LWP 4932)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 80960

Thread 1 (Thread -1227327824 (LWP 4932))

#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 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 nautilus_file_ref
#11 nautilus_directory_ref
#12 POA_Nautilus_MetafileMonitor__init
#13 POA_Nautilus_MetafileMonitor__init
#14 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#15 g_object_set
from /usr/lib/libgobject-2.0.so.0
#16 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#17 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#18 g_object_new
from /usr/lib/libgobject-2.0.so.0
#19 POA_Nautilus_MetafileMonitor__init
#20 POA_Nautilus_MetafileMonitor__init
#21 POA_Nautilus_MetafileMonitor__init
#22 POA_Nautilus_MetafileMonitor__init
#23 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#24 g_object_set
from /usr/lib/libgobject-2.0.so.0
#25 POA_Nautilus_MetafileMonitor__init
#26 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#27 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#28 gtk_widget_new
from /usr/lib/libgtk-x11-2.0.so.0
#29 POA_Nautilus_MetafileMonitor__init
#30 POA_Nautilus_MetafileMonitor__init
#31 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#32 ??
#33 ??
#34 ??
#35 ??
#36 ??
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-10-31 13:48:04 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 349840 ***