[Expired for ubuntu-settings (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: ubuntu-settings (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Thanks for all the responses. I'm not sure how quickly I'll be able to
get to this either, so I'm hesitant to commit to fixing myself. That
said, if I can get time to send patches before your team gets to fixing
it, I'll do my best.
To answer the question about how frequently we see this: it
Hi Mitchell,
Thanks for taking a look at this bug report.
In my Ubuntu-22.04 environment, I am building openssl 3.1.2 myself,
packaging it and installing it on the box.
Instead of selectively taking one patch, would it be worth just moving the
newer versions of openssh ?
Debian appear to have
Special maas image built with util-linux, 2.39.1-4ubuntu2, from
https://ppa.launchpadcontent.net/xnox/release-critical/ubuntu is looking
good. I have one machine deployed with this:
ubuntu@rumford:~$ uname -r
6.5.0-5-lowlatency
ubuntu@rumford:~$ apt-cache policy util-linux
util-linux:
** Changed in: util-linux (Ubuntu Mantic)
Status: New => Triaged
** Changed in: util-linux (Ubuntu Mantic)
Importance: Undecided => Critical
** Changed in: systemd (Ubuntu Mantic)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu Mantic)
Status: Incomplete =>
This bug was fixed in the package network-manager - 1.44.2-1ubuntu1
---
network-manager (1.44.2-1ubuntu1) mantic; urgency=medium
* Merge with Debian (LP: #2038439)
network-manager (1.44.2-1) unstable; urgency=medium
* New upstream version 1.44.2
* Rebase patches
-- Jeremy
Fix under review https://lists.ubuntu.com/archives/kernel-
team/2023-October/146015.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2038567
Title:
Disable
Closing this FFe, it needs to wait on the next LXD releases in a few
weeks and it is already too late to land this in Mantic.
If it is to land it will have to be done via an SRU after the LXD
releases, and verification that all is good with LXD.
Marking as invalid and unsubscribing the release
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2038561
Title:
Requesting Ubuntu package manager to
Fix for the ptrace issue
** Patch added:
"0001-UBUNTU-SAUCE-no-up-apparmor-disable-1ea37b26d720-UBU.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038567/+attachment/5707461/+files/0001-UBUNTU-SAUCE-no-up-apparmor-disable-1ea37b26d720-UBU.patch
--
You received this bug
Hello Prashanth, thank you very much for making this bug report and
making Ubuntu better!
Are you building openssl 3.1.2 or pulling the package from somewhere?
I tried installing a slightly newer version in a jammy LXC container and
see this error when trying to install libssl3 (a requirement to
** Summary changed:
- Mantic 6.5.0-7 kernel causes regression in LXD container usage
+ Disable restricting unprivileged change_profile by default, due to LXD
latest/snap not yet compatible with this new apparmor feature
** Changed in: lxd (Ubuntu)
Importance: Undecided => High
** Changed
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-535
(Ubuntu)
--
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/bugs/2038681
Title:
nvidia-driver-535.113.01 crash
Thanks John,
it has been confirmed that
1ea37b26d720 UBUNTU: SAUCE: apparmor4.0.0 [73/76]: userns - allow
restricting unprivileged change_profile
is causing the issue. It has a sysctl to disable its behavior, but the sysctl
can't be defaulted to off in the kernel. So to disable the sysctl,
Public bug reported:
It was running RealVNC server, VMware Workstation Pro with Windows 11 guest,
Firefox and Thunderbird.
I used it with RealVNC Viewer on another machine and suddenly my VNC connection
dropped.
Coming to my nVIDIA laptop it was showing no gnome desktop anymore but a black
The bug description says "dnsmasq on Ubuntu Jammy/Lunar crashes [...]",
but IIUC it's actually only the Jammy one that crashes (the lunar-on-
jammy one maybe has other issues, but doesn't exhibit the crash). Am I
right? In this case please update the bug description accordingly.
Thanks!
Edit: I
Hello, I verified that Sergio's PPA contains the candidate upstream
patch (upstream commit d290630d31f4517ab26392d00753d1397f9a4114). If the
crash is still happening that probably wasn't the issue after all.
I see two possible ways forward here. One is classic git based
debugging:
1. compile
I was going over the ADT results for the complete linux suite:
https://autopkgtest.ubuntu.com/results/autopkgtest-
mantic/mantic/amd64/l/linux/20231002_144159_55314@/log.gz (6.5.0-7.7)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Grr... it works if I first run a dummy command within the machine:
systemd-nspawn -M jammy-rootfs --as-pid2 passwd root
machinectl start jammy-rootfs # it's working now!
machinectl login jammy-rootfs
(Even just "echo hello world" does the job)
However if you go back to a *fresh* image then
** Tags removed: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/2023545
Title:
[UBUNTU 22.04] openssl with ibmca engine configured dumps core when
Public bug reported:
My bluetooth it's loosing connection every 3 or 4 seconds.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluetooth 5.53-0ubuntu3.6
ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122
Uname: Linux 5.15.0-86-generic x86_64
NonfreeKernelModules:
Bluetooth not working as expected in ubuntu 20.04.
--
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/2038665
Title:
bluetooth not working proper;ly
Status in bluez package in
FEDORA-2023-86e10b6cae has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh
--advisory=FEDORA-2023-86e10b6cae`
You can provide feedback for this update here:
Thanks James, I've sent an official update as you can see.
--
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/2037497
Title:
gnome-shell crashes on Intel Ice Lake with SIGSEGV
FEDORA-2023-86e10b6cae has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-86e10b6cae
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
** Changed in: mesa (Fedora)
Status: Confirmed => Fix Committed
--
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/2037497
Title:
gnome-shell crashes on Intel Ice Lake
(In reply to Adam Williamson from comment #20)
> Scratch build is done for x86_64:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=107101328
>
> can folks test that and see if it helps? Thanks!
Works after updating to the packages in that Koji task.
--
You received this bug notification
Scratch build is done for x86_64:
https://koji.fedoraproject.org/koji/taskinfo?taskID=107101328
can folks test that and see if it helps? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Some upstream discussion indicates
https://gitlab.freedesktop.org/mesa/mesa/-/commit/9590bce3e249a34665b2c42b20bfdbdc7f32147f
may fix this. Setting POST, will do a scratch build for folks to test
shortly.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Hi!
Could you share the kernel and apparmor version?
I tested on mantic with the configuration below and I wasn't able to reproduce
the failure for this specific test.
I did see an unrelated dbus issue with the test suite and proposed a fixed on
** Description changed:
Two-line reproducer: run this on an Ubuntu 22.04 server.
sudo machinectl pull-raw
http://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64.img
jammy-rootfs
sudo machinectl start jammy-rootfs
Response:
Job for
Public bug reported:
Two-line reproducer: run this on an Ubuntu 22.04 server.
sudo machinectl pull-raw
http://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64.img
jammy-rootfs
sudo machinectl start jammy-rootfs
Response:
Job for systemd-nspawn@jammy-rootfs.service failed
This bug was fixed in the package usbmuxd - 1.1.1-3ubuntu1
---
usbmuxd (1.1.1-3ubuntu1) mantic; urgency=medium
* Rename usbmuxd.postinst to usbmuxd.preinst (LP: #2034539)
- Due to an issue with Netplan (LP#1999178), upgrades from Lunar to Mantic
are suffering from long
Repeating a bit with a Jammy container (hence new comment)
### PRE CONDITION
this is using the custom Mantic VM _and_ has
apparmor_restrict_unprivileged_unconfined disabled
sudo bash -c "echo 0 >
/proc/sys/kernel/apparmor_restrict_unprivileged_unconfined"
1. start a jammy container
lxc launch
on my machine (specs at the end) running Jammy as the host, and
launching a Jammy container:
1. lxc launch ubuntu:jammy test-jammy-on-jammy
from journal
Oct 06 07:36:47 j5awry-sys76 kernel: audit: type=1400
audit(1696595807.223:51559): apparmor="DENIED" operation="mount" class="mount"
Did the following:
1. launched a new VM from the custom build
lxc launch mantic-20231005 --vm --device root,size=20GiB mantic-cust-vm
2. pushed squashfs and lxc metadata from same custom build
lxc file push build.output/livecd.ubuntu-cpc.squashfs mantic-cust-vm/root/
lxc file push
We're not going to change the ubuntu-desktop metapackage to allow
switching to pulseaudio for Ubuntu 23.10.
There was a pipewire 1.0 RC (versioned as 0.3.81) release today with further
JACK improvements. That version is too late for Ubuntu 23.10 but it will be in
Ubuntu 24.04 LTS.
** Changed in: ubuntu-meta (Ubuntu Mantic)
Status: New => Won't Fix
** No longer affects: ubuntu-meta (Ubuntu Mantic)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
** Tags removed: rls-mm-incoming
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2038650
Title:
crash reports not sent to the Error Tracker
(did my mail answer from yesterday get eaten by launchpad?)
Here's an updated debdiff that:
- renames files using the lp- prefix,
- reworks the changelog to a more typical format:
* what (LP: #)
- ${file}
- adds DEP-3 to the patches
I've pushed an updated build on LP at
** Tags added: rls-mm-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2038650
Title:
crash reports not sent to the Error Tracker
Status in apport package in
jammy and focal packages uploaded to the archive for SRU
jammy, focal, and bionic also uploaded to
https://launchpad.net/~deity/+archive/ubuntu/apt/+packages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
Public bug reported:
>From what I can tell when I click the send button to send a crash report
to the Error Tracker the crash doesn't actually get sent. My testing
process follows:
1) Launch xeyes
2) pkill -11 xeyes
3) Click send in the apport dialog
4) ls -lh /var/crash
I would expect there to
** Changed in: apt (Ubuntu Jammy)
Status: Confirmed => In Progress
** Changed in: apt (Ubuntu Focal)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
** Description changed:
[Impact]
The snapshot service provides users access to older states of the archive
with ease of use, and enables a consistent user experience across all supported
releases, as otherwise users would have to rewrite their sources.list to make
use of snapshots and set
I tested on two machines where the boot failed previously. With the new
`scripts/functions`, the boot now works properly. Thanks you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
** Changed in: mesa (Ubuntu)
Milestone: mantic-updates => ubuntu-23.10
--
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/2037497
Title:
gnome-shell crashes on Intel Ice
I'll add that patch to mantic now, as it would take some time to get it
via a bugfix release
** Changed in: mesa (Ubuntu)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Submitted:
https://github.com/prusa3d/PrusaSlicer/issues/11429
While I have a MP that hides the problem by making tests verbose, I do
not want to proceed with it unless absolutely necessary as this is a
quite breaking bug for the GUI.
** Bug watch added: github.com/prusa3d/PrusaSlicer/issues
** Also affects: ubuntu-release-notes
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://bugs.launchpad.net/bugs/2037642
Title:
[FFe] Raspberry Pi 5 support
Public bug reported:
System crashed when installing update
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
ApportVersion:
** Attachment added: "prusa-slicer.log.gz"
https://bugs.launchpad.net/ubuntu/+source/slic3r-prusa/+bug/2031340/+attachment/5707297/+files/prusa-slicer.log.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gmp in Ubuntu.
The tests use boost background worker and are prone to race conditions.
Increasing verbosity of the test runner provides a band-aid by shifting
the test timings.
** Merge proposal linked:
https://code.launchpad.net/~vpa1977/ubuntu/+source/slic3r-prusa/+git/slic3r-prusa/+merge/453027
--
You
To test if 1ea37b26d720 UBUNTU: SAUCE: apparmor4.0.0 [73/76]: userns -
allow restricting unprivileged change_profile is the cause of the ptrace
denials. You can disable it using
sudo bash -c "echo 0 >
/proc/sys/kernel/apparmor_restrict_unprivileged_unconfined"
--
You received this bug
54 matches
Mail list logo
