Bug 494581 – crash in Open Folder: clicked on a file inside...

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 494581 - crash in Open Folder: clicked on a file inside...


Summary:	crash in Open Folder: clicked on a file inside...


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 13:07 UTC by debian
Modified:	2007-11-07 20:29 UTC

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

Description debian 2007-11-07 13:07:53 UTC

Version: 2.18.3

What were you doing when the application crashed?
clicked on a file inside a folder on a microsd card


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-2-486 #1 Wed Jul 11 03:17:09 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 108486656 vsize: 108486656 resident: 23339008 share: 11689984 rss: 23339008 rss_rlim: 4294967295
CPU usage: start_time: 1194304475 rtime: 14613 utime: 12749 stime: 1864 cutime:1 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6cd4b40 (LWP 2310)]
0xb75eabf1 in waitpid () from /lib/libpthread.so.0

+ Trace 176033

Thread 1 (Thread 0xb6cd4b40 (LWP 2310))

#0 waitpid
from /lib/libpthread.so.0
#1 libgnomeui_segv_handle
at gnome-ui-init.c line 872
#2 <signal handler called>
#3 raise
from /lib/libc.so.6
#4 abort
from /lib/libc.so.6
#5 g_logv
from /usr/lib/libglib-2.0.so.0
#6 g_log
from /usr/lib/libglib-2.0.so.0
#7 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#8 ??
from /usr/lib/libgtk-x11-2.0.so.0
#9 ??
from /usr/lib/libgtk-x11-2.0.so.0
#10 ??
from /usr/lib/libgtk-x11-2.0.so.0
#11 ??
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 ??
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
#16 ??
#17 ??
#18 ??
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 node_find_closest
at gsequence.c line 1136
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
Gtk-ERROR **: file /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c: line 1677 (gtk_list_store_compare_func): assertion failed: (VALID_ITER (&iter_b, list_store))
aborting...
/usr/share/themes/Glossy/gtk-2.0/gtkrc:62: error: unexpected identifier `colorize_scrollbar', expected character `}'
warning: .dynamic section for "/usr/lib/libpcre.so.3" is not at the expected address (wrong library or version mismatch?)
--------------------------------------------------

Comment 1 André Klapper 2007-11-07 20:29:04 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 ***