[gentoo-user] evdev broken?

[gentoo-user] evdev broken?

[Francisco Ares]

[-- Attachment #1: Type: text/plain, Size: 789 bytes --]

Hi, All

Recently, after blindingly emerging world, X11/Xorg stopped to accept mouse
and keyboard events. After some ways to figure out what was going on, I
found that it seems related to "evdev".

Anybody noticed something like that? The xorg-server package (or
xorg-drivers, can't remember nor check now, because I had to use Windows
:-(  ) is being built with "evdev" flag, but there is an error in the log
file about evdev could not be found, as long as "dri" and "dri2". I am using
nvidia proprietary video driver.

Thanks a lot
Francisco
"If you have an apple and I have an apple and we exchange apples then you
and I will still each have one apple. But if you have an idea and I have one
idea and we exchange these ideas, then each of us will have two ideas." -
George Bernard Shaw

[-- Attachment #2: Type: text/html, Size: 889 bytes --]

[gentoo-user] Re: evdev broken?

[Grant Edwards]

On 2011-07-20, Francisco Ares <frares@gmail.com> wrote:
> Hi, All
>
> Recently, after blindingly emerging world, X11/Xorg stopped to accept mouse
> and keyboard events. After some ways to figure out what was going on, I
> found that it seems related to "evdev".
>
> Anybody noticed something like that? The xorg-server package (or
> xorg-drivers, can't remember nor check now, because I had to use Windows
>:-(  ) is being built with "evdev" flag, but there is an error in the log
> file about evdev could not be found, as long as "dri" and "dri2". I am using
> nvidia proprietary video driver.

You probably just need to re-emerge the xf86-input packages that you
have installed. That happens after every update to the Xorg server,
and there are probably messages in the portage log to that effect.

-- 
Grant

Re: [gentoo-user] Re: evdev broken?

[Francisco Ares]

[-- Attachment #1: Type: text/plain, Size: 977 bytes --]

On Wed, Jul 20, 2011 at 12:05 AM, Grant Edwards
<grant.b.edwards@gmail.com>wrote:

> On 2011-07-20, Francisco Ares <frares@gmail.com> wrote:
> > Hi, All
> >
> > Recently, after blindingly emerging world, X11/Xorg stopped to accept
> mouse
> > and keyboard events. After some ways to figure out what was going on, I
> > found that it seems related to "evdev".
> >
> > Anybody noticed something like that? The xorg-server package (or
> > xorg-drivers, can't remember nor check now, because I had to use Windows
> >:-(  ) is being built with "evdev" flag, but there is an error in the log
> > file about evdev could not be found, as long as "dri" and "dri2". I am
> using
> > nvidia proprietary video driver.
>
> You probably just need to re-emerge the xf86-input packages that you
> have installed. That happens after every update to the Xorg server,
> and there are probably messages in the portage log to that effect.
>
> --
> Grant
>
>
>
Thank you, gonna try it

--
Francisco

[-- Attachment #2: Type: text/html, Size: 1457 bytes --]

Re: [gentoo-user] Re: evdev broken?

[Francisco Ares]

[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]

On Wed, Jul 20, 2011 at 12:10 AM, Francisco Ares <frares@gmail.com> wrote:

> On Wed, Jul 20, 2011 at 12:05 AM, Grant Edwards <grant.b.edwards@gmail.com
> > wrote:
>
>> On 2011-07-20, Francisco Ares <frares@gmail.com> wrote:
>> > Hi, All
>> >
>> > Recently, after blindingly emerging world, X11/Xorg stopped to accept
>> mouse
>> > and keyboard events. After some ways to figure out what was going on, I
>> > found that it seems related to "evdev".
>> >
>> > Anybody noticed something like that? The xorg-server package (or
>> > xorg-drivers, can't remember nor check now, because I had to use Windows
>> >:-(  ) is being built with "evdev" flag, but there is an error in the log
>> > file about evdev could not be found, as long as "dri" and "dri2". I am
>> using
>> > nvidia proprietary video driver.
>>
>> You probably just need to re-emerge the xf86-input packages that you
>> have installed. That happens after every update to the Xorg server,
>> and there are probably messages in the portage log to that effect.
>>
>> --
>> Grant
>>
>>
>>
> Thank you, gonna try it
>
> --
> Francisco
>


It worked. Thanks a lot!! Back to Gentoo / X11 again ;-)

Francisco

[-- Attachment #2: Type: text/html, Size: 1932 bytes --]

Re: [gentoo-user] Re: evdev broken?

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1625 bytes --]

On Wednesday 20 Jul 2011 04:38:37 Francisco Ares wrote:
> On Wed, Jul 20, 2011 at 12:10 AM, Francisco Ares <frares@gmail.com> wrote:
> > On Wed, Jul 20, 2011 at 12:05 AM, Grant Edwards
> > <grant.b.edwards@gmail.com
> > 
> > > wrote:
> >> On 2011-07-20, Francisco Ares <frares@gmail.com> wrote:
> >> > Hi, All
> >> > 
> >> > Recently, after blindingly emerging world, X11/Xorg stopped to accept
> >> 
> >> mouse
> >> 
> >> > and keyboard events. After some ways to figure out what was going on,
> >> > I found that it seems related to "evdev".
> >> > 
> >> > Anybody noticed something like that? The xorg-server package (or
> >> > xorg-drivers, can't remember nor check now, because I had to use
> >> > Windows
> >> > 
> >> >:-(  ) is being built with "evdev" flag, but there is an error in the
> >> >:log
> >> >:
> >> > file about evdev could not be found, as long as "dri" and "dri2". I am
> >> 
> >> using
> >> 
> >> > nvidia proprietary video driver.
> >> 
> >> You probably just need to re-emerge the xf86-input packages that you
> >> have installed. That happens after every update to the Xorg server,
> >> and there are probably messages in the portage log to that effect.
> >> 
> >> --
> >> Grant
> > 
> > Thank you, gonna try it
> > 
> > --
> > Francisco
> 
> It worked. Thanks a lot!! Back to Gentoo / X11 again ;-)

Every time after you emerge xorg you're meant to remerge its drivers (evdev 
being one of them).  Usually there is some elog message telling you to run 
qfile to find what is need to be reinstalled:

  qlist -I -C x11-drivers/

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: evdev broken?

[Dale]

Mick wrote:
>
> Every time after you emerge xorg you're meant to remerge its drivers (evdev
> being one of them).  Usually there is some elog message telling you to run
> qfile to find what is need to be reinstalled:
>
>    qlist -I -C x11-drivers/
>
>    

I think this works too:

emerge -1av @x11-module-rebuild

Correct me if I am wrong here.

Dale

:-)  :-)

Re: [gentoo-user] Re: evdev broken?

[Francisco Ares]

[-- Attachment #1: Type: text/plain, Size: 732 bytes --]

On Wed, Jul 20, 2011 at 3:20 AM, Dale <rdalek1967@gmail.com> wrote:

> Mick wrote:
>
>>
>> Every time after you emerge xorg you're meant to remerge its drivers
>> (evdev
>> being one of them).  Usually there is some elog message telling you to run
>> qfile to find what is need to be reinstalled:
>>
>>   qlist -I -C x11-drivers/
>>
>>
>>
>
> I think this works too:
>
> emerge -1av @x11-module-rebuild
>
> Correct me if I am wrong here.
>
> Dale
>
> :-)  :-)
>
>

Thanks for replying, but emerge tells me there are no sets to satisfy
'x11-module-rebuild' . Where would it come from? As far as I could tell,
those sets are manually set, isn't it?

And by the way, what is the use of 'xorg-drivers' package ?

Best regards
Francisco

[-- Attachment #2: Type: text/html, Size: 1276 bytes --]

Re: [gentoo-user] Re: evdev broken?

[Alex Schuster]

Francisco Ares writes:

> On Wed, Jul 20, 2011 at 3:20 AM, Dale <rdalek1967@gmail.com> wrote:
> > Mick wrote:
> >> Every time after you emerge xorg you're meant to remerge its drivers
> >> (evdev being one of them).  Usually there is some elog message telling
> >> you to run
> >> 
> >> qfile to find what is need to be reinstalled:
> >>   qlist -I -C x11-drivers/
> > 
> > I think this works too:
> > 
> > emerge -1av @x11-module-rebuild
> > 
> > Correct me if I am wrong here.

> Thanks for replying, but emerge tells me there are no sets to satisfy
> 'x11-module-rebuild' . Where would it come from? As far as I could tell,
> those sets are manually set, isn't it?

No, you just need a newer portage, probably a version >= 2.2. This seems to 
be safe and is often suggested here on this list. Although there are 
frequent updates and I wonder if some big bug might slide into portage one 
day.

If you want to do so, put

    <sys-apps/portage-9999 **

in /etc/portage/package.accept_keywords. Or something like 

    =sys-apps/portage-2.2.0_alpha45

to install this version only, but I guess when it moves out of the portage 
tree it will be downgraded, so you'd need to put the ebuild into your local 
overlay then.

> And by the way, what is the use of 'xorg-drivers' package ?

I think it's just some sort of meta package pulling in the real drivers. At 
least the output of equery files xorg-drivers is empty.

	Wonko

Re: [gentoo-user] Re: evdev broken?

[Francisco Ares]

[-- Attachment #1: Type: text/plain, Size: 1833 bytes --]

On Wed, Jul 20, 2011 at 3:05 AM, Mick <michaelkintzios@gmail.com> wrote:

> On Wednesday 20 Jul 2011 04:38:37 Francisco Ares wrote:
> > On Wed, Jul 20, 2011 at 12:10 AM, Francisco Ares <frares@gmail.com>
> wrote:
> > > On Wed, Jul 20, 2011 at 12:05 AM, Grant Edwards
> > > <grant.b.edwards@gmail.com
> > >
> > > > wrote:
> > >> On 2011-07-20, Francisco Ares <frares@gmail.com> wrote:
> > >> > Hi, All
> > >> >
> > >> > Recently, after blindingly emerging world, X11/Xorg stopped to
> accept
> > >>
> > >> mouse
> > >>
> > >> > and keyboard events. After some ways to figure out what was going
> on,
> > >> > I found that it seems related to "evdev".
> > >> >
> > >> > Anybody noticed something like that? The xorg-server package (or
> > >> > xorg-drivers, can't remember nor check now, because I had to use
> > >> > Windows
> > >> >
> > >> >:-(  ) is being built with "evdev" flag, but there is an error in the
> > >> >:log
> > >> >:
> > >> > file about evdev could not be found, as long as "dri" and "dri2". I
> am
> > >>
> > >> using
> > >>
> > >> > nvidia proprietary video driver.
> > >>
> > >> You probably just need to re-emerge the xf86-input packages that you
> > >> have installed. That happens after every update to the Xorg server,
> > >> and there are probably messages in the portage log to that effect.
> > >>
> > >> --
> > >> Grant
> > >
> > > Thank you, gonna try it
> > >
> > > --
> > > Francisco
> >
> > It worked. Thanks a lot!! Back to Gentoo / X11 again ;-)
>
> Every time after you emerge xorg you're meant to remerge its drivers (evdev
> being one of them).  Usually there is some elog message telling you to run
> qfile to find what is need to be reinstalled:
>
>  qlist -I -C x11-drivers/
>
> --
> Regards,
> Mick
>


qlist works, too, thanks, that will be very useful in the future.

Best regards
Francisco

[-- Attachment #2: Type: text/html, Size: 2823 bytes --]

[gentoo-user] Re: evdev broken?

[Grant Edwards]

On 2011-07-20, Mick <michaelkintzios@gmail.com> wrote:

> Every time after you emerge xorg you're meant to remerge its drivers (evdev 
> being one of them).  Usually there is some elog message telling you to run 
> qfile to find what is need to be reinstalled:
>
>   qlist -I -C x11-drivers/

I've always wondered why, if portage knows that has to be done, can't
portage just go ahead and do it?

-- 
Grant Edwards               grant.b.edwards        Yow! Let's send the
                                  at               Russians defective
                              gmail.com            lifestyle accessories!

Re: [gentoo-user] Re: evdev broken?

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 884 bytes --]

On Wednesday 20 Jul 2011 15:16:06 Grant Edwards wrote:
> On 2011-07-20, Mick <michaelkintzios@gmail.com> wrote:
> > Every time after you emerge xorg you're meant to remerge its drivers
> > (evdev being one of them).  Usually there is some elog message telling
> > you to run
> > 
> > qfile to find what is need to be reinstalled:
> >   qlist -I -C x11-drivers/
> 
> I've always wondered why, if portage knows that has to be done, can't
> portage just go ahead and do it?

Because as a gentoo user you may have some very good reason NOT to do it (i.e. 
you want to only emerge certain drivers and not others, unmask and emerge 
particular versions, etc.)

Now portage could offer the choice of doing it (I have found these drivers, 
would sir/madam like me to remerge them?) but it could confuse newbies or halt 
emerges when run on a cron job.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: evdev broken?

[Alan McKinnon]

On Wednesday 20 July 2011 14:16:06 Grant Edwards did opine thusly:
> On 2011-07-20, Mick <michaelkintzios@gmail.com> wrote:
> > Every time after you emerge xorg you're meant to remerge its
> > drivers (evdev being one of them).  Usually there is some elog
> > message telling you to run
> > 
> > qfile to find what is need to be reinstalled:
> >   qlist -I -C x11-drivers/
> 
> I've always wondered why, if portage knows that has to be done,
> can't portage just go ahead and do it?

Actually not. Portage doesn't know it has to be done, the ebuild dev 
knows and stuck a literal message in one of the post_() functions.

To do what you mention, the driver would have to depend on xorg, but 
in fact xorg-server depends on the xorg-drivers meta package, which in 
turn depends on the drivers defined in USE.

In theory, one could use PDEPEND I suppose, but I also suspect that 
would cause circular dependencies. The other option is to put an 
emerge call in pkg_postinst() but that would be heavily frowned upon 
as

- it's a highly unusual solution and just an ugly hack
- it wreaks the dep graph that emerge generates
- stuff will get emerged that isn't visible at the beginning
- portage can't definitively tell you before you start that the 
drivers will be remerged


-- 
alan dot mckinnon at gmail dot com

[gentoo-user] Re: evdev broken?

[Grant Edwards]

On 2011-07-20, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On Wednesday 20 July 2011 14:16:06 Grant Edwards did opine thusly:
>> On 2011-07-20, Mick <michaelkintzios@gmail.com> wrote:
>> > Every time after you emerge xorg you're meant to remerge its
>> > drivers (evdev being one of them).  Usually there is some elog
>> > message telling you to run
>> > 
>> > qfile to find what is need to be reinstalled:
>> >   qlist -I -C x11-drivers/
>> 
>> I've always wondered why, if portage knows that has to be done,
>> can't portage just go ahead and do it?
>
> Actually not. Portage doesn't know it has to be done, the ebuild dev 
> knows and stuck a literal message in one of the post_() functions.

Ah, I see.

> To do what you mention, the driver would have to depend on xorg, but 
> in fact xorg-server depends on the xorg-drivers meta package, which
> in turn depends on the drivers defined in USE.

To paraphrase...

The data structures and algorithms used to represent dependancies by
portage can't deal with two packages that depend on each-other. That
is the case with xorg and xorg-drivers, so the dependencies in one
direction are ignore by Portage itself (but not by the devs who have
put the message in the ebuild) and have to be handled out-of-band as
special cases.

Fair enough.  If this is something peculiar to Xorg (it seems there
are a lot of things that are) and doesn't crop up in other places,
it's probably not worth trying to make Portage handle it.

-- 
Grant Edwards               grant.b.edwards        Yow! Does someone from
                                  at               PEORIA have a SHORTER
                              gmail.com            ATTENTION span than me?

Re: [gentoo-user] Re: evdev broken?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 610 bytes --]

On Wed, 20 Jul 2011 14:16:06 +0000 (UTC), Grant Edwards wrote:

> > Every time after you emerge xorg you're meant to remerge its drivers
> > (evdev being one of them).  Usually there is some elog message
> > telling you to run qfile to find what is need to be reinstalled:
> >
> >   qlist -I -C x11-drivers/  
> 
> I've always wondered why, if portage knows that has to be done, can't
> portage just go ahead and do it?

Now that we have a set to do this, I see no reason why this could not be
an option, enabled by a USE flag.


-- 
Neil Bothwick

COMMAND: A suggestion made to a computer.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: evdev broken?

[Michael Orlitzky]

On 07/20/2011 12:37 PM, Neil Bothwick wrote:
> On Wed, 20 Jul 2011 14:16:06 +0000 (UTC), Grant Edwards wrote:
> 
>>> Every time after you emerge xorg you're meant to remerge its drivers
>>> (evdev being one of them).  Usually there is some elog message
>>> telling you to run qfile to find what is need to be reinstalled:
>>>
>>>   qlist -I -C x11-drivers/  
>>
>> I've always wondered why, if portage knows that has to be done, can't
>> portage just go ahead and do it?
> 
> Now that we have a set to do this, I see no reason why this could not be
> an option, enabled by a USE flag.
> 
> 

The last time I complained about this, someone sent me here:

  https://bugs.gentoo.org/show_bug.cgi?id=192319

Re: [gentoo-user] Re: evdev broken?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 813 bytes --]

