[Touch-packages] [Bug 1984067] [NEW] Xorg crash
Public bug reported: All logs should be added automatically but the central issue is: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Backtrace: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55b7984596e9] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f3e6a242520] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x55b7982ee1e9] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x55b7982efc85] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x55b7982f0183] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x55b7982f1183] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x55b7983cfa7d] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x55b7983f9e4c] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x55b7983f2f21] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x55b7983f311e] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x55b798452c60] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x55b798452ee8] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x55b7982e3257] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x55b7982e7524] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f3e6a229d90] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f3e6a229e40] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x55b7982d05f5] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Segmentation fault at address 0x7ffc51d3 Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: Fatal server error: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Caught signal 11 (Segmentation fault). Server aborting Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: Please consult the The X.Org Foundation support Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: #011 at http://wiki.x.org Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: for help. Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information. Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-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..01.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 510.73.05 Sat May 7 05:30:26 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 9 15:22:16 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: acpi-call/1.2.2, 5.15.0-41-generic, x86_64: installed acpi-call/1.2.2, 5.15.0-43-generic, x86_64: installed fwts-efi-runtime-dkms/22.03.00, 5.15.0-41-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms/22.03.00, 5.15.0-43-generic, x86_64: installed (WARNING! Diff between built and installed module!) DpkgLog: Ex
[Touch-packages] [Bug 1984067] Re: Xorg crash
** Attachment added: "xorg.1 file from crashed session" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1984067/+attachment/5607529/+files/Xorg.1.log.old -- 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/1984067 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: All logs should be added automatically but the central issue is: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Backtrace: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55b7984596e9] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f3e6a242520] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x55b7982ee1e9] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x55b7982efc85] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x55b7982f0183] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x55b7982f1183] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x55b7983cfa7d] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x55b7983f9e4c] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x55b7983f2f21] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x55b7983f311e] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x55b798452c60] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x55b798452ee8] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x55b7982e3257] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x55b7982e7524] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f3e6a229d90] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f3e6a229e40] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x55b7982d05f5] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Segmentation fault at address 0x7ffc51d3 Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: Fatal server error: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Caught signal 11 (Segmentation fault). Server aborting Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: Please consult the The X.Org Foundation support Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: #011 at http://wiki.x.org Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: for help. Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information. Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-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..01.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 510.73.05 Sat May 7 05:30:26 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDe
[Touch-packages] [Bug 1239756] Re: apport-bug linux hangs forever at "collecting problem information"
same for me. Bug report is https://bugs.launchpad.net/ubuntu/+source/gdm3/+filebug/2954d34c-7bd9-11ed-8040-40a8f03099c8? ** Changed in: apport (Ubuntu) Status: Incomplete => 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/1239756 Title: apport-bug linux hangs forever at "collecting problem information" Status in apport package in Ubuntu: Confirmed Bug description: also apport-cli ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: apport 2.12.5-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportLog: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Mon Oct 14 12:13:38 2013 InstallationDate: Installed on 2013-09-17 (26 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130917) MarkForUpload: True PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1239756/+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 1239756] Re: apport-bug linux hangs forever at "collecting problem information"
same issue as in https://bugs.launchpad.net/launchpad/+bug/1996471 -- 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/1239756 Title: apport-bug linux hangs forever at "collecting problem information" Status in apport package in Ubuntu: Confirmed Bug description: also apport-cli ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: apport 2.12.5-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportLog: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Mon Oct 14 12:13:38 2013 InstallationDate: Installed on 2013-09-17 (26 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130917) MarkForUpload: True PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1239756/+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 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
still present in 22.10. Newest ubuntu still work against old version of snap. # probe for assertions, must run before udisks2 ACTION=="add", SUBSYSTEM=="block", KERNEL!="loop*", KERNEL!="ram*" \ RUN+="/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/%k" in my rule file -- 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/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 Status in snapd: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Configuration: OS:jammy-live-server20220320-amd64.iso CPU:AMD EPYC 7702 64-Core Processor UEFI Version:D8E119A BMC Version:D8BT19I SSD:Intel 1.60TB NVMe SSD Boot mode:legacy Reproduce Steps: 1.Boot into BIOS and set boot mode to legacy 2.install ubuntu 22.04 on NVMe SSD 3.Check syslog log Current behaviors: syslog shows systemd-udevd errors in Ubuntu 22.04 Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+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 1908814] [NEW] systemd : inconsistencies in man pages
Public bug reported: >From "man systemd-system.conf": When packages need to customize the configuration, they can install configuration snippets in /usr/lib/systemd/*.conf.d/ or /usr/local/lib/systemd/*.conf.d/. The main configuration file is read before any of the configuration directories, and has the lowest precedence; entries in a file in any configuration directory override entries in the single configuration file. Files in the *.conf.d/ configuration subdirectories are sorted by their filename in lexicographic order, regardless of in which of the subdirectories they reside. When multiple files specify the same option, for options which accept just a single value, the entry in the file with the lexicographically latest name takes precedence. For options which accept a list of values, entries are collected as they occur in files sorted lexicographically. However from "man SYSTEMD": DIRECTORIES System unit directories The systemd system manager reads unit configuration from various directories. Packages that want to install unit files shall place them in the directory returned by pkg-config systemd --variable=systemdsystemunitdir. Other directories checked are /usr/local/lib/systemd/system and /lib/systemd/system. User configuration always takes precedence. pkg-config systemd --variable=systemdsystemconfdir returns the path of the system configuration directory. Packages should alter the content of these directories only with the enable and disable commands of the systemctl(1) tool. Full list of directories is provided in systemd.unit(5). User unit directories Similar rules apply for the user unit directories. However, here the XDG Base Directory specification[6] is followed to find units. Applications should place their unit files in the directory returned by pkg-config systemd --variable=systemduserunitdir. Global configuration is done in the directory reported by pkg-config systemd --variable=systemduserconfdir. The enable and disable commands of the systemctl(1) tool can handle both global (i.e. for all users) and private (for one user) enabling/disabling of units. Full list of directories is provided in systemd.unit(5). Obviously, the 2nd one is more precise about directories for configuration files and therefore should be used in all cases. 1st paragraph of doc should link there ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1908814 Title: systemd : inconsistencies in man pages Status in openssh package in Ubuntu: New Bug description: From "man systemd-system.conf": When packages need to customize the configuration, they can install configuration snippets in /usr/lib/systemd/*.conf.d/ or /usr/local/lib/systemd/*.conf.d/. The main configuration file is read before any of the configuration directories, and has the lowest precedence; entries in a file in any configuration directory override entries in the single configuration file. Files in the *.conf.d/ configuration subdirectories are sorted by their filename in lexicographic order, regardless of in which of the subdirectories they reside. When multiple files specify the same option, for options which accept just a single value, the entry in the file with the lexicographically latest name takes precedence. For options which accept a list of values, entries are collected as they occur in files sorted lexicographically. However from "man SYSTEMD": DIRECTORIES System unit directories The systemd system manager reads unit configuration from various directories. Packages that want to install unit files shall place them in the directory returned by pkg-config systemd --variable=systemdsystemunitdir. Other directories checked are /usr/local/lib/systemd/system and /lib/systemd/system. User configuration always takes precedence. pkg-config systemd --variable=systemdsystemconfdir returns the path of the system configuration directory. Packages should alter the content of these directories only with the enable and disable commands of the systemctl(1) tool. Full list of directories is provided in systemd.unit(5). User unit directories Similar rules apply for the user unit directories. However, here the XDG Base Directory specification[6] is followed to find units. Applications should place their unit files in the directory returned by pkg-config systemd --variable=systemduserunitdir. Global configuration is done in the directory reported by pkg-config systemd --variable=systemduserconfdir. The enable and disable commands of the systemctl(1) tool can handle both global (i.e.
[Touch-packages] [Bug 1908818] [NEW] pure packaging of libnss3
Public bug reported:
dpkg -L libnss3
/.
/usr
/usr/lib
/usr/lib/${DEB_HOST_MULTIARCH}
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libnss3.so
/usr/lib/x86_64-linux-gnu/libnssutil3.so
/usr/lib/x86_64-linux-gnu/libsmime3.so
/usr/lib/x86_64-linux-gnu/libssl3.so
/usr/lib/x86_64-linux-gnu/nss
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
/usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
/usr/share
/usr/share/doc
/usr/share/doc/libnss3
/usr/share/doc/libnss3/changelog.Debian.gz
/usr/share/doc/libnss3/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libnss3
/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
as we can see soft links to libraries do nor resolve ${DEB_HOST_MULTIARCH} to
x86_64-linux-gnu
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: libnss3 2:3.55-1ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
Uname: Linux 5.8.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Dec 20 14:36:10 2020
SourcePackage: nss
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: nss (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug groovy third-party-packages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1908818
Title:
pure packaging of libnss3
Status in nss package in Ubuntu:
New
Bug description:
dpkg -L libnss3
/.
/usr
/usr/lib
/usr/lib/${DEB_HOST_MULTIARCH}
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libnss3.so
/usr/lib/x86_64-linux-gnu/libnssutil3.so
/usr/lib/x86_64-linux-gnu/libsmime3.so
/usr/lib/x86_64-linux-gnu/libssl3.so
/usr/lib/x86_64-linux-gnu/nss
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
/usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
/usr/share
/usr/share/doc
/usr/share/doc/libnss3
/usr/share/doc/libnss3/changelog.Debian.gz
/usr/share/doc/libnss3/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libnss3
/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
as we can see soft links to libraries do nor resolve ${DEB_HOST_MULTIARCH} to
x86_64-linux-gnu
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: libnss3 2:3.55-1ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
Uname: Linux 5.8.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Dec 20 14:36:10 2020
SourcePackage: nss
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1908818/+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 1753946] [NEW] verbosity for logrotate
Public bug reported: User has modified /etc/logrotate.conf file such that it includes another file /path/to/own/other_logrotate.conf: ... include /path/to/own/other_logrotate.conf ... Now run under root: logrotate -v /etc/logrotate.conf Expected result: verbosity related to other logrotate file should be very same as if we run other logrotate directly i.e: logrotate -v /etc/logrotate.conf should have same output related to /path/to/own/other_logrotate.conf as if we run directly logrotate -v /path/to/own/other_logrotate.conf Actual result: logrotate -v /etc/logrotate.conf has empty output regarding to /path/to/own/other_logrotate.conf ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: logrotate 3.8.7-2ubuntu2.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 7 10:33:11 2018 InstallationDate: Installed on 2018-01-23 (42 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: logrotate UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.logrotate.conf: 2018-03-07T10:33:03.883000 ** Affects: logrotate (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1753946 Title: verbosity for logrotate Status in logrotate package in Ubuntu: Invalid Bug description: User has modified /etc/logrotate.conf file such that it includes another file /path/to/own/other_logrotate.conf: ... include /path/to/own/other_logrotate.conf ... Now run under root: logrotate -v /etc/logrotate.conf Expected result: verbosity related to other logrotate file should be very same as if we run other logrotate directly i.e: logrotate -v /etc/logrotate.conf should have same output related to /path/to/own/other_logrotate.conf as if we run directly logrotate -v /path/to/own/other_logrotate.conf Actual result: logrotate -v /etc/logrotate.conf has empty output regarding to /path/to/own/other_logrotate.conf ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: logrotate 3.8.7-2ubuntu2.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 7 10:33:11 2018 InstallationDate: Installed on 2018-01-23 (42 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: logrotate UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.logrotate.conf: 2018-03-07T10:33:03.883000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1753946/+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 1753946] Re: verbosity for logrotate
** Changed in: logrotate (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1753946 Title: verbosity for logrotate Status in logrotate package in Ubuntu: Invalid Bug description: User has modified /etc/logrotate.conf file such that it includes another file /path/to/own/other_logrotate.conf: ... include /path/to/own/other_logrotate.conf ... Now run under root: logrotate -v /etc/logrotate.conf Expected result: verbosity related to other logrotate file should be very same as if we run other logrotate directly i.e: logrotate -v /etc/logrotate.conf should have same output related to /path/to/own/other_logrotate.conf as if we run directly logrotate -v /path/to/own/other_logrotate.conf Actual result: logrotate -v /etc/logrotate.conf has empty output regarding to /path/to/own/other_logrotate.conf ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: logrotate 3.8.7-2ubuntu2.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 7 10:33:11 2018 InstallationDate: Installed on 2018-01-23 (42 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: logrotate UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.logrotate.conf: 2018-03-07T10:33:03.883000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1753946/+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 2084963] [NEW] cannot connect a2dp/avrcp profiles after upgrade
Public bug reported: After upgrading to 24.10 my wireless earphones "CX True Wireless" cannot be connected: Oct 19 12:49:30 ice-home bluetoothd[1313]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 00:1B:66:13:E4:48: Connection refused (111) Oct 19 12:49:30 ice-home bluetoothd[1313]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 00:1B:66:13:E4:48: Connection refused (111) Oct 19 12:49:32 ice-home bluetoothd[1313]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 00:1B:66:13:E4:48: Connection refused (111) Only forget+paring from scratch solves the issue ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: bluez 5.77-0ubuntu1 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME CurrentDmesg: [ 9942.120221] Bluetooth: hci0: AOSP extensions version v1.00 [ 9942.120242] Bluetooth: hci0: AOSP quality report is supported Date: Sat Oct 19 12:55:46 2024 InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP Victus by HP Laptop 16-e0xxx ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-8-generic root=UUID=26ede9d0-ad0f-4dd5-8bec-e4dccddbf9c0 ro splash quiet iommu=soft acpi_sleep=s4_nohwsig resume=UUID=3e286b51-cc86-4fea-b6c8-750ef8948ea8 hibernate=nocompress crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to oracular on 2024-10-17 (2 days ago) dmi.bios.date: 08/10/2022 dmi.bios.release: 15.15 dmi.bios.vendor: AMI dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 88EB dmi.board.vendor: HP dmi.board.version: 80.72 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 80.72 dmi.modalias: dmi:bvnAMI:bvrF.15:bd08/10/2022:br15.15:efr80.72:svnHP:pnVictusbyHPLaptop16-e0xxx:pvr:rvnHP:rn88EB:rvr80.72:cvnHP:ct10:cvrChassisVersion:sku4R8D6EA#A2Q: dmi.product.family: 103C_5335M7 HP VICTUS dmi.product.name: Victus by HP Laptop 16-e0xxx dmi.product.sku: 4R8D6EA#A2Q dmi.sys.vendor: HP hciconfig: hci0: Type: Primary Bus: USB BD Address: 34:6F:24:E8:6B:90 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:64570 acl:109 sco:0 events:1845 errors:0 TX bytes:74287 acl:105 sco:0 commands:737 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular -- 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/2084963 Title: cannot connect a2dp/avrcp profiles after upgrade Status in bluez package in Ubuntu: New Bug description: After upgrading to 24.10 my wireless earphones "CX True Wireless" cannot be connected: Oct 19 12:49:30 ice-home bluetoothd[1313]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 00:1B:66:13:E4:48: Connection refused (111) Oct 19 12:49:30 ice-home bluetoothd[1313]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 00:1B:66:13:E4:48: Connection refused (111) Oct 19 12:49:32 ice-home bluetoothd[1313]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 00:1B:66:13:E4:48: Connection refused (111) Only forget+paring from scratch solves the issue ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: bluez 5.77-0ubuntu1 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME CurrentDmesg: [ 9942.120221] Bluetooth: hci0: AOSP extensions version v1.00 [ 9942.120242] Bluetooth: hci0: AOSP quality report is supported Date: Sat Oct 19 12:55:46 2024 InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP Victus by HP Laptop 16-e0xxx ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-8-generic root=UUID=26ede9d0-ad0f-4dd5-8bec-e4dccddbf9c0 ro splash quiet iommu=soft acpi_sleep=s4_nohwsig resume=UUID=3e286b51-cc86-4fea-b6c8-750ef8948ea8 hibernate=nocompress crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to oracular on 2024-10-17 (2 days ago) dmi.bios.date: 08/10/2022 dmi.bios.release: 15.15 dmi.bios.vendor: AMI dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 88EB dmi.board.vendor: HP dmi.board.version: 80.72 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 80.72 dmi.modalias: dmi:bvnAMI:bvrF.15:bd08/10/2022:br15.15:efr80.72:svnHP:pnVictusbyHPLaptop16-e0xxx:pvr:rvnHP:rn88EB:rvr80.72:cvnHP:ct10:cvrChassisVersion:sku4R8D6EA#A2Q: dmi.product.family: 103C_5335M7 HP VICTUS dmi.product.name:
[Touch-packages] [Bug 2084963] Re: cannot connect a2dp/avrcp profiles after upgrade
reinstalled bluez and with purge of previous data: seems old data wasn't converted to new one or smth ** Bug watch added: github.com/bluez/bluez/issues #973 https://github.com/bluez/bluez/issues/973 -- 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/2084963 Title: cannot connect a2dp/avrcp profiles after upgrade Status in bluez package in Ubuntu: New Bug description: After upgrading to 24.10 my wireless earphones "CX True Wireless" cannot be connected: Oct 19 12:49:30 ice-home bluetoothd[1313]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 00:1B:66:13:E4:48: Connection refused (111) Oct 19 12:49:30 ice-home bluetoothd[1313]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 00:1B:66:13:E4:48: Connection refused (111) Oct 19 12:49:32 ice-home bluetoothd[1313]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 00:1B:66:13:E4:48: Connection refused (111) Only forget+paring from scratch solves the issue ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: bluez 5.77-0ubuntu1 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME CurrentDmesg: [ 9942.120221] Bluetooth: hci0: AOSP extensions version v1.00 [ 9942.120242] Bluetooth: hci0: AOSP quality report is supported Date: Sat Oct 19 12:55:46 2024 InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP Victus by HP Laptop 16-e0xxx ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-8-generic root=UUID=26ede9d0-ad0f-4dd5-8bec-e4dccddbf9c0 ro splash quiet iommu=soft acpi_sleep=s4_nohwsig resume=UUID=3e286b51-cc86-4fea-b6c8-750ef8948ea8 hibernate=nocompress crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to oracular on 2024-10-17 (2 days ago) dmi.bios.date: 08/10/2022 dmi.bios.release: 15.15 dmi.bios.vendor: AMI dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 88EB dmi.board.vendor: HP dmi.board.version: 80.72 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 80.72 dmi.modalias: dmi:bvnAMI:bvrF.15:bd08/10/2022:br15.15:efr80.72:svnHP:pnVictusbyHPLaptop16-e0xxx:pvr:rvnHP:rn88EB:rvr80.72:cvnHP:ct10:cvrChassisVersion:sku4R8D6EA#A2Q: dmi.product.family: 103C_5335M7 HP VICTUS dmi.product.name: Victus by HP Laptop 16-e0xxx dmi.product.sku: 4R8D6EA#A2Q dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: 34:6F:24:E8:6B:90 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:64570 acl:109 sco:0 events:1845 errors:0 TX bytes:74287 acl:105 sco:0 commands:737 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2084963/+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 2084963] Re: cannot connect a2dp/avrcp profiles after upgrade
and refuses to work again after reboot of device. Known issue https://github.com/bluez/bluez/issues/973 ? -- 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/2084963 Title: cannot connect a2dp/avrcp profiles after upgrade Status in bluez package in Ubuntu: New Bug description: After upgrading to 24.10 my wireless earphones "CX True Wireless" cannot be connected: Oct 19 12:49:30 ice-home bluetoothd[1313]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 00:1B:66:13:E4:48: Connection refused (111) Oct 19 12:49:30 ice-home bluetoothd[1313]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 00:1B:66:13:E4:48: Connection refused (111) Oct 19 12:49:32 ice-home bluetoothd[1313]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 00:1B:66:13:E4:48: Connection refused (111) Only forget+paring from scratch solves the issue ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: bluez 5.77-0ubuntu1 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME CurrentDmesg: [ 9942.120221] Bluetooth: hci0: AOSP extensions version v1.00 [ 9942.120242] Bluetooth: hci0: AOSP quality report is supported Date: Sat Oct 19 12:55:46 2024 InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP Victus by HP Laptop 16-e0xxx ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-8-generic root=UUID=26ede9d0-ad0f-4dd5-8bec-e4dccddbf9c0 ro splash quiet iommu=soft acpi_sleep=s4_nohwsig resume=UUID=3e286b51-cc86-4fea-b6c8-750ef8948ea8 hibernate=nocompress crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to oracular on 2024-10-17 (2 days ago) dmi.bios.date: 08/10/2022 dmi.bios.release: 15.15 dmi.bios.vendor: AMI dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 88EB dmi.board.vendor: HP dmi.board.version: 80.72 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 80.72 dmi.modalias: dmi:bvnAMI:bvrF.15:bd08/10/2022:br15.15:efr80.72:svnHP:pnVictusbyHPLaptop16-e0xxx:pvr:rvnHP:rn88EB:rvr80.72:cvnHP:ct10:cvrChassisVersion:sku4R8D6EA#A2Q: dmi.product.family: 103C_5335M7 HP VICTUS dmi.product.name: Victus by HP Laptop 16-e0xxx dmi.product.sku: 4R8D6EA#A2Q dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: 34:6F:24:E8:6B:90 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:64570 acl:109 sco:0 events:1845 errors:0 TX bytes:74287 acl:105 sco:0 commands:737 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2084963/+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 2084963] Re: cannot connect a2dp/avrcp profiles after upgrade
any comments? bt session to analyze communication during failed connect ** Attachment added: "bt_session.pcapng" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2084963/+attachment/5833494/+files/bt_session.pcapng -- 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/2084963 Title: cannot connect a2dp/avrcp profiles after upgrade Status in bluez package in Ubuntu: New Bug description: After upgrading to 24.10 my wireless earphones "CX True Wireless" cannot be connected: Oct 19 12:49:30 ice-home bluetoothd[1313]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 00:1B:66:13:E4:48: Connection refused (111) Oct 19 12:49:30 ice-home bluetoothd[1313]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 00:1B:66:13:E4:48: Connection refused (111) Oct 19 12:49:32 ice-home bluetoothd[1313]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 00:1B:66:13:E4:48: Connection refused (111) Only forget+paring from scratch solves the issue ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: bluez 5.77-0ubuntu1 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME CurrentDmesg: [ 9942.120221] Bluetooth: hci0: AOSP extensions version v1.00 [ 9942.120242] Bluetooth: hci0: AOSP quality report is supported Date: Sat Oct 19 12:55:46 2024 InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP Victus by HP Laptop 16-e0xxx ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-8-generic root=UUID=26ede9d0-ad0f-4dd5-8bec-e4dccddbf9c0 ro splash quiet iommu=soft acpi_sleep=s4_nohwsig resume=UUID=3e286b51-cc86-4fea-b6c8-750ef8948ea8 hibernate=nocompress crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to oracular on 2024-10-17 (2 days ago) dmi.bios.date: 08/10/2022 dmi.bios.release: 15.15 dmi.bios.vendor: AMI dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 88EB dmi.board.vendor: HP dmi.board.version: 80.72 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 80.72 dmi.modalias: dmi:bvnAMI:bvrF.15:bd08/10/2022:br15.15:efr80.72:svnHP:pnVictusbyHPLaptop16-e0xxx:pvr:rvnHP:rn88EB:rvr80.72:cvnHP:ct10:cvrChassisVersion:sku4R8D6EA#A2Q: dmi.product.family: 103C_5335M7 HP VICTUS dmi.product.name: Victus by HP Laptop 16-e0xxx dmi.product.sku: 4R8D6EA#A2Q dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: 34:6F:24:E8:6B:90 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:64570 acl:109 sco:0 events:1845 errors:0 TX bytes:74287 acl:105 sco:0 commands:737 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2084963/+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 2087735] [NEW] apt: folder for gpg
Public bug reported: Hello. I'm sick and tired of politics of ubuntu to locate gpg's here and there. For this purpose folder /etc/apt/trusted.gpg.d stands for. And please do not use other directories like /usr/share/keyrings. And let all package providers to use this only directory forever and ever! ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: apt 2.9.8 ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0 Uname: Linux 6.11.0-9-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Nov 9 11:42:48 2024 SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular -- 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/2087735 Title: apt: folder for gpg Status in apt package in Ubuntu: New Bug description: Hello. I'm sick and tired of politics of ubuntu to locate gpg's here and there. For this purpose folder /etc/apt/trusted.gpg.d stands for. And please do not use other directories like /usr/share/keyrings. And let all package providers to use this only directory forever and ever! ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: apt 2.9.8 ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0 Uname: Linux 6.11.0-9-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Nov 9 11:42:48 2024 SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2087735/+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 2081384] Re: bluetooth headphones need reconnect after every reboot
Checked for mine under https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2084963 ii bluez 5.77-0ubuntu2 amd64Bluetooth tools and daemons ii bluez-cups 5.77-0ubuntu1 amd64Bluetooth printer driver for CUPS ii bluez-obexd5.77-0ubuntu1 amd64bluez obex daemon Everything works as expected. After restart of machine BT device is reattachable without pairing -- 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/2081384 Title: bluetooth headphones need reconnect after every reboot Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in bluez source package in Oracular: Confirmed Status in linux source package in Oracular: Confirmed Bug description: This issue seems to be caused by a recent package update in oracular. Every time I reboot my desktop my bluetooth headset will fail to connect until I manually go through forget device -> new pairing. journalctl says: 23:13:44 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111) 23:13:45 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:13:47 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:13:59 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111) 23:13:59 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:14:00 desktop bluetoothd[3274]: No matching connection for device 23:14:04 desktop bluetoothd[3274]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Operation already in progress 23:14:04 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:14:25 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111) 23:14:25 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:14:27 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 80:C3:33:59:89:D6: Connection refused (111) 23:15:46 desktop bluetoothd[3274]: /org/bluez/hci0/dev_80_C3_33_59_89_D6/sep7/fd0: fd(43) ready In dmesg I see lots of: [44738.102583] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [44749.325565] Bluetooth: hci0: ACL packet for unknown connection handle 3837 [44749.496566] Bluetooth: hci0: ACL packet for unknown connection handle 3837 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2081384/+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 2087735] Re: apt: folder for gpg
no, you still have backdoors to do things wrong. Remove unconditionally apt-key and make half of world to do things right! ** Changed in: apt (Ubuntu) Status: Invalid => New -- 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/2087735 Title: apt: folder for gpg Status in apt package in Ubuntu: New Bug description: Hello. I'm sick and tired of politics of ubuntu to locate gpg's here and there. For this purpose folder /etc/apt/trusted.gpg.d stands for. And please do not use other directories like /usr/share/keyrings. And let all package providers to use this only directory forever and ever! ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: apt 2.9.8 ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0 Uname: Linux 6.11.0-9-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Nov 9 11:42:48 2024 SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2087735/+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
