> Was it it more than a red line in systemctl status output? Does it
have annoying logging behaviour or break some other service if it isn't
running?
Red lines and an avoidable boot delay while trying to restart and
failing a bunch of times.
--
You received this bug notification because you are
** 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 Kernel
Packages, which is subscribed to qrtr in Ubuntu.
https://bugs.launchpad.net/bugs/2062667
Title:
Fails on (and should
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
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
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 Kernel
Packages, which is subscribed to qrtr in Ubuntu.
https://bugs.launchpad.net/bugs/2062667
Title:
Fails on (and should be removed from) raspi
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 Kernel
Packages, which is subscribed to qrtr in
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
This impacts all arm64 installs, not just raspberry pi.
The MIR for qrtr and protection-domain-mapper [0] was requested late in
the Mantic cycle and was only approved by Security since it was promised
to only be used for x13s hardware enablement. Hopefully Qualcomm IPC is
only enabled for x13s
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/2062667
** Tags added: iso-testing
--
You received this bug notification because you are a member of Kernel
Packages, which
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qrtr (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to qrtr in Ubuntu.
https://bugs.launchpad.net/bugs/2062667
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: protection-domain-mapper (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to qrtr in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to qrtr in Ubuntu.
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to qrtr in Ubuntu.
https://bugs.launchpad.net/bugs/2062667
Title:
Fails on (and should be removed from)
13 matches
Mail list logo
