no keyboard no mouse

classic Classic list List threaded Threaded
29 messages Options
12
Reply | Threaded
Open this post in threaded view
|

no keyboard no mouse

Alain Didierjean
After upgrading xcb, ati driver and rebooting xorg can't read mouse and keyboard
anymore. No more access to the system besides booting an unbuntu livecd.
According to /var/log/Xorg.0.log, evdev cant't be loaded any more (see below).
What can I do ? Is there an upgrade to evdev ?

--------- excerpt from /var/log/Xorg.0.log-------------
 13.246] (II) LoadModule: "evdev"
    786 [    13.246] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
    787 [    13.247] (II) Module evdev: vendor="X.Org Foundation"
    788 [    13.247]    compiled for 1.9.4, module version = 2.6.0
    789 [    13.247]    Module class: X.Org XInput Driver
    790 [    13.247]    ABI class: X.Org XInput driver, version 11.0
    791 [    13.247] (EE) module ABI major version (11) doesn't match the
server's version (12)
    792 [    13.247] (II) UnloadModule: "evdev"
    793 [    13.247] (II) Unloading evdev
    794 [    13.247] (EE) Failed to load module "evdev" (module requirement
mismatch, 0)
    795 [    13.247] (EE) No input driver matching `evdev'
    796 [    13.252] (II) config/udev: Adding input device Power Button
(/dev/input/event0)
    797 [    13.252] (**) Power Button: Applying InputClass "evdev keyboard
catchall"
    798 [    13.252] (II) LoadModule: "evdev"
    799 [    13.253] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
    800 [    13.253] (II) Module evdev: vendor="X.Org Foundation"
    801 [    13.253]    compiled for 1.9.4, module version = 2.6.0
    802 [    13.253]    Module class: X.Org XInput Driver
    803 [    13.253]    ABI class: X.Org XInput driver, version 11.0
    804 [    13.253] (EE) module ABI major version (11) doesn't match the
server's version (12)
    805 [    13.253] (II) UnloadModule: "evdev"
    806 [    13.253] (II) Unloading evdev
    807 [    13.253] (EE) Failed to load module "evdev" (module requirement
mismatch, 0)
    808 [    13.253] (EE) No input driver matching `evdev'
    809 [    13.254] (II) config/udev: Adding input device Logitech Logitech
Illuminated Keyboard (/dev/input/event2)
    810 [    13.254] (**) Logitech Logitech Illuminated Keyboard: Applying
InputClass "evdev keyboard catchall"
    811 [    13.254] (II) LoadModule: "evdev"
    812 [    13.254] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
    813 [    13.254] (II) Module evdev: vendor="X.Org Foundation"
    814 [    13.254]    compiled for 1.9.4, module version = 2.6.0
    815 [    13.254]    Module class: X.Org XInput Driver
    816 [    13.254]    ABI class: X.Org XInput driver, version 11.0
    817 [    13.254] (EE) module ABI major version (11) doesn't match the
