1 |
On 2/7/09, Arttu V. <arttuv69@×××××.com> wrote: |
2 |
> Maybe the new xorg-server is only supposed to work reliably on a fully |
3 |
> ~amd64? This box has mostly stable amd64 and only select packages, |
4 |
> mostly end-used apps like seamonkey, OOo and firefox are allowed to be |
5 |
> ~amd64 along with some of their more obscure requirements (like |
6 |
> xulrunner). |
7 |
> |
8 |
> Anyway, thanks for everyone for the helpful comments and ideas! I'll |
9 |
> post a short reply about the success with the downgrade hopefully |
10 |
> tomorrow and then try to leave this for now. |
11 |
|
12 |
After a week of frustrating nightly recompilations with emerge -e |
13 |
failing at various points (gcc-43 not supported for *stable* |
14 |
packages?! o.O [1]) and futile downgrade-attempts not changing the |
15 |
situation, I've finally figured out the culprit for the keyboard |
16 |
trouble: acpid. I had mistakenly added it to default runlevel. (IIRC, |
17 |
due to something hinting to do it with the latest xorg-server.) |
18 |
|
19 |
Anyway, after dropping acpid the keyboard is back again, functioning |
20 |
as expected, ctrl+c copying stuff, cursor keys working (I even lost |
21 |
them at some point), etc. (Not to forget some keyboard related conf |
22 |
settings that appeared in /etc/hal/fdi during the emerge -e kde-meta.) |
23 |
|
24 |
That should teach me to remember *all* the changes I do, not just |
25 |
suspect the unstable packages. :) |
26 |
|
27 |
[1] http://bugs.gentoo.org/show_bug.cgi?id=229269#c4 |
28 |
|
29 |
-- |
30 |
Arttu V. |