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 515971 - crash in Open Folder: as usually after 2.21.6 ...
crash in Open Folder: as usually after 2.21.6 ...
Status: RESOLVED DUPLICATE of bug 512040
Product: nautilus
Classification: Core
Component: general
2.21.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-12 10:41 UTC by nemes.sorin
Modified: 2008-02-12 18:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description nemes.sorin 2008-02-12 10:41:37 UTC
Version: 2.21.91

What were you doing when the application crashed?
as usually after 2.21.6 Nautilus just crash on ...whatever you want ..now I just navigate my folders. I was closed the single opened folder. Then crash. I hope this will be solved until Hardy Heron launch.  I'll change Nautilus with PCMAN FM (it is pretty stable and in some aspects ..superior to Nautilus )


Distribution: Ubuntu 8.04 (hardy)
Gnome Release: 2.21.91 2008-02-12 (Ubuntu)
BugBuddy Version: 2.21.90

System: Linux 2.6.24-7-generic #1 SMP Thu Feb 7 01:29:58 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Aurora-looks
Icon Theme: nuoveXT.2.2

Memory status: size: 145354752 vsize: 145354752 resident: 54276096 share: 18845696 rss: 54276096 rss_rlim: 4294967295
CPU usage: start_time: 1202808214 rtime: 3303 utime: 2418 stime: 885 cutime:79 cstime: 12 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/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6a486c0 (LWP 5838)]
(no debugging symbols found)
0xb7eea410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6a486c0 (LWP 5838))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/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/tls/i686/cmov/libc.so.6
  • #8 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #9 g_assertion_message
    from /usr/lib/libglib-2.0.so.0
  • #10 g_assertion_message_expr
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
  • #12 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (6 sec old) ---------------------
(synaptic:7023): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
(synaptic:7023): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed
(synaptic:7023): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed
(synaptic:7023): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed
(synaptic:7023): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed
Window manager warning: Log level 16: Could not get attrs
Window manager warning: Log level 16: Could not get attrs
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0xc03491 (tarmure - ); these messages lack timestamps and therefore suck.
**
** ERROR:(fm-tree-model.c:1563):fm_tree_model_unref_node: assertion failed: (parent->dummy_child_ref_count > 0)
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-02-12 18:04:06 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 512040 ***