server's version (12)
    818 [    13.254] (II) UnloadModule: "evdev"
    819 [    13.254] (II) Unloading evdev
    820 [    13.254] (EE) Failed to load module "evdev" (module requirement
mismatch, 0)
    821 [    13.254] (EE) No input driver matching `evdev'
    822 [    13.255] (II) config/udev: Adding input device Logitech Logitech
Illuminated Keyboard (/dev/input/event3)
    823 [    13.255] (**) Logitech Logitech Illuminated Keyboard: Applying
InputClass "evdev keyboard catchall"
    824 [    13.255] (II) LoadModule: "evdev"


Reply | Threaded
Open this post in threaded view
|

Re: no keyboard no mouse

Sebastian Beßler-4
Am 24.06.2011 10:47, schrieb [hidden email]:
> After upgrading xcb, ati driver and rebooting xorg can't read mouse and keyboard
> anymore. No more access to the system besides booting an unbuntu livecd.
> According to /var/log/Xorg.0.log, evdev cant't be loaded any more (see below).
> What can I do ? Is there an upgrade to evdev ?
>
>     804 [    13.253] (EE) module ABI major version (11) doesn't match the
> server's version (12)

A emerge -1 x11-drivers/xf86-input-evdev should do the trick.

Greetings

Sebastian Beßler




signature.asc (918 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: no keyboard no mouse

Adam Carter
In reply to this post by Alain Didierjean
On Fri, Jun 24, 2011 at 6:47 PM,  <[hidden email]> wrote:
> After upgrading xcb, ati driver and rebooting xorg can't read mouse and keyboard
> anymore. No more access to the system besides booting an unbuntu livecd.
> According to /var/log/Xorg.0.log, evdev cant't be loaded any more (see below).
> What can I do ? Is there an upgrade to evdev ?

No you just need to rebuild it, so emerge xf86-input-evdev

Reply | Threaded
Open this post in threaded view
|

Re: no keyboard no mouse

Matthew Finkel
In reply to this post by Alain Didierjean
On 06/24/11 04:47, [hidden email] wrote:

> After upgrading xcb, ati driver and rebooting xorg can't read mouse and keyboard
> anymore. No more access to the system besides booting an unbuntu livecd.
> According to /var/log/Xorg.0.log, evdev cant't be loaded any more (see below).
> What can I do ? Is there an upgrade to evdev ?
>
> --------- excerpt from /var/log/Xorg.0.log-------------
>  13.246] (II) LoadModule: "evdev"
>     786 [    13.246] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
>     787 [    13.247] (II) Module evdev: vendor="X.Org Foundation"
>     788 [    13.247]    compiled for 1.9.4, module version = 2.6.0
>     789 [    13.247]    Module class: X.Org XInput Driver
>     790 [    13.247]    ABI class: X.Org XInput driver, version 11.0
>     791 [    13.247] (EE) module ABI major version (11) doesn't match the
> server's version (12)
>     792 [    13.247] (II) UnloadModule: "evdev"
>     793 [    13.247] (II) Unloading evdev
>     794 [    13.247] (EE) Failed to load module "evdev" (module requirement
> mismatch, 0)
>     795 [    13.247] (EE) No input driver matching `evdev'
>     796 [    13.252] (II) config/udev: Adding input device Power Button
> (/dev/input/event0)
>     797 [    13.252] (**) Power Button: Applying InputClass "evdev keyboard
> catchall"
>     798 [    13.252] (II) LoadModule: "evdev"
>     799 [    13.253] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
>     800 [    13.253] (II) Module evdev: vendor="X.Org Foundation"
>     801 [    13.253]    compiled for 1.9.4, module version = 2.6.0
>     802 [    13.253]    Module class: X.Org XInput Driver
>     803 [    13.253]    ABI class: X.Org XInput driver, version 11.0
>     804 [    13.253] (EE) module ABI major version (11) doesn't match the
> server's version (12)
>     805 [    13.253] (II) UnloadModule: "evdev"
>     806 [    13.253] (II) Unloading evdev
>     807 [    13.253] (EE) Failed to load module "evdev" (module requirement
> mismatch, 0)
>     808 [    13.253] (EE) No input driver matching `evdev'
>     809 [    13.254] (II) config/udev: Adding input device Logitech Logitech
> Illuminated Keyboard (/dev/input/event2)
>     810 [    13.254] (**) Logitech Logitech Illuminated Keyboard: Applying
> InputClass "evdev keyboard catchall"
>     811 [    13.254] (II) LoadModule: "evdev"
>     812 [    13.254] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
>     813 [    13.254] (II) Module evdev: vendor="X.Org Foundation"
>     814 [    13.254]    compiled for 1.9.4, module version = 2.6.0
>     815 [    13.254]    Module class: X.Org XInput Driver
>     816 [    13.254]    ABI class: X.Org XInput driver, version 11.0
>     817 [    13.254] (EE) module ABI major version (11) doesn't match the
> server's version (12)
>     818 [    13.254] (II) UnloadModule: "evdev"
>     819 [    13.254] (II) Unloading evdev
>     820 [    13.254] (EE) Failed to load module "evdev" (module requirement
> mismatch, 0)
>     821 [    13.254] (EE) No input driver matching `evdev'
>     822 [    13.255] (II) config/udev: Adding input device Logitech Logitech
> Illuminated Keyboard (/dev/input/event3)
>     823 [    13.255] (**) Logitech Logitech Illuminated Keyboard: Applying
> InputClass "evdev keyboard catchall"
>     824 [    13.255] (II) LoadModule: "evdev"
Did you try remerging evdev? I believe there's another package you need
to reemerge also, I can't remember off the top of my head. If some one
else doesn't chime in by the time I wake up then I'll look it up.

