045e:0745 [Samsung NP350E5C-A02AU] Wireless Mouse not recognized after reboot

Bug #1311923 reported by slumbergod
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Low
Unassigned

Bug Description

When I reboot the laptop, my Microsoft Wireless Mobile Mouse 1000 stops working.

WORKAROUND: Unplug and replug wireless transmitter from the USB port.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-generic 3.13.0.24.29
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: slumbergod 2098 F.... pulseaudio
Date: Thu Apr 24 11:21:48 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-04-18 (5 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140414)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 350V5C/351V5C/3540VC/3440VC
ProcEnviron:
 LANGUAGE=en_NZ:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=7ef0aef5-c4f9-45fb-b729-95b463a492d6 ro quiet splash acpi_backlight=vendor vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P09ABE
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NP350E5C-A02AU
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: BOARD REVISION 00
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP09ABE:bd07/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn350V5C/351V5C/3540VC/3440VC:pvrP09ABE.012.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350E5C-A02AU:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 350V5C/351V5C/3540VC/3440VC
dmi.product.version: P09ABE.012.CP
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
slumbergod (slumbergod) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: Wireless Mouse not recognized after reboot

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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/v3.15-rc2-trusty/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
slumbergod (slumbergod) wrote :

Tested with upstream kernel 3.15.0 r2 and the problem has not been resolved.

Revision history for this message
slumbergod (slumbergod) wrote :

Is it ok for me to change the status of the bug to confirmed if I was the reporter of the bug in the first place?
Is this only affecting me? If someone else is using a wireless mouse and you aren't experiencing this problem can you please tell me what mouse you are using.

penalvch (penalvch)
tags: added: needs-full-computer-model
summary: - Wireless Mouse not recognized after reboot
+ 045e:0745 Wireless Mouse not recognized after reboot
description: updated
Changed in linux (Ubuntu):
importance: Medium → Low
Revision history for this message
slumbergod (slumbergod) wrote : Re: [Bug 1311923] Re: Wireless Mouse not recognized after reboot
Download full text (7.1 KiB)

Hi,

the sticker on the underside shows the same as on the box:
NP350E5C-A02AU

On 27 April 2014 10:25, Christopher M. Penalver <
<email address hidden>> wrote:

> slumbergod, could you please provide the full computer model as noted on
> the sticker?
>
> ** Tags added: needs-full-computer-model
>
> ** Summary changed:
>
> - Wireless Mouse not recognized after reboot
> + 045e:0745 Wireless Mouse not recognized after reboot
>
> ** Description changed:
>
> - When I reboot the laptop, the previously-working wireless mouse is not
> working.
> - I have to unplug the wireless transmitter from the USB port and plug it
> in again for it to start working again.
> + When I reboot the laptop, my Microsoft Wireless Mobile Mouse 1000 stops
> + working.
>
> - I tried upstream image 3.14 and the same behaviour was present.
> -
> - I am using a Microsoft Wireless Mobile Mouse 1000. I realise that
> - Microsoft make no claims that it will work under linux but it was
> - working fine in previous versions of ubuntu. I've also spotted a few
> - reports that the Logitech M185 mouse - which does list linux 2.6+ as a
> - supported operating system - might be also affected.
> + WORKAROUND: Unplug and replug wireless transmitter from the USB port.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 14.04
> Package: linux-generic 3.13.0.24.29
> ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
> Uname: Linux 3.13.0-24-generic x86_64
> ApportVersion: 2.14.1-0ubuntu3
> Architecture: amd64
> AudioDevicesInUse:
> - USER PID ACCESS COMMAND
> - /dev/snd/controlC0: slumbergod 2098 F.... pulseaudio
> + USER PID ACCESS COMMAND
> + /dev/snd/controlC0: slumbergod 2098 F.... pulseaudio
> Date: Thu Apr 24 11:21:48 2014
> EcryptfsInUse: Yes
> InstallationDate: Installed on 2014-04-18 (5 days ago)
> InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64
> (20140414)
> MachineType: SAMSUNG ELECTRONICS CO., LTD. 350V5C/351V5C/3540VC/3440VC
> ProcEnviron:
> - LANGUAGE=en_NZ:en
> - TERM=xterm
> - PATH=(custom, no user)
> - LANG=en_NZ.UTF-8
> - SHELL=/bin/bash
> + LANGUAGE=en_NZ:en
> + TERM=xterm
> + PATH=(custom, no user)
> + LANG=en_NZ.UTF-8
> + SHELL=/bin/bash
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed
> root=UUID=7ef0aef5-c4f9-45fb-b729-95b463a492d6 ro quiet splash
> acpi_backlight=vendor vt.handoff=7
> PulseList:
> - Error: command ['pacmd', 'list'] failed with exit code 1: Home
> directory not accessible: Permission denied
> - No PulseAudio daemon running, or not running as session daemon.
> + Error: command ['pacmd', 'list'] failed with exit code 1: Home
> directory not accessible: Permission denied
> + No PulseAudio daemon running, or not running as session daemon.
> RelatedPackageVersions:
> - linux-restricted-modules-3.13.0-24-generic N/A
> - linux-backports-modules-3.13.0-24-generic N/A
> - linux-firmware 1.127
> + linux-restricted-modules-3.13.0-24-generic N/A
> + linux-backports-modules-3.13.0-24-generic N/A
> + linux-firmware 1.127
> SourcePackage: linux
> ...

