| Summary: | Touchpad settings are disabled in Wayland | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Bogdan Lashkov <i> |
| Component: | general | Assignee: | Furkan Tokac <furkantokac34> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bugseforuns, matejm98mthw, michal.dybczak, nate, notuxius, pavbaranov, subdiff, tones111 |
| Priority: | NOR | ||
| Version: | 5.13.0 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=395348 | ||
| Latest Commit: | Version Fixed In: | 5.16.0 | |
| Sentry Crash Report: | |||
| Attachments: |
creenshot from the touchpad settings section
kcm on neon dev unstable kcmshell5_kcm_touchpad_bogdan empty kcm in system settings, neon dev unstable |
||
I have the same problem on neon dev unstable. My device is Elantech too. Is this happening sometimes or always? Pls start the KCM from terminal via: kcmshell5 kcm_touchpad and paste the output. In my case "kcmshell5 kcm_touchpad" starts the kcm without any problem. Searching for "touchpad" in kickoff menu also works. Problem occurs only when I access the kcm via system settings. Created attachment 113332 [details]
kcm on neon dev unstable
hum, after my previous comment I installed some updates and now
almost all options are enabled. Only "acceleration profile"
radio buttons are still disabled no matter if kcm is launched via konsole,
kickoff or system settings.
Created attachment 113337 [details]
kcmshell5_kcm_touchpad_bogdan
(In reply to Roman Gilg from comment #2) > Is this happening sometimes or always? Pls start the KCM from terminal via: > > kcmshell5 kcm_touchpad > > and paste the output. Hello! Thnks for your help! Yes, this happens always, when I am starting plasma in wayland. Touchpad settings work through kcmshell5 kcm_touchpad (screenshot is in attachment: https://bugsfiles.kde.org/attachment.cgi?id=113337) But in system settings they are still greyed out. Can you please tell me, how it can be fixed? kcmshell5 kcm_touchpad output: kcm_touchpad: Using KWin+Wayland backend kcm_touchpad: Devices list received successfully from KWin. kcm_touchpad: Touchpad found: "Elan Touchpad" ("event18") Using Wayland-EGL qml: Touchpad configuration of device '1 : Elan Touchpad' opened Using the 'xdg-shell-v6' shell integration Also, as I have noticed in these settings only Tap-and-drag lock trigger is enabled, but not setting for it (e.g. slider with timer for locked drags) > Also, as I have noticed in these settings only Tap-and-drag lock trigger is > enabled, but not setting for it (e.g. slider with timer for locked drags) One issue per bug report please. See https://community.kde.org/Get_Involved/Bug_Reporting#One_issue_per_bug_report Some features aren't available with Libinput. I have different touchpad hardware and its settings on wayland are working correctly. However, mouse settings are completely grayed out. (In reply to Dr. Chapatin from comment #3) > In my case "kcmshell5 kcm_touchpad" starts the kcm without any problem. > Searching for "touchpad" in kickoff menu also works. > Problem occurs only when I access the kcm via system settings. Reproducible Plasma: 5.13.1 Apps: 18.04.2 Frameworks: 5.47.0 Qt: 5.11.1 Kernel: 4.18.0-1-MANJARO OS: Netrunner Rolling Video: Intel 4400 Driver: xf86-video-intel 1:2.99.917+831+ge7bfc906-1 Mesa 3D: 18.1.2 Screen: 1600x900 Xorg: 1.20 Wayland: 1.15.0-1 Wayland Protocols: 1.14-1 kcmshell5 kcm_touchpad kcm_touchpad: Using KWin+Wayland backend kcm_touchpad: Devices list received successfully from KWin. kcm_touchpad: Touchpad found: "Synaptics TM2668-001" ("event14") Using Wayland-EGL qml: Touchpad configuration of device '1 : Synaptics TM2668-001' opened Using the 'xdg-shell-v6' shell integration *** Bug 397056 has been marked as a duplicate of this bug. *** Is this still happening on latest 5.13 release and/or on master? Created attachment 114757 [details]
empty kcm in system settings, neon dev unstable
on neon dev unstable, kcm is empty in system settings.
kcm started via the apps launcher or "kcmshell5 kcm_touchpad"
has "acceleration profile" settings disabled.
It's not empty for me in System Settings. Maybe the issue is that some old renamed libraries have not been removed correctly. Search for files in /usr containing the word "touchpad" in their names. Normally the package manager should clean these up on update though. I can reproduce the disabled acceleration profile setting though. Hi Roman I have just tested neon dev unstable based on ubuntu 18.04 and I can confirm that the kcm is not empty in system settings. Thank you. Phew, thanks for testing! I looked up the acceleration profile options being disabled all the time: apparently these are not supported for touchpads in general. libinput just always uses a specific curve for them: https://wayland.freedesktop.org/libinput/doc/latest/pointer-acceleration.html#pointer-acceleration-on-touchpads So it would make sense to just remove the option in the touchpad KCM all together. We should keep the backend code in place though, because support for custom touchpad acceleration profiles is on the roadmap. *** Bug 398976 has been marked as a duplicate of this bug. *** *** Bug 398976 has been marked as a duplicate of this bug. *** We got another report of this in the 5.14 beta via Bug 398976; re-opening. I'm seeing this issue with systemsettings version 5.14.3. When I try to bring up the touchpad settings I get the following output:
kcm_touchpad: Using KWin+Wayland backend
kcm_touchpad: Devices list received successfully from KWin.
kcm_touchpad: Touchpad found: "SynPS/2 Synaptics TouchPad" ("event14")
qrc:/libinput/main.qml:27:1: "components": no such directory
QObject::connect: Cannot connect (null)::changeSignal() to TouchpadConfigLibInput::onChange()
This seems to imply a qml issue. line 27 of kcms/touchpad/src/kcm/libinput/main.qml is a comment, however, when looking at kcms/mouse/kcm/libinput/main.qml line 27 attempts to import "components". It looks like it's processing the wrong qml file.
There is something strange with it. When I try to use Touchpad settings from systemsettings - all are greyed and any option cannot be changed. When I use kcmshell5 touchpad from konsole - everyting is ok. System: KF 5.54, Plasma 5.14.90, Qt5 5.12 This problem persists. Icon view shows all settings greyed out, sidebar view shows an kcm almost completely empty. We only see "Touchpad" header. Operating System: KDE neon Developer Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 (In reply to Patrick Silva from comment #23) > This problem persists. > Icon view shows all settings greyed out, sidebar view shows an kcm almost > completely empty. We only see "Touchpad" header. > Situation remains the same. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.0 You said earlier in Comment 14 that the KCM would not be empty on this system. Now again? I can't reproduce on my system. (In reply to Roman Gilg from comment #25) > You said earlier in Comment 14 that the KCM would not be empty on this > system. Now again? > > I can't reproduce on my system. Apparently the problem was solved when I wrote comment 14, but it reappeared some time later such comment. I installed neon dev unstable again a few days ago and the problem persists with my main user account. I just created a new user account and I can't reproduce the problem starting plasma with it. However, there is a weird bug with the new user account: touchpad and mouse kcms are almost the same (bug 398228). I can't reproduce this on my system in a wayland session either. I can't reproduce this bug anymore. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.16.80 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.0 Probably fixed by the fix for Bug 398228. |
Created attachment 113302 [details] creenshot from the touchpad settings section Hello! Thanks for fantastic work on KDE Neon, especially on 5.13 version. I have an issue related to touchpad settings, they are disabled in Wayland, but works fine under X-org session. Here is cutting from my device list: I: Bus=0018 Vendor=04f3 Product=0005 Version=0000 N: Name="Elan Touchpad" P: Phys= S: Sysfs=/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-17/i2c-ELAN1000:00/input/input16 U: Uniq= H: Handlers=mouse0 event16 B: PROP=5 B: EV=b B: KEY=e520 10000 0 0 0 0 B: ABS=663800013000003 In attachment there is a screenshot from the touchpad settings section.