Reply | Threaded
Open this post in threaded view
|

Re: no keyboard no mouse

Neil Bothwick
On Fri, 24 Jun 2011 05:05:13 -0400, Matthew Finkel wrote:

> Did you try remerging evdev? I believe there's another package you need
> to reemerge also, I can't remember off the top of my head. If some one
> else doesn't chime in by the time I wake up then I'll look it up.

If you use portage 2.2, emerge @x11-module-rebuild


--
Neil Bothwick

Time is the best teacher; unfortunately it kills all its students.

signature.asc (205 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: no keyboard no mouse

Alan Mackenzie
In reply to this post by Adam Carter
Hi, Adam.

On Fri, Jun 24, 2011 at 06:59:42PM +1000, Adam Carter wrote:
> On Fri, Jun 24, 2011 at 6:47 PM,  <[hidden email]> wrote:
> > After upgrading xcb, ati driver and rebooting xorg can't read mouse and keyboard
> > anymore. No more access to the system besides booting an unbuntu livecd.
> > According to /var/log/Xorg.0.log, evdev cant't be loaded any more (see below).
> > What can I do ? Is there an upgrade to evdev ?

> No you just need to rebuild it, so emerge xf86-input-evdev

This problem hit me too.  Can you give us an explanation for needing to
rebuild evdev?  Was there some missing dependency in an ebuild, or
something?

--
Alan Mackenzie (Nuremberg, Germany).

Reply | Threaded
Open this post in threaded view
|

Re: no keyboard no mouse

Dale-46
Alan Mackenzie wrote:

> Hi, Adam.
>
> On Fri, Jun 24, 2011 at 06:59:42PM +1000, Adam Carter wrote:
>    
>> On Fri, Jun 24, 2011 at 6:47 PM,<[hidden email]>  wrote:
>>      
>>> After upgrading xcb, ati driver and rebooting xorg can't read mouse and keyboard
>>> anymore. No more access to the system besides booting an unbuntu livecd.
>>> According to /var/log/Xorg.0.log, evdev cant't be loaded any more (see below).
>>> What can I do ? Is there an upgrade to evdev ?
>>>        
>    
>> No you just need to rebuild it, so emerge xf86-input-evdev
>>      
> This problem hit me too.  Can you give us an explanation for needing to
> rebuild evdev?  Was there some missing dependency in an ebuild, or
> something?
>
>    

It is sort of like when you update a kernel and have to rebuild the
video drivers.  One is built against the other and when you upgrade, you
have to update the things it was built against.  There are other
examples of this but this is just the first one I thought of.

Anyone recall expat?  That I think is another.

Dale

:-)  :-)

Reply | Threaded
Open this post in threaded view
|

Re: no keyboard no mouse

Adam Carter
In reply to this post by Alan Mackenzie
>> No you just need to rebuild it, so emerge xf86-input-evdev
>
> This problem hit me too.  Can you give us an explanation for needing to
> rebuild evdev?  Was there some missing dependency in an ebuild, or
> something?

If you update xorg (which OP didnt list, but a new version just went
stable) you need to rebuild its drivers (unless they were
automatically rebuilt due to version bump).

Reply | Threaded
Open this post in threaded view
|

Re: no keyboard no mouse

Alain Didierjean
In reply to this post by Alain Didierjean

----- Mail Original -----
De: "Adam Carter" <[hidden email]>
À: [hidden email]
Envoyé: Vendredi 24 Juin 2011 14h07:02 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Re: [gentoo-user] no keyboard no mouse

>> No you just need to rebuild it, so emerge xf86-input-evdev
>
> This problem hit me too.  Can you give us an explanation for needing to
> rebuild evdev?  Was there some missing dependency in an ebuild, or
> something?

If you update xorg (which OP didnt list, but a new version just went
stable) you need to rebuild its drivers (unless they were
automatically rebuilt due to version bump).

I think portage should take care of that... but obviously it doesn't
I solved the problem by rebuilding xf86-input-evdev after booting on an unbuntu livecd then chrooting... Took some time.
As for using portage 2.2, it's listed as ~*2.2.0_alpha41, too early for me.
Thanks all for the help


