Created attachment 111622 [details] Rapid mouse state changes Dragging icons or widgets on the desktop causes the mouse to alternate rapidly between normal and disabled. The attached picture shows the behavior. The same exact behavior happens in panels when dragging widgets. Every other pixel the mouse switches between the "drag" icon and the "disabled" icon. The behavior happens on the Desktop and on Panels for folders and widgets, but does *not* happen in Dolphin. I'm running Plasma 5.12.3 in KDE Neon on a Microsoft Surface Pro 4. I have HiDPI scaling=2.0 and PLASMA_USE_QT_SCALING=true set. The problem also happens with PLASMA_USE_QT_SCALING=false. (I'm not sure if it happens if HiDPI scaling is disabled entirely).
maybe related/dupicate bug 391548
These seem to be different bugs. I don't get the problem I mentioned when dragging from Dolphin to the desktop, only when: 1. dragging from the desktop to itself 2. dragging a widget to the desktop 3. dragging a widget to the panel The thing I'm talking about is really the rapid flip-flopping of "drag" and "disabled" mouse states.
Disabled mouse state appears only once - when starting dragging desktop icon very slowly in: Plasma: 5.12.3 Apps: 17.12.3 Frameworks: 5.44.0 Qt: 5.10.1 Kernel: 4.14.27-1-MANJARO OS: Netrunner Rolling
Strange. A few questions: 1) What DPI setting are you using? 2) Do you get the problem if you drag and drop a new widget onto the desktop? 3) Do you get a problem if you drag and drop a new widget onto a panel?
Created attachment 111737 [details] mouse-cursor-when-dragging-desktop-icon 1) Tried without scaling and with 1.2 scaling 2) Yes attaching video with demonstration
I got this bug too, it feels like some pixels are valid drop locations and some others are not. Usually it's possible to find a "valid" pixel and complete the drag'n'drop by moving the mouse very slowly and try to drop when the cursor shows as a valid spot. I say "feels" because I haven't found a way to see if it's really given pixels, or if it just randomly changes when moving the mouse. I see it happening also in the pulseaudio applet, when draging an application to a sound output. Running Plasma 5.12.5 on Arch.
I got more infos: I did a fresh Manjaro KDE install, and the problem started to happen after installing the nvidia proprietary driver. My gpu is a GTX1080.
More infos again: I checked a few distros (Manjaro, Kubuntu & OpenSUSE TW), it happened only on Arch based ones.
Alexander Mentyu: can you try with 2.0 scaling? llamatron2212@gmail.com: well, at least it's confirmed for some distros. I have it for Neon, haven't tried with the others. Kind of surprised it isn't on Kubuntu for you - I'll be testing that later.
Confirming this bug is here in Plasma 5.13 as well on Neon (Trusty).
OK, some more details. I also have this bug on another laptop which doesn't have HiDPI support, so it doesn't seem to be related to that. However, the common situation in both cases is that I'm using this on a touchpad. I wonder if this is a touchpad issue specifically, rather than a mouse?
(In reply to battaglia01 from comment #11) > OK, some more details. I also have this bug on another laptop which doesn't > have HiDPI support, so it doesn't seem to be related to that. > > However, the common situation in both cases is that I'm using this on a > touchpad. I wonder if this is a touchpad issue specifically, rather than a > mouse? I have this issue with a mouse
Cannot reproduce in Plasma 5.21 with either a touchpad or a mouse. Can you re-check? Thanks!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!