Read more...

Revision history for this message
penalvch (penalvch) wrote :

slumbergod, did this problem not occur in a release prior to Trusty?

tags: added: latest-bios-p09abe
removed: needs-full-computer-model
summary: - 045e:0745 Wireless Mouse not recognized after reboot
+ 045e:0745 [Samsung NP350E5C-A02AU] Wireless Mouse not recognized after
+ reboot
Changed in linux (Ubuntu):
importance: Low → Medium
importance: Medium → Low
Revision history for this message
slumbergod (slumbergod) wrote : Re: [Bug 1311923] Re: 045e:0745 Wireless Mouse not recognized after reboot
Download full text (4.6 KiB)

Hi,

I did not use 13.10. When I installed 13.10 I found it to be very buggy on
my laptop and I was getting tired of doing clean installs every six months
so I went back to 12.10. 12.10 was a good release for me where everything
worked well on my laptop.

The only reason I did a clean install of 14.04 was because it was a LTS and
I was sure the issues I had with 13.10 would have been worked out. Also,
12.10 was no longer being supported with updates.

So far 14.04 has been quite good. Other than this strange USB mouse problem
the only other issues have been minor xfce4 bugs.

I asked if anyone else was experiencing this problem with USB mice and if
not, what brand of mouse they were using. If I could be sure that it was
only with microsoft mobile 1000 mice I would just go and buy a logitech
replacement.

This issue did not happen with 12.10. It isn't a show stopper because I
leave my laptop on 24/7 so it is only when I reboot that I have to unplug
my mouse transmitter and replug it in. I just hoped that if it was a bug
that affected others reporting it might help it get fixed.

On 28 April 2014 04:03, Christopher M. Penalver <
<email address hidden>> wrote:

> slumbergod, did this problem not occur in a release prior to Trusty?
>
> ** Tags removed: needs-full-computer-model
> ** Tags added: latest-bios-p09abe
>
> ** Summary changed:
>
> - 045e:0745 Wireless Mouse not recognized after reboot
> + 045e:0745 [Samsung NP350E5C-A02AU] Wireless Mouse not recognized after
> reboot
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1311923
>
> Title:
> 045e:0745 [Samsung NP350E5C-A02AU] Wireless Mouse not recognized after
> reboot
>
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> When I reboot the laptop, my Microsoft Wireless Mobile Mouse 1000
> stops working.
>
> WORKAROUND: Unplug and replug wireless transmitter from the USB port.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 14.04
> Package: linux-generic 3.13.0.24.29
> ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
> Uname: Linux 3.13.0-24-generic x86_64
> ApportVersion: 2.14.1-0ubuntu3
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: slumbergod 2098 F.... pulseaudio
> Date: Thu Apr 24 11:21:48 2014
> EcryptfsInUse: Yes
> InstallationDate: Installed on 2014-04-18 (5 days ago)
> InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64
> (20140414)
> MachineType: SAMSUNG ELECTRONICS CO., LTD. 350V5C/351V5C/3540VC/3440VC
> ProcEnviron:
> LANGUAGE=en_NZ:en
> TERM=xterm
> PATH=(custom, no user)
> LANG=en_NZ.UTF-8
> SHELL=/bin/bash
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed
> root=UUID=7ef0aef5-c4f9-45fb-b729-95b463a492d6 ro quiet splash
> acpi_backlight=vendor vt.handoff=7
> PulseList:
> Error: command ['pacmd', 'list'] failed with exit code 1: Home
> directory not accessible: Permission denied
> No PulseAudio daemon running, or not running as session daemon.
> RelatedPackageVersions:
> lin...

