Bug 505094 – crash in Open Folder: Right-click with mouse o...

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 505094 - crash in Open Folder: Right-click with mouse o...


Summary:	crash in Open Folder: Right-click with mouse o...


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-12-22 19:34 UTC by cordawyn
Modified:	2007-12-23 18:36 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description cordawyn 2007-12-22 19:34:40 UTC

Version: 2.18.3

What were you doing when the application crashed?
Right-click with mouse on a file (or folder), choose "Properties". Nautilus always crashes.


Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-k7 #1 SMP Mon Nov 12 09:12:50 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glider
Icon Theme: Tango

Memory status: size: 112562176 vsize: 112562176 resident: 38371328 share: 17690624 rss: 38371328 rss_rlim: 4294967295
CPU usage: start_time: 1198343273 rtime: 3267 utime: 3042 stime: 225 cutime:3895 cstime: 303 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6d796b0 (LWP 3648)]
[New Thread 0xb14d4b90 (LWP 8619)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 182678

Thread 1 (Thread 0xb6d796b0 (LWP 3648))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 __kernel_vsyscall
#7 raise
from /lib/i686/cmov/libc.so.6
#8 abort
from /lib/i686/cmov/libc.so.6
#9 g_logv
from /usr/lib/libglib-2.0.so.0
#10 g_log
from /usr/lib/libglib-2.0.so.0
#11 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#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 ??
from /usr/lib/libgtk-x11-2.0.so.0
#17 ??
from /usr/lib/libgtk-x11-2.0.so.0
#18 ??
from /usr/lib/libgtk-x11-2.0.so.0
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??
#32 ??
#33 ??
#34 ??
#35 ??
#36 ??
#37 ??
#38 ??
#39 ??
#40 ??
#41 ??
from /usr/lib/libgtk-x11-2.0.so.0
#42 ??
#43 ??
#44 ??
#45 ??
#46 ??
#47 ??
#48 ??
#49 ??
from /usr/lib/libgtk-x11-2.0.so.0
#50 ??
#51 ??
#52 ??
#53 ??
#54 ??
#55 ??
#56 g_sequence_sort_changed_iter
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
WARN: error in ioctl CDROMREADTOCHDR: Input/output error
CDROMREADTOCHDR: Input/output error
WARN: error in ioctl CDROMREADTOCHDR: Input/output error
xine-lib: error: The xine engine failed to start.: No demuxer found - stream format not recognised.
CDROMREADTOCHDR: Input/output error
WARN: error in ioctl CDROMREADTOCHDR: Input/output error
CDROMREADTOCHDR: Input/output error
WARN: error in ioctl CDROMREADTOCHDR: Input/output error
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...
--------------------------------------------------

Comment 1 Cosimo Cecchi 2007-12-23 18:36:58 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 ***