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 362705 - crash in Computer:
crash in Computer:
Status: RESOLVED DUPLICATE of bug 350975
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-16 20:35 UTC by jdodd
Modified: 2006-10-17 08:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description jdodd 2006-10-16 20:35:10 UTC
What were you doing when the application crashed?



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

Memory status: size: 98496512 vsize: 0 resident: 98496512 share: 0 rss: 31899648 rss_rlim: 0
CPU usage: start_time: 1161008937 rtime: 0 utime: 2677 stime: 0 cutime:2488 cstime: 0 timeout: 189 it_real_value: 0 frequency: 0

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

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

Thread 1 (Thread -1226684752 (LWP 5641))

  • #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 g_str_hash
    from /usr/lib/libglib-2.0.so.0
  • #5 g_hash_table_lookup
    from /usr/lib/libglib-2.0.so.0
  • #6 nautilus_file_get_uri
  • #7 nautilus_file_get_uri
  • #8 nautilus_directory_async_state_changed
  • #9 nautilus_file_get_uri
  • #10 nautilus_file_unref
  • #11 gnome_vfs_job_get_count
    from /usr/lib/libgnomevfs-2.so.0
  • #12 ??
  • #13 ??
  • #0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-10-17 08:49: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 350975 ***