Results 1 to 6 of 6

Thread: Logitech Anywhere MX problem

  1. #1
    Join Date
    Jan 2013
    Beans
    18

    Logitech Anywhere MX problem

    Hi.

    I have a wireless mouse from Logitech (Anywhere MX) that connects to the PC using the Logitech Unifying Receiver (USB dongle).

    Every time I restart the laptop I need to remove the receiver and plug in it again to the mouse start working.
    After that it works great, but it would be better if it could work without having to plug off\plug in every time the laptop starts.

    Anyone have the same problem?
    Any ideas?

    Thanks in advance

  2. #2
    Join Date
    Jan 2013
    Beans
    18

    Re: Logitech Anywhere MX problem

    Anyone?

  3. #3
    Join Date
    May 2007
    Beans
    12,428

    Re: Logitech Anywhere MX problem

    Sorry, but I think you're stuck doing that.

    I have a multi-port USB hub that I have several things connected to because my laptop only has two USB ports -- and I have to unplug and replug the USB hub every time.
    Ubuntu 14.04, Mint 17; MS Win 8.1.
    Will not respond to PM requests for support -- use the forums.

  4. #4
    Join Date
    Jan 2013
    Beans
    18

    Re: Logitech Anywhere MX problem

    Hi Mark.

    I've found this bug report in the launchpad:
    https://bugs.launchpad.net/ubuntu/+s...x/+bug/1006145

    It seems to be a common problem.
    It's odd it exists since Ubuntu 12.04 and still is active in the latest kernels of 13.04.

    I'm with kernel 3.8.0-4.

  5. #5
    Join Date
    Feb 2013
    Beans
    1

    Re: Logitech Anywhere MX problem

    My temporary suggestion would be to see if you know someone with an older receiver (who does not use linux) and see if that person is willing to swap, even just to test it out.

    --------------------------------------------

    Using an OLD unifying receiver, my mice (yes, I tried 2) and keyboard work just fine in Ubuntu; however if using a new receiver they do not. The reason I have both is that I lost my old MX Anywhere mouse (the old model), but still have the receiver from it.

    Upon plugging the old or new unifying receivers into my laptop, I get the following:
    Bus 003 Device 006: ID 046d:c52b Logitech, Inc. Unifying Receiver

    If I plug both in, I get this:
    Bus 003 Device 006: ID 046d:c52b Logitech, Inc. Unifying Receiver
    Bus 003 Device 007: ID 046d:c52b Logitech, Inc. Unifying Receiver

    That gives me the impression that both are being detected.

    --------------------------------------------

    Here is what I have tried on a Windows machine using the Unifying software:

    1. Remove all pairings from both devices
    2. Added any combination of 1, 2 or 3 devices to ONE receiver at a time.
    3. Tried that receiver in the Linux laptop.

    --------------------------------------------

    • With the OLD receiver, depending on how many devices are paired, the command "ls /dev/hidraw*" displays at least hidraw0 and hidraw1
    • With the NEW receiver, no matter how many devices are paired simultaneously, no /dev/hidraw entries appear.
    • If I pair the devices with the new receiver, while the laptop is on and plug them in, they (sometimes) work until I reboot the machine again at which time the connection is lost.
    • If I paired 1 or 2 devices on one receiver and the remaining on the other, only devices that were paired with the OLD receiver appear as entries in /dev/hidraw*
    • "ls -l /dev | wc -l" shows 217 entries when the old receiver is plugged in. If I plug in the NEW receiver that number does not change. Unplugging the OLD receiver, reduces the number of items in /dev, but adding the NEW receiver does not even if the old receiver is not connected.

    --------------------------------------------

    I suspect something might have changed in the receiver itself that is causing this, but that is my impression at this point.
    Last edited by massacgr; February 18th, 2013 at 04:48 AM.

  6. #6
    Join Date
    Oct 2007
    Beans
    3

    Re: Logitech Anywhere MX problem

    The discussion in the bug report noted above has a workaround solution effective for some users.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •