Skip to main content
Topic: Plasma/X11 was torn apart for downscaling using the below environment varibles (Read 594 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Plasma/X11 was torn apart for downscaling using the below environment varibles

Due to so, every Qt6/5 apps are entirely unusable until i disable the related scaling arguments below
Code: [Select]
ELM_SCALE=0.62
GDK_DPI_SCALE=0.62
GTK_IM_MODULE=ibus
HISTFILESIZE=0
HISTIGNORE=*
HISTSIZE=0
KWIN_FORCE_SW_CURSOR=1
LANG="en_GB.UTF-8"
LANGUAGE="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_ALL="en_GB.UTF-8"
LC_COLLATE="en_GB.UTF-8"
LC_CTYPE="en_GB.UTF-8"
LC_IDENTIFICATION="en_GB.UTF-8"
LC_MEASUREMENT="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_MONETARY="en_GB.UTF-8"
LC_NAME="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_PAPER="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
PLASMA_USE_QT_SCALING=1
QT_AUTO_SCREEN_SCALE_FACTOR=0
QT_FONT_DPI=54
QT_IM_MODULE=ibus
QT_QPA_PLATFORMTHEME=qt5ct
QT_SCALE_FACTOR=0.62
QT_SCREEN_SCALE_FACTOR=0.62
SAVEHIST=0
XMODIFIERS=@im=ibus
However, even when unscaled, still too high in DPI for me, i also set the related section X11 arguments for my sddm.conf to,
Code: [Select]
ServerArguments = -nolisten tcp -dpi 54
But SDDM entirely doesn't react to my settings for downscaling
Finally, when i run the below command, it still entirely doesn't reacct,
Code: [Select]
% xrandr --dpi 54
%
:) AMD APU R4750G Zen2 Lucienne-G GCN Vega8 :) ASRock DeskMini X300 AMD edition :) (14.9+46.9)GiB SoDiMM DDR4 RAM’s
:) Samsung 990PRO HS NVMe SSD 3.63TiB (nda0; with 2.61TiB ZPool) :) Kingston NV2 NVMe SSD 3.63TiB (nvme1n1; with 2.7TiB ZPool)
:) Samsung 860QVO 2.5’’ SSD 3.63TiB (sda; with 2.1TiB ZPool) :) Transcend 220Q 2.5’’ SSD 1.82TiB (sdb; with 1.29TiB ZPool)
:) Intehill 4K UHD LED-IGZo screen

Re: Plasma/X11 was torn apart for downscaling using the below environment varibles

Reply #1
I've hit a similar issue but only with the Qt6 stuff, the fix was as simple as setting QT_QPA_PLATFORMTHEME to qt6ct (not qt5ct as you have it there, install qt6ct instead; it works with qt5 too)

Basically what Qt*ct does is replace the Qt platform support, which for now Kde is still using Qt5, later this year will be released Plasma 6 with full Qt6 platform support.

LXQt has experimentally platform support for Qt6, called lxqt-qt6plugin-git, which should also do the same effect just by building that package and installing it.

This should at least partly fix your problem. If you still have weird scaling issues try disabling the compositing in KWin and replace it with standalone compositor e.g. Picom.


//Offtopic: Trinity i see, a man of culture :) I use it sometimes dearly.

Re: Plasma/X11 was torn apart for downscaling using the below environment varibles

Reply #2
I also have Qt6CT already installed but never enabled, just to enable so to wait for Qt6 based KDE Plasma 6?
And try disabling KWIn compositions and used a standalone composition instead? Has to be tested to answer you

I've hit a similar issue but only with the Qt6 stuff, the fix was as simple as setting QT_QPA_PLATFORMTHEME to qt6ct (not qt5ct as you have it there, install qt6ct instead; it works with qt5 too)

Basically what Qt*ct does is replace the Qt platform support, which for now Kde is still using Qt5, later this year will be released Plasma 6 with full Qt6 platform support.

LXQt has experimentally platform support for Qt6, called lxqt-qt6plugin-git, which should also do the same effect just by building that package and installing it.

This should at least partly fix your problem. If you still have weird scaling issues try disabling the compositing in KWin and replace it with standalone compositor e.g. Picom.


//Offtopic: Trinity i see, a man of culture :) I use it sometimes dearly.
:) AMD APU R4750G Zen2 Lucienne-G GCN Vega8 :) ASRock DeskMini X300 AMD edition :) (14.9+46.9)GiB SoDiMM DDR4 RAM’s
:) Samsung 990PRO HS NVMe SSD 3.63TiB (nda0; with 2.61TiB ZPool) :) Kingston NV2 NVMe SSD 3.63TiB (nvme1n1; with 2.7TiB ZPool)
:) Samsung 860QVO 2.5’’ SSD 3.63TiB (sda; with 2.1TiB ZPool) :) Transcend 220Q 2.5’’ SSD 1.82TiB (sdb; with 1.29TiB ZPool)
:) Intehill 4K UHD LED-IGZo screen

Re: Plasma/X11 was torn apart for downscaling using the below environment varibles

