Dia crashed randomly, possible pango bug?

[hiroshi yui]

Binary package hint: dia

Ubuntu version: 9.10
Console output:
$ dia
sys:1: PangoWarning: Unable to open font file /usr/share/fonts/truetype/arphic/uming.ttc for font AR PL UMing TW Light 15.359375, falling back to /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf

sys:1: PangoWarning: Unable to open font file /usr/share/fonts/truetype/arphic/uming.ttc for font AR PL UMing TW Light 12, falling back to /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf

sys:1: PangoWarning: Unable to open font file /usr/share/fonts/wenquanyi/wqy-zenhei/wqy-zenhei.ttc for font WenQuanYi Zen Hei Medium 15.359375, falling back to /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf

Pango-ERROR **: Unable to open font file /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf for font AR PL UMing TW Light 15.359375, exiting

aborting...

[hiroshi yui (hiroshiyui)]

Hello all,
I found that when I enable anti-aliasing in Dia, it crashed randomly and console output as above. By contrast, if I turn anti-aliasing off, it's totally ok. Any ideas?

Thanks.

[agonified (hakanakkan)]

Same here... console output:

Pango-ERROR **: Unable to open font file /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf for font DejaVu Sans Bold 15.359375, exiting

[ℵ (zeta-function)]

It happens to me too.

This should be a CRITICAL bug, rendering dia almost unusable.

[penalvch (penalvch)]

hirshi yui, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
gksudo gedit /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Please do not attach your crash report manually to this report and reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs