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 365485 - crash in GNOME Commander: Trying to view a jpeg im...
crash in GNOME Commander: Trying to view a jpeg im...
Status: RESOLVED DUPLICATE of bug 364620
Product: pango
Classification: Platform
Component: general
1.14.x
Other All
: High critical
: ---
Assigned To: pango-maint
pango-maint
: 366476 366666 366674 382941 408447 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-10-26 22:43 UTC by erez.schatz
Modified: 2007-02-16 21:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description erez.schatz 2006-10-26 22:43:17 UTC 
Version: 1.2.0

What were you doing when the application crashed?
Trying to view a jpeg image


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

Memory status: size: 44949504 vsize: 0 resident: 44949504 share: 0 rss: 17793024 rss_rlim: 0
CPU usage: start_time: 1161708159 rtime: 0 utime: 1810 stime: 0 cutime:1599 cstime: 0 timeout: 211 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-commander'

(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 -1224898896 (LWP 10745)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 78597

Thread 1 (Thread -1224898896 (LWP 10745))

  • #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 FcFreeTypeCharIndex
    from /usr/lib/libfontconfig.so.1
  • #5 pango_fc_font_lock_face
    from /usr/lib/libpangoft2-1.0.so.0
  • #6 pango_fc_font_get_glyph
    from /usr/lib/libpangoft2-1.0.so.0
  • #7 script_engine_init
    from /usr/lib/pango/1.5.0/modules/pango-hangul-fc.so
  • #8 script_engine_init
    from /usr/lib/pango/1.5.0/modules/pango-hangul-fc.so
  • #9 pango_coverage_new
    from /usr/lib/libpango-1.0.so.0
  • #10 pango_shape
    from /usr/lib/libpango-1.0.so.0
  • #11 pango_layout_set_width
    from /usr/lib/libpango-1.0.so.0
  • #12 pango_layout_iter_get_char_extents
    from /usr/lib/libpango-1.0.so.0
  • #13 pango_layout_iter_get_char_extents
    from /usr/lib/libpango-1.0.so.0
  • #14 pango_layout_iter_get_char_extents
    from /usr/lib/libpango-1.0.so.0
  • #15 pango_fc_font_create_metrics_for_context
    from /usr/lib/libpangoft2-1.0.so.0
  • #16 pango_cairo_fc_font_get_type
    from /usr/lib/libpangocairo-1.0.so.0
  • #17 pango_font_get_metrics
    from /usr/lib/libpango-1.0.so.0
  • #18 text_render_get_display_mode
    from /usr/lib/gnome-commander/libgviewer.so.0
  • #19 text_render_set_font_size
    from /usr/lib/gnome-commander/libgviewer.so.0
  • #20 gviewer_set_font_size
    from /usr/lib/gnome-commander/libgviewer.so.0
  • #21 gviewer_window_set_settings
    from /usr/lib/gnome-commander/libgviewer.so.0
  • #22 gviewer_window_file_view
    from /usr/lib/gnome-commander/libgviewer.so.0
  • #23 ??
  • #24 ??
  • #25 ??
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2006-10-29 12:33:02 UTC
        



*** Bug 366476 has been marked as a duplicate of this bug. ***






Comment 2


André Klapper





          2006-10-29 12:33:17 UTC
        



*** Bug 366666 has been marked as a duplicate of this bug. ***






Comment 3


André Klapper





          2006-10-29 12:33:24 UTC
        



*** Bug 366674 has been marked as a duplicate of this bug. ***






Comment 4


André Klapper





          2006-10-29 12:33:33 UTC
        



looks like a pango or fontconfig issue, reassigning, confirming as per duplicates.






Comment 5


erez.schatz





          2006-10-30 15:07:08 UTC
        



Also worth mentioning, the images that caused this crash were, at the time, restricted as root. After I chown-ed them to the regular (non-admin) user, there was no crash.






Comment 6


Behdad Esfahbod





          2006-11-01 22:34:16 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 364620 ***






Comment 7


Bruno Boaventura





          2006-12-06 21:48:45 UTC
        



*** Bug 382941 has been marked as a duplicate of this bug. ***






Comment 8


Christian Kirbach





          2007-02-16 21:55:22 UTC
        



*** Bug 408447 has been marked as a duplicate of this bug. ***