Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 277996 - app-misc/razercfg: New package / ebuild
Summary: app-misc/razercfg: New package / ebuild
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Default Assignee for New Packages
URL: http://bu3sch.de/joomla/index.php/raz...
Whiteboard:
Keywords: EBUILD
Depends on:
Blocks:
 
Reported: 2009-07-15 23:14 UTC by Allen Brooker (AllenJB)
Modified: 2013-04-26 19:43 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
razercfg-0.04.ebuild (razercfg-0.04.ebuild,705 bytes, text/plain)
2009-07-15 23:15 UTC, Allen Brooker (AllenJB)
Details
razercfg-0.05.ebuild (razercfg-0.05.ebuild,705 bytes, text/plain)
2009-07-15 23:15 UTC, Allen Brooker (AllenJB)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Allen Brooker (AllenJB) 2009-07-15 23:14:51 UTC
razercfg is a tool for advanced configuration of several Razer branded mice.

I'm uploading ebuilds for both 0.04 and 0.05 because 0.05 segfaults for me on amd64. Neither has been tested on any other arch.

These packages can also currently be found in my overlay:
https://trax.allenjb.me.uk/overlay
Comment 1 Allen Brooker (AllenJB) 2009-07-15 23:15:27 UTC
Created attachment 198112 [details]
razercfg-0.04.ebuild
Comment 2 Allen Brooker (AllenJB) 2009-07-15 23:15:51 UTC
Created attachment 198114 [details]
razercfg-0.05.ebuild
Comment 3 Allen Brooker (AllenJB) 2009-07-15 23:26:19 UTC
Just a quick note that both packages are exactly the same, except for KEYWORDS. Probably didn't need to bother uploading both, but it's late here =P
Comment 4 jon R-B 2009-07-15 23:29:56 UTC
compiles and runs fine on my amd64 setup so maybe the keywork -amd64 could be removed for ~amd64

mind you the actualy application (qrazercfg) is of no use to me atm since I have a Razer Copperhead and that device isn't supported yet
Comment 5 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2009-07-16 06:12:57 UTC
Just for the record, this package is currently no replacement for app-misc/razertool...
Comment 6 Steev Klimaszewski (RETIRED) gentoo-dev 2010-04-06 04:27:55 UTC
Does razertool support both the Death Adder (1800) and the Lachesis?  If not, I'd probably be willing to look at maintaining this.  I've got one of each of those, but I still don't know how some things come together, I'm still reading through the code.... and then there is the whole qtpython portion of it, that i can't/won't test as I do not install qt.
Comment 7 Bernard Cafarelli gentoo-dev 2010-04-06 11:45:01 UTC
razertool mostly is for the Copperhead (which is the one I have) AFAIR.

If 0.0.6 works for you Steev, it may be worth bringing this package in tree then :)
Comment 8 Christian Birchinger (RETIRED) gentoo-dev 2010-07-18 12:36:34 UTC
0.0.6 (or recent git) still segfaults here on amd64. I even tried to debug some of it but it makes absolutely no sense.

-[hw_deathadder.c:664]-----------------------------------------------
        printf("udev->bus->dirname: \"%s\"\n", udev->bus->dirname);
        
        snprintf(devid, sizeof(devid), "%04X-%04X-%s",
                 udev->descriptor.idVendor,              
                 udev->descriptor.idProduct, serial);    
        
        razer_create_idstr(buf, BUSTYPESTR_USB, "002",
                           DEVTYPESTR_MOUSE, "DeathAdder", devid);
---------------------------------------------------------------------

Razer device service daemon
udev->bus->dirname: "002"
Segmentation fault

It has the correct string ("002") but still segfaults when accessing it.
Once the printf is removed the hard coded "002" const char works fine.
What's really weird is, the 002 needs to be a "const char" and using a
normal char fails later on again.

Also, it worked in the past when i forced to build a 32bit binary with -m32
but that's no longer possible (latest git version).

I think it's currently to problematic to have it amd64 keyworded at all.

I've contacted upstream about a year ago and he couldn't find a solution.
So anyone who can reproduce the issue and fix it, please contact upstream
with a patch.
Comment 9 Wolfram Schlich (RETIRED) gentoo-dev 2013-04-26 19:43:09 UTC
joker@gentoo.org is actively maintaining it since 2011.