--
                           
        Alain DIDIERJEAN      Puisque ces mystères nous dépassent
                           Feignons d'en être l'organisateur


Reply | Threaded
Open this post in threaded view
|

Re: no keyboard no mouse

Adam Carter
> I think portage should take care of that... but obviously it doesn't
> I solved the problem by rebuilding xf86-input-evdev after booting on an unbuntu livecd then chrooting... Took some time.
> As for using portage 2.2, it's listed as ~*2.2.0_alpha41, too early for me.

Make an entry in your grub.conf with gentoo=nox, so you can boot to
command line. here's what mine looks like

title Gentoo Linux 2.6.39-r1a
root (hd0,0)
kernel /boot/kernel-2.6.39-r1a root=/dev/sda3 usbcore.autosuspend=1

title Gentoo Linux 2.6.39-r1a Console
root (hd0,0)
kernel /boot/kernel-2.6.39-r1a root=/dev/sda3 usbcore.autosuspend=1 gentoo=nox

Reply | Threaded
Open this post in threaded view
|

Re: no keyboard no mouse

Mick-10
In reply to this post by Neil Bothwick
On Friday 24 Jun 2011 10:34:50 Neil Bothwick wrote:
> On Fri, 24 Jun 2011 05:05:13 -0400, Matthew Finkel wrote:
> > Did you try remerging evdev? I believe there's another package you need
> > to reemerge also, I can't remember off the top of my head. If some one
> > else doesn't chime in by the time I wake up then I'll look it up.
>
> If you use portage 2.2, emerge @x11-module-rebuild

or in the words of the elog itself which the OP evidently missed:
================================================================
>>> Messages generated by process 15731 on 2011-06-23 19:30:53 BST for package
x11-base/xorg-server-1.10.2:

LOG: postinst
You should consider reading upgrade guide for this release:
        http://www.gentoo.org/proj/en/desktop/x/x11/xorg-server-1.10-upgrade-
guide.xml

WARN: postinst
You must rebuild all drivers if upgrading from <xorg-server-1.10
because the ABI changed. If you cannot start X because
of module version mismatch errors, this is your problem.
You can generate a list of all installed packages in the x11-drivers
category using this command:
        emerge portage-utils; qlist -I -C x11-drivers/
or using sets from portage-2.2:
        emerge @x11-module-rebuild
================================================================

HTH.
--
Regards,
Mick

