|
Bugzilla – Full Text Bug Listing |
| Summary: | CTRL-ALT-Fx keys do no longer work | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Raymond Wooninck <tittiatcoke> |
| Component: | X.Org | Assignee: | Stefan Dirsch <sndirsch> |
| Status: | RESOLVED FIXED | QA Contact: | Stefan Dirsch <sndirsch> |
| Severity: | Normal | ||
| Priority: | P2 - High | ||
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
/var/log/Xorg.0.log file
X.org configuration |
||
|
Description
Raymond Wooninck
2005-08-20 17:32:13 UTC
Please attach your /var/log/Xorg.0.log and /etc/X11/xorg.conf. Created attachment 46779 [details]
/var/log/Xorg.0.log file
Created attachment 46780 [details]
X.org configuration
> (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap
That's it. This was broken on Beta1 and couldn't be fixed by an update from
Beta1 to Beta2. This shouldn't happen when updating from 9.3 to Beta2. Any
chance to verify this, i.e. install a 9.3 and update to Beta2?
For me it was strange to see that if I would revert back to the Xorg version coming with 9.3 everything would work again. I am updating over the internet and the laptop is busy for quite a long time. Would it be a possibility to revert back just the Xorg package to the 9.3 level and then update the Xorg package to the ones of Beta 2 ?? I have just tried to follow the approach that I described above. I performed the following steps : 1) Return to the Xorg version from SuSE 9.3 => OK 2) Reboot 3) Verify if the CTRL-ALT-Fx switch is working => Yes, it works fine 4) Upgrade to the Xorg version from Beta 2 => OK 5) Reboot 6) Verify if the CTRL-ALT-Fx switch is working => No,same problem. I am however not sure if this approach could solve the problem, but it would be not that easy to revert back to SuSE 9.3 and then perform the upgrade again. Can this problem be solved in a manual way ? Like updating a certain file or setting certain links ? Unfortunately trying to test this manually by replacing packages won't be enough. This needs to be verified by a real update 9.3 --> 10.0 (via YaST). I'll do this ASAP. > This needs to be verified by a real update 9.3 --> 10.0 (via YaST).
> I'll do this ASAP.
done. The problem cannot be reproduced. --> FIXED
|