Bug 33193

Hi
I have already packaged Razergenie, together with openrazer. 
I have been using it with a Razer Basilisk V3 X hyperspeed for a while.
It is available in the MLO repo for testing.
I propose to add them to Cauldron and to MGA9 Backport. It would not hurt anything to add it to MGA9 Core Updates right away, but I know this topic is sensitive.

CC: (none) => chb0
Assignee: pkg-bugs => chb0

Great.

Adding MGA9TOO for backport (at least, i too think it could do in update to be more easily found)

I added a note in our mentioned forum thread to this bug asking for testing.

Whiteboard: (none) => MGA9TOO

Ready for testing for MGA9, in Core/Backports_testing.
I face an issue to import it into Cauldron. I will take care of that later.

I just installed razergenie from backports_testing and it appears to work. Not sure how clean the installation was because of some detritus sitting around from previous experimentation, but it did install and work.

The notes say to enable razerd, but my system does not find razerd. Is there a naming problem?

# systemctl status razerd
Unit razerd.service could not be found.

I have seen references to "openrazer-daemon"

May 17 13:49:23 linux6core systemd[12178]: Starting openrazer-daemon.service...
May 17 13:49:23 linux6core openrazer-daemon[2138584]: Starting daemon.
May 17 13:49:23 linux6core dbus-daemon[12195]: [session uid=1001 pid=12195] Successfully activated service 'org.razer'



inxi info for my system.

$ inxi -b
System:
  Host: linux6core Kernel: 6.6.28-desktop-1.mga9 arch: x86_64 bits: 64
    Desktop: KDE Plasma v: 5.27.10 Distro: Mageia 9
Machine:
  Type: Desktop Mobo: Micro-Star model: MPG Z490 GAMING EDGE WIFI (MS-7C79)
    v: 1.0 serial: <superuser required> UEFI: American Megatrends v: 1.C0
    date: 06/10/2022
CPU:
  Info: 6-core 11th Gen Intel Core i5-11400 [MT MCP] speed (MHz): avg: 800
    min/max: 800/4400
Graphics:
  Device-1: Intel RocketLake-S GT1 [UHD Graphics 730] driver: i915 v: kernel
  Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X:
    loaded: modesetting,v4l dri: iris gpu: i915 resolution: 1: 1920x1080~60Hz
    2: 1920x1080~60Hz
  API: OpenGL v: 4.6 Mesa 24.0.5 renderer: Mesa Intel Graphics (RKL GT1)
Network:
  Device-1: Intel Comet Lake PCH CNVi WiFi driver: iwlwifi
  Device-2: Realtek RTL8125 2.5GbE driver: r8169
Drives:
  Local Storage: total: 954.81 GiB used: 52.9 GiB (5.5%)
Info:
  Processes: 320 Uptime: 7h 32m Memory: 31.2 GiB used: 3.11 GiB (10.0%)
  Shell: Bash inxi: 3.3.26

CC: (none) => briankimerer

Thanks Brian

