Public bug reported:
Same failure as previously reported for LTS 24.04.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1:22.04.20
Uname: Linux 6.9.3-76060903-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
CasperMD5CheckResult: unknown
Cra
The tests are successful with both the crun and runc runtimes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2040483
Title:
AppArmor denies crun sending signals to containers (stop, kill)
To manage
As above, the tests specified for the SRU complete successfully with the
new packages installed.
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
** Tags removed: mantic server-todo
--
You received this bug notification bec
There's a possible additional issue with runc apparmor in
https://bugs.launchpad.net/ubuntu/+source/runc/+bug/2072452
that is affecting k8s in Noble. May be worth testing the fixed package
to see if it corrects that as well.
--
You received this bug notification because you are a member of Ubunt
Upstream fault report:
https://github.com/containerd/containerd/issues/10542
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072452
Title:
AppArmor denies crun sending signals to containers
To manag
unknown error after kill: runc did not terminate successfully: exit
status 1: unable to signal init: permission denied
** Also affects: runc (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: github.com/containerd/containerd/issues #10542
https://github.com/containerd/con
You are all very welcome to use the version in the Brightbox
Experimental PPA
(https://launchpad.net/~brightbox/+archive/ubuntu/experimental), which
has a Noble update with the fix in it.
Bear in mind the title of the PPA: "Here be dragons"
--
You received this bug notification because you are a
I have Xubuntu 23.04 on one drive and 22.04 on another drive as a
backup. I have upgraded to 24.04 twice, once when it became available
and some time around the middle of June. The computer would not boot
after I upgraded. I also have Windows 11 on another drive. I am looking
forward to when I can
port.
> https://bugs.launchpad.net/bugs/2040483
>
> Title:
> AppArmor denies crun sending signals to containers (stop, kill)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptio
Thank you for your reply.
My main goal was to raise awareness since it wasn't clear to me whether
anyone was aware of this issue. As I mentioned previously, it would be
great to be able to install in PVH mode since it is "the best" mode
currently available as I understand it based on this page:
h
PR accepted upstream. I've backported the patch the oracular MP above.
What needs to be done now to get this into an SRU for noble?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2040483
Title:
AppA
PR opened upstream: https://github.com/containers/common/pull/2004
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2040483
Title:
AppArmor denies crun sending signals to containers (stop, kill)
To ma
ubuntu@srv-9vqc0:~$ sudo grep -r "runbindable*/*" /etc/apparmor.d
/etc/apparmor.d/abstractions/passt: mount options=(rw, runbindable) /,
ubuntu@srv-9vqc0:~$ sudo aa-logprof
ERROR: Operation {'runbindable'} cannot have a source. Source =
AARE('/')
HTH
--
You received this bug notification bec
I've pushed the changes based on your comments to the MP above. I've
left the signal set for podman as (int, quit, term, kill).
Do you think that signal set should be tighter, or is that a good
compromise?
If that seems ok with you, I'll happily handle the PR upstream at
GitHub.
--
You received
The debdiff is in the MP above.
Podman does try to kill the container itself, as the error trace above
testifies.
May 14 11:14:41 srv-omzr6 kernel: audit: type=1400
audit(1715685281.392:118): apparmor="DENIED" operation="signal"
class="signal" profile="containers-default-0.57.4" pid=7458
comm="co
Adding the podman signal line, and building a libpod that overrides the
default packages eliminates the errors I was getting.
All the tests in this ticket pass with the updated packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've built a backported 4.9.4 libpod for noble based on an updated
golang-github-containers-common including the above patch.
It's available from ppa:brightbox/experimental
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
The debdiff I've put together for oracular updates the patch to be a bit
more general and cover all the signals I've seen so far in testing. (As
well as dropping the other patch that has been incorporated upstream).
# Allow certain signals from OCI runtimes (podman, runc and crun)
signal (r
The patch above doesn't work as it stands. We are still getting signal
filters in the audit log
May 14 11:13:06 srv-omzr6 kernel: audit: type=1400 audit(1715685186.296:112):
apparmor="DENIED" operation="signal" class="signal"
profile="containers-default-0.57.4" pid=8031 comm="3" requested_mask="
Public bug reported:
On the latest LTS, aa-logprof does nothing other than fail with the
error
ERROR: Operation {'runbindable'} cannot have a source. Source =
AARE('/')
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: apparmor-utils 4.0.0-beta3-0ubuntu3
ProcVersionSignature: User Name 6
To move this on a bit more rapidly as it is a blocking issue for me.
It's the same version in Oracular at present. I've pushed the changes as
an MP against ubuntu/devel.
What needs to happen next?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Merge proposal linked:
https://code.launchpad.net/~neil-aldur/ubuntu/+source/golang-github-containers-common/+git/golang-github-containers-common/+merge/465970
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Public bug reported:
The Xen server I am working on has Debian 12 as dom0. As mentioned in
the summary I am trying to install Ubuntu 22.04 server as a domU in PVH
mode.
I tested using ubuntu-22.04.4-live-server-amd64.iso.
This is the domU configuration I used. It attempts to use PVHGRUB:
name
NEW Remote Login - Ubuntu 24.04 LTS Noble Numbat (development branch) -
Log in to blank desktop with almost no functionality
Remote logged on using Remmina RDP to the 24.04 Desktop Remote Logon
and:
Mouse works, kind of.
I can click on and open the calendar.
Open and toggle Accessibility settin
Public bug reported:
Failed on upgrade from Ubuntu 18.xx to latest version for Jetson nano.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: chromium-browser 97.0.4692.71-0ubuntu0.18.04.1
Uname: Linux 4.9.253-tegra aarch64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: arm64
CasperMD5
On Mon, 31 Jan 2022, 07:05 Neil Mayhew, <1958...@bugs.launchpad.net>
wrote:
> FYI, Debian will likely update again to 8.12.42 which is a better release
> to work with long-term.
>
8.12.42 is now in Debian testing. Will Ubuntu sync again automatically?
>
--
You received thi
> Debian update to the current version which got synced to Ubuntu
That's good to hear.
FYI, Debian will likely update again to 8.12.42 which is a better
release to work with long-term. (It has a git tag, and the artefact
versions don't have "-SNAPSHOT" in them).
I assume this will sync automatic
Thank you for the suggestion. I linked to the upstream bug report that
describes the issue, but I can see that it's helpful to have a brief
summary in both downstream issues.
Previously, the C/C++ version of libphonenumber was accepting and
parsing phone numbers that have malformed UTF-8 sequences
Sure, updating the 7.0 version to include the .pc file for readline is a
fine approach to fixing this problem, but I dont think I would consider
this a low priority issue. There are 37 non-ubuntu service accounts
watching this bug, so it seems to have significant impact. Add to that
the fact that
Public bug reported:
The upstream project is now at 8.12.41. There are a number of bug fixes
in this release, including one for handling invalid UTF-8 sequences
correctly in the C version of the library.
See:
* https://issuetracker.google.com/issues/206677455
* https://github.com/google/libphone
sooo...Is anyone going to bother looking into this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938591
Title:
update 18.04 to readline8
To manage notifications about this bug go to:
https://bugs
Public bug reported:
I was installing UBUNTU 21.04
I was playing AisleRiot and Sudoku while the system installed. An error
message popped up referring to shim that I closed. Then the Bug Report
process started. I'll restart and see what happens.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Packa
** Package changed: ubuntu => linux-hwe-5.4 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947757
Title:
NVMe Write Zeroes command has incorrect values for PI modes
To manage notifications
Public bug reported:
The attached screenshot of a PCIe trace snippet is from Ubuntu 20.04.3
LTS, k5.4.0-73-generic, with an NVMe controller formatted to 4K+8 DIX
PI2
It shows
- A Single-sector Write Zeroes command with SLBA=0x02E18439, ILBRT=0x0 (valid
for PI2), PRCHK=0x0 (no checks), PRACT=0 *,
on here:
https://chng.it/n2kqmpfxgD
Thanks!
Neil
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/695825
Title:
Qemu is running without kvm acceleration in maverick
To manage notifications about this b
Just to mention, I am having this bothersome issue also. My Ubuntu 18.04
is completely up to date. Does anyone know of a DM that works better?
Cheers...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17
Public bug reported:
libreadline up until version 8 didn't include a pkg-config file, and so
any other package that relied on being able to find the readline
libraries using the autoconf PKG_CHECK_MODULES macro failed in build.
This has since been corrected, but I've received several reports of
pe
I can demonstrate that
https://cdimage.ubuntu.com/ubuntu-legacy-
server/releases/focal/release/ubuntu-20.04.1-legacy-server-amd64.iso
is affected. The installer prompts with
> Your installation medium is on /dev/sdb. You will not be able to create,
> delete, or resize partitions on this disk
I have finally proceeded with a partial upgrade. It seems to have
worked. I have not investigated all packages and PPAs yet. However I am
much relieved.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
I did that Ubuntu-release -upgrader -p. It asked me to install all available
updates. So I typed sudo apt-get updates. It did 5 lines:
Hit:1 http//mirror.intergrid.com.au/Ubuntu focal InRelease
Hit:2 http//mirror.intergrid.com.auUbuntu focal-updates InRelease
Hit:3 http//mirror.intergrid.com.a
options so I am not game to select either. What should I do?
Regards
Neil
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921798
Title:
I think it couldn't estimate what was needed for the up
Same as before.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921798
Title:
I think it couldn't estimate what was needed for the upgrade and said
it couldn't proceed
To manage notifications abou
2nd time this has occurred.
** Attachment added: "See screenshot of error message"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1921798/+attachment/5482220/+files/Screenshot%20from%202021-03-30%2010-02-23.png
--
You received this bug notification because you are a m
Public bug reported:
I have made several attempt to upgrade. I think the error massage is
different each time. This is the second one where I have submitted a
report as recommended.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.42
ProcVersionSignature:
Public bug reported:
I just thought it would upgrade from 18.04.5 LTS to 20 automatically but
I get an error message and don't know what to do . What is PPA, PPA-
Purge package and launchpad PPA? How do I know what is official and what
is unoffical Ubuntu software?
ProblemType: Bug
DistroRelease:
It's now 2021 - I'm on Ubuntu 20.04.2 LTS and I'm still being annoyed
by this bug!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778627
Title:
bash completion now quotes shell variable references r
Exploring further, this issue happens with the default theme (which is
Yaru-MATE-Light, I think) but not with Ambient-MATE, where the "Close"
button displays correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Public bug reported:
Ubuntu Mate 21.04 daily build fresh install today. Selected "Redmond"
layout. Installed nextcloud-desktop and connected to my server. Clicked
on the nextcloud icon in the panel and selected "settings".
What should happen:
- Nextcloud settings app should appear with close/mini
Wonderful. Thank you.
> On 7 Feb 2021, at 18:05, Dmitry Shachnev <1913...@bugs.launchpad.net> wrote:
>
> And finally it migrated.
>
> ** Changed in: puppet (Ubuntu)
> Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
I have prepared a 1ubuntu1 version with what I think is the missing
diff.
https://launchpad.net/~brightbox/+archive/ubuntu/experimental?field.series_filter=hirsute
which has been built from the following branch
https://code.launchpad.net/~neil-
aldur/ubuntu/+source/puppet/+git/puppet/+ref
** Changed in: puppet (Ubuntu)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913557
Title:
Please merge 5.5.22-1 into hirsute
To manage notifications about this
Similarly the Debian package passes a local Autopkgtest
Following 4.3 here: https://packaging.ubuntu.com/html/auto-pkg-test.html
#executing-the-test
$ sudo autopkgtest puppet -U --apt-pocket=proposed=src:puppet -- qemu
autopkgtest-hirsute-amd64.img
Gives
autopkgtest [10:55:15]: test command4:
Are there know differences between the Debian CI and the Ubuntu CI?
Because it passes autopkgtest over there.
https://ci.debian.net/data/autopkgtest/testing/amd64/p/puppet/10026148/log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Backport to Focal available at
https://launchpad.net/~brightbox/+archive/ubuntu/experimental
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913567
Title:
Sync puppet 5.5.22-1 (universe) from Debian
Public bug reported:
Please sync puppet 5.5.22-1 (universe) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
* d/t/control: fix second dep8 test by telling it to not use a proxy
for the "puppet" hostname, and allow stderr because of a ruby
deprecati
** Changed in: puppet (Ubuntu)
Status: New => 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/1913557
Title:
Please merge 5.5.22-1 into hirsute
To manage notifications about this
Public bug reported:
tracking bug
** Affects: puppet (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913557
Title:
Please merge 5.5.22-1 int
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: puppet 5.5.10-4ubuntu3
ProcVersionSignature: User Name 5.4.0-62.70-generic 5.4.78
Uname: Linux 5.4.0-62-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Jan 27 17:11:14 2021
PackageArchi
*** This bug is a duplicate of bug 1875848 ***
https://bugs.launchpad.net/bugs/1875848
Public bug reported:
The puppet 5.5 version available in Focal throws a lot of ruby warnings,
which interferes with the puppet installation traces.
remote: /usr/lib/ruby/vendor_ruby/puppet/util.rb:461: war
Public bug reported:
remote: ^[[1;31mError: Execution of '/usr/bin/gem install --no-rdoc --no-ri
uricp' returned 1: ERROR: While executing gem ... (OptionParser::InvalidOption)
remote: invalid option: --no-rdoc
remote: Did you mean? no-force^[[0m
remote: ^[[1;31mError: /Stage[main]/Mys_serv
Debian just updated to 8.12.16 and its bug was closed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797390
Title:
Update to 8.9.15
To manage notifications about this bug go to:
https://bugs.launch
I'm lost but the install hasn't worked
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877687
Title:
grub installation failed! I'm new in ubuntu and I was trying to
install ubuntu alongside of my w
Thanks Chris. I checked further on support sites. One suggested redirecting
sources (sources.list) from Eoan to "...old-releases.ubuntu...", which I did
and allowed me to upgrade to 20.04 (albeit the desktop still says 19.10). I'll
see what happens when I try next upgrade. If it's too messy, I'l
Public bug reported:
similar to #934371 but even less detail.
Was running "sudo do-release-upgrade"
result
"Calculating the changes
Calculating the changes
Could not calculate the upgrade
An unresolvable problem occurred while calculating the upgrade.
If none of this applies, then please rep
Problem seems to have resolved itself at 5.4.0-58
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895342
Title:
Acer Aspire E15 keyboard and trackpad non functional after update to
vmlinuz-5.4.0-47
Public bug reported:
I have a Lenovo t440.
The touchpad works fine from boot.
However when resuming from standby, occasionally the touchpad will stop
responding to any input. The keyboard still works fine. It has only happened
since upgrading to 20.04.
ProblemType: Bug
DistroRelease: Ubuntu 2
Has anyone put together a step-by-step tutorial (written or video), to
give a little detailed direction to these steps?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895422
Title:
Sound card not de
Same: uname -a
Linux … 5.4.0-54-generic #60-Ubuntu SMP Fri Nov 6 10:37:59 UTC 2020 x86_64
x86_64 x86_64 GNU/Linux
--
You received t
*** This bug is a duplicate of bug 1872159 ***
https://bugs.launchpad.net/bugs/1872159
Same bug affects me, I'm running 20.04 on an Asus Zenbook and can
confirm that removing "quiet splash" DOES NOT resolve the boot issue.
--
You received this bug notification because you are a member of Ubu
Public bug reported:
Installing Ubuntu in Virtualbox crashes 1/2 way through the install.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity 20.10.13
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl ic
Having not had any success with removing gnuradio, I tried removing
other things, including the PPAs I had removed before (I was aiming to
make one change at a tie to pin down the issue). It turns out that I had
a non-Ubunutu standard versions of sane and some associated libraries.
When I forced th
*** This bug is a duplicate of bug 1897747 ***
https://bugs.launchpad.net/bugs/1897747
Public bug reported:
Upgrading 18.04 to 20.04 failed
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.3
ProcVersionSignature: hostname 4.15.0-111.112-generic 4.15.18
U
Thanks for the suggestion. I did a complete removal of gnuradio-dev
using synaptic package manager, and then tried doing an upgrade.
Unfortunately I got the same result.
I then did a complete removal of gnuradio, and all installed libgnuradio
packages (they were 3.7.11-10, if that is any use). I t
Looks like a duplicate of Bug #1875523 and Bug #1875599.
Problem seems to be with python-is-python2 / python-minimal:
2020-10-03 08:28:12,888 INFO installing python-is-python2 because
python-minimal was installed
2020-10-03 08:28:12,889 DEBUG Installing 'python-is-python2' (python-minimal
was
Public bug reported:
Fails complaining about possible issue with PPAs. When these are removed
fails with no complaints about PPAs or anything else. Just asks for bug
to be reported.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.38
ProcVersionSignature:
options to 5.4.0-26: Keyboard/trackpad works
normally.
Some Fn buttons work after login, but only ones monitored by firmware
(E.g. screen brightness works, volume control doesn't)
neil@neil-Aspire-E5-511:~$ lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
ProblemType
Details from working guest 18.04
$ lsmod
Module Size Used by
isofs 45056 0
nls_iso8859_1 16384 1
kvm_intel 217088 0
kvm 614400 1 kvm_intel
irqbypass 16384 1 kvm
crct10dif_pclmul 16384 0
crc32_pclmul
Hi Christian
As you pointed out this does appear to be an issue with the reduced
kernel kvm image. I ran the same setup using a standard image and the
interface showed up. However after running your suggested updates from
comment A on the kvm kernal image, the interface still did not show up.
If
Thanks to everyone who contributed to this fix. I confirm that it works
for me in testing with Ussuri and Ubuntu Bionic on vmx-enabled GCP VMs;
with fixed qemu packages coming from cloud-archive:ussuri.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Public bug reported:
After setting up pci pass through for a virtual function it did not show up as
an interface in Ubuntu 20.04, it did however show up as a PCI device.
After reverting back to 18.04 with exactly the same configuration the interface
showed up as expected.
Bellow is the configu
Public bug reported:
Would you please make autoinstall work in bionic?
Thanks in advance.
** Affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
This is fixed with the following patch:
https://github.com/OpenSC/pam_pkcs11/pull/45
It looks like OpenSSL 1.1.0 handling for CRL's hadn't been implemented
in cert_vfy.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Hi, see attachment pam_pkcs11.conf - it's pretty much the generic 0.4
package demo file with some small changes. Below I've pasted the ls/cat
outputs for other files in the pam_pkcs11 folder
/etc/pam_pkcs11$ cat subject_mapping
/DC=com/DC=removedforsecurity/DC=xxx/OU=xxxx/CN=Ne
Confirming no icon in sys tray on upgrade from Mint 19.3 to 20. Blank
space where icon should be and the solaar menu when that space is left
clicked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17659
I don't believe this is to do with networking-calico, so will mark as
Invalid for networking-calico.
** Changed in: networking-calico
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Python 3 support was added in Calico v3.15
https://docs.projectcalico.org/release-notes/#v3150
The master networking-calico code now supports Python 3, and no longer
Python 2. There is a 'release-v3.15-python2' branch that still supports
Python 2, but we are hoping that maintenance of that branch
Public bug reported:
I also had a login loop. nothing unusual with my install - just
upgrading packages. Nothing custom.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: lightdm 1.30.0-0ubuntu3.1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
Christian, would it be easy for you to build this for Bionic as well? I
run tests with GCP instances as the OpenStack hypervisors, and have hit
this bug, so am keen to test your fix.
(http://lists.openstack.org/pipermail/openstack-
discuss/2020-June/015343.html)
--
You received this bug notific
I've managed to get the system to boot when not plugged into mains by
adding 'iommu=soft' to the linux line in grub.
Not sure at what cost but at least I don't lose my display info like
when nomodeset is used.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Just to provide a source, I got it from here (where it seems other
people have the same issue):
https://askubuntu.com/questions/1206472/ubuntu-18-04-and-20-04-stuck-on-
gnome-startup-on-battery-only
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Wrong package initially selected
** Package changed: coolkey (Ubuntu) => opensc (Ubuntu)
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
This affects me too - Ubuntu MATE 20.04, Lenovo T495 (so AMD
graphics/amdgpu).
Boots fine with power supply connected, but running from battery, laptop
POSTs ok, displays grub, displays boot msgs but then screen goes blank.
Happy to provide logs if you let me know what you need, I can SSH into
the
** Also affects: mate-desktop via
https://github.com/mate-desktop/marco/issues/595
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866657
Title:
Long
*** This bug is a duplicate of bug 1872778 ***
https://bugs.launchpad.net/bugs/1872778
Want to add my thanks as well Simon, I'm still getting a warning abut a
wildcard cert, but it's at least functional now!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
If the fix is not in the security pocket, how does it get sorted if the
updates pocket is turned off?
I understood *-updates are only supposed to be recommended.
As I mentioned if you build an image with a tool like 'mkosi' which utilises
debootstrap and then cleans the cache, the partial direc
Public bug reported:
The "System Problem Detected" dialog appeared after I closed a game. I
did not notice any problem. I note the error message is the same as in
https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1863392 but I'm
using the "fix-released" package.
ProblemType: Crash
DistroReleas
Public bug reported:
I was confronted with the System Error dialog when closing a game. I
hadn't noticed anything wrong.
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: marco 1.24.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
Nonfr
Expires: 14/03/21
```
## On Ubuntu 19.10 (Working)
```
neil@thinkpad:~$ apt search evolution
Sorting... Done
Full Text Search... Done
evolution/eoan,now 3.34.1-2 amd64 [installed]
groupware suite with mail client and organizer
neil@thinkpad:~$ apt search evolution-ews
Sorting... Done
Full Text Se
Public bug reported:
I was confronted by the "System problem detected" dialog on logging in.
I didn't notice anything abnormal.
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: marco 1.24.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-18-generic x86_6
Here's a little video clip. I've logged out of telegram for privacy
reasons (and it doesn't minimise to the dock when logged out) but you
can see the effect just by opening the app.
** Attachment added: "shrinking_terminal.mp4"
https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1869475/+atta
1 - 100 of 5874 matches
Mail list logo
