A recent update to the update-manager seems to have fixed this for me.
Still problems with the Nvidia driver post-update, but that is not the
same bug/dependency issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in
I would also like to have shutdown messages logged. Could it be
configured to stop on reaching the last of the init-style of run-levels?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
Still broken on 12.04.5 recently updated:
$ apt-cache policy ureadahead
ureadahead:
Installed: 0.100.0-12
Candidate: 0.100.0-12
Version table:
*** 0.100.0-12 0
500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
100 /var/lib/dpkg/status
$ uname -a
Linux
Public bug reported:
I tried the daily build of 16.04 32-bit to test out the watchdog daemon
code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in
/etc/modules so it is loaded at boot-time, as watchdog timer modules are
not normally auto-loaded due to the risk of an unexpected reboot.
This is still present in the development branch for 16.04
Jan 19 17:53:23 ubuntu rsyslogd-2039: Could not open output pipe
'/dev/xconsole':: No such file or directory [v8.14.0 try
http://www.rsyslog.com/e/2039 ]
System information:
$ lsb_release -rd
Description:Ubuntu Xenial Xerus
Public bug reported:
I was testing the watchdog daemon code on the development version of
16.04 today and found the associated systemd service files for this has
some bugs.
The first of these was a typo in /lib/systemd/system/watchdog.service
where there was a missing ['] character. This lead to
*** This bug is a duplicate of bug 1575572 ***
https://bugs.launchpad.net/bugs/1575572
I don't think this is a duplicate of bug #1575572
I am seeing this problem on an Ubuntu 16.04 machine that has the update "This
bug was fixed in the package init-system-helpers - 1.29ubuntu2" mentioned as
Generally me work-around so far has been to avoid systemd!
However, where that is not an option you might be able to edit
/etc/default/watchdog so the module is loaded on watchdog start-up. It is not
ideal as you might have some other reasons for wanting the /dev/watchdog
virtual file to be
We were seeing this on a fresh Ubuntu 16.04 64-bit installation using
fixed IP addresses and automounter for NFS drives. The suggestion #7
seems to fix it for use, but it would be useful to know just what is
happening with the script. Is it trawling through some user's home
directory when
If it was fixed in 8.12.0-1ubuntu3 why am I still seeing this on a
16.04.2 system with:
apt-cache policy rsyslog
rsyslog:
Installed: 8.16.0-1ubuntu3
Candidate: 8.16.0-1ubuntu3
Version table:
*** 8.16.0-1ubuntu3 500
500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
10 matches
Mail list logo