Read more...

Revision history for this message
slumbergod (slumbergod) wrote :
Download full text (5.3 KiB)

I guess this could be something unfortunate with Samsung laptops. I also
have to add acpi_backlight=vendor to get the display brightness tools to
work properly:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor"

On 28 April 2014 08:32, David Scott <email address hidden> wrote:

> Hi,
>
> I did not use 13.10. When I installed 13.10 I found it to be very buggy on
> my laptop and I was getting tired of doing clean installs every six months
> so I went back to 12.10. 12.10 was a good release for me where everything
> worked well on my laptop.
>
> The only reason I did a clean install of 14.04 was because it was a LTS
> and I was sure the issues I had with 13.10 would have been worked out.
> Also, 12.10 was no longer being supported with updates.
>
> So far 14.04 has been quite good. Other than this strange USB mouse
> problem the only other issues have been minor xfce4 bugs.
>
> I asked if anyone else was experiencing this problem with USB mice and if
> not, what brand of mouse they were using. If I could be sure that it was
> only with microsoft mobile 1000 mice I would just go and buy a logitech
> replacement.
>
> This issue did not happen with 12.10. It isn't a show stopper because I
> leave my laptop on 24/7 so it is only when I reboot that I have to unplug
> my mouse transmitter and replug it in. I just hoped that if it was a bug
> that affected others reporting it might help it get fixed.
>
>
> On 28 April 2014 04:03, Christopher M. Penalver <
> <email address hidden>> wrote:
>
>> slumbergod, did this problem not occur in a release prior to Trusty?
>>
>> ** Tags removed: needs-full-computer-model
>> ** Tags added: latest-bios-p09abe
>>
>> ** Summary changed:
>>
>> - 045e:0745 Wireless Mouse not recognized after reboot
>> + 045e:0745 [Samsung NP350E5C-A02AU] Wireless Mouse not recognized after
>> reboot
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1311923
>>
>> Title:
>> 045e:0745 [Samsung NP350E5C-A02AU] Wireless Mouse not recognized after
>> reboot
>>
>> Status in “linux” package in Ubuntu:
>> Incomplete
>>
>> Bug description:
>> When I reboot the laptop, my Microsoft Wireless Mobile Mouse 1000
>> stops working.
>>
>> WORKAROUND: Unplug and replug wireless transmitter from the USB port.
>>
>> ProblemType: Bug
>> DistroRelease: Ubuntu 14.04
>> Package: linux-generic 3.13.0.24.29
>> ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
>> Uname: Linux 3.13.0-24-generic x86_64
>> ApportVersion: 2.14.1-0ubuntu3
>> Architecture: amd64
>> AudioDevicesInUse:
>> USER PID ACCESS COMMAND
>> /dev/snd/controlC0: slumbergod 2098 F.... pulseaudio
>> Date: Thu Apr 24 11:21:48 2014
>> EcryptfsInUse: Yes
>> InstallationDate: Installed on 2014-04-18 (5 days ago)
>> InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64
>> (20140414)
>> MachineType: SAMSUNG ELECTRONICS CO., LTD. 350V5C/351V5C/3540VC/3440VC
>> ProcEnviron:
>> LANGUAGE=en_NZ:en
>> TERM=xterm
>> PATH=(custom, no user)
>> LANG=en_NZ.UTF-8
>> SHELL=/bin/bash
>> ProcFB: 0 inteldrmfb
>> ProcKernelCmdL...

Read more...

Revision history for this message
slumbergod (slumbergod) wrote :

After multiple reboots in a row suddenly the mouse was being recognized again. No idea why because I didn't do anything other than try rebooting vs shutdown and restart.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.