On Wed, 20 Jul 2011 18:34:03 -0400, Michael Orlitzky wrote:

> >> I've always wondered why, if portage knows that has to be done, can't
> >> portage just go ahead and do it?  
> > 
> > Now that we have a set to do this, I see no reason why this could not
> > be an option, enabled by a USE flag.
> > 
> >   
> 
> The last time I complained about this, someone sent me here:
> 
>   https://bugs.gentoo.org/show_bug.cgi?id=192319

That seems to be discussing ABI changes. The X drivers situation is
different. Also, that issue has largely been resolved, in as much as ABI
changes don't break things like they used to, with @preserved-rebuild.


-- 
Neil Bothwick

Programming Language: (n.) a shorthand way of describing a series of bugs
                      to a computer or a programmer.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: evdev broken?

[Michael Orlitzky]

On 07/21/2011 04:57 AM, Neil Bothwick wrote:
> On Wed, 20 Jul 2011 18:34:03 -0400, Michael Orlitzky wrote:
> 
>>>> I've always wondered why, if portage knows that has to be done, can't
>>>> portage just go ahead and do it?  
>>>
>>> Now that we have a set to do this, I see no reason why this could not
>>> be an option, enabled by a USE flag.
>>>
>>>   
>>
>> The last time I complained about this, someone sent me here:
>>
>>   https://bugs.gentoo.org/show_bug.cgi?id=192319
> 
> That seems to be discussing ABI changes. The X drivers situation is
> different. Also, that issue has largely been resolved, in as much as ABI
> changes don't break things like they used to, with @preserved-rebuild.
> 
> 

