[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#289593: marked as done (usb devices blocking each other)



Your message dated Tue, 20 Mar 2007 20:18:36 +0000
with message-id <2007032020183622@ekaia.org>
and subject line Closed bug 289593 on the Debian BTS
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: KPilot
Version: 4.4.1
I am using a PalmOS device on usb. I am too using a mouse on an other usb connector. I start KPilot. Then I hit the hotsync button on my Palm and my mouse stops functioning. 
When I hit the hotsync button while Kpilot is not yet started the mouse runs. 
The mouse is an optical Microsoft mouse. 
lsusb says:
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 002: ID 05e3:0502 Genesys Logic, Inc. GL620USB GeneLink USB-USB Bridge
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
Bus 001 Device 001: ID 0000:0000

I am using Sarge. 



reportbug is buggy so I have to report this bug this way. 

greetings 

Juergen Katins
________________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt neu bei WEB.DE FreeMail: http://freemail.web.de/?mc=021193



--- End Message ---
--- Begin Message ---
Submitter was asked to provide more information about this bug
( http://bugs.debian.org/289593 ) four weeks ago.

Since more info was not provided, we are closing the bug.
Feel free to reopen this bug if you are still experiencing this issue
and you have extra information on how reproduce the issue.



-- 
Ana,
  on behalf of the Debian Qt/KDE team

--- End Message ---

Reply to: