Re: [gentoo-user] Re: How am I supposed to block the KDE update?

[J. Roeleveld]

On March 14, 2017 6:05:17 PM GMT+01:00, Nikos Chantziaras  
wrote:
>On 03/14/2017 06:34 PM, Alan McKinnon wrote:
>> Eek. That's not nice. You have masked frameworks-5.32.0 and
>plasma-5.9.3
>> packages (presumably you got all of them), and you missed something
>in
>> the huge chain that needs one or more of them.
>
>Oops, you are absolutely correct. In fact, what I didn't mask is 
>=kde-frameworks/plasma-5.32.0-r1.
>
>And here's the funny part: I specifically only masked =*/*-5.32.0 
>instead of ~*/*-5.32.0 so that I'll know when the bug gets potentially 
>fixed; it would result in this exact kind of breakage I got, reminding 
>me to try the update again.
>
>So I'll be trying the update again to see if the plasma revbumb is
>there 
>to actually fix the desktop again. (The issue was that hovering over 
>icons or other items would highlight them but they would stay 
>highlighted forever even after the mouse moved somewhere else or even
>if 
>you click somewhere else. So everything would be full of highlighted
>icons.)
>
>Moral of the story: more coffee before posting :-P

I have seen this happen on MS Windows machines. (Customer supplied ones)

I think it is related to some accessibility thing that accidentally gets 
enabled.
(I simply reboot Windows as I prefer not to fight my way through a stupidly 
locked down system)

Could be a similar cause with your KDE/Plasma issue?

--
Joost
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] Re: OpenGL problem after upgrading mesa and xorg-server

[wabe]

Miroslav Rovis  wrote:

> On 170314-05:32+0100, wabe wrote:
> > wabe  wrote:
> >   
> > > Since I've upgraded mesa (12.0.1 to 13.0.5) and xorg-server 
> > > (1.18.4 to 1.19.2), OpenGL programs don't work any longer for 
> > > non-root users, even when these users are members of the group 
> > > "video".  
> ...
> > > 
> > > I searched the web and also read the gentoo xserver wiki but
> > > couldn't find a solution.  
> > 
> > P.S.: After downgrading mesa to 12.0.1 everything works fine again.
> > So the problem has nothing to do with xorg-server.  
> 
> Lots of bugs with mesa, esp. recently:
> https://bugs.gentoo.org/buglist.cgi?quicksearch=mesa
> 
> I masked it for now (if I had time, I'd contribute reports...):
> 
> /etc/portage/package.mask/package.mask.file:>=media-libs/mesa-13.0.0  

THX for your answer. I also masked it and will wait for next version.

--
Regards
wabe

Re: [gentoo-user] Can't get rid of binutils 'preserved libs' warning

[Alan McKinnon]

On 14/03/2017 19:51, Willie M wrote:
> On 03/14/2017 09:52 AM, Alan McKinnon wrote:
>> On 14/03/2017 17:45, Grant Edwards wrote:
>>> After I do an update, I get this message:
>>>
>>>   !!! existing preserved libs:
>>>   >>> package: sys-libs/binutils-libs-2.27
>>>*  - /usr/lib64/libbfd-2.25.1.so
>>>*  used by 
>>> /usr/lib64/binutils/x86_64-pc-linux-gnu/2.25.1/libopcodes-2.25.1.so 
>>> (sys-devel/binutils-2.25.1-r1)
>>>   Use emerge @preserved-rebuild to rebuild packages using these libraries
>>>
>>> When I do an 'emerge @preserved-rebuild', it re-builds
>>> binutils-2.25.1, and then shows the same warning again.
>>>
>>> I've run @preserved-rebuild 5 or 6 times, sourcing /etc/profile and
>>> logging out/in between.  Still, I always get the same preserved-libs
>>> warning.
>>>
>>> Portage seems upset tht binutils-2.25.1 is using binutils-libs-2.25.1
>>> instead of binutils-libs-2.27, but re-emerging binutils-2.25.1 doesn't
>>> help.
>>>
>> I've run into similar things a few times and never really got to the
>> bottom of any of them and ldd wasn't very useful either.
>>
>> How I have got around it in the past is to stop rebuilding, that just
>> keeps the crazy loop going as each time the new thing doesn't like the
>> existing thing. So I emerge -C the offending package and the
>> dependencies, then emerge both back in so they start from scratch.
>>
>> But in this case, removing binutils might be problematic, that's where
>> your elf tools and linker come from. A workaround comes to mind:
>>
>> - quickpkg both packages
>> - emerge -C both packages
>> - manually untar both quickpkg archives to their original location. Now
>> you have all your tools back, without the package metadata to confuse
>> portage
>> - emerge both packages, ignoring the expected file collision errors.
>>
> 
> Way better idea than I had with just a warning.

After 20 years in this game, just develop a sixth sense to smell things
that will go wrong :-)

Pity that sense failed me when I last tried removing most of @system and
using the busybox equivalent - busybox tar doesn't implement an option
that emerge requires.



-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] Recommended CDR-Burning-frontend without QT and without KDE?

[tuxic]

On 03/14 06:34, Joerg Schilling wrote:
> Miroslav Rovis  wrote:
> 
> > growisofs, cdrecord, and friends ...mkisofs for cdrecord, IIRC ...I use
> > it rarely nowadays...
> >
> > but none (assisting other programs) actually if it's data to burn on DVD
> > or BD, growisofs is fine solo there...
> 
> ???
> 
> cdrecord supports DVDs since March 1998 which makes it the third DVD writing 
> software worldwide and the first OSS DVD writing software.
> 
> cdrecord supports writing BD media since July 2007 which is nearly 10 years 
> ago.
> 
> growisofs on the other side is unmaintained since 9 years and there already 
> have been reported problems where growisofs could not be used while cdrecord 
> works fine.
> 
> 
> BTW: X-CD-Roast is still alive and works fine with cdrtools.
> 
> Jörg
> 
> -- 
>  EMail:jo...@schily.net(home) Jörg Schilling D-13353 
> Berlin
> joerg.schill...@fokus.fraunhofer.de (work) Blog: 
> http://schily.blogspot.com/
>  URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/'
> 

Hi Jörg,

is it possible to run xcdroast without root ( i.e. user root or suid
)?

Cheers
Meino

Re: [gentoo-user] Recommended CDR-Burning-frontend without QT and without KDE?

[Marvin Gülker]

I find bashburn a fairly nice tool, but for reasons unknown to me it
always fails when burning DVDs. Otherwise it does fine.

Marvin

-- 
Blog: https://www.guelkerdev.de
PGP/GPG ID: F1D8799FBCC8BC4F

Re: [gentoo-user] Can't get rid of binutils 'preserved libs' warning

[Marc Joliet]

On Dienstag, 14. März 2017 18:43:07 CET John Covici wrote:
> On Tue, 14 Mar 2017 12:52:07 -0400,
> 
> Alan McKinnon wrote:
> > On 14/03/2017 17:45, Grant Edwards wrote:
> > > After I do an update, I get this message:
> > >   !!! existing preserved libs:
> > >   >>> package: sys-libs/binutils-libs-2.27
> > >
> > >*  - /usr/lib64/libbfd-2.25.1.so
> > >*  used by
> > >/usr/lib64/binutils/x86_64-pc-linux-gnu/2.25.1/libopcodes-2.25.1.so
> > >(sys-devel/binutils-2.25.1-r1)> >   
> > >   Use emerge @preserved-rebuild to rebuild packages using these
> > >   libraries
> > > 
> > > When I do an 'emerge @preserved-rebuild', it re-builds
> > > binutils-2.25.1, and then shows the same warning again.
> > > 
> > > I've run @preserved-rebuild 5 or 6 times, sourcing /etc/profile and
> > > logging out/in between.  Still, I always get the same preserved-libs
> > > warning.
> > > 
> > > Portage seems upset tht binutils-2.25.1 is using binutils-libs-2.25.1
> > > instead of binutils-libs-2.27, but re-emerging binutils-2.25.1 doesn't
> > > help.
> > 
> > I've run into similar things a few times and never really got to the
> > bottom of any of them and ldd wasn't very useful either.
> > 
> > How I have got around it in the past is to stop rebuilding, that just
> > keeps the crazy loop going as each time the new thing doesn't like the
> > existing thing. So I emerge -C the offending package and the
> > dependencies, then emerge both back in so they start from scratch.
> > 
> > But in this case, removing binutils might be problematic, that's where
> > your elf tools and linker come from. A workaround comes to mind:
> > 
> > - quickpkg both packages
> > - emerge -C both packages
> > - manually untar both quickpkg archives to their original location. Now
> > you have all your tools back, without the package metadata to confuse
> > portage
> > - emerge both packages, ignoring the expected file collision errors.
> 
> What I did when I had this, was to unmerge an older version of
> binutils which I had, seemed no reason to keep it, but do an emerge
> --depclean on it just to be safe.  Once I did that the preserved libs
> warning went away.

Wow, when I saw OPs Email, I didn't notice the version, but it seems that that 
would explain it.

In this case it seems that one should keep in mind the recommendation to use 
--depclean after a @world update (as a matter of fact, emerge helpfully prints 
out such a message after @world updates).  I have been doing so religiously 
for years now.

HTH
-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Can't get rid of binutils 'preserved libs' warning

[Willie M]

On 03/14/2017 09:52 AM, Alan McKinnon wrote:
> On 14/03/2017 17:45, Grant Edwards wrote:
>> After I do an update, I get this message:
>>
>>   !!! existing preserved libs:
>>   >>> package: sys-libs/binutils-libs-2.27
>>*  - /usr/lib64/libbfd-2.25.1.so
>>*  used by 
>> /usr/lib64/binutils/x86_64-pc-linux-gnu/2.25.1/libopcodes-2.25.1.so 
>> (sys-devel/binutils-2.25.1-r1)
>>   Use emerge @preserved-rebuild to rebuild packages using these libraries
>>
>> When I do an 'emerge @preserved-rebuild', it re-builds
>> binutils-2.25.1, and then shows the same warning again.
>>
>> I've run @preserved-rebuild 5 or 6 times, sourcing /etc/profile and
>> logging out/in between.  Still, I always get the same preserved-libs
>> warning.
>>
>> Portage seems upset tht binutils-2.25.1 is using binutils-libs-2.25.1
>> instead of binutils-libs-2.27, but re-emerging binutils-2.25.1 doesn't
>> help.
>>
> I've run into similar things a few times and never really got to the
> bottom of any of them and ldd wasn't very useful either.
>
> How I have got around it in the past is to stop rebuilding, that just
> keeps the crazy loop going as each time the new thing doesn't like the
> existing thing. So I emerge -C the offending package and the
> dependencies, then emerge both back in so they start from scratch.
>
> But in this case, removing binutils might be problematic, that's where
> your elf tools and linker come from. A workaround comes to mind:
>
> - quickpkg both packages
> - emerge -C both packages
> - manually untar both quickpkg archives to their original location. Now
> you have all your tools back, without the package metadata to confuse
> portage
> - emerge both packages, ignoring the expected file collision errors.
>

Way better idea than I had with just a warning.

-- 

Willie L Matthews
matthews.willi...@gmail.com
702-659-9966




signature.asc
Description: OpenPGP digital signature

Re: [gentoo-user] Can't get rid of binutils 'preserved libs' warning

[John Covici]

On Tue, 14 Mar 2017 12:52:07 -0400,
Alan McKinnon wrote:
> 
> On 14/03/2017 17:45, Grant Edwards wrote:
> > After I do an update, I get this message:
> > 
> >   !!! existing preserved libs:
> >   >>> package: sys-libs/binutils-libs-2.27
> >*  - /usr/lib64/libbfd-2.25.1.so
> >*  used by 
> > /usr/lib64/binutils/x86_64-pc-linux-gnu/2.25.1/libopcodes-2.25.1.so 
> > (sys-devel/binutils-2.25.1-r1)
> >   Use emerge @preserved-rebuild to rebuild packages using these libraries
> > 
> > When I do an 'emerge @preserved-rebuild', it re-builds
> > binutils-2.25.1, and then shows the same warning again.
> > 
> > I've run @preserved-rebuild 5 or 6 times, sourcing /etc/profile and
> > logging out/in between.  Still, I always get the same preserved-libs
> > warning.
> > 
> > Portage seems upset tht binutils-2.25.1 is using binutils-libs-2.25.1
> > instead of binutils-libs-2.27, but re-emerging binutils-2.25.1 doesn't
> > help.
> > 
> 
> I've run into similar things a few times and never really got to the
> bottom of any of them and ldd wasn't very useful either.
> 
> How I have got around it in the past is to stop rebuilding, that just
> keeps the crazy loop going as each time the new thing doesn't like the
> existing thing. So I emerge -C the offending package and the
> dependencies, then emerge both back in so they start from scratch.
> 
> But in this case, removing binutils might be problematic, that's where
> your elf tools and linker come from. A workaround comes to mind:
> 
> - quickpkg both packages
> - emerge -C both packages
> - manually untar both quickpkg archives to their original location. Now
> you have all your tools back, without the package metadata to confuse
> portage
> - emerge both packages, ignoring the expected file collision errors.

What I did when I had this, was to unmerge an older version of
binutils which I had, seemed no reason to keep it, but do an emerge
--depclean on it just to be safe.  Once I did that the preserved libs
warning went away.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici
 cov...@ccs.covici.com

Re: [gentoo-user] some capital B blockers in world update

[Alan McKinnon]

On 14/03/2017 19:00, allan gottlieb wrote:
> On Tue, Mar 14 2017, Alan McKinnon wrote:
> 
>> On 14/03/2017 16:43, allan gottlieb wrote:
>>> I update roughly twice a week.  On one machine (full output below) I was
>>> told that libinput and evdev are blocking xorg-drivers
>>>
>>> [blocks B ] >> (">> x11-base/xorg-drivers-1.19)
>>> [blocks B ] >> (">> x11-base/xorg-drivers-1.19)
>>>
>>> However the merge does propose to update xorg-drivers
>>> [ebuild U ] x11-base/xorg-drivers-1.19 [1.18-r1] VIDEO_CARDS="-ark%
>>> -i915% -i965% (-newport) -sis%"
>>>
>>> It also proposes to update libinput and evdev
>>> [ebuild U  ]   x11-drivers/xf86-input-libinput-0.24.0 [0.19.0]
>>> [ebuild U  ]  x11-drivers/xf86-input-evdev-2.10.5 [2.10.3]
>>>
>>> I do see that the versions of libinput and evdev to be used are higher
>>> than the versions that would block xorg-drivers.  I am wondering why in
>>> this case emerge is telling me about the block (in red with a capital B)
>>> and more importantly would appreciate confirmation that I should let the
>>> emerge proceed.
>>
>>
>> Portage found a solution that satisfies all constraints, so you should
>> let it proceed.
>>
>> Did you run emerge with -v to get the above?
>> That looks like portage is doing it's usual -v thing which is to core
>> dump to your console in the hope that maybe you can figure it out and
>> you are willing to play the game called "let's find out what portage
>> thinks it means today!"
>>
>> I don't understand why those blockers are marked hard, as portage found
>> a solution. The blocker lines are really telling you why portage wants
>> to upgrade your libinput and evdev drivers - the current ones won't work
>> with your current drivers.
>>
>> Which is all totally pointless, as newer versions of everything are
>> available and you want a full update. There's very little point in
>> software going to great lengths to tell you why it won't keep old
>> versions when you explicitly told it to not keep old versions :-)
> 
> Thank you for the confirmation!  I also doubt the use of B when b would
> be appropriated.  No this was not a --verbose run.  I would guess that
> output would be even less illuminating.

:-)

Portage is a lot like Sheldon from The Big Bang Theory. Everything it
says is completely correct, and most of us have no clue what it is
talking abut!

-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] Re: How am I supposed to block the KDE update?

[Alan McKinnon]

On 14/03/2017 19:05, Nikos Chantziaras wrote:
> On 03/14/2017 06:34 PM, Alan McKinnon wrote:
>> Eek. That's not nice. You have masked frameworks-5.32.0 and plasma-5.9.3
>> packages (presumably you got all of them), and you missed something in
>> the huge chain that needs one or more of them.
> 
> Oops, you are absolutely correct. In fact, what I didn't mask is
> =kde-frameworks/plasma-5.32.0-r1.
> 
> And here's the funny part: I specifically only masked =*/*-5.32.0
> instead of ~*/*-5.32.0 so that I'll know when the bug gets potentially
> fixed; it would result in this exact kind of breakage I got, reminding
> me to try the update again.
> 
> So I'll be trying the update again to see if the plasma revbumb is there
> to actually fix the desktop again. (The issue was that hovering over
> icons or other items would highlight them but they would stay
> highlighted forever even after the mouse moved somewhere else or even if
> you click somewhere else. So everything would be full of highlighted
> icons.)


Ew. That would drive folks nuts after about 10 seconds!

> 
> Moral of the story: more coffee before posting :-P
> 
> 


-- 
Alan McKinnon
alan.mckin...@gmail.com

[gentoo-user] Re: Can't get rid of binutils 'preserved libs' warning

[Grant Edwards]

On 2017-03-14, Alan McKinnon  wrote:
> On 14/03/2017 17:45, Grant Edwards wrote:
>> After I do an update, I get this message:
>> 
>>   !!! existing preserved libs:
>>   >>> package: sys-libs/binutils-libs-2.27
>>*  - /usr/lib64/libbfd-2.25.1.so
>>*  used by 
>> /usr/lib64/binutils/x86_64-pc-linux-gnu/2.25.1/libopcodes-2.25.1.so 
>> (sys-devel/binutils-2.25.1-r1)
>>   Use emerge @preserved-rebuild to rebuild packages using these libraries
>> 
>> When I do an 'emerge @preserved-rebuild', it re-builds
>> binutils-2.25.1, and then shows the same warning again.
>> 
>> I've run @preserved-rebuild 5 or 6 times, sourcing /etc/profile and
>> logging out/in between.  Still, I always get the same preserved-libs
>> warning.
>> 
>> Portage seems upset tht binutils-2.25.1 is using binutils-libs-2.25.1
>> instead of binutils-libs-2.27, but re-emerging binutils-2.25.1 doesn't
>> help.
>
> I've run into similar things a few times and never really got to the
> bottom of any of them and ldd wasn't very useful either.
>
> How I have got around it in the past is to stop rebuilding, that just
> keeps the crazy loop going as each time the new thing doesn't like the
> existing thing. So I emerge -C the offending package and the
> dependencies, then emerge both back in so they start from scratch.

I had both binutils-2.25 and 2.26 installed, and when I did an emerge
--depclean, it wanted to uninstalled 2.25, so I let it do that.

I usually try to eliminate all portage warnings before doing
--depclean, but in this case, it seems to have solved the problem.  It
doesn't look like I needed binutils-2.25 -- so far...

-- 
Grant Edwards   grant.b.edwardsYow! Actually, what I'd
  at   like is a little toy
  gmail.comspaceship!!

Re: [gentoo-user] Recommended CDR-Burning-frontend without QT and without KDE?

[Joerg Schilling]

Miroslav Rovis  wrote:

> growisofs, cdrecord, and friends ...mkisofs for cdrecord, IIRC ...I use
> it rarely nowadays...
>
> but none (assisting other programs) actually if it's data to burn on DVD
> or BD, growisofs is fine solo there...

???

cdrecord supports DVDs since March 1998 which makes it the third DVD writing 
software worldwide and the first OSS DVD writing software.

cdrecord supports writing BD media since July 2007 which is nearly 10 years 
ago.

growisofs on the other side is unmaintained since 9 years and there already 
have been reported problems where growisofs could not be used while cdrecord 
works fine.


BTW: X-CD-Roast is still alive and works fine with cdrtools.

Jörg

-- 
 EMail:jo...@schily.net(home) Jörg Schilling D-13353 Berlin
joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
 URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/'

Re: [gentoo-user] Can't get rid of binutils 'preserved libs' warning

[Willie M]

On 03/14/2017 08:45 AM, Grant Edwards wrote:
> After I do an update, I get this message:
>
>   !!! existing preserved libs:
>   >>> package: sys-libs/binutils-libs-2.27
>*  - /usr/lib64/libbfd-2.25.1.so
>*  used by 
> /usr/lib64/binutils/x86_64-pc-linux-gnu/2.25.1/libopcodes-2.25.1.so 
> (sys-devel/binutils-2.25.1-r1)
>   Use emerge @preserved-rebuild to rebuild packages using these libraries
>
> When I do an 'emerge @preserved-rebuild', it re-builds
> binutils-2.25.1, and then shows the same warning again.
>
> I've run @preserved-rebuild 5 or 6 times, sourcing /etc/profile and
> logging out/in between.  Still, I always get the same preserved-libs
> warning.
>
> Portage seems upset tht binutils-2.25.1 is using binutils-libs-2.25.1
> instead of binutils-libs-2.27, but re-emerging binutils-2.25.1 doesn't
> help.
>

The abosolute only way I got that to quit telling me about a rebuild
about some dumb program was to uninstall and reinstall.

You won't be uninstalling using "emerge -av --depclean
=sys-libs/binutils-libs-2.27" becuase there will be dependancies.

You would have to "emerge -C =sys-libs/binutils-libs-2.27"

You can either reinstall it using "revdep-rebuild" or "emerge -1av
=sys-libs/binutils-libs-2.27"

Be warned the strip command is also part of the package. If I am not
mistaken strip is also used in building program to strip away un-needed
symbols and sections from files.

-- 

Willie L Matthews
matthews.willi...@gmail.com
702-659-9966




signature.asc
Description: OpenPGP digital signature

[gentoo-user] Re: How am I supposed to block the KDE update?

[Nikos Chantziaras]

On 03/14/2017 06:34 PM, Alan McKinnon wrote:

Eek. That's not nice. You have masked frameworks-5.32.0 and plasma-5.9.3
packages (presumably you got all of them), and you missed something in
the huge chain that needs one or more of them.


Oops, you are absolutely correct. In fact, what I didn't mask is 
=kde-frameworks/plasma-5.32.0-r1.


And here's the funny part: I specifically only masked =*/*-5.32.0 
instead of ~*/*-5.32.0 so that I'll know when the bug gets potentially 
fixed; it would result in this exact kind of breakage I got, reminding 
me to try the update again.


So I'll be trying the update again to see if the plasma revbumb is there 
to actually fix the desktop again. (The issue was that hovering over 
icons or other items would highlight them but they would stay 
highlighted forever even after the mouse moved somewhere else or even if 
you click somewhere else. So everything would be full of highlighted icons.)


Moral of the story: more coffee before posting :-P

Re: [gentoo-user] some capital B blockers in world update

[allan gottlieb]

On Tue, Mar 14 2017, Alan McKinnon wrote:

> On 14/03/2017 16:43, allan gottlieb wrote:
>> I update roughly twice a week.  On one machine (full output below) I was
>> told that libinput and evdev are blocking xorg-drivers
>> 
>> [blocks B ] > ("> x11-base/xorg-drivers-1.19)
>> [blocks B ] > ("> x11-base/xorg-drivers-1.19)
>> 
>> However the merge does propose to update xorg-drivers
>> [ebuild U ] x11-base/xorg-drivers-1.19 [1.18-r1] VIDEO_CARDS="-ark%
>> -i915% -i965% (-newport) -sis%"
>> 
>> It also proposes to update libinput and evdev
>> [ebuild U  ]   x11-drivers/xf86-input-libinput-0.24.0 [0.19.0]
>> [ebuild U  ]  x11-drivers/xf86-input-evdev-2.10.5 [2.10.3]
>> 
>> I do see that the versions of libinput and evdev to be used are higher
>> than the versions that would block xorg-drivers.  I am wondering why in
>> this case emerge is telling me about the block (in red with a capital B)
>> and more importantly would appreciate confirmation that I should let the
>> emerge proceed.
>
>
> Portage found a solution that satisfies all constraints, so you should
> let it proceed.
>
> Did you run emerge with -v to get the above?
> That looks like portage is doing it's usual -v thing which is to core
> dump to your console in the hope that maybe you can figure it out and
> you are willing to play the game called "let's find out what portage
> thinks it means today!"
>
> I don't understand why those blockers are marked hard, as portage found
> a solution. The blocker lines are really telling you why portage wants
> to upgrade your libinput and evdev drivers - the current ones won't work
> with your current drivers.
>
> Which is all totally pointless, as newer versions of everything are
> available and you want a full update. There's very little point in
> software going to great lengths to tell you why it won't keep old
> versions when you explicitly told it to not keep old versions :-)

Thank you for the confirmation!  I also doubt the use of B when b would
be appropriated.  No this was not a --verbose run.  I would guess that
output would be even less illuminating.

allan

Re: [gentoo-user] Can't get rid of binutils 'preserved libs' warning

[Alan McKinnon]

On 14/03/2017 17:45, Grant Edwards wrote:
> After I do an update, I get this message:
> 
>   !!! existing preserved libs:
>   >>> package: sys-libs/binutils-libs-2.27
>*  - /usr/lib64/libbfd-2.25.1.so
>*  used by 
> /usr/lib64/binutils/x86_64-pc-linux-gnu/2.25.1/libopcodes-2.25.1.so 
> (sys-devel/binutils-2.25.1-r1)
>   Use emerge @preserved-rebuild to rebuild packages using these libraries
> 
> When I do an 'emerge @preserved-rebuild', it re-builds
> binutils-2.25.1, and then shows the same warning again.
> 
> I've run @preserved-rebuild 5 or 6 times, sourcing /etc/profile and
> logging out/in between.  Still, I always get the same preserved-libs
> warning.
> 
> Portage seems upset tht binutils-2.25.1 is using binutils-libs-2.25.1
> instead of binutils-libs-2.27, but re-emerging binutils-2.25.1 doesn't
> help.
> 

I've run into similar things a few times and never really got to the
bottom of any of them and ldd wasn't very useful either.

How I have got around it in the past is to stop rebuilding, that just
keeps the crazy loop going as each time the new thing doesn't like the
existing thing. So I emerge -C the offending package and the
dependencies, then emerge both back in so they start from scratch.

But in this case, removing binutils might be problematic, that's where
your elf tools and linker come from. A workaround comes to mind:

- quickpkg both packages
- emerge -C both packages
- manually untar both quickpkg archives to their original location. Now
you have all your tools back, without the package metadata to confuse
portage
- emerge both packages, ignoring the expected file collision errors.

-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] some capital B blockers in world update

[Alan McKinnon]

On 14/03/2017 16:43, allan gottlieb wrote:
> I update roughly twice a week.  On one machine (full output below) I was
> told that libinput and evdev are blocking xorg-drivers
> 
> [blocks B  ]   (" x11-base/xorg-drivers-1.19)
> [blocks B  ]   (" x11-base/xorg-drivers-1.19)
> 
> However the merge does propose to update xorg-drivers
> [ebuild U  ] x11-base/xorg-drivers-1.19 [1.18-r1] VIDEO_CARDS="-ark% 
> -i915% -i965% (-newport) -sis%" 
> 
> It also proposes to update libinput and evdev
> [ebuild U  ]   x11-drivers/xf86-input-libinput-0.24.0 [0.19.0]
> [ebuild U  ]  x11-drivers/xf86-input-evdev-2.10.5 [2.10.3]
> 
> I do see that the versions of libinput and evdev to be used are higher
> than the versions that would block xorg-drivers.  I am wondering why in
> this case emerge is telling me about the block (in red with a capital B)
> and more importantly would appreciate confirmation that I should let the
> emerge proceed.


Portage found a solution that satisfies all constraints, so you should
let it proceed.

Did you run emerge with -v to get the above?
That looks like portage is doing it's usual -v thing which is to core
dump to your console in the hope that maybe you can figure it out and
you are willing to play the game called "let's find out what portage
thinks it means today!"

I don't understand why those blockers are marked hard, as portage found
a solution. The blocker lines are really telling you why portage wants
to upgrade your libinput and evdev drivers - the current ones won't work
with your current drivers.

Which is all totally pointless, as newer versions of everything are
available and you want a full update. There's very little point in
software going to great lengths to tell you why it won't keep old
versions when you explicitly told it to not keep old versions :-)



> 
> thanks in advance,
> allan
> 
> [nomerge   ] x11-base/xorg-x11-7.4-r2 
> [nomerge   ]  media-fonts/font-daewoo-misc-1.0.3 
> [nomerge   ]   x11-apps/bdftopcf-1.0.5 
> [ebuild U  ]x11-libs/libXfont-1.5.2 [1.5.1]
> [nomerge   ] x11-apps/xdm-1.1.11-r3 
> [ebuild U  ]  x11-apps/xconsole-1.0.7 [1.0.6]
> [nomerge   ] app-office/libreoffice-5.2.3.3-r1 
> [nomerge   ]  sci-mathematics/lpsolve-5.5.2.0 
> [nomerge   ]   sci-libs/colamd-2.8.0 
> [ebuild U  ]sci-libs/suitesparseconfig-4.2.1-r1 [4.2.1] 
> ABI_X86="(64%*) -32% (-x32)" 
> [nomerge   ] gnome-base/gnome-3.20.0 
> [nomerge   ]  gnome-base/gnome-extra-apps-3.20.0 
> [nomerge   ]   gnome-extra/gnome-characters-3.20.1 
> [ebuild U  ]dev-libs/libunistring-0.9.7 [0.9.5] ABI_X86="(64%*) -32% 
> (-x32)" 
> [nomerge   ] media-video/gnome-mplayer-1.0.9 
> [nomerge   ]  x11-themes/gnome-icon-theme-symbolic-3.12.0 
> [nomerge   ]   x11-misc/icon-naming-utils-0.8.90 
> [nomerge   ]dev-perl/XML-Simple-2.200.0-r1 
> [ebuild U  ] dev-perl/XML-LibXML-2.12.800-r1 [2.12.100] 
> USE="-examples% -minimal%" 
> [ebuild U  ] www-client/firefox-45.8.0 [45.7.0]
> [ebuild U  ] www-client/chromium-57.0.2987.98 [56.0.2924.76-r1] 
> USE="system-libvpx%* -component-build% -gconf%" 
> [nomerge   ] gnome-base/gnome-3.20.0 
> [nomerge   ]  gnome-base/gnome-core-apps-3.20.0 
> [nomerge   ]   gnome-base/gnome-control-center-3.20.2-r1 
> [nomerge   ]x11-drivers/xf86-input-libinput-0.24.0 [0.19.0]
> [nomerge   ] x11-base/xorg-server-1.19.2 [1.18.4] USE="-debug%" 
> [nomerge   ]  x11-base/xorg-drivers-1.19 [1.18-r1] VIDEO_CARDS="-ark% 
> -i915% -i965% (-newport) -sis%" 
> [ebuild U  ]   x11-drivers/xf86-input-synaptics-1.9.0 [1.8.3]
> [ebuild U  ]   x11-drivers/xf86-video-intel-2.99.917_p20170216 
> [2.99.917_p20160621-r1] USE="-tools%" 
> [ebuild U  ] net-misc/wget-1.19.1-r1 [1.18]
> [ebuild U  ] x11-base/xorg-drivers-1.19 [1.18-r1] VIDEO_CARDS="-ark% 
> -i915% -i965% (-newport) -sis%" 
> [ebuild U  ]  x11-drivers/xf86-input-evdev-2.10.5 [2.10.3]
> [nomerge   ] x11-base/xorg-drivers-1.19 [1.18-r1] VIDEO_CARDS="-ark% 
> -i915% -i965% (-newport) -sis%" 
> [ebuild U  ]   x11-drivers/xf86-input-libinput-0.24.0 [0.19.0]
> [ebuild U  ]x11-base/xorg-server-1.19.2 [1.18.4] USE="-debug%" 
> [ebuild U  ] x11-apps/xauth-1.0.10 [1.0.9-r2] USE="{-test}" 
> [ebuild U  ]dev-libs/libinput-1.6.2 [1.4.2]
> [nomerge   ] net-libs/webkit-gtk-2.14.5 
> [ebuild U  ]  x11-libs/cairo-1.14.8 [1.14.6]
> [nomerge   ] x11-base/xorg-x11-7.4-r2 
> [ebuild U  ]  x11-apps/sessreg-1.1.1 [1.1.0]
> [nomerge   ] x11-base/xorg-drivers-1.19 [1.18-r1] VIDEO_CARDS="-ark% 
> -i915% -i965% (-newport) -sis%" 
> [nomerge   ]   x11-drivers/xf86-input-evdev-2.10.5 [2.10.3]
> [nomerge   ]x11-base/xorg-server-1.19.2 [1.18.4] USE="-debug%" 
> [ebuild  N ] x11-libs/libXfont2-2.0.1  USE="bzip2 ipv6 truetype -doc 
> -static-libs" 
> [ebuild U  ]dev-libs/libevdev-1.5.6 [1.5.2]
> [nomerge   ] 

Re: [gentoo-user] How am I supposed to block the KDE update?

[Alan McKinnon]

On 14/03/2017 17:45, Nikos Chantziaras wrote:
> Updading to kde-frameworks 5.32 breaks my desktop. So I masked it. Meaning:
> 
>   =kde-frameworks/attica-5.32.0
>   =kde-frameworks/breeze-icons-5.32.0
>   =kde-frameworks/extra-cmake-modules-5.32.0
>   # ... and all the rest
> 
> in /etc/portage/package.mask/kdeframeworks
> 
> That worked for a couple days. Not anymore. Now I can't update my system
> anymore, since emerge -uDN @world aborts:
> 
>   The following mask changes are necessary to proceed:
>(see "package.unmask" in the portage(5) man page for more details)
>   # required by kde-misc/kshutdown-4.0::gentoo[kde]
>   # required by @selected
>   # required by @world (argument)
>   # /etc/portage/package.mask/kde:
>   #=kde-frameworks/kdelibs-4.14.29-r1
>   #=kde-frameworks/kdelibs-env-4.14.3
>   #=kde-frameworks/kf-env-4
>   =kde-frameworks/kglobalaccel-5.32.0
>   # required by kde-plasma/ksshaskpass-5.9.3::gentoo
>   # required by kde-plasma/plasma-meta-5.9.3::gentoo
>   # required by @selected
>   # required by @world (argument)
>   # /etc/portage/package.mask/kde:
>   =kde-frameworks/kcoreaddons-5.32.0
>   # required by kde-plasma/kdeplasma-addons-5.9.3::gentoo
>   # required by kde-plasma/plasma-meta-5.9.3::gentoo
>   # required by @selected
>   # required by @world (argument)
>   # /etc/portage/package.mask/kde:
>   =kde-frameworks/kcompletion-5.32.0
> 
> (This are just the first lines. The full error output is huge.)
> 
> So what am I supposed to do?

Eek. That's not nice. You have masked frameworks-5.32.0 and plasma-5.9.3
packages (presumably you got all of them), and you missed something in
the huge chain that needs one or more of them. More likely, something
else needs that something, and a third something else needs the first
something else.

Yeah, with enough patience you *could* follow the chain all the way down
and mask every last bit that needs masking. That's a lot of work and
you'll undo it in a week when the desktop breakage is fixed :-)

I'd say it's just not worth the effort (unless someone else posts a
proper list they already worked out).

Probably *much* easier to deal with frameworks breaking your desktop in
the first sentence. Would you be OK to deal with that rather than try
the masking route? What's the breakage you mention?


-- 
Alan McKinnon
alan.mckin...@gmail.com

[gentoo-user] How am I supposed to block the KDE update?

[Nikos Chantziaras]

Updading to kde-frameworks 5.32 breaks my desktop. So I masked it. Meaning:

  =kde-frameworks/attica-5.32.0
  =kde-frameworks/breeze-icons-5.32.0
  =kde-frameworks/extra-cmake-modules-5.32.0
  # ... and all the rest

in /etc/portage/package.mask/kdeframeworks

That worked for a couple days. Not anymore. Now I can't update my system 
anymore, since emerge -uDN @world aborts:


  The following mask changes are necessary to proceed:
   (see "package.unmask" in the portage(5) man page for more details)
  # required by kde-misc/kshutdown-4.0::gentoo[kde]
  # required by @selected
  # required by @world (argument)
  # /etc/portage/package.mask/kde:
  #=kde-frameworks/kdelibs-4.14.29-r1
  #=kde-frameworks/kdelibs-env-4.14.3
  #=kde-frameworks/kf-env-4
  =kde-frameworks/kglobalaccel-5.32.0
  # required by kde-plasma/ksshaskpass-5.9.3::gentoo
  # required by kde-plasma/plasma-meta-5.9.3::gentoo
  # required by @selected
  # required by @world (argument)
  # /etc/portage/package.mask/kde:
  =kde-frameworks/kcoreaddons-5.32.0
  # required by kde-plasma/kdeplasma-addons-5.9.3::gentoo
  # required by kde-plasma/plasma-meta-5.9.3::gentoo
  # required by @selected
  # required by @world (argument)
  # /etc/portage/package.mask/kde:
  =kde-frameworks/kcompletion-5.32.0

(This are just the first lines. The full error output is huge.)

So what am I supposed to do?

I don't get it :-/

[gentoo-user] Can't get rid of binutils 'preserved libs' warning

[Grant Edwards]

After I do an update, I get this message:

  !!! existing preserved libs:
  >>> package: sys-libs/binutils-libs-2.27
   *  - /usr/lib64/libbfd-2.25.1.so
   *  used by 
/usr/lib64/binutils/x86_64-pc-linux-gnu/2.25.1/libopcodes-2.25.1.so 
(sys-devel/binutils-2.25.1-r1)
  Use emerge @preserved-rebuild to rebuild packages using these libraries

When I do an 'emerge @preserved-rebuild', it re-builds
binutils-2.25.1, and then shows the same warning again.

I've run @preserved-rebuild 5 or 6 times, sourcing /etc/profile and
logging out/in between.  Still, I always get the same preserved-libs
warning.

Portage seems upset tht binutils-2.25.1 is using binutils-libs-2.25.1
instead of binutils-libs-2.27, but re-emerging binutils-2.25.1 doesn't
help.

-- 
Grant Edwards   grant.b.edwardsYow! Is it 1974?  What's
  at   for SUPPER?  Can I spend
  gmail.commy COLLEGE FUND in one
   wild afternoon??

[gentoo-user] some capital B blockers in world update

[allan gottlieb]

I update roughly twice a week.  On one machine (full output below) I was
told that libinput and evdev are blocking xorg-drivers

[blocks B  ]  

Re: [gentoo-user] [SOLVED] date+filename

[thelma]

On 03/14/2017 04:51 AM, Neil Bothwick wrote:
> On Mon, 13 Mar 2017 17:10:40 -0600, the...@sys-concept.com wrote:
> 
>> I'm trying to add to Xface menu: Configure Custom Actions
>> This:
>> pdfunite %N folder/`date +%F`-output.pdf
>>
>> The file in dir folder gets created ("-output.pdf") but is missing the
>> date.
>>
>> This works from command line:
>> pdfunite 1.pdf 2.pdf folder/`date +%F`-output.pdf
> 
> Command substitution is a shell feature, so it may h=not work elsewhere.
> The solution may be to write a one line shell script and have XFCE call
> that.
> 
> #!/bin/sh
> pdfunite $* $(date +%F)-output.pdf

Yes, that is what I end up doing, calling a bash script, it is easier to
implement.

pdfunite %N pdfunite-join.pdf && sh combine_files.sh

--
Thelma

Re: [gentoo-user] date+filename

[thelma]

On 03/14/2017 04:40 AM, Hogren wrote:
> Hello,
> 
> Did you try with the alternative substitution syntax ("$(date +%F)" in
> place of "`date +%F`") ?
> 
> Did you try to replace "%F" with "%Y-%m-%d" ?
> 
> Did you try to escape the % ("\%")?
> 
> I don't know Xface, so I give you advices with my Bash skills.
> 
> Good luck.
> 
> 
> Hogren
> 
> 
> On 14/03/2017 00:10, the...@sys-concept.com wrote:
>> I'm trying to add to Xface menu: Configure Custom Actions
>> This:
>> pdfunite %N folder/`date +%F`-output.pdf
>>
>> The file in dir folder gets created ("-output.pdf") but is missing the date.
>>
>> This works from command line:
>> pdfunite 1.pdf 2.pdf folder/`date +%F`-output.pdf
>>
>> What kind of bracket am I missing?

I've tried all brackets () quotes "`$ nothing works
I don't know why they make it different from standard Bash commands.

--
Thelma

Re: [gentoo-user] date+filename

[Neil Bothwick]

On Mon, 13 Mar 2017 17:10:40 -0600, the...@sys-concept.com wrote:

> I'm trying to add to Xface menu: Configure Custom Actions
> This:
> pdfunite %N folder/`date +%F`-output.pdf
> 
> The file in dir folder gets created ("-output.pdf") but is missing the
> date.
> 
> This works from command line:
> pdfunite 1.pdf 2.pdf folder/`date +%F`-output.pdf

Command substitution is a shell feature, so it may h=not work elsewhere.
The solution may be to write a one line shell script and have XFCE call
that.

#!/bin/sh
pdfunite $* $(date +%F)-output.pdf


-- 
Neil Bothwick

Top Oxymorons Number 44: Advanced BASIC


pgpI9parVwFl1.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] invitation to gentobb project

[Ural]

Daniel Campbell:
> On Sun, Mar 12, 2017 at 08:56:00PM +, Ural wrote:
>> Hello guys. I am sorry about a bit of offtopic, but if everyone is
>> interested, I am inviting anyone into
>> https://github.com/edannenberg/gentoo-bb project discussion thread here:
>> https://github.com/edannenberg/gentoo-bb/issues/102, where we user
>> Docker as engine and Gentoo GNU/Linux as host OS. We have some ideas on
>> (possibly) the best server and LAMP/LEMP management using Gentoo, Docker
>> and GentooBB. Discussing the most table, fastest and secure dedicated
>> server configuration to host everything. Thanks
>>
> 
> The concept sounds pretty neat; what do you guys do different than a
> typical Gentoo installation?
> 
> What does Gentoo do for a containerized environment? Does this project
> include easier container management than usual? I like the
> containers-as-services idea. If it's not hard to write/make one, I could
> see this project taking off.

The idea of this project is very simple. Manage containers, based on
Gentoo. The only OS you can configure everything. I.E. -march=native,
which decreases php memory usage by 25% and accelerates binaries.

But in usual way, you will do
# docker import stage3-xxx.tar.bz2 gentoo
and emerge needed service, like nginx, mariadb or php.
This way you will have bunch of unmanaged >1GB containers, which have
90% unneded files and is hard to update.

Our project solves this problem. You have bunch of preconfigured
packages, which you already can install and use. Or you can easily
create yours. The images are layered and nested, and your nginx
container will be 17MB and have only what it need.
You can easily rebuild/upgrade/recompile any container, or upgrade all
at once. You just define all settings once.
Example. To build php7 container, it will build busybox, glibc, openssl,
and then including all previous containers will create a resulting
nested container. So you have only one glibc or one bash for all child
containers. So you can take one container as source, add to it a package
and have another nested container.

Why this 'container-per-service' is the best way?
* Security. Containers are just isolated from host OS, thanks to
cgroups, and if hijacked, don't access your rest system. That way if I
use separate php containers for phpBB, piwik and other community-driven
projects, hijacking phpBB will not allow access to rest services. Most
containers runs unprivileged.

* No any overhead. It is just another namespace inside kernel.

* Ability to have blk and cpu priorities for different services, even
when it is not possible to assign in usual native way, like priority for
a mariadb database. If you have 3 mariadb containers, you can easily
manage priorities as needed.

* Easy to upgrade on production, preserving old versions. I described my
way to do this in referenced issue, and I have just a few seconds of
downtime, when I turn off old containers and start new, but all configs
and data are mounted as volumes. If something is not well with upgraded
containers, I can switch it back temporarily.

* This project is already working well, mostly stable and is used on
production. All I did was edited package config files for my need, and
./main.sh build mynamespace. It builds all packages, emerging latest
versions and compiling them from scratch, creating docker containers.
After all built, you start using your containers.

(the developing is going in spring branch and soon we will have big
version update)



> 
> Thanks for sharing!
> 

Re: [gentoo-user] date+filename

[Hogren]

Hello,

Did you try with the alternative substitution syntax ("$(date +%F)" in
place of "`date +%F`") ?

Did you try to replace "%F" with "%Y-%m-%d" ?

Did you try to escape the % ("\%")?

I don't know Xface, so I give you advices with my Bash skills.

Good luck.


Hogren


On 14/03/2017 00:10, the...@sys-concept.com wrote:
> I'm trying to add to Xface menu: Configure Custom Actions
> This:
> pdfunite %N folder/`date +%F`-output.pdf
>
> The file in dir folder gets created ("-output.pdf") but is missing the date.
>
> This works from command line:
> pdfunite 1.pdf 2.pdf folder/`date +%F`-output.pdf
>
> What kind of bracket am I missing?
>

Re: [gentoo-user] invitation to gentobb project

[Daniel Campbell]

On Sun, Mar 12, 2017 at 08:56:00PM +, Ural wrote:
> Hello guys. I am sorry about a bit of offtopic, but if everyone is
> interested, I am inviting anyone into
> https://github.com/edannenberg/gentoo-bb project discussion thread here:
> https://github.com/edannenberg/gentoo-bb/issues/102, where we user
> Docker as engine and Gentoo GNU/Linux as host OS. We have some ideas on
> (possibly) the best server and LAMP/LEMP management using Gentoo, Docker
> and GentooBB. Discussing the most table, fastest and secure dedicated
> server configuration to host everything. Thanks
> 

The concept sounds pretty neat; what do you guys do different than a
typical Gentoo installation?

What does Gentoo do for a containerized environment? Does this project
include easier container management than usual? I like the
containers-as-services idea. If it's not hard to write/make one, I could
see this project taking off.

Thanks for sharing!


signature.asc
Description: Digital signature

Re: [gentoo-user] Re: OpenGL problem after upgrading mesa and xorg-server

[Miroslav Rovis]

On 170314-06:18+, J. Roeleveld wrote:
> On March 14, 2017 6:57:59 AM GMT+01:00, Miroslav Rovis 
>  wrote:
...
> >/etc/portage/package.mask/package.mask.file:>=media-libs/mesa-13.0.0
> >
> >( Btw. how does one search for only recent bugs, anybody? )
> 
> To see most recent bugs, sort on ID.
> To see most recently modified bug, sort on changed.
> 
> (Click on the column headers)

Yes, it was right there for my understanding... Thanks!

Can an address this long be sent, and received, in an email correctly? :
"https://bugs.gentoo.org/buglist.cgi?bug_status=UNCONFIRMED_status=CONFIRMED_status=IN_PROGRESS=alias=short_desc=changeddate
 DESC%2Cbug_id 
DESC_format=advanced=substring=substring=mesa=mesa"

Anyway, it's, currently, 15 bugs that have the status changed with the latest
timestamp somewhere in 2017.  What's happening in that development?

Maybe what happens will be something like what happened with syslog-ng, where
we kind of have this mid-2014 created ebuild (only be looking in Changelog 
which I wasn't able to find on the gitweb, but in portage:

# cat /usr/portage/app-admin/syslog-ng/ChangeLog-2015
...
*syslog-ng-3.4.8 (06 Jun 2014)

 06 Jun 2014; Michael Sterrett  +syslog-ng-3.4.8.ebuild:
 version bump for 3.4 branch

 17 May 2014; Michael Sterrett  -syslog-ng-3.4.2.ebuild,
 -syslog-ng-3.5.4.ebuild:
 clean old
...

):

https://gitweb.gentoo.org/repo/gentoo.git/tree/app-admin/syslog-ng/syslog-ng-3.4.8.ebuild
for almost forever...

(
I still have:
# grep -r syslog-ng /etc/portage/p*
/etc/portage/package.keywords/package.keywords.file:=app-admin/syslog-ng-3.4.8
/etc/portage/package.mask/package.mask.file:>=app-admin/syslog-ng-3.5.6
#
because there really were issues:
app-admin/syslog-ng-3.6.2: scary time stamp jumps
https://bugs.gentoo.org/show_bug.cgi?id=533328
and:
Kernel log message time drift #121
https://github.com/balabit/syslog-ng/issues/121
which I described in:
Syslog-ng from Delay Logging to BrokenPipe/no Logging
http://forums.gentoo.org/viewtopic-t-1001994.html
)

No time to investigate mesa... Anybody can give us a summary of what's really
going on upstream with mesa?

-- 
Miroslav Rovis
Zagreb, Croatia
https://www.CroatiaFidelis.hr


signature.asc
Description: Digital signature

Re: [gentoo-user] Re: OpenGL problem after upgrading mesa and xorg-server

[J. Roeleveld]

On March 14, 2017 6:57:59 AM GMT+01:00, Miroslav Rovis 
 wrote:
>On 170314-05:32+0100, wabe wrote:
>> wabe  wrote:
>> 
>> > Since I've upgraded mesa (12.0.1 to 13.0.5) and xorg-server 
>> > (1.18.4 to 1.19.2), OpenGL programs don't work any longer for 
>> > non-root users, even when these users are members of the group 
>> > "video".
>...
>> > 
>> > I searched the web and also read the gentoo xserver wiki but
>> > couldn't find a solution.
>> 
>> P.S.: After downgrading mesa to 12.0.1 everything works fine again.
>> So the problem has nothing to do with xorg-server.
>
>Lots of bugs with mesa, esp. recently:
>https://bugs.gentoo.org/buglist.cgi?quicksearch=mesa
>
>I masked it for now (if I had time, I'd contribute reports...):
>
>/etc/portage/package.mask/package.mask.file:>=media-libs/mesa-13.0.0
>
>( Btw. how does one search for only recent bugs, anybody? )

To see most recent bugs, sort on ID.
To see most recently modified bug, sort on changed.

(Click on the column headers)
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] Re: OpenGL problem after upgrading mesa and xorg-server

[Miroslav Rovis]

On 170314-05:32+0100, wabe wrote:
> wabe  wrote:
> 
> > Since I've upgraded mesa (12.0.1 to 13.0.5) and xorg-server 
> > (1.18.4 to 1.19.2), OpenGL programs don't work any longer for 
> > non-root users, even when these users are members of the group 
> > "video".
...
> > 
> > I searched the web and also read the gentoo xserver wiki but
> > couldn't find a solution.
> 
> P.S.: After downgrading mesa to 12.0.1 everything works fine again.
> So the problem has nothing to do with xorg-server.

Lots of bugs with mesa, esp. recently:
https://bugs.gentoo.org/buglist.cgi?quicksearch=mesa

I masked it for now (if I had time, I'd contribute reports...):

/etc/portage/package.mask/package.mask.file:>=media-libs/mesa-13.0.0

( Btw. how does one search for only recent bugs, anybody? )

-- 
Miroslav Rovis
Zagreb, Croatia
https://www.CroatiaFidelis.hr


signature.asc
Description: Digital signature