Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 149686 - app-misc/logitech-applet has stoped working after upgrading to libusb-0.1.12
Summary: app-misc/logitech-applet has stoped working after upgrading to libusb-0.1.12
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Carlos Silva (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-30 23:59 UTC by Anton Bolshakov
Modified: 2006-10-09 21:44 UTC (History)
2 users (show)

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


Attachments
emerge --info is here. (emerge_info,2.65 KB, text/plain)
2006-10-01 00:01 UTC, Anton Bolshakov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Anton Bolshakov 2006-09-30 23:59:26 UTC
I have updated to dev-libs/libusb-0.1.12 recently and my
logitech_applet stoped working. Recompiling logitech-applet didn't help.
I have downgraded back to libusb-0.1.11  and it sovled the problem.
Comment 1 Anton Bolshakov 2006-10-01 00:01:03 UTC
Created attachment 98499 [details]
emerge --info is here.
Comment 2 Jakub Moc (RETIRED) gentoo-dev 2006-10-01 00:09:10 UTC
Would be really useful to explain what "stopped working" exactly means...
Comment 3 Anton Bolshakov 2006-10-01 00:25:11 UTC
Sorry.
Normally if you run it without any parameters it will display some info about mouse: resolution, cruise control, etc.
It displays nothing with the new library without any crash.
"logitech_applet -h" still works and displays help.

ant ~ # gdb logitech_applet
GNU gdb 6.4
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".

(gdb) r
Starting program: /usr/sbin/logitech_applet
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

Program exited normally.
(gdb)  
Comment 4 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2006-10-03 21:27:38 UTC
logitech-applet works here with libusb-0.12, but logitech-applet has always given the wrong output compared to lmctl/lomoco - now if I could just find something to interface with the keyboard, I'd be very happy.

root@newton-int:/tmp # logitech_applet 
001/003     046D/C50B  	967300-0403 	Cordless MX Duo Receiver
   Channel 1    Battery: 7    Single channel   No 800cpi support   No Horiz Roller   No Vert Roller   3 butt.
root@newton-int:/tmp # lomoco -i
001.003: 046d:c50b Receiver for Cordless Desktop MX (C-BK16A-DUAL) Caps: CSR SMS 
	Receiver type: C50B
	Mouse type: MX700 Cordless Optical Mouse (2ch)
	Connect button on mouse pressed: yes
	Active RF Channel: 1
	Battery status: 5 (good)
	Cordless security ID: 0x0000
	Receiver talking: yes
	Lock Request (CONNECT button pressed): no
	Mouse Powerup (First time out of the box auto-locking): no
	Receiver Unlocked (Mouse disconnected): no
	Wait Lock (Searching for mouse): no
	SmartScroll (SMS): reporting not supported
	USB Mouse Polling Interval:  10ms

Comment 5 Anton Bolshakov 2006-10-09 21:44:26 UTC
I found what cases the problem.
It's an additional UDEV script(you need it then hot-plug the mouse).
I took it from http://gentoo-wiki.com/UDEV:

SYSFS{manufacturer}=="Logitech", SYSFS{product}=="USB-PS/2 Optical Mouse", NAME="input/%k", MODE="0644", RUN+="/usr/bin/logitech_applet -s 800"

it seems like a permission problem to me.
Somehow it was working fine with the previous version of libusb.

The bug is closed and marked as 'invalid'.

Sorry for trouble.