Bug#849077: new version of wpa-supplicant uploaded -- please test

On Thu, 26 Jan 2017 18:36:08 +0100 Andrew Shadura wrote: > I have cherry-picked a few patches from the upstream Git repository. I tried this on my mbpr 11,1 with wl.ko and still same result. Scan failure in endless loop return -22 just like in my previously attached log dump.

Bug#849077: [pkg-wpa-devel] Bug#849077: wpasupplicant: [Regression] Updating wpasupplicant makes not possible to connect to encrypted WiFi

I will again reference my comment https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849077#45 I'm encountering this bug without NetworkManager, wicd or anything else, just a simple wpa_supplicant config file which has worked fine until wpa_supplicant update and then stopped working, no other

Bug#849077: [pkg-wpa-devel] Bug#849077: wpasupplicant: [Regression] Updating wpasupplicant makes not possible to connect to encrypted WiFi

my machine is having an identical looping scan failure messages as did the submitter after recent update. worked: 2.5-2+v2.4-3+b1 broken: 2.6-2 device: 03:00.0 Network controller: Broadcom Limited BCM4360 802.11ac Wireless Network Adapter (rev 03) driver: Broadcom BCM43a0 802.11 Hybrid

Bug#824853: tex-common: package installation fails

Installing the package 'context' (which also provides "syst-tex.mkii" albeit in a different location) seems to fix this also; tex packages upgrade and can finish install without issues afterwards.

Bug#814394: xserver-xorg-legacy: Fails to start xserver after upgrade to 1.18.1

Julien Cristau on 2016/02/13 +0100 @11:30:30: > > startx does not longer work after upgrade; `grep EE > > Xorg.log' shows: > > > >[ 1463.840] (EE) systemd-logind: failed to get > >session: The name org.freedesktop.login1 was not > >provided by any .service files > > X requires

Bug#802544: Xorg.wrap move to xorg-legacy broke X startup (permissions)

Julien Cristau on 2015/10/22 +0200 @07:47:28: > > That would surely be a regression. Debian went > > from a working X that dropped privileges, to a > > non-working X that can only be run as root. Huh?? > > No, Debian is going from an X server that always runs > as root to one that can run as

Bug#802544: Xorg.wrap move to xorg-legacy broke X startup (permissions)

Julien Cristau on 2015/10/21 +0200 @20:48:56: > > xserver-xorg-core:amd64 (1.17.2-1.1, 1.17.2-3) > > > > This upgrade has broken X startup for me. Here is how > > I start X (as ordinary user): > > > > exec setsid env -i \ > > ... > > X :0 vt63 \ > > So one solution is to

Bug#802544: Xorg.wrap move to xorg-legacy broke X startup (permissions)

Package: xserver-xorg-legacy Version: 2:1.17.2-3 Severity: grave I recently did an upgrade of X, which broke it on my machine. Here are old (working) and new (broken) versions that apt-get installed, as shown in /var/log/apt/history.log: xserver-xorg-core:amd64 (1.17.2-1.1, 1.17.2-3) This