I’m using a “Logitech MX Master 3S” mouse with the “Solaara” application for mouse support. However, I’m encountering a login issue on the Fedora KDE login page. After entering my credentials, the screen goes dark, and then the login page reappears. Interestingly, if I unplug the “Bolt Receiver,” I can log in to my desktop without any problems. Once logged in, I can plug the “Bolt Receiver” back in, and the mouse works fine. Additionally, the Solaara application detects the mouse correctly. Any assistance in resolving this issue would be appreciated.
We do need more information:
inxi -Fzxxplease past it as pre formated text ( see</>in editor menu)- Are you using some sort of device in between dongle and computer (like docking station etc ?
- Is the dongle up do date with the firmware?
- Is this issue new? Just after an update/upgrade?
- As you tagged it with x11 did you test Wayland?
Hello,
The detailed information is as follows:
sudo inxi -Fzxx
Output: (Using X11)
System:
Kernel: 6.10.10-100.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.40-14.fc39
Console: pty pts/2 wm: kwin_x11 DM: SDDM Distro: Fedora Linux 39 (KDE
Plasma)
Machine:
Type: Laptop System: LENOVO product: 82WQ v: Legion Pro 7 16IRX8H
serial: <filter> Chassis: type: 10 v: Legion Pro 7 16IRX8H serial: <filter>
Mobo: LENOVO model: LNVNB161216 v: SDK0T76461 WIN serial: <filter>
part-nu: LENOVO_MT_82WQ_BU_idea_FM_Legion Pro 7 16IRX8H UEFI: LENOVO
v: KWCN46WW date: 07/04/2024
Battery:
ID-1: BAT0 charge: 79.0 Wh (77.0%) condition: 102.6/99.9 Wh (102.7%)
volts: 16.4 min: 15.5 model: SMP L22M4PC1 serial: <filter>
status: not charging
CPU:
Info: 24-core (8-mt/16-st) model: 13th Gen Intel Core i9-13900HX bits: 64
type: MST AMCP arch: Raptor Lake rev: 1 cache: L1: 2.1 MiB L2: 32 MiB
L3: 36 MiB
Speed (MHz): avg: 837 high: 1370 min/max: 800/2200:1600 cores: 1: 800
2: 800 3: 1200 4: 1006 5: 808 6: 1370 7: 800 8: 800 9: 800 10: 800 11: 800
12: 800 13: 800 14: 800 15: 800 16: 800 17: 800 18: 800 19: 800 20: 800
21: 800 22: 800 23: 800 24: 800 25: 800 26: 800 27: 800 28: 800 29: 800
30: 800 31: 800 32: 800 bogomips: 154828
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel Raptor Lake-S UHD Graphics vendor: Lenovo driver: i915
v: kernel arch: Gen-13 ports: active: eDP-1 empty: none bus-ID: 00:02.0
chip-ID: 8086:a788
Device-2: NVIDIA AD104M [GeForce RTX 4080 Max-Q / Mobile] vendor: Lenovo
driver: nvidia v: 560.35.03 arch: Lovelace pcie: speed: 16 GT/s lanes: 16
ports: active: none empty: DP-1, DP-2, DP-3, HDMI-A-1, eDP-2
bus-ID: 01:00.0 chip-ID: 10de:27e0
Device-3: Luxvisions Innotech Integrated Camera driver: uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-11:4 chip-ID: 30c9:00ac
Display: server: X.Org v: 1.20.14 with: Xwayland v: 23.2.7
compositor: kwin_x11 driver: X: loaded: modesetting,nvidia
unloaded: fbdev,nouveau,vesa alternate: nv dri: iris gpu: i915
display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1600 s-dpi: 96
Monitor-1: eDP-1 model-id: CSO 0x1628 res: 2560x1600 dpi: 189
diag: 406mm (16")
API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 1 drv: iris
device: 3 drv: swrast surfaceless: drv: nvidia x11: drv: iris
inactive: gbm,wayland,device-2
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 23.3.6 glx-v: 1.4
direct-render: yes renderer: Mesa Intel Graphics (RPL-S)
device-ID: 8086:a788
API: Vulkan v: 1.3.275 surfaces: xcb,xlib device: 0 type: integrated-gpu
driver: N/A device-ID: 8086:a788 device: 1 type: discrete-gpu driver: N/A
device-ID: 10de:27e0 device: 2 type: cpu driver: N/A device-ID: 10005:0000
Audio:
Device-1: Intel Raptor Lake High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:7a50
Device-2: NVIDIA AD104 High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:22bc
API: ALSA v: k6.10.10-100.fc39.x86_64 status: kernel-api
Server-1: PipeWire v: 1.0.7 status: n/a (root, process) with:
1: pipewire-pulse status: active 2: wireplumber status: active
3: pipewire-alsa type: plugin 4: pw-jack type: plugin
Network:
Device-1: Intel Raptor Lake-S PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:7a70
IF: wlp0s20f3 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Lenovo driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
port: 4000 bus-ID: 76:00.0 chip-ID: 10ec:8168
IF: enp118s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 bus-ID: 1-14:5 chip-ID: 8087:0033
Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 5.3
lmp-v: 12
Drives:
Local Storage: total: 1.84 TiB used: 404.98 GiB (21.5%)
ID-1: /dev/nvme0n1 vendor: Samsung model: MZVL21T0HCLR-00BL2
size: 953.87 GiB speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 45.9 C
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 990 PRO 1TB size: 931.51 GiB
speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 35.9 C
Partition:
ID-1: / size: 124.93 GiB used: 76.27 GiB (61.0%) fs: ext4
dev: /dev/nvme0n1p5
ID-2: /boot/efi size: 511 MiB used: 19 MiB (3.7%) fs: vfat
dev: /dev/nvme0n1p4
Swap:
ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p6
ID-2: swap-2 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 43.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB available: 31.08 GiB used: 2.93 GiB (9.4%)
igpu: 60 MiB
Processes: 524 Power: uptime: 2h 47m wakeups: 0 Init: systemd v: 254
target: graphical (5) default: graphical
Packages: pm: flatpak pkgs: 43 Compilers: gcc: 13.3.1 Shell: Sudo
v: 1.9.15p5 running-in: konsole inxi: 3.3.34
Output: (Using Wayland)
System:
Kernel: 6.10.10-100.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.40-14.fc39
Console: pty pts/2 wm: kwin_wayland DM: SDDM Distro: Fedora Linux 39 (KDE
Plasma)
Machine:
Type: Laptop System: LENOVO product: 82WQ v: Legion Pro 7 16IRX8H
serial: <filter> Chassis: type: 10 v: Legion Pro 7 16IRX8H serial: <filter>
Mobo: LENOVO model: LNVNB161216 v: SDK0T76461 WIN serial: <filter>
part-nu: LENOVO_MT_82WQ_BU_idea_FM_Legion Pro 7 16IRX8H UEFI: LENOVO
v: KWCN46WW date: 07/04/2024
Battery:
ID-1: BAT0 charge: 79.0 Wh (77.0%) condition: 102.6/99.9 Wh (102.7%)
volts: 16.4 min: 15.5 model: SMP L22M4PC1 serial: <filter>
status: not charging
CPU:
Info: 24-core (8-mt/16-st) model: 13th Gen Intel Core i9-13900HX bits: 64
type: MST AMCP arch: Raptor Lake rev: 1 cache: L1: 2.1 MiB L2: 32 MiB
L3: 36 MiB
Speed (MHz): avg: 796 high: 800 min/max: 800/2200:1600 cores: 1: 800
2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 700
12: 800 13: 800 14: 800 15: 800 16: 800 17: 800 18: 800 19: 800 20: 800
21: 800 22: 800 23: 800 24: 800 25: 800 26: 800 27: 800 28: 800 29: 800
30: 800 31: 800 32: 800 bogomips: 154828
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel Raptor Lake-S UHD Graphics vendor: Lenovo driver: i915
v: kernel arch: Gen-13 ports: active: eDP-1 empty: none bus-ID: 00:02.0
chip-ID: 8086:a788
Device-2: NVIDIA AD104M [GeForce RTX 4080 Max-Q / Mobile] vendor: Lenovo
driver: nvidia v: 560.35.03 arch: Lovelace pcie: speed: 16 GT/s lanes: 16
ports: active: none empty: DP-1, DP-2, DP-3, HDMI-A-1, eDP-2
bus-ID: 01:00.0 chip-ID: 10de:27e0
Device-3: Luxvisions Innotech Integrated Camera driver: uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-11:4 chip-ID: 30c9:00ac
Display: server: X.Org v: 23.2.7 with: Xwayland v: 23.2.7
compositor: kwin_wayland driver: X: loaded: modesetting,nvidia
unloaded: fbdev,nouveau,vesa alternate: nv dri: iris gpu: i915
display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1600 s-dpi: 96
Monitor-1: eDP-1 model-id: CSO 0x1628 res: 2560x1600 dpi: 191
diag: 406mm (16")
API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 1 drv: iris
device: 3 drv: swrast surfaceless: drv: nvidia x11: drv: iris
inactive: gbm,wayland,device-2
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 23.3.6 glx-v: 1.4
direct-render: yes renderer: Mesa Intel Graphics (RPL-S)
device-ID: 8086:a788
API: Vulkan v: 1.3.275 surfaces: xcb,xlib device: 0 type: integrated-gpu
driver: N/A device-ID: 8086:a788 device: 1 type: discrete-gpu driver: N/A
device-ID: 10de:27e0 device: 2 type: cpu driver: N/A device-ID: 10005:0000
Audio:
Device-1: Intel Raptor Lake High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:7a50
Device-2: NVIDIA AD104 High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:22bc
API: ALSA v: k6.10.10-100.fc39.x86_64 status: kernel-api
Server-1: PipeWire v: 1.0.7 status: n/a (root, process) with:
1: pipewire-pulse status: active 2: wireplumber status: active
3: pipewire-alsa type: plugin 4: pw-jack type: plugin
Network:
Device-1: Intel Raptor Lake-S PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:7a70
IF: wlp0s20f3 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Lenovo driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
port: 4000 bus-ID: 76:00.0 chip-ID: 10ec:8168
IF: enp118s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 bus-ID: 1-14:5 chip-ID: 8087:0033
Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 5.3
lmp-v: 12
Drives:
Local Storage: total: 1.84 TiB used: 404.98 GiB (21.5%)
ID-1: /dev/nvme0n1 vendor: Samsung model: MZVL21T0HCLR-00BL2
size: 953.87 GiB speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 46.9 C
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 990 PRO 1TB size: 931.51 GiB
speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 36.9 C
Partition:
ID-1: / size: 124.93 GiB used: 76.27 GiB (61.0%) fs: ext4
dev: /dev/nvme0n1p5
ID-2: /boot/efi size: 511 MiB used: 19 MiB (3.7%) fs: vfat
dev: /dev/nvme0n1p4
Swap:
ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p6
ID-2: swap-2 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 45.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB available: 31.08 GiB used: 4.66 GiB (15.0%)
igpu: 60 MiB
Processes: 524 Power: uptime: 2h 42m wakeups: 0 Init: systemd v: 254
target: graphical (5) default: graphical
Packages: pm: flatpak pkgs: 43 Compilers: gcc: 13.3.1 Shell: Sudo
v: 1.9.15p5 running-in: konsole inxi: 3.3.34
sudo journalctl -u sddm(During X11 session login)
Output:
Sep 20 01:14:16 fedora sddm-helper[22068]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=987) by (uid=0)
Sep 20 01:14:27 fedora sddm-helper[22251]: gkr-pam: unable to locate daemon control file
Sep 20 01:14:27 fedora sddm-helper[22251]: gkr-pam: stashed password to try later in open session
Sep 20 01:14:27 fedora sddm-helper[22251]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Sep 20 01:14:27 fedora sddm-helper[22251]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Sep 20 01:14:28 fedora sddm-helper[22251]: pam_unix(sddm:session): session opened for user rumi(uid=1000) by rumi(uid=0)
Sep 20 01:14:28 fedora sddm-helper[22251]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
Sep 20 01:14:28 fedora sddm-helper[22251]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Sep 20 01:14:28 fedora sddm-helper[22251]: Starting X11 session: "/usr/bin/X -nolisten tcp -background none -seat seat0 -noreset -keeptty -novtswitch -verbose 3" "/etc/X11/xinit/Xsession \"/usr/bin/startplasm>
Sep 20 01:14:31 fedora sddm-helper[22360]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=987) by (uid=0)
Sep 20 01:14:41 fedora sddm-helper[22464]: gkr-pam: unable to locate daemon control file
Sep 20 01:14:41 fedora sddm-helper[22464]: gkr-pam: stashed password to try later in open session
Sep 20 01:14:41 fedora sddm-helper[22464]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Sep 20 01:14:41 fedora sddm-helper[22464]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Sep 20 01:14:41 fedora sddm-helper[22464]: pam_unix(sddm:session): session opened for user rumi(uid=1000) by rumi(uid=0)
Sep 20 01:14:41 fedora sddm-helper[22464]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
Sep 20 01:14:41 fedora sddm-helper[22464]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Sep 20 01:14:41 fedora sddm-helper[22464]: Starting X11 session: "/usr/bin/X -nolisten tcp -background none -seat seat0 -noreset -keeptty -novtswitch -verbose 3" "/etc/X11/xinit/Xsession \"/usr/bin/startplasm>
sudo fwupdtool get-updates
Output:
Loading… [******************* ]19:26:22.354 FuEngine failed to add device /sys/devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.3/0003:046D:C548.000D/hidraw/hidraw7: failed to fetch the number of pairing slots: failed to send: failed to write: wrote -1 of 7
Loading… [************************************** ]
Devices with no available firmware updates:
• ELAN06FA:00 04F3:327E
• BIOS1
• Bolt Receiver
• Integrated Camera
• MX Master 3S
• MZVL21T0HCLR-00BL2
• Radio
• Radio
• SSD 990 PRO 1TB
• System Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• USB4 host controller
Devices with the latest available firmware version:
• UEFI dbx
No updates available for remaining devices
- I recently purchased the mouse, and the issue has been present since the beginning.
- The issue only occurs when using an X11 session and doesn’t persist in a Wayland session. However, I’m hesitant to use Wayland with an NVIDIA GPU since this is my work laptop, and it feels risky.
Best regards.
I do somehow understand you. Just your problem you face is exactly what will happen soon wit several newer equipment. Devs are recusing to touch x11 and will focus on wayland, because they recognize it as the new standard.
In your case it would make sense, to use wayland and report your Issues you still have with it to find there a solution. This way you are actively supporting the development and will also be able in future to use Fedora KDE without pain. Do not forget to check the Internet alias other distros working already with wayland to find a suitable solution also to integrate in Fedora.
On the manjaro site I could find a comment that the logi bolt just works after booting, what reflects your case.
If you want to test more, there is also the Arch page i found very usefull:
Logitech Unifying Receiver - ArchWiki
The Logitech Unifying Receiver is a wireless receiver using 2.4 GHz band radio communication that can connect up to six compatible wireless mice and keyboards to your computer. The same applies to the newer Logi Bolt wireless technology that comes with newer devices.
1 Like
Thank you so much for your thoughtful input! I really appreciate the suggestion, and you’re absolutely right—Wayland is definitely the way forward. I’ve already switched from X11 to Wayland, and I’m happy to report that it has resolved the issue I was experiencing with the Logitech MX Master 3S and the Bolt receiver. Everything has been running smoothly since the switch, and I’m glad I made the change. I’ve also started using the “Solaar” application, and it’s working well so far. Thanks again for the insight—fingers crossed everything continues to run smoothly from here! Best regards.
1 Like