FS#4956 - ttf-cheapskate breaks openbox
Attached to Project:
Arch Linux
Opened by Darin (omgwtfbyobbq) - Tuesday, 04 July 2006, 06:24 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 04 July 2006, 07:28 GMT
Opened by Darin (omgwtfbyobbq) - Tuesday, 04 July 2006, 06:24 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 04 July 2006, 07:28 GMT
|
Details
I installed xorg-7 and the land was calm, exe openbox spoke,
and openbox blessed me with it's standards compliant
presence. Then I decided I'd like domestic manners and
installed ttf-cheapskate and dependencies (twm and some
other stuff). After this openbox (and gtk-chtheme) couldn't
find fonts for some reason, probably due to one of the
packages ttf-cheapskate pulled in? I found a related forum
post and apparently intalling artwiz-fonts and
font-bitstream-speedo solves the problem, somehow... It'd be
great if these two packages were dependencies of
ttf-cheapskate.
|
This task depends upon
Closed by Jan de Groot (JGC)
Saturday, 05 August 2006, 15:58 GMT
Reason for closing: Fixed
Additional comments about closing: Most fonts are fixed with correct postinstall. At least these fonts are.
Saturday, 05 August 2006, 15:58 GMT
Reason for closing: Fixed
Additional comments about closing: Most fonts are fixed with correct postinstall. At least these fonts are.
Comment by Jan de Groot (JGC) -
Tuesday, 04 July 2006, 11:21 GMT
Comment by Darin (omgwtfbyobbq) -
Friday, 07 July 2006, 17:37 GMT
Comment by Jan de Groot (JGC) -
Friday, 07 July 2006, 17:44 GMT
Comment by Darin (omgwtfbyobbq) -
Friday, 07 July 2006, 20:20 GMT
I guess the cheapskate fonts still need adjustments to the new
font installation policy we have. The two fonts you named to fix
the problem have been fixed for this policy, I guess the
postinstall of those fonts make sure the font cache and font.dir
files on your system are working again.
Sounds good to me. I also installed the fonts associated with
asian characters and had the same thing happen. This time
reinstalling those two fonts didn't work, so I searched and found
the refresh-fonts script. Since this seems to be a widely known
bug, should I just shoot the maintainters of those fonts an email
instead of filing another bug report?
A combined bug for all these fonts is still open. I haven't had
the time to check them all yet, only half of them are done up to
now.
Oh, well then, I'll check that out. Thanks for the info! :)