Bug 2395103 - Unifying receiver not listed/accessible on reboot; unplug/replug resolves
Summary: Unifying receiver not listed/accessible on reboot; unplug/replug resolves
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: solaar
Version: 43
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Dominik 'Rathann' Mierzejewski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-09-15 00:31 UTC by Jeremy Nickurak
Modified: 2025-10-07 20:23 UTC (History)
5 users (show)

Fixed In Version: solaar-1.1.14-13.fc44 solaar-1.1.14-13.fc43
Clone Of:
Environment:
Last Closed: 2025-10-07 08:09:35 UTC
Type: ---
Embargoed:
carl: mirror+


Attachments (Terms of Use)
Screenshot of solaar listing no detected receivers after a reboot (33.41 KB, image/png)
2025-09-15 00:32 UTC, Jeremy Nickurak
no flags Details
Screenshot of solaar listing a detected receiver and keyboard/mouse after unplugging/replugging receiver (186.97 KB, image/png)
2025-09-15 00:34 UTC, Jeremy Nickurak
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-2453 0 None None None 2025-10-07 03:57:28 UTC

Description Jeremy Nickurak 2025-09-15 00:31:31 UTC
Since upgrading to Fedora 43, Solaar doesn't detect any unifying receivers after a reboot. Unplugging the receiver and re-attaching it after boot is completed restores it to full functionality.

Reproducible: Always

Steps to Reproduce:
1. Reboot
2. Run solaar
3. Observe solaar not listing any receivers (although connected devices, in my case a logitech k400, still work, although without settings like fn-lock configuration) (see screenshot)
4. Unplug unifying receiver, re-plug in
5. Observe unifying receiver is detected (see screenshot)

Comment 1 Jeremy Nickurak 2025-09-15 00:32:29 UTC
Created attachment 2106659 [details]
Screenshot of solaar listing no detected receivers after a reboot

Comment 2 Jeremy Nickurak 2025-09-15 00:34:00 UTC
Created attachment 2106660 [details]
Screenshot of solaar listing a detected receiver and keyboard/mouse after unplugging/replugging receiver

Comment 3 Jeremy Nickurak 2025-09-15 00:39:00 UTC
This worked fine in Fedora 42. In case it's relevant, here's the technical details solaar yields for my reciever once it is detected after applying the unplug/replug workaround:

Path         : /dev/hidraw0
USB ID       : 046d:C52B
Serial       : 0F7E9EA1
  0          : 12.10.B0032
  1          : 02.14
  3          : AA.AA
Notifications: wireless
               software present

Comment 4 Brad Smith 2025-09-17 20:42:05 UTC
I had the same experience with solaar and F43 - I did a reboot and did not have any mouse available. Solaar is apparently running but no icon displays in Gnome task bar and no apparent access to the UI. If I manually run solaar I see a message that solaar is already running and the UI will appear.

Comment 5 Brad Smith 2025-09-18 14:39:45 UTC
Update 18 Sept. Morning reboot on F43 Workstation beta - no problems with Solaar and mouse.

Comment 6 Carl George 🎩 2025-10-07 03:06:34 UTC
https://src.fedoraproject.org/rpms/solaar/pull-request/8

Comment 7 Fedora Update System 2025-10-07 08:05:14 UTC
FEDORA-2025-3d2d508d18 (solaar-1.1.14-13.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-3d2d508d18

Comment 8 Fedora Update System 2025-10-07 08:09:35 UTC
FEDORA-2025-3d2d508d18 (solaar-1.1.14-13.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2025-10-07 10:57:50 UTC
FEDORA-2025-a3e7b98080 (solaar-1.1.14-13.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-a3e7b98080

Comment 10 Fedora Update System 2025-10-07 13:55:12 UTC
FEDORA-2025-a3e7b98080 (solaar-1.1.14-13.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.


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