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 415161 - crash in CD/DVD Creator: installation
crash in CD/DVD Creator: installation
Status: RESOLVED DUPLICATE of bug 363289
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-06 02:57 UTC by frafael
Modified: 2007-06-20 21:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description frafael 2007-03-06 02:57:56 UTC
What were you doing when the application crashed?
installation


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

Memory status: size: 27553792 vsize: 0 resident: 98889728 share: 0 rss: 98889728 rss_rlim: 0
CPU usage: start_time: 377 rtime: 0 utime: 1173149841 stime: 0 cutime:244 cstime: 0 timeout: 227 it_real_value: 0 frequency: 17

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 805545744 (LWP 6327)]
(no debugging symbols found)
0x0f23a370 in __waitpid_nocancel () from /lib/libpthread.so.0

Thread 1 (Thread 805545744 (LWP 6327))

  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 _gtk_icon_cache_add_icons
    from /usr/lib/libgtk-x11-2.0.so.0
  • #4 gtk_icon_theme_list_icons
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_object_set
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_value_set_boxed
    from /usr/lib/libgobject-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_show
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
  • #28 ??
  • #29 ??
  • #30 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #31 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #32 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #33 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #34 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #35 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #36 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #37 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #38 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0

Comment 1 Susana 2007-03-07 11:15:51 UTC
Thanks for taking the time to report this bug.
Unfortunately, that 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. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 André Klapper 2007-06-20 21:07:34 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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