Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#2846 - Xorg Xserver keyboard changed

Attached to Project: Arch Linux
Opened by Michel (michel) - Saturday, 18 June 2005, 18:47 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To No-one
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Heya,

I suddenly can't some keys anymore. I tried typing a character, but it isn't displayed anymore. Something changed my Xorg-configuration ... It seemed my original xorg.conf has been overwritten? I check the xorg.conf-file and it seems to be the case.

greetings,

Michel
This task depends upon

Closed by  arjan timmerman (blaasvis)
Monday, 20 June 2005, 08:10 GMT
Reason for closing:  Not a bug
Additional comments about closing:  seems like it is fine in the original package
Comment by Michel (michel) - Saturday, 18 June 2005, 18:50 GMT
Heya,

it seems my xorg.conf-config-file wasn't overwritten, but my keyboard changed some way, although it is still the same config it seems. I compared it with a backup.

greetings,

Michel
Comment by Michel (michel) - Saturday, 18 June 2005, 18:56 GMT
Heya,

I noticed the following:

[root@computerke xkb]# ls -l keymap
ls: keymap/sony: Permission denied
ls: keymap/xfree86: Permission denied
ls: keymap/xfree98: Permission denied

I changed the owner and group back to root ... I'm going to see if it works again.

greetings,

Michel
Comment by Michel (michel) - Saturday, 18 June 2005, 19:01 GMT
Heya again,

it was solved by "chown -R root:root keymap". The characters are shown again.

greetings,

Michel
Comment by Michel (michel) - Sunday, 19 June 2005, 10:11 GMT
Heya,

this problem mayba appeared because of filesystem-corruption or hardware-corruption. I'm not completely sure.

greetings,

Michel

Loading...