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 381531 - crash in CD/DVD Creator: J'ai cliqué droit sur l'...
crash in CD/DVD Creator: J'ai cliqué droit sur l'...
Status: RESOLVED DUPLICATE of bug 360330
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-02 08:54 UTC by huguesb_fr
Modified: 2006-12-02 12:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description huguesb_fr 2006-12-02 08:54:33 UTC
What were you doing when the application crashed?
J'ai cliqué droit sur l'icone de mon disque dur externe USB afin de le débrancher et j'ai cliqué sur "ejecter" ... et paf le chien


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

Memory status: size: 222654464 vsize: 222654464 resident: 37801984 share: 21188608 rss: 37801984 rss_rlim: -1
CPU usage: start_time: 1165045019 rtime: 19691 utime: 1846 stime: 17845 cutime:67 cstime: 12 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 47007133862448 (LWP 4872)]
(no debugging symbols found)
0x00002ac0af86ceef in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 47007133862448 (LWP 4872))

  • #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 gtk_container_add
    from /usr/lib/libgtk-x11-2.0.so.0
  • #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
    from /usr/lib/libgtk-x11-2.0.so.0
  • #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 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 gtk_menu_shell_append
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #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_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 _gdk_events_init
    from /usr/lib/libgdk-x11-2.0.so.0
  • #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 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #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 Germán Poo-Caamaño 2006-12-02 12:26:02 UTC
Thanks for taking the time to report this bug.
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 in order to help the developers?


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