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 effect on either.
You shoudl be able to stop and restart udev without any ill effect
(except of course losing rules evaluation while it is down) at any time.
Just to double-check, can you do "sudo stop udev" / "sudo start udev"
and see whether it has any effect on NM or rfkill?
I assume this was a trusty→trusty daily upgrade, not one from saucy, so
hopefully the list of upgraded packages should be not too big. Could you
filter out the list of packages that were upgraded in that run from
/var/log/dpkg.log?
Thanks!
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1288411/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
