Selon Alan McKinnon alan.mckin...@gmail.com:
On Wednesday 07 October 2009 06:34:06 alain.didierj...@free.fr wrote:
Thanks all for the help. Finally the problem was solved by re-compiling all
X11 drivers used, and most notably xf86-input-keyboard xf86-input-mouse.
I still think that any
On Thursday 08 October 2009 11:19:44 alain.didierj...@free.fr wrote:
Selon Alan McKinnon alan.mckin...@gmail.com:
On Wednesday 07 October 2009 06:34:06 alain.didierj...@free.fr wrote:
Thanks all for the help. Finally the problem was solved by re-compiling
all X11 drivers used, and most
On Thu, 08 Oct 2009 11:19:44 +0200, alain.didierj...@free.fr wrote:
I have the weird habit to trust portage, as it works great 99.9% of the
time (is that a bug ?). I usually don't read elogs as I usually don't
need it.
If you trust portage you should read and follow the the advice it gives
On Wednesday 07 October 2009 06:34:06 alain.didierj...@free.fr wrote:
Thanks all for the help. Finally the problem was solved by re-compiling all
X11 drivers used, and most notably xf86-input-keyboard xf86-input-mouse.
I still think that any package update that breaks a working config
Alan McKinnon ha scritto:
On Wednesday 07 October 2009 06:34:06 alain.didierj...@free.fr wrote:
Thanks all for the help. Finally the problem was solved by re-compiling all
X11 drivers used, and most notably xf86-input-keyboard xf86-input-mouse.
I still think that any package update that
On Wednesday 07 October 2009 19:07:36 bn wrote:
Alan McKinnon ha scritto:
On Wednesday 07 October 2009 06:34:06 alain.didierj...@free.fr wrote:
Thanks all for the help. Finally the problem was solved by re-compiling
all X11 drivers used, and most notably xf86-input-keyboard
Definitly, an update shouldn't break an existing working configuration! This
happens these days only too often with the Xorg + hal mess.
I happen to use linux as a working tool and 3 days without being able to launch
a working X is a source of problems! This is the second time. As for hal config,
On Tue, 06 Oct 2009 16:35:44 +0200, alain.didierj...@free.fr wrote:
Where is that b. AllowEmptyOption ? certainly not in xorg.conf.
An option not appearing in xorg.cong doesn't mean it is not in use, only
that the default is used. Try man xorg.conf.
(EE) Failed to load module evdev
alain.didierj...@free.fr schrieb:
Definitly, an update shouldn't break an existing working configuration! This
happens these days only too often with the Xorg + hal mess.
I happen to use linux as a working tool and 3 days without being able to
launch
a working X is a source of problems! This
On Tue, Oct 6, 2009 at 10:22 AM, Florian Philipp
li...@f_philipp.fastmail.net wrote:
alain.didierj...@free.fr schrieb:
Definitly, an update shouldn't break an existing working configuration!
This
happens these days only too often with the Xorg + hal mess.
I happen to use linux as a
Kevin O'Gorman schrieb:
On Tue, Oct 6, 2009 at 10:22 AM, Florian Philipp
li...@f_philipp.fastmail.net mailto:li...@f_philipp.fastmail.net wrote:
alain.didierj...@free.fr mailto:alain.didierj...@free.fr schrieb:
Definitly, an update shouldn't break an existing working
Selon Florian Philipp li...@f_philipp.fastmail.net:
alain.didierj...@free.fr schrieb:
Definitly, an update shouldn't break an existing working configuration!
This
happens these days only too often with the Xorg + hal mess.
I happen to use linux as a working tool and 3 days without being
alain.didierj...@free.fr wrote:
Thanks all for the help. Finally the problem was solved by re-compiling all
X11
drivers used, and most notably xf86-input-keyboard xf86-input-mouse.
I still think that any package update that breaks a working config without any
specific doc IS A BUG. That
13 matches
Mail list logo