Reply #3
Still, every apps never get properly downscaled, but still being entirely torn apart to be entirely unusable
Simply entirely nothing has been changed, i’ve instead to be await for the full KDE Plasma 6 availability coming to Artix
:) AMD APU R4750G Zen2 Lucienne-G GCN Vega8 :) ASRock DeskMini X300 AMD edition :) (14.9+46.9)GiB SoDiMM DDR4 RAM’s
:) Samsung 990PRO HS NVMe SSD 3.63TiB (nda0; with 2.61TiB ZPool) :) Kingston NV2 NVMe SSD 3.63TiB (nvme1n1; with 2.7TiB ZPool)
:) Samsung 860QVO 2.5’’ SSD 3.63TiB (sda; with 2.1TiB ZPool) :) Transcend 220Q 2.5’’ SSD 1.82TiB (sdb; with 1.29TiB ZPool)
:) Intehill 4K UHD LED-IGZo screen

Re: Plasma/X11 was torn apart for downscaling using the below environment varibles

Reply #4
Yes this would be ideal, but still your problem shouldn't be that all programs get scaled weirdly.

Do you have an .Xresources file in your home directory? I've seen Plasma not read it correctly before.

Also just try to delete anything KDE related from .config and .local/share from another de, then log back in to plasma, of course backup important settings first.

Re: Plasma/X11 was torn apart for downscaling using the below environment varibles

Reply #5
You mean removing Plasma settings first from e.g. Trinity or Trinity then try again? How much should be removed? Everything?
Yes this would be ideal, but still your problem shouldn't be that all programs get scaled weirdly.

Do you have an .Xresources file in your home directory? I've seen Plasma not read it correctly before.

Also just try to delete anything KDE related from .config and .local/share from another de, then log back in to plasma, of course backup important settings first.
:) AMD APU R4750G Zen2 Lucienne-G GCN Vega8 :) ASRock DeskMini X300 AMD edition :) (14.9+46.9)GiB SoDiMM DDR4 RAM’s
:) Samsung 990PRO HS NVMe SSD 3.63TiB (nda0; with 2.61TiB ZPool) :) Kingston NV2 NVMe SSD 3.63TiB (nvme1n1; with 2.7TiB ZPool)
:) Samsung 860QVO 2.5’’ SSD 3.63TiB (sda; with 2.1TiB ZPool) :) Transcend 220Q 2.5’’ SSD 1.82TiB (sdb; with 1.29TiB ZPool)
:) Intehill 4K UHD LED-IGZo screen

Re: Plasma/X11 was torn apart for downscaling using the below environment varibles

Reply #6
Unfortunately there was a minor messup for even just rename those items w/in whose "kde" and "Plasma" keywords into sth else
And even when having changed the window decoration to "Oxygen", still entirely doesn't stop apps against being torn apart
No better changes have been made anymore right now and maybe unfortunately i've to be await for KDE Plasma 6 Wayland compositions since about this autumn
:) AMD APU R4750G Zen2 Lucienne-G GCN Vega8 :) ASRock DeskMini X300 AMD edition :) (14.9+46.9)GiB SoDiMM DDR4 RAM’s
:) Samsung 990PRO HS NVMe SSD 3.63TiB (nda0; with 2.61TiB ZPool) :) Kingston NV2 NVMe SSD 3.63TiB (nvme1n1; with 2.7TiB ZPool)
:) Samsung 860QVO 2.5’’ SSD 3.63TiB (sda; with 2.1TiB ZPool) :) Transcend 220Q 2.5’’ SSD 1.82TiB (sdb; with 1.29TiB ZPool)
:) Intehill 4K UHD LED-IGZo screen

Re: Plasma/X11 was torn apart for downscaling using the below environment varibles

Reply #7
Yeah exactly I meant to delete everything with kde/plasma from Trinity, sometimes plasma settings come in the least expected places and break things when they get recreated.

Until this autumn, if you'd like to try, use LXQt desktop with KWin as a window manager which has most of the kde usefullness, with the lxqt-qt6plugin-git package (if you use that unset qt5/6ct, or maybe use Kvantum as platformtheme), and with .Xresources file specifying Xft.dpi (if you use that unset gtk/qt scaling variables). This is the best compromise setup I personally use since last year, and it's good enough.

Wayland will indeed solve this completely but i'll wait more before i switch, it's still immature imo.

 

Re: Plasma/X11 was torn apart for downscaling using the below environment varibles

Reply #8
Maybe Wayland is sth at late alpha to early beta, but X11 is still rather old
But Wayland isn't designed to become a replacement over X11
Ultimately newbies soon and later will always have whose own freedoms between Wayland and X11
:) AMD APU R4750G Zen2 Lucienne-G GCN Vega8 :) ASRock DeskMini X300 AMD edition :) (14.9+46.9)GiB SoDiMM DDR4 RAM’s
:) Samsung 990PRO HS NVMe SSD 3.63TiB (nda0; with 2.61TiB ZPool) :) Kingston NV2 NVMe SSD 3.63TiB (nvme1n1; with 2.7TiB ZPool)
:) Samsung 860QVO 2.5’’ SSD 3.63TiB (sda; with 2.1TiB ZPool) :) Transcend 220Q 2.5’’ SSD 1.82TiB (sdb; with 1.29TiB ZPool)
:) Intehill 4K UHD LED-IGZo screen