View Issue Details

IDProjectCategoryView StatusLast Update
0002651ardourbugspublic2020-04-19 20:14
ReporterEjis Assigned Tocth103  
PrioritynormalSeveritycrashReproducibilityalways
Status closedResolutionfixed 
Product Version2.8 
Summary0002651: Crash with sazanami TTF
DescriptionHi,

I'm using my computer in japanese, with the sazanami fonts.
When starting a session, ardour crashes with this output:

Pango-ERROR **: Unable to open font file /usr/share/fonts/TTF/sazanami-gothic.ttf for font Sazanami Gothic Medium 7.9990234375, exiting

aborting...
????????
Additional InformationI'm using Zenwalk GNU/Linux
TagsNo tags attached.

  Users sponsoring this issue
Sponsors List Total Sponsorship = US$ 5

2009-06-26 11:59: Ejis (US$ 5)
  Users sponsoring this issue (Total Sponsorship = US$ 5)

Activities

Ejis

2009-05-01 10:17

reporter   ~0005953

After tesing with "export LANG=C", I got the same error with DejaVuSans.
The value 7.9990234375 still remains. I think this is the true problem.

Ejis

2009-05-01 11:05

reporter   ~0005954

Interesting thing: I don't have this error with ardourvst.

Ejis

2009-05-01 11:30

reporter   ~0005955

Last edited: 2009-07-09 15:02

I don't get this error when I create a new session with ardour2, and open it later.
This bug only occurs with sessions I saved with ardourvst. I must use it to be able to open them again.

nettings

2009-08-15 10:54

manager   ~0006553

is this still an issue, and is it really ardour's fault or a pango bug that might have been fixed in the mean time?

as a workaround, maybe check the session file for this weird value and edit it to something sane (if it's really in there), see if that helps.

Ejis

2009-09-10 13:15

reporter   ~0006658

This doesn't happen anymore since the latest version. I assume the problem is now solved.

cth103

2009-09-10 18:22

administrator   ~0006659

Reporter says this is fixed.

system

2020-04-19 20:14

developer   ~0021902

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2009-05-01 10:12 Ejis New Issue
2009-05-01 10:17 Ejis Note Added: 0005953
2009-05-01 11:05 Ejis Note Added: 0005954
2009-05-01 11:30 Ejis Note Added: 0005955
2009-06-26 11:59 Ejis Sponsorship Added Ejis: US$ 5
2009-06-26 11:59 Ejis Sponsorship Total 0 => 5
2009-07-09 15:02 Ejis Note Edited: 0005955
2009-08-15 10:54 nettings Note Added: 0006553
2009-08-15 10:54 nettings Status new => feedback
2009-09-10 13:15 Ejis Note Added: 0006658
2009-09-10 18:22 cth103 cost => 0.00
2009-09-10 18:22 cth103 Note Added: 0006659
2009-09-10 18:22 cth103 Status feedback => resolved
2009-09-10 18:22 cth103 Resolution open => fixed
2009-09-10 18:22 cth103 Assigned To => cth103
2010-04-24 10:28 cth103 Category bugs => bugs2
2010-04-24 10:31 cth103 Category bugs2 => bugs
2020-04-19 20:14 system Note Added: 0021902
2020-04-19 20:14 system Status resolved => closed