** Changed in: urfkill (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1288411
Title:
udev restart on upgrade broke my wireless state
To manage noti
> I'd like to understand how urfkill ended-up installed on your system?
Because I had manually installed it for dogfooding purposes prior to
urfkill being integrated in the default system.
> Also the version you reference is quite old and frankly was still
super-unstable even on the phone
I've c
@Steve
I changed the Status back to Incomplete as I'd like to understand how
urfkill ended-up installed on your system? AFAIK, urfkill has not yet
been seeded as a default desktop package in Ubuntu.
Also the version you reference is quite old and frankly was still super-
unstable even on the pho
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: urfkill (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/1288411
Title:
ud
Hmmm. syslog shows:
Mar 5 12:38:09 virgil URfkill[23110]: Starting urfkilld version 0.5.0
Mar 5 12:38:09 virgil URfkill[23110]: adding killswitch idx 1 soft 0 hard 0
Mar 5 12:38:09 virgil URfkill[23110]: killswitch state: KILLSWITCH_STATE_NO_ADA
PTER new_state: KILLSWITCH_STATE_UNBLOCKED
Mar
FTR, I did "sudo apt-get install --reinstall udev systemd-shim systemd-
services" a couple of times without any problem, but I guess it'd be no
fun if it was that easy :-/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
> I also see the following in dmesg coinciding with the upgrade,
I think that's just the result of NM shutting down the network. Do you
still have the corresponding NetworkManager logs in /var/log/syslog from
that time? It usually says why it shut down the net.
> That's precisely the time that t
On Fri, Mar 07, 2014 at 06:37:50AM -, Martin Pitt wrote:
> Indeed the "[ ] Enable network" menu entry isn't rfkill, sorry. That's
> "[ ] Enable wireless network". I think "Enable network" just pokes
> org.freedesktop.NetworkManager.Enable(False/True), which tells NM to
> shut down/restart all i
Indeed the "[ ] Enable network" menu entry isn't rfkill, sorry. That's
"[ ] Enable wireless network". I think "Enable network" just pokes
org.freedesktop.NetworkManager.Enable(False/True), which tells NM to
shut down/restart all interfaces. Aside from this manual operation the
main automatic thing
$ rfkill list
1: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
17: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
$
Certainly there's nothing soft-blocked now; there also s
Did you happen to check in "rfkill list" whether anything set it to
soft-block? I wouldn't know what udev had to do with soft rfkill
settings, as it is not touching anything in /sys/class/rfkill nor is
there any rule which would fiddle with /dev/rfkill, nor should
restarting the daemon have any eff
11 matches
Mail list logo
