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 534211 - crash in Open Folder: I assigned "Emacs" as th...
crash in Open Folder: I assigned "Emacs" as th...
Status: RESOLVED DUPLICATE of bug 510468
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-21 15:58 UTC by kristianrumberg
Modified: 2008-05-21 23:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description kristianrumberg 2008-05-21 15:58:34 UTC
Version: 2.20.0

What were you doing when the application crashed?
I assigned "Emacs" as the default application for a cmake-file CMakeList.txt in Nautilus - then closed emacs and finally nautilus


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: dlg-neu

Memory status: size: 104198144 vsize: 104198144 resident: 38825984 share: 18010112 rss: 38825984 rss_rlim: 4294967295
CPU usage: start_time: 1211378291 rtime: 4303 utime: 4071 stime: 232 cutime:47 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6bee720 (LWP 20925)]
[New Thread 0xb6a5cb90 (LWP 1492)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6bee720 (LWP 20925))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 682
  • #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 IA__g_logv
  • #10 IA__g_log
  • #11 g_assert_warning
    at /build/buildd/glib2.0-2.16.3/glib/gmessages.c line 573
  • #12 ??
  • #13 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (7 sec old) ---------------------
Warning: more than one line!
Warning: more than one line!
Warning: more than one line!
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2a0001e (Archive Ma)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(gnome-terminal:16478): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
Warning: Lisp directory `/usr/local/share/emacs/site-lisp' does not exist.
kbuildsycoca running...
Reusing existing ksycoca
(nautilus:20925): Gtk-CRITICAL **: gtk_tree_model_sort_real_unref_node: assertion `elt->ref_count > 0' failed
** ERROR **: file fm-tree-model.c: line 1531 (fm_tree_model_unref_node): assertion failed: (node->ref_count > 0)
aborting...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-05-21 23:28:50 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 510468 ***