Bug#1033690: Different HiDPI scaling for GTK applications
Package: kde-config-gtk-style Version: 5.27.2-1 Severity: important Tags: fixed-upstream, bookworm, sid, experimental I have a QHD 13' laptop screen, which requires (150-200%) scaling for it to be usable with any desktop environment (also have an external 4K monitor that needs similar scaling). Since upgrading to KDE 5.27.x the GTK application scaling has regressed (this was working fine in 5.26.x and even in the beta 5.26.90). Qt apps are correctly scaled but GTK apps are pegged at 100% scaling. This is a major headache for many users of GTK apps like firefox, gimp, inkscape, etc on KDE, as the apps look tiny. This regression was quickly reported upstream: https://bugs.kde.org/show_bug.cgi?id=466463 A fix has been merged into KDE 5.27.x, and it's slated to be released for version 5.27.4 (see: https://invent.kde.org/plasma/kde-gtk-config/-/merge_requests/63) Please consider allowing KDE 5.27.4 to migrate to testing when it's available or at least apply this upstream fix to the bookworm package before release. Best, Andres
Bug#754200: KDM does not initialize keyboard backlight support properly
reassign 754200 kdm/4.11.9-1 forwarded 754200 https://bugs.kde.org/show_bug.cgi?id=334321 retitle 754200 KDM does not initialize keyboard backlight support properly thanks -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAH=dyrfxhl8b1i31godjdxhdzbyaeqh6ujg5rob_bsla+qo...@mail.gmail.com
Bug#754200: kde-baseapps-bin: KDE fails to recognize keyboard backlight capabilities on fresh boot
A workaround is possible by creating a small script in ~.kde/env/ invoking: qdbus --system org.freedesktop.UPower For more info see: https://forum.kde.org/viewtopic.php?f=63t=121045 This bug appears to be in KDE. The power manager which is relying on upower should start it before login to become aware of all the laptop capabilities. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAH=dYrH1=PJJDqP2=ebv3m6dhggu981bh+cxltzso98wu39...@mail.gmail.com
Bug#754200: kde-baseapps-bin: KDE fails to recognize keyboard backlight capabilities on fresh boot
With the help of someone in the KDE forums () I found out the problem is the upower daemon is not started by KDE early enough (before KDM login) and this causes KDE power manager to become unaware of the keyboard brightness option. I tested this by in the following way: 1. Reboot machine 2. Wait till KDM login screen 3. Switch to a VT 4. Login there 5. ps aux | grep upower → zero results → upower is not running before login 6. invoke the command in my previous post to changer keyboard brightness 7. Upowerd is forced to start by dbus 8. Log out from VT 9. Login to KDE 10. Keyboard brightness works as expected It looks like upowerd is working as expected (from reading its description on its man page). It falls to the desktop environment to probe it and recognize that's possible to changer the keyboard backlight brightness. Andres -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAH=dyrgg-rfiqfuj_2kjzrvulge1fg4hnc0xws+jdehqits...@mail.gmail.com
Bug#754200: kde-baseapps-bin: KDE fails to recognize keyboard backlight capabilities on fresh boot
Package: kde-baseapps-bin
Version: 4:4.12.4-1
Severity: normal
Dear Maintainer,
I'm not sure if this is right package to post the bug to. I had a hard
time figuring out which KDE package contains all the power management
stuff.
When I boot my laptop, an Asus G55VW, I notice my Fn+F3/F4 shortcut keys
are useless within KDE, even though 'xev' correctly identifies the keys:
KeyRelease event, serial 46, synthetic NO, window 0x781,
root 0x289, subw 0x0, time 3638383, (105,55), root:(105,78),
state 0x0, keycode 238 (keysym 0x1008ff05, XF86KbdBrightnessUp),
same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 46, synthetic NO, window 0x781,
root 0x289, subw 0x0, time 3639413, (105,55), root:(105,78),
state 0x0, keycode 237 (keysym 0x1008ff06, XF86KbdBrightnessDown),
same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
However, I've noticed that if I log out and log back in, KDE's power
manager is suddenly aware that the keyboard backlight can be changed and
everything works as expected.
It looks like during the booting process KDE starts sooner than upower
or something like that, but I find that strange because screen
brightness keys work all the time.
Furthermore after booting the first time (KDE unaware of keyboard
brightness) I can change the brightness manual through the command like
either by invoking this command:
dbus-send --type=method_call --print-reply=literal --system \
--dest='org.freedesktop.UPower' \
'/org/freedesktop/UPower/KbdBacklight'\
'org.freedesktop.UPower.KbdBacklight.SetBrightness' \
int32:${value}}
(with ${value}} equal to 0,1,2 or 3)
or as superuser:
echo 1 /sys/class/leds/asus::kbd_backlight/brightness
So the hardware works as expected and the kernel seems to be doing what
is supposed to be doing but KDE's power manager seems unable to register
this during the initial boot sequence.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (900, 'testing'), (200, 'unstable'), (175, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13.11.4-desktop.1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages kde-baseapps-bin depends on:
ii kde-baseapps-data 4:4.12.4-1
ii kde-runtime4:4.13.1-1
ii libc6 2.19-4
ii libkdecore54:4.13.1-1
ii libkdeui5 4:4.13.1-1
ii libkfile4 4:4.13.1-1
ii libkio54:4.13.1-1
ii libkparts4 4:4.13.1-1
ii libqt4-dbus4:4.8.6+dfsg-2
ii libqt4-xml 4:4.8.6+dfsg-2
ii libqtcore4 4:4.8.6+dfsg-2
ii libqtgui4 4:4.8.6+dfsg-2
ii libstdc++6 4.9.0-7
ii libx11-6 2:1.6.2-2
kde-baseapps-bin recommends no packages.
kde-baseapps-bin suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/20140708162743.25076.41770.reportbug@asus-g55vw
