| 1 |
Selon Florian Philipp <lists@f_philipp.fastmail.net>: |
| 2 |
|
| 3 |
> alain.didierjean@××××.fr schrieb: |
| 4 |
> > Definitly, an update shouldn't break an existing working configuration! |
| 5 |
> This |
| 6 |
> > happens these days only too often with the Xorg + hal mess. |
| 7 |
> > I happen to use linux as a working tool and 3 days without being able to |
| 8 |
> launch |
| 9 |
> > a working X is a source of problems! This is the second time. As for hal |
| 10 |
> config, |
| 11 |
> > the author should remember that ol'saying:KISS for Keep It Simple, Stupid. |
| 12 |
> > Now, with or without /etc/X11/xorg.conf, my machine (amd64), updated to |
| 13 |
> > libxcb-1.4, xorg-1.6 and hal last version launches X all right, only mouse |
| 14 |
> and |
| 15 |
> > keyboard are not working ! |
| 16 |
> > A line in /var/log/Xorg.0.log says: |
| 17 |
> > (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or |
| 18 |
> 'vmmouse' |
| 19 |
> > will be disabled. |
| 20 |
> > Where is that b..... AllowEmptyOption ? certainly not in xorg.conf. |
| 21 |
> > How do I get back some input on X screen ? |
| 22 |
> > I also get (with xorg.conf) |
| 23 |
> > (EE) Failed to load module "type1" (module doesn't exist, 0) |
| 24 |
> > (EE) Failed to load module "evdev" (module doesn't exist, 0) |
| 25 |
> > Please help before I turn crazy (it might be too late) |
| 26 |
> > |
| 27 |
> |
| 28 |
> With 'launches X' do you mean your desktop environment (login -> startx) |
| 29 |
> or xdm/kdm/gdm? |
| 30 |
both |
| 31 |
> |
| 32 |
|
| 33 |
Thanks all for the help. Finally the problem was solved by re-compiling all X11 |
| 34 |
drivers used, and most notably xf86-input-keyboard & xf86-input-mouse. |
| 35 |
I still think that any package update that breaks a working config without any |
| 36 |
specific doc IS A BUG. That just happened for the scond time. |
Archives