Bug 30388 - solaar bug fixes in 1.1.3
Summary: solaar bug fixes in 1.1.3
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA8-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2022-05-05 20:37 CEST by christian barranco
Modified: 2022-05-08 10:01 CEST (History)
4 users (show)

See Also:
Source RPM: solaar-1.1.2-1.mga8.src.rpm
CVE:
Status comment:


Attachments

Description christian barranco 2022-05-05 20:37:23 CEST
Upstream released version 1.1.3 on April 25th, fixing many bugs: 

https://github.com/pwr-Solaar/Solaar/releases/tag/1.1.3

This new version is already available for Cauldron. I propose to push it for MGA8 as well.
Comment 1 christian barranco 2022-05-05 21:11:38 CEST
Hi
Package is now ready for QA in Testing


ADVISORY NOTICE PROPOSAL
========================

Updated solaar package fixes bugs and adds some more features.



Description
1.1.3 fixes numerous bugs and adds some more features.

*Update documentation files
*Lower remove python 3.7 constructs and lower python dependency to 3.6
*Fix bug in xtest mouse scrolling
*Allow mouse gesture setting for non-mice, e.g., trackballs
*Print message when there is another Solaar process running
*Fix determination of whether to force read before writing boolean setting
*Add recent diversion features to default list in rules UI
*Add setting to divert hires scroll wheel
*Don't use device kind to determine how to handle notifications
*Update Polish, Russian, and zh_CN translations
*Remove pggettext so as to not require Python 3.8
*Remove Python 2 unicode support
*Store keys in configuration file as int instead of str
*Use yaml for configuration file instead of json.
*Remove process-dependent rules from built-in rules.
*Handle situation where GTK application cannot be set up in CLI.
*Remove obsolete upower signals.
*Appinfo/metadata fixes including using correct APP_ID.
*Fix bugs in solaar config.
*Add full set of mouse buttons in persistent remappable actions setting.
*Improve rule behaviour under Wayland and when Xtest or X11 not available.
*Fix up and document dependencies (evdev, Python, ...)

References
https://bugs.mageia.org/show_bug.cgi?id=30388
https://github.com/pwr-Solaar/Solaar/releases/tag/1.1.3

SRPMS
8/core
solaar-1.1.3-1.mga8.src.rpm


PROVIDED PACKAGE (for QA)
=========================
solaar-1.1.3-1.mga8.noarch.rpm

Assignee: chb0 => qa-bugs
CC: (none) => sysadmin-bugs

Comment 2 Rolf Pedersen 2022-05-05 21:28:56 CEST
Howdy.  I installed this from distrib-coffee, closed running solaar-1.1.2-1.mga8, then opened solaar-1.1.3-1.mga8.
K360 keyboard and M510v2 mouse along with the unifying receiver appear in the gui and all seems to work as before on up-to-date plasma.
Thanks.

CC: (none) => rolfpedersen

Comment 3 christian barranco 2022-05-06 10:19:46 CEST
Ok on Plasma x86_64, MX Keys keyboard and MX vertical mouse; both RF and BT.
Comment 4 Thomas Andrews 2022-05-07 15:15:44 CEST
mga8-64 Plasma. No installation issues. closed running solaar and opened the update. No changes in reporting of devices. Put a battery in a spare mouse, it was detected and battery level reported. Unpaired the mouse successfully, then paired it again.

OKing and validating. Advisory in Comment 1.

Keywords: (none) => validated_update
Whiteboard: (none) => MGA8-64-OK
CC: (none) => andrewsfarm

Dave Hodgins 2022-05-08 02:06:58 CEST

Keywords: (none) => advisory
CC: (none) => davidwhodgins

Comment 5 Mageia Robot 2022-05-08 10:01:12 CEST
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2022-0066.html

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


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