Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 116608
| Summary: | Latest kernel rpms cause X crash due to PS/2 mouse driver not working | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mark Bidewell <kbidewe> |
| Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
| Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-02-21 19:01:34 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Yea ... probably another duplicate to bug # 116118 *** This bug has been marked as a duplicate of 116118 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040217 Description of problem: Latest kernel rpms cause X crash due to PS/2 apparently mouse driver not working. This problem exists in all kernels since 2.6.1-1.65. Version-Release number of selected component (if applicable): rpm-2.6.3-1.91 How reproducible: Always Steps to Reproduce: 1. Load latest kernel 2. Attempt to load X 3. Actual Results: X server crashed stating that /dev/psaux could not be opened Expected Results: X should load Additional info: This appears to be an rpm configuration bug. I am using FC1 with a 2.6.3 kernel compiled from www.kernel.org source and it does not exhibit this behavior.