*** This bug is a duplicate of bug 2063970 ***
https://bugs.launchpad.net/bugs/2063970
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2063970, so it is being marked as such. Please
When the problem is happening please run:
gsettings list-recursively | grep keybindings > keybindings.txt
and attach the resulting text file here.
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received
@u-dal:
This sounds like the apparmor policy is not being loaded can you please
provide the output of
```
sudo aa-status
```
and
```
sudo systemctl status apparmor
```
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Merge proposal linked:
https://code.launchpad.net/~juergh/ubuntu-seeds/+git/ubuntu/+merge/465215
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2062667
Title:
I seem to have the same apparmor problem with Chrome under Lubuntu
24.04. From "$ journalctl | grep apparmor | grep chrome" I got
info="Userns create restricted - failed to find unprivileged_userns
profile" (among other things). And it's been reproduced by another as
the following relates.
Can
We found that the root cause is the ibus.
A workaround to fix this problem is running:
GTK_IM_MODULE=simple gnome-text-editor
Furthermore, I will open an issue in:
https://github.com/ibus/ibus
** No longer affects: gtk4 (Ubuntu)
** Also affects: ibus (Ubuntu)
Importance: Undecided
Hello Julian, or anyone else affected,
Accepted apt into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.8.0 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
I'm having trouble seeing what the consequences are:
> the result is a permanently failed service
vs
> this is was a major annoyance on my m2 air after upgrading to noble
Was it it more than a red line in systemctl status output? Does it have
annoying logging behaviour or break some other
Hello Jeremy, or anyone else affected,
Accepted glib2.0 into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.80.0-6ubuntu3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Merge proposal linked:
https://code.launchpad.net/~simpoir/livecd-rootfs/+git/livecd-rootfs/+merge/465193
--
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
*** This bug is a duplicate of bug 2024392 ***
https://bugs.launchpad.net/bugs/2024392
The right duplicate might be bug #2040979 instead.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
I don't think that's enough since it also gets pulled in by ubuntu-
desktop and ubuntu-desktop-minimal as recommends. It would also be nice
if we found a solution that fixes the issue on existing installations
since upgrades from mantic to noble will trigger the bug.
--
You received this bug
The updates look good, thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2063221
Title:
Drop libglib2.0-0 transitional package
Status in glib2.0 package in Ubuntu:
** Description changed:
Impact
--
apt can struggle with ordering when handling the massive Y2028 time_t
transition when upgrading to Ubuntu 24.04 LTS.
It was identified that dropping the libglib2.0-0 transitional package
can help apt do things in the correct order.
+
** Description changed:
Impact
--
apt can struggle with ordering when handling the massive Y2028 time_t
transition when upgrading to Ubuntu 24.04 LTS.
It was identified that dropping the libglib2.0-0 transitional package
can help apt do things in the correct order.
Test
I got some information from a user on a more recent duplicate (bug
2063533). The problem seems to be that some users, when disabling the
stub-resolver, also create a symlink /etc/resolv.conf ->
/run/systemd/resolve/resolv.conf. This is not actually necessary because
systemd-resolved will make
reopening as per comment #8. @Sebastian, I suggest you disable
whoopsie-path instead "systemctl disable whoopsie-path" and then reboot
to get a clean "systemctl --failed"
for those who are like me looking for the "Privacy" GUI control panel
mentioned in comment #5, make sure you have the
Hi Andrea - since this is now a stable release update, I *think* the
next steps should be:
1) Edit this bug to use the SRU Template
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
(now done)
Since your team owns this package, please review that and let me know if you
have any
Hi Jeremy,
This looks mostly good, AFAICT.
Could you please complete the SRU bug template by adding the section
'Where problems could occur' / 'Regression potential'? [1]
And although the 'Test Case' is feasible to understand, based on the 'Impact'
section, it would be nice to have a
** Package changed: ubuntu => grep (Ubuntu)
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/2064165
Title:
When I used the wrong flag in a command I
*** This bug is a duplicate of bug 2047975 ***
https://bugs.launchpad.net/bugs/2047975
Ah, I see. Thanks for that link. The issue is that it is not actually
necessary to make the /etc/resolv.conf ->
/run/systemd/resolve/resolv.conf symlink. systemd-resolved will handle
DNSStubListener=no by
You have been subscribed to a public bug:
When I used the wrong flag in a command I received very unusual output:
( I was trying to prevent the colorization of the grep output )
administrator@updatestestsvr:~$ sudo dmesg |grep -i -nocolor cpu
LinuxTestRemoteOffice.zip
lscpu-out.txt
I tested this with a local package build and local repo in a mantic container,
doing an `apt --dry-run dist-upgrade` without/with that repo (w/ noble apt
sources list),
and manually download/run noble's release upgrader without/with that repo.
The behavior is the same (ie, no regressions) as
Is still an issue in 2024?
** Changed in: whoopsie-preferences (Ubuntu)
Assignee: Evan (ev) => (unassigned)
** Changed in: whoopsie-preferences (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Description changed:
- iproute2 upstream produces releases coinciding with upstream kernel
- releases to support the latest kernel features. Noble's iproute2 is
- still back at v6.1 even though it will use the v6.8 kernel. This means
- we provide no userspace interface for newer features -
When I make the insertion work. The problem is when I restart, it comes
back unconfigured.
--
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/2064169
Title:
Keyboard shortcuts
Public bug reported:
I don't know if the section is correct, but when using the ubuntu
keyboard shortcuts I added. Increase sound volume, when you put the
super+up on, it ends up doing the behavior of another one that I had
already removed to give way to this new one I made.
ProblemType: Bug
** Summary changed:
- [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from
testing/unstable (main)
+ Backport iproute2 6.8.0 to noble
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
All autopkgtests for the newly accepted software-properties (0.99.49) for noble
have finished running.
The following regressions have been reported in tests triggered by the package:
software-properties-qt/unknown (amd64, arm64, armhf, i386, ppc64el,
s390x)
Please visit the excuses page listed
> To clarify, this is not something that can be solved upstream in
apparmor, and a profile can't be accepted due to the nature of the path
location?
correct, if it is a unprivileged user writable location it can't be
fixed entirely upstream. It is possible for us to ship a profile that is
*** This bug is a duplicate of bug 2047975 ***
https://bugs.launchpad.net/bugs/2047975
cainmp@svr-ns1:~$ cat /etc/resolv.conf
# This is /run/systemd/resolve/resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking
*** This bug is a duplicate of bug 2047975 ***
https://bugs.launchpad.net/bugs/2047975
Per here: https://www.turek.dev/posts/disable-systemd-resolved-cleanly/
and the "Clean" solution
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Also affects: guix (Ubuntu)
Importance: Undecided
Status: New
--
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/2046844
Title:
AppArmor user namespace creation
We should drop it from the seed since we're not building ARM ISOs
anymore.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2062667
Title:
Fails on (and should be
Here's how to reproduce this in a LXD VM:
Download Ubuntu 24.04 Desktop image into ~/Downloads
Import the ISO
$ lxc storage volume import default ~/Downloads/ubuntu-24.04-desktop-amd64.iso
24.04-desktop --type=iso
Prepare a LXD VM
$ lxc init --empty --vm lxd-noble-fde -c limits.memory=6GiB -c
** Attachment added: "1st of snap to left bug"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2064146/+attachment/5772562/+files/IMG_3608.jpeg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
** Attachment added: "Screen snap that froze"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2064146/+attachment/5772558/+files/Screenshot%20from%202024-04-29%2019-50-09.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Attachment added: "3rd of snap to left bug"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2064146/+attachment/5772564/+files/IMG_3610.jpg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
** Attachment added: "2nd of snap to left bug"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2064146/+attachment/5772563/+files/IMG_3609.jpeg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Public bug reported:
I have "Active screen edge" -feature enabled.
First bug:
I had 2 instances of transparent orange snap to place appear for no reason in a
strange place.
Second bug:
I have transparent orange snap to place appear twice when trying to snap window
to left, top and right. Bottom
*** This bug is a duplicate of bug 2047975 ***
https://bugs.launchpad.net/bugs/2047975
How exactly did you disable the stub resolver?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
*** This bug is a duplicate of bug 2047975 ***
https://bugs.launchpad.net/bugs/2047975
And, if you still have an affected system in this state, what does
readlink /etc/resolv.conf show?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I plan to work on this during the OO cycle. It's an issue inherited from
Debian AFAIU.
--
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/1297025
Title:
Either the
*** This bug is a duplicate of bug 1297025 ***
https://bugs.launchpad.net/bugs/1297025
** This bug has been marked a duplicate of bug 1297025
Either the changelog.gz is missing or there is an erroneous link in the
libssl1.0.0 package
--
You received this bug notification because you are
n.b. If Ubuntu hasn't taken the 32-bit time_t change (which is in
Debian unstable) I have a commit which backs out this change for
building e2fsprogs on older systems, e.g., for backports.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rsyslog (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
Azure CVM images are impacted by the same issue. I see on #2064088 that
this is an tpm-backed FDE system. So I think it's the same problem here
if those desktop images use an systemd-based initramfs.
For now I suspect that the issue is due to systemd starting services and
setting up UNIX sockets
Looking at the diff between mantic and noble I think the regression was
cause by a change to pd-mapper.service.in for
https://bugs.launchpad.net/ubuntu/+source/qrtr/+bug/2054296
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
@Dmitry I have tried your workaround from #2, but step 8. (the second
hibernate) fails for me with a "Not enough swap space" error message.
On my setup I'm using a swapfile on a Btrfs formatted Logical Volume.
This worked fine in regards of hibernating on Kubuntu 23.10.
--
You received this bug
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2063221
Title:
Drop libglib2.0-0 transitional package
Status in glib2.0 package in Ubuntu:
I was able to get something working on my win 11 i9-13900H discrete
RTX2000 laptop.
I used:
mks.enable3d = "TRUE"
mks.enableDX12Renderer = "TRUE"
mks.enableDX11Renderer = "FALSE"
mks.dx12.vendorID = "0x17AA"
and I also had to do:
settings->system->dislay->graphics
entries for both vmware.exe
Thanks Lukas!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/2064093
Title:
if-up.d files do not have effect on ubuntu 24.04 LTS
Status in ifupdown package in Ubuntu:
You filed the bug report against NetworkManager. But the "up.d" hook is
called differently in NM, see https://netplan.io/faq#use-pre-up-post-up-
etc-hook-scripts
If this is about /etc/network/if-up.d then it should be targeted towards
the "ifupdown" package. I'm adding a corresponding bug task.
Hello, any progress on this? Now that ubuntu-fan is officially
deprecated in Noble can we simply sync iproute2 with Debian? Is there
any pending activity / requirement that are preventing this? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
The same caveat applies to -updates, but there is a question of whether
we should ship 2.8.0 as this or make 2.8.0 different, I did not push a
tag for it yet.
i.e. given that this is a stable release update that will break PPAs
users currently have warnings for, it might make sense to make it
** Description changed:
- ⚠️ Only land this in the release pocket after PPAs have been resigned
+ ⚠️ Only land this in the release/updates pocket after PPAs have been
+ resigned
(This bumps the apt version to 2.8.0. APT uses the odd/even number
system, with 2.7.x being the development
Fix committed in ubuntu/main
** Summary changed:
- Package wasn't installed on upgrade from Jammy to Noble
+ systemd-resolved wasn't installed on upgrade from Jammy to Noble
** No longer affects: systemd (Ubuntu)
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Fix
Tested with 22.02.0-2ubuntu0.4 and working fine. Thanks!
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
Can confirm that this is was a major annoyance on my m2 air after
upgrading to noble. it seems like this worked better in previous
releases. Looking at my logs it seems like it was already installed on
mantic but didn't cause startup problems. I think it gets pulled in by
being in Recommends for
** Merge proposal linked:
https://code.launchpad.net/~juliank/ubuntu/+source/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/465146
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Can we get proper SRU information on this bug? Thank you!
** Also affects: network-manager (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu Mantic)
Public bug reported:
This might be related to #2064088
The rsyslog service is continually timing out and restarting. If I use a
service drop-in file and change the 'Type' from 'notify' to 'simple',
the service starts and appears to work normally.
In the journal, I can see the attached apparmor
Public bug reported:
Some time ago I wrote a detailed answer to fix an error for lowering MTU
size for a cisco-compatible VPN
(here:https://unix.stackexchange.com/questions/768757/unable-to-ssh-
into-remote-machine-but-able-to-ping-vpnc/768758#768758)
After upgrading to Ubuntu 24.04 LTS, I'm
You have been subscribed to a public bug:
Some time ago I wrote a detailed answer to fix an error for lowering MTU
size for a cisco-compatible VPN
(here:https://unix.stackexchange.com/questions/768757/unable-to-ssh-
into-remote-machine-but-able-to-ping-vpnc/768758#768758)
After upgrading to
Hi Jeremy
> I do not understand why bugs like this cannot get fixed even years after
> several people have reported the same issue and the repro steps are clear
I understand this might seem frustrating, but the TL;DR is: Because it
isn't as clear as it might seem
Detail:
As you see throughout
Public bug reported:
[Impact]
libraries become marked as manually installed after transitioning to t64
package names as we forgot to transition the automatically installed bit.
Before:
root@m:~# apt-mark showmanual
base-files
bash
bsdutils
cloud-init
dash
diffutils
eatmydata
findutils
grep
gzip
** Description changed:
- I just do-release-upgraded from Jammy to Noble on a pretty minimal
- server.
+ [Impact]
+ Upgrades from jammy to noble sometimes end up without systemd-resolved being
installed, breaking networking as the system already migrated to resolved in
jammy and now it
The "Call to Hibernate failed: Invalid argument" problem, i try to
resolve it by using a separate swap partition(i used a swap file before
upgrade to 24.04), changing the /etc/default/grub by removing the
resume=xxx and resume_offset=xxx kernel parameter, changing the
Please try adding kernel parameter:
i915.enable_psr=0
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Tags added: noble
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
70 matches
Mail list logo
