[Touch-packages] [Bug 1982441] Re: package python2.7-minimal 2.7.18-1~20.04.3 failed to install/upgrade: installed python2.7-minimal package post-installation script subprocess returned error exit sta
[Expired for python2.7 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: python2.7 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1982441 Title: package python2.7-minimal 2.7.18-1~20.04.3 failed to install/upgrade: installed python2.7-minimal package post-installation script subprocess returned error exit status 139 Status in python2.7 package in Ubuntu: Expired Bug description: idk ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python2.7-minimal 2.7.18-1~20.04.3 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jul 20 19:58:35 2022 DuplicateSignature: package:python2.7-minimal:2.7.18-1~20.04.3 Setting up python2.7-minimal (2.7.18-1~20.04.3) ... Segmentation fault (core dumped) dpkg: error processing package python2.7-minimal (--configure): installed python2.7-minimal package post-installation script subprocess returned error exit status 139 ErrorMessage: installed python2.7-minimal package post-installation script subprocess returned error exit status 139 InstallationDate: Installed on 2022-07-06 (14 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: python2.7 Title: package python2.7-minimal 2.7.18-1~20.04.3 failed to install/upgrade: installed python2.7-minimal package post-installation script subprocess returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1982441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1972939] Re: Jammy tinc incompatibile with older (e.g. Xenial) tinc nodes
(I've opened LP:#1990216 to request that the fix for upstream "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes #18359" be backported to libssl3 in Jammy.) -- 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/1972939 Title: Jammy tinc incompatibile with older (e.g. Xenial) tinc nodes Status in Release Notes for Ubuntu: New Status in openssl package in Ubuntu: New Status in tinc package in Ubuntu: New Bug description: The tinc included in Jammy (1.0.36-2build1 linked with libssl3) cannot connect to tinc nodes running e.g. tinc from Xenial (1.0.26-1). (Tinc from Impish, which is also v1.0.36-2 but is linked to libssl1.1, can connect to these nodes without problems.) The symptom is a log message (on the system running Jammy) during the metadata channel negotiation (with debug level set to 5): Error during initialisation of cipher from tinc_xenial [...] error:0308010C:digital envelope routines::unsupported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1972939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990216] [NEW] backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes" to Jammy
Public bug reported: OpenSSL upstream implemented a fix for their issue #18359 "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes" https://github.com/openssl/openssl/issues/18359 as of libssl3 3.0.4 (and thus it is included in recent libssl3 versions in Kinetic). Could this fix be backported to libssl3 in Jammy? ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- 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/1990216 Title: backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes" to Jammy Status in openssl package in Ubuntu: New Bug description: OpenSSL upstream implemented a fix for their issue #18359 "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes" https://github.com/openssl/openssl/issues/18359 as of libssl3 3.0.4 (and thus it is included in recent libssl3 versions in Kinetic). Could this fix be backported to libssl3 in Jammy? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1990216/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990170] Re: HDMI refresh rate at 4k 144hz cant be set
Thanks for the bug report. This appears to be either a hardware problem or a bug in the Nvidia driver. I think most likely it's due to insufficient HDMI cable bandwidth. Please ensure you are using an HDMI 2.1 certified cable capable of at least 40 Gbit/s. An HDMI 2.0 cable will not be good enough. ** Summary changed: - refresh rate at 4k 144hz cant be set + HDMI refresh rate at 4k 144hz cant be set ** Summary changed: - HDMI refresh rate at 4k 144hz cant be set + HDMI refresh rate at 4K 144Hz can't be set ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-515 (Ubuntu) ** Changed in: nvidia-graphics-drivers-515 (Ubuntu) Status: New => Incomplete -- 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/1990170 Title: HDMI refresh rate at 4K 144Hz can't be set Status in nvidia-graphics-drivers-515 package in Ubuntu: Incomplete Bug description: in the setting,when i set a refresh rate>60Hz, there will be a black screen for about half a minute and the refresh rate is automatically reset to 60Hz. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0d.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: fail CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 19 23:41:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GA102 [GeForce RTX 3080 Ti] [10de:2208] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GA102 [GeForce RTX 3080 Ti] [1458:4081] InstallationDate: Installed on 2022-08-22 (27 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic root=UUID=00c387f2-1035-4d26-a66d-d9bcc66f1b7b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F36e dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36e:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/1990170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)
Nick
#apt-cache policy systemd
systemd:
Installed: 249.11-0ubuntu3.6
Candidate: 249.11-0ubuntu3.6
Version table:
*** 249.11-0ubuntu3.6 500
500 http://ci.archive.ubuntu.com/ubuntu jammy-proposed/main amd64
Packages
100 /var/lib/dpkg/status
249.11-0ubuntu3.4 500
500 http://ci.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
249.11-0ubuntu3 500
500 http://ci.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
#systemctl list-dependencies systemd-pstore.service
systemd-pstore.service
● ├─-.mount
○ ├─modprobe@chromeos_pstore.service
○ ├─modprobe@efi_pstore.service
○ ├─modprobe@mtdpstore.service
○ ├─modprobe@pstore_blk.service
○ ├─modprobe@pstore_zone.service
○ ├─modprobe@ramoops.service
● └─system.slice
#systemctl list-dependencies --reverse modprobe@mtdpstore.service
modprobe@mtdpstore.service
○ └─systemd-pstore.service
#systemd-analyze unit-files systemd-pstore.service
ids: systemd-pstore.service → /etc/systemd/system/systemd-pstore.service
aliases: systemd-pstore.service ← systemd-pstore.service
--
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/1981622
Title:
mtd device must be supplied (device name is empty)
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
In Progress
Status in systemd source package in Jammy:
Fix Committed
Bug description:
[WORKAROUND]
This will NOT fix a system that is not booting, because the "mtd
device must be supplied (device name is empty)" message is not the
cause of failed boots. This work around is only for those who are
annoyed by the error message, but are otherwise not experiencing any
issues.
If you are not able to boot your system, but you see this error
message, please open a separate bug with your journalctl and dmesg
logs.
# cp /{lib,etc}/systemd/system/systemd-pstore.service
# sed -i 's/modprobe@mtdpstore.service //'
/etc/systemd/system/systemd-pstore.service
# systemctl daemon-reload
[Impact]
Due to mtdpstore not being properly configured as a pstore backend,
when systemd-pstore.service tries to load the module, users get the
following error in dmesg:
[ 18.453473] systemd[1]: Starting Load Kernel Module mtdpstore...
[ 18.462685] mtd device must be supplied (device name is empty)
This is a distracting error for users trying to diagnose other system
issues, especially if their system does not boot after a kernel crash
and this is the only message displayed on the console.
[Test Plan]
* Force a kernel crash to populate /sys/fs/pstore, thus causing
systemd-pstore.service to start on the subsequent boot:
# echo 1 > /proc/sys/kernel/sysrq
# echo 1 > /proc/sys/kernel/panic
# echo c > /proc/sysrq-trigger
* When the system reboots, observe the error in dmesg:
# dmesg | grep mtd
[Where problems could occur]
If a system was relying on this pstore backend, and mtdpstore is built
as a module, it is possible for systemd-pstore.service to trigger
before mtdpstore is loaded, causing systemd-pstore to not copy the
contents of /sys/fs/pstore. Note however that before the patched
introduced as a result of bug 1978079, systemd-pstore.service would
not attempt to load *any* kernel modules.
[Original Description]
After updating my 22.04 system (possibly caused by Systemd update).
And now booting, dmesg has two errors:
'mtd device must be supplied (device name is empty)'.
See line 8 and 134 in the included logfile.
The system are booting as it should though, and the system are working
like it should no errors at all.
Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
systemd?
I have an EFI mounted at boot but it isn't used because I have
installed my system in legacy BIOS mode.
Is this maybe the culprit?
I could ignore the message but it isn't nice though.
Regards
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1972939] Re: Jammy tinc incompatibile with older (e.g. Xenial) tinc nodes
On Wed, May 18, 2022 at 15:36:30 -, Nathan Stratton Treadway wrote: > On Wed, May 18, 2022 at 13:37:46 -, Simon Chopin wrote: > > Could you give more details about what happens when using the legacy > > providers? > > The short version is that by enabling the legacy provider and setting > SECLEVEL to 1, I'm able to get past the "digital envelope (With the fixed version of OpenSSL's legacy.so, the SECLEVEL=1 configuration change is no longer needed -- tincd's openssl.cnf only needs to activate the "legacy" provider.) -- 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/1972939 Title: Jammy tinc incompatibile with older (e.g. Xenial) tinc nodes Status in Release Notes for Ubuntu: New Status in openssl package in Ubuntu: New Status in tinc package in Ubuntu: New Bug description: The tinc included in Jammy (1.0.36-2build1 linked with libssl3) cannot connect to tinc nodes running e.g. tinc from Xenial (1.0.26-1). (Tinc from Impish, which is also v1.0.36-2 but is linked to libssl1.1, can connect to these nodes without problems.) The symptom is a log message (on the system running Jammy) during the metadata channel negotiation (with debug level set to 5): Error during initialisation of cipher from tinc_xenial [...] error:0308010C:digital envelope routines::unsupported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1972939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1972939] Re: Jammy tinc incompatibile with older (e.g. Xenial) tinc nodes
On Fri, Aug 05, 2022 at 00:35:32 -, Don wrote: > It appears the issue is resolved in libssl3 3.0.4-1ubuntu1 from kinetic > (in addition to enabling the legacy providers) I installed a Kinetic test environment, and confirmed that I was able to connect to my Xenial tinc (1.0.26-1) instance successfully (with the legacy provider enabled). I noticed that Jammy and Kinetic actually have the same exact tinc package, so I figure the difference in functionality must be in libssl3: Jammy:pool/universe/t/tinc/tinc_1.0.36-2build1_amd64.deb Kinetic: pool/universe/t/tinc/tinc_1.0.36-2build1_amd64.deb I experimented with downgrading the libssl3 package: libssl3 3.0.5-2ubuntu1 (current latest version): worked 3.0.4-1ubuntu1: worked 3.0.3-5ubuntu3: got "Bogus data received from" error message again Further experimentation running tinc with the OPENSSL_MODULES environment variable set confirmed that the tinc connection succeeds if libssl3 3.0.3-5ubuntu3 is installed but the ossl-modules/legacy.so file from 3.0.4-1ubuntu1 is used by the tincd process. Cross-referencing the commit history for legacyprov.c with the the git commit logs for changes between 3.0.3 and .4: https://github.com/openssl/openssl/compare/openssl-3.0.3...openssl-3.0.4 , I found the commit "Fix regression in default key length for Blowfish CFB and OFB ciphers"... which would seem to be the change allows Tinc to work again (since Tinc 1.0.26 uses the Blowfish algorithm for the metadata connection). https://github.com/openssl/openssl/commit/1b8ef23e68b273bb5e59f60df62251153f24768d https://github.com/openssl/openssl/issues/18359 "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes" Finally, going back to the original issue on Jammy: I copied the ossl-modules/legacy.so taken from libssl3 3.0.5-2ubuntu1 over to my Jammy instance and pointed OPENSSL_MODULES to that file (in /etc/default/tinc)... and sure enough that allowed my Jammy Tinc node to connect to the Xenial Tinc node successfully as well ** Bug watch added: github.com/openssl/openssl/issues #18359 https://github.com/openssl/openssl/issues/18359 -- 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/1972939 Title: Jammy tinc incompatibile with older (e.g. Xenial) tinc nodes Status in Release Notes for Ubuntu: New Status in openssl package in Ubuntu: New Status in tinc package in Ubuntu: New Bug description: The tinc included in Jammy (1.0.36-2build1 linked with libssl3) cannot connect to tinc nodes running e.g. tinc from Xenial (1.0.26-1). (Tinc from Impish, which is also v1.0.36-2 but is linked to libssl1.1, can connect to these nodes without problems.) The symptom is a log message (on the system running Jammy) during the metadata channel negotiation (with debug level set to 5): Error during initialisation of cipher from tinc_xenial [...] error:0308010C:digital envelope routines::unsupported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1972939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1980408] Re: Update glib to 2.72.3
There is a regression introduced in the 2.72.3 update so we're going to prepare 2.72.4 for Jammy when it's released. https://gitlab.gnome.org/GNOME/glib/-/issues/2687 ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy ** Tags removed: verification-done verification-done-jammy ** Tags added: verification-failed verification-failed-jammy ** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2687 https://gitlab.gnome.org/GNOME/glib/-/issues/2687 -- 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/1980408 Title: Update glib to 2.72.3 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 2.72 series https://gitlab.gnome.org/GNOME/glib/-/blob/2.72.3/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopgktest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1980408/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966849] Re: gzip exec format error under WSL1
Tested and verified. Note that there is no original TEST CASE, but the original issue is clearly reproducible. Used the following TEST CASE to verify: 1. Installed 22.04 in WSL2 (for performance reasons until everything is updated) 2. sudo apt update && sudo apt upgrade -y 3. Installed my normal working environment (Fish shell, httpie, exa, etc. etc.) 4. Downloaded https://gnu.askapache.com/gzip/gzip-1.12.tar.gz (as a test gzip'd file) 5. tar xvzf gzip-1.12.tar.gz: Succeeded (this is still WSL2) 6. Removed resulting directory 7. Exited Ubuntu/WSL 8. Converted to WSL1 with "wsl --set-version Ubuntu-22.04 1" 9. Restarted Ubuntu-22.04 under WSL1 10. tar xvzf gzip-1.12.tar.gz: Failed with "/usr/bin/gzip: 1: ELF: not found" 11. gunzip gzip-1.12.tar.gz: Failed with "/usr/bin/gunzip: 57: exec: gzip: Exec format error" 12. sudo apt update && sudo apt upgrade -y: No updates 13. Added jammy-proposed to sources (as root) with: cat
[Touch-packages] [Bug 1989599] Re: Random auditd start failures on Ubuntu 20.04 EC2 AMIs
** Description changed: Description:Ubuntu 20.04.5 LTS Release:20.04 linux-image-aws 5.15.0.1019.23~20.04.11 auditd 1:2.8.5-2ubuntu6 - - I am having issues with auditd on Ubuntu 20.04 LTS Ubuntu official AMIs. I have tested this with published AMIs ami-0123376e204addb71 and ami-00bb3d0b5b36e89b8. + I am having issues with auditd on Ubuntu 20.04 LTS Ubuntu official AMIs. + I have tested this with published AMIs ami-0123376e204addb71 and + ami-00bb3d0b5b36e89b8. I am following a process that has worked up to June 20 2022. The process installs and configures the audit package for CIS hardening. The process steps are: • Launch an instance as a base, I’ve used ami-0123376e204addb71 or ami-00bb3d0b5b36e89b8 (official Ubuntu AMIs). • Installed the packages listed below. • Copied the “auditdconf” contents as /etc/audit/auditd.conf • Copied the “auditrules” contents as /etc/audit/rules.d/audit.rules • Edit /etc/default/grub, and set: GRUB_CMDLINE_LINUX="audit=1 selinux=1 audit_backlog_limit=8192" • Run: grub-mkconfig > /boot/grub/grub.cfg • Stopped the instance, and created an AMI. I then launch 10 or 14 instances of this AMI in us-west-2. Most will come up with auditd service running, and all rules loaded. Usually at least two come up broken for unknown reason, with the auditd service reporting an error I cannot understand: ● auditd.service - Security Auditing Service - Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor preset: enabled) - Active: failed (Result: exit-code) since Wed 2022-09-14 15:08:14 UTC; 22min ago -Docs: man:auditd(8) - https://github.com/linux-audit/audit-documentation - Process: 357 ExecStart=/sbin/auditd (code=exited, status=1/FAILURE) + Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor preset: enabled) + Active: failed (Result: exit-code) since Wed 2022-09-14 15:08:14 UTC; 22min ago + Docs: man:auditd(8) + https://github.com/linux-audit/audit-documentation + Process: 357 ExecStart=/sbin/auditd (code=exited, status=1/FAILURE) Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: Starting Security Auditing Service... Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Error receiving audit netlink packet (No buffer space available) Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Error setting audit daemon pid (No buffer space available) Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: Unable to set audit pid, exiting Sep 14 15:08:14 ip-10-210-197-90 auditd[357]: Cannot daemonize (Success) Sep 14 15:08:14 ip-10-210-197-90 auditd[357]: The audit daemon is exiting. Sep 14 15:08:14 ip-10-210-197-90 auditd[382]: The audit daemon is exiting. Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: auditd.service: Control process exited, code=exited, status=1/FAILURE Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: auditd.service: Failed with result 'exit-code'. Sep 14 15:08:14 ip-10-210-197-90 systemd[1]: Failed to start Security Auditing Service. When I launch the above, it is a launch of 10 or so instances from the same AMI, with the same parameters. Matter of fact, the launch is done by requesting X number of instances during the EC2 instance launch I've been trying to solve this for some time, and I've found the only way I can make the instances always start correctly is to remove the kernel "audit_backlog_limit" setting entirely - no value for the parameter works correctly (tried 320, 8192, 16384, 32768). See attachments for the above mentioned files. Thanks. -Alan expected behavior is: * service loaded and active * "auditctl -l" shows list of loaded rules seen behavior: * service dead with errors shown above. * "auditctl -l" reports "No rules". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1989599 Title: Random auditd start failures on Ubuntu 20.04 EC2 AMIs Status in audit package in Ubuntu: New Bug description: Description:Ubuntu 20.04.5 LTS Release:20.04 linux-image-aws 5.15.0.1019.23~20.04.11 auditd 1:2.8.5-2ubuntu6 I am having issues with auditd on Ubuntu 20.04 LTS Ubuntu official AMIs. I have tested this with published AMIs ami-0123376e204addb71 and ami-00bb3d0b5b36e89b8. I am following a process that has worked up to June 20 2022. The process installs and configures the audit package for CIS hardening. The process steps are: • Launch an instance as a base, I’ve used ami-0123376e204addb71 or ami-00bb3d0b5b36e89b8 (official Ubuntu AMIs). • Installed the packages listed below. • Copied the “auditdconf” contents as /etc/audit/auditd.conf • Copied the “auditrules” contents as /etc/audit/rules.d/audit.rules • Edit /etc/default/grub, and set:
[Touch-packages] [Bug 1990064] Re: unconfined profile denies userns_create for chromium based processes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- 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/1990064 Title: unconfined profile denies userns_create for chromium based processes Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: For Ubuntu 22.10, since the last kernel update, i can´t launch any chromium based browser, due to apparmor denying userns_create dmesg shows: apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=21323 comm="steamwebhelper" requested="userns_create" denied="userns_create" This happens for every process which uses a chromium engine, like google chrome itself or in this case steamwebhelper. Might be related to this change?: https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/ not sure if it got merged in this form though.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990187] [NEW] systemd-resolved recommends libnss-resolve in kinetic, pulls it into minimal system where it was explicitly excluded before
Public bug reported: In kinetic, systemd-resolved now Recommends: libnss-resolve, pulling it into the ubuntu-minimal seed. In the past we briefly had libnss-resolve seeded (between xenial and bionic LTSes but not in any LTS) but it was removed because: - it was redundant; /etc/resolv.conf was consistent and correct. - its presence could mask wrong DNS configuration resulting in difficult-to-debug differences in behavior between applications that did use nss_resolved via /etc/nsswitch.conf and those that did not (examples: i386 binaries that could not use nss_resolved because it was not installed; statically-linked go implementations that parsed /etc/resolve.conf directly and did not load NSS modules) This new recommends was noticed specifically because of some broken kinetic container images where /etc/resolv.conf was broken (empty) and *some* applications still worked via nss but others failed by trying to use the DNS protocol directly. (I.e.: 2nd point above) I believe systemd-resolved should drop its recommends on libnss-resolve for Ubuntu. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1990187 Title: systemd-resolved recommends libnss-resolve in kinetic, pulls it into minimal system where it was explicitly excluded before Status in systemd package in Ubuntu: New Bug description: In kinetic, systemd-resolved now Recommends: libnss-resolve, pulling it into the ubuntu-minimal seed. In the past we briefly had libnss-resolve seeded (between xenial and bionic LTSes but not in any LTS) but it was removed because: - it was redundant; /etc/resolv.conf was consistent and correct. - its presence could mask wrong DNS configuration resulting in difficult-to-debug differences in behavior between applications that did use nss_resolved via /etc/nsswitch.conf and those that did not (examples: i386 binaries that could not use nss_resolved because it was not installed; statically-linked go implementations that parsed /etc/resolve.conf directly and did not load NSS modules) This new recommends was noticed specifically because of some broken kinetic container images where /etc/resolv.conf was broken (empty) and *some* applications still worked via nss but others failed by trying to use the DNS protocol directly. (I.e.: 2nd point above) I believe systemd-resolved should drop its recommends on libnss- resolve for Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1464958] Re: chromium-browser does not run in guest account
** No longer affects: google-chrome-beta (Ubuntu) ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1464958 Title: chromium-browser does not run in guest account Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Incomplete Status in lightdm package in Ubuntu: Fix Released Bug description: Description: In guest account, start chromium browser shows nothing. Start with command line shows error: guest-1qFsXl@home:~$ chromium-browser http://www.google.com Check failed: NamespaceUtils::DenySetgroups() This used to work for months and found failed for few weeks. Version: Ubuntu 14.04 LTS chromium-browser43.0.2357.81-0ubuntu0.14.04.1.1 linux-image-3.13.0-54-generic3.13.0-54.91 --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Desktop-Session: 'None' 'None' 'None' DetectedPlugins: DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes Env: 'None' 'None' Load-Avg-1min: 0.28 Load-Processes-Running-Percent: 0.2% MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia Package: chromium-browser 43.0.2357.81-0ubuntu0.14.04.1.1089 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-54-generic root=UUID=85a7733c-fbc4-49bf-84ce-02be4c5ba907 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-54.91-generic 3.13.11-ckt20 Tags: third-party-packages trusty Uname: Linux 3.13.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: H97M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd12/15/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2015-01-14T08:39:14.796369 To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1464958/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867204] Re: /usr/share/apport/whoopsie-upload-all:FileNotFoundError:/usr/share/apport/whoopsie-upload-all@170:collect_info:process_report
** Description changed: + [Impact] + The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu19, the problem page at https://errors.ubuntu.com/problem/7a3912ff155870bdb23500abfa48a21a6cb07171 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. + + There were 1301 crashes reported in the last month for this bug, which + makes it to number 3 of the apport bug list (despite Ubuntu 22.04 + already being fixed and only older releases are still affected). + + [Test Plan] + + Check that the fixed version does not appear on + https://errors.ubuntu.com/problem/3adc63930455e99063ec1f77bf461d975492e9b4. + + [Where problems could occur] + + Worst case - in any part of the bug reporting/collection procedure, + since that is what's changing. + + [Other info] + + Due to the huge amount of broken autopkgtest tests, the diff for the + SRUs are bigger than desired. The individual commits in + https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/ are + probably easier to review. + + * jammy SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=1fa042cc27714c407494b3d6dfd0730bb984f3eb + * focal SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=eaa92037c7dfba621719c6f81fd75f6a09e90881 -- 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/1867204 Title: /usr/share/apport/whoopsie-upload- all:FileNotFoundError:/usr/share/apport/whoopsie-upload- all@170:collect_info:process_report Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Confirmed Bug description: [Impact] The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu19, the problem page at https://errors.ubuntu.com/problem/7a3912ff155870bdb23500abfa48a21a6cb07171 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. There were 1301 crashes reported in the last month for this bug, which makes it to number 3 of the apport bug list (despite Ubuntu 22.04 already being fixed and only older releases are still affected). [Test Plan] Check that the fixed version does not appear on https://errors.ubuntu.com/problem/3adc63930455e99063ec1f77bf461d975492e9b4. [Where problems could occur] Worst case - in any part of the bug reporting/collection procedure, since that is what's changing. [Other info] Due to the huge amount of broken autopkgtest tests, the diff for the SRUs are bigger than desired. The individual commits in https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/ are probably easier to review. * jammy SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=1fa042cc27714c407494b3d6dfd0730bb984f3eb * focal SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=eaa92037c7dfba621719c6f81fd75f6a09e90881 To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1867204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867204] Re: /usr/share/apport/whoopsie-upload-all:FileNotFoundError:/usr/share/apport/whoopsie-upload-all@170:collect_info:process_report
** Changed in: apport (Ubuntu Focal) Status: Fix Committed => Confirmed -- 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/1867204 Title: /usr/share/apport/whoopsie-upload- all:FileNotFoundError:/usr/share/apport/whoopsie-upload- all@170:collect_info:process_report Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Confirmed Bug description: [Impact] The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu19, the problem page at https://errors.ubuntu.com/problem/7a3912ff155870bdb23500abfa48a21a6cb07171 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. There were 1301 crashes reported in the last month for this bug, which makes it to number 3 of the apport bug list (despite Ubuntu 22.04 already being fixed and only older releases are still affected). [Test Plan] Check that the fixed version does not appear on https://errors.ubuntu.com/problem/3adc63930455e99063ec1f77bf461d975492e9b4. [Where problems could occur] Worst case - in any part of the bug reporting/collection procedure, since that is what's changing. [Other info] Due to the huge amount of broken autopkgtest tests, the diff for the SRUs are bigger than desired. The individual commits in https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/ are probably easier to review. * jammy SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=1fa042cc27714c407494b3d6dfd0730bb984f3eb * focal SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=eaa92037c7dfba621719c6f81fd75f6a09e90881 To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1867204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962454] Re: Oops pages show wrong time window in JournalErrors
** Description changed: [Impact] Oops pages show wrong time window in JournalErrors. For example, I just experienced a crash at: Feb 28 17:31:12 And the JournalErrors entries are: Feb 28 17:31:30 - Feb 28 17:31:41 So don't relate to the crash. [Test Plan] 1. Find a recent crash report from a relevant Ubuntu release on https://errors.ubuntu.com/ If you're looking at https://errors.ubuntu.com/problem/SOMETHING then scroll down and pick a relevant instance from the Occurrences list. 2. Now you're on a page starting with https://errors.ubuntu.com/oops/ look at ApportVersion and verify that apport is a recent enough version to contain the proposed fix. If not then go to step 1. 3. Verify the Date field falls within the time range of the JournalErrors entries. Step 3 might fail in the case of there being no system log entries from around the time of the crash. That does not necessarily mean the test plan has failed. Go to step 1 and pick a different crash. Prior to the fix you would almost never find oops pages that would pass the test. After the fix you should find many/most oops pages do pass the test. [Where problems could occur] Worst case - in any part of the bug reporting/collection procedure, since that is what's changing. [Other Info] + + Due to the huge amount of broken autopkgtest tests, the diff for the + SRUs are bigger than desired. The individual commits in + https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/ are + probably easier to review. + + * jammy SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=1fa042cc27714c407494b3d6dfd0730bb984f3eb + * focal SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=eaa92037c7dfba621719c6f81fd75f6a09e90881 ** Also affects: apport (Ubuntu Focal) Importance: Undecided Status: New -- 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/1962454 Title: Oops pages show wrong time window in JournalErrors Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: New Status in apport source package in Jammy: Incomplete Bug description: [Impact] Oops pages show wrong time window in JournalErrors. For example, I just experienced a crash at: Feb 28 17:31:12 And the JournalErrors entries are: Feb 28 17:31:30 - Feb 28 17:31:41 So don't relate to the crash. [Test Plan] 1. Find a recent crash report from a relevant Ubuntu release on https://errors.ubuntu.com/ If you're looking at https://errors.ubuntu.com/problem/SOMETHING then scroll down and pick a relevant instance from the Occurrences list. 2. Now you're on a page starting with https://errors.ubuntu.com/oops/ look at ApportVersion and verify that apport is a recent enough version to contain the proposed fix. If not then go to step 1. 3. Verify the Date field falls within the time range of the JournalErrors entries. Step 3 might fail in the case of there being no system log entries from around the time of the crash. That does not necessarily mean the test plan has failed. Go to step 1 and pick a different crash. Prior to the fix you would almost never find oops pages that would pass the test. After the fix you should find many/most oops pages do pass the test. [Where problems could occur] Worst case - in any part of the bug reporting/collection procedure, since that is what's changing. [Other Info] Due to the huge amount of broken autopkgtest tests, the diff for the SRUs are bigger than desired. The individual commits in https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/ are probably easier to review. * jammy SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=1fa042cc27714c407494b3d6dfd0730bb984f3eb * focal SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=eaa92037c7dfba621719c6f81fd75f6a09e90881 To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1962454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982487] Re: apport fails with PermissionError for dump mode 2 in containers
** Description changed:
[Impact]
Apport will fail for processes with dump mode 2 inside of containers.
[Test plan]
Run following testcase script inside a LXC container:
```
#!/bin/sh
sudo rm -rf /var/crash/* /var/log/apport.log
sudo -u mail sh -c "ping 127.0.0.1 > /dev/null" &
sleep 0.3
killall -11 ping
sleep 0.3
cat /var/log/apport.log
```
apport.log for the affected version:
```
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: called for pid 6449,
signal 11, core limit 0, dump mode 2
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: not creating core for pid
with dump mode of 2
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: Unhandled exception:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 681, in
add_proc_info
self["ExecutablePath"] = _read_proc_link(
File "/usr/lib/python3/dist-packages/apport/report.py", line 92, in
_read_proc_link
return os.readlink(path, dir_fd=dir_fd)
PermissionError: [Errno 13] Permission denied: 'exe'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/share/apport/apport", line 862, in
info.add_proc_info(proc_pid_fd=proc_pid_fd)
File "/usr/lib/python3/dist-packages/apport/report.py", line 686, in
add_proc_info
raise ValueError("not accessible")
ValueError: not accessible
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: pid: 6452, uid: 0, gid: 0,
euid: 8, egid: 8
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: environment:
environ({'LANG': 'C.UTF-8', 'PATH':
'/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin',
'LISTEN_PID': '6452', 'LISTEN_FDS': '1', 'LISTEN_FDNAMES': 'connection',
'INVOCATION_ID': '1352c67b4a21480a9b35db8012dafb42', 'JOURNAL_STREAM':
'8:29587491', 'SYSTEMD_EXEC_PID': '6452'})
```
The apport log should not show a Traceback.
[Where problems could occur]
The apport binary is called by the kernel when a process crashes. Worst
case scenarios include breaking the apport binary and no problem report
is generated any more (or apport uses too much resources). Users will
see problems reports inside the container which cause additional load or
disk usage. The fix is accompanied by a test case (run in autopkgtest).
[Other Info]
The autopkgtest for armhf are run inside a LXC container and some test
cases like test_crash_setuid_drop trigger this bug.
+
+ Due to the huge amount of broken autopkgtest tests, the diff for the
+ SRUs are bigger than desired. The individual commits in
+ https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/ are
+ probably easier to review.
+
+ * jammy SRU:
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=1fa042cc27714c407494b3d6dfd0730bb984f3eb
+ * focal SRU:
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=eaa92037c7dfba621719c6f81fd75f6a09e90881
--
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/1982487
Title:
apport fails with PermissionError for dump mode 2 in containers
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Focal:
New
Status in apport source package in Jammy:
New
Bug description:
[Impact]
Apport will fail for processes with dump mode 2 inside of containers.
[Test plan]
Run following testcase script inside a LXC container:
```
#!/bin/sh
sudo rm -rf /var/crash/* /var/log/apport.log
sudo -u mail sh -c "ping 127.0.0.1 > /dev/null" &
sleep 0.3
killall -11 ping
sleep 0.3
cat /var/log/apport.log
```
apport.log for the affected version:
```
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: called for pid 6449,
signal 11, core limit 0, dump mode 2
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: not creating core for pid
with dump mode of 2
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: Unhandled exception:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 681, in
add_proc_info
self["ExecutablePath"] = _read_proc_link(
File "/usr/lib/python3/dist-packages/apport/report.py", line 92, in
_read_proc_link
return os.readlink(path, dir_fd=dir_fd)
PermissionError: [Errno 13] Permission denied: 'exe'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/share/apport/apport", line 862, in
info.add_proc_info(proc_pid_fd=proc_pid_fd)
File "/usr/lib/python3/dist-packages/apport/report.py", line 686, in
add_proc_info
raise ValueError("not accessible")
ValueError: not accessible
ERROR: apport (pid 6452) Thu Jul 21 12:59:45 2022: pid: 6452, uid: 0, gid: 0,
euid: 8, egid: 8
[Touch-packages] [Bug 1982555] Re: core dump file empty inside container
** Description changed: [Impact] Apport will write an empty core dump file inside of containers. [Test plan] Run following testcase script inside a LXC container: ``` rm -f /var/lib/apport/coredump/* ulimit -c 100 sleep 86400 & killall -3 sleep ``` Apport will write a core dump into /var/lib/apport/coredump, but this core dump is empty: ``` $ stat /var/lib/apport/coredump/core._usr_bin_sleep.* File: /var/lib/apport/coredump/core._usr_bin_sleep.0.44f483a1-e487-44b3-88d1-805d1026f31d.9059.34839819 Size: 0 Blocks: 0 IO Block: 4096 regular empty file Device: fd00h/64768d Inode: 120848663 Links: 1 Access: (0400/-r) Uid: (0/root) Gid: (0/root) Access: 2022-07-22 07:54:48.838682067 + Modify: 2022-07-22 07:54:48.838682067 + Change: 2022-07-22 07:54:48.838682067 + Birth: 2022-07-22 07:54:48.838682067 + ``` This file should not be empty. [Where problems could occur] The apport binary is called by the kernel when a process crashes. Worst case scenarios include breaking the apport binary and no problem report is generated any more (or apport uses too much resources). Users will see problems reports inside the container which cause additional load or disk usage. The fix is accompanied by a test case. [Other Info] The autopkgtest for armhf are run inside a LXC container and the test case test_core_dump_packaged_sigquit triggers this bug. + + Due to the huge amount of broken autopkgtest tests, the diff for the + SRUs are bigger than desired. The individual commits in + https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/ are + probably easier to review. + + * jammy SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=1fa042cc27714c407494b3d6dfd0730bb984f3eb + * focal SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=eaa92037c7dfba621719c6f81fd75f6a09e90881 -- 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/1982555 Title: core dump file empty inside container Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Confirmed Status in apport source package in Jammy: Confirmed Bug description: [Impact] Apport will write an empty core dump file inside of containers. [Test plan] Run following testcase script inside a LXC container: ``` rm -f /var/lib/apport/coredump/* ulimit -c 100 sleep 86400 & killall -3 sleep ``` Apport will write a core dump into /var/lib/apport/coredump, but this core dump is empty: ``` $ stat /var/lib/apport/coredump/core._usr_bin_sleep.* File: /var/lib/apport/coredump/core._usr_bin_sleep.0.44f483a1-e487-44b3-88d1-805d1026f31d.9059.34839819 Size: 0 Blocks: 0 IO Block: 4096 regular empty file Device: fd00h/64768d Inode: 120848663 Links: 1 Access: (0400/-r) Uid: (0/root) Gid: (0/root) Access: 2022-07-22 07:54:48.838682067 + Modify: 2022-07-22 07:54:48.838682067 + Change: 2022-07-22 07:54:48.838682067 + Birth: 2022-07-22 07:54:48.838682067 + ``` This file should not be empty. [Where problems could occur] The apport binary is called by the kernel when a process crashes. Worst case scenarios include breaking the apport binary and no problem report is generated any more (or apport uses too much resources). Users will see problems reports inside the container which cause additional load or disk usage. The fix is accompanied by a test case. [Other Info] The autopkgtest for armhf are run inside a LXC container and the test case test_core_dump_packaged_sigquit triggers this bug. Due to the huge amount of broken autopkgtest tests, the diff for the SRUs are bigger than desired. The individual commits in https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/ are probably easier to review. * jammy SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=1fa042cc27714c407494b3d6dfd0730bb984f3eb * focal SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=eaa92037c7dfba621719c6f81fd75f6a09e90881 To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1982555/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1989467] Re: Several autopkgtest failures on Ubuntu 22.04 and older
** Description changed: [Impact] All autopkgtest fail on Ubuntu 22.04 (jammy) and older: https://autopkgtest.ubuntu.com/packages/apport This leads to not detecting regressions from security updates. [Test Plan] Check that the autopkgtest succeed all architectures (except for i386). [Where problems could occur] The test cases are only part of the apport source package and are not copied in any binary packages. Changes to the test will only affect the package build and test execution. + + [Other info] + + Due to the huge amount of broken autopkgtest tests, the diff for the + SRUs are bigger than desired. The individual commits in + https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/ are + probably easier to review. + + * jammy SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=1fa042cc27714c407494b3d6dfd0730bb984f3eb + * focal SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=eaa92037c7dfba621719c6f81fd75f6a09e90881 [Details] Following test cases fail: * backend_apt_dpkg: ** test_get_dependencies (armhf) ** test_get_source_tree_sandbox (arm64, armhf, ppc64el) ** test_install_old_packages (arm64, armhf, ppc64el) ** test_install_package_from_a_ppa (arm64, armhf, ppc64el) ** test_install_packages_dependencies (arm64, armhf, ppc64el) ** test_install_packages_from_launchpad (arm64, armhf, ppc64el) ** test_install_packages_permanent_sandbox (arm64, armhf, ppc64el) ** test_install_packages_permanent_sandbox_repack (arm64, armhf, ppc64el) ** test_install_packages_unversioned (arm64, armhf, ppc64el) ** test_install_packages_versioned (arm64, armhf, ppc64el) * hookutils: ** test_module_license_evaluation (armhf) * python_crashes: ** test_dbus_service_timeout_running (armhf) ** test_dbus_service_unknown_wrongbus_notrunning (armhf) * report: ** test_add_gdb_info_abort (armhf) ** test_add_gdb_info_script (armhf) ** test_add_zz_parse_segv_details (arm64, armhf, ppc64el, s390x) * signal_crashes: ** test_core_dump_packaged (armhf, ppc64el, s390x) ** test_core_dump_unpackaged (armhf) ** test_core_file_injection (armhf) ** test_crash_system_slice (amd64, ppc64el, s390x) ** test_empty_core_dump (follow-up failure for test_crash_system_slice) ** test_flood_limit (follow-up failure for test_crash_system_slice) ** test_ignore (follow-up failure for test_crash_system_slice) ** test_ignore_sigquit (follow-up failure for test_crash_system_slice) * ui: ** test_run_crash_kernel (arm64, s390x) ** test_run_update_report_different_binary_source (armhf) ** test_run_report_bug_kernel_thread (armhf) * ui_gtk: ** test_kerneloops_nodetails (armhf) -- 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/1989467 Title: Several autopkgtest failures on Ubuntu 22.04 and older Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Triaged Status in apport source package in Jammy: Triaged Bug description: [Impact] All autopkgtest fail on Ubuntu 22.04 (jammy) and older: https://autopkgtest.ubuntu.com/packages/apport This leads to not detecting regressions from security updates. [Test Plan] Check that the autopkgtest succeed all architectures (except for i386). [Where problems could occur] The test cases are only part of the apport source package and are not copied in any binary packages. Changes to the test will only affect the package build and test execution. [Other info] Due to the huge amount of broken autopkgtest tests, the diff for the SRUs are bigger than desired. The individual commits in https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/ are probably easier to review. * jammy SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=1fa042cc27714c407494b3d6dfd0730bb984f3eb * focal SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=eaa92037c7dfba621719c6f81fd75f6a09e90881 [Details] Following test cases fail: * backend_apt_dpkg: ** test_get_dependencies (armhf) ** test_get_source_tree_sandbox (arm64, armhf, ppc64el) ** test_install_old_packages (arm64, armhf, ppc64el) ** test_install_package_from_a_ppa (arm64, armhf, ppc64el) ** test_install_packages_dependencies (arm64, armhf, ppc64el) ** test_install_packages_from_launchpad (arm64, armhf, ppc64el) ** test_install_packages_permanent_sandbox (arm64, armhf, ppc64el) ** test_install_packages_permanent_sandbox_repack (arm64, armhf, ppc64el) ** test_install_packages_unversioned (arm64, armhf, ppc64el) ** test_install_packages_versioned (arm64, armhf, ppc64el) * hookutils: ** test_module_license_evaluation (armhf) * python_crashes: ** test_dbus_service_timeout_running (armhf) **
[Touch-packages] [Bug 1332226] Re: sensible-browser opens a new chromium even if one is already running
I cannot verify that. BROWSER=chromium sensible-browser a & BROWSER=chromium sensible-browser b & gives me two tabs in one Chromium window. Since the report is old, I'm marking it as invalid, but please bump it if still reproducible for you. ** Also affects: sensible-utils (Ubuntu) Importance: Undecided Status: New ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid ** Changed in: sensible-utils (Ubuntu) Status: New => Confirmed ** Changed in: sensible-utils (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sensible-utils in Ubuntu. https://bugs.launchpad.net/bugs/1332226 Title: sensible-browser opens a new chromium even if one is already running Status in chromium-browser package in Ubuntu: Invalid Status in sensible-utils package in Ubuntu: Invalid Bug description: This fails terribly because the new chromium cannot lock the profile and just generally doesn't work well. sensible-browser should be opening a new window in an existing instance of a browser. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sensible-utils 0.0.9 Uname: Linux 3.13.0-031300rc3-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 19 10:50:21 2014 Dependencies: InstallationDate: Installed on 2013-01-14 (521 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64+mac (20121017.3) PackageArchitecture: all SourcePackage: sensible-utils UpgradeStatus: Upgraded to trusty on 2014-04-18 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1332226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990170] [NEW] refresh rate at 4k 144hz cant be set
Public bug reported: in the setting,when i set a refresh rate>60Hz, there will be a black screen for about half a minute and the refresh rate is automatically reset to 60Hz. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0d.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: fail CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 19 23:41:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GA102 [GeForce RTX 3080 Ti] [10de:2208] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GA102 [GeForce RTX 3080 Ti] [1458:4081] InstallationDate: Installed on 2022-08-22 (27 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic root=UUID=00c387f2-1035-4d26-a66d-d9bcc66f1b7b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F36e dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36e:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy resolution 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/1990170 Title: refresh rate at 4k 144hz cant be set Status in xorg package in Ubuntu: New Bug description: in the setting,when i set a refresh rate>60Hz, there will be a black screen for about half a minute and the refresh rate is automatically reset to 60Hz. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0d.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: fail CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 19
[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)
Onuh and David - Please share the output from the following commands:
$ apt-cache policy systemd
$ systemctl list-dependencies systemd-pstore.service
$ systemctl list-dependencies --reverse modprobe@mtdpstore.service
$ systemd-analyze unit-files systemd-pstore.service
--
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/1981622
Title:
mtd device must be supplied (device name is empty)
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
In Progress
Status in systemd source package in Jammy:
Fix Committed
Bug description:
[WORKAROUND]
This will NOT fix a system that is not booting, because the "mtd
device must be supplied (device name is empty)" message is not the
cause of failed boots. This work around is only for those who are
annoyed by the error message, but are otherwise not experiencing any
issues.
If you are not able to boot your system, but you see this error
message, please open a separate bug with your journalctl and dmesg
logs.
# cp /{lib,etc}/systemd/system/systemd-pstore.service
# sed -i 's/modprobe@mtdpstore.service //'
/etc/systemd/system/systemd-pstore.service
# systemctl daemon-reload
[Impact]
Due to mtdpstore not being properly configured as a pstore backend,
when systemd-pstore.service tries to load the module, users get the
following error in dmesg:
[ 18.453473] systemd[1]: Starting Load Kernel Module mtdpstore...
[ 18.462685] mtd device must be supplied (device name is empty)
This is a distracting error for users trying to diagnose other system
issues, especially if their system does not boot after a kernel crash
and this is the only message displayed on the console.
[Test Plan]
* Force a kernel crash to populate /sys/fs/pstore, thus causing
systemd-pstore.service to start on the subsequent boot:
# echo 1 > /proc/sys/kernel/sysrq
# echo 1 > /proc/sys/kernel/panic
# echo c > /proc/sysrq-trigger
* When the system reboots, observe the error in dmesg:
# dmesg | grep mtd
[Where problems could occur]
If a system was relying on this pstore backend, and mtdpstore is built
as a module, it is possible for systemd-pstore.service to trigger
before mtdpstore is loaded, causing systemd-pstore to not copy the
contents of /sys/fs/pstore. Note however that before the patched
introduced as a result of bug 1978079, systemd-pstore.service would
not attempt to load *any* kernel modules.
[Original Description]
After updating my 22.04 system (possibly caused by Systemd update).
And now booting, dmesg has two errors:
'mtd device must be supplied (device name is empty)'.
See line 8 and 134 in the included logfile.
The system are booting as it should though, and the system are working
like it should no errors at all.
Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
systemd?
I have an EFI mounted at boot but it isn't used because I have
installed my system in legacy BIOS mode.
Is this maybe the culprit?
I could ignore the message but it isn't nice though.
Regards
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1974456] Re: regression: apt.postint fails if never previously configured
Reverified for 1.6.17 as per #23 ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1974456 Title: regression: apt.postint fails if never previously configured Status in apt package in Ubuntu: Confirmed Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Released Bug description: [Impact] bootstrapping a system with apt that fixes #1968154 fails in focal and bionic, as they try to execute the config file that is being removed. This is not a problem on updates, only on new installs, so impact is limited to bootstrapping tools that enable -updates, such as mmdebstrap. [Test case] bootstrapping with -updates enabled can easily be tested with mmdebstrap: mmdebstrap -v focal ~/Projects/Ubuntu/Scratch/focal for example, on focal: Setting up apt (2.0.8) ... /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found dpkg: error processing package apt (--configure): installed apt package post-installation script subprocess returned error exit status 127 [Regression potential] We remove 5 lines from the shell postinst script, there could be syntax errors? But then we'd see those during upgrades, so practically none. [Original bug report] #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch: https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0 ...but `apt.postinst` still tries to run it: # create kernel autoremoval blacklist on update if dpkg --compare-versions "$2" lt 0.9.9.3; then /etc/kernel/postinst.d/apt-auto-removal fi If I understand correctly, "$2" is the most-recently-configured- version, and if it's empty `dpkg --compare-versions lt` will evaluate to true. This fails when I'm building a focal (20.04) userspace from scratch: $ dpkg --configure -a [...] Setting up apt (2.0.8) ... /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found dpkg: error processing package apt (--configure): installed apt package post-installation script subprocess returned error exit status 127 It works with apt 2.0.6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1989973] Re: focal: Vim 2:8.1.2269-1ubuntu5.8 failed to build for arm32, makes it uninstallable without explicit version
This bug was fixed in the package vim - 2:8.1.2269-1ubuntu5.9 --- vim (2:8.1.2269-1ubuntu5.9) focal-security; urgency=medium * No-change rebuild to republish missing architecture binaries in the security pocket (LP: #1989973) -- Nishit Majithia Mon, 19 Sep 2022 10:29:57 +0530 ** Changed in: vim (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1989973 Title: focal: Vim 2:8.1.2269-1ubuntu5.8 failed to build for arm32, makes it uninstallable without explicit version Status in vim package in Ubuntu: Fix Released Bug description: In a fresh focal install/container, vim is uninstallable because version 2:8.1.2269-1ubuntu5.8 failed to build for vim, but the `all` packages did succeed. ``` $ docker run -ti --rm arm32v7/ubuntu:focal bash -c 'apt update && apt install vim-tiny' WARNING: The requested image's platform (linux/arm/v7) does not match the detected host platform (linux/amd64) and no specific platform was requested Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [108 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [114 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports focal/main armhf Packages [1227 kB] Get:6 http://ports.ubuntu.com/ubuntu-ports focal/universe armhf Packages [10.9 MB] Get:7 http://ports.ubuntu.com/ubuntu-ports focal/multiverse armhf Packages [141 kB] Get:8 http://ports.ubuntu.com/ubuntu-ports focal/restricted armhf Packages [10.8 kB] Get:9 http://ports.ubuntu.com/ubuntu-ports focal-updates/restricted armhf Packages [16.9 kB] Get:10 http://ports.ubuntu.com/ubuntu-ports focal-updates/universe armhf Packages [996 kB] Get:11 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse armhf Packages [9626 B] Get:12 http://ports.ubuntu.com/ubuntu-ports focal-updates/main armhf Packages [1400 kB] Get:13 http://ports.ubuntu.com/ubuntu-ports focal-backports/universe armhf Packages [27.4 kB] Get:14 http://ports.ubuntu.com/ubuntu-ports focal-backports/main armhf Packages [54.7 kB] Get:15 http://ports.ubuntu.com/ubuntu-ports focal-security/main armhf Packages [1032 kB] Get:16 http://ports.ubuntu.com/ubuntu-ports focal-security/multiverse armhf Packages [4730 B] Get:17 http://ports.ubuntu.com/ubuntu-ports focal-security/universe armhf Packages [698 kB] Get:18 http://ports.ubuntu.com/ubuntu-ports focal-security/restricted armhf Packages [16.6 kB] Fetched 17.2 MB in 8s (2274 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 23 packages can be upgraded. Run 'apt list --upgradable' to see them. Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: vim-tiny : Depends: vim-common (= 2:8.1.2269-1ubuntu5.7) but 2:8.1.2269-1ubuntu5.8 is to be installed E: Unable to correct problems, you have held broken packages. ``` Seems to be due to https://launchpad.net/ubuntu/+source/vim/2:8.1.2269-1ubuntu5.8/+build/24478851 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1989973/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761341] Re: lsb_release crashed with ValueError in (): could not convert string to float: '6.06 LTS'
@mwhudson yes, I am working on the debdiffs and once ready I'll attach
them here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lsb in Ubuntu.
https://bugs.launchpad.net/bugs/1761341
Title:
lsb_release crashed with ValueError in (): could not convert
string to float: '6.06 LTS'
Status in lsb package in Ubuntu:
Fix Released
Status in lsb source package in Bionic:
Confirmed
Status in lsb source package in Focal:
Confirmed
Status in lsb source package in Jammy:
Confirmed
Bug description:
[Description]
In some cases lsb_release script can crash with the following trace :
Traceback (most recent call last):
File "/usr/bin/lsb_release", line 95, in
main()
File "/usr/bin/lsb_release", line 59, in main
distinfo = lsb_release.get_distro_information()
File "/usr/lib/python3/dist-packages/lsb_release.py", line 356, in
get_distro_information
distinfo = guess_debian_release()
File "/usr/lib/python3/dist-packages/lsb_release.py", line 246, in
guess_debian_release
get_distro_info(distinfo['ID'])
File "/usr/lib/python3/dist-packages/lsb_release.py", line 48, in
get_distro_info
RELEASES_ORDER.sort(key=lambda n: float(n[0]))
File "/usr/lib/python3/dist-packages/lsb_release.py", line 48, in
RELEASES_ORDER.sort(key=lambda n: float(n[0]))
ValueError: could not convert string to float: '6.06 LTS
The root cause of this is that function get_distro_info() while parsing
the '/usr/share/distro-info/ubuntu.csv' and expects to find a float at the
beginning of each line, instead it find a string ("6.06 LTS").
There is a fix for this bug upstream:
https://salsa.debian.org/debian/lsb/-/commit/4b36f9d31c00233ea20415542633729ab3799e61
and is already in kinetic.
[Test Case]
The easier way to reproduce this bug is to hack
/usr/share/pyshared/lsb_release.py file
change the get_distro_info definition from
def get_distro_info(origin='Debian'):
to
def get_distro_info(origin='Ubuntu'):
and run
$ lsb_release
Traceback (most recent call last):
File "/usr/bin/lsb_release", line 25, in
import lsb_release
File "/usr/lib/python3/dist-packages/lsb_release.py", line 58, in
get_distro_info()
File "/usr/lib/python3/dist-packages/lsb_release.py", line 48, in
get_distro_info
RELEASES_ORDER.sort(key=lambda n: float(n[0]))
File "/usr/lib/python3/dist-packages/lsb_release.py", line 48, in
RELEASES_ORDER.sort(key=lambda n: float(n[0]))
ValueError: could not convert string to float: '6.06 LTS'
A detailed analysis on how this bug can happen in a real life scenario
can be found in comment #3.
[Regression Potential]
The fix changes the way get_distro_info function parses the csv file and
instead of expecting
a float at the beginning of the line, it now expects a string and isolates
the numerical part.
The regression potential is small and would affect the behavior of
lsb_release executable.
[Other]
Debian bug : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980566
Fix :
https://salsa.debian.org/debian/lsb/-/commit/4b36f9d31c00233ea20415542633729ab3799e61
Affected releases : Jammy, Focal, Bionic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1761341/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1989457] Re: FFE: Enable riscv64 build
Sponsored for kinetic-proposed. Please make sure systemd migrates into the release pocket. ** Changed in: systemd (Ubuntu) Importance: Undecided => Wishlist ** Changed in: systemd (Ubuntu) Status: Triaged => In Progress -- 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/1989457 Title: FFE: Enable riscv64 build Status in systemd package in Ubuntu: In Progress Bug description: The upstream source supports building systemd-boot for the riscv64 architecture. We just haven't enabled it yet in debian/control. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1989457/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1989729] Re: Problem with graphics card
Thanks for the bug report. I can't yet see anything wrong with the machine. Can you describe the problem in more detail, maybe with a video? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1989729 Title: Problem with graphics card Status in Ubuntu: Incomplete Bug description: Hi,Names Hamdaan. I have installed Ubuntu on my PC about 4-5 days ago. At first I didn't seem to notice, But as I used my PC I've been noticing that it seems that my PC's graphics card is not working as efficient as before. But when I read the driver name I got to know that it has not downloaded the correct Driver software , and I don't know how to fix that?. Thanks in advance for answering. IN CASE YOU NEED IT: PC MODEL: Acer Aspire E1-572 MEMORY : 4.0 GiB PROCESSER: Intel® Core™ i5-4200U CPU @ 1.60GHz × 4 OS TYPE : 64x ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 15 17:46:25 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Haswell-ULT Integrated Graphics Controller [1025:0775] InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Aspire E1-572 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=fcb232d7-2139-4cee-b321-7332acc47658 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2014 dmi.bios.release: 2.17 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HW dmi.board.vendor: Acer dmi.board.version: V2.17 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.17:bd09/02/2014:br2.17:efr2.17:svnAcer:pnAspireE1-572:pvrV2.17:rvnAcer:rnEA50_HW:rvrV2.17:cvnAcer:ct10:cvrChassisVersion:skuAspireE1-572_0775_V2.17: dmi.product.family: SharkBay System dmi.product.name: Aspire E1-572 dmi.product.sku: Aspire E1-572_0775_V2.17 dmi.product.version: V2.17 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1989729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990113] Re: Increase timeout on test doc-check for RISC-V
The package built successfully here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13962373/+listing- archive-extra ** Attachment added: "debdiff" https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1990113/+attachment/5616956/+files/debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1990113 Title: Increase timeout on test doc-check for RISC-V Status in json-glib package in Ubuntu: New Bug description: The doc-check test fails on RISC-V because it is a very slow architecture: fix this by increasing the timeout on this specific test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1990113/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915471] Re: FFe: base-files update MOTD help text formatting
As this is indeed an FFe from previous cycles, I'll close it down as Invalid. ** Changed in: base-files (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1915471 Title: FFe: base-files update MOTD help text formatting Status in base-files package in Ubuntu: Invalid Bug description: [Description] Provide updated messaging text and formatting for MOTD 10-help-text related to text message organization, layout and verbiage. Minor improvements for cleaner formatting of messages greeting ssh attaches to a machine. [Rationale] MOTD messaging is one of the primary means of communicating to Ubuntu server customers, we wish to improve the layout and messaging a bit to polish that experience a little bit for Hirsute and later. [Timeline] Current specs are in flight for base-files and update-notifier MOTD changes expect that we have final usability doc updates there by beginning of March. [Risks] Low risk as these changes are text-only formatting and potentially color-control characters. Potentially errors in any new partsdir files in /etc/update-motd.d/ are trapped and the offending text or invalid shell logic is geneally trapped and ignored without affecting other MOTD text To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1915471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990113] [NEW] Increase timeout on test doc-check for RISC-V
Public bug reported: The doc-check test fails on RISC-V because it is a very slow architecture: fix this by increasing the timeout on this specific test. ** Affects: json-glib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1990113 Title: Increase timeout on test doc-check for RISC-V Status in json-glib package in Ubuntu: New Bug description: The doc-check test fails on RISC-V because it is a very slow architecture: fix this by increasing the timeout on this specific test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1990113/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990081] Re: Computer continually sends audio to bluetooth headphones
PipeWire is not supported in 22.04, but it will be supported in 22.10. Do you still experience this bug without PipeWire in 22.04? ** Tags added: jammy ** Package changed: bluez (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: a2dp -- 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/1990081 Title: Computer continually sends audio to bluetooth headphones Status in Ubuntu: Incomplete Bug description: Pipewire/BlueZ is constantly sending audio data to Bluetooth headphones even when no audio is playing. This causes three problems: 1. Prevents any other device sending audio to the headphones when Bluetooth multipoint connection is use. 2. Additional battery drain on a laptop due to unnecessary Bluetooth traffic. 3. Additional battery drain on the headphones for the same reason. The first problem is the primary reason for creating this bug report, it can prevent the headphones from being used with two devices simultaneously (e.g. computer and mobile phone) when only one device plays audio at any one time (a so-called 'multipoint connection'). The issue can be easily diagnosed by running 'sudo btmon' and noticing that very similar packets are continually being transmitted, even when no audio is being played, likely representing silence encoded as Bluetooth A2DP packets. When audio is played via the computer, these packets look like encoded data (the audio encoded as Bluetooth A2DP packets). Sometimes this does not cause an issue, it all depends on what connection the headphones deem as the primary connection, if the computer is deemed the priority then the silence being continually transmitted prevents audio from the other connected device being heard. If the other connected device is deemed the priority then its audio will be heard instead and the silence from the computer ignored. Note that Android works properly in this aspect: when no audio is playing, it does not continually send audio packets to the headphones allowing the other device to play audio correctly, irrespective of which device is deemed the priority by the headphones. $ lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 richard@richard-dell:~ $ sudo apt-cache policy bluez bluez: Installed: 5.64-0ubuntu1 Candidate: 5.64-0ubuntu1 Version table: *** 5.64-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status richard@richard-dell:~ $ sudo apt-cache policy pipewire-media-session pipewire-media-session: Installed: 0.4.1.r11.ga870086-2~ubuntu22.04 Candidate: 0.4.1.r11.ga870086-2~ubuntu22.04 Version table: *** 0.4.1.r11.ga870086-2~ubuntu22.04 500 500 https://ppa.launchpadcontent.net/pipewire-debian/pipewire-upstream/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 0.4.1-2ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages richard@richard-dell:~ $ sudo apt-cache policy pipewire-pulse pipewire-pulse: Installed: 0.3.58-1~ubuntu22.04 Candidate: 0.3.58-1~ubuntu22.04 Version table: *** 0.3.58-1~ubuntu22.04 500 500 https://ppa.launchpadcontent.net/pipewire-debian/pipewire-upstream/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 0.3.48-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages richard@richard-dell:~ $ sudo apt-cache policy pipewire-audio-client-libraries pipewire-audio-client-libraries: Installed: (none) Candidate: 0.3.58-1~ubuntu22.04 Version table: 0.3.58-1~ubuntu22.04 500 500 https://ppa.launchpadcontent.net/pipewire-debian/pipewire-upstream/ubuntu jammy/main amd64 Packages 500 https://ppa.launchpadcontent.net/pipewire-debian/pipewire-upstream/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status 0.3.48-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages $ bluetoothctl info Device 80:C7:55:FB:B1:4E (public) Name: RB-M700B Alias: RB-M700B Class: 0x00240404 Icon: audio-headset Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Vendor specific (---0099-aabbccddeeff) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Advanced Audio Distribu.. (110d--1000-8000-00805f9b34fb) UUID: A/V Remote Control
