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 363338 - crash in Computer: dont know why nautilius ...
crash in Computer: dont know why nautilius ...
Status: RESOLVED DUPLICATE of bug 352592
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-19 06:53 UTC by nemes.sorin
Modified: 2006-10-19 07:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description nemes.sorin 2006-10-19 06:53:35 UTC 
What were you doing when the application crashed?
dont know why nautilius die just when ..I navigate on my folders (my home folder not XP instalation folders  [ wich are NTFS and Fat32] ) .. this time I was on my home folder -> cut & paste some pdf files  



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 128364544 vsize: 0 resident: 128364544 share: 0 rss: 34594816 rss_rlim: 0
CPU usage: start_time: 1161240211 rtime: 0 utime: 1240 stime: 0 cutime:1140 cstime: 0 timeout: 100 it_real_value: 0 frequency: 151

Backtrace was generated from '/usr/bin/nautilus'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1226848592 (LWP 5361)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 77112

Thread 1 (Thread -1226848592 (LWP 5361))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 IA__g_logv
  • #8 IA__g_log
  • #9 IA__g_assert_warning
  • #10 fm_icon_view_remove_file
    at fm-icon-view.c line 503
  • #11 nautilus_marshal_VOID__OBJECT_OBJECT
    at nautilus-marshal-guts.c line 469
  • #12 g_type_class_meta_marshal
    at gclosure.c line 567
  • #13 IA__g_closure_invoke
    at gclosure.c line 490
  • #14 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #15 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #16 IA__g_signal_emit
    at gsignal.c line 2243
  • #17 display_pending_callback
    at fm-directory-view.c line 2789
  • #18 g_timeout_dispatch
    at gmain.c line 3422
  • #19 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #20 g_main_context_iterate
    at gmain.c line 2677
  • #21 IA__g_main_loop_run
    at gmain.c line 2881
  • #22 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 main
    at nautilus-main.c line 372
  • #24 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #25 _start
  • #0 __kernel_vsyscall 






Comment 1


Karsten Bräckelmann





          2006-10-19 07:08:42 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 352592 ***