Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-driver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mesa (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mesa (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mesa (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mesa (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Hello Sergio, or anyone else affected,
Accepted openldap into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openldap/2.5.14+dfsg-0ubuntu0.22.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Sergio, or anyone else affected,
Accepted openldap into kinetic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/openldap/2.5.14+dfsg-0ubuntu0.22.10.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Public bug reported:
Updating base-files at point releases is pointless, misleading, and
causes confusing and anxiety
Can we please stop updating base-files at point releases?
Building new installer media, and calling it with a new .N number is
good, and helps to differentiate what the initial
Hello Kai-Heng, or anyone else affected,
Accepted pulseaudio into jammy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:15.99.1+dfsg1-1ubuntu2.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Kai-Heng, or anyone else affected,
Accepted pulseaudio into kinetic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:16.1+dfsg1-1ubuntu3.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
This bug was fixed in the package rsyslog - 8.2302.0-1ubuntu2
---
rsyslog (8.2302.0-1ubuntu2) lunar; urgency=medium
* d/t/simple-*, d/t/control: ignore aa-enforce error, which can happen
on armhf in the Ubuntu DEP8 infrastructure, and allow-stderr for
these tests (LP:
** Also affects: gce-compute-image-packages (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
The AppArmor profile for rsyslog, which had been disabled on previous
Ubuntu versions, was enabled in lunar.
The package google-compute-engine added a config file to
Public bug reported:
The AppArmor profile for rsyslog, which had been disabled on previous
Ubuntu versions, was enabled in lunar.
The package google-compute-engine added a config file to rsyslog which
requires rw access to /dev/console
google:ubuntu-23.04-64 /root# cat
I'd like to understand better exactly how it happened that the user got
this crash. Is it a matter of a corrupted .crash file on input, or is
it that the user tried to feed in a file that was not intended to be
input for apport-unpack? I see that the command line that triggered
this appears to
Hello Andreas, or anyone else affected,
Accepted apparmor into kinetic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/apparmor/3.0.7-1ubuntu2.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug may NOT BE A SECURITY ISSUE, but without access to audio I
cannot do 90% of the work I do in Ubuntu. I suggest that you acknowledge
the problem and fix it. For the meantime I will be using Windows 10.
G
Bug description:
I didn't have sound after an update to Ubuntu (and a reboot
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Public bug reported:
I didn't have sound after an update to Ubuntu (and a reboot the next day).
Pulseaudio does not recognize my soundcard. Since all my work involves audio, I
have switched to Windows 10 (I have a dual boot computer).
LSPCI finds my sound card but alsa and pacmd don't.
Until
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1008.8
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-jammy' to 'verification-done-jammy'. If the
problem still exists,
i have the same issue
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2007913
Title:
HDMI Output sound has disappeared after Ubuntu update
Status in alsa-driver
** Merge proposal linked:
https://code.launchpad.net/~nteodosio/software-properties/+git/software-properties/+merge/438313
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
** Changed in: pixman (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pixman in Ubuntu.
https://bugs.launchpad.net/bugs/1988796
Title:
Incorrect rendering
** Tags removed: need-duplicate-check
--
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/2009168
Title:
package linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1
Public bug reported:
every time i boot the computer an error appear on that package
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
This bug was fixed in the package xubuntu-meta - 2.248
---
xubuntu-meta (2.248) lunar; urgency=medium
* Refreshed dependencies
* Added dbus-x11 to desktop-minimal-recommends, desktop-recommends
(LP: #2009145)
-- Sean Davis Fri, 03 Mar 2023 05:56:02 -0500
** Changed in:
After further investigation, I would say that "Discover" wants to
upgrade a package (libmm-glib0) notwithstanding the fact that it is
phased and that apt does not want to upgrade it.
Funny enough, Discover does not indicate the other phased packages (it
is up to 24!) as upgradable.
--
You
There is a further problem, I do not know if it should be a separate
issue.
The updates icon in the system tray now appears also when there are in
fact no updates that can be applied. Don't know if this actually depends
on the presence of updates that are phased out or on the presence of
Ubuntu
Hi, what is the current status? Apport seems to be default-enabled on
all the live images I tried. Also let me ask, the informational link
where one can query one’s own uploads, it does not seem to display
whether or not a coredump was uploaded. Could you provide the same? It
was said that if
Public bug reported:
Related to https://salsa.debian.org/xorg-team/xorg/-/merge_requests/17
The dbus-x11 package is being deprecated. As a result, the Xfce packages
from upstream Debian no longer pull it in. Until the xorg packages have
been updated accordingly in Ubuntu, the Xubuntu settings
It seems keyboard layouts available for xkb layouts but not for m17n
layouts
** Changed in: console-setup (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
** Package changed: ubuntu => pulseaudio (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2009110
Title:
USB audio card not recognized
Status in pulseaudio
You have been subscribed to a public bug:
My USB audio card, named CM383-80864, was plugged in and recognized in
alsamixer but not shown in setting.
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: pulseaudio 1:16.1+dfsg1-1ubuntu3
ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
32 matches
Mail list logo
