** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576024
Title:
Wifi "device not ready" after booting into OS for the 1st time
T
** Also affects: wpa (Debian)
Importance: Undecided
Status: New
** Changed in: wpa (Debian)
Importance: Undecided => Wishlist
** Changed in: wpa (Debian)
Status: New => Fix Released
** Changed in: wpa (Debian)
Assignee: (unassigned) => Andrej Shadura (andrew.sh)
--
You
@cyphermox, has there been any proper solution of this since then? Is
the patch still needed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576024
Title:
Wifi "device not ready" after booting into
Any progress in seeing this fixed in Xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576024
Title:
Wifi "device not ready" after booting into OS for the 1st time
To manage notifications abou
Note that this should be rebased on 6.2 now that a security release was
published without the 6.1 changes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576024
Title:
Wifi "device not ready" after
I see there are some nplan regressions for this upload. I looked at them
briefly and I see that the nplan testsuite is in terrible shape and
tends to just fail a lot, so they're probably are unrelated, but could
the uploader please take a look and double-confirm? I can then release
this fix to -upd
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576024
Title:
Wifi "device not ready" after booting into OS for the
wpasupplicant 2.4-0ubuntu6.1 amd64 fixed it for me.
My case was going from graphical.target to multi-user.target and back to
graphical.target.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576024
Ti
Hello Kristin, or anyone else affected,
Accepted wpa into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/wpa/2.4-0ubuntu6.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubu
** Changed in: network-manager (Ubuntu Xenial)
Status: Confirmed => Invalid
** Description changed:
+ [Impact]
+ Users booting from OEM setup may find that their wireless device is "not
ready" as per NetworkManager, because wpasupplicant is not running. This is
because the steps taken to
Shall the WPA package be updated in 16.04 ? I guess the impact is so
limited that it's possible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576024
Title:
Wifi "device not ready" after booting in
This affects the entire Ekimia product line also ( intel 8285 M.2 )
We will apply the patch for WPA
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576024
Title:
Wifi "device not ready" after bootin
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: wpa (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576024
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576024
Tit
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15760
Yes, I believe this still affects 16.04. I applied the patch on machines
that System76 ships, but it is not upstream. It is the same patch as was
applied to 17.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Hi, is this issue released with Ubuntu 16.04.2 LTS. I am still
experiencing this one. If not what should be done exactly to fix it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576024
Title:
Wifi
This bug was fixed in the package wpa - 2.4-0ubuntu9
---
wpa (2.4-0ubuntu9) zesty; urgency=medium
* debian/patches/wpa_service_ignore-on-isolate.patch: add IgnoreOnIsolate=yes
so that when switching "runlevels" in oem-config will not kill off wpa
and cause wireless to be una
** Changed in: network-manager (Ubuntu)
Status: Triaged => Invalid
** Changed in: network-manager (Ubuntu)
Milestone: ubuntu-16.04.2 => None
** Also affects: network-manager (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: ubiquity (Ubuntu Xenial)
Import
Would it be acceptable to have a patch to `wpa` to add `IgnoreOnIsolate`
for the time being? If we hold it in the Ubuntu debian/patches then we
can wait for a better solution to be done upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Here is how I have been working around this bug for System76's machines:
https://launchpadlibrarian.net/303137969/wpa_2.4-0ubuntu6_2.4-0ubuntu7~system76~1.diff.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
It's exactly as Jeremy points out -- NM should be detecting that
wpasupplicant is not running and start it -- this should already have
been working by way of wpasupplicant being dbus-activated.
The isolate command is there for a good reason. We want a dramatically
different environment while oem-c
Adding an oem-config/ubiquity task in case it turns out it needs to be
fixed there.
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu)
Status: New => Incomplete
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
Let's wait for Mathieu's opinion.
This seems like a good candidate for 16.04.2 if we can get it fixed in
time.
** Changed in: network-manager (Ubuntu)
Milestone: None => ubuntu-16.04.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Yes, I am. I just need to know what is permissible - we can add
IgnoreOnIsolate in a ubuntu patch but it seems like the source of the
issue is in network manager - it should detect that wpa supplicant is
not running and restart it dynamically.
--
You received this bug notification because you are
The call was added by Mathieu in bin/oem-config-firstboot when he added
systemd support, subscribing him to the bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576024
Title:
Wifi "device not read
rbasak: I guess what you said -- find out who added that isolate c
all there
Let's set this to Triaged, as Jeremy appears to have pinned down the
cause so it's solely in the realm of "developers" now. The affected
package may need to change as we figure out where it should go.
Jeremy: are you co
rbasak: hmm, jackpot51 isn't here, but "isolate" is pretty much de
fined as "stop everything which is not part of the given target"
so this sounds like a case of YAFIYGI to me -- isolate isn't somet
hing which users should ever want to actually use...
--
You received this bug notification beca
I suggest talking to the person who wrote the "systemctl isolate ..."
line in the first place. Did that line come from Debian?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576024
Title:
Wifi "devi
By the way, it is possible to trigger the bug running on your own
system. All you have to do is run `sudo systemctl isolate
default.target` while connected to WiFi
Bluetooth may also go down.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
This is caused by wpa_supplicant being killed by systemctl isolate in
oem-config-firstboot
A potential fix is to add IgnoreOnIsolate=true to [Unit] in
wpa_supplicant.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Experience the same on a new Macbook Air running Kubuntu 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576024
Title:
Wifi "device not ready" after booting into OS for the 1st time
To manage
This affects the entire System76 product line, including:
Lemur 6, Lemur 7, Gazelle 10, Gazelle 11, Kudu 2, Kudu 3, Serval 10,
Bonobo 10, Bonobo 11, Meerkat 2, Sable 6, Ratel 5, and other desktop
hardware with additional wifi cards added.
To reproduce:
- Install Ubuntu in OEM mode
- Prepare for
Our systems contain an Intel 8260, 7260, or 3165 Wifi card, and this bug
affects all 3 cards.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576024
Title:
Wifi "device not ready" after booting into
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576024
Tit
35 matches
Mail list logo
