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 514514 - crash in Open Folder: Just opening - closing N...
crash in Open Folder: Just opening - closing N...
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-05 11:52 UTC by nemes.sorin
Modified: 2008-02-07 15:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description nemes.sorin 2008-02-05 11:52:07 UTC 
Version: 2.21.90

What were you doing when the application crashed?
Just opening - closing Nautilus windows - Nautilus crash - not as stable (50% maybe) as in Gutsy - But I hope it will be rock stable around Hardy release - and with all features back (if no others ...).



Distribution: Ubuntu 8.04 (hardy)
Gnome Release: 2.21.90 2008-01-29 (Ubuntu)
BugBuddy Version: 2.21.90

System: Linux 2.6.24-5-generic #1 SMP Thu Jan 24 19:45:21 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Aurora-M1
Icon Theme: nuoveXT.2.2

Memory status: size: 141127680 vsize: 141127680 resident: 61693952 share: 23601152 rss: 61693952 rss_rlim: 4294967295
CPU usage: start_time: 1202206750 rtime: 5554 utime: 4203 stime: 1351 cutime:71 cstime: 23 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 0xb6b1b6c0 (LWP 9607)]
[New Thread 0xb377eb90 (LWP 10834)]
[New Thread 0xb1cffb90 (LWP 9629)]
(no debugging symbols found)
0xb7fba410 in __kernel_vsyscall ()

+ Trace 188157

Thread 1 (Thread 0xb6b1b6c0 (LWP 9607))

  • #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 ---------------------
** 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)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
opera: Could not initialize Opera Mail: Not possible to run old Opera version with new Opera mail files.AccountManager Init failed
opera: Could not initialize Opera Mail: Engine Init() failed
**
** 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-07 15:54:13 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 ***