Sorry to bang on, but (1) previous comments don't seem editable, (2)
running the aforementioned script through http://www.shellcheck.net/
identifies some potential problems.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus
(But I've removed the cups and the 'up' bits.)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1438612
Title:
remote file systems hang on shutdown, D-BUS stops too early
Stat
@Adam Felson
I'm trying out your script, combined with autofs (which doesn't work via
fstab).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1438612
Title:
remote file syste
I suffer from this too. It affects both systemd's automounts and autofs.
It's driving me nuts.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1438612
Title:
remote file syste
> ExecStop=/bin/sh -c "echo Stopping the system dbus-daemon is not
supported. Reboot the system instead.; exit 1"
This is nonsense and makes me wonder if I should switch back to Windows
instead.
Trolling intended.
--
You received this bug notification because you are a member of Ubuntu
Touch se
Adam, can you confirm what link you have in pre-down? I created a link
in pre-down.d called pre-down pointing to nfs.sh in the higher
directory. When I included this script (on ubuntu 16.04), in systog I
get messages like:
root: ** NetworkManager dispatch script nfs, IF=none
after years of suffering with this bug, I found a solution that works for me.
I put a pre-down dispatch script for network manager to dismount nfs shares
when bringing the network down. This works even if a reboot is run from a
shell.
In /etc/NetworkManager/dispatcher.d/nfs.sh:
/etc/NetworkMa
@stormhike do you run Upstart or systemd? I'm just wondering if this
works on systemd since you're modifying init scripts and I thought
systemd doesn't look at these.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubu
I have found a workaround on my 16.04.1 system (whether dbus problem that was
already fixed or not).
I removed the .sh from the umount files in rc0.d, rc6.d and init.d ...
su
cd /etc/init.d/
mv umountnfs.sh umountnfs
cd /etc/rc0.d
rm K05umountnfs
ln -s ../init.d/umountnfs K05umountnfs
cd /etc/rc6.
I got tired of having to gracelessly cut the power every time nfs
umounts hung. I slipped an unmount command into the desktop manager's
systemd init script. I run kubuntu, so the unmounts went into
/etc/init/sddm.conf.
--
You received this bug notification because you are a member of Ubuntu
To
To recent commentators, unless you are sure this is a problem caused
by dbus stopping too early then it is a different issue. Even if you
believe it is the same issue it is probably best to open new bug rather
than commenting on a closed one.
--
You received this bug notification because you a
I experience a similar isses as Tommy. I mounted the NFS manually and
the computer will just not shutdown. Additionally I also failed mounting
the device via fstab but I used different options.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which i
Apparently this is not a solved problem, as my fresh 16.04 install hangs on
shutdown with NFS drives mounted.
My fstab:
10.10.10.10:/media/storage1 /nasnfs
noauto,x-systemd.automount,soft,timeo=20,retrans=10 0 0
Un-mounting before shutdown makes it shutdown correctly.
Is th
** Changed in: dbus
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1438612
Title:
remote file systems hang on shutdown, D-BUS stops too
This bug was fixed in the package dbus - 1.8.12-1ubuntu5
---
dbus (1.8.12-1ubuntu5) vivid; urgency=medium
* Add debian/patches/dont-stop-dbus.patch: Don't stop D-Bus in the service
unit (see patch header and upstream bug for details). Fixes various causes
of shutdown hangs,
Launchpad has imported 1 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=89847.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
I started a discussion with upstream in the linked fd.o bug, and
uploaded this in the meantime.
** Bug watch added: freedesktop.org Bugzilla #89847
https://bugs.freedesktop.org/show_bug.cgi?id=89847
** Also affects: dbus via
https://bugs.freedesktop.org/show_bug.cgi?id=89847
Importance:
Fixed here too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1438612
Title:
remote file systems hang on shutdown, D-BUS stops too early
Status in dbus package in Ubuntu:
Martin, your fix worked for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1438612
Title:
remote file systems hang on shutdown, D-BUS stops too early
Status in dbus pack
dbus would be stopped by the final killing spree.
This usually looks like this
Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining processes...
Unmounting file systems.
All filesystems unmounted.
Deactivating swaps.
All swaps deactivated.
Detaching loop devices.
All loop devi
Andy, Colin, can you please revert the workaround in
/lib/systemd/system/NetworkManager.service (remove After=dbus.service),
and instead append these lines in /lib/systemd/system/dbus.service, to
the [Service] section:
ExecStop=/bin/true
KillMode=none
This makes things work in my tests, and is a
** Summary changed:
- remote file systems hang on shutdown
+ remote file systems hang on shutdown, D-BUS stops too early
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1438612
Yes, I have that version:
$ apt-cache policy wpasupplicant
wpasupplicant:
Installed: 2.1-0ubuntu7
Candidate: 2.1-0ubuntu7
Version table:
*** 2.1-0ubuntu7 0
500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status
$ systemctl cat wpa_suppli
Andy gets this issue as well (http://paste.ubuntu.com/10711795/)
** Changed in: dbus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/143
Can you confirm that you have wpasupplicant 2.1-0ubuntu7 ? I. e. you
should see
$ systemctl cat wpa_supplicant.service |grep Before
Before=network.target
Your journal looks like it would stop wpa_supplicant before
network.target.
--
You received this bug notification because you are a member of
** Changed in: dbus (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1438612
Title:
remote file systems hang on shutdown
Status in db
No problem. Attaching journal
** Attachment added: "Journal showing wait on unmount when connected via wifi"
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1438612/+attachment/4361872/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seed
27 matches
Mail list logo
