Public bug reported:
% lsb_release -rd
No LSB modules are available.
Description:Ubuntu 24.04.1 LTS
Release:24.04
% LANG=C apt policy python3-apparmor
python3-apparmor:
Installed: 4.0.1really4.0.1-0ubuntu0.24.04.3
Candidate: 4.0.1really4.0.1-0ubuntu0.24.04.3
Version table:
***
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 2083995
When reporting bugs in the future please use apport by using 'ubuntu-
One thing that I noticed this morning is that sometimes some loop mounts
also appear from time to time.
** Attachment added: "Screenshot From 2024-10-09 07-34-31.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2083686/+attachment/5826195/+files/Screenshot%
** Package changed: ubuntu => bluez (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2083995
Title:
Bluetooth can neither find new device, nor be connected by paired
You have been subscribed to a public bug:
Os version: Kubuntu 24.10
After recent updates after Oct 1st, the bluetooth failed to work. I
can't use it to find any new device, also the already paired device
cannot connect to it. I compared the log with the past and didn't find
anything related to th
In Bluetooth the default headset profile is indeed lower quality than
you would want for music. Have a look in Settings > Sound to change the
profile in use.
** Tags added: oracular raspi
** Tags added: a2dp
** Package changed: bluez (Ubuntu) => pipewire (Ubuntu)
** Summary changed:
- Bluetoot
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
an
In the logs I'm running kernel 6.4 as this version supports my monitors.
When trying the most recent 6.8 kernel, the issue persists.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
>>> Copied from an email to kernel maintainers sent on 31.10.2023
15:23:52
Moving from Ubuntu 23.04 to 23.10 came alongside a kernel update from
6.2.0-36-generic to 6.5.0-10-generic. As of the update, plugging in my
USB-C monitor causes my machine to immediately shut off its
I fixed it with:
sudo apt purge arctica-greeter
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/2081302
Title:
Graphical crash loop on fresh installation
Status in Ubuntu
Thanks for 99-hp-lt4129-test.rules, it works fine on kubuntu 24.04.1!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1574582
Title:
HP lt4120 Snapdragon X5 LTE USB
I can confirm graphical crash loop after upgrade from Ubuntu MATE 24.04
to 24.10. Please fix before release.
$ sudo tail /var/log/lightdm/seat0-greeter.log
[+1,31s] DEBUG: Read 8 bytes from daemon
[+1,31s] DEBUG: Read 35 bytes from daemon
[+1,31s] DEBUG: Prompt user with 1 message(s)
[+1,32s] DEB
This issue arises because the container is running on top of a FIPS-
enabled kernel which provides the /proc/sys/crypto/fips_enabled = 1
flag.
On Noble, openssl sees this flag and expects therefore to be operating
in FIPS mode, but at this point the Noble container is not in FIPS mode
- we haven't
This bug was fixed in the package shadow - 1:4.13+dfsg1-4ubuntu3.2
---
shadow (1:4.13+dfsg1-4ubuntu3.2) noble; urgency=medium
* d/p/lp2063200/*: amend the patch to fix `useradd -D` breakage
(LP: #2063200)
-- Simon Chopin Thu, 30 May 2024 16:52:35 +0200
** Changed in: shadow
The verification of the Stable Release Update for shadow has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2083944
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
Updated [Test Plan].
Further clarifying the verification done confirmation from Simon in #22: in
chat "I actually retested the thing on Jammy, Noble, and the proposed version,
just to be sure.".
Thank you very much, Simon!
--
You received this bug notification because you are a member of Ubuntu
Thanks for clarifying!
1) Ok, that's reasonable.
2) Ok, I'll fix the Test Plan in the SRU bug description after your
confirmation (in chat) I could do it.
3) Ok, thanks for confirming. Right, after reviewing the comments, it seems the
delays were related to getting a verification confirmation an
Public bug reported:
Title basically
oracular-preinstalled-desktop-arm64+raspi.img.xz
2024-10-07 20:21
9aaacf14e4d12bd59ac20ba07d34dbe6ad2dee14bc211947915d6b2b845af424
To reproduce:
Fresh "installation"
Connect any bluetooth headset or speaker
Play any youtube video (preferably music you're fami
For the SRU, keep the system V zone as they are. I tested that the newly
build tzdata files haven't changed:
```
for x in CET CST6CDT EET EST EST5EDT HST MET MST MST7MDT PST8PDT WET; do cmp
/usr/share/zoneinfo/$x tzgen/$x; done
```
--
You received this bug notification because you are a member
Ugh, blast from the past.
1/ That output, while very probably a bug, is not a regression, as it
was already present in Jammy. Given my lack of familiarity with the
upstream code, I didn't even try to find out what was going there and
instead focused on my task :)
2/ It's a bug in the test plan (I
Hi Simon,
Thanks for the all work on this.
This seems almost good to go for release, but I wanted to check 3 points with
your first.
1) Are these uppercase messages expected by default?
They seem unrelated to the proposed changes; just checking.
uppercase messages by default?
+ groupadd --ext
Running `snap refresh --channel=24.10/stable subiquity` on a Jammy ISO
shows an up-to-date Subiquity with the right colors.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kbd in Ubuntu.
https://bugs.launchpad.net/bugs/1980587
Autopkgtests in update_excuses are clear/good now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/2063200
Title:
useradd --extrausers --groups tries to lock /etc/group
Sta
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1980587
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
Are there any other apps that flicker? If you find non-Flutter apps
exhibit the bug then this would be a GTK bug. If you find it's only
Flutter apps then the issue needs to move to
https://github.com/flutter/flutter/issues
** Package changed: ubuntu => gtk+3.0 (Ubuntu)
--
You received this bug n
You have been subscribed to a public bug:
The windows contours (and shades) and display in general starts to
blinks after the computer return from the "save energy turn off of the
display".
Steps to reproduce:
- Let the display turn off and Ubuntu lock as save energy configuration;
- Wake up the
This seems to be still the case on Oracular, on a Thinkpad x201 (bug
2083857), though I can't reproduce it on Jammy .5.
Here is a screenshot of colortest-8. The blue background seems to appear
during the boot, when the setvtrgb unit is started, so I'm flagging this
as also affecting `kbd`. That mi
I don't think there's interest in upgrading mesa in jammy at this point
so here comes a 4-versions-across bisect 😰
--
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:
Indeed installing mesa 24.2 in the snap resolves the issue.
However the patch that was linked in the mesa bug alone does not:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29124
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
30 matches
Mail list logo
