Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You
Public bug reported:
** Affects: wireplumber (Ubuntu)
Importance: Undecided
Assignee: Sebastien Bacher (seb128)
Status: Incomplete
** Tags: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(In reply to Worcester12345 from comment #152)
> Michael Baffoni, is this REALLY "working for you"?
Not working for me, since about one week:
- problem with message in MIME multipart, with invitation in .ICS
- I see a header saying "this message contains an invitation", I can accept it
or not,
Thanks Hans - I had done what you suggested several times before
reporting the bug. But I tried again today and found the error did not
recur. kdeconnect installed without a problem. It's conceivable that
there was an issue with the availability of that package in the
repositories before, but the
Accepted both focal and impish, but I don't see anyone sponsoring the
hirsute version - could we get that uploaded as well? I know it's not
the latest series, but hirsute will still be supported for a while and
we shouldn't forget about users of 21.04, at least not yet. Not everyone
upgraded yet.
Hello Yuan-Chen, or anyone else affected,
Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.9-0ubuntu0.20.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Yuan-Chen, or anyone else affected,
Accepted mutter into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/40.5-1ubuntu3~21.10.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
SRU Justification
[Impact]
Microsoft has asked to enable arm64 in Azure 5.11 and subsequent
kernels.
+
+ [Test Case]
+
+ Microsoft tested.
[Where things could go wrong]
Some of the patches touch common PCI code. Device detection could be
Public bug reported:
I received a message today about Ubuntu 21.10 having been released and I
upgraded even though I was already using that version.
A large number of packages were installed and a lesser number removed.
The computer then was rebooted and seemed normal except for web pages on
** Changed in: ubuntu-dev-tools (Ubuntu Focal)
Status: In Progress => 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/1947192
Title:
[BPO] version 0.185
To manage notifications
The attachment "lbzip2.patch" seems to be a patch. If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray,
Public bug reported:
On an AMD 5700G system, NTP does NOT synchronize :
hercules@pjamdz3a:~$ timedatectl
Local time: Thu 2021-11-04 12:57:24 CET
Universal time: Thu 2021-11-04 11:57:24 UTC
RTC time: Thu 2021-11-04 11:57:44
Time zone:
vmware-gos-Yuhua : what is the corresponding ovf template entry for
Connected At Power On? We generate all builds in a chroot, with a
templated OVF, so we need to identify the exact stanza. What we have now
is:
https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu-
Similar problem occurred during upgrade to linux-firmware (1.187.20);
initial install failed, but was able to successfully install after a
reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945845
** Changed in: gnome-shell-extension-dashtodock (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: New => Triaged
** Changed in:
Hi, this seems to have something to do with `debian/compat` file. There
are warnings during building about version 9 being deprecated, so I
changed it to `10` and applied the attached patch to `debian/rules` and
have a working package. I know nothing about debian packaging so this
may be the wrong
Hello OEM, or anyone else affected,
Accepted oem-somerville-maester-meta into focal-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/oem-somerville-maester-
meta/20.04~ubuntu1 in a few hours, and then in the -proposed repository.
Please help us by
This bug is awaiting verification that the linux-iot/5.4.0-1000.2 kernel
in -proposed solves the problem. Please test the kernel and update this
bug with the results. If the problem is solved, change the tag
'verification-needed-focal' to 'verification-done-focal'. If the problem
still exists,
Current workaround would be to kill plank and restart it - something
like
killall plank; sleep 2; nohup plank &
That could be connected to a manually created keyboard shortcut.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The bug was encountered over at RedHat and someone apparently came up
with a workaround : https://bugzilla.redhat.com/show_bug.cgi?id=1962035
** Bug watch added: Red Hat Bugzilla #1962035
https://bugzilla.redhat.com/show_bug.cgi?id=1962035
--
You received this bug notification because you
I also have the same issue here. Additional information I can offer is
that I already has a weird situation when upgrading to 21.04, something
of the usrmerge went wrong and I ended up not having a working ld. Not
sure this is related, anyway.
Here's the output of running dpkg:
(Reading database
** Changed in: timidity (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946767
Title:
Build fails on riscv64
To manage notifications about this bug go to:
** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)
** Changed in: linux-azure (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux-azure (Ubuntu)
Assignee: (unassigned) => Tim Gardner
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1949770
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
SRU Justification
[Impact]
Microsoft has asked to enable arm64 in Azure 5.11 and subsequent
kernels.
[Where things could go wrong]
Some of the patches touch common PCI code. Device detection could be
impacted.
[Other Info]
SF: #00310705
** Affects: linux-azure (Ubuntu)
** Changed in: charm-rabbitmq-server
Importance: Undecided => Medium
** Changed in: charm-rabbitmq-server
Status: New => Triaged
** Changed in: charm-rabbitmq-server
Milestone: None => 22.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hey Andy! So I'm less concerned about the additional devices included as
part of the SRU, but more about the additional changes that are pulled
in. Since there's also a lot of patches that are unrelated to the actual
ID additions. My worry is that we don't have a good test case and
regression
+ it is merged master long time ago, this is really proper fix and
should be included in ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814890
Title:
Unit tests are not passing under
While clearing old bugs I found this one and priority for Xenila/Zesty
backports never was important to anyone. Nowadays those are on ESM
support and since there is a workaround (rule overrides) and this isn't
a security issue I'll set Won't Fix for those.
** Changed in: libvirt (Ubuntu Xenial)
Hi,
I'm trying to clean up old bugs right now.
On this particular case there never was an actionable level of debug/info or a
chance to recreate.
Furthermore I have not seen "similar" issues come in since then so we really
would need to understand better what config/setup made this trigger the
Due to the fallback code present and working neither IBM (for ppc64) nor
anyone else found the time/need to work on this. While clearing old
cases let us reflect that properly by marking it as incomplete.
** Changed in: libvirt (Ubuntu)
Status: New => Incomplete
** Changed in: libvirt
** Bug watch added: Debian Bug tracker #902769
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902769
** Also affects: timidity (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902769
Importance: Unknown
Status: Unknown
--
You received this bug notification
Thank you for the patch. LGTM.
In the future please remember to run `update-maintainer` if the package carries
an Ubuntu delta.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946767
Title:
Build
While it is sad that no one found the time to prepare an upload for this
fix while clearing old bugs I have to state that Trusty is (for a while
already) in ESM support and this isn't a security issue. Therefore to
reflect the most correct state I sadly have to set this to Won't Fix :-/
**
** Changed in: libvirt (Ubuntu Eoan)
Status: New => Won't Fix
** Changed in: libvirt (Ubuntu Bionic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859016
FYI - this is still being worked on by Ioanna (thanks) and a v2 patch
set is up for review at the upstream mailing list.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927519
Title:
Mitigate
** Changed in: juju
Milestone: 2.9.18 => 2.9.19
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944080
Title:
[fan-network] Race-condition between "apt update" and dhcp request
causes
While sadly nothing changed, Trusty is nowadays out of non-ESM support
and while a shame to not have been updated it isn't a security issue, so
I'm marking it as Won't Fix to better reflect reality.
@Rbasak, if there is anything other than "didn't find the time" we can
learn from this to avoid
Hi,
I'm trying to clear a few old bugs, nothing similar has come up over the recent
years that would have made this more debuggable/reproducible :-/ Nor was there
further feedback/discussion here, therefore I'll set it to incomplete as I
can't see how to further act on this case without more
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949640
Title:
Hirsute update: upstream stable patchset 2021-11-03
Public bug reported:
NetworkManager keyfiles allows to specify "scope: link" routes, by
leaving the gateway/next_hop field unspecified, e.g.:
route3=2.2.2.2/7
route4=3.3.3.3/6,0.0.0.0,4
route3=4:5:6:7:8:9:0:1/63,::,5
To keep compatibility, netplan needs to be able to accept "scope: link"
Public bug reported:
Since a while I have an issue with gwenview.
After opening and modifying a jpeg file, and the press the save button
shows an Error message.
"Gwenview cannot save images in 'jfif' format."
If I try to use "Save As" and try to save as jpeg I get 2 error dialogs:
1.
Given this really breaks cross-arch toolchains of all sorts I'm even
bumping this to critical.
** Changed in: qemu (Ubuntu)
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: oem-priority
Assignee: OEM Taipei Jenkins Role Account (oem-taipei-bot) => Yuan-Chen
Cheng (ycheng-twn)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936266
Title:
[MIR]
** Description changed:
[Background]
Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.
[Impact]
1. Upgrade path: Users will be upgrading from a package in the associated
OEM archive, not the Ubuntu
Please use one of the plymouth.debug kernel parameters to record a
plymouth log of the problem happening and then attach the log here.
See
https://gitlab.freedesktop.org/plymouth/plymouth/-/raw/main/docs/development.txt
** Changed in: plymouth (Ubuntu)
Status: New => Incomplete
**
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: plank (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949741
Title:
Can confirm.
This is most probably because the current plank package contains this
extra patch added by Debian - dropping this patch should resolve this.
https://github.com/ricotz/plank/pull/6
** Also affects: plank (Ubuntu)
Importance: Undecided
Status: New
** No longer affects:
B-KVM 4.15.0-1102.104
** Tags added: sru-20211018
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845919
Title:
memcg_failcnt in mm from ubuntu_ltp failed on B 4.15
To manage notifications about
Haha. No problem, the package won't be moved to updates before November
10th anyway (7 days should pass).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947553
Title:
wrong panel size 21.10
To
Sure, I put that custom core18 snap into
https://people.ubuntu.com/~slyon/uc18/ as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949089
Title:
systemd randomly fails to activate mount units
Public bug reported:
installed libnss-resolve that put "resolve" in nsswitch.conf.
$ lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:20.04
$ dpkg -l systemd | grep systemd
ii systemd245.4-4ubuntu3.13 amd64system and service manager
$ grep ^hosts
Public bug reported:
I installed Ubuntu 20.04 and the sound is not working on the fresh install.
The microphone either.
I have 5 computers with same hardware. Same problem everywhere.
I guess there is a missing driver.
Here is lspci output:
00:00.0 Host bridge: Intel Corporation Device 9a14
I started kernel bisecting in an attempt to find the commit that causes this
issue.
Painfull process.
I found another workaround (not a solution) on stackoverflow (which has
been deleted from stackoverflow by now). The workaround was to disable
virtualization in the BIOS: Intel VTX -> disabled ,
When the bug occurs, doing rmmod i2c_hid then modprobe i2c_hid fixes the
things temporarily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945444
Title:
Touchpad high CPU consumption and random
See https://askubuntu.com/a/1163018/300665
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949304
Title:
package bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 failed to
install/upgrade:
[Where problems could occur] is updated
** Description changed:
[Impact]
The modem certification requires that different modem firmware is used for
different network carrier.
This needs the firmware upgrading capability during the modem certification
process.
The modem
Please note the libmbim 1.24 branch is not actively maintained any more
in upstream. If you want to keep on using that release, you're fully on
your own.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** Bug 1736804 has been marked as a duplicate of 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/1065126
Title:
"Always do this from now on" does not work
To manage notifications
(In reply to Anje from comment #203)
> there are going to be an increase in Thunderbird users
I can't comment on Thunderbird, and recommend you contact the
Thunderbird devs through non-bugzilla channels (matrix or email is
probably best). I believe that bug 1690395 was reopened and tracks the
TB
(In reply to :Gijs (he/him) from comment #201)
> We are actively working on a fix, but as several comments here have already
> pointed out, it isn't trivial and will come with some side-effects to 20-odd
> year old ways that Firefox has done downloads. The root cause of this issue
> is outlined
I do have a Geoclue2 geolocation provider for gecko-dev right now and
have been using it in Firefox for a few weeks now.
This provider is purely (G)D-Bus based, so it doesn't need any additional
external library as a dependency.
I envision it as a system-wide geolocation source, much like the
Thanks a lot, Christian, for the verification and all the previous help
on this!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505670
Title:
python exceptions bleeding into stdout
To manage
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/411320
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/411321
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
+
+ [Impact]
+
+ * The kernel changed handling of binfmt-P and that breaks qemu
+using binfmt registering TCG based emulators to run foreign
+architecture code.
+
+ * This happened late 5.11.0-20 -> 5.13.0-20 and even as of today
+cloud-images start with
Right, cockpit-machines only shows libvirt machines. So if `virsh list`
is empty, so will be c-machines.
** Changed in: cockpit-machines (Ubuntu)
Status: Incomplete => Won't Fix
** Summary changed:
- does not show any VMs
+ does not show VMWare VMs
--
You received this bug notification
I have site down and eventually together with paride was able to create
a bit of a timeline and a fix.
I have - at first - wondered as I could reproduce it in Jammy, but not in Impish
I had qemu 1:6.0+dfsg-2expubuntu1 in both, why would they behave different.
And then I found that my Impish
bot asked to select a package and nautilus was the closest I could think
of for the issue... I might be wrong...
** Package changed: ubuntu => nautilus (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[Impact]
Four years ago I got a backports approval for the "cockpit" source
package in bug #1686022. A while ago, the "Machines" page was split out
into its own separate https://github.com/cockpit-project/cockpit-
machines/ project, mostly to make development easier and
Uploaded to https://launchpad.net/ubuntu/impish/+queue?queue_state=1 and
https://launchpad.net/ubuntu/focal/+queue?queue_state=1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949715
Title:
[BPO]
As a workaround you can execute the "netplan try" command as:
netplan try --state /etc/netplan
This will mitigate the problem for the time being.
** Tags added: regression-update
** Also affects: netplan.io (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: netplan.io
Hello!
Thank you!
Unfortunately my work desktop is out of my reach for next several days, so I
will be able to do test only at Monday :-(
Minin and Pozharsky and, definitely, Poland's intervention are still delaying
us ;-)
--
You received this bug notification because you are a member of
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
Hirsute
Check after cacher is down in the host
+;enp8s0;IPv4;apt-cacher-ng\032proxy\032on\032Keschdeichel;_apt_proxy._tcp;local
+;enp7s0;IPv4;apt-cacher-ng\032proxy\032on\032Keschdeichel;_apt_proxy._tcp;local
+;enp1s0;IPv4;apt-cacher-ng\032proxy\032on\032Keschdeichel;_apt_proxy._tcp;local
Focal
Check after cacher is down in the host
+;enp8s0;IPv4;apt-cacher-ng\032proxy\032on\032Keschdeichel;_apt_proxy._tcp;local
+;enp7s0;IPv4;apt-cacher-ng\032proxy\032on\032Keschdeichel;_apt_proxy._tcp;local
+;enp1s0;IPv4;apt-cacher-ng\032proxy\032on\032Keschdeichel;_apt_proxy._tcp;local
Bionic
Check after cacher is down in the host
+;enp8s0;IPv4;apt-cacher-ng\032proxy\032on\032Keschdeichel;_apt_proxy._tcp;local
=;enp8s0;IPv4;apt-cacher-ng\032proxy\032on\032Keschdeichel;_apt_proxy._tcp;local;Keschdeichel.local;192.168.122.1;3142;
ubuntu@b-deb-proxy:~$ curl 192.168.122.1:3142
Public bug reported:
Steps to reporduce:
1) Open a browser (e.g. Chrome)
2) Open any other application and make sure it's in the foreground.
3) Open a terminal and run: xdg-open "https://google.com;
Expected:
Your browser should be brought to foreground with the Google website open
Actual:
Your
** Changed in: iptables-persistent (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949643
Title:
iptables-persistent unconditionally drops existing iptables
** Changed in: linux-raspi (Ubuntu Impish)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949370
Title:
Missing modules in linux-modules
To manage notifications
Hi jchittum,
"Serial Port 1" is added with ubuntu-21.10-server-cloudimg-amd64.ova
The default configuration about "Serial Port 1" is
Serial Port 1: Use physical serial port
Status: Connected at PowerOn
But with the default configuration I get warning message as follows when power
on the
Just adding a note to mention the same thing happens on 2 others Dell Latitude
7490.
No possibility to use anything above Kernel: 5.8.0-43-generic as machine
freezes with higher kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: iptables (Ubuntu Impish)
Importance: Undecided => Medium
** Changed in: iptables (Ubuntu Jammy)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please
1. run apport-collect 1949654
2. report to https://github.com/OpenPrinting/system-config-printer/issues and
share a link here.
** Also affects: system-config-printer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Public bug reported:
nothing
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.20
ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USER
It looks like OpenStack's upper-constraints has now updated to > 2 [1]
1:
https://github.com/openstack/requirements/blob/2c681dd1c8a9a7e89d4b80b946a9e2e8c1280b03/upper-
constraints.txt#L561
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: originate-from-1943787
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949026
Title:
System hangs on purple screen
To manage notifications about this bug go to:
MR ready and uploaded.
Due to the ppc64 test backlog that might still take a while.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946901
Title:
Merge spice from Debian unstable for 22.04
To
tagged as a sync and synced after review with Miriam.
Currently in migration:
pyjwt | 1.7.1-2ubuntu2 | jammy | source
pyjwt | 2.1.0-1 | jammy-proposed | source
** Tags added: needs-sync
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I encountered something very similar to this issue (maybe even this
issue?) when my docker containers could not start (using snap on Ubuntu
20.04.3 LTS under VirtualBox with a Windows 10 host). Similar to others,
`sudo apt install libblockdev-mdraid2` seems to have fixed it.
In case these log
Still happens after yesterday's update of linux-firmware to 1.201.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948563
Title:
amdgpu errors, desktop freezes
To manage notifications about this
It's probably the choice of graphics mode that's making pixels non-
square, and probably is not specific to the vendor logo(?)
Can you provide output from 'lspci -kv' ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
As Ubuntu boots up, the vendor logo will be retrieved and displayed on
the monitor.
Per test, as internal and external monitors have different Wide/Hight
ratios, Plymouth will use the monitor ratio of the internal monitor, and
the vendor logo will be displayed on both
thunderbird 1:91.2.1+build1-0ubuntu0.21.10.1 is now available in impish
(updates and security pockets)
** Changed in: thunderbird (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
201 - 293 of 293 matches
Mail list logo
