https://bugs.kde.org/show_bug.cgi?id=526294
--- Comment #2 from Bob English <[email protected]> --- (In reply to TraceyC from comment #1) > Thanks for the bug report. We need to narrow this down to what might be a > problem in KDE code. Most of the behavior you describe was happening in the > Solaar application, which would need to be reported to the folks maintaining > that. > > We don't have any magic, unfortunately. What we need is a concise, clear > description of the current problem. A screen recording would help a lot. Well, I did some extra deep digging, and I had to even remove the receiver, re-install and use Solaar to re-detect it, then pair both the mouse, and the keyboard separately by force within system (not Solaar) config files, since Solaar's detection didn't work, and it also then found them to have good batteries and the warnings stopped. Sorry, But I just got it done, and had a medical episode and spent a few weeks in hospital, and still recovering, and so forgot all about it! Before that, I did manage to uninstalled Solar, went to my bug report on their Git page, reported the fix, and tore into them for all of that not working...: Let's just say they are no KDE by far! Bug reports go ignored for weeks... no effort to make it more user friendly and add needed controls to the UI... The bug reporting process itself is like a 15 step operation, needing to grep stuff... with a large wiki documentation that never gets into the details needed when it doesn't work! Thanks to the Arch Wiki for pointing out some vital clues! :>) -- You are receiving this mail because: You are watching all bug changes.
