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
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1231178
Title:
Altec Lansing speakers remote control not working
Status in
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884207
Title:
Wifi Enterprice Login Page does not appear at connect
Status
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/927225
Title:
Yukon Optima 88E8059 fails to come up as a network interface
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1696859
Title:
package linux-image-4.10.0-22-generic (not installed) failed to
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1919150
Title:
My keyboard stop working
Status in linux package in Ubuntu:
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1904391
Title:
Touchpad and Keyboard not detectable in the new kernel
Status
Regardless of how the bluetooth device works, enabling unbonded devices
in BlueZ makes a computer vulnerable to CVE-2023-45866. It won't be
enabled by the security team.
Perhaps GNOME or other desktops could become more aware of gaming
controllers with these issues to make pairing easier, without
hi @werdem o/
What bluetooth device are you using?
Your version of BlueZ has a security patch for vulnerability
CVE-2023-45866 which disables support for certain legacy bluetooth
devices.
If your device does not support Classic Bonding, you can re-enable it by
setting `ClassicBondedOnly=false`
=> Won't Fix
** Changed in: bluez (Ubuntu)
Assignee: Nishit Majithia (0xnishit) => Mark Esler (eslerm)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2045931
Title:
ps3 sixasis cont
hi @yudamjoo o/
Please check the end of your `DpkgTerminalLog.txt` file.
To fix CVE-2023-45866 [0] a configuration file
(`/etc/bluetooth/input.conf`) was changed. If there had been edits made
to this file before updating BlueZ, apt will ask what you want to do
with the configuration file. "Y" is
I reviewed protection-domain-mapper as checked into mantic. This shouldn't be
considered a full audit but rather a quick gauge of maintainability.
pd-mapper: [no upstream description]
- CVE History:
- no CVE history
- possible security issues in commit messages
- no security policy
-
I reviewed qrtr 1.0-2 as checked into mantic. This shouldn't be
considered a full audit but rather a quick gauge of maintainability.
qrtr: Userspace reference for net/qrtr in the Linux kernel
- CVE History:
- no CVE history
- no security policy
- CVE-2019-19079 and CVE-2021-29647 affect
Juerg, yes.
The Breaks line of comment 15 used the most recently available version
(<< 20220711.gitdfa29317-0~).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1983409
Title:
\o/ woo!
Thanks everyone who helped get this into Kinetic before feature freeze!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1983409
Title:
Please merge amd64-microcode
The current version of linux-firmware (20220819.git8413c63c-0ubuntu1)
contains a Breaks line with: `amd64-microcode (<= 3.20220411.1ubuntu1)`.
The linux-firmware patch proposed in comment 16 contains a Breaks line
with: `amd64-microcode (<< 3.20220411.1~)`.
The patch in comment 16 works.
Using
@juergh, the amd64-microcode in kinetic proposed could be fixed by using
the control file in
https://launchpad.net/~eslerm/+archive/ubuntu/share3/+sourcepub/13868029/+listing-
archive-extra
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
The conflicts are resolved with patches for amd64-microcode and linux-
firmware here:
https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1983409
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
I am setting this to confirmed and assigning owning teams per
https://wiki.ubuntu.com/UbuntuDevelopment/Merging
Please let me know if I assigned teams incorrectly or if I can do more
work for this merge.
** Changed in: amd64-microcode (Ubuntu)
Status: In Progress => Confirmed
** Changed
** Changed in: amd64-microcode (Ubuntu)
Assignee: Mark Esler (eslerm) => (unassigned)
** Changed in: linux-firmware (Ubuntu)
Assignee: Mark Esler (eslerm) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Please see the proposed diff for the next linux-firmware update:
https://launchpad.net/~eslerm/+archive/ubuntu/share/+sourcepub/13868068/+listing-archive-extra
I was not able to specify [amd64] in the Breaks line, since that broke
build: "error: the Breaks field ... 'linux-firmware' is
@vorlon suggested to use "linux-firmware (<< 20220711.gitdfa29317-0~)"
to make this SRU-proof for the future.
d/control now contains:
```
Breaks: intel-microcode (<< 2), linux-firmware (<< 20220711.gitdfa29317-0~)
Replaces: linux-firmware (<< 20220711.gitdfa29317-0~)
```
Please see the latest
An updated merge is ready for review.
https://launchpad.net/~eslerm/+archive/ubuntu/share2/+sourcepub/13867943/+listing-archive-extra
This package has a d/control with:
```
Source: amd64-microcode
Section: non-free/admin
Priority: standard
Maintainer: Ubuntu Developers
XSBC-Original-Maintainer:
In the above comment I did not apply rule 9 to linux-firmware properly.
Since the next linux-firmware version number is unknown, the
amd64-microcode relationship to linux-firmware will use earlier or
equal to (<=) the current linux-firmware version
Thank you @superm1 and @juergh! I have not made packages outside of
security patches and I immensely appreciate the advice.
Since not everyone who needs linux-firmware wants amd64-micocode, I believe it
should be #9: "Reorg: A and B existed; move some files from A to B; new A does
not require
25 matches
Mail list logo
