Appreciate this everyone. I have multiple people beginning to test this
today. I will be joining them next week. I have asked each to report
back here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Tags added: systemd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2045075
Title:
Framework Laptop Expansion Card enabling auto suspend
Status in systemd package in
Public bug reported:
Framework provides expansion cards. For the HDMI and DisplayPort, these benefit
power management via enabling auto suspend.
Ubuntu 22.04.3 LTS
6.1.0-1026-oem
systemd 249 (249.11-0ubuntu3.11)
#
# Framework
> if it's time to re-visit that practice of not updating through minor
openssl versions; it's risky to try.
As an upstream OpenSSL maintainer we try very hard to ensure that stable
releases remain stable across patch releases. We only allow bug fixes
(no new features etc) into our patch releases
Public bug reported:
Following the resolution for bug #1747499, after a kernel upgrade when
Livepatch is enabled, the current behaviour in unattended-upgrades
(2.3ubuntu0.2 and later) is not to touch /var/run/reboot-required so as
not to confuse users with two separate messages calling for a
On another reading of this, it looks like the issue may end up being in
dependency (and upstream package) httplib2. I'd like a sanity check on
that, and I'm willing to file tickets in other packages or upstream as
soon as I have cycles. I'm buried in the middle of another project
right now, but
Public bug reported:
It appears that if one has an HTTP or HTTPS proxy called out
specifically by IPv6 address rather than hostname, it will fail.
Placing an entry in /etc/hosts, or the proxy into DNS (and calling by
hostname) will function.
failure steps:
1) set proxy environment variables
Confirming that we see this behaviour on Ubuntu 20.04 servers (reboots
happening even though `Unattended-Upgrade::Automatic-Reboot` is set to
false).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Here is a link for cairo/egl: https://jan.newmarch.name/Wayland/Cairo/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1977748
Title:
Build Cairo with OpenGL support
Status
Public bug reported:
It seems that attaching to Ubuntu Advantage takes a long time. When I
tried to attach using my token in the GUI, it repeatedly told me that I
"failed to attach, try again". Finally I gave up and canceled out of
the dialog, only to see that in the underlying UI for the
Public bug reported:
Can python-psutil be updated to 5.9.1? It fixes incorrect cpu_freq which
affects s-tui.
https://github.com/giampaolo/psutil/issues/2049
https://github.com/amanusk/s-tui/issues/186#issuecomment-1100639705
Thanks
** Affects: python-psutil (Ubuntu)
Importance: Undecided
I was looking to run cairo on wayland. A web search led me to the EGL
device. I'm guessing by buffer you mean IMAGE surface (after digging in
the headers a bit). I am happy to try that. But I'm guessing at some
point in the future peeps will want it. Thanks for digging in.
--
You received
ant. Though as
it turns out if the "rfc3442-classless-routes" hook file is accidentally
missing then that makes the behavior of the newer, more correct
dhclient-script version worse.
--Matt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
doesn't function and we cannot install Ubuntu.
My colleague tested modifying the initrd by adding the
/etc/dhcp/dhclient-exit-hooks.d/rfc3442-classless-routes file and
reports that works.
--Matt
# from the initrd rescue shell
(initramfs) ls /etc/dhcp/dhclient-exit-hooks.d/rfc3442-classless-routes
ls: ca
FYI, upstream have now also merged a fix in the 1.1.1 branch:
https://github.com/openssl/openssl/commit/e04ba889594d84a8805f3d0caeadf0527470e508
If Ubuntu pulls in that patch I expect that this bug should be fixed by
it.
--
You received this bug notification because you are a member of Ubuntu
FYI, upstream merged a fix for the underlying problem in OpenSSL 3.0:
https://github.com/openssl/openssl/commit/8b63b174b00b0e8c5cefcea12989d90450e04b24
I expect a similar fix to be backported to 1.1.1 soon. Although the
specific issue that this bug report is about doesn't impact upstream, I
Thanks for your analysis. Based on your description I was able to find
an instance of this bug that impacts an unmodified upstream OpenSSL
directly. I've raised an issue for it here:
https://github.com/openssl/openssl/issues/18047
That particular instance only impacts OpenSSL 3.0 - but its the
Public bug reported:
Recently on systems in Ireland, systemd became unresponsive due the
change from GMT to Irish Standard Time. This is due to Ireland being
unique in having their standard time during the summer, unlike most
regions.
Related to:
Public bug reported:
Problematic commit reverted upstream causing incorrect behavior in
Ubuntu Focal.
Discussion: https://github.com/iputils/iputils/issues/320
Fix: https://github.com/iputils/iputils/pull/321
Release: https://github.com/iputils/iputils/releases/tag/20210722
Could this patch be
:
Start-Date: 2022-01-03 18:34:51
Commandline: apt autoremove
Requested-By: matt (1000)
Remove: libnvidia-common-470:amd64 (470.86-0ubuntu0.21.10.1), libxnvctrl0:amd64
(470.57.01-0ubuntu3), libnvidia-fbc1-470:amd64 (470.86-0ubuntu0.21.10.1),
libnvidia-fbc1-470:i386 (470.86-0ubuntu0.21.10.1
Public bug reported:
Launching openssl s_server as follows:
$ openssl s_server -nocert -psk 01020304 -dtls1
And using openssl s_client to connect to it like this:
$ openssl s_client -dtls1 -psk 01020304
Results in s_server entering an infinite loop:
Using default temp DH parameters
ACCEPT
Public bug reported:
Add the olcDbDirectory value as a debconf setting, so the directory may
be relocated. This is especially helpful when building a container to
run slapd with multiple ldap databases using one or more volumes.
** Affects: openldap (Ubuntu)
Importance: Undecided
@jsing You may well be correct that the server was incorrectly
configured, unfortunately it was a Windows server managed by a third
party and I don't know precisely how it was set up. Given that the cert
in question was issued on 9th September 2021 I suspect it was a
misconfiguration of their
I ran into an SSL verification issue today, caused by this change.
It seems that some older LetsEncrypt clients have still recently been
issuing valid certificates signed by the DST Root CA X3 root.
These certificates would have otherwise continued to work normally until
the root expired
According to https://stackoverflow.com/questions/66319610/gpg-error-in-
ubuntu-21-04-after-second-apt-get-update-during-docker-build, this bug
fix is supposed to fix the issue of getting the following error when
running "apt-get update" in an Ubuntu 21.04 container: "W: GPG error:
After this report, it automatically ran something like dpkg --configure
--pending, which succeeded in running the lilo update. The only thing it
didn't do was run autoremove to remove the outdated libraries and stuff.
Rebooted into the new kernel via lilo successfully as well.
--
You received
Public bug reported:
Upgrading from 16.04 to 18.04 on an old server that still has to use
lilo.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3.12
ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262
Uname: Linux 4.4.0-210-generic i686
ApportVersion:
I can pair successfully if I enable LE Privacy:
sudo btmgmt power off
sudo btmgmt privacy on
sudo btmgmt power on
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638
Public bug reported:
do-release-upgrade from 18.04 LTS to 20.04 LTS results in this error
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.3
ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18
Uname: Linux 4.15.0-122-generic x86_64
ApportVersion:
I don't see the updated applied to the ARM architecture. The versions of
arm64 and armhf at https://packages.ubuntu.com/focal/libseccomp-dev
still show 2.4.3-1ubuntu1. What's the story on that?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Public bug reported:
I have two monitors, with the secondary one rotated in a portrait
orientation. Using the nvidia 440 drivers, the orientation is not
applied when configuring in gnome settings (the displays go blank for a
second, and then reappear in landscape orientation).
Using nvidia
** Attachment added: "Screenshot from 2020-04-24 08-37-43.png"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1874567/+attachment/5358812/+files/Screenshot%20from%202020-04-24%2008-37-43.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
The following worked for me: see
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974/comments/8
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
*** This bug is a duplicate of bug 1872778 ***
https://bugs.launchpad.net/bugs/1872778
Thank you Simon Déziel! That worked for me too.
I was all set to give up on ubuntu 20 because having a working
evolution-ews is a deal-breaker for me.
I wonder why the linked duplicate thread does not
I can confirm this bug. Viewing systemd logs on my system showed the
weekly TRIM of /home stopped around the end of October 2019 as reported
by Jeffery.
This bug was filed upstream (https://github.com/karelzak/util-
linux/issues/824) and will affect users with /home on a separate
partition.
It
This bug persists. It may be a regression associated with 5.0.0.37.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1814262
Title:
Wired interface gets impossibly high
I just upgraded from 16.04 to 18.04 and I'm seeing the same/similar
issue. I have the same messages in the log, and I have an encrypted
home folder.
When I *first* try to log in after a reboot, I get bounced back to the
login screen. It then logs in on the second attempt (so far - but this
I've now been using an Xorg session rather than Wayland and haven't seen
the repeated keys issue. I do get some very nasty screen tearing when
scrolling (e.g. websites) on Xorg however, so ideally I'd like to
continue using Wayland.
Does that mean that this is likely a mutter bug, rather than
Public bug reported:
I have a Microsoft Surface bluetooth keyboard, and semi-frequently (e.g.
around every 10-15mins) end up with repeated keypresses being made (e.g.
apppt get update).
This seems to happen when the machine is under slight stress, or when a
new notification pops up in
Public bug reported:
I have an external monitor capable of 3440 x 1440. I am using a Thinkpad
T480s. Up until about 2 weeks ago, I could set the resolution of the
monitor to 3440 x 1440 just fine. Now when I try, the screen goes black
and I have to revert to a lower resolution. The highest it
Nothing helpful in this post but can confirm this issue still exists in
19.04. :(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Title:
Problem to connect
Dan, thanks for the comment. I will test this evening and let you know.
Sorry for the delay!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1824806
Title:
Network stops
Public bug reported:
I have four 18.04 servers that are regularly updated and have a
bond/bridge configured via netplan. Every so often the interfaces
themselves will have "speed changed to 0" and the server will be
unresponsive over network. The servers are still usable via the console,
though.
I stopped using resolve because of this bug so unfortunately, I can't
say whether or not that error appeared in the log at the same time.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Okay. I guess I would have expected that if there was a dependency on a
specific kernel version, that I wouldn't be able to install a package
that wasn't compatible and breaks the system by installing a security
update. It would be preferable to be informed there is a security
update but that I
Same situation. Ubuntu 16.04 openvz vps image of unknown origin.
Minimized image, ran security updates and rebooted. openssh server
failed to start due to systemd-tmpfiles failing with
Failed to validate path /var/run/sshd: Too many levels of symbolic
links
Which then causes ssh server to
I'm seeing the same behavior with Ubuntu 18.04.2 running in a VMware
virtual machine. When networking for the VM is set to "Host-only", it
takes two extra minutes to boot while waiting for systemd-networkd-wait-
online.service to fail.
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:
** Changed in: sqlalchemy-migrate
Status: New => In Progress
** Changed in: sqlalchemy-migrate
Assignee: (unassigned) => Corey Bryant (corey.bryant)
** Changed in: sqlalchemy-migrate
Importance: Undecided => High
--
You received this bug notification because you are a member of
** Attachment added: "ufw.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/+attachment/5222404/+files/ufw.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
** Attachment added: "dpkg.list"
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/+attachment/5222403/+files/dpkg.list
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
** Attachment added: "ufw.raw"
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/+attachment/5222405/+files/ufw.raw
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
I rebooted and confirmed that ufw still reports itself as inactive.
Attached are the requested files. Note: I only included the last 25000
lines from journal.full - otherwise I would have to upload 250Mb!
** Attachment added: "journal.full"
I made the change to /lib/ufw/ufw-init as requested and confirmed that
after reboot I was still hitting the issue (Ubuntu 18.04.1 LTS):
$ sudo ufw status
Status: inactive
Attached is the requested journalctl output.
** Attachment added: "journalctl.log"
,
Matt Rush
OSCP, OSCE
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.4
ProcVersionSignature: Ubuntu 4.15.0-1025.25-aws 4.15.18
Uname: Linux 4.15.0-1025-aws x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Wed Dec 5 17:35:09 2018
Ec2AMI: ami
Thank you very much, Dimitri -- I am interested in this also.
I tested that PPA on a test web server running nginx, uwsgi, uwsgi-
plugin-python3, Django 1.11(.16), and a Python 3.6 'pyvenv' virtual
environment using 'psycopg2' to connect to a PostgreSQL 10 server via
the pre-built Python wheel
Public bug reported:
Just tried to run the updates the app updater recommended
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: python3 3.6.5-3ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
I recently switched back to Ubuntu, only to find that Slack in a snap is
still crashing on Wayland! I previously reported what seems like a
related bug on snapcraft-- here's the link to the related bug with logs
and some details from experiences on Fedora28 and Arch.
Ok, ignore previous post. My laptop was sitting unused and suddenly I
hear the fans spin up (which they almost never do). Sure enough, the
avahi-daemon was running up a full cpu core. I've attached the logs.
Thanks for looking into it.
** Attachment added: "avahi.zip"
Ok, ignore previous post. My laptop was sitting unused and suddenly I
hear the fans spin up (which they almost never do). Sure enough, the
avahi-daemon was running up a full cpu core. I've attached the logs.
Thanks for looking into it.
** Attachment added: "avahi.zip"
Ok, ignore previous post. My laptop was sitting unused and suddenly I
hear the fans spin up (which they almost never do). Sure enough, the
avahi-daemon was running up a full cpu core. I've attached the logs.
Thanks for looking into it.
** Attachment added: "avahi.zip"
Ok, the issue seems gone! I cannot recreate it, and I'm not sure why.
First, thank you for the quick reply. When I first read your response, I
ran the
`echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted
universe multiverse" | sudo tee -a /etc/apt/sources.list.d/ddebs.list`
Public bug reported:
package linux-image-4.4.0-138-generic 4.4.0-138.164 failed to
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
exited with return code 127
kernel installations halt while scanning mdadm arrays, eventually timing
out and failing
ProblemType: Package
Public bug reported:
Currently running Kubuntu 18.10, Dell XPS 13 9350
Since updating from Kubuntu 18.04 to 18.10, the avahi-daemon has been
consistently hampering network performance and using CPU for long
periods of time.
When booting machine from off state, avahi-daemon uses an entire CPU at
I'm seeing a similar issue with a similar setup. I've got a media
center connected to a receiver via HDMI. Sometimes when I'm playing
audio and power-cycle devices in the chain (TV, receiver, etc), pulse
will stop playing audio. I don't get any errors or anything, and
issuing pulseaudio -k will
I just tried:
After=network.target
After 5 reboot tests I got mixed results:
The first two reboots failed to start networking at all and ufw reported its
status as "inactive" immediately after boot.
The next two reboots networking started successfully, and ufw reported as
active.
The final
I just tried that:
$ diff -u ufw.service.orig ufw.service
--- ufw.service.orig2018-05-26 13:45:48.696356561 +0100
+++ ufw.service 2018-07-17 16:50:45.545596167 +0100
@@ -2,7 +2,8 @@
Description=Uncomplicated firewall
Documentation=man:ufw(8)
DefaultDependencies=no
-Before=network.target
Public bug reported:
I keep trying to set up external SSH access using openssh server on my
18.04 system and it throws back this error
sudo service ssh status
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset:
enabled)
Unfortunately, after a few reboots using these settings it seems this is
not the answer. While it does seem to work intermittently, it also
sometimes fails. I've also had some issues with network not working at
all. I'm not 100% sure that this change is the culprit - but for now I
have reverted
This issue still seems to be a problem in 18.04.
If found a solution:
https://askubuntu.com/questions/1040539/how-do-i-get-ufw-to-start-on-boot/1040584
I edited /lib/systemd/system/ufw.service as follows:
$ diff -u ufw.service.orig ufw.service
--- ufw.service.orig2018-05-26
Thanks for pointing out the changes to server start/stop, Robie. Adding
the `--as-pid2` parameter to `systemd-nspawn` allows it to work.
** Changed in: mysql-5.7 (Ubuntu)
Status: New => Invalid
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug
It behaves differently (the installation succeeds) if you install mysql-
server from a bash prompt inside the container. Running the installation
as a parameter to `systemd-nspawn` will fail. I have tested this on a
16.04.3 system and an 18.04 system.
I just noticed something especially weird: if
It also succeeds if I replace `dpkg --configure -a` with `ls`:
rm -rf testmysql && cp -a bionic testmysql && systemd-nspawn -D testmysql bash
-c 'apt update && apt install mysql-server; ls'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
Adding a 4th 10TB disk to an existing 3 disk mdadm raid5 set.
Left the stock resize2fs running for nearly 30 hours... 100% CPU no disk
writing.
Downloaded current e2fsprogs package 1.43.8.2, built and installed.
This is working fine.
Hope that helps someone,
--Matt
Hi Seth,
This is what I get:
matt@matt-laptop:~$ sudo ufw status
Status: inactive
matt@matt-laptop:~$ journalctl -u ufw.service
-- Logs begin at Tue 2017-10-24 22:48:54 BST, end at Wed 2017-10-25 00:03:54
BST. --
Oct 24 22:48:54 matt-laptop systemd[1]: Started Uncomplicated firewall.
matt@matt
Public bug reported:
Whenever I boot into 17.10 ufw is always inactive, even though
/etc/ufw/ufw.conf has this:
# Set to yes to start on boot. If setting this remotely, be sure to add a rule
# to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp'
ENABLED=yes
ProblemType:
Just had this bug happen to me when installing my machine's first-ever
Snappy package (keepassxc if it matters). Ubuntu Gnome 16.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
Excellent, thank you for the details.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1569925
Title:
Shutdown hang on 16.04 with iscsi targets
Status in systemd package
As I said I don't have one up right now, but Comment 3 above has my
interfaces for one of the recreates.
Nothing bothered me in any way. I wanted to make sure that you knew
that I wasn't one guy who was looking to fix his one system, that's all.
You said "Usually those type of "partnership"
Please let me explain who I am and what we do to possibly shed some
light on this.
I am an Interoperability engineer at NetApp. We test our storage
products with many popular operating systems, adapters, protocols and
switches, in varying combinations.
We test software initiator iscsi
I have node.session.timeo.replacement_timeout = 20, which seems
completely reasonable in my book.
We have already established that this occurs without multipath even
enabled, thus it is not a multipath settings problem.
Also I have no containers.
--
You received this bug notification because
** Bug watch added: Debian Bug tracker #867625
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867625
** Also affects: isc-dhcp (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867625
Importance: Unknown
Status: Unknown
--
You received this bug notification because
FYI this bug is fixed in newer versions, see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748272
So perhaps this bug can be closed?
--Matt
** Bug watch added: Debian Bug tracker #748272
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748272
--
You received this bug notification
hat should I pursue fixing the Debian package first?
(https://wiki.ubuntu.com/Debian/Bugs)
--Matt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1664352
Title:
dhcli
Public bug reported:
Changes to support day-of-week patching and logging to syslog were added
to upstream (https://github.com/mvo5/unattended-upgrades) over a year
ago. These changes are not present in the latest Xenial nor Trusty
packages (0.90 and 0.82.1) - requesting that these changes be
I can confirm that the daily 17.10 build does not exhibit the problem.
Interestingly, the first time we tried we forgot to stop running IO to
our iSCSI volumes and it _looked_ like we reproduced the problem, then
the IOs timed out and our application stopped and we were able to
complete the
My test configuration has long since been re-tasked. I will eventually
be able to come back and test as you ask, but it may take a few weeks.
If anyone else on the bug has their systems up and available, please
test and reply.
--
You received this bug notification because you are a member of
This bug is about using the GRUB2 gfxmenu theme api* to provide a fancy
bitmap theme. GRUB being purple is just setting the background colour.
*originally developed as this summer of code project:
http://grub.gibibit.com/
Latest docs: https://www.gnu.org/software/grub/manual/grub.html#Theme-
Public bug reported:
Trying to troubleshoot unexpected behavior with haproxy, I discovered
that lookbehind appears to be broken in version 1:8.31-2ubuntu2.3 of the
libpcre3 package.
I have an haproxy rule to rewrite URL paths that do not begin with
"build" or "static":
reqirep ^([^\ :]*)\
I am also have the issue of blank screen. I tried a fresh install of
Fedora out of curiosity and worked perfect.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
route (a NAT gateway) provided by the private network
DHCP server. Unfortunately the current dhclient script ignores the
configured metric when adding DHCP provided rfc3442 classless routes to
the routing table. This patch from Tom fixes dhclient behavior for my
use case.
--Matt
--
You received
Installed the most recent build of Zesty (zesty-server-amd64.iso
2017-02-22 06:54676M).
I was able to:
1. Confirm the issue still exists.
2. Confirm that the issue is not caused by multipath (i.e. it still occurs
during reboot when multipathing is disabled).
--
You received this bug
Didn't take as long as I thought. Installed the most recent build of
Zesty (zesty-server-amd64.iso 2017-02-22 06:54676M).
I was able to:
1. Confirm the issue still exists.
2. Confirm that the issue is not caused by multipath (i.e. it still occurs
during reboot when multipathing is
It is possible to test without multipath, this will take some time as I
no longer have anything with 16.04 installed. For fun I may go ahead
and try with 17.04 so we can figure out if it still exists then we'll
kind of kill two birds with one stone.
--
You received this bug notification because
iSCSI disks are not the root/boot disks.
Multipath IS in use. Hence the /dev/mapper at the beginning of the disk
names.
Yes I have tried 16.10, it is still present and I have another bug for
that release. https://bugs.launchpad.net/bugs/1636862
--
You received this bug notification because
Any idea on this one folks?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1569925
Title:
Shutdown hang on 16.04 with iscsi targets
Status in systemd package in Ubuntu:
Any movement here?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1636862
Title:
Shutdown hangs with active iscsi sessions
Status in systemd package in Ubuntu:
This bug (if it's a bug) also affects sys-libs/glibc-2.23-r3 on Gentoo.
The Qt Blog has a post about this issue from 2011:
http://blog.qt.io/blog/2011/10/28/rpath-and-runpath/
This may not be a bug: it is possible that DT_RUNPATH was never intended
to be transitive. However, if this is so, then
on reboot at the
'Reached target shutdown" message. Are there any logs that I can provide to
assist in troubleshooting?
Thanks,
-Matt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Removing ntpdate should remove the if-up script, so I imagine that would
"resolve" the bug by way of workaround.
The hosts in question were upgraded from prior LTS, so they would have
inherited ntpdate from there. I wasn't aware of the changes to sunset
it in the current release.
--
You
Public bug reported:
After the 6:9.20-0ubuntu0.14.04.1 security update, playing an XVID
stream in an AVI container segfaults decoding video frames. Reverting
to 6:9.11-2ubuntu2 works -- I can't find a .deb for the previous 9.18
release, but this system was playing videos without issue until
1 - 100 of 185 matches
Mail list logo
