Bug 494458 – crash in Open Folder:

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 494458 - crash in Open Folder:


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 440988

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.18.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-11-07 05:06 UTC by kuttachar
Modified:	2007-11-08 01:36 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description kuttachar 2007-11-07 05:06:59 UTC

Version: 2.18.3

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 143507456 vsize: 143507456 resident: 42741760 share: 25710592 rss: 42741760 rss_rlim: 4294967295
CPU usage: start_time: 1194408460 rtime: 488 utime: 436 stime: 52 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 -1208404256 (LWP 3393)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 175948

Thread 1 (Thread -1208404256 (LWP 3393))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /lib/libglib-2.0.so.0
#8 g_log
from /lib/libglib-2.0.so.0
#9 g_assert_warning
from /lib/libglib-2.0.so.0
#10 ??
from /usr/lib/libgtk-x11-2.0.so.0
#11 ??
#12 ??
#13 g_sequence_sort_changed_iter
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_list_store_set_valist
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_list_store_set
from /usr/lib/libgtk-x11-2.0.so.0
#17 ??
#18 ??
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
from /lib/libglib-2.0.so.0
#24 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#25 ??
from /lib/libglib-2.0.so.0
#26 g_main_loop_run
from /lib/libglib-2.0.so.0
#27 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#28 main
#0 __kernel_vsyscall



----------- .xsession-errors (2665 sec old) ---------------------
[00000371] esd audio output error: write failed (Bad file descriptor)
[00000371] esd audio output error: write failed (Bad file descriptor)
[00000371] esd audio output error: write failed (Bad file descriptor)
[00000371] esd audio output error: write failed (Bad file descriptor)
[00000371] esd audio output error: write failed (Bad file descriptor)
[00000371] esd audio output error: write failed (Bad file descriptor)
[00000371] esd audio output error: write failed (Bad file descriptor)
[00000371] esd audio output error: write failed (Bad file descriptor)
[00000371] esd audio output error: write failed (Bad file descriptor)
[00000371] esd audio output error: write failed (Bad file descriptor)
[00000371] esd audio output error: write failed (Bad file descriptor)
[00000371] esd audio output error: write failed (Bad file descriptor)
[00000371] esd audio output error: write failed (Bad file descriptor)
[00000371] esd audio output error: write faile
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 André Klapper 2007-11-08 01:36:24 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 440988 ***