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 556363 - crash in Open Folder: Closing the folder windo...
crash in Open Folder: Closing the folder windo...
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-10-15 05:25 UTC by alex
Modified: 2008-10-18 14:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description alex 2008-10-15 05:25:29 UTC
Version: 2.20.0

What were you doing when the application crashed?
Closing the folder window.


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

System: Linux 2.6.26-1-686 #1 SMP Wed Sep 10 16:46:13 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 93655040 vsize: 93655040 resident: 32546816 share: 16715776 rss: 32546816 rss_rlim: 4294967295
CPU usage: start_time: 1224034020 rtime: 872 utime: 813 stime: 59 cutime:13 cstime: 2 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 0xb6aec710 (LWP 4323)]
[New Thread 0xb62ecb90 (LWP 13192)]
(no debugging symbols found)
0xb7f56424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6aec710 (LWP 4323))

  • #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 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 __kernel_vsyscall
  • #8 raise
    from /lib/i686/cmov/libc.so.6
  • #9 abort
    from /lib/i686/cmov/libc.so.6
  • #10 g_assertion_message
    from /usr/lib/libglib-2.0.so.0
  • #11 g_assertion_message_expr
    from /usr/lib/libglib-2.0.so.0
  • #12 ??
  • #13 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e0001e (Archive Ma)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
warning: could not initiate dbus
current dist not found in meta-release file
could not send the dbus Inhibit signal: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security poli
**
** ERROR:(fm-tree-model.c:1527):fm_tree_model_unref_node: assertion failed: (parent->dummy_child_ref_count > 0)
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-10-18 14:33:55 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 ***