FS#76076 - [xterm] 373 [Orphan] ignores xft.dpi xresource

Attached to Project: Arch Linux
Opened by Gabor Hauzer (cysp74) - Friday, 30 September 2022, 16:20 GMT
Last edited by Toolybird (Toolybird) - Saturday, 15 October 2022, 21:08 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
It's very likely an upstream bug, new xterm 373 doesn't respect xft.dpi, however it worked and used flawlessly in 372.

Steps to reproduce:
Set xft.dpi in xresources, xrdb -load <xresource>, launch xterm. nothing will happen.

Checked under xorg.
This task depends upon

Closed by  Toolybird (Toolybird)
Saturday, 15 October 2022, 21:08 GMT
Reason for closing:  Fixed
Additional comments about closing:  xterm 374-1
Comment by Toolybird (Toolybird) - Monday, 03 October 2022, 06:42 GMT
> It's very likely an upstream bug

As per the Arch bug guidelines [1] you really must report this upstream.

[1] https://wiki.archlinux.org/title/Bug_reporting_guidelines#Upstream_or_Arch%3F
Comment by Gabor Hauzer (cysp74) - Monday, 03 October 2022, 09:10 GMT

> As per the Arch bug guidelines [1] you really must report this upstream.

- Already happened before I opened this ticket.
- As I told it's very likely, but not sure, since the developer told last change shouldn't cause this kind of behavior.

Ty
Comment by Toolybird (Toolybird) - Tuesday, 04 October 2022, 07:33 GMT
The upstream dev doesn't think there's a bug? Unfortunately there is not much we can do because this Arch pkg is marked as "Orphan" i.e. no maintainer. I have notified @arojas who kindly packaged the recent update but not sure if investigating new bugs is on the agenda...
Comment by Jaak Pruulmann-Vengerfeldt (jjpp) - Tuesday, 04 October 2022, 09:43 GMT
Looks like the fontconfig now gets initialized by xterm and not by Xft.
Overriding the DPI via .config/fontconfig/fonts.conf was workaround for me (using debian unstable but that should not make a difference. This here was the only complaint about the broken DPI-calculation in 373 I could find).

Comment by Antonio Rojas (arojas) - Tuesday, 04 October 2022, 09:54 GMT
Can someone please post the link to the upstream report?
Comment by Jaak Pruulmann-Vengerfeldt (jjpp) - Tuesday, 04 October 2022, 10:21 GMT
I am not sure if linking to the upstream report is possible at all: https://invisible-island.net/xterm/xterm.faq.html#report_bugs
Comment by Gabor Hauzer (cysp74) - Tuesday, 04 October 2022, 18:52 GMT
Hi,


In the meantime I was able to debug the origin of problem, and it's coming from a newly inserted code snippet of xterm (fontutils.c) and I'm in touch w/ developer. So, this issue intro'd by new package of 373 xterm comes from upstream.

Ty


Loading...