Bug 508118 – crash in Open Folder: Opened "Select Custom Ic...

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 508118 - crash in Open Folder: Opened "Select Custom Ic...


Summary:	crash in Open Folder: Opened "Select Custom Ic...


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:	2008-01-08 18:42 UTC by collusion.inc
Modified:	2008-01-09 08:45 UTC

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

Description collusion.inc 2008-01-08 18:42:08 UTC

Version: 2.18.3

What were you doing when the application crashed?
Opened "Select Custom Icon" file browser dialog. No files showing, none selected.


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

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 72736768 vsize: 72736768 resident: 23924736 share: 16113664 rss: 23924736 rss_rlim: 4294967295
CPU usage: start_time: 1199809123 rtime: 4131 utime: 3826 stime: 305 cutime:21 cstime: 5 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 0xb6dfa6b0 (LWP 3837)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 184560

Thread 1 (Thread 0xb6dfa6b0 (LWP 3837))

#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 ??
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
(nautilus:3837): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sahowarth\s.gnome2\snautilus-scripts\sRoot' to action group 'ScriptsGroup'
(nautilus:3837): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sahowarth\s.gnome2\snautilus-scripts\sRoot' to action group 'ScriptsGroup'
(nautilus:3837): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sahowarth\s.gnome2\snautilus-scripts\sUtils' to action group 'ScriptsGroup'
(nautilus:3837): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sahowarth\s.gnome2\snautilus-scripts\sUtils' to action group 'ScriptsGroup'
** Message: drive = 0
** Message: volume = 0
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4c specified for 0x140721d ().
** 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...
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-01-09 08:45:34 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 ***