Bug 419870 – crash in Computer: logging in

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 419870 - crash in Computer: logging in


Summary:	crash in Computer: logging in


Status:	RESOLVED DUPLICATE of bug 349551

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-03-18 20:30 UTC by fmulder4
Modified:	2007-03-18 21:06 UTC

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

Description fmulder4 2007-03-18 20:30:44 UTC

What were you doing when the application crashed?
logging in


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 317206528 vsize: 317206528 resident: 4165632 share: 12988416 rss: 17154048 rss_rlim: 1118202880
CPU usage: start_time: 1174249824 rtime: 41 utime: 36 stime: 5 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47577532433024 (LWP 3494)]
(no debugging symbols found)
0x00002b457f695c5f in waitpid () from /lib64/libpthread.so.0

+ Trace 119832

Thread 1 (Thread 47577532433024 (LWP 3494))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /opt/gnome/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib64/libc.so.6
#4 abort
from /lib64/libc.so.6
#5 g_logv
from /opt/gnome/lib64/libglib-2.0.so.0
#6 g_log
from /opt/gnome/lib64/libglib-2.0.so.0
#7 nautilus_directory_async_state_changed
#8 nautilus_directory_async_state_changed
#9 nautilus_directory_async_state_changed
#10 nautilus_directory_async_state_changed
#11 nautilus_undo_transaction_unregister_object
#12 nautilus_undo_transaction_unregister_object
#13 g_hash_table_foreach
from /opt/gnome/lib64/libglib-2.0.so.0
#14 nautilus_undo_transaction_unregister_object
#15 g_closure_invoke
from /opt/gnome/lib64/libgobject-2.0.so.0
#16 g_signal_override_class_closure
from /opt/gnome/lib64/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /opt/gnome/lib64/libgobject-2.0.so.0
#18 g_signal_emit
from /opt/gnome/lib64/libgobject-2.0.so.0
#19 gnome_vfs_job_get_count
from /opt/gnome/lib64/libgnomevfs-2.so.0
#20 g_main_context_dispatch
from /opt/gnome/lib64/libglib-2.0.so.0
#21 g_main_context_prepare
from /opt/gnome/lib64/libglib-2.0.so.0
#22 g_main_loop_run
from /opt/gnome/lib64/libglib-2.0.so.0
#23 gtk_main
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#24 POA_Nautilus_MetafileMonitor__init
#25 __libc_start_main
from /lib64/libc.so.6
#26 g_cclosure_marshal_VOID__ENUM
#27 ??
#28 ??
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Christian Kirbach 2007-03-18 21:06:08 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 349551 ***