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 506716 - crash in File Browser: Estaba cambiando el icon...
crash in File Browser: Estaba cambiando el icon...
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-01 18:01 UTC by s3b4.deb
Modified: 2008-01-01 18:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description s3b4.deb 2008-01-01 18:01:17 UTC 
Version: 2.18.3

What were you doing when the application crashed?
Estaba cambiando el icono 


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: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: skymind

Memory status: size: 74457088 vsize: 74457088 resident: 23232512 share: 16224256 rss: 23232512 rss_rlim: 4294967295
CPU usage: start_time: 1199208608 rtime: 301 utime: 274 stime: 27 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 0xb6d6a6b0 (LWP 3503)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 183719

Thread 1 (Thread 0xb6d6a6b0 (LWP 3503))

  • #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 ---------------------
/usr/share/themes/ClearlooksClassic/gtk-2.0/gtkrc:61: error: unexpected identifier `colorize_scrollbar', expected character `}'
/usr/share/themes/ClearlooksClassic/gtk-2.0/gtkrc:61: error: unexpected identifier `colorize_scrollbar', expected character `}'
(gnome-appearance-properties:3747): Gtk-WARNING **: Imposible encontrar el motor de temas en la ruta al _modulo: «lighthouseblue»,
(gnome-appearance-properties:3747): Gtk-WARNING **: Theme directory scalable/apps/24 of theme OSX_Iconset has no size field
(gnome-appearance-properties:3747): Gtk-WARNING **: Theme directory  scalable/stock/128 of theme OSX_Iconset has no size field
** 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 Christian Kirbach 2008-01-01 18:23:18 UTC 
please update your nautilus version

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 440988 ***