So could this release to updates now then?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/2083020
Title:
Backport packages for 24.04.2 HWE stack
Status in OEM Priority Pro
To me it looks like the crash is in glib.
** Information type changed from Private to Public
** Package changed: fwupd (Ubuntu) => glib2.0 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://b
> Now the problem is I can't reproduce this so far. gnome-shell/xwayland
randomly exits at some point without any explanation (you can see it
just starts broken pipe at 12:31:54, no crash before, I need to find the
cause for that and report another bug :(
Maybe this:
https://gitlab.gnome.org/GNOM
> Attaching the Journal, the initial crash can be seen at 12:31:54, lots
going on there, but nothing root-causing this.
[ 3300.659129] WARNING: CPU: 1 PID: 65823 at
drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:315
dal_gpio_service_open+0x1b6/0x270 [amdgpu]
This is the assertion yo
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2083538
Title:
amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 p
> but the GPU restarts are failing and the driver apparently deadlocks
or something (quite a bunch of mutex backtraces).
Yes; poor clean up/recovery should be tracked as a separate bug report
at https://gitlab.freedesktop.org/drm/amd/-/issues
--
You received this bug notification because you are
Possibly the same issue as fixed in mesa 24.1
https://gitlab.freedesktop.org/mesa/mesa/-/issues/11138
Please uprev mesa in the snap and see if it helps.
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #11138
https://gitlab.freedesktop.org/mesa/mesa/-/issues/11138
--
You receiv
Can you check that? Was this maybe when the snap refreshed silently in
background? Or try a version without snap so you could use the host
mesa?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.laun
This is most likely a mesa issue. Have you upgraded mesa recently to
match when it showed up?
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in
Thanks for checking. I believe what's going on is that it resets the
topology, but the policy to re-authorize it doesn't happen because bolt
is missing until the rootfs is loaded. So initramfs needs a hook to
include bolt.
--
You received this bug notification because you are a member of Ubuntu
Thanks for confirming it. You can also try to add thunderbolt to
/etc/initramfs-tools/modules to see if that's enough to fix the issue
instead of the kernel command line workaround.
I suspect it's not though, and that a hook will be needed to add:
* /lib/udev/rules/90-bolt.rules
* bolt.service
*
Try adding thunderbolt.host_reset=0 to your kernel command line.
Suspect it's the changes that came in
https://launchpad.net/ubuntu/+source/linux/6.8.0-38.38:
- thunderbolt: Introduce tb_port_reset()
- thunderbolt: Introduce tb_path_deactivate_hop()
- thunderbolt: Make tb_switch_reset(
Perhaps a dumb question - but why even bother to put any of the GPU
binaries in the initramfs? There should be a good enough display from
the pre-boot framebuffer that none of them should be needed with
simpledrm.
Punt i915.ko, xe.ko, amdgpu.ko, nvidia.ko out of the initramfs and let
them get loa
> No longer in progress. You can get to 100% fixed by adding kernel
parameter 'plymouth.use-simpledrm' but I'm not totally sure that's
something everyone will want.
The main reasons that can be problematic are rotation right? I wonder
if the right way to go about it is a heuristic within plymouth
Public bug reported:
When resizing a VMWare Workstation, under Ubuntu20 the resolution would
change automaticaly. It does not in the Ubuntu 24 Beta. During
installation I have enabled download of third party driver.
I can see vmtoold running.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package
According to the upstream bug, this appears to be a new intended
behavior with newer gnupg2:
https://dev.gnupg.org/T6871
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/206
I managed to get it working as a user by manually starting pcscd.service
and with the following to force scdaemon to use it.
# cat ~/.gnupg/scdaemon.conf
card-timeout 5
disable-ccid
To me this seems to be a regression in behavior from 2.2.27-3ubuntu2.1
to 2.4.4-2ubuntu17.
** Bug watch added:
g
Public bug reported:
In Ubuntu 22.04 I used by GPG key stored on a Yubikey smart card, but
since upgrading to Noble I get the following trying to access it.
$ gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
If I run this as root it wo
Can you double check the framebuffer FB related conf options in your
kconfig against those in Fedora?
--
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/1970069
Title:
Annoyin
The backend is a framebuffer driver. For example efifb which uses the
framebuffer set up by GOP in pre-boot.
If there are framebuffer drivers in tinydrm then maybe they matter for
those architectures.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
untu 22.04-LTS to fix many more bugs, but
apparently that is too late now, according to
https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/709476
Thanks,
-mario
** Affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Tags: gstreamer pipewire pulseaudio so
n great to get Pulseaudio upgraded to
version 17 for upcoming Ubuntu 22.04-LTS to fix many more bugs, but
apparently that is too late now, according to
https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/709476
Thanks,
-mario
To manage notifications about this bug go
Even if FRAMEBUFFER=Y wasn't added, I think that a change to stop adding
all those other drm drivers makes a lot of sense. No use doubling the
initrd size for the LUKS case.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to syst
AFAICT; these initramfs-tools package changes would cover it:
* hooks/framebuffer can be totally removed.
* scripts/init-top/framebuffer should probably stay
* conf/initramfs.conf needs FRAMEBUFFER=y added to it
--
You received this bug notification because you are a member of Ubuntu
Touch see
Plymouth only gets added to the initrd when LUKS is enabled or you mark
another reason for needing the framebuffer.
So the suggestion I have from comment #49 is to mark needing the
framebuffer by default, and then stop including any DRM modules because
simpledrm is built into the kernel.
--
You
.04-LTS to fix many more bugs, but
apparently that is too late now, according to
https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/709476
Thanks,
-mario
** Affects: gst-plugins-good
Importance: Unknown
Status: Unknown
** Affects: pipewire
Importance: Unknown
It's marked failed to upload on all architectures right now:
INFOgir1.2-glib-2.0-dev_1.78.1-15_amd64.deb: Version older than that in the
archive. 1.78.1-15 <= 2.79.1-1
INFOgir1.2-glib-2.0_1.78.1-15_amd64.deb: Version older than that in the
archive. 1.78.1-15 <= 2.79.1-1
I guess that me
With your change Fedora and Ubuntu are now behaving relatively similarly.
* Both have a deficiency where the handoff from BGRT logo to Plymouth is doing
a modeset for some reason.
* Due to something in Fedora's GRUB it's a little clearer when GRUB starts.
Here's various artifacts if you want to
Ah I did have GRUB_TIMEOUT set; I hadn't expected that caused a black
screen.
Moving that to zero certainly helps. It's a lot better; but still not perfect.
Let me get things back to as close as possible to stock and capture logs and a
videos to compare with Ubuntu and Fedora with this exact sam
I tested it on Noble with a hand built kernel and it at least does what
you planned (don't see any console messages), but also I'm not seeing
the OEM vendor logo stick all the way through. There's a really long
time of a black screen. Not sure if this is because it was an upstream
kernel and it's
You could detect both parameters to avoid that corner case.
Alternatively this is something I feel simpledrm will help you avoid
hitting too.
Otherwise it sounds good to me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sys
Yeah; so try forcing plymouth to the Ubuntu initrd like this:
echo "FRAMEBUFFER=y" | sudo tee /etc/initramfs-tools/conf.d/splash
Then if you rebuild the initrd you'll end up with plymouth in it.
This unfortunately DOUBLES the initramfs size; but it's because it puts all the
drm modules in there
Something "big" I notice different is that by default Ubuntu doesn't put
plymouth in the initramfs but Fedora does.
Maybe plymouthd really isn't running at the time systemd-fsckd is
running.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
> I don't really know if Fedora does that better or they just failed to
notice the bug.
I have Fedora 39 and Ubuntu both set up on a Z13 and Plymouth comes up in
Fedora with simpledrm; never see the console. That's why I was thinking
something might be missing and worth looking at.
* Fedora doe
Have you already looked at everything Fedora is doing in this area?
They already have simpledrm; but from what you described I would have
thought they should still lose the fbcon race.
Is it just that they don't have systemd-fsckd patch? I would think they
still end up showing ERR/WARN kernel mes
> But the feature would still be gated on the "splash" kernel parameter
which is Plymouth-specific and may cause pushback from kernel
developers.
If the patch is the way you go another idea for you is to use the
"quiet" keyword to key off instead for this behavior which is already
used by the kern
** Package changed: fwupd (Ubuntu) => initramfs-tools (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2046646
Title:
package fwupd 1.7.9-1~22.04.3 failed t
This is the same issue as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045573
Here is a commit that fixes the issue by changing default pre-emption
policy since the kernel can't know about your mesa version.
https://github.com/torvalds/linux/commit/d6a57588666301acd9d42d3b00d74240964f07f
Public bug reported:
While upgrading procedure abort
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: cups-ppdc 2.3.1-9ubuntu1.2
ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126
Uname: Linux 5.15.0-89-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
AptOrdering:
libx
Public bug reported:
While updating
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libx11-6 2:1.6.9-2ubuntu1.2
ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126
Uname: Linux 5.15.0-88-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
CasperMD5Check
Public bug reported:
While updating
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libavahi-glib1 0.7-4ubuntu7.1
ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126
Uname: Linux 5.15.0-88-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5Che
Public bug reported:
bugs while updating
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libx11-6 2:1.6.9-2ubuntu1.6
ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126
Uname: Linux 5.15.0-88-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
CasperMD5
I've published a PPA here:
https://launchpad.net/~superm1/+archive/ubuntu/gitlab2971/+packages
This has builds both for 22.04 (Jammy) and 23.04 (Lunar). Please
upgrade to that, drop the module parameter and see if things improve.
# sudo add-apt-repository ppa:superm1/gitlab2971
# sudo apt upgrad
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Package changed: mutter (Ubuntu) => mesa (Ubuntu)
** Also affects: mesa (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
**
From the upstream bug this is caused by PSR, so it's not a mesa issue.
** No longer affects: mesa (Ubuntu)
** No longer affects: mesa (Ubuntu Jammy)
** No longer affects: mesa (Ubuntu Lunar)
** No longer affects: mesa (Ubuntu Mantic)
** No longer affects: mesa (Ubuntu Noble)
--
You received
It's unclear if this is a BIOS, mesa or kernel bug at this time, but
it's certainly not an Xorg bug as it was reproduced in Wayland.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2954
https://gitlab.free
** Package changed: xorg (Ubuntu) => mesa (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2042054
Title:
22.04.3, zen 4 7840, screen turn white exception
Status in m
6.5.6 has the fix for preemption issue, it should get fixed when stable
updates come in Mantic.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2039868
Title:
amdgpu reset dur
Ok in this case can you please open an upstream mesa bug?
** Changed in: mesa (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/203
Also - can you still repro with mesa 23.2.1-1ubuntu2? This just landed
right after you reported this issue.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: mesa (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you ar
I'd say that's very likely. That mesa upgrade just landed in the archive
a few days ago and the trace you reported looks more like how a mesa bug
manifests.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
--
You r
Are you up to date on the current version of mesa in 23.10?
23.2.1-1ubuntu2?
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://b
** Changed in: mesa (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1987792
Title:
Totem and VLC crash when playing dvd with VAAPI ra
Random resets are "typically" triggered by mesa or application bugs.
Can you still trigger them in the latest mantic (which has a more up to
date mesa and kernel)?
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Status: New => Invalid
** Changed in: mesa (Ubuntu)
Status: New => In
> NonfreeKernelModules: fglrx
Nothing that will be done in mesa for an issue with fglrx anyway these
days.
** Changed in: mesa (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to m
In this case the kernel is the "messenger" for the page fault. This is
more likely to be a mesa or application issue than a kernel issue.
Can you please raise a ticket to the upstream mesa bug tracker?
https://gitlab.freedesktop.org/mesa/mesa/
** Also affects: mesa (Ubuntu)
Importance: Undec
This seems to be a related problem:
Sep 29 07:00:30 hyades systemd[1]: apt-daily-upgrade.service: Unit
process 51088 (exim4) remains running after unit stopped.
I would think that apt-daily-upgrade relies on exim4 getting actually
restarted after an update. If the process remains running, does th
I'm running systemd:amd64 249.11-0ubuntu3.10 from jammy-updates on
Ubuntu 22.04.3 LTS.
--
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/2037399
Title:
Processes keep running
Public bug reported:
I have a number of Ubuntu 22.04 installations on various computers. In
the last month, I have seen more and more log messages like the
following from different systems:
```
systemd[1]: apache2.service: Unit process 70257 (apache2) remains running after
unit stopped.
systemd
** Also affects: mesa (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux-hwe-6.2 (Ubuntu Mantic)
Importance: Undecided
Status: Invalid
** Also affects: mesa (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux-hwe-6.2 (Ubuntu
I believe this likely needs the VCN fixes from
https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 backported.
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #9728
https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728
** Also affects: mesa (Ubuntu)
Importance: Undecided
I believe the same thing can likely happen if llvm updates but mesa
stays the same. Can you embed both into the string?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2020604
T
It seems a way that this may be avoided is for GL_RENDERER string to
always be updated when mesa updates.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2020604
Title:
After
** 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
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2017142
T
Public bug reported:
[ Impact ]
VA-API decoding doesn't work on DCN 3.1.4.
Mesa 22.2.5 includes all the code to support it but is missing the chip ID.
The device ID was included in upstream mesa 22.3.1.
[ Test Plan ]
* Verify that VA-API works using "mpv" or a similar tool that uses VA-API
*
> Where? /usr/lib/systemd/system/fwupd-refresh.service only has
After=network.target. Perhaps that'd be the fix.
Ah... this was fixed in upstream already in 1.8.5 release.
https://github.com/fwupd/fwupd/commit/fe5d93f7d2712f3b708e562a5f7e9be897e04d1d
** Also affects: systemd (Ubuntu Kinetic)
I
BTW - fwupd already uses network-online.target for this unit. One could
probably argue this is a systemd bug.
> [Unit]
> Description=Refresh fwupd metadata and update motd
> Documentation=man:fwupdmgr(1)
> After=network-online.target
>
> [Service]
> Type=oneshot
> CacheDirectory=fwupdmgr
> Stand
Public bug reported:
problema para abrir qualquer vídeo seja com o totem ou usando o opencv,
apenas consigo abrir video com ffmpeg ( não se aplica ao opencv )
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: libgstreamer1.0-0 1.20.3-1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
At least from AMD's tests, backported mesa stack is working properly
with RDNA3. Adjusting tag 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 U
Public bug reported:
Version 1.1.0 (released in March 2022) brings MP3 encoding/decoding
support. It would be great if the version here could be updated.
** Affects: libsndfile (Ubuntu)
Importance: Undecided
Status: New
** Tags: upgrade-software-version
--
You received this bug
I reported the bug here: https://bugs.launchpad.net/ubuntu/+bug/1990723
Seems to affect quite some people (via other discussions), please help.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.l
@dbungert
Updated to 249-11-0ubuntu3.6 using normal repository.
The error " mtd device must be supplied (device name is empty)" disappeared.
[actually with normal sudo apt upgrade nothing was being upgraded saying "The
following packages have been kept back: .
Solution 2 here did the job
https:
Hi,
on 21.09.2022 updating ubuntu broke it with this bug.
Running on i386, dell latitude e7450 with ssd and ubuntu22.04.1, kernel
5.15.0-48 generic, x86.
After booting, I get the mtd device must be supplied etc etc error, and
I am left with a terminal only version.
I have an important hint: as s
Public bug reported:
Die Paketinstallation ist gescheitert
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libnih-dbus1 1.0.3-6ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
C
YC is in the process of doing an SRU for a bunch of other bugs in fwupd
and the fix should come in that same SRU I expect.
** Changed in: fwupd (Ubuntu Jammy)
Assignee: (unassigned) => Yosu (yc)
** Changed in: fwupd (Ubuntu Jammy)
Assignee: Yosu (yc) => Yuan-Chen Cheng (ycheng-twn)
--
** Changed in: fwupd (Ubuntu Impish)
Status: Confirmed => Won't Fix
--
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/1969976
Title:
DynamicUser=1 doesn't get along wi
One possible solution is to split the fwupd package along it's possible plugins
into multiple packages.
However I tend to agree that it has no use in a cloud or container seed.
I also agree libmm-glib0 shouldn't recommend modem manager.
** Changed in: fwupd (Ubuntu)
Status: New => Invalid
** Changed in: fwupd (Ubuntu)
Status: New => Fix Committed
--
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/1969976
Title:
DynamicUser=1 doesn't get along with servic
Just to correct a few of the targets on this issue.
* The reverts mentioned in #30 need to be pulled into linux-firmware for focal.
* They're already included in jammy.
** Changed in: amd
Status: New => Fix Released
** No longer affects: mesa (Ubuntu)
** Also affects: linux-firmware
OK, so upstream here is what we have done (pretty much your suggested
W/A).
main:
https://github.com/fwupd/fwupd/commit/7b0d6bc6e03381544e3fb1836c177d492c9d0bbc
https://github.com/fwupd/fwupd/commit/e90b04d7319874db36c06245ab07858589ce8bc8
https://github.com/fwupd/fwupd/commit/f818404d817f6f366998
> The comment at
https://github.com/fwupd/fwupd/issues/3037#issuecomment-1100816992
suggests that disabling the DynamicUser= setting makes the service work
again. Maybe that's worth a try, in order to get both problems solved?
(i.e. shipping an override config for fwupd)
> $cat /etc/systemd/system
Public bug reported:
Updating to systemd 245.4-4ubuntu3.16 has caused a regression in Ubuntu
20.04, that fwupd-refresh.service always fails to run.
This has been root caused down to the changes in
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538
Unfortunately this is an ups
> https://git.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/systemd/commit/?id=e3aacfa26e3fc6df369e6f28e740389ae0020907
This appears to have caused a regression in fwupd in Ubuntu 20.04 with
details at https://github.com/fwupd/fwupd/issues/3037
fwupd-refresh.service uses DynamicUser and now hi
> If fwupd is being backported to previous releases of Ubuntu it seems
like libgusb would also need to be backported.
Actually the bug was introduced in libgusb 0.3.8, fixed in libgusb
0.3.9. If older releases have older than 0.3.8 they shouldn't need
libgusb backport. See comment #3.
--
You r
** Changed in: fwupd (Ubuntu)
Status: Confirmed => Invalid
** Changed in: libusb (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libusb in Ubuntu.
https://bugs.launchpad.net
Ah probably was caused by
https://github.com/hughsie/libgusb/commit/4b52b0cd27fdadcb29b4518cff293c1c76b872a9
in 0.3.8 and fixed by
https://github.com/hughsie/libgusb/commit/24934619a2ad3467b98142dfab2039985afc970d
in that case.
** Also affects: libgusb (Ubuntu)
Importance: Undecided
Stat
** Package changed: protobuf-c (Ubuntu) => protobuf (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/847065
Title:
libprotobuf-lite link not created
Status in pro
** No longer affects: initramfs-tools (Ubuntu Xenial)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1561643
Title:
initramfs-tools ignores the FRAMEBUFFER option
Verified on YC with the following combination all from -proposed:
# dpkg -l | grep "linux-firmware\|linux-image-5.14.0-1005-oem\|21.0.3-0ubuntu0."
ii libegl-mesa0:amd64 21.0.3-0ubuntu0.3~20.04.3
amd64free implementation of the EGL API -- Mesa vendor li
With manually placing firmware in /lib/firmware (since SRU not started
for that) and using 5.14 kernel confirmed that mesa looks good. Since
we don't have linux-firmware SRU package yet and they are combined on
this bug report I will not add "verification-done-focal".
# glxinfo | grep "OpenGL ren
#134: @xnox, have you re-sent it? It looks like
https://lkml.org/lkml/2021/1/14/1091 got no feedback.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1835660
Title:
Here's a PPA build with the mesa fix Alex mentioned backported:
https://launchpad.net/~superm1/+archive/ubuntu/lp1928393
If you can follow the directions to add that PPA and upgrade to that
mesa package you can see if that indeed fixes it.
** Also affects: mesa (Ubuntu)
Importance: Undecided
Public bug reported:
Hi
1)
$ lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04
2)
$ apt-cache policy xorg
xorg:
Installed: 1:7.7+19ubuntu14
Candidate: 1:7.7+19ubuntu14
Version table:
*** 1:7.7+19ubuntu14 500
500 http://cl.archive.ubuntu.com/ubuntu focal/main
@Lukas (#8): Works.
1. Permissions are correct. This was obvious already, since `update-initramfs
-v` states that it doesn't execute /usr/share/initramfs-tools/hooks/lvm2 due to
insufficient permissions.
2. Unpacked the initramfs and files are included again.
3. Boots.
Thanks a lot.
--
You re
Good morning. Took me an afternoon to figure this out, after no kernel
was booting anymore. Still present with version 2.03.11-2ubuntu2 of the
package.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bu
** Package changed: python-defaults (Ubuntu) => update-manager-core
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1901173
Title:
Updating focal to groovy
Public bug reported:
Running `do-release-upgrade` from focal to groovy, I got the following
crash after the packages were downloaded:
```
apt_pkg.Error: E:Could not configure 'libc6:amd64'. , E:Could not perform
immediate configuration on 'libnss-nis:amd64'. Please see man 5 apt.conf under
APT:
I was just following the documentation on https://ubuntu.com/server/docs
/service-ldap and there it is present. It still was on 19.10. So I was
just wondering. Sorry!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in
Public bug reported:
Installing slapd and ldap-utils results in missing backend
dn: olcBackend={0}mdb,cn=config
the installer skips the installation step. Has to be added by
ldpamodify.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: slapd 2.4.49+dfsg-2ubuntu1.2
ProcVersionSignature: Ubun
re-enabling secure boot makes no difference
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1859308
Title:
software-properties-gtk erroneously reports that Inte
1 - 100 of 277 matches
Mail list logo
