Bug 430518 – 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 430518 - crash in Computer: logging in


Summary:	crash in Computer: logging in


Status:	RESOLVED DUPLICATE of bug 368534

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-04-17 02:23 UTC by gabe
Modified:	2007-04-17 23:12 UTC

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

Description gabe 2007-04-17 02:23:52 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: 291758080 vsize: 291758080 resident: 3952640 share: 10883072 rss: 14835712 rss_rlim: 1792501760
CPU usage: start_time: 1176776565 rtime: 30 utime: 26 stime: 4 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 47967557812864 (LWP 4656)]
0x00002ba04ebc5c5f in waitpid () from /lib64/libpthread.so.0

+ Trace 128401

Thread 1 (Thread 47967557812864 (LWP 4656))

#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 g_assert_warning
from /opt/gnome/lib64/libglib-2.0.so.0
#8 nautilus_clipboard_monitor_emit_changed
#9 g_closure_invoke
from /opt/gnome/lib64/libgobject-2.0.so.0
#10 g_signal_override_class_closure
from /opt/gnome/lib64/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /opt/gnome/lib64/libgobject-2.0.so.0
#12 g_signal_emit
from /opt/gnome/lib64/libgobject-2.0.so.0
#13 gnome_vfs_volume_monitor_client_get_type
from /opt/gnome/lib64/libgnomevfs-2.so.0
#14 dbus_connection_dispatch
from /usr/lib64/libdbus-1.so.3
#15 dbus_server_setup_with_g_main
from /usr/lib64/libdbus-glib-1.so.2
#16 g_main_context_dispatch
from /opt/gnome/lib64/libglib-2.0.so.0
#17 g_main_context_prepare
from /opt/gnome/lib64/libglib-2.0.so.0
#18 g_main_loop_run
from /opt/gnome/lib64/libglib-2.0.so.0
#19 gtk_main
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#20 POA_Nautilus_MetafileMonitor__init
#21 __libc_start_main
from /lib64/libc.so.6
#22 g_cclosure_marshal_VOID__ENUM
#23 ??
#24 ??
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Pedro Villavicencio 2007-04-17 23:12:46 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 368534 ***