Bug 115342 – Segfault on nautilus -q

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 115342 - Segfault on nautilus -q


Summary:	Segfault on nautilus -q


Status:	RESOLVED DUPLICATE of bug 87414

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.2.x
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2003-06-17 09:50 UTC by Philipp Meier
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	2.1/2.2

Description Philipp Meier 2003-06-17 09:51:20 UTC

Package: nautilus
Severity: major
Version: 2.2.4
Synopsis: Segfault on nautilus -q
Bugzilla-Product: nautilus
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.1)

Description:
Description of Problem:

Called nautilus -q -> Segfault


Steps to reproduce the problem:
1. In shell (nautilus is running) : nautilus -q

Actual Results:
Segfault

Expected Results:
Nautilus quits

How often does this happen?
Frequently

Additional Information:




Debugging Information:

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

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New
Thread 16384 (LWP 1319)]
[New Thread 32769 (LWP 1343)]
[New Thread 16386 (LWP 1344)]
[New Thread 32771 (LWP 1345)]
[New Thread 49156 (LWP 1346)]
[New Thread 65541 (LWP 1347)]
[New Thread 81926 (LWP 1348)]
[New Thread 98311 (LWP 1349)]
[New Thread 114696 (LWP 1350)]
[New Thread 131081 (LWP 1351)]
[New Thread 147466 (LWP 1352)]
[New Thread 163851 (LWP 1353)]
0x40b56af9 in wait4 () from /lib/libc.so.6

+ Trace 37880

Thread 1 (Thread 16384 (LWP 1319))

#0 wait4
from /lib/libc.so.6
#1 sys_sigabbrev
from /lib/libc.so.6
#2 ??
#3 waitpid
from /lib/libc.so.6
#4 waitpid
from /lib/libpthread.so.0
#5 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#6 __pthread_sighandler
from /lib/libpthread.so.0
#7 <signal handler called>
#8 kill
from /lib/libc.so.6
#9 pthread_kill
from /lib/libpthread.so.0
#10 raise
from /lib/libpthread.so.0
#11 abort
from /lib/libc.so.6
#12 g_logv
from /usr/lib/libglib-2.0.so.0
#13 g_log
from /usr/lib/libglib-2.0.so.0
#14 _gnome_vfs_async_job_map_get_job
from /usr/lib/libgnomevfs-2.so.0
#15 gnome_vfs_async_cancel
from /usr/lib/libgnomevfs-2.so.0
#16 nautilus_trash_directory_get_type
from /usr/lib/libnautilus-private.so.2
#17 eel_g_hash_table_safe_for_each
from /usr/lib/libeel-2.so.2
#18 nautilus_trash_directory_finish_initializing
from /usr/lib/libnautilus-private.so.2
#19 g_object_class_list_properties
from /usr/lib/libgobject-2.0.so.0
#20 nautilus_directory_unref
from /usr/lib/libnautilus-private.so.2
#21 nautilus_trash_monitor_get_type
from /usr/lib/libnautilus-private.so.2
#22 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#23 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#24 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#28 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#29 g_object_class_list_properties
from /usr/lib/libgobject-2.0.so.0
#30 nautilus_trash_monitor_get_type
from /usr/lib/libnautilus-private.so.2
#31 eel_debug_shut_down
from /usr/lib/libeel-2.so.2
#32 main
#33 __libc_start_main
from /lib/libc.so.6
#34 _start
#0 wait4
from /lib/libc.so.6





------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-06-17 05:51 -------

The original reporter (meier@meisterbohne.de) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.

Comment 1 Elijah Newren 2003-06-17 21:17:22 UTC

Appears to be a unique stack trace, according to the
simple-dup-finder.  Setting version->2.2.x, marking priority->high &
severity->critical (it's a crasher), adding GNOMEVER2.2 keyword, and
marking as new.

Should this be moved to gnome-vfs?

Comment 2 Kjartan Maraas 2003-07-01 19:27:16 UTC

Cannot reproduce this here. Can you still see it? Can we get some more
details about your trash folder since that seems to be involved in the
backtrace...

Comment 3 Kjartan Maraas 2003-07-02 14:50:29 UTC

Duplicate

Comment 4 Kjartan Maraas 2003-07-02 14:50:48 UTC


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