#1103304 xskat 4.0-9 starts in a tiny window that cannot be enlarged anymore.

Package:
xskat
Source:
xskat
Description:
3-player card game "Skat"
Submitter:
Date:
2025-04-24 14:33:02 UTC
Severity:
normal
Tags:
#1103304#5
Date:
2025-04-16 10:26:03 UTC
From:
To:
Dear Maintainer,

xskat 4.0-9 only starts in a tiny xterm-like window that cannot be
enlarged anymore. There is no possibility to scale the window freely.
Image and text objects are displayed so small that it is almost
impossible to use the programme. Other programmes such as gnome-mahjongg
or gnome-sudoku, on the other hand, continue to function without
impairment.

#1103304#10
Date:
2025-04-16 14:16:33 UTC
From:
To:
Am 16.04.2025 um 10:26:03 Uhr schrieb Karlheinz Geyer:

IIRC this window was never resizable.

IIRC this was always the case.

Do you have a high DPI and set up any enlargement of text in the
settings of your desktop environment?
Also tell the monitor model.

On my system with "normal" monitors, xskat looks fine.

#1103304#15
Date:
2025-04-24 14:32:14 UTC
From:
To:
Control: severity -1 normal
Control: tags -1 moreinfo unreproducible

Ack to both.

However, the "-geometry" command line option allows specifying a
different size upon startup.

Thanks @Marco, same here, tested with both the Bookworm version and the
Trixie version.

@Karlheinz, this sounds more like your display environment applying some
settings than XSkat doing anything wrong by itself.  However, XSkat is
admittedly a rather old-fashioned program, so it can all too easily
happen that it falls through the proverbial cracks when run in any
modern display environment, unlike other programmes that have been
explicitly developed for the environment of choice (in your case Gnome,
I presume).

As for the text size, the "-font" command line option might help, using
any of the fonts listed by the "xlsfonts" command from the "x11-utils"
package. This won't change the size of the images, though. So better
check your display environment for any settings which might have an
effect, just like Marco suggests.

For now I am lowering the bug severity to "normal", as per
<https://www.debian.org/Bugs/Developer#severities> since it doesn't
seem to be a general issue, and tag the bug according to
<https://www.debian.org/Bugs/Developer#tags> since I don't see yet what
XSkat could/should do differently.

Cheers,
Flo