Bug 30315 - After power management pause, mouse loses left+right = middle click setting (Plasma)
Summary: After power management pause, mouse loses left+right = middle click setting (...
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-21 14:56 CEST by Pierre Fortin
Modified: 2022-05-13 19:30 CEST (History)
0 users

See Also:
Source RPM: Plasma
CVE:
Status comment:


Attachments

Description Pierre Fortin 2022-04-21 14:56:34 CEST
Description of problem:  After Power Management kicks in, I lose the ability to use left+right mouse buttons for middle click. I need this because newer mice are too touchy -- it's more difficult to middle click with the wheel without the scrolling just as the wheel is depressed.  
This may be related to a change that also caused bug 30303; both issues started about the same time.

Version-Release number of selected component (if applicable):


How reproducible: happens overnight vs while trying to test.  So not sure how long I have to wait to trigger the issue.


Steps to Reproduce:
1. System Settings>Input Devices>Mouse>[x]Press left and right buttons for middle-click
2. Power Management shuts down screens
3. move mouse or hit a key to restore screens
4. turn off setting, Apply, turn on setting, Apply to restore left+right
Comment 1 Lewis Smith 2022-04-21 21:27:46 CEST
Thank you for the report.
I guess this is another Plasma affair. (Please always say what desktop is involved in things like this).

For both of these bugs, I have to ask whether you have explored the KDE forums to see whether the problem is seen elsewhere.

If another Bugsquad person has a system on which the complaint can be verified (with power management), please do. I cannot.

CC: (none) => kde, lewyssmith
Summary: Mouse loses left+right = middle click setting => After power management pause, mouse loses left+right = middle click setting (Plasma)
Source RPM: (none) => Plasma

Comment 2 Pierre Fortin 2022-04-21 22:25:41 CEST
Sorry.  I thought default Cauldron install would cover the info.

Operating System: Mageia 9
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.2
Kernel Version: 5.17.3-server-2.mga9 (64-bit)
Graphics Platform: X11
Processors: 20 × 12th Gen Intel® Core™ i7-12700K
Memory: 62.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6600 XT

I don't have much time to go on a search expedition; is there a resource that tells us where to report each product/package?  I've tended to report here, thinking Mageia should be aware of issues in Cauldron before releasing as the next version (9 now).

If I report bugs to LO, KDE, etc; is there a recommended method to inform Mageia?  Maybe we need a "Info" bug report classification to inform where to track/follow an external bug...

Ah! Does the above "X11" imply I'm not running Wayland?  For the most part, I install default.  However, I hope to test other desktops in the coming days.
Comment 3 Lewis Smith 2022-04-22 08:40:26 CEST
Thanks for the extra information.
> Does the above "X11" imply I'm not running Wayland?
Just so. Only Gnome uses Wayland by default; you have to manipulate Plasma to do so, and that is experimental.

> If I report bugs to LO, KDE, etc; is there a recommended method to
> inform Mageia?
The normal way is to put the URL of the upstream bug report in the Mageia bug 'URL' field, and UPSTREAM in the keyword field (which we normally do).
I agree we could have say a Wiki for upstream forums & bug reporting URLs. Many bug reporters do research their problem there first.

I failed to note that this bug was for Cauldron; so it merits going straight to the KDE team.

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=30303
Assignee: bugsquad => kde
CC: kde, lewyssmith => (none)

Comment 4 Pierre Fortin 2022-05-13 19:30:56 CEST
Something must've changed.  Not currently seeing this issue. Closing for now.

Resolution: (none) => WORKSFORME
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.