Hi,
I installed piper from Yast2, but it doesn’t start 1st time, but after 2nd try.
1st time it wrote errors to me:
Traceback (most recent call last):
File "/usr/lib/python3.11/site-packages/piper/window.py", line 123, in _on_device_removed
if device is mouse_perspective.device:
^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib64/python3.11/site-packages/gi/_propertyhelper.py", line 207, in __get__
value = self.fget(instance)
^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/piper/mouseperspective.py", line 68, in device
assert self._device is not None
^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError
It seems its related to ratbagd service which does not start when needed.
It seems ratbagctl command is working as intended and it successfully starts the ratbagd service either. After that piper doesn’t make error on first run. After a fresh boot:
norbi@Norbi-PC:~> systemctl status ratbagd
○ ratbagd.service - Daemon to introspect and modify configurable mice
Loaded: loaded (/usr/lib/systemd/system/ratbagd.service; disabled; preset:>
Active: inactive (dead)
norbi@Norbi-PC:~> ratbagctl
hollering-marmot: SteelSeries SteelSeries Rival 300 HP Omen
cheering-viscacha: SteelSeries SteelSeries Rival 300 HP Omen
thundering-gerbil: SteelSeries SteelSeries Rival 300 HP Omen
norbi@Norbi-PC:~> systemctl status ratbagd
● ratbagd.service - Daemon to introspect and modify configurable mice
Loaded: loaded (/usr/lib/systemd/system/ratbagd.service; disabled; preset:>
Active: active (running) since Fri 2024-11-01 15:19:47 CET; 19s ago
Invocation: fa9b6b53d06240b1b338bc436c0cfd83
Main PID: 3373 (ratbagd)
Tasks: 1 (limit: 18912)
CPU: 147ms
CGroup: /system.slice/ratbagd.service
└─3373 /usr/sbin/ratbagd
No. After a fresh reboot, it runs only after 2nd start of piper itself, 1st run results the error that I mentioned in opening post.
After a reboot and starting ratbagd service manually first (systemctl start ratbagd), piper successfully start.
I don’t know those issues are related to each other but piper even does not work after it is running. Maybe it would be an issue with piper itself.
It shows 3 device:
Steelseries Steelseries Rival 300 HP Omen (fw 0.104)
Steelseries Steelseries Rival 300 HP Omen (fw 0.0)
Steelseries Steelseries Rival 300 HP Omen
but neither one seems to work if I try to modify something.
It shows 404 instead of mouse image, sliders even doesn’t work at all, which is basically a dot.
lsusb: Bus 003 Device 003: ID 1038:1718 SteelSeries ApS SteelSeries Rival 300 HP Omen
Can I do something to add this as a supported device or report that piper starting issue to somewhere else?
It’s a HP Omen mouse but a Steelseries 300 in real and it works with the Steelseries managing sw in Windows. Unfortunately coudn’t find a graphical program to manage it easily in Linux.
norbi@Norbi-PC:~> ratbagctl list
hollering-marmot: SteelSeries SteelSeries Rival 300 HP Omen
cheering-viscacha: SteelSeries SteelSeries Rival 300 HP Omen
thundering-gerbil: SteelSeries SteelSeries Rival 300 HP Omen
norbi@Norbi-PC:~> ratbagctl hollering-marmot info
hollering-marmot - SteelSeries SteelSeries Rival 300 HP Omen
Model: usb:1038:1718:0
Device Type: Mouse
Firmware version: 0.104
Number of Buttons: 6
Number of Leds: 2
Number of Profiles: 1
Profile 0: (active)
Name: n/a
Report Rate: 1000Hz
Resolutions:
0: 800dpi (active) (default)
1: 1600dpi
Button: 0 is mapped to 'button 1'
Button: 1 is mapped to 'button 2'
Button: 2 is mapped to 'button 3'
Button: 3 is mapped to 'button 4'
Button: 4 is mapped to 'button 5'
Button: 5 is mapped to 'resolution-cycle-up'
LED: 0, depth: rgb, mode: on, color: 0000ff
LED: 1, depth: rgb, mode: on, color: 0000ff
norbi@Norbi-PC:~> ratbagctl cheering-viscacha info
cheering-viscacha - SteelSeries SteelSeries Rival 300 HP Omen
Model: usb:1038:1718:0
Device Type: Mouse
Number of Buttons: 6
Number of Leds: 2
Number of Profiles: 1
Profile 0: (active)
Name: n/a
Report Rate: 1000Hz
Resolutions:
0: 800dpi (active) (default)
1: 1600dpi
Button: 0 is mapped to 'button 1'
Button: 1 is mapped to 'button 2'
Button: 2 is mapped to 'button 3'
Button: 3 is mapped to 'button 4'
Button: 4 is mapped to 'button 5'
Button: 5 is mapped to 'resolution-cycle-up'
LED: 0, depth: rgb, mode: on, color: 0000ff
LED: 1, depth: rgb, mode: on, color: 0000ff
norbi@Norbi-PC:~> ratbagctl thundering-gerbil info
thundering-gerbil - SteelSeries SteelSeries Rival 300 HP Omen
Model: usb:1038:1718:0
Device Type: Mouse
Number of Buttons: 6
Number of Leds: 2
Number of Profiles: 1
Profile 0: (active)
Name: n/a
Report Rate: 1000Hz
Resolutions:
0: 800dpi (active) (default)
1: 1600dpi
Button: 0 is mapped to 'button 1'
Button: 1 is mapped to 'button 2'
Button: 2 is mapped to 'button 3'
Button: 3 is mapped to 'button 4'
Button: 4 is mapped to 'button 5'
Button: 5 is mapped to 'resolution-cycle-up'
LED: 0, depth: rgb, mode: on, color: 0000ff
LED: 1, depth: rgb, mode: on, color: 0000ff
yeah, I think I have found that kind of issue was already reported:
Maybe it would be a good idea to attach my infos here too.
It seems that kind of issue is common in Linux.
XFCE mouse settings thinks I have 2 mouse devices and 1 keyboard.
Of course it doesn’t have a working sensitivity slider for the mouse, so I had to activate flat acceleration profile by command and use the acceleration slider instead…