Huh? If implemented, that would allow
FORCEREBUILD=x11-drivers/xf86-input* on major Xorg upgrades.

Re: [gentoo-user] Re: evdev broken?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 762 bytes --]

On Thu, 21 Jul 2011 12:13:09 -0400, Michael Orlitzky wrote:

> > That seems to be discussing ABI changes. The X drivers situation is
> > different. Also, that issue has largely been resolved, in as much as
> > ABI changes don't break things like they used to, with
> > @preserved-rebuild.

> Huh?

@preserved-rebuild largely prevents  ABI changes breaking the system by
keeping old libraries around until packages have been rebuilt. It's the
other way round since the depending packages are affected, whereas here
it is the dependencies.

> If implemented, that would allow
> FORCEREBUILD=x11-drivers/xf86-input* on major Xorg upgrades.

Or even @x11-module-rebuild


-- 
Neil Bothwick

Got kleptomania? Be sure to take something for it.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] evdev broken?

[Arthur Barlow]

On Tue, Jul 19, 2011 at 7:50 PM, Francisco Ares <frares@gmail.com> wrote:
> Hi, All
>
> Recently, after blindingly emerging world, X11/Xorg stopped to accept mouse
> and keyboard events. After some ways to figure out what was going on, I
> found that it seems related to "evdev".
>
> Anybody noticed something like that? The xorg-server package (or
> xorg-drivers, can't remember nor check now, because I had to use Windows
> :-(  ) is being built with "evdev" flag, but there is an error in the log
> file about evdev could not be found, as long as "dri" and "dri2". I am using
> nvidia proprietary video driver.
>
> Thanks a lot
> Francisco
> "If you have an apple and I have an apple and we exchange apples then you
> and I will still each have one apple. But if you have an idea and I have one
> idea and we exchange these ideas, then each of us will have two ideas." -
> George Bernard Shaw
>

Francisco,

Yes, this happen to me as well.  It happened right after I did a fair
number of updates that were revealed through emerge -vu --deep world.
It appears that one of the packages, which I believe was libpng-1.4,
did not have a properly designed ebuild script and it subsequently
deleted a number of installed portage packages, including
xf86-input-evdev.  I don't know all the details, but I definately say
some notes on this in the forums section.

Art