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 510733 - crash in Home Folder:
crash in Home Folder:
Status: RESOLVED DUPLICATE of bug 440988
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-20 04:31 UTC by inforcore
Modified: 2008-01-20 12:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description inforcore 2008-01-20 04:31:46 UTC
What were you doing when the application crashed?



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: Moomex
Icon Theme: OSX

Memory status: size: 76075008 vsize: 76075008 resident: 25378816 share: 16412672 rss: 25378816 rss_rlim: 4294967295
CPU usage: start_time: 1200784395 rtime: 621 utime: 565 stime: 56 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6cac6b0 (LWP 2909)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6cac6b0 (LWP 2909))

  • #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 ---------------------
(file-roller:17663): Gtk-WARNING **: Error parsing gtk-icon-sizes string:
	'panel-menu=24,24
panel=20,20
gtk-button=18,18
gtk-large-toolbar=24,24'
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkTreeView::even-row-color' of type `GdkColor' from rc file value "((GString*) 0x8285b90)" of type `GString'
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...
(bug-buddy:17679): Gtk-WARNING **: Error parsing gtk-icon-sizes string:
	'panel-menu=24,24
panel=20,20
gtk-button=18,18
gtk-large-toolbar=24,24'
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-20 12:09:46 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 ***