jwm icon indicating copy to clipboard operation
jwm copied to clipboard

Ugly fonts after Devuan upgrade

Open maccagnan opened this issue 3 years ago • 8 comments

After upgrading Devuan to Daedalus, all Jwm fonts look ugly (every other program works fine). I tried several fixes like: Reconfiguring the systemwide fonts trying several fonts in .jwmrc trying the default jwmrc Nothing seems to work My .jwmrc looks like this: <Font>-*-fixed-*-r-*-*-10-*-*-*-*-*-*-*</Font> or <Font>DejaVu Sans-10</Font> and other combinations. A screenshot of the taskbar can be seen at https://drive.google.com/file/d/1mr9dAY … p=sharing]

Any suggestions?

maccagnan avatar Dec 04 '21 21:12 maccagnan

You could try running:

jwm -v

or

ldd /path/to/jwm

to see if there is any mention of freetype, fontconfig, or pango. If not, it probably means that jwm was built with only the ancient XFree86-type fonts.

P.S. The link to your screenshot is broken from here.

yetanothergeek avatar Dec 04 '21 21:12 yetanothergeek

Thanks for your prompt reply.

$ jwm -v JWM v2.4.0 by Joe Wingbermuehle compiled options: confirm icons jpeg nls png shape svg xbm xft xinerama xpm xrender system configuration: /etc/jwm/system.jwmrc no mention of freetype, fontconfig, or pango in the output from lld /usr/bin/jwm

screenshot link: https://drive.google.com/file/d/1mr9dAYJqfqsIqgEHTy4fgjxGLdmINtOx/view?usp=sharing

maccagnan avatar Dec 04 '21 23:12 maccagnan

I downgraded Jwm from 2.4.0-1 to 2.3.7-5, and now the fonts are just fine. Not a solution, perhaps, but a fix.

maccagnan avatar Dec 05 '21 00:12 maccagnan

Or you could install pango-devel (and the other required *-devel packages) and compile jwm 2.4.1 from source.

yetanothergeek avatar Dec 05 '21 09:12 yetanothergeek

Actually, I have a Debian development version installed on a spare partition. I could do that or, perhaps, file a bug issue on Debian website.

maccagnan avatar Dec 05 '21 17:12 maccagnan

I would file the bug and build a new version to tide you over.

On Sun, Dec 5, 2021 at 12:12 PM maccagnan @.***> wrote:

Actually, I have a Debian development version installed on a spare partition. I could do that or, perhaps, file a bug issue on Debian website.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/joewing/jwm/issues/535#issuecomment-986266844, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHPGUGJUFFC62WWPCBLFV3UPOMHLANCNFSM5JL67AYQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

-- Kelly "STrRedWolf" Price http://redwolf.ws

STrRedWolf avatar Dec 05 '21 17:12 STrRedWolf

Same problem with jwm-2.4.0-1 under ArchLinux. Last working version is jwm-2.3.7-3

brussell1 avatar Dec 14 '21 20:12 brussell1

@brussell1 you can try jwm-git from AUR. The PKGBUILD doesn't explicitly require pango, but it should still link to it, provided you have pango installed (which you probably do) https://aur.archlinux.org/packages/jwm-git/

yetanothergeek avatar Dec 14 '21 21:12 yetanothergeek