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 435026 - crash in Home Folder: root (/) -ordner im date...
crash in Home Folder: root (/) -ordner im date...
Status: RESOLVED DUPLICATE of bug 425157
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 443314 448668 450674 450857 451054 460835 478033 481358 484470 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-05-01 21:45 UTC by nofragemo
Modified: 2007-10-08 10:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description nofragemo 2007-05-01 21:45:29 UTC 
What were you doing when the application crashed?
root (/) -ordner im datei-browser versucht zu öffnen


Distribution: Fedora release 6.93 (Rawhide)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.5.fc7xen #1 SMP Thu Mar 22 13:51:38 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299905
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 79900672 vsize: 79900672 resident: 28827648 share: 15282176 rss: 28827648 rss_rlim: 4294967295
CPU usage: start_time: 1178061320 rtime: 6139 utime: 2520 stime: 3619 cutime:0 cstime: 1 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208292592 (LWP 3625)]
(no debugging symbols found)
0x00b9f402 in __kernel_vsyscall ()

+ Trace 131766

Thread 1 (Thread -1208292592 (LWP 3625))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/i686/nosegneg/libc.so.6
  • #6 abort
    from /lib/i686/nosegneg/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 nautilus_connect_background_to_file_metadata
  • #11 ??
  • #12 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #13 ??
    from /lib/libgobject-2.0.so.0
  • #14 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #15 ??
    from /lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #18 fm_directory_view_begin_loading
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
    from /lib/libglib-2.0.so.0
  • #23 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #24 ??
    from /lib/libglib-2.0.so.0
  • #25 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #26 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (13 sec old) ---------------------
** (nautilus:3625): WARNING **: Throbber fallback animation not found either
(nautilus:3625): Eel-CRITICAL **: wrap_table_get_num_fitting: assertion `max_child_size > 0' failed
(nautilus:3625): Eel-CRITICAL **: wrap_table_get_num_fitting: assertion `max_child_size > 0' failed
(nautilus:3625): Eel-CRITICAL **: wrap_table_get_num_fitting: assertion `max_child_size > 0' failed
(nautilus:3625): Eel-CRITICAL **: wrap_table_get_num_fitting: assertion `max_child_size > 0' failed
** (nautilus:3625): WARNING **: destroyed file still being monitored
** ERROR **: file nautilus-directory-background.c: line 621 (nautilus_connect_background_to_file_metadata): assertion failed: (NAUTILUS_IS_FILE (old_file))
aborting...
--------------------------------------------------
Comment 1 palfrey 2007-05-02 11:30:41 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!
Comment 2 palfrey 2007-06-02 23:44:25 UTC 
*** Bug 443314 has been marked as a duplicate of this bug. ***
Comment 3 Cragin 2007-06-03 00:04:49 UTC 
Crap! I can't reproduce it.
Comment 4 André Klapper 2007-06-24 19:32:59 UTC 
*** Bug 448668 has been marked as a duplicate of this bug. ***
Comment 5 André Klapper 2007-06-24 19:33:09 UTC 
*** Bug 450674 has been marked as a duplicate of this bug. ***
Comment 6 Pedro Villavicencio 2007-06-26 00:18:20 UTC 
*** Bug 451054 has been marked as a duplicate of this bug. ***
Comment 7 Pedro Villavicencio 2007-06-26 00:33:26 UTC 
*** Bug 450857 has been marked as a duplicate of this bug. ***
Comment 8 palfrey 2007-07-04 09:07:53 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 425157 ***
Comment 9 Pedro Villavicencio 2007-07-27 16:18:52 UTC 
*** Bug 460835 has been marked as a duplicate of this bug. ***
Comment 10 Cosimo Cecchi 2007-09-18 19:29:49 UTC 
*** Bug 478033 has been marked as a duplicate of this bug. ***
Comment 11 Cosimo Cecchi 2007-09-28 19:34:45 UTC 
*** Bug 481358 has been marked as a duplicate of this bug. ***
Comment 12 Cosimo Cecchi 2007-10-08 10:51:16 UTC 
*** Bug 484470 has been marked as a duplicate of this bug. ***