It appears the messages in the bug description are actually status
messages from the kernel, and not bluetoothctl commands. So the UI
design of bluetoothctl is a little misleading. But it makes me think
even more that this is a kernel issue. Also I can't reproduce the
problem here.
Please see comm
This sounds like it's chip-specific. Please run:
lsusb > lsusb.txt
lspci > lspci.txt
dmesg > dmesg.txt
and attach the resulting text files here.
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch
** Changed in: webbrowser-app (Ubuntu)
Assignee: (unassigned) => Asa Mirzaieva (asaly12)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/2044664
Title:
HDMI plu
Public bug reported:
Bluetooth not working, turning on and turning off
[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Discovery started
[bluetooth]# hci0 type 1 discovering off
[bluetooth]# hci0 type 1 discovering on
[bluetooth]# hci0 type 1 discovering off
[bluetooth]#
The size of the resulting initrd is not a firmware package problem but
an initramfs-tools issue.
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-firmware (Ubuntu)
Status: New => Invalid
--
You received this bug notification becau
This bug was fixed in the package util-linux - 2.40.2-1ubuntu1
---
util-linux (2.40.2-1ubuntu1) oracular; urgency=medium
* Merge with Debian unstable (LP: #2072813). Remaining changes:
- Disable brand new feature with --disable-libmount-mountfd-support that
causes inabilit
[Expired for zeromq3 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: zeromq3 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zeromq3 in Ubuntu.
https://bu
** Also affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Also affects: util-linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
** Tags added: server-todo
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/20770
Issue can be reproduced.
[Steps]
1. Flash image genio-classic-desktop-2204-20240322-185 and boot into OS
2. Upgrade to the latest kernek version via command `sudo apt upgrade`
3. Plugt the serial cable for debugging, reboot DUT and append the
"display-hdmi.dtbo" to list_dtbo variable in u-boot to
** Description changed:
Impact
==
+ The Ubuntu Desktop plans to install the sysprof app by default (LP: #2077465)
Some libraries have a build option to enable greater integration with sysprof,
so we should enable that option.
+
+ This is not believed to otherwise have an impact on apps
Public bug reported:
Impact
==
** Affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
** Tags: oracular
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.ne
This bug was fixed in the package software-properties - 0.101
---
software-properties (0.101) oracular; urgency=medium
* Revert "ppa: Cache the launchpad objects across objects"
* Cache Launchpad objects in add-apt-repository --refresh-keys
-- Julian Andres Klode Tue, 20 Aug 2
Public bug reported:
This is filed as a draft to provide early notice to the Ubuntu Release
Team as requested.
It is not yet ready for action since the libdex MIR has not been
approved yet. LP: #2066262
Impact
==
The Ubuntu Desktop team wishes to install the sysprof app in the default Ubuntu
** Changed in: gnome-online-accounts (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/2072782
Title:
Upda
`protontricks` requires an AppArmor profile and is currently broken on
Ubuntu due to this, unless `--no-bwrap` flag is used. Same as Steam, it
uses Steam Runtime which in turn rely on bwrap.
I copied the one from `/etc/apparmor.d/steam` and just adjusted the name
and path to point to `/usr/bin/pro
Hello Lukas,
I am the person who raised the issue with the cloud-init folks about
this difference.
I would not call it a fix, but rather a workaround for a configuration
that behaves differently with systemd on focal version.
Now whether it is a simple issue to be fixed on systemd is another
sto
** Changed in: mpich (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/2071468
Title:
ELF package metadata failure: environment varia
Verification completed on apparmor noble-proposed
$ apt policy apparmor
apparmor:
Installed: 4.0.1really4.0.1-0ubuntu0.24.04.3
Candidate: 4.0.1really4.0.1-0ubuntu0.24.04.3
Version table:
*** 4.0.1really4.0.1-0ubuntu0.24.04.3 100
100 http://archive.ubuntu.com/ubuntu noble-proposed/ma
** Changed in: shadow (Ubuntu)
Status: In Progress => Fix Committed
--
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/2076898
Title:
Numeric name is accepted as valid u
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/2056768
Title:
apparmor="DENIED" operation="open" class="file" profile="rsyslogd"
name="/run/sy
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/rsyslog/+git/rsyslog/+merge/471628
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/2056768
peer=unconfined in most cases is not meant to be any. It is just that
the policy could not distinguish between the different unconfined
processes.
Confined processes were still being blocked by the peer=unconfined rule.
--
You received this bug notification because you are a member of Ubuntu
Tou
** Merge proposal linked:
https://code.launchpad.net/~dgadomski/ubuntu/+source/powermgmt-base/+git/powermgmt-base/+merge/471623
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu.
https://bugs.launchp
I have noticed that a lot of AppArmor policies use peer=unconfined when
they meant *any* peer. I believe this is also the case for bug 2040483.
I see little difference in allowing "signal (receive) peer=unconfined,"
vs "signal (receive)," in abstractions/base, so I proposed
https://gitlab.com/appa
Hey Christian!
thanks a lot for your fast reaction on this report!
>In other words: this looks like normal and expected behaviour to me.
You'll need to add a rule
ok, that makes sense.
>Note that abstractions/base allows signal (receive) peer=unconfined, -
and "unconfined" does not match your p
And once allowing reading the directory, the contents should also be
allowed:
[Sun Sep 1 16:00:46 2024] audit: type=1400 audit(1724157515.788:5238):
apparmor="DENIED" operation="open" class="file" profile="rsyslogd"
name="/run/systemd/sessions/2" pid=1873 comm=72733A6D61696E20513A526567
requested
> comm="apparmor_signal" requested_mask="receive" denied_mask="receive"
signal=kill peer="/home/ubuntu/apparmor_signal_test_wrap.sh"
So you get a denial for receiving a signal from
peer="/home/ubuntu/apparmor_signal_test_wrap.sh" - which is not
surprising because that peer has a profile:
> "/home
** Also affects: apparmor (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/2077413
Title:
apparmor unconfined profile b
The packages are now all built, and passing autopkg tests (the failing
software-properties test is unrelated).
Packages, that are not yet ready:
- atlas (ftbfs)
- s390-tools, s390-tools-signed (not yet uploaded)
- postgresql-16 (superseded by security upload, new upload in the unapproved
queu
I confirm having the same issue on a baremetal x86_amd64 server running
Ubuntu 24.04 LTS (automatic updates on).
syslog gets occasional line pairs like this:
```
2024-08-16T13:25:25.532537+03:00 hostname kernel: __common_interrupt: 5.36 No
irq handler for vector
2024-08-16T13:25:25.542460+03:00
Yes, Lukas, adding "on-link: true" to the static routes in the Netplan
configuration fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2073869
Title:
systemd
This was definitely fixed ages ago
--
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/1966418
Title:
[jammy regression] webkit apps do not display content (yelp, epiphany,
gnom
Hi Sam,
Canonical will take a look at this issue and get back to you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/2044664
Title:
HDMI plugin after boot, but disp
Hello again,
After re-updating my Ubuntu packages, I wonder if I mistakenly used
24.0.5 in the past, because now I'm having the same issue with 24.0.9
and cleaning the cache, node_modules, etc, does not help at all, I'm
having the same issue as before.
Is there somewhere else I should look for ca
Thanks. Those crash reports are from 1-2 years ago so don't look
relevant.
journal.txt seems to show the problem. The system ran out of memory at
Aug 18 10:08:14 but gnome-shell kept running. It was then told to shut
down cleanly by systemd and you can see the clean shutdown a few seconds
later at
36 matches
Mail list logo
