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 546614 - crash in Computer: I was entering in a hidd...
crash in Computer: I was entering in a hidd...
Status: RESOLVED DUPLICATE of bug 512040
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-08-06 15:59 UTC by pahcixam
Modified: 2008-08-07 08:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description pahcixam 2008-08-06 15:59:01 UTC
Version: 2.20.0

What were you doing when the application crashed?
I was entering in a hidden folder in my personnel directory.


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-amd64 #1 SMP Mon Jul 14 11:05:23 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks Wine Dark
Icon Theme: gnome-wine

Memory status: size: 541450240 vsize: 541450240 resident: 46624768 share: 18247680 rss: 46624768 rss_rlim: 18446744073709551615
CPU usage: start_time: 1218035402 rtime: 739 utime: 681 stime: 58 cutime:0 cstime: 0 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 0x7f682db1d780 (LWP 3971)]
(no debugging symbols found)
0x00007f6828b2dedf in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x7f682db1d780 (LWP 3971))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_assertion_message
    from /usr/lib/libglib-2.0.so.0
  • #8 g_assertion_message_expr
    from /usr/lib/libglib-2.0.so.0
  • #9 ??
  • #10 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 ??
    from /usr/lib/libgtk-x11-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 gtk_tree_row_reference_free
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gtk_tree_view_set_cursor_on_cell
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 ??
  • #20 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #21 ??
    from /usr/lib/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #23 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 ??
  • #25 __libc_start_main
    from /lib/libc.so.6
  • #26 ??
  • #27 ??
  • #28 ??
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors ---------------------
(gnome-appearance-properties:6321): appearance-properties-WARNING **: Unknown Tag: comment
(gnome-appearance-properties:6395): appearance-properties-WARNING **: Unknown Tag: comment
(gnome-appearance-properties:6395): appearance-properties-WARNING **: Unknown Tag: comment
** (gnome-settings-daemon:3948): WARNING **: Failed to open file '/etc/gnome/config/General.ad': Aucun fichier ou répertoire de ce type
** (gnome-settings-daemon:3948): WARNING **: Failed to open file '/etc/gnome/config/General.ad': Aucun fichier ou répertoire de ce type
**
** ERROR:(fm-tree-model.c:1531):fm_tree_model_unref_node: assertion failed: (node->ref_count > 0)
--------------------------------------------------
Comment 1 A. Walton 2008-08-07 08:11:01 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 ***