Public bug reported:
I recently installed Ubuntu Server 20.04 to replace an ESXi server.
During the installation, I configured a bonded interface for two
ethernet interfaces. I configured the bond on my ZyXel GS1900-8 as a
static LAG. During the setup process, the link came up successfully and
was
> your bonded links are down; nothing will happen until they are brought
up.
Yes, I figured as such. I've already tried to bring up eth0, eth1, and
bond0 via ip, ifup, and ifconfig to no success.
> your pasted log appears incomplete since i see no output for eth0 or
eth1; please paste or attach y
I thought this could be related to
https://bugzilla.kernel.org/show_bug.cgi?id=199813. Indeed dmidecode -t
41 shows there are two interfaces for type interface 1 and two for 2.
** Bug watch added: Linux Kernel Bug Tracker #199813
https://bugzilla.kernel.org/show_bug.cgi?id=199813
--
You recei
There's a BIOS update available for my board. I'll install this and
hopefully I won't need a SW fix.
--
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/1908140
Title:
Bond DHC
The BIOS update does indeed fix the type interface number issue. This
ticket can be marked as a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578141 and closed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Thank you for all of your help!
--
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/1908140
Title:
Bond DHCP fails on Ubuntu Server 20.04 netplan
Status in systemd package in
Public bug reported:
I am using systemd version 248.3-1ubuntu3 from the impish repository.
It was compiled and built in the following manner:
# add impish deb-src repository to apt sources
apt build-dep systemd/impish
apt source -b systemd/impish
Once built, it was installed over the top of syst
I'm not a bash script architect, but I bodged together this workaround
and the ipmiutil_wdt service starts correctly with it applied to my
system:
https://gist.github.com/TheWug/1a7f509e040f10c05039acc06fe29d9e
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
It also looks like, farther down, systemctl_redirect() leaks $service.
Not sure if it's intentional or not, given that it works to protect its
other variables, so maybe it could use some attention too.
https://gist.github.com/TheWug/e120145f08e994d89e235e077a82ea75#file-40-systemd-L70
--
You rec
** Description changed:
I have noticed that Kubuntu 18.04 (Bionic Beaver) does not login to
public Wifi hotspots without wifi security, that require login through a
web page. I don't know if this is reproducible on arbitrary public
networks, or only on the few I tried.
The solution wa
This issue is still happening in Ubuntu 18.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1610944
Title:
GNOME Online Accounts breaks if you log out
Public bug reported:
In Ubuntu 18.10 if the blank screen feature initiates (5 minutes
default) the system will remain blank and there is no way to get the
display back on without a hard reset. The video card I am using is a
Vega 64. Other users who have Vega AMD GPU's are experiencing the same
iss
Public bug reported:
Speakers and HDMI sound work fine, only headphones not working. I went
through all of the steps on
https://help.ubuntu.com/community/SoundTroubleshootingProcedure
https://help.ubuntu.com/community/SoundTroubleshooting
and
https://wiki.ubuntu.com/DebuggingSoundProblems
and su
** Description changed:
Speakers and HDMI sound work fine, only headphones not working. I went
through all of the steps on
https://help.ubuntu.com/community/SoundTroubleshootingProcedure
https://help.ubuntu.com/community/SoundTroubleshooting
and
https://wiki.ubuntu.com/DebuggingSoun
My initramfs-tools seems to be part of the problem too:
sudo apt-get install --reinstall initramfs-tools
> E: Internal Error, No file name for initramfs-tools:amd64
sudo apt-get install initramfs-tools
> subprocess installed post-installation script returned error exit status 1
> Errors were enco
.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0c: ryan 3043 F...m pulseaudio
/dev/snd/controlC0: ryan 3043 F pulseaudio
CurrentDesktop: GNOME
Date: Wed May 31 15:47:08 2017
EcryptfsInUse:
Hi Daniel,
Thank you for reaching out. I ran
sudo apt remove timidity*
and then rebooted. It did not fix the issue.
Thanks,
-- Ryan Viertel
On Sun, Mar 31, 2019 at 11:40 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> Please try uninstalling 'timidity'
Public bug reported:
when computer is coming out of suspension mode, i get terrible screen
flickers. Only way i have worked around this is a reboot.
This video card is from sapphire
Nitro + SE 5700xt
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignatur
This bug has starting affecting one of my production servers. I would
classify it as "critical". I turned off and uninstalled the screensaver
on this computer, but apparently that is not enough to prevent Ubuntu
from going to sleep. It will go to sleep by itself even if there is NO
SCREENSAVER app
Public bug reported:
after installing a few updates my laptop won't boot up normally.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic i686
.tmp.unity.support.test.0:
Apport
This issue also effects 16.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-bluetooth in
Ubuntu.
https://bugs.launchpad.net/bugs/1126108
Title:
Indicator disappears entirely when disabling / turning off bluetoo
I tested the ppa in comment #5, and I note the following changes.
Environment is a docked laptop with 2 external displays.
When the laptop is removed from the dock (external displays
disconnected), I no longer receive a segfault for plasmashell, but the
panel does not automagicailly resize to the
I'm seeing similar behavior to the previous PPA, when the screens are
disconnected the panel fails to resize, and when the screens are
reconnected plasma segfaults. Note that in my configuration, the
internal display is disabled by kscreen to allow both external monitors
to activate.
--
You recei
I've recently updated to a mainline kernel build (4.7.0 201608021801)
and the audio output from the dock is working now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/15
Public bug reported:
Whenever I try to create a new wifi connection with WPA2 Enterprise
security and LEAP authentication, the Save (or Connect) button is grayed
out. I put in all of the required information; like SSID, Username, and
Password. It still does not let me Save or Connect.
Description
Public bug reported:
Thinkpad T460, Ultra dock, 2 channel speakers connected to dock.
4.4.0-18 Kernel / 16.04.
When the laptop is docked & speakers are connected to the dock audio
connector, I get no audio outpout from the dock audio connector.
Looks like the same issue as reported in:
https://b
In my case Chrome causes the crashes, mostly when I open a new tab.
Starting Chrome with parameter --disable-gpu seems to prevent them (but
rendering is much slower).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in
Yesterday I did this:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1510970/comments/40
… and haven't experienced crashses since then. No "--disable-gpu" for
Chrome required anymore (see my comment
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1509846/comments/
As of today, this appears to have been resolved.
--
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/1558660
Title:
Unable to create Wifi connection with WPA2 Enterpris
Public bug reported:
15.04
Using Appgrid
Expected it to install
It failed
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: libpam-ck-connector:amd64 0.4.6-5
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
NonfreeKernelModules: wl
Apport
No brightness issues when I disconnect the external monitor while the
notebook screen has focus (click on a window or the empty desktop on the
notebook screen).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
h
That affects different Google Chrome inputs. Address bar, Google search
bar, Google Keep inputs and so on. It's not limited to a special
extension. (I use a Zenbook Prime UX31A with Ubuntu 14.04 running.)
Maybe other programs are affected too, but I don't think so. Can't
reproduce it with Gedit for
Public bug reported:
Today, APT Performed the following update:
Start-Date: 2024-03-02 16:23:10
Commandline: aptdaemon role='role-commit-packages' sender=':1.304'
Upgrade: tcpdump:amd64 (4.99.1-3ubuntu0.1, 4.99.1-3ubuntu0.2),
libglx-mesa0:amd64 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubun
** Summary changed:
- Wine program crashes with unhandled page fault on startup
+ [regression] Wine program crashes with unhandled page fault on startup
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://
Public bug reported:
When specifying vers=4.0 or nfsvers=4.0 in NFSv4 mount options, the
client ends up using version 4.2 instead. This option seems to be
ignored.
This happens with pam_mount and manual mount. We have been using
pam_mount for years with the option vers=4.0, but now it appears to
** Description changed:
When specifying vers=4.0 or nfsvers=4.0 in NFSv4 mount options, the
client ends up using version 4.2 instead. This option seems to be
ignored.
This happens with pam_mount and manual mount. We have been using
pam_mount for years with the option vers=4.0, but now
Public bug reported:
#> lsb_release -rd
Description:Ubuntu 20.04.4 LTS
Release:20.04
#> apt-cache policy apt
apt:
Installed: 2.0.9
Candidate: 2.0.9
Version table:
*** 2.0.9 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64
Packages
100 /var/l
Simply stating that you no longer protect the last installed kernel and
providing a link to the details is preferred over making one feel
inadequate for reporting a perceived issue.
"apt-auto-removal" is not specifically mentioned in the changelog since
v0.9.12, and apt-file continues to indicate
Public bug reported:
possibly relating to locked boot disk.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
NonfreeKernelModules: nv
Public bug reported:
1) # lsb_release -rd
No LSB modules are available.
Description:Ubuntu 24.04 LTS
Release:24.04
2) # apt-cache policy lxc-dev
lxc-dev:
Installed: 1:5.0.3-2ubuntu7
Candidate: 1:5.0.3-2ubuntu7
Version table:
*** 1:5.0.3-2ubuntu7 500
500 http://archive.u
I'm not sure exactly how the liblxc.a static lib was dropped, but the
attached debdiff resolves this by not removing all .a files (an extra
find|rm is around a comment about removing all .la files) and then
adding the file to lxc-dev.install
This produces a lxc-dev deb which includes the static l
dpkg --contents on lxc-dev_5.0.3-2ubuntu7_amd64.deb
** Attachment added: "output from dpkg --contents on
lxc-dev_5.0.3-2ubuntu7_amd64.deb"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2080069/+attachment/5814926/+files/lxc-dev_5.0.3-2ubuntu7_amd64.deb.contents
--
You received this bug
** Patch added: "Diff of dpkg --contents file column only between 7 and 8"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2080069/+attachment/5814925/+files/file-list.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
dpkg --contents lxc-dev_5.0.3-2ubuntu8_amd64.deb output
** Attachment added: "dpkg --contents lxc-dev_5.0.3-2ubuntu8_amd64.deb output"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2080069/+attachment/5814927/+files/lxc-dev_5.0.3-2ubuntu8_amd64.deb.contents
--
You received this bug noti
I generated the smaller diff with:
$ diff -u <(awk '{print $6}' lxc-dev_5.0.3-2ubuntu7_amd64.deb.contents )
<(awk '{print $6}' lxc-dev_5.0.3-2ubuntu8_amd64.deb.contents) > file-
list.diff
so one can just see which files were added/removed vs the date/timestamp
change on files that are in both ar
Public bug reported:
1) # lsb_release -rd
Description:Ubuntu 20.04.5 LTS
Release:20.04
2) # apt-cache policy systemd
systemd:
Installed: 245.4-4ubuntu3.19
Candidate: 245.4-4ubuntu3.19
Version table:
*** 245.4-4ubuntu3.19 500
500 http://azure.archive.ubuntu.com/ubuntu
Public bug reported:
1) # lsb_release -rd
Description:Ubuntu 20.04.5 LTS
Release:20.04
2) # apt-cache policy systemd
systemd:
Installed: 245.4-4ubuntu3.19
Candidate: 245.4-4ubuntu3.19
Version table:
*** 245.4-4ubuntu3.19 500
500 http://archive.ubuntu.com/ubuntu focal-
To reproduce what happens on physical systems I create two VMs with nics
in the same bridge on the host. Booting the first VM up and allowing
the network config to apply, and then when booting the second VM up
layer, as it applies the IPv6 address to the interface in the bridge,
the kernel detects
# Create a bridge and add two ports
$ sudo ip link add name atx-fabric0 type bridge
$ sudo ip link set up dev atx-fabric0
$ sudo ip tuntap add atx-fabric0i1p1 user $USER group $USER
$ sudo ip tuntap add atx-fabric0i2p1 user $USER group $USER
# create two focal VM images from focal daily server
$
** Attachment added: "netplan config for vm1"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2000325/+attachment/5637220/+files/50-v4-v6-fail-vm1.yaml
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubun
** Attachment added: "netplan config for vm2"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2000325/+attachment/5637221/+files/50-v4-v6-fail-vm2.yaml
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubun
There are two scenarios: Applying to VM the first time, on subsequent
boots.
On first boot without the updated netplan config, when you first add it
root@ubuntu:/home/ubuntu# ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:
root@ubuntu:/home/ubuntu# networkctl status eth2-2 --no-pager
● 2: eth2-2
Link File: /run/systemd/network/10-netplan-eth2-2.link
Network File: /run/systemd/network/10-netplan-eth2-2.network
Type:
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
--
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/2000325
Title:
ipv6 duplicate address pr
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
--
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/2000170
Title:
bond interface down: devi
I am facing this issue on Ubuntu 22.04 LTS as well so I suspect that
this is not related to the operating system per se but more of the
package and how it interacts with google. I have attached my
dependencies as well as my full cpuinfo.
** Attachment added: "Dependencies.txt"
https://bugs.lau
** Attachment added: "ProcCPUinfoFull.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2039235/+attachment/5712189/+files/ProcCPUinfoFull.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-o
Can confirm that the workaround worked for me as well. I had a yubikey
on my google account and that was what caused the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.laun
Public bug reported:
As reported in the following question, Ubuntu 22.04 is currently missing the
CMake installation files from tinyxml version 9.0.0.
https://answers.launchpad.net/ubuntu/+source/tinyxml2/+question/708581
These were added in the following source PR as part of the 9.0.0
release:
On Fri, May 14, 2021 at 01:36:12PM -, Stephane Chazelas wrote:
>The important backtrace in there is the one from thread 11:
>
>#0 0x7fb288428474 in read () from /lib/x86_64-linux-gnu/libpthread.so.0
>No symbol table info available.
>#1 0x7fb2890c4518 in ?? () from /usr/lib/x86_64-linu
On Wed, May 19, 2021 at 06:46:02PM -, Sergio Durigan Junior wrote:
>Ryan, IIUC the patch you're proposing fixes the issue experienced by
>Stephane, but we're not entirely sure that it's the same issue being
>reported in this bug. Am I right?
Yes, exactly.
(My debd
Public bug reported:
This s390x VM has been upgraded to Jammy, including the host (qemu-
system-s390x 1:6.2+dfsg-2ubuntu6). Now any attempt to use ssh, or any
incoming sshd attempt immediately results in e.g.:
ryan@s390x-dev:~$ ssh g...@github.com
[ 433.672800] User process fault: interruption
to use ssh, or any
incoming sshd attempt immediately results in e.g.:
ryan@s390x-dev:~$ ssh g...@github.com
[ 433.672800] User process fault: interruption code 0011 ilc:3 in
libc.so.6[3ffa6c0+1ca000]
[ 433.672946] Failing address: 02aa0b84d000 TEID: 02aa0b84d800
[ 433.672
client/server upon Jammy upgrade
Status in openssh package in Ubuntu:
New
Bug description:
This s390x VM has been upgraded to Jammy, including the host (qemu-
system-s390x 1:6.2+dfsg-2ubuntu6). Now any attempt to use ssh, or any
incoming sshd attempt immediately results in e.g.:
t for smbk5pwd.
* Stop disabling test060-mt-hot on ppc64el. The underlying kernel bug
(#866122) is fixed in all relevant suites by now.
-- Ryan Tandy Fri, 27 Aug 2021 09:42:31 -0700
openldap (2.4.57+dfsg-3) unstable; urgency=medium
* Link smbk5pwd with -lkrb5. (Closes: #9
This is still broken on impish when running i3 under X11.
Oct 22 15:23:39 operations /usr/libexec/gdm-x-session[5615]:
/etc/X11/Xsession.d/30x11-common_xresources: line 16: has_option: command not
found
Oct 22 15:23:39 operations /usr/libexec/gdm-x-session[5646]:
/etc/X11/Xsession.d/75dbus_dbus
Public bug reported:
I want to implement pam_faillock which replaces pam_tally2 but requires pam
version >= 1.4.0
The ability to 'reliably' lock accounts after a certain number of failed
attempts is a requirement of the NIST 800-171 controls implemented by many U.S.
government agencies and cont
Fixed in 2.4.51+dfsg-1 i.e. groovy
** Changed in: openldap (Ubuntu)
Assignee: Ryan Tandy (rtandy) => (unassigned)
** Changed in: openldap (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
On Sat, Mar 27, 2021 at 01:06:42AM -, Vincent Vanlaer wrote:
>https://git.openldap.org/openldap/openldap/-/commit/735e1ab
Note that this commit is for OpenLDAP 2.5 and needs adjustment for the
2.4 branch. The commit ids for 2.4 are:
https://git.openldap.org/openldap/openldap/-/commit/7cf7aa3
@Daniel van Vugt - Thank you for suggesting the change in post #60. It
didn't work for me though.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1576559
Title:
Refused
There is a patch now that is expected to be in kernel version 5.13.
If you're willing to build your own kernel, you can find the patch here
and do it yourself:
https://github.com/thesofproject/linux/issues/2748
** Bug watch added: github.com/thesofproject/linux/issues #2748
https://github.com
There is a patch now that is expected to be in kernel version 5.13.
If you're willing to build your own kernel, you can find the patch here
and do it yourself:
https://github.com/thesofproject/linux/issues/2748
** Bug watch added: github.com/thesofproject/linux/issues #2748
https://github.com
I also have this bug on Ubuntu 22.04 following this guide, aside from setting
it to my user.
https://code.luasoftware.com/tutorials/linux/ubuntu-prompt-system-policy-prevents-modification-of-network-settings-for-all-users
[Let all users modify system settings for network]
Identity=unix-user:ryan
Public bug reported:
I am attempting to install Zoom onto my laptop. Any assistance would be
greatly appreciated. Thank you!
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: cups-bsd 2.3.1-9ubuntu1.5
ProcVersionSignature: Ubuntu 5.15.0-83.92~20.04.1-generic 5.15.116
Uname: Linux 5.15.0-8
Hello Hector,
On Fri, Mar 22, 2019 at 12:36:57PM -, Heitor R. Alves de Siqueira wrote:
>The slapd package for OpenLDAP is shipped with a SysV-style init script
>(/etc/init.d/slapd). Systemd automatically converts this to a systemd
>service by generating the unit file using the systemd-sysv-g
Public bug reported:
This happened on a near-fresh install of 18.04 on a new computer. I was
having trouble getting the NVIDIA proprietary drivers working. So I did
quite a bit of install/uninstall cycles, failing to get the NVIDIA
drivers working. I couldn't seem to get the NVIDIA drivers to w
It seems there are some limitations to what systemd will do with
IPv6BytesMTU.
1) if LinkLocalAddressing is not disabled, it will clobber any
IPv6BytesMTU value set.
[Network]
LinkLocalAddressing=ipv6
Address=10.10.10.10/24
IPv6MTUBytes=1470
This results in: /proc/sys/net/ipv6/conf//mtu having a
On Mon, Nov 26, 2018 at 11:11 PM Jay Vosburgh
<1671...@bugs.launchpad.net> wrote:
>
> Regarding #2 from comment #19:
>
> As the defined range for the ipv6.mtu is from IPV6_MIN_MTU to the
> device's MTU, and the existing API returns an error if the ipv6.mtu is
> out of range, I think it's reasonable
On Tue, Dec 4, 2018 at 6:31 AM Dimitri John Ledkov
wrote:
> Using systemd 237-3ubuntu10.10
>
> Using:
> [Match]
> Name=ens3
> [Network]
> DHCP=ipv4
> IPv6MTUBytes=1600
> [Link]
> MTUBytes=1800
> [DHCP]
> UseMTU=no
> RouteMetric=100
>
Do you put this in the same .network file or .link file?
--
On Tue, Dec 4, 2018 at 9:31 AM Ryan Harper
wrote:
>
>
> On Tue, Dec 4, 2018 at 6:31 AM Dimitri John Ledkov
> wrote:
>
>> Using systemd 237-3ubuntu10.10
>>
>> Using:
>> [Match]
>> Name=ens3
>> [Network]
>> DHCP=ipv4
>> IPv6
Public bug reported:
Running bionic's 4.15 kernel on trusty on an HPE DL385 Gen10 results in
a device node for the NVMe controller,
/devices/pci:40/:40:03.1/:43:00.0/nvme/nvme0/nvme0c33n1
which itself does not have a devname. When mountall gets to it:
fsck_update: updating check prio
** Patch added: "lp1807077-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+attachment/5219619/+files/lp1807077-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mountall in Ubu
** Patch added: "lp1807077-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+attachment/5219620/+files/lp1807077-xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mountall in Ubu
** Description changed:
+ [Impact]
+
+ * udev block nodes without a devname will crash mountall, resulting in
+ an unbootable system (emergency root shell)
+
+ * While this is not likely to happen in a matched distro/kernel
+ environment (it was discovered while needing to run a bionic 4.15 ke
** Tags added: patch trusty xenial
** Also affects: mountall (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: mountall (Ubuntu Xenial)
Importance: Undecided
Status: New
** Summary changed:
- mountall crashes on udev node with missing devname
+ [SRU] mountal
Thanks. I saw xenial had mountall and figured maybe there was
transition path where it was used, but if it's vestigial, I agree this
should be trusty-only.
** Tags removed: xenial
** Patch removed: "lp1807077-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+at
** Changed in: mountall (Ubuntu Trusty)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/1807077
Title:
[SRU] mountall crashes on udev node
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/1807
** Description changed:
[Impact]
- * udev block nodes without a devname will crash mountall, resulting in
+ * udev block nodes without a devname will crash mountall, resulting in
an unbootable system (emergency root shell)
- * While this is not likely to happen in a matched distro/ker
Hello Mario,
This was an intentional change by OpenLDAP developers, in order to fix a
replication bug that could cause providers and consumers to lose sync.
Please see the upstream issue for the full details:
http://www.openldap.org/its/?findid=6545
I confirm this behaviour on a producer runni
** Changed in: openldap (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1809938
Title:
delta syncrepl generates reqMod Attribute 'co
Looks like this issue, I think:
https://github.com/systemd/systemd/issues/12490
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubunt
** Changed in: netplan
Status: Incomplete => Invalid
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
@Dan/Chad I suggest we skip-by this bug number on the eoan vlan test
case;
--
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/1846232
Title:
vmtests: test_ip_output failing i
This can be reproduced in an LXD Eoan container:
lxc launch ubuntu-daily:eoan e1
lxc exec e1
cat > /etc/netplan/50-cloud-init.yaml << EOF
network:
version: 2
ethernets:
eth0:
dhcp4: false
mtu: 1500
vlans:
eth0.2667:
id: 2667
This looks to be related to networkd:
https://github.com/systemd/systemd/pull/12574/commits
Which is automatically added 4 bytes to base interface MTU, even though
we're explicitly setting mtu to 1500 on base interface and vlan.
** Also affects: systemd (Ubuntu)
Importance: Undecided
I cannot verify this is working on bionic with ipv6 static addresses.
root@ubuntu:~# lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04
root@ubuntu:~# cat /etc/cloud/build.info
build_name: server
serial: 20191021
root@ubuntu:~# uname -a
Linux ubuntu 4.15.0-66-generic #75-Ubu
The original netplan yaml I was testing was simpler, but also failed so
I tried to see if additional settings would make a difference, but it
did not.
network:
version: 2
ethernets:
interface0:
dhcp4: true
match:
macaddress: '52:54:00:12:34:0
In the Eoan version of systemd, I can see in the logs these messages:
Oct 24 18:52:32.753746 ubuntu systemd-networkd[1167]: Setting
'/proc/sys/net/ipv6/conf/interface1/proxy_ndp' to '0'
Oct 24 18:52:32.753848 ubuntu systemd-networkd[1167]: Setting
'/proc/sys/net/ipv6/conf/interface1/use_tempaddr
I did some more testing today. I upgraded systemd and netplan.io to
disco level, rebooted and tested the MTU settings; disco packages fail
as well. I then upgraded to eoan systemd/netplan.io rebooted and the
MTU settings are correct.
--
You received this bug notification because you are a memb
1 - 100 of 725 matches
Mail list logo
