Bug 169980 - Mouse freeze in X11 and disappears in console
Summary: Mouse freeze in X11 and disappears in console
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 4
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
URL:
Whiteboard:
: 169982 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-10-06 03:48 UTC by Uno Engborg
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-11-21 18:21:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Uno Engborg 2005-10-06 03:48:15 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; sv-SE; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7

Description of problem:
When running X11 the mouse freezes a couple of times a day. If I switch to console using ctrl-alt-F1, the block curor is gone in the console too.

Restarting the X server will not get the mouse back in working condition.
The only way to get it back seam to be to reboot.

Version-Release number of selected component (if applicable):
kernel-2.6.13-1526_FC4

How reproducible:
Sometimes

Steps to Reproduce:
1.Happens intermittenly while using X11.
2.
3.
  

Additional info:

Comment 1 Uno Engborg 2005-10-06 03:51:16 UTC
I should have mentioned that I have
a Matrox G450 graphics card, and I am using
the mga driver and xorg-x11 version 6.8.2-37.FC4.49.2

Comment 2 Dave Jones 2005-10-06 07:38:08 UTC
*** Bug 169982 has been marked as a duplicate of this bug. ***

Comment 3 Dave Jones 2005-11-10 19:48:57 UTC
2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.

Thank you.


Comment 4 Uno Engborg 2005-11-21 18:05:06 UTC
Seam to be working now. I haven't been experiencing the problems for a while.


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