[Bug 1288411] Re: udev restart on upgrade broke my wireless state
Steve Langasek
steve.langasek at canonical.com
Fri Mar 7 06:58:34 UTC 2014
On Fri, Mar 07, 2014 at 06:37:50AM -0000, 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 interfaces. Aside from this manual operation the
> main automatic thing to indirectly call this that I know of is logind:
> it sends a PrepareForSleep(True) signal right before suspend, and a
> PrepareForSleep(False) signal after resuming; NM listens to that signal
> and then does the equivalent of Enable(False/True), to restart the
> network after resuming.
> Now, suspend certainly wasn't involved here either, but during your
> upgrade systemd-services/libpam-systemd were upgraded as well. Their
> maint scripts don't do anything to manually restart them, but perhaps
> logind wasn't running before the upgrade and starting it had such a
> funky effect? Do you have any /var/crash/* which could be related?
$ ls /var/crash/*login*
ls: cannot access /var/crash/*login*: No such file or directory
$
But perhaps it's worth mentioning that, although this didn't happen during a
suspend/resume, the problem has repeated for me since this upgrade when I
*did* suspend/resume (without rebooting since the upgrade). Maybe due to a
different cause, maybe not.
I also see the following in dmesg coinciding with the upgrade, which is
probably of interest:
Mar 5 12:38:09 virgil kernel: [650446.233498] rfkill: input handler disabled
Mar 5 12:38:09 virgil kernel: [650446.473658] wlan2: deauthenticating from 00:26:b8:ee:3c:38 by local choice (reason=3)
That's precisely the time that the systemd packages were being configured
(udev, libsystemd-daemon0, systemd-shim, systemd-services). All other
packages of interest were configured at irrelevant moments (either later, or
too much earlier to be related).
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1288411
Title:
udev restart on upgrade broke my wireless state
Status in “systemd” package in Ubuntu:
Incomplete
Bug description:
Upgrading on trusty today, my wireless connection suddenly cut out,
with network-manager reporting that "wireless is disabled". Looking
at the logs, I see that udev was upgraded, and that as part of that
upgrade udev was restarted. I had to toggle the wireless switch on my
laptop off and on again to get the wireless to come back.
I don't know why udev is being restarted on upgrade in Ubuntu - this
is a delta from the Debian package, where udev is never restarted.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: udev 204-5ubuntu13
ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
Uname: Linux 3.13.0-12-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
CustomUdevRuleFiles: 70-ssd-scheduler.rules 70-kvm-perms.rules
Date: Wed Mar 5 12:43:35 2014
InstallationDate: Installed on 2010-09-24 (1258 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
MachineType: LENOVO 2306CTO
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-12-generic root=UUID=362a1cf5-63b7-4122-8457-33ca1d10a8ad ro quiet splash
SourcePackage: systemd
UpgradeStatus: Upgraded to trusty on 2013-10-23 (133 days ago)
dmi.bios.date: 10/25/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ET97WW (2.57 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2306CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2306CTO
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1288411/+subscriptions
More information about the foundations-bugs
mailing list