Bug 354815 – crash in Home Folder: Nothing

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 354815 - crash in Home Folder: Nothing


Summary:	crash in Home Folder: Nothing


Status:	RESOLVED DUPLICATE of bug 350758

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-07 17:22 UTC by ltkun.lucifer
Modified:	2006-09-07 19:27 UTC

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

Description ltkun.lucifer 2006-09-07 17:22:34 UTC

What were you doing when the application crashed?
Nothing


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 21729280 vsize: 0 resident: 21729280 share: 0 rss: 7622656 rss_rlim: 0
CPU usage: start_time: 1157649707 rtime: 0 utime: 6 stime: 0 cutime:5 cstime: 0 timeout: 1 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 -1226238288 (LWP 21792)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 71816

Thread 1 (Thread -1226238288 (LWP 21792))

#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 *__GI_raise
from /lib/tls/i686/cmov/libc.so.6
#6 *__GI_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 oobs_session_get
from /usr/lib/liboobs-1.so.0
#11 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#12 g_object_set
from /usr/lib/libgobject-2.0.so.0
#13 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#14 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#15 g_object_new
from /usr/lib/libgobject-2.0.so.0
#16 oobs_session_get
from /usr/lib/liboobs-1.so.0
#17 nautilus_shares_register_type
from /usr/lib/nautilus/extensions-1.0/libnautilus-gst-shares.so
#18 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#19 g_object_set
from /usr/lib/libgobject-2.0.so.0
#20 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#21 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#22 g_object_new
from /usr/lib/libgobject-2.0.so.0
#23 nautilus_marshal_BOOLEAN__POINTER
#24 nautilus_marshal_BOOLEAN__POINTER
#25 POA_Nautilus_MetafileMonitor__init
#26 POA_Nautilus_MetafileMonitor__init
#27 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#28 ??
#0 __kernel_vsyscall

Comment 1 Teppo Turtiainen 2006-09-07 19:27:16 UTC

Thanks for the bug report. 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?


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