For me, this issue has now been resolved; I assume due to the pulseaudio
package updates that I installed yesterday, but it might have been fixed
for a few days longer.
** Changed in: alsa-driver (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a
Sorry, please ignore my previous comment (comment 6); I'd copied the
netplan config from another machine and adjusted all the IPs, but forgot
to change the interface name, so the entries were ignored.
Basic IP connectivity was working since I have an encrypted volume
that's unlocked via the initrd
Uggh. On a second system that I upgraded 16.04->18.04->20.04, I have
netplan installed and a configuration file in place. However, the DNS
entry in the netplan config is ignored, so even switching to netplan
doesn't fix this bug:-(
--
You received this bug notification because you are a member of
The system has resolvconf 1.82 installed. /etc/resolv.conf claims that
it's generated by resolvconf, at least after I switched the system to
netplan, and I'm pretty sure it did before to. I also have ifupdown
0.8.35ubuntu1 installed.
A thought on deprecation: A deprecated package is simply somethi
Switching to netplan does avoid this issue, but doesn't directly solve
it.
--
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/1883412
Title:
20.04: DNS servers from /etc/netwo
Oh, and /etc/resolv.conf contains:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the ac
Public bug reported:
I have a server that uses /etc/network/interfaces to configure static IP
info, including DNS, via /etc/network/interfaces. This worked fine in
16.04 and 18.04. However, when I updated to 20.04 this no longer works;
I have to run "systemd-resolve --set-dns=192.168.63.1
--interf
My headset (which works fine) is USB.
Which bug do you believe this is a duplicate of? I did find something
similar, but it was on 16.04, and my issue is definitely a regression
between 18.04 and 20.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded package
I ran alsa-info before/after running "sudo alsa force-reload" to see if
there were any obvious differences in the output. While there are a few
differences, nothing really stands out as causing this issue.
** Attachment added: "diff for alsa-info output before/after reloading alsa"
https://bug
Public bug reported:
I had Ubuntu 18.04 installed, running XFCE (Xubuntu session), and audio
worked fine, using either the built-in speakers/mic on the laptop or via
a USB headset when that was plugged in.
However, after upgrading to 20.04, the built-in audio device is no
longer available until I
For my own understanding, I'm curious:
a) Whether Ubuntu toolchains are usually updated for bugs like this
b) Roughly how often toolchain updates are usually released. I suppose
you're busy with Spectre stuff right now though?
--
You received this bug notification because you are a member of Ub
Public bug reported:
gas in binutils 2.26 contains a bug that prevents compilation of ARM
Trusted Firmware in particular, or any code that references the "."
symbol following a .align statement that specifies explicit padding
data.
ATF bug report: https://github.com/ARM-software/tf-issues/issues/
After updating to the latest packages, this issue is solve. I can lxc-
start, lxc-attach, lxc-stop, and lxc-execute.
I do get some warning/error spew when running lxc-execute though. If
this looks unexpected, I can open a separate bug for it:
$ lxc-execute -n t1 -- /bin/bash
lxc-execute: utils.c:
Thanks. The chown solves the issue. I didn't need to make the
modification to the pam config file at all. I do need to do the chown
every time I log in though, with or without the pam change.
FWIW, when I ssh into the working server, the relevant /sys directory is
owned by swarren:swarren without
Could you please expand on "Then re-chown your current systemd cgroup"?
I'm not sure exactly how/where cgroups get mounted, so I'm not sure what
path I should chown.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubunt
Yes, I'm running lightdm.
$ cat /etc/pam.d/common-session
session [default=1] pam_permit.so
session requisite pam_deny.so
session requiredpam_permit.so
session optionalpam_umask.so
session requiredpa
Switching the linode system to the Ubuntu kernel (booted via pv-grub)
didn't make that system fail. Perhaps the difference is cgroup setup via
ssh vs XFCE/GUI login?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubunt
I have 2 Xenial systems. They are both fully up-to-date as of 5 minutes
ago. The failing system is a laptop running XFCE GUI, and I'm attempting
to use LXC from a GUI terminal. The other system is a linode that I
access via ssh, and LXC works fine there. I believe I've configured the
two systems th
Public bug reported:
On Ubuntu Xenial pre-release, I see the following, so can't start a
container:
[swarren@sprint ~]$ lxc-create -t download -n t2 -- -d ubuntu -r trusty -a amd64
Using image from local cache
Unpacking the rootfs
---
You just created an Ubuntu container (release=trusty, arch=am
19 matches
Mail list logo
