[gentoo-user] Networkmanager Auto Connect

[Silvio Siefke]

Hello, 

since networkmanger version 1.4 auto connect with wlan not work anymore
when logged in. Have someone same problem? Could find fix?

siefke@sisibox ~ $ find /var/db/pkg -name "networkmanager*" -type d
/var/db/pkg/net-misc/networkmanager-1.4.2
/var/db/pkg/net-misc/networkmanager-openvpn-1.2.6


siefke@sisibox ~ $ equery u networkmanager | cut -c -30
-audit
+bluetooth
+connection-sharing
+consolekit
+dhclient
-gnutls
+introspection
-json
+modemmanager
-ncurses
+nss
-ofono
+ppp
+resolvconf
-systemd
-teamd
-test
+vala
-wext
+wifi

Thank you & Nice Day
Silvio 


pgp1xIuMFg26q.pgp
Description: PGP signature

Re: [gentoo-user] Madly flickering display

[Peter Humphrey]

On Friday 23 Sep 2016 10:36:23 J. Roeleveld wrote:
> On Friday, September 23, 2016 09:13:00 AM Peter Humphrey wrote:
--->8
> > I still get the rapid flickering and general confusion though, which is
> > cured by logging out and in again.
> 
> I just tested on my desktop by madly switching desktops for 2 minutes
> using the keyboard bindings (CTRL + F1..4) and didn't see this happening.
> > * That was the only relevant package to have such a USE flag, according
> > to "equery h -p evdev".

I can't yet prove it, but I think I know the culprit: BOINC manager. If I 
don't run it, I get all my desktops running properly, but if I do, the 
window manager gets confused about which desktop is on display and tries to 
display bits of several of them, overlapping, missing, showing through, 
flickering, you name it. The bug persists even if I shut down boincmgr 
before the problem appears.

It may have something to do with focus stealing, because I had to raise the 
prevention setting one or two notches to be able to switch away from 
boincmgr's desktop. If it is so, I suppose it's a consequence of coding for 
Windows with only a single desktop in the entire known universe.

-- 
Rgds
Peter

Re: [gentoo-user] GTK+ circular dependency

[Stroller]

> On 13 Oct 2016, at 18:01, Daniel Quinn  wrote:
> 
> On 13/10/16 02:36, wabe wrote:
>> Since the update process is dead slow anyway and I really don't care
> about a few minutes less ore more, I always use --backtrack=999.
> 
> Unfortunately yes.  I took your advice just now and it's still
> complaining about circular dependencies.  Maybe I'm missing something,
> but how can gtk+ *depend* on gtk-engines-adwaita?

If you look in the ebuilds:

• gtk+-2.24.31-r1 depends upon x11-themes/gtk-engines-adwaita, [1] and
• gtk-engines-adwaita-3.20.2 depends upon >=x11-libs/gtk+-2.24.15 [2]

If you look at the packages page for x11-libs/gtk+ [3], you'll see there are 
some earlier versions of it in the tree that fulfils gtk-engines-adwaita's 
requirement, x11-libs/gtk+-2.24.28-r1 for example.

x11-libs/gtk+-2.24.28-r1 does not seem to require gtk-engines-adwaita. [4]

So you should be able to `emerge -1 =x11-libs/gtk+-2.24.28-r1` and then `emerge 
-1 gtk-engines-adwaita` should pull in the 3.20.2 version of it.

You can then, for good measure, update gtk+ to version 2.24.31-r1 (`emerge -1 
=x11-libs/gtk+-2.24.31-r1`), I think.

Stroller.



[1] 
https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-libs/gtk+/gtk+-2.24.31-r1.ebuild
[2] 
https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-themes/gtk-engines-adwaita/gtk-engines-adwaita-3.20.2.ebuild
[3] https://packages.gentoo.org/packages/x11-libs/gtk+
[4] 
https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-libs/gtk+/gtk+-2.24.28-r1.ebuild