Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 202322 - xorg-base/xorg-server-1.4.0.90: a part of bug 201047 is unsolved
Summary: xorg-base/xorg-server-1.4.0.90: a part of bug 201047 is unsolved
Status: VERIFIED DUPLICATE of bug 201047
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-14 20:53 UTC by Rafał Mużyło
Modified: 2008-01-11 13:07 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rafał Mużyło 2007-12-14 20:53:47 UTC
As the bug #201047 was closed, part of upstream bug mentioned there (http://bugs.freedesktop.org/show_bug.cgi?id=12523) is still unsolved. Last comment there (14) reports a problem, that I can confirm.
I run startx, it executes ~/.xsession and polish input is unavailable,
well, unless I explicitly call setxkbmap in ~/.xsession.
This probably affects other keymaps, too.
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2007-12-14 20:55:30 UTC

*** This bug has been marked as a duplicate of bug 201047 ***
Comment 2 Rafał Mużyło 2008-01-11 12:25:53 UTC
Hey, I can't reopen 201047, as I was not the orginal reporter.
Well, yes.
I'm using evdev 1.2.0 and hal 0.5.10. I've got correct fdi but even then setxkbmap is needed, cause although keymap is polish, the problem from other bugs happens (the one about arrow keys not working, or they do work but left arrow is not repeated when held.
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2008-01-11 12:54:21 UTC
Why don't you reply on the bug as requested finally?

*** This bug has been marked as a duplicate of bug 201047 ***
Comment 4 Rafał Mużyło 2008-01-11 13:05:03 UTC
Well, I could reply, but couldn't reopen.
Comment 5 Jakub Moc (RETIRED) gentoo-dev 2008-01-11 13:07:49 UTC
(In reply to comment #4)
> Well, I could reply, but couldn't reopen.

I don't see any reply from you there. Please reply on the *original* bugs with the requested info.