Summary: | sys-apps/kbd not pulled in, but it's in packages file | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Anton Kuzmin <selecter> |
Component: | Current packages | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Anton Kuzmin
2006-04-16 13:55:05 UTC
Is your XKB working properly? What's the output of `setxkbmap -print`? What version of xkbdata or xkeyboard-config? Please attach xorg.conf and /var/log/Xorg.0.log, then reopen when you've answered the above questions. I've found the problem. emerge xorg-x11 (7.0) didn't include the xkb and xset packages. As I emerged them manually the problem went away. (In reply to comment #2) > I've found the problem. emerge xorg-x11 (7.0) didn't include the xkb and xset > packages. > As I emerged them manually the problem went away. > The xset package shouldn't be required to use ctrl+alt+Fx. What xkb package are you referring to? Need a response, reopen when you reply. emerge kbd kbd is in "system", I'm not sure how you managed to avoid installing it unless you removed it from the "packages" file with a local profile in /etc/portage/. I don't think so. It was not installed. I am sure the package was new when I did emerge -up world after xorg update. Besides, not only me suffer from this bug. I saw some posts on gentoo forum and one on linux.org.ru forum. Seeing that this is an isolated incident I'm pretty sure it was a local screwup (and would be nearly impossible to debug now anyway). |