Version: unspecified (using KDE 4.7.1) OS: Linux I tryed ubuntu-armel 10.10, 11.04, 11.10, debian sid-armhf, with clean user profile and clean install. All plasmoids like networkmanager, powermanager, digital clock, etc.. have unclickable buttons\checkboxes. click on them do nothing Reproducible: Always Steps to Reproduce: install kde workspace on any arm machine log on to kde click on any plasmoid in panel try to press button\checkbox in menu Actual Results: nothing happens Expected Results: flags in checkboxes must be set\unset on click, button must be pressable
we know that this works as we do arm builds; not sure what the differences would be, but this does work with a proper build.
(In reply to comment #1) > we know that this works as we do arm builds; not sure what the differences > would be, but this does work with a proper build. and which magick? i tryed vanilla packages on archlinux and problem still at place
I have this problem too on three NVidia Tegra2 based devices (Hannspad, Trimslice, Iconia A500). Plasmoids in the tray icon bar are unusable becase it is impossible to click any button. These plasmoids are e.g. the calendar, plasma-applet-networkmanagement, devices manager. Also the interface for adding widgets is unusable (the panel configuration widget is usable but when I press to "Add widgets..", the next panel is unusable). Other panel elements work fine (the menu, task manager, switch desktop). On problematic plasmoids neither highlighting happens when going over a button, suggesting that it may be a window focusing problem. It is not related to Tegra2 video drivers because the same happens with fbdev. It is not related to touch screen input because Trimslice doesn't have one, it is connected to HDMI display and driven with a mouse. I don't know what to debug to try to fix this bug...thanks for any help.
Is this still valid with KDE 4.8.4 or trunk?
Sorry for the delay, I just tried KDE 4.8.4 on the arm/tegra tablet and unfortunately the problem is still present. If you have any suggestion on how to debug this problem I will take some time to make tests. Thanks.
Thank you for the feedback.
Updated today to KDE 4.9.2, problem still present.
From 4.8.x, 4.9.5 and 4.10 the problem is present here on armv7 pandaboard running Gentoo. It is also present on Ubuntu KDE builds. It works perfect on x86 and amd64 but this makes using KDE as a desktop impossible for me on pandaboard.
I test 4.10.2 on my Asus tf700t (tegra3 device) running on Gentoo Linux, but also encountered this issue.
Same problem also on Samsung Galaxy Note 10.1" with KDE 4.10.4.
odroid-x2 board same problem on: Gentoo, kde-overlay branch 4.11.49.9999, xorg 1.14 same problem on: Ubuntu 13.04
Confirmed on fedora 19/20, see also https://bugzilla.redhat.com/show_bug.cgi?id=969524
Some more observations: [13:54] <ltinkl> I see something similar here as well... expand the hidden section of the tray (the up arrow), and try to click on the apper entry [13:54] <ltinkl> the only possible spot to click onto is the apper icon (and you have to really make sure you don't hit any transparent part) [13:55] <ltinkl> weird thing is that other QML applets (like the device notifier) don't exhibit this bug, they can be clicked anywhere to popup [13:56] <ltinkl> another similar bug, if you click the battery applet and drag the brightness slider around, it changes correctly the brightness [13:56] <ltinkl> howerever, when you're on battery, the popup closes as soon as you drag the slider a bit... quite annoying
See http://mail.kde.org/pipermail/active/2013-November/007228.html and quick-n-dirty workaround: http://goo.gl/ph8OqQ
update summary/version info...
The interesting thing is that everything works fine when I run kubuntu from chroot(crouton project) on my arm chromebook from chromeos. And the same issue when natively. The difference is only in xorg input driver. Chromeos uses xf86-input-cmt. Maybe problem in arm xorg driver?
Hello! This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5. Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham