This was a fairly painful regression, thanks for the patch dreamcat4 -
that solved it for me. The other warnings are unrelated to the patch,
certainly (and did not occur for me, nor I do have those options in my
fstab).
--
You received this bug notification because you are a member of Ubuntu
Bugs
I can confirm this issue, on Ubuntu Bionic - server is
4.15.0-43-generic, client is 4.15.0-45-generic. Server filesystem is ZFS
(using nfs-kernel-server for export). Mounting with vers=4.1 works
around it as noted above.
--
You received this bug notification because you are a member of Ubuntu
Bug
Hmmm, filtering out syslog treats only a single symptom (dmesg, etc will
still have log spew) not to mention the events are still occurring
resulting in wasted CPU cycles. Why not just unload and reload the
module? It's much more straightforward...
--
You received this bug notification because yo
I have a similar workaround as Rekby, only as a pm-action hook.
https://gitlab.com/snippets/1786967
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784152
Title:
i2c_hid_get_input floods system logs
We can confirm that this patch does not solve the issue as we are still
seeing the same dmesg pattern with the 4.4.0-1069-aws kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788035
Title:
nvm
This [1] appears to be the source of the problem, specifically "Add new
RSA certificate types that that can be used in the above options and on
the wire to require the use of RSA/SHA2 signatures." - unfortunately,
those new certificate types don't exist/work in openssh <7.8, breaking
backwards comp
Updated the description - specifically, this appears to affect
certificate authentication and be related to rsa-
sha2-512-cert-...@openssh.com and rsa-sha2-256-cert-...@openssh.com
which are present in 7.8 server, but not earlier versions (nor are valid
to add to the configuration manually).
** Su
** Description changed:
Users are unable to connect to Ubuntu when using openssh client 7.8. We
have seen this with both xenial and bionic, but this affects connecting
- to ANY host running openssh <7.8.
+ to ANY host running openssh server <7.8.
The only known recourse at this time is ei
Public bug reported:
Users are unable to connect to Ubuntu when using openssh client 7.8. We
have seen this with both xenial and bionic, but this affects connecting
to ANY host running openssh <7.8.
The only known recourse at this time is either downgrade clients to 7.7
or a previous version of o
** Bug watch added: Debian Bug tracker #799170
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799170
** Also affects: cronolog (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799170
Importance: Unknown
Status: Unknown
** Summary changed:
- gcc optimizer bug
+ cr
Dupe in https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1770676
Also, can someone delete the spam in #4?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012178
Title:
cronolog fails to keep sym
Found another old bug related to this:
https://bugs.launchpad.net/ubuntu/+source/cronolog/+bug/1012178
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770676
Title:
gcc optimizer bug
To manage notif
Issue and pull request for cronolog submitted.
Issue: https://github.com/fordmason/cronolog/issues/4
Pull request: https://github.com/fordmason/cronolog/pull/5
** Bug watch added: github.com/fordmason/cronolog/issues #4
https://github.com/fordmason/cronolog/issues/4
--
You received this bug
It looks like GCC has determined this is expected to be undefined
behavior, so I'll be getting a pull request into cronolog and then work
with MOTU to get the patch in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
To reproduce this in cronolog:
echo hello | cronolog --symlink=/tmp/foo /tmp/foo.%Y%m%d-%H%M%S.log
This will create a new log every second (effectively each time the
command is run). The correct behavior is that the /tmp/foo symlink
should move to the new log file. In the broken case, the link do
** Also affects: gcc-5 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- Note: Package gcc-7 selected, but this affects other gcc versions.
-
While investigating why cronolog was no longer changing a log symlink in
bionic, I discovered a bug in gcc (reproducable
Public bug reported:
While investigating why cronolog was no longer changing a log symlink in
bionic, I discovered a bug in gcc (reproducable in 7.3.0-16ubuntu3 in
bionic and 5.4.0-6ubuntu1~16.04.9 in xenial) for code compiled with -O2.
I have created a simple testcase to reproduce the problem, wh
It looks like it got deferred to 4.4.0-125 according to the changelog
[1].
[1] https://launchpad.net/ubuntu/+source/linux/4.4.0-125.150
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755627
Title:
Thank you @kamalmostafa - we'll keep an eye out for the updated packages
in the repositories and follow up if anything is not as expected. Thanks
again for fixing this!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Description changed:
Sync request:
Source package name: pcp
Source package version number: 4.0.1-1
Where to sync from: Debian sid main
+
+ Freeze exception justification:
+
+ The current version of PCP in bionic (4.0.0) has a serious bug that
+ prevents the PCP daemons from startin
** Description changed:
- The PCP 4.0.0 packages for bionic do not automatically start PCP daemon
- processes.
+ Sync request:
+
+ Source package name: pcp
+ Source package version number: 4.0.1-1
+ Where to sync from: Debian sid main
+
+ === Original Description
+ The PCP 4.0.0 packages for bio
4.0.1 has been released, and the upstream debian sid version is now
4.0.1-1 and can be brought into bionic directly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755615
Title:
PCP daemons do not s
Fixed via
https://github.com/performancecopilot/pcp/pull/455/commits/ae80a78c7789b430901de1395b377923bf282a72
and will be in PCP 4.0.1 to be released soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Thank you Leann!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755627
Title:
ibrs/ibpb fixes result in excessive kernel logging
To manage notifications about this bug go to:
https://bugs.launchpad
Returning to confirmed status - easily reproducible with LTS kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755627
Title:
ibrs/ibpb fixes result in excessive kernel logging
To manage notif
We use LTS kernels, so no - unfortunately we cannot.
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Reported upstream at
https://github.com/performancecopilot/pcp/issues/454
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755615
Title:
PCP daemons do not start automatically for bionic
To manage no
Public bug reported:
The PCP 4.0.0 packages for bionic do not automatically start PCP daemon
processes.
>From my research so far, I believe the reason for this is that PCP 4.0.0
ships both sysvinit scripts and systemd unit files (which simply call
the sysvinit scripts). The services are enabled i
I can confirm that with the latest bionic packages (zfsutils-linux
0.7.5-1ubuntu4) all units start successfully for the case where no ZFS
pools are present. This is exactly as I would expect.
I can't really speak to the discussion about tainted kernel. If I didn't
want ZFS, I wouldn't install zfsu
OK, I retested with 0.7.5-1ubuntu3 and it's almost there but zfs-
mount.service still runs before the zfs kernel module is loaded:
$ systemctl --failed
UNIT LOAD ACTIVE SUBDESCRIPTION
● zfs-mount.service loaded failed failed Mount ZFS filesystems
$ sudo journalctl -u zfs-moun
** Bug watch added: github.com/systemd/systemd/issues #4762
https://github.com/systemd/systemd/issues/4762
** Also affects: systemd via
https://github.com/systemd/systemd/issues/4762
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a membe
** Bug watch added: github.com/systemd/systemd/issues #8328
https://github.com/systemd/systemd/issues/8328
** Also affects: systemd via
https://github.com/systemd/systemd/issues/8328
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a membe
Great, thanks Colin! We will test this on bionic very soon and will
follow up to confirm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741081
Title:
zfs-import-cache.service fails on startup
To m
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752722
Title:
systemd 237 reports incorrect state when drop-in present
To manage notifications about this bug go to:
https://bug
I found the xenial issue I was thinking of [1] but I'd be surprised if
that particular case regressed (it had to do with use of /etc/mtab). For
completeness, I'll mention it here anyway.
[1] https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1607920
--
You received this bug notification be
Note that for bionic as of this week the behavior is now different. This
particular problem doesn't surface for zfs-import-cache.service (because
the ConditionPathExists expression is back in the unit).
It's not all good news, however, as that one failed unit has been
replaced with:
$ systemctl -
Let me know what I can do to help move this forward. The ubuntu-load-
zfs-unconditionally patch was not a great solution as it results in
systems that install zfsutils-linux to come up in a failed state when
there are no ZFS pools present:
$ systemctl --failed
UNIT LOAD ACT
Confirmed to also affect bionic:
$ sudo journalctl -u zfs-import-cache.service
-- Logs begin at Tue 2018-01-23 17:46:55 UTC, end at Tue 2018-01-23 17:49:18
UTC. --
Jan 23 17:46:58 ubuntu systemd[1]: Starting Import ZFS pools by cache file...
Jan 23 17:46:59 ubuntu zpool[640]: failed to open cache
Great, Thank you Brian!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655153
Title:
long-running stunnel leaks memory
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
It certainly fixes the bug for me - stunnel4 process was up until the
server was rebooted (several months) versus crashing after a day or two.
However, as the author of the patch I'm not sure that I should be the
one to verify it...
--
You received this bug notification because you are a member
** Changed in: hundredpapercuts
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1484083
Title:
Don't work autologin after update lightdm
To manage notificatio
Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it and converting it to
a question in the support tracker. We appreciate the difficulties you
are facing, but
Summary: This does not appear to be a bug with the Ubuntu kodi package,
but an incompatibility with a package from another source.
>From what I can see, the new version of the kodi package did not come
from Ubuntu repositories [1]. When installing newer versions of packages
from other sources, you
It looks like this change was a result of Debian bug 792535 [1], which
switched the implementation from Crypt::OpenSSL::Random to
Bytes::Random::Secure [2].
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792535
[2]
https://alioth.debian.org/scm/loggerhead/users/cjwatson/makepasswd/trunk/re
Xenial currently has python 3.5 (not python 3.4) and at a version where
the upstream bug[1] should be fixed.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809079
** Bug watch added: Debian Bug tracker #809079
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809079
** Also affects: p
** Summary changed:
- systemd service not enabled on install
+ shorewall systemd service not enabled on install
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571972
Title:
shorewall systemd servic
** Summary changed:
- Crashes due to missing dependencies
+ gpxviewer crashes due to missing dependencies
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654976
Title:
gpxviewer crashes due to missi
The commit for this in upstream Debian (0.123 version of initramfs-
tools) is here: https://anonscm.debian.org/cgit/kernel/initramfs-
tools.git/commit/?id=ac6d31fc2c707b72ff8af9944c9b4f8af303a6a3 - I would
be happy to make a patch for this commit to xenial (zesty and later has
0.125+, so should alr
Sorry, my previous comment was for another initramfs-tools related bug.
Please disregard #18.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515513
Title:
/boot/initrd.img-*.old-dkms files left behi
The commit for this in upstream Debian (0.123 version of initramfs-
tools) is here: https://anonscm.debian.org/cgit/kernel/initramfs-
tools.git/commit/?id=ac6d31fc2c707b72ff8af9944c9b4f8af303a6a3 - I would
be happy to make a patch for this commit to xenial (zesty and later has
0.125+, so should alr
Thank you very much Simon, I do appreciate your time and help in getting
my patch correct.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655153
Title:
long-running stunnel leaks memory
To manage n
** Description changed:
We are running a long-running stunnel4 daemon to proxy TLS connections
to another set of servers. After leaving it running for a few weeks, its
memory usage had grown to 1.5GB. Restarting it reduced its memory usage
to expected levels (VSZ and RSS) but while I've be
Attached is an updated debdiff. I have attempted to fill out the header
per recommendations (somewhat tricky for stunnel4, as there is no bug
tracking system and granularity of commits is by release - official
source repository is an rsync of tarballs, but the maintainer does have
a github mirror w
Thanks Simon, I didn't expect my current patch to be the final one -
just a demonstration of the fix. I am more than happy to contribute a
compliant patch, if this one-off fix for Xenial is the best way to go.
Unfortunately, upstream debian closed the bug without fixing jessie-
backports and the ma
Duplicate: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709749
Related: https://github.com/moby/moby/issues/34361
** Bug watch added: github.com/moby/moby/issues #34361
https://github.com/moby/moby/issues/34361
--
You received this bug notification because you are a member of Ubuntu
This appears to be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1679768 and
also affects Xenial when using hwe backported kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
We are seeing the same issue here with 4.10.0-24-generic, and will see
if we can reproduce with a newer hwe backport (4.11.0-13-generic).
Jul 20 14:32:47 ubuntu kernel: INFO: task kworker/5:2:574 blocked for more than
120 seconds.
Jul 20 14:32:47 ubuntu kernel: Tainted: P O
4.
This bug is not to track a problem, it's to change a default kernel
option to a more secure setting already in use by other distributions,
such as upstream Debian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Fix confirmed to solve the SSL session leak for me - under constant
load, the RSS for stunnel would continue to grow - seeing an RSS of
50+ was common after a few hours. Now, after running overnight the
RSS is still at 13348 and I was able to remove a cron job to restart
stunnel.
--
You recei
59 matches
Mail list logo
