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 363714 - crash in CD/DVD Creator: I was trying to get WINE...
crash in CD/DVD Creator: I was trying to get WINE...
Status: RESOLVED DUPLICATE of bug 361093
Product: pango
Classification: Platform
Component: general
1.14.x
Other All
: High critical
: ---
Assigned To: pango-maint
pango-maint
Depends on:
Blocks:
 
 
Reported: 2006-10-20 16:48 UTC by Janetswilliams
Modified: 2006-10-23 05:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Janetswilliams 2006-10-20 16:48:22 UTC
What were you doing when the application crashed?
I was trying to get WINE to work and guild wars


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

Memory status: size: 81240064 vsize: 0 resident: 81240064 share: 0 rss: 26845184 rss_rlim: 0
CPU usage: start_time: 1161362793 rtime: 0 utime: 368 stime: 0 cutime:351 cstime: 0 timeout: 17 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 -1226914128 (LWP 4542)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226914128 (LWP 4542))

  • #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 pango_shape
    from /usr/lib/libpango-1.0.so.0
  • #5 pango_layout_set_width
    from /usr/lib/libpango-1.0.so.0
  • #6 pango_layout_iter_get_char_extents
    from /usr/lib/libpango-1.0.so.0
  • #7 pango_layout_iter_get_char_extents
    from /usr/lib/libpango-1.0.so.0
  • #8 pango_layout_iter_get_char_extents
    from /usr/lib/libpango-1.0.so.0
  • #9 pango_layout_get_pixel_extents
    from /usr/lib/libpango-1.0.so.0
  • #10 pango_layout_get_pixel_size
    from /usr/lib/libpango-1.0.so.0
  • #11 eel_pango_font_description_get_largest_fitting_font_size
    from /usr/lib/libeel-2.so.2
  • #12 POA_Nautilus_MetafileMonitor__init
  • #13 g_cclosure_marshal_VOID__STRING
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #18 POA_Nautilus_MetafileMonitor__init
  • #19 POA_Nautilus_MetafileMonitor__init
  • #20 POA_Nautilus_MetafileMonitor__init
  • #21 POA_Nautilus_MetafileMonitor__init
  • #22 nautilus_undo_transaction_unregister_object
  • #23 fm_directory_view_bump_zoom_level
  • #24 nautilus_clipboard_monitor_emit_changed
  • #25 nautilus_directory_async_state_changed
  • #26 nautilus_icon_container_request_update_all
  • #27 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #28 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #29 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #30 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #31 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 POA_Nautilus_MetafileMonitor__init
  • #33 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #34 ??
  • #0 __kernel_vsyscall

Comment 1 Christian Kirbach 2006-10-21 14:12:03 UTC
similar to bug 357939 but not an exact duplicate

please install the pango debug package

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 Behdad Esfahbod 2006-10-23 05:14:39 UTC

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