GNOME Bugzilla – Bug 304702
Pango-ERROR **: file shape.c line 75 (pango_shape): assertion failed: (glyphs->num_glyphs > 0)
Last modified: 2007-06-13 13:16:38 UTC
Steps to reproduce: 1. Start GIMP 2. File -> Open... 3. Click 'C:\' Stack trace: Other information:
Version: GIMP 2.2.7
There don't seem to be any duplicates of this that are in an "Open" status. I have a number of gaim bugs that I'd like to mark as dependent on this (or some other bug), should I use this bug or should one of the closed ones be reopened?
*** Bug 301139 has been marked as a duplicate of this bug. ***
*** Bug 307604 has been marked as a duplicate of this bug. ***
Note that the most useful information about this bug seems to be in the comments for bug #151068 (even though it is marked as a duplicate of another bug).
Note that the error in the Subject line is entirely generic .. it just means that *SOMETHING* went wrong in the shaping process, and could have many different sources.
This error happens when you open a directory with a file named somthing weird. In my case it was a file named https___www1.netbank.commbank.com.au_NetBank_scripts_cgiclnt.....pdf
Same thing happens on a PC that's never had any version of GIMP or the GTK on it after install of 2.2.7 1. Start GIMP 2. File -> Open... 3. Click 'My Documents' button and wait a couple of seconds and the error pops up and when you clcik ok GIMP crashes.
*** Bug 311877 has been marked as a duplicate of this bug. ***
One of you guys should run the crashing application under gdb, put a breakpoint on g_log by typing "b g_log", then type "run" and enter, wait for control to get back to gdb, and type "bt" and enter, send the resulting backtrace here. I'm assuming that no other error message is written to the output before the error reported here.
*** Bug 309961 has been marked as a duplicate of this bug. ***
*** Bug 312898 has been marked as a duplicate of this bug. ***
This is caused by some Windows fonts. eg "MS Sans Serif". I had this same problem on Linux. I had windows fonts installed on my fedora (core 4) and "MS Sans Serif" defined as default font in gnome. Every time, i opened Nautilus, it crashed. When i changed default font, problem went away. I guess that this change is causing this behaviour: http://cvs.gnome.org/viewcvs/pango/pango/shape.c?r1=1.9&r2=1.10
Also, the current action -- crash -- upon noticing that something went wrong in the shaper just isn't right. It would be far better to issue a g_warning and then insert a random glyph or two so the rest of pango could limp on. For example, just insert "?".
Tomi - anything happening on Linux is unrelated to this bug report and should be filed separetely, thanks.
*** Bug 314312 has been marked as a duplicate of this bug. ***
*** Bug 314295 has been marked as a duplicate of this bug. ***
*** Bug 314228 has been marked as a duplicate of this bug. ***
*** Bug 314535 has been marked as a duplicate of this bug. ***
*** Bug 317243 has been marked as a duplicate of this bug. ***
*** Bug 317034 has been marked as a duplicate of this bug. ***
I think Bug 317243 is a duplicate too. It's not on windows, but the backtrace shows that the same assertion fails as in this bug.
Created attachment 53665 [details] [review] Patch to downgrade crash to critical This patch -- untested, except that it compiles -- downgrades the crash to an error message by adding a nul glyph when something went wrong. With this... (a) we don't look like dorks when file->open crashes the program. (b) we get a chance at figuring out the cause (by looking at what text was rendered blank)
Created attachment 58354 [details] [review] committed patch. 2006-01-29 Behdad Esfahbod <behdad@gnome.org> Do not crash if the (win32 typically) shaper fails. Bug #304702: * pango/pango-engine.c (_pango_engine_shape_shape): Set num_glyphs to zero if failing. * pango/pango-shape.c (pango_shape): Instead of crashing if the shaper failed to produce any glyphs, print out a warning message containing the name of the font, and mark the font such that we don't keep printing warning for the same font. Moreover, inject one whitespace glyph per character, so you just see nothing, but everything works otherwise.
This actually closes this bug. As for why this happenes, that's what I'm working on right now and will be fixed soon, but anyway, the crash is gone.
I'm unclear what to do with the patch. Could someone walk me through how to install it? Sorry to be ignorant. I like GIMP, but I have **very** limited programming skills.
Can anyone help with how to fix this problem? If there is a release with this problem fixed? Thanks
This is in Pango 1.12.0 that was released last week.
*** Bug 343474 has been marked as a duplicate of this bug. ***
*** Bug 348715 has been marked as a duplicate of this bug. ***
*** Bug 307881 has been marked as a duplicate of this bug. ***
*** Bug 376695 has been marked as a duplicate of this bug. ***
*** Bug 325704 has been marked as a duplicate of this bug. ***
*** Bug 446917 has been marked as a duplicate of this bug. ***