Bug 896355 - Mouse clicks stop responding in Anaconda installer
Summary: Mouse clicks stop responding in Anaconda installer
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11
Version: 19
Hardware: x86_64
OS: Linux
urgent
high
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-17 05:53 UTC by Mike
Modified: 2015-02-17 14:40 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-17 14:40:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
syslog from install of FC18 (153.16 KB, application/octet-stream)
2013-01-19 03:28 UTC, Mike
no flags Details
syslog from FC18 install (128.63 KB, application/octet-stream)
2013-01-19 03:36 UTC, Mike
no flags Details
X.log from FC18 install (40.74 KB, text/x-log)
2013-01-19 03:36 UTC, Mike
no flags Details

Description Mike 2013-01-17 05:53:16 UTC
Description of problem:
During anaconda setup my mouse clicks (left-click) stops responding after the first menu item; time setup.

Version-Release number of selected component (if applicable):


How reproducible:
Anytime I try to install Fedora 18 (the problem actually occurred in F17 as well) anaconda stop responding to my mouse clicks.


Steps to Reproduce:
1. Attempt to install Fedora 18 (or F17)
2. After configuring time in Anaconda, the anaconda installer no longer responds to mouse clicks. The mouse does still move; it just doesn't respond to left or right mouse clicks.
3.
  
Actual results:
Mouse clicks stop responding.

Expected results:
I would expect the mouse to function properly.


Additional info:
I have tried 2 USB mice. I originally used my default, Logitech MX518, and I pulled out a USB Dell branded laser mouse. The problem occurred with each mouse. I have also tried different USB ports on my computer.

Comment 1 Chris Lumens 2013-01-18 15:28:41 UTC
Hm, I've not seen this before.  Can you try to switch to tty2 and grab /tmp/X.log and /tmp/syslog?  Additionally, are there any relevant messages on tty1?

Comment 2 Mike 2013-01-19 03:28:15 UTC
Created attachment 682878 [details]
syslog from install of FC18

Comment 3 Mike 2013-01-19 03:36:34 UTC
Created attachment 682879 [details]
syslog from FC18 install

Comment 4 Mike 2013-01-19 03:36:59 UTC
Created attachment 682880 [details]
X.log from FC18 install

Comment 5 Mike 2013-01-19 03:40:28 UTC
So, in grabbing those files for you, and looking at the output from tty1, I found something new, in regards to this issue.

After going to those different tty's, and then coming back to the graphical install (anaconda) at tty6, my mouse buttons are working.

Steps to Reproduce:
1. Attempt to install Fedora 18 (or F17)
2. After configuring time in Anaconda, the anaconda installer no longer responds to mouse clicks. The mouse does still move; it just doesn't respond to left or right mouse clicks.

Steps to Remediate (if mouse clicks stop responding):
1. Switch to a different terminal, tty1 or tty2 tested.
2. Come back to the graphical installer at tty6
3. Mouse button clicks will now work/respond.

Comment 6 Joshua Rosen 2013-06-14 21:34:11 UTC
I'm seeing a simliar problem in the Fedora 19 Beta installer, mouse clicks don't work. I was able to install F19 on a laptop and a netbook but not on a desktop system. The mouse moves but I can't select anything with it. I tried two different monitors, a 27" 2560x1440 and an old 1280x1024 20" monitor. They both exhibited the same problem. The installer is completely unusable on this system.

This is an 32G Ivy Bridge system with a Gigabyte motherboard. 


00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1c.5 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c4)
00:1c.6 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 7 (rev c4)
00:1c.7 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 8 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Z77 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GF108 High Definition Audio Controller (rev a1)
03:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller (rev 11)
04:00.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 41)
05:01.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev c0)
06:00.0 Ethernet controller: Atheros Communications Inc. AR8151 v2.0 Gigabit Ethernet (rev c0)
07:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller (rev 11)

Comment 7 Joshua Rosen 2013-06-15 18:16:05 UTC
This seems to be a problems with Logitech wireless devices. My wireless mouse was unusable during the installation, I had to remove the wireless adapter and switch to a wired mouse. I also ran into problems with a wireless keyboard which stopped functioning during the installation. I works fine on the installed F19 system but not during installation. I also had to replace the keyboard with a wired keyboard to do the install.

Comment 8 Mike 2013-06-16 19:43:25 UTC
It's still occurring with my wired devices. Keyboard and mouse, both wired.

Comment 9 Fedora End Of Life 2015-01-09 17:35:15 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 10 Fedora End Of Life 2015-02-17 14:40:48 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.