Bug 353514 – crash in Home Folder: relogin

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 353514 - crash in Home Folder: relogin


Summary:	crash in Home Folder: relogin


Status:	RESOLVED DUPLICATE of bug 351713

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-08-30 08:05 UTC by hipsis
Modified:	2006-08-30 09:18 UTC

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

Description hipsis 2006-08-30 08:05:01 UTC

What were you doing when the application crashed?
relogin


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.92 2006-08-22 (Ubuntu)
BugBuddy Version: 2.15.92

Memory status: size: 46338048 vsize: 0 resident: 46338048 share: 0 rss: 15351808 rss_rlim: 0
CPU usage: start_time: 1156925054 rtime: 0 utime: 82 stime: 0 cutime:79 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 -1226160464 (LWP 6304)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 71241

Thread 1 (Thread -1226160464 (LWP 6304))

#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 strlen
from /lib/tls/i686/cmov/libc.so.6
#5 g_strdup
from /usr/lib/libglib-2.0.so.0
#6 nautilus_directory_async_state_changed
#7 nautilus_file_get_uri
#8 nautilus_file_get_uri
#9 nautilus_file_has_volume
#10 nautilus_icon_container_request_update_all
#11 _shortcuts_model_filter_get_type
#12 POA_Nautilus_MetafileMonitor__init
#13 POA_Nautilus_MetafileMonitor__init
#14 nautilus_marshal_BOOLEAN__POINTER
#15 POA_Nautilus_MetafileMonitor__init
#16 POA_Nautilus_MetafileMonitor__init
#17 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#18 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#19 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#23 gtk_widget_show
from /usr/lib/libgtk-x11-2.0.so.0
#24 _shortcuts_model_filter_get_type
#25 nautilus_undo_transaction_unregister_object
#26 fm_directory_view_bump_zoom_level
#27 nautilus_clipboard_monitor_emit_changed
#28 nautilus_directory_async_state_changed
#29 nautilus_directory_async_state_changed
#30 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#31 ??
#32 ??
#33 ??
#34 g_slice_alloc
from /usr/lib/libglib-2.0.so.0
#35 g_source_is_destroyed
from /usr/lib/libglib-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 Fabio Bonelli 2006-08-30 09:18:57 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 351713 ***