Bug 365949 – crash while opening 'preferences' in Nautilus

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 365949 - crash while opening 'preferences' in Nautilus


Summary:	crash while opening 'preferences' in Nautilus


Status:	RESOLVED DUPLICATE of bug 357955

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-27 21:09 UTC by wojnar321
Modified:	2006-10-31 23:50 UTC

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

Description wojnar321 2006-10-27 21:09:22 UTC

What were you doing when the application crashed?
Próba otwarcia preferencji Nautilusa


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

Memory status: size: 78311424 vsize: 0 resident: 78311424 share: 0 rss: 26378240 rss_rlim: 0
CPU usage: start_time: 1161982095 rtime: 0 utime: 383 stime: 0 cutime:372 cstime: 0 timeout: 11 it_real_value: 0 frequency: 1

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 -1226778960 (LWP 4886)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 78981

Thread 1 (Thread -1226778960 (LWP 4886))

#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 POA_Nautilus_MetafileMonitor__init
#5 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#6 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#7 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#8 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#10 _gtk_action_emit_activate
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_action_activate
from /usr/lib/libgtk-x11-2.0.so.0
#12 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#13 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#17 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_menu_shell_activate_item
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_menu_shell_append
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_menu_reorder_child
from /usr/lib/libgtk-x11-2.0.so.0
#21 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#22 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#23 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#27 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#30 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.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_loop_run
from /usr/lib/libglib-2.0.so.0
#34 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#35 POA_Nautilus_MetafileMonitor__init
#36 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#37 ??
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-10-31 23:50:53 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 357955 ***