RF mouse (with USB dongle) doesn't work after reboot until I unplug it and plug it back in

[Jonathan Kamens]

My wireless mouse doesn't work after I reboot until I unplug its USB dongle and plug it back in.

I don't see anything in Xorg.0.log which obviously explains this problem. It looks like the mouse is added to the X server configuration on startup without any problems, at least unless I'm misreading the log, and then the second time it's added, when I unplug it and plug it back in, it looks like the same thing happens in the log, but then the mouse works.

This was a problem in 17.04 as well, i.e., it isn't new in 17.10.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xserver-xorg-core 2:1.19.5-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus.0000.01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0000:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017
 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
.tmp.unity_support_test.0:

ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 20 18:31:15 2018
DistUpgraded: 2018-01-20 12:11:24,767 ERROR Cache can not be locked (E:Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable), E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?)
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Device [196e:1131]
InstallationDate: Installed on 2016-01-16 (735 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Acer Predator G6-710
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: Upgraded to artful on 2018-01-20 (0 days ago)
dmi.bios.date: 05/18/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A4
dmi.board.name: Predator G6-710
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
dmi.product.family: Acer Desktop
dmi.product.name: Predator G6-710
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sat Jan 20 17:16:47 2018
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.19.5-0ubuntu2

[Daniel van Vugt (vanvugt)]

This sounds like a kernel problem, and at least very likely not caused by Xorg. So reassigning to the kernel.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc9

[Jonathan Kamens (jik)]

I am using the nvidia driver for my graphics card. It sounds like I can't do that with an upstream kernel build? Is that correct? Well my X server automatically use the open-source Nouveau drivers if the nvidia driver isn't in the kernel, or do I need to reconfigure something manually?

And it looks like the virtualbox driver won't build with the upstream kernel header files. Can you advise me on the best way to temporarily disable the virtualbox driver so that it can be reenabled easily and reliably when I'm done doing this testing?

Thanks.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Jonathan Kamens (jik)]

I asked for assistance with the test you asked me to perform back in January. Can you help?

[Jonathan Kamens (jik)]

Please help me with the test you want me to do and I will gladly do it.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Kai-Heng Feng (kaihengfeng)]

I can see
[ 24.500827] hid-generic 0003:1BCF:0535.0005: input,hiddev1,hidraw3: USB HID v1.00 Mouse [2.4GHZ RF ONLY MOUSE] on usb-0000:00:14.0-8/input1

But no error message though...

Can you try Bionic (18.04)?

[Jonathan Kamens (jik)]

1) Just tested bionic, same behavior.

2) I also discovered something new about this issue when I tested this on bionic. I _thought_ I observed this on artful, but I wasn't certain so I didn't mention it, but now I'm certain. Immediately after reboot, when I move the mouse (note I'm using Xorg, not Wayland), the mouse pointer on the screen moves for a fraction of a second and _then_ stops working at until I unplug the dongle and plug it back in again.

[Kai-Heng Feng (kaihengfeng)]

Does the mouse movement work again after you click its button?

[Jonathan Kamens (jik)]

>Does the mouse movement work again after you click its button?

No.

Do you think I am an idiot?

[Kai-Heng Feng (kaihengfeng)]

> On May 8, 2018, at 5:42 PM, Jonathan Kamens <email address hidden>
> wrote:
>
>> Does the mouse movement work again after you click its button?
>
> No.
>
> Do you think I am an idiot?
No. It's quite normal for a runtime suspended USB mouse.

Your attitude is not constructive at all. Please be aware of that.

>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1744510
>
> Title:
> RF mouse (with USB dongle) doesn't work after reboot until I unplug it
> and plug it back in
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> My wireless mouse doesn't work after I reboot until I unplug its USB
> dongle and plug it back in.
>
> I don't see anything in Xorg.0.log which obviously explains this
> problem. It looks like the mouse is added to the X server
> configuration on startup without any problems, at least unless I'm
> misreading the log, and then the second time it's added, when I unplug
> it and plug it back in, it looks like the same thing happens in the
> log, but then the mouse works.
>
> This was a problem in 17.04 as well, i.e., it isn't new in 17.10.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 17.10
> Package: xserver-xorg-core 2:1.19.5-0ubuntu2
> ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
> Uname: Linux 4.13.0-25-generic x86_64
> NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
> .proc.driver.nvidia.gpus.0000.01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0000:01:00.0'
> .proc.driver.nvidia.registry: Binary: ""
> .proc.driver.nvidia.version:
> NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017
> GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
> .tmp.unity_support_test.0:
>
> ApportVersion: 2.20.7-0ubuntu3.7
> Architecture: amd64
> CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
> CompositorRunning: None
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Jan 20 18:31:15 2018
> DistUpgraded: 2018-01-20 12:11:24,767 ERROR Cache can not be locked (E:Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable), E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?)
> DistroCodename: artful
> DistroVariant: ubuntu
> ExtraDebuggingInterest: Yes
> GraphicsCard:
> NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller])
> Subsystem: Device [196e:1131]
> InstallationDate: Installed on 2016-01-16 (735 days ago)
> InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
> MachineType: Acer Predator G6-710
> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
> SourcePackage: xorg-server
> UpgradeStatus: Upgraded to artful on 2018-01-20 (0 days ago)
> dmi.bios.date: 05/18/2016
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: R01-A4
> dmi.board.name: Predator G6-710
> dmi.board.vendor: Acer
> dmi.chassis.typ...