Bug 440615 – crash in Computer: gksudo nautilus, looking...

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 440615 - crash in Computer: gksudo nautilus, looking...


Summary:	crash in Computer: gksudo nautilus, looking...


Status:	RESOLVED DUPLICATE of bug 368958

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-05-23 02:50 UTC by gigaferz
Modified:	2007-05-23 13:44 UTC

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

Description gigaferz 2007-05-23 02:50:17 UTC

What were you doing when the application crashed?
gksudo nautilus, looking for firefox folder, did whereis firefox in terminal, then went to usr/bin


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

Memory status: size: 77918208 vsize: 0 resident: 77918208 share: 0 rss: 27398144 rss_rlim: 0
CPU usage: start_time: 1179887922 rtime: 0 utime: 3941 stime: 0 cutime:3650 cstime: 0 timeout: 291 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 -1227028816 (LWP 5809)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 135629

Thread 1 (Thread -1227028816 (LWP 5809))

#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 fm_directory_view_bump_zoom_level
#11 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#12 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#16 _gtk_action_emit_activate
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_action_new
from /usr/lib/libgtk-x11-2.0.so.0
#18 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#22 gtk_accel_group_activate
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_accel_groups_activate
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_window_activate_key
from /usr/lib/libgtk-x11-2.0.so.0
#25 gtk_window_activate_key
from /usr/lib/libgtk-x11-2.0.so.0
#26 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#27 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#28 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#29 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#31 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#32 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#33 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#34 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#35 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#36 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#37 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#38 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#39 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#40 POA_Nautilus_MetafileMonitor__init
#41 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#42 ??
#0 __kernel_vsyscall

Comment 1 palfrey 2007-05-23 13:44:36 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 368958 ***