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 465775 - crash in Computer: opening my data partitio...
crash in Computer: opening my data partitio...
Status: RESOLVED DUPLICATE of bug 406462
Product: nautilus
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-11 20:22 UTC by sbennett
Modified: 2007-10-25 12:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description sbennett 2007-08-11 20:22:20 UTC 
What were you doing when the application crashed?
opening my data partition.


Distribution: PCLinuxOS release 2007 (PCLinuxOS) for i586
Gnome Release: 2.16.0 2006-11-20 (%vendor)
BugBuddy Version: 2.16.0

Memory status: size: 76255232 vsize: 0 resident: 76255232 share: 0 rss: 26120192 rss_rlim: 0
CPU usage: start_time: 1186820329 rtime: 0 utime: 141 stime: 0 cutime:132 cstime: 0 timeout: 9 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227912896 (LWP 3981)]
(no debugging symbols found)
0xb7f88410 in __kernel_vsyscall ()

+ Trace 154496

Thread 1 (Thread -1227912896 (LWP 3981))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/i686/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gtk_widget_get_toplevel
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 gtk_widget_get_toplevel
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 gtk_widget_has_screen
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 gtk_entry_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #12 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 POA_Nautilus_MetafileMonitor__init
  • #14 __libc_start_main
    from /lib/i686/libc.so.6
  • #15 ?? 






Comment 1


André Klapper





          2007-10-19 22:27:38 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, the 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 help fixing this by installing some debugging packages [1], start the application as normal, and try to 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] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui.

More details can be found here: http://live.gnome.org/GettingTraces







Comment 2


André Klapper





          2007-10-25 12:35:14 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 406462 ***