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 507282 - crash in Open Folder: Open a desktop launcher'...
crash in Open Folder: Open a desktop launcher'...
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-04 15:57 UTC by rafaelbco
Modified: 2008-01-05 18:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description rafaelbco 2008-01-04 15:57:06 UTC
Version: 2.18.3

What were you doing when the application crashed?
Open a desktop launcher's properties and clicked in the icon, to select the icon.


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

Memory status: size: 72863744 vsize: 72863744 resident: 24711168 share: 15237120 rss: 24711168 rss_rlim: 4294967295
CPU usage: start_time: 1199460869 rtime: 1090 utime: 1006 stime: 84 cutime:0 cstime: 1 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 0xb6dac6b0 (LWP 3586)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6dac6b0 (LWP 3586))

  • #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 ---------------------
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
Window manager warning: last_user_time (3076482096) is greater than comparison timestamp (1166308358).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE
Window manager warning: 0x2600003 (Network Se) appears to be one of the offending windows with a timestamp of 3076482096.  Working around...
Window manager warning: last_user_time (3075540016) is greater than comparison timestamp (1166394716).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE
Window manager warning: 0x1e01659 (# Terminal) appears to be one of the offending windows with a timestamp of 3075540016.  Working around...

(gnome-terminal:7011): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
** Message: drive = 0
** Message: volume = 0
** 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 André Klapper 2008-01-05 18:48:46 UTC
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 ***