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 478033 - crash in Computer:
crash in Computer:
Status: RESOLVED DUPLICATE of bug 435026
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-18 13:23 UTC by jivagoalves
Modified: 2007-09-18 19:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jivagoalves 2007-09-18 13:23:29 UTC
Version: 2.18.3

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: MacOS-X
Icon Theme: Aero

Memory status: size: 120049664 vsize: 120049664 resident: 36261888 share: 23248896 rss: 36261888 rss_rlim: 4294967295
CPU usage: start_time: 1190119763 rtime: 1989 utime: 1732 stime: 257 cutime:373 cstime: 96 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208199456 (LWP 7439)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208199456 (LWP 7439))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/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 (10 sec old) ---------------------
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
core: bindWindow(): XGetWindowAttributes() returned non-success.Window: 0x3C01491
core: bindWindow(): XGetWindowAttributes() returned non-success.Window: 0x3C018A0
closing
closing
closing
(nautilus:7439): Eel-WARNING **: No extension, not implemented yet
** (nautilus:7439): 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 Cosimo Cecchi 2007-09-18 19:29:49 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 435026 ***