Please mark stable on x86: app-misc/logitech-applet-0.4_pre1-r1
Can somebody mark it stable please? It's only a trivial thing. Thanks.
Archs, please mark it stable.
/usr/share/doc/logitech-applet-0.4_pre1-r1/README.gz says, Model Description 400/800 SS CSR M-BP82 "MX300 Optical Mouse" Yes No No I've got that. Bottom of my mouse says so. lsusb, Bus 002 Device 002: ID 046d:c01f Logitech, Inc. unaffiliated ~ # logitech_applet --get-res unaffiliated ~ # nothing happens, I can't get or set resolution to 400 or 800 like it says on README. I've tested it on both, x86 and ~x86. Any insight? Bad luck with usb bus id's?
(Maybe we should move this discusion to the Gentoo forums.) Did you compile your kernel with evdev? And your X.org also? BTW On my mouse there are two small buttons above and below the scroll wheel, and they change the resolution, without the help of logitech-applet. Quite weird.
(In reply to comment #3) > /usr/share/doc/logitech-applet-0.4_pre1-r1/README.gz says, > > Model Description 400/800 SS CSR > M-BP82 "MX300 Optical Mouse" Yes No No > > I've got that. Bottom of my mouse says so. > > lsusb, Bus 002 Device 002: ID 046d:c01f Logitech, Inc. > > unaffiliated ~ # logitech_applet --get-res > unaffiliated ~ # > > nothing happens, I can't get or set resolution to 400 or 800 like it says on > README. I've tested it on both, x86 and ~x86. > > Any insight? Bad luck with usb bus id's? > Weird enought, your mouse have the wrong ID. It should be 0xC024. Anyway, i'll cook up a patch in a moment...
Ok Samuli, just added revison -r2 to CVS so it should hit the mirrors in a couple of hours. Please sync and test it, it should work now. @archs: Please test and mark stable the -r2 version.
tested on amd64 with mx1000 and good to go stable...
(In reply to comment #6) > Ok Samuli, just added revison -r2 to CVS so it should hit the mirrors in a > couple of hours. Please sync and test it, it should work now. > > @archs: > Please test and mark stable the -r2 version. > Now I can read my DPI, but cannot change it. unaffiliated ~ # logitech_applet --set-res 400 002/002 046D/C01F M-BS82 MX300 Optical Mouse unaffiliated ~ # logitech_applet --get-res 002/002 046D/C01F M-BS82 MX300 Optical Mouse Resolution: 800cpi I'm wondering why it says M-BS82 now and M-BP82 in bottom of mouse, and in README. I could guess smthing like "this must be some modified version of MX300." but I won't. Anyway, I can build it -r2 fine and get resolution. My mouse shouldn't be blocking stabilization of -r1 for x86.
strace reveals following: open("/dev/bus/usb/002/001", O_RDWR) = 3 ioctl(3, USBDEVFS_IOCTL, 0xbfa3f4e0) = 3 close(3) = 0 open("/dev/bus/usb/002/002", O_RDWR) = 3 ioctl(3, USBDEVFS_IOCTL, 0xbfa3f4e0) = -1 ENOTTY (Inappropriate ioctl for device) close(3) = 0 I'll ask upstream about this. This is getting off tracks from original purpose of this bug (IMHO).
(In reply to comment #9) > strace reveals following: > > open("/dev/bus/usb/002/001", O_RDWR) = 3 > ioctl(3, USBDEVFS_IOCTL, 0xbfa3f4e0) = 3 > close(3) = 0 > open("/dev/bus/usb/002/002", O_RDWR) = 3 > ioctl(3, USBDEVFS_IOCTL, 0xbfa3f4e0) = -1 ENOTTY (Inappropriate ioctl for > device) > close(3) = 0 > > I'll ask upstream about this. This is getting off tracks from original purpose > of this bug (IMHO). > Ok, just open a new bug for this please.
OK, so the r2 ebuild has an issue with the MX300 mouse that Samuli Suominen owns. In particular, the "add-new-id-of-mx300.patch" that Carlos Silva created does not have the desired effect at the moment. However, logitech-applet-0.4_pre1-r1.ebuild (which seems to have been deleted!) works perfectly. The original logitech-applet-0.4_pre1.ebuild is stable already, and the only difference is the logitech_applet-mx518.patch. I can comfirm this patch is working properly. So why not add support for mx518 to gentoo stable?
i prefer to clear that other problem and let it go to stable with every problem solved, including that new mx300 version :/
as its now waiting on the fix's please readd us when its again ready to go.
(In reply to comment #12) > i prefer to clear that other problem and let it go to stable with every problem > solved, including that new mx300 version :/ > It would be nice, yes but I don't think it should be blocking -r1 (fix for MX518). I've looked at logitech-applet and tried to change some calls it uses for mice without success (I didn't really know what I was doing.. lol) So unless someone gives me something to try, or way to get more information I'm stuck. - drac
Readding x86 since -r2 was never stabilized and reminding some friendly amd64 dev to stabilize this as I tested it some weeks ago and it works fine ;)
(In reply to comment #15) > Readding x86 since -r2 was never stabilized and reminding some friendly amd64 > dev to stabilize this as I tested it some weeks ago and it works fine ;) amd64 stable. thanks for testing.
OK, thank you all for your time. >2006-05-24 03:43 PST >2006-08-08 15:43 PST I don't mean to offend anybody, and I do appreciate all the work you guys do for gentoo, but it took 2 1/2 months for something quite simple. Maybe the maintainers are very busy and under-staffed? Could I volunteer to help out?
(In reply to comment #17) > OK, thank you all for your time. > > >2006-05-24 03:43 PST > >2006-08-08 15:43 PST > > I don't mean to offend anybody, and I do appreciate all the work you guys do > for gentoo, but it took 2 1/2 months for something quite simple. Maybe the > maintainers are very busy and under-staffed? Could I volunteer to help out? > If you look at the replies there has been work going on with this bug, It hasn't just been sitting here for 2.5 months with nothing going on. There was a problem with some logitech mice that the maintainer wanted to take care of before marking it stable... If however you are sincere about helping out there's the archtester program for various arches and then there's also becoming a developer, to do the latter you'd need to find a current dev to mentor you though.
x86 is done as well.