(In reply to Morgan Leijström from comment #4)
> Packages in core/updates_testing
 I should have written "backport_" - not "updates_"

(In reply to Brian Kimerer from comment #5)
> 
> The notes say to enable razerd, but my system does not find razerd. Is there
> a naming problem?
> 
> # systemctl status razerd
> Unit razerd.service could not be found.
> 
> I have seen references to "openrazer-daemon"
> 
> May 17 13:49:23 linux6core systemd[12178]: Starting
> openrazer-daemon.service...
> May 17 13:49:23 linux6core openrazer-daemon[2138584]: Starting daemon.
> May 17 13:49:23 linux6core dbus-daemon[12195]: [session uid=1001 pid=12195]
> Successfully activated service 'org.razer'
> 
> 

Indeed, the proper command is:
systemctl --user enable --now openrazer-daemon

My bad. I fix that.

Good Christian.

Assign this bug to QA when fixed :)

Keywords: (none) => Backport

(In reply to Morgan Leijström from comment #8)
> Good Christian.
> 
> Assign this bug to QA when fixed :)

 I still need to take care of Cauldron....

I think it is OK to QA test in mga9 but not release until it is in Cauldron and at least briefly tested there too.

Packages in core/backports_testing

__For 64 bit
razergenie-1.1.0-1.mga9
python3-openrazer-3.8.0-1.1.mga9
openrazer-kernel-modules-dkms-3.8.0-1.1.mga9
openrazer-meta-3.8.0-1.1.mga9
openrazer-daemon-3.8.0-1.1.mga9
lib64libopenrazer0-0.2.0-1.mga9
lib64libopenrazer-devel-0.2.0-1.mga9

__For 32 bit
razergenie-1.1.0-1.mga9
python3-openrazer-3.8.0-1.1.mga9
openrazer-kernel-modules-dkms-3.8.0-1.1.mga9
openrazer-meta-3.8.0-1.1.mga9
openrazer-daemon-3.8.0-1.1.mga9
liblibopenrazer-devel-0.2.0-1.mga9
liblibopenrazer0-0.2.0-1.mga9

Ready for Cauldron as well

Status comment: Need to be fixed in Cauldron => (none)
Source RPM: razercfg => razercfgrazergenie-1.1.0-2.mga10.src.rpm,openrazer-meta-3.8.0-2.mga10.src.rpm,libopenrazer-0.2.0-2.squidf.mga10.src.rpm
Assignee: chb0 => qa-bugs

ADVISORY NOTICE PROPOSAL
========================
RazerGenie for configuring your Razer devices


Description
RazerGenie is a Qt application for configuring your Razer devices under GNU/Linux.
RazerGenie uses OpenRazer for providing control over Razer peripherals.

                
References
https://bugs.mageia.org/show_bug.cgi?id=33193
https://github.com/z3ntu/RazerGenie/releases/tag/v1.1.0
https://github.com/openrazer/openrazer/releases/tag/v3.8.0
https://github.com/z3ntu/libopenrazer/releases/tag/v0.2.0


SRPMS
9/core
  libopenrazer-0.2.0-1.mga9.src.rpm
  openrazer-meta-3.8.0-1.1.mga9.src.rpm
  razergenie-1.1.0-1.mga9.src.rpm

    
PACKAGES FOR QA TESTING
=======================
In core/backports_testing

x86_64:
lib64libopenrazer-devel-0.2.0-1.mga9.x86_64.rpm
lib64libopenrazer0-0.2.0-1.mga9.x86_64.rpm
openrazer-daemon-3.8.0-1.1.mga9.noarch.rpm
openrazer-kernel-modules-dkms-3.8.0-1.1.mga9.noarch.rpm
openrazer-meta-3.8.0-1.1.mga9.noarch.rpm
python3-openrazer-3.8.0-1.1.mga9.noarch.rpm
razergenie-1.1.0-1.mga9.x86_64.rpm

i586:
lib64libopenrazer-devel-0.2.0-1.mga9.i586.rpm
lib64libopenrazer0-0.2.0-1.mga9.i586.rpm
openrazer-daemon-3.8.0-1.1.mga9.noarch.rpm
openrazer-kernel-modules-dkms-3.8.0-1.1.mga9.noarch.rpm
openrazer-meta-3.8.0-1.1.mga9.noarch.rpm
python3-openrazer-3.8.0-1.1.mga9.noarch.rpm
razergenie-1.1.0-1.mga9.i586.rpm

(In reply to christian barranco from comment #12)
> Ready for Cauldron as well

Is it done for Cauldron? 

If so, then the appropriate fields (Component, Version, etc.) need to be changed before it can be validated for mga9.

We'll need somebody with a Razer mouse to test with MGA9, as well. We may need to ask outside of QA for that.

CC: (none) => andrewsfarm

I can do some testing. I have the Razer Basilisk V3. I just need to know when it's  ready.

It is ready for testing.

@Thomas, I assumed you wanted me to rewrite Morgan's report to target MGA9.
Just did that.

Version: Cauldron => 9
Component: RPM Packages => Backports
Whiteboard: MGA9TOO => (none)
Source RPM: razercfgrazergenie-1.1.0-2.mga10.src.rpm,openrazer-meta-3.8.0-2.mga10.src.rpm,libopenrazer-0.2.0-2.squidf.mga10.src.rpm => libopenrazer-0.2.0-1.mga9.src.rpm,openrazer-meta-3.8.0-1.1.mga9.src.rpm,razergenie-1.1.0-1.mga9.src.rpm

I tested this on a new Mageia9 installation, and it works.

There was one glitch. When I tried to enable openrazer-daemon it threw an error.

# systemctl --user enable --now openrazer-daemon
Failed to connect to bus: No medium found

I logged out and back in, and the tool ran anyway. But after the logout/login, it did not recognize my mouse. So I rebooted the computer and everything works. It can control the mouse.

Looks good on this end.

Do user need to issue
 # systemctl --user enable --now openrazer-daemon
?

Can it be automated by a postinstall script of that package?

(In reply to Morgan Leijström from comment #18)
> Do user need to issue
>  # systemctl --user enable --now openrazer-daemon
> ?
> 
> Can it be automated by a postinstall script of that package?

I could do it. I remember I got some push back in the past to adjust system settings and the preference was to let the admin deciding.
The thing is that, anyway, the user will have to adjust the system setting by adding him/her to the group plugdev
Just let me know.

@Brian
The command systemctl --user enable --now openrazer-daemon 
needs to be run as a user, not as root. Is it what you have done?
I can't explain why you go such error.

(In reply to christian barranco from comment #19)
> (In reply to Morgan Leijström from comment #18)

> The thing is that, anyway, the user will have to adjust the system setting
> by adding him/her to the group plugdev

OK then IMO dont, no automation is better than half automated.

How do we tell the user to add himself to that group and execute that command?

@Brian
The command systemctl --user enable --now openrazer-daemon 
needs to be run as a user, not as root. Is it what you have done?
I can't explain why you go such error.

I ran the command as root.

(In reply to Morgan Leijström from comment #20)
> (In reply to christian barranco from comment #19)
> > (In reply to Morgan Leijström from comment #18)
> 
> > The thing is that, anyway, the user will have to adjust the system setting
> > by adding him/her to the group plugdev
> 
> OK then IMO dont, no automation is better than half automated.
> 
> How do we tell the user to add himself to that group and execute that
> command?

urpmi.readme

Just for grins, I tried the enable command again as myself instead of root, and there was no error.

$ systemctl --user enable --now openrazer-daemon
Created symlink /home/brian/.config/systemd/user/default.target.wants/openrazer-daemon.service → /usr/lib/systemd/user/openrazer-daemon.service.

So it works as advertised when used properly.

(In reply to Brian Kimerer from comment #23)
> So it works as advertised when used properly.

Validating the backport then.
I see earlier you tested on 64 bit, I assume this is the same.

It would be good to have some test on Cauldron too anyway if possible.

Whiteboard: (none) => MGA9-64-OK
Keywords: (none) => validated_backport

Yes. I tested it on the 64 bit.

Validated backport, please let message when is moved and I send mail to backport-announce

The RPMs have been moved to backports.

CC: (none) => dan
Status: NEW => ASSIGNED

Announce Published

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