You are not logged in.
Some HIDPI issue?
xdpyinfo | grep resolution
xrandr -q
Offline
Some HIDPI issue?
xdpyinfo | grep resolution xrandr -q
Thanks man and everyone!
Added
export QT_FONT_DPI=96
in .bashrc and xinitrc
and works perfectly
Last edited by werewolf_65 (2020-08-24 15:43:05)
Offline
https://www.archlinux.org/packages/comm … 86_64/vym/
Remove it from the export, the wiki means to "run vym w/ QT_FONT_DPI=96".
Offline
https://www.archlinux.org/packages/comm … 86_64/vym/
Remove it from the export, the wiki means to "run vym w/ QT_FONT_DPI=96".
Ohh my bad. Thanks. Updated.
Offline
According to a comment in this bugreport : setting 'deny = 0' in /etc/security/faillock.conf solves the bad behaviour in Qt5 applications :
https://bugs.archlinux.org/task/67644
Comment by Trit' (trit) - Tuesday, 25 August 2020, 10:35 GMT+1
“deny = 0” fixed both the lockout and the appearance of the Qt5 applications for me! Thank you a million times, nl6720!!! \o/
It seems that there is a link between pam package and Qt5 applications in unknown conditions that can explain some GUI bugs.
Last edited by Potomac (2020-08-25 10:47:12)
Offline
https://bugs.archlinux.org/task/67644#comment191936 seems to suggest that the qt5ct config wasn't used (and therefore a wrong? theme?)
If you fail™ to login and maybe use systemd-homed, I could see how your config gets garbled ('cause you can't access it)
That does however not seem to be the issue here.
Offline