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 510580 - crash in File Browser: changing an icon from th...
crash in File Browser: changing an icon from th...
Status: RESOLVED DUPLICATE of bug 440988
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-19 10:59 UTC by rricardoortega
Modified: 2008-01-20 12:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description rricardoortega 2008-01-19 10:59:24 UTC 
Version: 2.18.3

What were you doing when the application crashed?
changing an icon from the desktop.


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

System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gorilla
Icon Theme: Gorilla

Memory status: size: 70868992 vsize: 70868992 resident: 21184512 share: 15392768 rss: 21184512 rss_rlim: 4294967295
CPU usage: start_time: 1200738759 rtime: 143 utime: 121 stime: 22 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 0xb6e116b0 (LWP 3634)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 185940

Thread 1 (Thread 0xb6e116b0 (LWP 3634))

  • #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 ---------------------
** Message: ButtonPress
** Message: emitting signal
** Message: ButtonPress signal received
** Message: ButtonPress
** Message: DestroyStream reason 2
** Message: URLNotify URL 'http://images.apple.com/support/home/es-es/videos/shuffle.mov' reason 2
** Message: totemPlugin dtor [0xafeda58]
** Message: NP_Shutdown
Advertencia del gestor de ventanas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2800058 (technical_)
Advertencia del gestor de ventanas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Advertencia del gestor de ventanas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2800058 (technical_)
Advertencia del gestor de ventanas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
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-20 12:03:47 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 ***