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 531296 - crash in Home Folder: I close it and got this ...
crash in Home Folder: I close it and got this ...
Status: RESOLVED DUPLICATE of bug 417962
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-03 22:30 UTC by marcelolaia
Modified: 2008-05-03 22:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description marcelolaia 2008-05-03 22:30:21 UTC 
What were you doing when the application crashed?
I close it and got this error


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: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 97841152 vsize: 97841152 resident: 35553280 share: 17682432 rss: 35553280 rss_rlim: 4294967295
CPU usage: start_time: 1209823207 rtime: 1982 utime: 1816 stime: 166 cutime:2634 cstime: 328 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6bb7720 (LWP 6742)]
[New Thread 0xb5f3bb90 (LWP 10731)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 196803

Thread 1 (Thread 0xb6bb7720 (LWP 6742))

  • #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 fm_tree_model_unref_node
    at fm-tree-model.c line 1527
  • #13 gtk_tree_model_unref_node
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
    from /usr/lib/libgobject-2.0.so.0
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
Aviso do gerenciador de janelas: last_user_time (3076215856) is greater than comparison timestamp (2956517000).  This most likely represents a buggy client sending inaccurate timestamps in messages su
Aviso do gerenciador de janelas: 0x3400081 (Synaptic) appears to be one of the offending windows with a timestamp of 3076215856.  Working around...
Cutting log (size: 102094, max: 100000)
** ERROR **: file fm-tree-model.c: line 1527 (fm_tree_model_unref_node): assertion failed: (parent->dummy_child_ref_count > 0)
aborting...
--------------------------------------------------
Comment 1 A. Walton 2008-05-03 22:35:29 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 417962 ***