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 413183 - crash in Computer: ejecting the cd by right...
crash in Computer: ejecting the cd by right...
Status: RESOLVED DUPLICATE of bug 360330
Product: nautilus
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-02-28 19:44 UTC by sqwishybon
Modified: 2007-06-22 14:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description sqwishybon 2007-02-28 19:44:30 UTC 
What were you doing when the application crashed?
ejecting the cd by right clicking on the desktop icon and pressing eject


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

Memory status: size: 207564800 vsize: 207564800 resident: 26976256 share: 15331328 rss: 26976256 rss_rlim: -1
CPU usage: start_time: 1172640969 rtime: 2190 utime: 1570 stime: 620 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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 47787716442704 (LWP 5046)]
0x00002b766ddfaeef in waitpid () from /lib/libpthread.so.0

+ Trace 114708

Thread 1 (Thread 47787716442704 (LWP 5046))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 IA__gtk_container_add
    at gtkcontainer.c line 946
  • #4 fm_directory_view_bump_zoom_level
  • #5 fm_directory_view_bump_zoom_level
  • #6 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #10 _gtk_action_emit_activate
    at gtkaction.c line 835
  • #11 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #15 IA__gtk_widget_activate
    at gtkwidget.c line 3946
  • #16 IA__gtk_menu_shell_activate_item
    at gtkmenushell.c line 1024
  • #17 gtk_menu_shell_button_release
    at gtkmenushell.c line 630
  • #18 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #19 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #23 gtk_widget_event_internal
    at gtkwidget.c line 3915
  • #24 IA__gtk_propagate_event
    at gtkmain.c line 2335
  • #25 IA__gtk_main_do_event
    at gtkmain.c line 1569
  • #26 gdk_event_dispatch
    at gdkevents-x11.c line 2318
  • #27 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #28 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #29 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #30 IA__gtk_main
    at gtkmain.c line 1148
  • #31 POA_Nautilus_MetafileMonitor__init
  • #32 __libc_start_main
    from /lib/libc.so.6
  • #33 ??
  • #34 ??
  • #35 ??
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


André Klapper





          2007-03-04 20:56:24 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 also installing nautilus-dbg, 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!

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







Comment 2


André Klapper





          2007-06-22 14:31:04 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 360330 ***