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 389684 - crash in Computer:
crash in Computer:
Status: RESOLVED DUPLICATE of bug 374002
Product: nautilus
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-26 09:54 UTC by lutfi.arab
Modified: 2007-06-22 22:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description lutfi.arab 2006-12-26 09:54:51 UTC 
Version: 2.16.2

What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled
----------- .xsession-errors (2918 sec old) ---------------------
** (nautilus:2186): WARNING **: Got load_underway report from unknown view
** (nautilus:2186): WARNING **: Got load_underway report from unknown view
** (nautilus:2186): WARNING **: Got load_underway report from unknown view
** (nautilus:2186): WARNING **: Got load_underway report from unknown view
** (nautilus:2186): WARNING **: Got load_underway report from unknown view
** (nautilus:2186): WARNING **: Got load_underway report from unknown view
** (nautilus:2186): WARNING **: Got load_underway report from unknown view
...Too much output, ignoring rest...
--------------------------------------------------

Memory status: size: 219779072 vsize: 0 resident: 219779072 share: 0 rss: 49213440 rss_rlim: 0
CPU usage: start_time: 1166604486 rtime: 0 utime: 124635 stime: 0 cutime:116625 cstime: 0 timeout: 8010 it_real_value: 0 frequency: 560

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 -1208349952 (LWP 2186)]
(no debugging symbols found)
0x00a85402 in __kernel_vsyscall ()

+ Trace 97034

Thread 1 (Thread -1208349952 (LWP 2186))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gtk_ui_manager_remove_ui
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 nautilus_marshal_BOOLEAN__POINTER
  • #6 fm_directory_view_bump_zoom_level
  • #7 fm_directory_view_bump_zoom_level
  • #8 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #9 g_value_set_static_boxed
    from /lib/libgobject-2.0.so.0
  • #10 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #11 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #14 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_widget_hide
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #17 fm_directory_view_bump_zoom_level
  • #18 gtk_clipboard_get_owner
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 gtk_marshal_BOOLEAN__VOID
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #21 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #23 g_signal_emit_by_name
    from /lib/libgobject-2.0.so.0
  • #24 gtk_target_list_unref
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 gtk_target_list_unref
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 gtk_marshal_BOOLEAN__VOID
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 g_value_set_static_boxed
    from /lib/libgobject-2.0.so.0
  • #28 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #29 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #30 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #31 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #32 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 gdk_add_client_message_filter
    from /usr/lib/libgdk-x11-2.0.so.0
  • #35 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #36 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #37 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #38 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 POA_Nautilus_MetafileMonitor__init
  • #40 __libc_start_main
    from /lib/libc.so.6
  • #41 g_cclosure_marshal_VOID__ENUM
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2007-01-03 20:20:19 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.
Could you please install some debugging packages [1], start nautilus as normal,
and reproduce the crash, if possible?
Once bug-buddy pops up, you can find the stacktrace in the "details", now
containing way more information. Please copy that stacktrace and paste it as a
comment here. Thanks in advance!

[1] debugging packages for nautilus, glib, gtk, pango, gnome-vfs and
libgnome(ui).
More details can be found here:
http://live.gnome.org/GettingTraces/DistroSpecificInstructions







Comment 2


André Klapper





          2007-06-22 22:07:37 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 374002 ***