signature.asc (205 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: no keyboard no mouse

Alan Mackenzie
In reply to this post by Adam Carter
Hi, Adam.

On Fri, Jun 24, 2011 at 10:07:02PM +1000, Adam Carter wrote:
> >> No you just need to rebuild it, so emerge xf86-input-evdev

> > This problem hit me too.  Can you give us an explanation for needing to
> > rebuild evdev?  Was there some missing dependency in an ebuild, or
> > something?

> If you update xorg (which OP didnt list, but a new version just went
> stable) you need to rebuild its drivers (unless they were
> automatically rebuilt due to version bump).

Hmm.  Recompiling the same source code produces a different binary?
Presumably, it uses C macros in a .h file which is part of xorg.  Or
something like that.

So evdev depends on xorg.  Isn't there a way of expressing this in
evdev's ebuild?  Something like the DEPEND variable?

--
Alan Mackenzie (Nuremberg, Germany).

Reply | Threaded
Open this post in threaded view
|

Re: no keyboard no mouse

Alan McKinnon-2
On Friday 24 June 2011 14:42:24 Alan Mackenzie did opine thusly:

> Hi, Adam.
>
> On Fri, Jun 24, 2011 at 10:07:02PM +1000, Adam Carter wrote:
> > >> No you just need to rebuild it, so emerge xf86-input-evdev
> > >
> > > This problem hit me too.  Can you give us an explanation for
> > > needing to rebuild evdev?  Was there some missing
> > > dependency in an ebuild, or something?
> >
> > If you update xorg (which OP didnt list, but a new version just
> > went stable) you need to rebuild its drivers (unless they were
> > automatically rebuilt due to version bump).
>
> Hmm.  Recompiling the same source code produces a different binary?

Not quite:

Rebuilding the same sources against different headers produces a
different binary.

> Presumably, it uses C macros in a .h file which is part of xorg.  Or
> something like that.
>
> So evdev depends on xorg.  Isn't there a way of expressing this in
> evdev's ebuild?  Something like the DEPEND variable?

It's already there, but doesn't help as the update trigger never
happens.

Actually, you have the depend the wrong way round - evdev depends on
xorg-server; to have the driver and for it to be useful, the xorg-
server must be present, otherwise there is nothing for the drivers to
build against.

You want to force a rebuild that is the opposite of the DEPEND, but
portage does not support that (it's a circular dependency). It will
also not rebuild the driver as part of a regular update as there is
not a new version of the driver, hence according to normal portage
logic there is no need to do so.

Make sense?


--
alan dot mckinnon at gmail dot com

Reply | Threaded
Open this post in threaded view
|

Re: no keyboard no mouse

Neil Bothwick
In reply to this post by Alain Didierjean
On Fri, 24 Jun 2011 14:43:02 +0200 (CEST), Alain DIDIERJEAN wrote:

> I solved the problem by rebuilding xf86-input-evdev after booting on an
> unbuntu livecd then chrooting... Took some time. As for using portage

Why did you need to chroot, just boot your normal system without X (add
gentoo=nox to the kernel paramaters).

> 2.2, it's listed as ~*2.2.0_alpha41, too early for me. Thanks all for
> the help

Don't let the ridiculous version number fool you, 2.2 has been
generally usable for a couple of years.


--
Neil Bothwick

THE BORG: Calm, Cool and Collective...

signature.asc (205 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: no keyboard no mouse

Dale-46
Neil Bothwick wrote:

> On Fri, 24 Jun 2011 14:43:02 +0200 (CEST), Alain DIDIERJEAN wrote:
>
>    
>> 2.2, it's listed as ~*2.2.0_alpha41, too early for me. Thanks all for
>> the help
>>      
> Don't let the ridiculous version number fool you, 2.2 has been
> generally usable for a couple of years.
>
>
>    

+1   I been using it here for a good while now.  Other than the
occasional surprise of feature enhancements, it has been fine.

Dale

:-)  :-)

Reply | Threaded
Open this post in threaded view
|

Re: no keyboard no mouse

Pandu Poluan
In reply to this post by Neil Bothwick
On Sat, Jun 25, 2011 at 05:00, Neil Bothwick <[hidden email]> wrote:

> On Fri, 24 Jun 2011 14:43:02 +0200 (CEST), Alain DIDIERJEAN wrote:
>
>> I solved the problem by rebuilding xf86-input-evdev after booting on an
>> unbuntu livecd then chrooting... Took some time. As for using portage
>
> Why did you need to chroot, just boot your normal system without X (add
> gentoo=nox to the kernel paramaters).
>
>> 2.2, it's listed as ~*2.2.0_alpha41, too early for me. Thanks all for
>> the help
>
> Don't let the ridiculous version number fool you, 2.2 has been
> generally usable for a couple of years.
>

Honestly, the "alpha" designation also made me shy away from 2.2

Really, someone should rebrand that as "beta", if 2.2 is indeed usable
for a couple of years.

That said, thanks for the heads-up. I'll unmask it on my systems :-)

Rgdsm
--
Pandu E Poluan
~ IT Optimizer ~
Visit my Blog: http://pepoluan.posterous.com
Google Talk:    pepoluan
Y! messenger: pepoluan
MSN / Live:      [hidden email] (do not send email here)
Skype:            pepoluan

Reply | Threaded
Open this post in threaded view
|

Re: no keyboard no mouse

Alan McKinnon-2
On Saturday 25 June 2011 11:31:50 Pandu Poluan did opine thusly:
> On Sat, Jun 25, 2011 at 05:00, Neil Bothwick <[hidden email]>
wrote:

> > On Fri, 24 Jun 2011 14:43:02 +0200 (CEST), Alain DIDIERJEAN wrote:
> >> I solved the problem by rebuilding xf86-input-evdev after
> >> booting on an unbuntu livecd then chrooting... Took some
> >> time. As for using portage
> >
> > Why did you need to chroot, just boot your normal system without
> > X (add gentoo=nox to the kernel paramaters).
> >
> >> 2.2, it's listed as ~*2.2.0_alpha41, too early for me. Thanks
> >> all for the help
> >
> > Don't let the ridiculous version number fool you, 2.2 has been
> > generally usable for a couple of years.
>
> Honestly, the "alpha" designation also made me shy away from 2.2

It's not alpha as in alpha

The rc point releases hit -99 sometime ago so Zac switched to a
different prefix. Most other projects would have been a release by
now.


>
> Really, someone should rebrand that as "beta", if 2.2 is indeed
> usable for a couple of years.
>
> That said, thanks for the heads-up. I'll unmask it on my systems :-)
>
> Rgdsm
--
alan dot mckinnon at gmail dot com

Reply | Threaded
Open this post in threaded view
|

Re: no keyboard no mouse

Alain Didierjean
In reply to this post by Neil Bothwick

----- Mail Original -----
De: "Neil Bothwick" <[hidden email]>
À: [hidden email]
Envoyé: Samedi 25 Juin 2011 00h00:30 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Re: [gentoo-user] no keyboard no mouse

On Fri, 24 Jun 2011 14:43:02 +0200 (CEST), Alain DIDIERJEAN wrote:

> I solved the problem by rebuilding xf86-input-evdev after booting on an
> unbuntu livecd then chrooting... Took some time. As for using portage

Why did you need to chroot, just boot your normal system without X (add
gentoo=nox to the kernel paramaters).

Didn't remember the option in these times of panic (I had some task to achieve rapidly). It's now an entry in grub.conf

> 2.2, it's listed as ~*2.2.0_alpha41, too early for me. Thanks all for
> the help

Don't let the ridiculous version number fool you, 2.2 has been
generally usable for a couple of years.

Oooops, I stupidly thought that "alpha" in version name, which usually doesn't appear, meant a specially risky version in alpha state... Silly me.


--
                           
        Alain DIDIERJEAN      Puisque ces mystères nous dépassent
                           Feignons d'en être l'organisateur


Reply | Threaded
Open this post in threaded view
|

Re: no keyboard no mouse

Alan Mackenzie
In reply to this post by Alan McKinnon-2
Hi, Alan.

On Fri, Jun 24, 2011 at 04:57:05PM +0200, Alan McKinnon wrote:

> > Hmm.  Recompiling the same source code produces a different binary?

> Not quite:

> Rebuilding the same sources against different headers produces a
> different binary.

> > Presumably, it uses C macros in a .h file which is part of xorg.  Or
> > something like that.

> > So evdev depends on xorg.  Isn't there a way of expressing this in
> > evdev's ebuild?  Something like the DEPEND variable?

> It's already there, but doesn't help as the update trigger never
> happens.

> Actually, you have the depend the wrong way round - evdev depends on
> xorg-server; to have the driver and for it to be useful, the xorg-
> server must be present, otherwise there is nothing for the drivers to
> build against.

> You want to force a rebuild that is the opposite of the DEPEND, but
> portage does not support that (it's a circular dependency). It will
> also not rebuild the driver as part of a regular update as there is not
> a new version of the driver, hence according to normal portage logic
> there is no need to do so.

> Make sense?

I think so - I've always had problems understanding dependencies.  What I
want is one of these "nice to have"s which would take an inordinate
amount of work, if it's even possible.

In the meantime, I'll carry on not starting Gnome at boot-up.  Despite
the existence of gentoo=nox, I feel safer starting it manually.  It's a
strange, depressing feeling when the only input device which works is the
reset button - thank goodness that isn't handled by evdev.  ;-)

> --
> alan dot mckinnon at gmail dot com

--
Alan Mackenzie (Nuremberg, Germany).

Reply | Threaded
Open this post in threaded view
|

Re: no keyboard no mouse

Neil Bothwick
In reply to this post by Alain Didierjean
On Sat, 25 Jun 2011 09:37:59 +0200 (CEST), Alain DIDIERJEAN wrote:

> > 2.2, it's listed as ~*2.2.0_alpha41, too early for me. Thanks all for
> > the help  
>
> Don't let the ridiculous version number fool you, 2.2 has been
> generally usable for a couple of years.
>
> Oooops, I stupidly thought that "alpha" in version name, which usually
> doesn't appear, meant a specially risky version in alpha state... Silly
> me.

I'd say the sillyness is in the version number. 2.2 (we're on 2.2.0 now)
reached the milestone of 99 release candidates, which is farcical.


--
Neil Bothwick

I don't have any solution, but I certainly admire the problem.

signature.asc (205 bytes) Download Attachment
12