Pointer missing on login

Bug #1448116 reported by themusicgod1
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

When I login there is no pointer. I unplug my mouse & replug again...pointer appears. Has happened a half dozen times now, but not every time. Might just be when I shut down after using the touchpad (usually I have the touchpad disabled). This laptop has a touchpad and an IBM mouse.

Bus 001 Device 008: ID 04b3:3107 IBM Corp. ThinkPad 800dpi Optical Travel Mouse

root@Hedy:/home/themusicgod1# xinput -list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ ETPS/2 Elantech Touchpad id=13 [slave pointer (2)]
⎜ ↳ HID 04b3:3107 id=15 [slave pointer (2)]
 ...

Has been happening for at least a month, probably longer, but seems like it started some time after October.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Apr 24 08:25:27 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:0689]
   Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0689]
InstallationDate: Installed on 2014-07-09 (288 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708)
MachineType: Acer TravelMate P273-MG
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=885e04f0-bd26-4885-aa1c-f134c674b8ff ro quiet splash nomdmonddf nomdmonisw vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/27/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.11
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: BA70_HC
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd11/27/2013:svnAcer:pnTravelMateP273-MG:pvrV2.11:rvnAcer:rnBA70_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: TravelMate P273-MG
dmi.product.version: V2.11
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1
xserver.bootTime: Fri Apr 24 08:18:10 2015
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 5278
 vendor AUO
xserver.version: 2:1.17.1-0ubuntu3

Revision history for this message
themusicgod1 (themusicgod1) wrote :
Revision history for this message
penalvch (penalvch) wrote :

themusicgod1, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

tags: added: latest-bios-2.11
Changed in xorg (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
themusicgod1 (themusicgod1) wrote :

Because it was an intermittent problem it's unclear that I could tag one way or another whether it's fixed. I have began with 4.1.0-040100rc1 -- I cannot reproduce so far, I will continue down the list, though to see if I can reproduce with one of the earlier kernels, too.

Revision history for this message
themusicgod1 (themusicgod1) wrote :

v3.19.2-vivid could reproduce
v3.19.1-vivid could not reproduce
v3.19-vivid could not reproduce
v3.19-rc7-vivid could not reproduce
v3.19-rc6-vivid could not reproduce
v3.19-rc5-vivid could reproduce
v3.19-rc4-vivid could not reproduce
v3.19-rc3-vivid could not reproduce
v3.19-rc2-vivid could not reproduce
v3.19-rc1-vivid could not reproduce
3.19.0-15-generic could not reproduce
3.19.0-14-generic could not reproduce
3.19.0-13-generic could not reproduce
3.19.0-12-generic could not reproduce
3.19.0-11-generic could reproduce
3.19.0-10-generic could not reproduce
3.19.0-9-generic could not reproduce
3.19.0-7-generic could not reproduce
3.19.0-5-generic reported

tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-3.19.2
Revision history for this message
themusicgod1 (themusicgod1) wrote :

v3.19.4-vivid could reproduce
v3.19.3-vivid could not reproduce

tags: added: kernel-bug-exists-upstream-3.19.4
Revision history for this message
penalvch (penalvch) wrote :

themusicgod1, could you please test the latest mainline kernel (4.1-rc1) and advise to the results?

tags: removed: kernel-bug-exists-upstream-3.19.2 kernel-bug-exists-upstream-3.19.4
Revision history for this message
themusicgod1 (themusicgod1) wrote :

could not reproduce on 4.1-rc1

penalvch (penalvch)
description: updated
tags: added: kernel-fixed-upstream kernel-fixed-upstream-4.1-rc1 needs-reverse-bisect
removed: kernel-bug-exists-upstream
affects: xorg (Ubuntu) → linux (Ubuntu)
Revision history for this message
themusicgod1 (themusicgod1) wrote :

I'm not convinced that 4.1-rc1 doesn't exhibit issue, given that it's intermittent (happens ~18% of the time?). Was able to reproduce on 4.0.0-040000rc1 though.

v4.0-rc1-vivid could reproduce
v3.19.6-vivid could not reproduce
v3.19.5-vivid could not reproduce

Revision history for this message
themusicgod1 (themusicgod1) wrote :

Aha. Reproduced on 4.1-rc1

tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.1-rc1
removed: kernel-fixed-upstream kernel-fixed-upstream-4.1-rc1
Revision history for this message
penalvch (penalvch) wrote :

themusicgod1, did this problem not occur in a release prior to Vivid?

tags: removed: needs-reverse-bisect
Revision history for this message
themusicgod1 (themusicgod1) wrote :

I had different hardware, then: different video card, motherboard/cpu/bios -- I think I upgraded hardware around September....I might not have restarted enough to have noticed it until October.

Changed in linux (Ubuntu):
status: Incomplete → New
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
themusicgod1 (themusicgod1) wrote :

Upgrade to wily kicked me over to xfce(?) ...this hasn't happened since I've started using xfce4/its greeter. :. it's probably closer related to lightdm than linux.

Revision history for this message
themusicgod1 (themusicgod1) wrote :

( xfce4's greeter is lightdm, on wily that would be lightdrm 1.15.0-0ubuntu1 )

Revision history for this message
themusicgod1 (themusicgod1) wrote :

Pretty sure this hasn't happened since I upgraded to wily.

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.