EDIT: THIS IS THE WORKAROUND:
bind 'set enable-bracketed-paste off'
The proposed work around does NOT work for me. It could be due to the fact that
it is over ssh?
I am sshing from 18.04 into 22.04.
Bash version on former is 4.4.20(1)-release
Bash version on latter is 5.1.16(1)-release
I CANNOT
Here is another example of a tool that fails to work as expected because
it expects strict compliance to PEP 440: https://github.com/tox-
dev/pipdeptree/issues/235 .
This affects older Ubuntu releases like Bionic and Focal too.
I hope adding another example like this helps to justify fixing this
*** This bug is a duplicate of bug 1855757 ***
https://bugs.launchpad.net/bugs/1855757
The fix is changing my background offten?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
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
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
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
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
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
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
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
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"
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
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
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:
I searched through /var/log/apt history files and resolvconf gets sucked
in as a dependency when I install the proprietary vpn-unlimited
application from Keepsolid.
If I remove resolvconf, is it necessary to re-install or re-configure
any other components? I realize that might break vpn-unlimited
Public bug reported:
Ubuntu 17.10 amd_64
resolvconf 1.79ubuntu8
The symlink at "/etc/resolvconf/resolv.conf.d/original" points to
"../run/systemd/resolve/stub-resolv.conf". This is a broken link as the
relative path does not exist. This causes resolvconf to improperly
(re-)generate
Public bug reported:
loose of sound completely every update its becoming more difficult to
restore
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
Uname: Linux 4.4.0-71-generic i686
.tmp.unity_support_test.0:
Public bug reported:
updated computer than tried printing a floor plan from the internet.
"print to file" was displayed in print window , clicked on printer icon
and it said no printer connected to server.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups (not installed)
I retested to make sure this bug is valid on my hardware. Apparently it
would seem there is a time limit for entering the Wi-Fi password, if the
Wi-Fi password is entered within the time limit the Wi-Fi password is
accepted otherwise password must be entered and saved from the Edit
Connections
Public bug reported:
Ubuntu 16.04.2 Live Session ISO test
Entered WI-FI password twice does connect
Then using from network menu right portion of top panel choosing Edit
Connections >> Edit >>WI-FI >> Edit >> Wi-Fi security manually entering and
saving Wi-Fi password.
The Ubuntu 16.04.2 Live
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:
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
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 required
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
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
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,
Scratch that, loading the modules allows it to work with a *single* IPv4
route, but I get the same error if I try to connect with multiple roots.
My NetworkManager output to syslog is attached.
** Attachment added: "NetworkManager.log"
I needed to load all three of these modules to get it to work:
nf_nat_pptp, nf_conntrack_pptp, nf_conntrack_proto_gre
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Public bug reported:
This package failed to be configured during an upgrade.
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: gconf2 3.2.6-3ubuntu3
ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1
Uname: Linux 4.2.0-12-generic x86_64
ApportVersion: 2.19.1-0ubuntu2
Architecture:
Here's some more info:
I ran "dpkg --configure -a" as root, which failed.
Then I ran "sudo dpkg --configure -a" as my user with sudo privileges
and it worked. Now my system is not in an unconfigured state.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I am getting the following still.
# docker run -i -t ubuntu /bin/bash
set apparmor profile docker-default: no such file or directory2014/10/13
11:05:41 Error response from daemon: Cannot start container
7981801146ab1771470fd72bc97e6582ff573fa159199f6cb86afaa7eaa74ea9: set apparmor
profile
I also tried the 3.17.0-031700-generic #2001410060605 linked above. It
also does not work on that kernel.
# docker run -i -t ubuntu /bin/bash
Unable to find image 'ubuntu' locally
Pulling repository ubuntu
1357f421be38: Download complete
511136ea3c5a: Download complete
1de2bd7201a2: Download
Just so you know, here's the docker.io package version also:
ii docker.io 1.2.0~dfsg1-1ubuntu1 amd64Linux container runtime
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
I just found that the apparmor profile for docker was disabled for some
reason. After removing the symlink from /etc/apparmor.d/disable/docker,
it works. I don't remember ever adding docker to the apparmor disable
links.
--
You received this bug notification because you are a member of Ubuntu
I discovered this problem this morning while trying to set up my laptop
with a bluetooth headset (Moto S305) for a pending video conference.
Some Googling led me to this thread and comment #93, and the fix works
just fine. Trusty being a LTS release, there are sure to be many other
people affected
37 matches
Mail list logo
