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 171851 - fatal crash when attempting to browse / open file
fatal crash when attempting to browse / open file
Status: RESOLVED DUPLICATE of bug 151068
Product: GIMP
Classification: Other
Component: General
2.2.x
Other Windows
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2005-03-28 06:45 UTC by Kevin Morris
Modified: 2008-01-15 12:51 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Kevin Morris 2005-03-28 06:45:50 UTC
Version details: gtk 2.6.4
Distribution/Version: SP2 + latest hotfixes

GIMP crashes out on when I attempt to browse my desktop via the Open Image dialog:

"Pango-ERROR **; file shape.c; line 75 (pango_shape); assertion failed;
(glyphs->num_glyphs > 0)

aborting..."

Followed immediately by a Microsoft C++ Visual Runtime Library runtime error
pointed to the GIMP executable (gimp-2.2.exe) which kills the app.

Crashes happens each and every time I attempt this. All I am doing is launching
GIMP, going to Open Image and browsing the files on my desktop - it seems to
happen mid-scroll, even. I've been able to browse other directories without an
issue so I'm starting to think there's a particular file extension on my desktop
that GIMP isn't happy with. Here's a full list of the extensions that are on my
desktop:

some folders
some jpgs
some bmps
some pdfs
some exes
a few zip files
one tar.gz file
some html files
some css files
one .mht file
a php file
some docs
some mpegs
an mp3
and some shortcuts

...all standard stuff, right?
Comment 1 weskaggs 2005-03-28 14:46:02 UTC
Kevin,
  This bug has already been reported, but it is a bug in Pango (the font
rendering library that GIMP uses), so you would not have been able to find it by
searching for duplicates.  It seems to be quite difficult to figure out -- the
best temporary workaround I can recommend is to revert back to Gtk+ 2.4.14 until
it gets fixed.  However one person with this problem was able to work around it
by changing to a different Windows theme (see bug #170826).

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