This error went away on restart, so it's probably safe to close.
** Description changed:
After dist-upgrading from focal to jammy, postgis no longer works due to
- an undeclared dependency on glibc 3.4.29:
+ an undeclared dependency on glibc++ 3.4.29:
```
Apr 24 10:55:14 tiles2
Public bug reported:
After dist-upgrading from focal to jammy, postgis no longer works due to
an undeclared dependency on glibc 3.4.29:
```
Apr 24 10:55:14 tiles2 renderd[1761]:reason: Postgis Plugin: ERROR: could
not load library "/usr/lib/postgresql/12/lib/postgis-3.so":
As outlined in the [Test Case] for focal:
* Images have been built with these packages from the -proposed pocket and
published in the `ubuntu-os-cloud-image-proposed` project
* The images have gone through CPC's own CTF framework and testing has been
successful
* The images have been
As outlined in the [Test Case] for focal:
* Images have been built with these packages from the -proposed pocket and
published in the `ubuntu-os-cloud-image-proposed` project
* The images have gone through CPC's own CTF framework and testing has been
successful
* The images have been
Public bug reported:
error code in subprocess usr/bin/dpkg
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: gitweb 1:2.34.1-1ubuntu1.10
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
AptOrdering:
As outlined in the [Test Case] for mantic and jammy:
* Images have been built with these packages from the -proposed pocket and
published in the `ubuntu-os-cloud-image-proposed` project
* The images have gone through CPC's own CTF framework and testing has been
successful
* The images have
As outlined in the [Test Case] for mantic and jammy:
* Images have been built with these packages from the -proposed pocket and
published in the `ubuntu-os-cloud-image-proposed` project
* The images have gone through CPC's own CTF framework and testing has been
successful
* The images have
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2045708
Title:
[SRU] Improve debian/99-gce.rules to set schedulers based on disk
To manage notifications about this bug go to:
Daniel (@vanvugt) Thank you very much for your hard work, out-of-band
patch (the ppa!), and speed addressing this extremely subtle, yet
annoying bug... much appreciated!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also affects me, using Uname: Linux 6.5.0-26-generic x86_64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058411
Title:
Builds with gcc -fsanitize=address crashing on startup
To manage
Public bug reported:
issue arose while installing first updates after install of ubuntu 20.04
operating system
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libjurt-java 1:6.4.7-0ubuntu0.20.04.9
ProcVersionSignature: Ubuntu 5.15.0-101.111~20.04.1-generic 5.15.143
Uname: Linux
With the advent of 22.04.4, this issue seems to have been resolved.
Thanks again for looking into it, Sudip! =)
** Changed in: tpm2-tools (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello again, Sudip, hope this message finds you well!
I attempted to recreate the issue using a cert whose footprint exceeds
the 1,024 byte TPM data bus by using two tpm2_nvwrite commands (the
second of which specifying --offset=1024) and I'm happy to report that
it's working!
However, we were
Thanks for looking into this, Sudip! I will need to write up explicit
instructions, but the issue only shows up when you attempt to write to
an offset, which (I would presume) is why your test didn't produce any
issues. My usecase is storing a DER encoded x509 certificate whose
footprint exceeds
Many thanks for that feedback and guidance. In parallel with working on
the suggested changes, I wanted to understand the right approach we
should take to fixing this bug.
From your comment in #1 "It can't hurt to discuss with Debian but it's
highly doubtful they'll take our delta", would it be
Bump. Is anyone looking at this at all?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048945
Title:
scsi_eh_* process using idle CPU after upgrade to kernel 6.5
To manage notifications about this
Matthieu, more recently a more likely problem has been characterized by Alberto
Mardegan and found the line in question in
https://bugs.launchpad.net/snapd/+bug/1973321
In particular, restarting snapd doesn't help at all for me, so having
the directory mounted before snapd starts doesn't help,
I was going to request this change into Debian as well, but appears that
has already been attempted and was rejected due to "qtchooser is dead
upstream". https://salsa.debian.org/qt-kde-
team/qt/qtchooser/-/merge_requests/2
I wonder if the situation can be improved though as if you are trying to
Thanks Fabio. Adjusted tags accordingly.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Why would Ubuntu want to remove ZFS support? I use both Ubuntu and
Fedora but would have no reason to continue with Ubuntu without ZFS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966773
Title:
Thanks Alberto. I tried running "hello" in a different directory, and
you were correct:
arc@andrewfairfield:~$ hello
cannot open path of the current working directory: Permission denied
arc@andrewfairfield:~$ cd /
arc@andrewfairfield:/$ hello
Hello, world!
arc@andrewfairfield:/$
[ This is in
I (using Kerberos) don't the get apparmor DENIED messages that Eric (not
using Kerberos) did, but I get exactly the same "cannot open path of the
current working directory: Permission denied" error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Using NVFv4, kerberos authenticated, mounted by autofs:
arc@andrewshoreham:~$ hello
cannot open path of the current working directory: Permission denied
[ Then as user with sudo privs, sudo systemctl restart snapd ]
arc@andrewshoreham:~$ hello
cannot open path of the current working directory:
> The whole issue also raises the silly question: what is so security-
sensitive about /tmp?
Another, non-privileged, user can write to it, so could leave a trojan
(malware) in there ...
Ubuntu has /tmp/user/uid which I assume exists to work around that issue,
but chromium wont let me see
I encountered this last week installing Ubuntu 22.04. I booted from USB
install media and installed to a second attached USB storage device. I
created an EFI system partition on the install target device, and
specifically selected this EFI system partition in the GUI as the place
to install the
I got exactly the same errors as Miles above; a simple permission denied
error stopping things before AppArmor got involved.
I.e., the answer to Markus Kuhn's question is no, in fact even in
enforce mode there are no denied apparmor complaints.
I don't know whether this is because the gating
Firefox also doesn't work now it is a snap in 22.04.
I think there are still multiple issues here. The original poster seems
to be using NVSv3 I believe based on the RPC errors (NFSv3 uses multiple
ports, one of which is called something like RPC, but I am not an expert
in this as I have only
; continue
We have observed this with Bionic, I haven't checked any other Ubuntu
releases.
Cheers,
Andrew
** Affects: cron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
I am pretty sure this is at least partly a problem with snaps not
working with Kerberos, which is the authentication mechanism for NFS.
The Kerberos credentials are (with good reason) not stored in the home
directory.
I described this in more detail in bug 1784774.
This means that firefox and
I did some more investigating, and I think there are two independent problems
here:
(1) The problem as believed so far, network access permissions
(2) New insight: Kerberos doesn't work with snaps.
This explains why fixing (1) didn't help me (or Adam).
Background: Kerberos is the authentication
ah whoops-please undo
** Changed in: snapd (Ubuntu)
Status: Fix Committed => 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/1969162
Title:
bad interaction between snapd and
This still doesn't work with 22.04, which is a problem for firefox,
which is now installed as a snap. This seems somewhat strange as firefox
obviously needs network access, so it is not just the network access
that causes problems.
Running firefox from the command line produces an error
I never got it to work in 20.04, so I don't know whether your fix ever
made it in.
I have just installed Jammy Jellyfish (22.04), and can confirm snaps
don't work in it when using autofs and nfs mounted home directories.
The prior work around was just never use any snap applications, which
was
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956243
Title:
Ping give socket error initially if IPv6 is disabled
To manage notifications about this bug go to:
I got it working, and confirmed the bug, only problem is it will get
overwritten with the next patch, and others cant use the fix.
Hopefully this is a quick fix for a proc dev.
This is how i did it
When you try to compile the drivers you get
./r8152-2.15.0/r8152.c:18530:25: error:
with
netlink error: Operation not supported
I tried to build the driver, but it fails to build on ubuntu 22.04, but builds
fine on older released ( in know not much help)
/home/andrew/r8152-2.15.0/r8152.c:18530:25: note: (near initialization for
‘ops.get_coalesce’)
/home/andrew/r8152-2.15.0/r8152.c:18531
** Changed in: kunpeng920/ubuntu-22.04
Status: Fix Committed => Fix Released
** Changed in: kunpeng920
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Any update?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967924
Title:
One overlayfs fix has not been backported to the 5.13 branch
To manage notifications about this bug go to:
Public bug reported:
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
UBUNTU: SAUCE: overlayfs: fix incorrect
** Also affects: linux-azure (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/1857257
Title:
linux-image-5.0.0-35-generic breaks checkpointing of
Public bug reported:
```
GNU Image Manipulation Program version 2.10.18
git-describe: GIMP_2_10_16-38-gde7f04567d
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
As 0.8.0-2ubuntu2 has fixed the build issue, marking this bug as "Fix Released".
Please feel free to revert if the issue is persisting.
** Changed in: capnproto (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: ubuntu-power-systems
Status: New => Fix Released
--
You
This was fixed two years ago for BleachBit 4.0.0
https://github.com/bleachbit/bleachbit/issues/819
The latest BleachBit 4.4.0 is here https://www.bleachbit.org/
Ubuntu has a "no rolling release" policy, so the version in the Ubuntu
repository may be rather old.
** Bug watch added:
I've fixed this in https://github.com/canonical/cloud-
init/pull/1340/files (sadly blocked on getting the CLA signed)
I'm interested that you've hit this too @tony-casanova-nc-33-2017.
FWIW, I'm using:
- cloud-init 22.1
- I'm on a Microsoft OS called 'Mariner'
- I'm on VMware vSphere V7 -> I've
I've also hit this (on VMware), and while I suspect that may be due to
some particular funnies of the OS I am on, I agree a defensive fix in
cloud-init to not raise an Exception if you can't write to /dev/console
and fall back to writing to stdout would be welcomed.
Any objections if I raise a PR
Running 5.13.0-xx on Parallels Desktop on M1 Macbook. 5.13.0-12-generic
is the last kernel that will boot. -13 and -14 have been withdrawn,
apparently. -15 and -16 just hang as soon as control is given to the
kernel back from the EFI loader. Some fail code was backported post -12
from more recent
@alexmurray, hey, I believe that commit was reverted later as it caused
a behavioural regression? The Github advisory
(https://github.com/flatpak/flatpak/security/advisories/GHSA-8ch7-5j3h-g4fx)
was changed to point to a different commit
Public bug reported:
I'm on a Raspberry Pi 4 Cannakit build. I have had some troubles with a
lot of various packages. I'm not sure if there's a way around this. I
thought I read somewhere you have to use curl for everything, but I had
trouble with that too. I'll keep playing around with it and
Marking as "incomplete" while waiting for input from Power MMU experts.
** Changed in: ubuntu-power-systems
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: kunpeng920/ubuntu-21.10
Status: Fix Committed => 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/1933301
Title:
[uacc-0623] hisi_sec2 fail to alloc uacce
To
** Changed in: kunpeng920
Importance: Undecided => Low
** Changed in: kunpeng920
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951289
Title:
https://github.com/OSGeo/gdal/issues/5324 is a result of this and the
upstream https://github.com/libexpat/libexpat/issues/501
** Bug watch added: github.com/OSGeo/gdal/issues #5324
https://github.com/OSGeo/gdal/issues/5324
--
You received this bug notification because you are a member of
** Bug watch added: github.com/libexpat/libexpat/issues #501
https://github.com/libexpat/libexpat/issues/501
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956202
Title:
`libexpat1-dev` CMake
** Also affects: expat via
https://github.com/libexpat/libexpat/issues/501
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/1956202
Title:
It says above fix released in August, however I still have the bad
wording and it has caught me out today. I'm running Ubuntu 20.04.03
gnome 3.36.8. Why has the fix not reached me yet please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: kunpeng920/ubuntu-18.04
Status: Fix Committed => Fix Released
** Changed in: kunpeng920
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Having a similar issue on my ASUS Zenbook UX434, also using the ALC294
as above, Kernel: 5.13.0-28-generic.
In my case after a reboot from my Windows 10 dual boot the audio out is
fine, but the microphone has very loud crackling which makes it
unusable. The problem isn't fixed by a reboot but
Public bug reported:
There's a known issue in nvme-cli where the compiler optimizes out BAR
accesses into a single 64B read rather than 2 32-bits. This causes some
devices to hang and reboot the system. This bug was fixed in version
v1.14. The ubuntu supported version should be >= v1.14.
**
Public bug reported:
it doesn't report any error message, the printer doesnt just print
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups 2.3.1-9ubuntu1.1
ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-43-generic x86_64
ApportVersion:
Public bug reported:
when viewing pixie02.jpg image crashes the image viewer
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: eog 3.36.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Public bug reported:
when attempting to play the vp8.webm file causes the Videos file to
crash
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libgstreamer1.0-0 1.16.2-2
ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
ApportVersion:
Please find attached the debdiff for Ubuntu 21.10 impish. I have
performed some testing in a VM and built in a PPA.
** Attachment added: "Impish CVE debdiff"
https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1957716/+attachment/5557881/+files/flatpak_impish_lp1957716.debdiff.gz
--
You
** Changed in: flatpak (Ubuntu Impish)
Status: New => In Progress
** Changed in: flatpak (Ubuntu Impish)
Assignee: (unassigned) => Andrew Hayzen (ahayzen)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I've trying the following commands (passwords are fake) to convert lets
encrypt certs for tp-link omada.
openssl pkcs12 -export -in fullchain.pem -inkey privkey.pem -name eap -out
keystore.p12 -password pass:myeapc
keytool -storetype jks -importkeystore -destkeypass tplink
** Description changed:
[Links]
https://github.com/flatpak/flatpak/security/advisories/GHSA-qpjc-vq3c-572j (
CVE-2021-43860 )
https://security-tracker.debian.org/tracker/CVE-2021-43860
https://github.com/flatpak/flatpak/security/advisories/GHSA-8ch7-5j3h-g4fx (
CVE-2022-21682 )
** Description changed:
[Links]
https://github.com/flatpak/flatpak/security/advisories/GHSA-qpjc-vq3c-572j (
CVE-2021-43860 )
https://security-tracker.debian.org/tracker/CVE-2021-43860
https://github.com/flatpak/flatpak/security/advisories/GHSA-8ch7-5j3h-g4fx (
CVE-2022-21682 )
Note that Jammy now has 1.12.3-1 so is fixed.
** Summary changed:
- Update for CVE-2021-43860 and second github advisory
+ Update for CVE-2021-43860 and CVE-2022-21682
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-21682
** Description changed:
[Links]
-
Should be updated in sync with
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1957996
to either 0.103.5 or 0.104.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798089
Title:
libclamunrar
libclamunrar should ideally be updated in sync with this, see
https://bugs.launchpad.net/ubuntu/+source/libclamunrar/+bug/1798089
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957996
Title:
** 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/bugs/1957996
Title:
CVE-2022-20698 ClamAV update
To manage notifications about this
** Changed in: flatpak (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957716
Title:
Update for CVE-2021-43860 and second github advisory
To manage
Can someone with permission add impish, focal, bionic as affected
series? (hirsute i assume we can skip as it's about to EOL).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957716
Title:
Update
ntu)
Importance: Undecided
Assignee: Andrew Hayzen (ahayzen)
Status: In Progress
** Information type changed from Public to Public Security
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-43860
** Changed in: flatpak (Ubuntu)
Assignee: (unassigned) =>
Here is a demonstration as requested in Discourse. These steps were run
on a stock image of Ubuntu Impish taken from https://cloud-
images.ubuntu.com/impish/current/.
Showing the inconsistent behavior of the default settings if the goal is
private home directories. Both adduser and useradd
I have a keyboard a4tech KV-300h and the bug reproduce on windows too. I have
already tried to replace to another a new keyboard. The problem isn't gone.
I found out if I use embedded USB port of keyboard to connect a mouse then the
problem reproduce very often.
Also I tested my keyboard on
Same issues here on Kubuntu 21.10 after upgrade to 5.13.0-23-generic:
amdgpu: failed to write reg wait reg
AMD Ryzen 7 3700U w/ Radeon Vega 10 Mobile graphics
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
With IpV6 enabled everything works well. However if you disable ipv6 by editing
/etc/default/grub with the following entry
GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1"
then when you ping there is an initial socket error
ping localhost
ping: socket: Address family not
if you need the fix for now, I temp added Hirsute to sources.list and
issued, sudo apt-get --only-upgrade true install graphite-carbon, of
course removing the hirsute repo's after. I will report everything
remained stable and has worked properly since. If you would like I can
post an exact guide
Public bug reported:
Since the appdata changes in the recent upload, steam-installer doesn't
appear in the software stores.
Lets revert back to our downstream changes for now as this was an
experiment.
** Affects: steam (Ubuntu)
Importance: Undecided
Assignee: Andrew Hayzen (ahayzen
** Summary changed:
- Merge steam 1.0.0.73-1 from debian sid to ubuntu jammy
+ Merge steam 1.0.0.74-1 from debian sid to ubuntu jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951894
Title:
I've done some exploratory testing of Wayland/portal related tests from
the test plan on a Impish VM and things are working normally.
$ apt policy flatpak
flatpak:
Installed: 1.10.2-3ubuntu0.1
Candidate: 1.10.2-3ubuntu0.1
Version table:
*** 1.10.2-3ubuntu0.1 500
500
I've done some exploratory testing of Wayland/portal related tests from
the test plan on a Hirsute VM and things are working normally.
$ apt policy flatpak
flatpak:
Installed: 1.10.2-1ubuntu1.1
Candidate: 1.10.2-1ubuntu1.1
Version table:
*** 1.10.2-1ubuntu1.1 500
500
I've done some exploratory testing of Wayland/portal related tests from
the test plan on a Bionic VM and things are working normally.
$ apt policy flatpak
flatpak:
Installed: 1.0.9-0ubuntu0.4
Candidate: 1.0.9-0ubuntu0.4
Version table:
*** 1.0.9-0ubuntu0.4 500
500
I've done some exploratory testing of Wayland/portal related tests from
the test plan on a Focal VM and things are working normally.
$ apt policy flatpak
flatpak:
Installed: 1.6.5-0ubuntu0.4
Candidate: 1.6.5-0ubuntu0.4
Version table:
*** 1.6.5-0ubuntu0.4 500
500
Sorry, I somehow missed comment 11 and was thinking we were still
waiting for the libseccomp decision. I'll check the packages now!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946578
Title:
Happened again, with associated stuff making it into syslog. File
crashlog2 attached.
** Attachment added: "crashlog2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951696/+attachment/5546513/+files/crashlog2
--
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- Merge steam 1.0.0.72-2 from debian sid to ubuntu jammy
+ Merge steam 1.0.0.73-1 from debian sid to ubuntu jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951894
Title:
** Changed in: ceph (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
(unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953339
Title:
Failure to
Public bug reported:
Mouse receives power via USB when plugged in, immediately loses it.
Mouse on other devices, USB port provides power to other mice.
Manufacturer: Microsoft
Model: Microsoft Ergonomic Mouse (Wired)
Connection: USB
Mechanism: Optical
Buttons: 4 Buttons + 1 Scrollwheel
I am currently working around this bug also.
The suggested workaround to generate a local repository of the packages
that are built in ~/pbuilder/dist_result is a good one, but it is
fragile because we are forced to assume the location of
~/pbuilder/dist_result when writing our ~/.pbuilderrc and
Adding to my previous comment, I can also see that the documentation is
wrong.
The page https://wiki.ubuntu.com/PbuilderHowto#Differences_with_pbuilder
says that:
[QUOTE]
pbuilder-dist does apparently not yet support all kinds of operations. The
following doesn't work correctly for example:
This bug still exists in focal 20.04. It should not have been closed.
When using pbuilder-dist the value of OTHERMIRROR is ignored, as is the
value of --othermirror passed as argument to pbuilder-dist.
To work around this I need to manually add a mirror to
/etc/apt/sources.list from within a
** Information type changed from Private to Public
** No longer affects: ubuntu-power-systems
** Changed in: kernel-package (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
(unassigned)
--
You received this bug notification because you are a member of
** Changed in: gcc-defaults (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-power-systems
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930086
** Also affects: ubuntu-power-systems
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/1952185
Title:
Embedded ARM64 crash trying to zero-fill an 8GB
Public bug reported:
This is an issue in the lubuntu-artwork 21.10.1 package in Ubuntu 21.10.
The source package is lubuntu-artwork.
The lubuntu-default-wallpaper.png wallpaper has transparent pixels in
its last column. When the image is used as a desktop wallpaper, the
transparent pixels appear
Public bug reported:
Debian has a newer version of steam packaging available, let's merge the
changes into the Ubuntu version to bring us back into sync.
** Affects: steam (Ubuntu)
Importance: Undecided
Assignee: Andrew Hayzen (ahayzen)
Status: In Progress
** Changed
Public bug reported:
I started getting kernel general protection faults after upgrading to
kubuntu 21.10, from 21.04.
Has happened five times since then. Each time the crash happened when
closing a Google Chrome window. Each time, the Chrome window was left
partially transparent - the crash
The issue seems to be resolved now with Linux 5.10.0-1051-oem. It helped
following https://bbs.archlinux.org/viewtopic.php?id=270392 and setting
the rt715 ADC 24 Mux selector in alsamixer to DMIC3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hi,
After the latest Ubuntu updates I am no longer experiencing this issue
(possibly nvidia related?)
Thanks for your support.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949909
Title:
1 - 100 of 23309 matches
Mail list logo
