On Sun, Dec 10, 2023 at 01:45:36AM -, Roger Nelson wrote:
> I'm curious if this bug is still being investigated. RPI4 with wlan0,
> eth0 and eth1 (USB3 using r8152 driver) definitely manifests this bug. I
> need to wait ~30 minutes before either wlan0 or eth0 becomes available
> in order to res
Public bug reported:
Sound is not coming in initial start up and after that and also pulse
audio is not opening
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 [modified:
usr/share/pulseaudio/alsa-mixer/paths/analog-output-speaker.conf]
ProcVersionSignature
Guten Tag!
Ich bin am 12.12.2023 wieder im Büro.
Ihre Nachricht wird NICHT automatisch weitergeleitet.
In dringenden Fällen wenden Sie sich bitte an Markus Delorenzo:
+43-5232-2208-39
md(@)ruetz.at
Mit freundlichen Grüßen
Hans-Peter Schmidt
--
You received this bug notification because you are
I'm curious if this bug is still being investigated. RPI4 with wlan0,
eth0 and eth1 (USB3 using r8152 driver) definitely manifests this bug. I
need to wait ~30 minutes before either wlan0 or eth0 becomes available
in order to restart systemd-networkd to activate eth1 and then ip link
set up eth1. A
Exact same behavior, and exact same fix. On 5.64-0ubuntu1.1, the
connection attempt results in a PIN prompt ( doesn't work). It
*does* still work over USB.
Per OP, I tried downgrading to 5.64-0ubuntu1 *immediately* corrected the
problem.
--
You received this bug notification because you ar
I've been having this issue since updating to mantic - the sound to HDMI
just freezes and any application that is writing to it also freezes. If
I do (from a terminal):
systemctl restart --user wireplumber.service
It comes back for a while.
I'm also running on a Lenovo X1 Carbon 7th generation.
I'm having this bug as well. It is a bug cause with current version
Dualshock 3 just doesn't connect, even if you do enter the PIN
code.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launch
Oh. To the question of whether there was a systemd change in this
window: yes absolutely, because this is the point at which the riscv64
builders moved from lgw manually-operated qemu with a 20.04 guest image,
to bos03 openstack-operated qemu with a 22.04 guest image.
Which is also why we've move
On Sat, Dec 09, 2023 at 05:13:28PM -, Andy Whitcroft wrote:
> Was there any systemd/udev change in this timeframe? As the device
> files are very much connected to those.
My understanding is that these devices are supposed to be created directly
by the kernel on devtmpfs and NOT via udev, whi
Was there any systemd/udev change in this timeframe? As the device
files are very much connected to those.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045586
Title:
This bug was fixed in the package newt - 0.52.24-1ubuntu1
---
newt (0.52.24-1ubuntu1) noble; urgency=medium
* Merge with Debian unstable (LP: #2045576). Remaining changes:
+ Remove libnewt0.52.preinst altogether, which contains destructive
operations with none of the appro
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
All autopkgtests for the newly accepted mesa (23.2.1-1ubuntu3.1~22.04.1) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
mutter/42.9-0ubuntu5 (arm64, ppc64el)
vtk9/9.1.0+really9.1.0+dfsg2-3build1 (armhf)
Please visit the excuses p
13 matches
Mail list logo
