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 348882 - crash on Computer
crash on Computer
Status: RESOLVED DUPLICATE of bug 339605
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-07-27 00:30 UTC by andyfranyates
Modified: 2006-07-27 09:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description andyfranyates 2006-07-27 00:30:45 UTC 
What were you doing when the application crashed?
clicked on sda2 hard drive icon from places/computer


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.90 2006-07-24 (Ubuntu)
BugBuddy Version: 2.15.90

Memory status: size: 83365888 vsize: 0 resident: 83365888 share: 0 rss: 29216768 rss_rlim: 0
CPU usage: start_time: 1153958673 rtime: 0 utime: 2164 stime: 0 cutime:1965 cstime: 0 timeout: 199 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 -1225685328 (LWP 5146)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 69669

Thread 1 (Thread -1225685328 (LWP 5146))

  • #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 ??
  • #8 ??
  • #0 __kernel_vsyscall 






Comment 1


Fabio Bonelli





          2006-07-27 09:47:34 UTC
        



Thanks for the bug report. 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?


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