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 508331 - crash in Open Folder: I was trying to set an i...
crash in Open Folder: I was trying to set an i...
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-09 16:46 UTC by artistar
Modified: 2008-01-10 01:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description artistar 2008-01-09 16:46:05 UTC
Version: 2.18.3

What were you doing when the application crashed?
I was trying to set an icon for a folder using Right click - Properties.
Fix this bug soon because it's annoying and am thinking of moving to some other desktop environment - there's no excuse for crashing the whole environment on such simple task!


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: Clearlooks
Icon Theme: gnome

Memory status: size: 68100096 vsize: 68100096 resident: 21245952 share: 14254080 rss: 21245952 rss_rlim: 4294967295
CPU usage: start_time: 1199904170 rtime: 87 utime: 82 stime: 5 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 0xb6d696b0 (LWP 3828)]
[New Thread 0xb61d3b90 (LWP 3920)]
[New Thread 0xb59d2b90 (LWP 3919)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6d696b0 (LWP 3828))

  • #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 ---------------------
Initializing gnome-mount extension
xrdb:  "*Label.background" on line 220 overrides entry on line 150
xrdb:  "*Text.background" on line 226 overrides entry on line 191
xrdb:  "*Label.foreground" on line 232 overrides entry on line 151
xrdb:  "*Text.foreground" on line 238 overrides entry on line 192
Window manager warning: Log level 8: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(gnome-panel:3826): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
** Message: drive = 0
** Message: volume = 0
Window manager warning: last_user_time (3075949616) is greater than comparison timestamp (1608306851).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE
Window manager warning: 0x2000003 (Login Wind) appears to be one of the offending windows with a timestamp of 3075949616.  Working around...
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-10 01:15:57 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 ***