desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #106840
[Bug 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target
Let me chime in here as maintainer of NM in Debian: The reason why we
ship the patch, which removes Wants/Before=network.target is, that this
lead to dependency cycles if services/sysv init scripts in rcS
(sysinit.target) had Should-Start/Required-Start: $network, like for
example /etc/init.d/rpcbind in Debian.
If there is no such sysv init script Ubuntu, this patch can be dropped
indeed.
As for Colin's remark in #25, sounds sensible, to add
After=network.target to wpa_supplicant.service as well.
Have you tried adding that and see if that fixes the problem on shutdown
with WiFi?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1431774
Title:
cifs mount hangs on shutdown - NetworkManager needs to stop after
network.target
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
To replicate, perform a manual cifs mount, for example:
sudo mount -t cifs -o credentials=****,user,rw,uid=1000
//192.168.1.nnn/docs /media/test_mount
Then shutdown. When booted with systemd there is a 1 to 2 minute
delay before shutdown. In syslog the last shutdown (09:47:11 13th
March) showed the effect, though I fear that syslog shuts down too
early to see anything.
If booted with upstart there is no noticeable delay on shutdown.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Mar 13 09:50:08 2015
InstallationDate: Installed on 2014-10-21 (142 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
MachineType: FUJITSU LIFEBOOK A544
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
SourcePackage: systemd
UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
dmi.bios.date: 12/01/2014
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.18
dmi.board.name: FJNBB35
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK A544
dmi.sys.vendor: FUJITSU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431774/+subscriptions
Follow ups