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 356620 - crash in Computer:
crash in Computer:
Status: RESOLVED DUPLICATE of bug 351713
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-09-18 20:15 UTC by Pierre Ossman
Modified: 2006-10-22 10:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Pierre Ossman 2006-09-18 20:15:34 UTC 
What were you doing when the application crashed?



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

Memory status: size: 76349440 vsize: 0 resident: 76349440 share: 0 rss: 15343616 rss_rlim: 0
CPU usage: start_time: 1158610467 rtime: 0 utime: 47 stime: 0 cutime:33 cstime: 0 timeout: 14 it_real_value: 0 frequency: 0

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 -1217537280 (LWP 14116)]
0xb7f60410 in __kernel_vsyscall ()

+ Trace 72689

Thread 1 (Thread -1217537280 (LWP 14116))

  • #0 __kernel_vsyscall
  • #1 g_cclosure_marshal_VOID__ENUM
    at gmarshal.c line 334
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_cclosure_marshal_VOID__ENUM
    at gmarshal.c line 334
  • #5 IA__g_strdup
    at gstrfuncs.c line 90
  • #6 nautilus_directory_async_state_changed
  • #7 nautilus_file_get_uri
  • #8 nautilus_file_get_uri
  • #9 nautilus_file_has_volume
  • #10 nautilus_icon_container_request_update_all
  • #11 fm_directory_view_bump_zoom_level
  • #12 nautilus_file_ref
  • #13 nautilus_file_ref
  • #14 fm_directory_view_bump_zoom_level
  • #15 nautilus_marshal_VOID__OBJECT_OBJECT
  • #16 g_type_class_meta_marshal
    at gclosure.c line 567
  • #17 IA__g_closure_invoke
    at gclosure.c line 490
  • #18 signal_emit_unlocked_R
    at gsignal.c line 2476
  • #19 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #20 IA__g_signal_emit
    at gsignal.c line 2241
  • #21 fm_directory_view_bump_zoom_level
  • #22 g_timeout_dispatch
    at gmain.c line 3422
  • #23 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #24 g_main_context_iterate
    at gmain.c line 2677
  • #25 IA__g_main_loop_run
    at gmain.c line 2881
  • #26 IA__gtk_main
    at gtkmain.c line 1001
  • #27 POA_Nautilus_MetafileMonitor__init
  • #28 __libc_start_main
    at gmarshal.c line 334
  • #29 g_cclosure_marshal_VOID__ENUM
    at gmarshal.c line 334
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2006-10-22 10:51:50 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 351713 ***