Bug 356771 – crash in Open Folder: Inicializando sesion de ...

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 356771 - crash in Open Folder: Inicializando sesion de ...


Summary:	crash in Open Folder: Inicializando sesion de ...


Status:	RESOLVED DUPLICATE of bug 354823

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-09-19 17:40 UTC by ichavero
Modified:	2006-09-19 17:46 UTC

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

Description ichavero 2006-09-19 17:40:43 UTC

What were you doing when the application crashed?
Inicializando sesion de gnome


Distribution: Gentoo Base System version 1.12.5
Gnome Release: 2.16.0 2006-09-18 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 105754624 vsize: 105754624 resident: 9056256 share: 7348224 rss: 9056256 rss_rlim: -1
CPU usage: start_time: 1158687603 rtime: 5 utime: 5 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47164012888304 (LWP 6808)]
0x00002ae538e98a84 in waitpid () from /lib/libpthread.so.0

+ Trace 72762

Thread 1 (Thread 47164012888304 (LWP 6808))

#0 waitpid
from /lib/libpthread.so.0
#1 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 dbus_connection_send_with_reply
from /usr/lib/libdbus-1.so.3
#4 dbus_connection_send_with_reply_and_block
from /usr/lib/libdbus-1.so.3
#5 gnome_vfs_volume_monitor_client_get_type
from /usr/lib/libgnomevfs-2.so.0
#6 gnome_vfs_volume_monitor_client_get_type
from /usr/lib/libgnomevfs-2.so.0
#7 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#8 g_object_new
from /usr/lib/libgobject-2.0.so.0
#9 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#10 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#11 g_object_new
from /usr/lib/libgobject-2.0.so.0
#12 gnome_vfs_volume_monitor_unref
from /usr/lib/libgnomevfs-2.so.0
#13 POA_Nautilus_MetafileFactory__fini
#14 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#15 g_object_new
from /usr/lib/libgobject-2.0.so.0
#16 bonobo_object_get_poa
from /usr/lib/libbonobo-2.so.0
#17 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#18 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_object_new
from /usr/lib/libgobject-2.0.so.0
#20 POA_Nautilus_MetafileFactory__fini
#21 POA_Nautilus_MetafileFactory__fini
#22 __libc_start_main
from /lib/libc.so.6
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#0 waitpid
from /lib/libpthread.so.0

Comment 1 Karsten Bräckelmann 2006-09-19 17:46:37 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 354823 ***