[Touch-packages] [Bug 2045931] Re: ps3 sixasis controller request pin to connect to bt
This sounds like it might be a feature and the bug was that previous versions DIDN'T ask. Try entering PIN: ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/2045931 Title: ps3 sixasis controller request pin to connect to bt Status in bluez package in Ubuntu: Incomplete Bug description: Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+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 2045931] Re: ps3 sixasis controller request pin to connect to bt
** Tags added: jammy regression-update ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Nishit Majithia (0xnishit) -- 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/2045931 Title: ps3 sixasis controller request pin to connect to bt Status in bluez package in Ubuntu: Incomplete Bug description: Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+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 2045855] Re: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file on stdin at conffile prompt
It looks like the problem was just no response provided to: Configuration file '/etc/bluetooth/input.conf' ==> File on system created by you or by a script. ==> File also in package provided by package maintainer. 어떻게 하시겠습니까? 다음 중에 하나를 선택할 수 있습니다: Y 또는 I : 패키지 관리자의 버전을 설치합니다 N 또는 O : 현재 설치된 버전을 유지합니다 D : 버전 간의 차이점을 표시합니다 Z : 프로세스를 백그라운드로 하고 상황을 알아봅니다 기본값으로 현재 버전을 그대로 유지합니다. *** input.conf (Y/I/N/O/D/Z) [기본값=N] ? Was the user ever aware of the prompt or was it hidden during upgrade? ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/2045855 Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file on stdin at conffile prompt Status in bluez package in Ubuntu: Incomplete Bug description: I did not recognized the error. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: bluez:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Dec 7 15:44:57 2023 ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2021-01-30 (1040 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. OptiPlex 7010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=1aa27b2f-8d22-4b4e-931f-bd8e304ed0d4 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.12, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: bluez Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: Upgraded to jammy on 2023-03-28 (253 days ago) dmi.bios.date: 03/25/2013 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0GY6Y8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd03/25/2013:br4.6:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0GY6Y8:rvrA00:cvnDellInc.:ct6:cvr:sku: dmi.product.name: OptiPlex 7010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:1A:7D:DA:71:03 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:1332 acl:0 sco:0 events:84 errors:0 TX bytes:3786 acl:0 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2020-04-03T15:47:01 mtime.conffile..etc.bluetooth.main.conf: 2020-02-26T18:57:50 mtime.conffile..etc.bluetooth.network.conf: 2012-12-25T02:46:55 mtime.conffile..etc.dbus-1.system.d.bluetooth.conf: 2022-03-24T15:30:38 mtime.conffile..etc.init.d.bluetooth: 2020-02-26T18:57:50 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045855/+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 597056] Re: HP Touchsmart 600-1005xt No sound from Internal Speakers
FWIW, I installed Lubuntu 23.10 on my old HP TouchSmart 600. Because of this audio problem, I've been using bluetooth speakers. Last week, I plugged in some old computer speakers via the 3.5mm audio out. For a short instance, sound actually came out of the internal speakers. Eventually, sound came out of the external speakers, and no longer the internal. I think Lubuntu uses PulseAudio by default, but ALSA seems to also be installed. I don't know why the internal speakers suddenly worked then stopped, and I haven't figured out how to reproduce it. Either way, bt and audio out still works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/597056 Title: HP Touchsmart 600-1005xt No sound from Internal Speakers Status in alsa-driver package in Ubuntu: Expired Bug description: Found there is no internal speaker output from hp touchsmart 600-1005xt in all releases of Ubuntu 8.04 to 10.04LTS (64bit) with updated alsa-base (on 1.0.22.1 in Lucid now). All outputs & inputs work except the Internal speakers. I Checked all alsamixer levels, I have also noticed the nodeid's it seem to be mapped 0x15 - 0x0d - 0x03 (21 - 13 - 3) for internal speakers which gives same results (no audio) in osx Applehda.kext. The Headphone nodeid's of 0x14 - 0x0c - 0x02 (20 - 12 - 2) seem to work in all Ubuntu Dists & OSx as well. Windows 7 Driver everything works of course. Is Bios sending wrong pin configs for internal audio? if so what would the resolution be? here is my alsa-information from alsa-info.sh attached, My only guess is the pin configs how do you change them in alsa driver & how could I get the correct ones if the bios was sending wrong pathmaps? I should also note I've tried most of the model flags in alsa-base.conf in the alc888 documentation & rebooted countless times, model=auto shows the internal speaker but sound comes out headphones plug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/597056/+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 2045668] Re: Please merge dbus 1.14.10-3 (main) from Debian unstable
usr-is-merged should probably be in main, it serves as an indicator that the system is already using the usrmerge layout. From: https://lists.debian.org/debian-ctte/2022/07/msg00019.html The usrmerge package has been updated to pick up a few fixes from Ubuntu, and most importantly to provide a new lightweight metapackage, usr-is-merged, that can only be installed on merged-usr systems, to provide a way for installers to avoid the additional dependencies of usrmerge when they set up the filesystem correctly by themselves (eg: debootstrap), and for users who already completed the transition. It also gained a flag file that stops the package from updating the system, clearly marked as making the system unsupported. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/2045668 Title: Please merge dbus 1.14.10-3 (main) from Debian unstable Status in dbus package in Ubuntu: In Progress Bug description: 1.14.10-3 Published in sid-release on 2023-10-30 dbus (1.14.10-3) unstable; urgency=medium * d/control: dbus Depends on usr-is-merged (>= 38~). Non-merged /usr has been unsupported since Debian 12, as per Technical Committee resolutions #978636 and #994388 (please see the Debian 12 release notes for details). The version of usr-is-merged shipped in Debian 12 had an undocumented opt-out mechanism intended for use on buildds and QA systems targeting Debian 12 (piuparts, reproducible-builds, autopkgtest and similar), to ensure that the upgrade path from Debian 11 to 12 will continue to work and continue to undergo automated tests. That opt-out is no longer applicable or available in trixie/sid, and was removed in usrmerge version 38. Since version 1.14.10-2, dbus ships its systemd units in /usr/lib/systemd/system, as part of the distro-wide transition away from making use of "aliased" paths. This is entirely valid on merged-/usr systems, but will no longer work in the unsupported filesystem layout with non-merged /usr, because for historical reasons, current versions of systemd on non-merged-/usr systems will only read units from /lib/systemd/system. In the case of dbus, the symptom when this assumption is broken is particularly bad (various key system services will not start, with long delays during boot, login and shutdown), so let's hold back this upgrade on unsupported non-merged-/usr systems until they have completed the switch to merged-/usr and can install usr-is-merged (>= 38~). (Closes: #1054650) -- Simon McVittie Mon, 30 Oct 2023 11:51:35 + 1.14.10-2 Superseded in sid-release on 2023-10-30 dbus (1.14.10-2) unstable; urgency=low * Backport packaging changes from experimental: - Install systemd system units into /usr/lib/systemd/system. This was allowed by TC resolution #1053901. The shared library is still in /lib, for now. Build-depend on debhelper 13.11.6~ to ensure that the units are still picked up by dh_installsystemd. - Build-depend on pkgconf rather than pkg-config - dbus-x11: Don't copy XDG_SEAT_PATH, XDG_SESSION_PATH to activation environment. These variables are specific to a single login session. * d/copyright: Drop unused entry for pkg.m4. This is no longer included in the upstream source release since 1.14.6. * d/dbus-tests.lintian-overrides: Drop unused overrides. Lintian no longer flags our RUNPATH as problematic. -- Simon McVittie Wed, 25 Oct 2023 15:56:36 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2045668/+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 1664352] Re: dhclient-script doesn't use configured metric for rfc3442 classless routes
This bug was fixed in the package isc-dhcp - 4.4.3-P1-4ubuntu1
---
isc-dhcp (4.4.3-P1-4ubuntu1) noble; urgency=medium
* Merge from Debian unstable, remaining changes:
- Ubuntu patches:
+ Give-an-example-for-subnet-mask-in-dhcpd.conf.patch
+ dhclient-fix-backoff
+ revert-next-server
+ multi-ip-addr-per-if
+ dhclient-safer-timeout
+ onetry_retry_after_initial_success
+ Add InfiniBand support:
- dhcp-lpf-ib.patch
- dhcp-improved-xid.patch
- dhcp-gpxe-cid.patch
- dhcp-improved-xid-correct-byte-order.patch
+ dhcp-4.2.4-dhclient-options-changed.patch
+ ubuntu-dhcpd-conf.patch
+ dhclient-write-pidfile-earlier.patch: Write pidfile before informing
parent of success.
+ bind-outdated-config.guess.patch: run autoreconf in the bind directory.
- Drop isc-dhcp-server/new_auth_behavior question from high to medium
- Apport hook for isc-dhcp-client and isc-dhcp-server.
- Add enforcing AppArmor profile for DHCP client and server
- Increase the timeout to 300 seconds for dhclient.conf (following the
default added by dhclient-safer-timeout).
- Separate default file for isc-dhcp-relay6.
- Create user/group dhcpd and make isc-dhcp-server depend on adduser.
- Create /etc/dhcp/ddns-keys/ for DDNS updates.
- Sanitize environment in dhclient-script.linux.
- Add systemd units for -server and -relay.
+ If /etc/ltsp/dhcpd.conf exists, use that instead of
/etc/dhcp/dhcpd.conf.
- isc-dhcp-server: Suggest policycoreutils instead of recommending it.
- ipv6: wait for duplicate address detection to finish. LP #1633479
- Ship dhcp exit hook to push DNS information to resolved. LP #1889068
- Stop building the udeb on request.
- debian/rules: Build with -O2 instead on -O3 on ppc64el
- debian/rules: build with -fno-strict-aliasing.
- Disable make_resolv_conf() if systemd-resolved is in use.
- debian/control: add Pre-Depends: ${misc:Pre-Depends} for
init-system-helpers.
- debian/apparmor/sbin.dhclient: Allow disabling dhclient hooks.
- Do not build with DH_VERBOSE=1
* Dropped changes, included in Debian:
- Ship keama, the KEA Migration Assistant in a new isc-dhcp-keama binary
package. (LP: #2020086)
* Refresh patches (using gbp pq)
* debian/control: Drop libcap-dev build dependency (no change in diffoscope).
* Use /run/dhcp-server6 for isc-dhcp-server6 service.
Thanks to Jason Penney (LP: #1543799)
* debian/rfc3442-classless-routes.linux: Use configured metric.
Thanks to Tom Carroll (LP: #1664352)
* autopkgtest: Use setup logic from isc-dhcp-server.service
isc-dhcp (4.4.3-P1-4) unstable; urgency=low
[ Athos Ribeiro ]
* d/p/adjust-keama-tests.patch: do not rely on endianess (Closes: #1054077)
isc-dhcp (4.4.3-P1-3) unstable; urgency=low
[ Athos Ribeiro ]
* Ship keama in a new isc-dhcp-keama binary package (Closes: #1036277)
* Add DEP8 tests for keama
* d/p/adjust-keama-tests.patch: adjust keama tests
* d/rules: make keama tests fail on error messages
[ Santiago Ruano Rincón ]
* Make dhclient-script exits with error when it is not able to write in the
temporary file. Patch by Johannes Weißl
(Closes: #982894)
* Import debian/patches/0013-DHCPv6-over-PPP-support-626514.patch
(Closes: #1015809)
* Enable ARM builds in salsa-ci.yml
* Bump Standards-Version to 4.6.2. No changes needed
* Remove obsolete dependencies on lsb-base and policykit-1. Replace with
polkitd
* Fix assignment of dpkg-architecture variables in d/rules
* Remove the --parallel argument from the call to dh on d/rules
-- Benjamin Drung Mon, 27 Nov 2023 14:04:49 +0100
** Changed in: isc-dhcp (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1664352
Title:
dhclient-script doesn't use configured metric for rfc3442 classless
routes
Status in isc-dhcp package in Ubuntu:
Fix Released
Status in isc-dhcp package in Debian:
New
Bug description:
lsb_release -rd
Description: Ubuntu 16.04.2 LTS
Release: 16.04
apt-cache policy isc-dhcp-client
isc-dhcp-client:
Installed: 4.3.3-5ubuntu12.6
Candidate: 4.3.3-5ubuntu12.6
Version table:
*** 4.3.3-5ubuntu12.6 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
100 /var/lib/dpkg/status
4.3.3-5ubuntu12 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
If the metric option is set in interfaces(5), dhclient is executed
with the variable IF_METRIC set to the configured administrative
metric. The exit-hook rfc3442-classless-routes doesn't use the
variable; thus, a multi-interface box will experience a race condition
if multiple interfaces are
[Touch-packages] [Bug 1543799] Re: isc-dhcp-server & isc-dhcp-server6 systemd service units use the same RuntimeDirectory leading to loss of pid files
This bug was fixed in the package isc-dhcp - 4.4.3-P1-4ubuntu1
---
isc-dhcp (4.4.3-P1-4ubuntu1) noble; urgency=medium
* Merge from Debian unstable, remaining changes:
- Ubuntu patches:
+ Give-an-example-for-subnet-mask-in-dhcpd.conf.patch
+ dhclient-fix-backoff
+ revert-next-server
+ multi-ip-addr-per-if
+ dhclient-safer-timeout
+ onetry_retry_after_initial_success
+ Add InfiniBand support:
- dhcp-lpf-ib.patch
- dhcp-improved-xid.patch
- dhcp-gpxe-cid.patch
- dhcp-improved-xid-correct-byte-order.patch
+ dhcp-4.2.4-dhclient-options-changed.patch
+ ubuntu-dhcpd-conf.patch
+ dhclient-write-pidfile-earlier.patch: Write pidfile before informing
parent of success.
+ bind-outdated-config.guess.patch: run autoreconf in the bind directory.
- Drop isc-dhcp-server/new_auth_behavior question from high to medium
- Apport hook for isc-dhcp-client and isc-dhcp-server.
- Add enforcing AppArmor profile for DHCP client and server
- Increase the timeout to 300 seconds for dhclient.conf (following the
default added by dhclient-safer-timeout).
- Separate default file for isc-dhcp-relay6.
- Create user/group dhcpd and make isc-dhcp-server depend on adduser.
- Create /etc/dhcp/ddns-keys/ for DDNS updates.
- Sanitize environment in dhclient-script.linux.
- Add systemd units for -server and -relay.
+ If /etc/ltsp/dhcpd.conf exists, use that instead of
/etc/dhcp/dhcpd.conf.
- isc-dhcp-server: Suggest policycoreutils instead of recommending it.
- ipv6: wait for duplicate address detection to finish. LP #1633479
- Ship dhcp exit hook to push DNS information to resolved. LP #1889068
- Stop building the udeb on request.
- debian/rules: Build with -O2 instead on -O3 on ppc64el
- debian/rules: build with -fno-strict-aliasing.
- Disable make_resolv_conf() if systemd-resolved is in use.
- debian/control: add Pre-Depends: ${misc:Pre-Depends} for
init-system-helpers.
- debian/apparmor/sbin.dhclient: Allow disabling dhclient hooks.
- Do not build with DH_VERBOSE=1
* Dropped changes, included in Debian:
- Ship keama, the KEA Migration Assistant in a new isc-dhcp-keama binary
package. (LP: #2020086)
* Refresh patches (using gbp pq)
* debian/control: Drop libcap-dev build dependency (no change in diffoscope).
* Use /run/dhcp-server6 for isc-dhcp-server6 service.
Thanks to Jason Penney (LP: #1543799)
* debian/rfc3442-classless-routes.linux: Use configured metric.
Thanks to Tom Carroll (LP: #1664352)
* autopkgtest: Use setup logic from isc-dhcp-server.service
isc-dhcp (4.4.3-P1-4) unstable; urgency=low
[ Athos Ribeiro ]
* d/p/adjust-keama-tests.patch: do not rely on endianess (Closes: #1054077)
isc-dhcp (4.4.3-P1-3) unstable; urgency=low
[ Athos Ribeiro ]
* Ship keama in a new isc-dhcp-keama binary package (Closes: #1036277)
* Add DEP8 tests for keama
* d/p/adjust-keama-tests.patch: adjust keama tests
* d/rules: make keama tests fail on error messages
[ Santiago Ruano Rincón ]
* Make dhclient-script exits with error when it is not able to write in the
temporary file. Patch by Johannes Weißl
(Closes: #982894)
* Import debian/patches/0013-DHCPv6-over-PPP-support-626514.patch
(Closes: #1015809)
* Enable ARM builds in salsa-ci.yml
* Bump Standards-Version to 4.6.2. No changes needed
* Remove obsolete dependencies on lsb-base and policykit-1. Replace with
polkitd
* Fix assignment of dpkg-architecture variables in d/rules
* Remove the --parallel argument from the call to dh on d/rules
-- Benjamin Drung Mon, 27 Nov 2023 14:04:49 +0100
** Changed in: isc-dhcp (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1543799
Title:
isc-dhcp-server & isc-dhcp-server6 systemd service units use the same
RuntimeDirectory leading to loss of pid files
Status in isc-dhcp package in Ubuntu:
Fix Released
Status in isc-dhcp source package in Xenial:
Triaged
Status in isc-dhcp source package in Bionic:
Triaged
Status in isc-dhcp source package in Cosmic:
Won't Fix
Status in isc-dhcp source package in Disco:
Won't Fix
Bug description:
dhcpd reports 'Can't create PID file /run/dhcp-server/dhcpd.pid' (or
'/run/dhcp-server/dhcpd6.pid' for isc-dhcp-server6), and no file is
found /run/dhcp-server.
Additionally, both isc-dhcp-server & isc-dhcp-server6 service unit
files specify the RuntimeDirectory 'dhcp-server', which is removed
when either unit stops (and thus would wipe out the other unit's pid
file, were it being successfully written).
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: isc-dhcp-server 4.3.3-5ubuntu4
ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 2045931] [NEW] ps3 sixasis controller request pin to connect to bt
Public bug reported: Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description:Ubuntu 22.04.3 LTS Release:22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- 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/2045931 Title: ps3 sixasis controller request pin to connect to bt Status in bluez package in Ubuntu: New Bug description: Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+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 1831747] Re: fixrtc hook requires e2fsprogs package, but that is not a dependency
** Changed in: initramfs-tools (Ubuntu Noble) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1831747 Title: fixrtc hook requires e2fsprogs package, but that is not a dependency Status in initramfs-tools package in Ubuntu: Fix Committed Status in initramfs-tools source package in Noble: Fix Committed Bug description: Package "initramfs-tools-core" provides "/usr/share/initramfs- tools/hooks/fixrtc" which runs during the update or regeneration of the initramfs and requires the file "/sbin/dumpe2fs" (available from "e2fsprogs") to be present, otherwise it fails and aborts the whole process, leading e.g. to an inconsistent package system. The problem/cause seems to be that "initramfs-tools-core" package has no direct or indirect hard dependency on "e2fsprogs". I believe either the package dependency should be added, or the fixrtc hook script should be rewritten so that it just outputs a warning instead of aborting with a failure if missing "dumpe2fs" is not a critical problem. This issue seems to affect at least Ubuntu 16.04 and 18.04. It has been brought to my attention at https://askubuntu.com/q/1148791/367990 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831747/+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 338563] Re: kernel update fails when kernels from other distributions are installed in shared /boot
set_linked_version in initramfs-tools 0.142ubuntu17 from noble has: ``` linktarget= if [ -e /initrd.img ] && [ -L /initrd.img ]; then linktarget="$(basename "$(readlink /initrd.img)")" fi if [ -e /boot/initrd.img ] && [ -L /boot/initrd.img ]; then linktarget="$(basename "$(readlink /boot/initrd.img)")" fi ``` ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/338563 Title: kernel update fails when kernels from other distributions are installed in shared /boot Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Jaunty: Won't Fix Bug description: I have multiple linux distributions installed on my computer with a shared /boot partition. I have had this configuration working for a while now with ubuntu as one of the distributions. With jaunty, updates break the boot process every time there is a kernel update and dselect attempts to regenerate initramfs as it incorrectly selects the image from another distribution rather than the ubuntu image. The error message is as follows: Setting up initramfs-tools (0.92bubuntu21) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-initrd-2.6.27.7-desktop-1mnb.img Cannot find /lib/modules/initrd-2.6.27.7-desktop-1mnb.img update-initramfs: failed for /boot/initrd.img-initrd-2.6.27.7-desktop-1mnb.img dpkg: subprocess post-installation script returned error exit status 1 In this case, deselect is trying to update the initrd image for Mandriva - instead of regenerating the ubuntu image: initrd.img-2.6.28-8-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/338563/+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 1831747] Re: fixrtc hook requires e2fsprogs package, but that is not a dependency
e2fsprogs has priority required: ``` $ dpkg -s e2fsprogs | grep "^Package\|^Version\|^Priority" Package: e2fsprogs Priority: required Version: 1.47.0-2ubuntu1 ``` So letting initramfs-tools-core depend on it seems like the correct approach to me. ** Changed in: initramfs-tools (Ubuntu Noble) Assignee: (unassigned) => Benjamin Drung (bdrung) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1831747 Title: fixrtc hook requires e2fsprogs package, but that is not a dependency Status in initramfs-tools package in Ubuntu: Fix Committed Status in initramfs-tools source package in Noble: Fix Committed Bug description: Package "initramfs-tools-core" provides "/usr/share/initramfs- tools/hooks/fixrtc" which runs during the update or regeneration of the initramfs and requires the file "/sbin/dumpe2fs" (available from "e2fsprogs") to be present, otherwise it fails and aborts the whole process, leading e.g. to an inconsistent package system. The problem/cause seems to be that "initramfs-tools-core" package has no direct or indirect hard dependency on "e2fsprogs". I believe either the package dependency should be added, or the fixrtc hook script should be rewritten so that it just outputs a warning instead of aborting with a failure if missing "dumpe2fs" is not a critical problem. This issue seems to affect at least Ubuntu 16.04 and 18.04. It has been brought to my attention at https://askubuntu.com/q/1148791/367990 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831747/+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 2026757] Re: dnsmasq on Ubuntu Jammy crashes on neutron-dhcp-agent updates
Noting that there's very little action Ironic can take on this bug, but marking it triaged to get it out of our dashboard. If there's anything Ironic contributors or CI can do to move this forward, please let us know. ** Changed in: ironic Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2026757 Title: dnsmasq on Ubuntu Jammy crashes on neutron-dhcp-agent updates Status in Ironic: Triaged Status in neutron: New Status in dnsmasq package in Ubuntu: Invalid Status in dnsmasq source package in Jammy: Incomplete Status in dnsmasq source package in Kinetic: Won't Fix Status in dnsmasq source package in Lunar: Invalid Status in dnsmasq source package in Mantic: Invalid Bug description: The Ironic project's CI has been having major blocking issues moving to utilizing Ubuntu Jammy and with some investigation we were able to isolate the issues down to the dhcp updates causing dnsmasq to crash on Ubuntu Jammy, which ships with dnsmasq 2.86. This issue sounds similar to an issue known about to the dnsmasq maintainers, where dnsmasq would crash with updates occurring due to configuration refresh[0]. This resulted in us upgrading dnsmasq to the version which ships with Ubuntu Lunar. Which was no better. Dnsmasq still crashed upon record updates for addresses and ports getting configuration added/changed/removed. We later downgraded to the version of dnsmasq shipped in Ubuntu Focal, and dnsmasq stopped crashing and appeared stable enough to utilize for CI purposes. ** Kernel log from Ubuntu Jammy Package ** [229798.876726] dnsmasq[81586]: segfault at 7c28 ip 7f6e8313147e sp 7fffb3d6f830 error 4 in libc.so.6[7f6e830b4000+195000] [229798.876745] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [229805.444912] dnsmasq[401428]: segfault at dce8 ip 7fe63bf6a47e sp 7ffdb105b440 error 4 in libc.so.6[7fe63beed000+195000] [229805.444933] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [230414.213448] dnsmasq[401538]: segfault at 78b8 ip 7f12160e447e sp 7ffed6ef2190 error 4 in libc.so.6[7f1216067000+195000] [230414.213467] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [230465.098989] dnsmasq[402665]: segfault at c378 ip 7f81458f047e sp 7fff0db334a0 error 4 in libc.so.6[7f8145873000+195000] [230465.099005] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [231787.247374] dnsmasq[402863]: segfault at 7318 ip 7f3940b9147e sp 7ffc8df4f010 error 4 in libc.so.6[7f3940b14000+195000] [231787.247392] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [231844.886399] dnsmasq[405182]: segfault at dc58 ip 7f32a29e147e sp 7ffddedd7480 error 4 in libc.so.6[7f32a2964000+195000] [231844.886420] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [234692.482154] dnsmasq[405289]: segfault at 67d8 ip 7fab0c5c447e sp 7fffd6fd8fa0 error 4 in libc.so.6[7fab0c547000+195000] [234692.482173] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a ** Kernel log entries from Ubuntu Lunar package ** [234724.842339] dnsmasq[409843]: segfault at fffd ip 7f35a147647e sp 7ffd536038c0 error 5 in libc.so.6[7f35a13f9000+195000] [234724.842368] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [234784.918116] dnsmasq[410019]: segfault at fffd ip 7f634233947e sp 7fff33877f20 error 5 in libc.so.6[7f63422bc000+195000] [234784.918133] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83
[Touch-packages] [Bug 2003756] Re: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142."
so perhaps the message should be more descriptive such as "we tried to start the $some.service, but it failed", instead of misleading "Could not execute systemctl". and also should print, "oh, by the way, this is the complete output and exit error code of invoking systemctl " -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2003756 Title: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142." Status in init-system-helpers package in Ubuntu: Confirmed Status in krb5 package in Ubuntu: Confirmed Bug description: I have a fresh install of Ubuntu Server 22.04.01 LTS. After installing the server and running all updates, I run the following command: apt -y install slapd ldap-utils schema2ldif sasl2-bin libsasl2-modules-gssapi-mit krb5-kdc-ldap krb5-admin-server krb5-kdc This will be installing krb5-kdc 1.19.2-2. This is in preparation for setting up an OpenLDAP server, a Kerberos server with an LDAP backend, and saslauthd for pass-through authentication. krb5-kdc was auto-selected when running the steps in the guide here in my development environment: https://ubuntu.com/server/docs/service-kerberos-with-openldap-backend When installing that, I get the following in the output: Setting up krb5-kdc (1.19.2-2) ... Created symlink /etc/systemd/system/multi-user.target.wants/krb5-kdc.service → /lib/systemd/system/krb5-kdc.service. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. I do get the prompts for the realm, kdc, and admin server hostnames, and they are reflected in /etc/krb5.conf. If I then run the following: dpkg-reconfigure krb5-kdc I am prompted for whether I want the package to create the Kerberos KDC configuration automatically, and when I say yes, it then repeats the following error: Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. I cannot find any further debug in the syslog or anything to indicate what the root cause is; the list of packages here are all installed together on a separate development server where I experimented with the configuration I will be deploying here in production so I don't think it's incompatible packages in the install list, but I am open to feedback on that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/2003756/+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 2003756] Re: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142."
this in turn fails when linux modules extra is not installed (it's the one that ships the zram module on which the package installed relies on) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2003756 Title: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142." Status in init-system-helpers package in Ubuntu: Confirmed Status in krb5 package in Ubuntu: Confirmed Bug description: I have a fresh install of Ubuntu Server 22.04.01 LTS. After installing the server and running all updates, I run the following command: apt -y install slapd ldap-utils schema2ldif sasl2-bin libsasl2-modules-gssapi-mit krb5-kdc-ldap krb5-admin-server krb5-kdc This will be installing krb5-kdc 1.19.2-2. This is in preparation for setting up an OpenLDAP server, a Kerberos server with an LDAP backend, and saslauthd for pass-through authentication. krb5-kdc was auto-selected when running the steps in the guide here in my development environment: https://ubuntu.com/server/docs/service-kerberos-with-openldap-backend When installing that, I get the following in the output: Setting up krb5-kdc (1.19.2-2) ... Created symlink /etc/systemd/system/multi-user.target.wants/krb5-kdc.service → /lib/systemd/system/krb5-kdc.service. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. I do get the prompts for the realm, kdc, and admin server hostnames, and they are reflected in /etc/krb5.conf. If I then run the following: dpkg-reconfigure krb5-kdc I am prompted for whether I want the package to create the Kerberos KDC configuration automatically, and when I say yes, it then repeats the following error: Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. I cannot find any further debug in the syslog or anything to indicate what the root cause is; the list of packages here are all installed together on a separate development server where I experimented with the configuration I will be deploying here in production so I don't think it's incompatible packages in the install list, but I am open to feedback on that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/2003756/+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 2003756] Re: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142."
probably because the service failed to start? $ journalctl --no-hostname -u zramswap Dec 07 20:55:42 systemd[1]: Starting Linux zramswap setup... Dec 07 20:55:42 root[452655]: Starting Zram Dec 07 20:55:42 zramswap[452655]: <13>Dec 7 20:55:42 root: Starting Zram Dec 07 20:55:42 zramswap[452656]: modprobe: FATAL: Module zram not found in directory /lib/modules/5.15.0-89-generic Dec 07 20:55:42 root[452657]: Error: inserting the zram kernel module Dec 07 20:55:42 zramswap[452657]: <13>Dec 7 20:55:42 root: Error: inserting the zram kernel module Dec 07 20:55:42 systemd[1]: zramswap.service: Main process exited, code=exited, status=1/FAILURE Dec 07 20:55:42 systemd[1]: zramswap.service: Failed with result 'exit-code'. Dec 07 20:55:42 systemd[1]: Failed to start Linux zramswap setup. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2003756 Title: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142." Status in init-system-helpers package in Ubuntu: Confirmed Status in krb5 package in Ubuntu: Confirmed Bug description: I have a fresh install of Ubuntu Server 22.04.01 LTS. After installing the server and running all updates, I run the following command: apt -y install slapd ldap-utils schema2ldif sasl2-bin libsasl2-modules-gssapi-mit krb5-kdc-ldap krb5-admin-server krb5-kdc This will be installing krb5-kdc 1.19.2-2. This is in preparation for setting up an OpenLDAP server, a Kerberos server with an LDAP backend, and saslauthd for pass-through authentication. krb5-kdc was auto-selected when running the steps in the guide here in my development environment: https://ubuntu.com/server/docs/service-kerberos-with-openldap-backend When installing that, I get the following in the output: Setting up krb5-kdc (1.19.2-2) ... Created symlink /etc/systemd/system/multi-user.target.wants/krb5-kdc.service → /lib/systemd/system/krb5-kdc.service. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. I do get the prompts for the realm, kdc, and admin server hostnames, and they are reflected in /etc/krb5.conf. If I then run the following: dpkg-reconfigure krb5-kdc I am prompted for whether I want the package to create the Kerberos KDC configuration automatically, and when I say yes, it then repeats the following error: Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. I cannot find any further debug in the syslog or anything to indicate what the root cause is; the list of packages here are all installed together on a separate development server where I experimented with the configuration I will be deploying here in production so I don't think it's incompatible packages in the install list, but I am open to feedback on that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/2003756/+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 2003756] Re: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142."
same error when installing `zram-tools` under jammy 22.04.3 LTS
$ sudo eatmydata apt install zram-tools
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
bc
The following NEW packages will be installed:
bc zram-tools
0 upgraded, 2 newly installed, 0 to remove and 33 not upgraded.
Need to get 93.3 kB of archives.
After this operation, 249 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 bc amd64
1.07.1-3build1 [87.6 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 zram-tools all
0.3.3.1-1 [5,676 B]
Fetched 93.3 kB in 0s (522 kB/s)
Selecting previously unselected package bc.
(Reading database ... 48059 files and directories currently installed.)
Preparing to unpack .../bc_1.07.1-3build1_amd64.deb ...
Unpacking bc (1.07.1-3build1) ...
Selecting previously unselected package zram-tools.
Preparing to unpack .../zram-tools_0.3.3.1-1_all.deb ...
Unpacking zram-tools (0.3.3.1-1) ...
Setting up bc (1.07.1-3build1) ...
Setting up zram-tools (0.3.3.1-1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/zramswap.service →
/lib/systemd/system/zramswap.service.
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142.
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for doc-base (0.11.1) ...
Processing 1 added doc-base file...
this is line 142 in /usr/bin/deb-systemd-invoke
system('systemctl', '--quiet', @instance_args, $action,
@start_units) == 0 or die("Could not execute systemctl: $!");
$ dpkg -S /usr/bin/deb-systemd-invoke
init-system-helpers: /usr/bin/deb-systemd-invoke
$ apt policy $(dpkg -S /usr/bin/deb-systemd-invoke|cut -d: -f1)
init-system-helpers:
Installed: 1.62
Candidate: 1.62
Version table:
*** 1.62 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages
100 /var/lib/dpkg/status
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/2003756
Title:
Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute
systemctl: at /usr/bin/deb-systemd-invoke line 142."
Status in init-system-helpers package in Ubuntu:
Confirmed
Status in krb5 package in Ubuntu:
Confirmed
Bug description:
I have a fresh install of Ubuntu Server 22.04.01 LTS. After
installing the server and running all updates, I run the following
command:
apt -y install slapd ldap-utils schema2ldif sasl2-bin
libsasl2-modules-gssapi-mit krb5-kdc-ldap krb5-admin-server krb5-kdc
This will be installing krb5-kdc 1.19.2-2.
This is in preparation for setting up an OpenLDAP server, a Kerberos
server with an LDAP backend, and saslauthd for pass-through
authentication. krb5-kdc was auto-selected when running the steps in
the guide here in my development environment:
https://ubuntu.com/server/docs/service-kerberos-with-openldap-backend
When installing that, I get the following in the output:
Setting up krb5-kdc (1.19.2-2) ...
Created symlink /etc/systemd/system/multi-user.target.wants/krb5-kdc.service
→ /lib/systemd/system/krb5-kdc.service.
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142.
I do get the prompts for the realm, kdc, and admin server hostnames,
and they are reflected in /etc/krb5.conf. If I then run the
following:
dpkg-reconfigure krb5-kdc
I am prompted for whether I want the package to create the Kerberos
KDC configuration automatically, and when I say yes, it then repeats
the following error:
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142.
I cannot find any further debug in the syslog or anything to indicate
what the root cause is; the list of packages here are all installed
together on a separate development server where I experimented with
the configuration I will be deploying here in production so I don't
think it's incompatible packages in the install list, but I am open to
feedback on that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/2003756/+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 2033195] Re: No sound on ASUS ROG Strix SCAR 16 G634JZ
I have the same problem. No sound using ubuntu 23.04 on a on ASUS ROG Strix SCAR 16 2023 G634JZ laptop. I can only ear sound with headphones. I have also tried with xubuntu 22.04 and 23.04 and the same result: no sound from internal speakers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2033195 Title: No sound on ASUS ROG Strix SCAR 16 G634JZ Status in alsa-driver package in Ubuntu: New Bug description: Using Ubuntu 23.04 on a on ASUS ROG Strix SCAR 16 G634JZ laptop. There is no sound from internal speakers. Sound via HDMI is fine. grep "Codec:" /proc/asound/card*/codec* /proc/asound/card0/codec#0:Codec: Realtek ALC285 /proc/asound/card0/codec#2:Codec: Intel Raptorlake HDMI /proc/asound/card1/codec#0:Codec: Nvidia GPU a5 HDMI/DP ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anied 2772 F wireplumber /dev/snd/controlC2: anied 2772 F wireplumber /dev/snd/controlC1: anied 2772 F wireplumber /dev/snd/seq:anied 2769 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Aug 27 16:43:12 2023 InstallationDate: Installed on 2023-05-03 (116 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=hu_HU.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G634JZ.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G634JZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.67 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG634JZ.317:bd07/12/2023:br5.27:efr0.67:svnASUSTeKCOMPUTERINC.:pnROGStrixG634JZ_G634JZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG634JZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G634JZ_G634JZ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2033195/+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 2018273] Re: package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with lib
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libnih (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnih in Ubuntu. https://bugs.launchpad.net/bugs/2018273 Title: package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances Status in libnih package in Ubuntu: Confirmed Bug description: . ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libnih-dbus1 1.0.3-6ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-71.78-generic 5.15.92 Uname: Linux 5.15.0-71-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: libnih-dbus1:amd64: Install libnih1:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue May 2 09:33:36 2023 DpkgTerminalLog: dpkg: error processing archive /var/cache/apt/archives/libnih-dbus1_1.0.3-12build1_amd64.deb (--unpack): package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances ErrorMessage: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances InstallationDate: Installed on 2014-05-11 (3278 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: libnih Title: package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances UpgradeStatus: Upgraded to jammy on 2022-11-20 (162 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/2018273/+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 2045855] Re: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file on stdin at conffile prompt
hi @yudamjoo o/
Please check the end of your `DpkgTerminalLog.txt` file.
To fix CVE-2023-45866 [0] a configuration file
(`/etc/bluetooth/input.conf`) was changed. If there had been edits made
to this file before updating BlueZ, apt will ask what you want to do
with the configuration file. "Y" is likely the right option if you do
not intend to have custom changes in `/etc/bluetooth/input.conf`.
Here's an example of me asking apt to show the config differences ("D") before
accepting the new changes ("Y"):
```
$ sudo apt install bluez
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be upgraded:
bluez
1 upgraded, 0 newly installed, 0 to remove and 157 not upgraded.
Need to get 1,106 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 https://redacted.launchpadcontent.net/ubuntu-security/ppa/ubuntu
jammy/main amd64 bluez amd64 5.64-0ubuntu1.1 [1,106 kB]
Fetched 1,106 kB in 1s (884 kB/s)
(Reading database ... 161840 files and directories currently installed.)
Preparing to unpack .../bluez_5.64-0ubuntu1.1_amd64.deb ...
Unpacking bluez (5.64-0ubuntu1.1) over (5.64-0ubuntu1) ...
Setting up bluez (5.64-0ubuntu1.1) ...
Configuration file '/etc/bluetooth/input.conf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** input.conf (Y/I/N/O/D/Z) [default=N] ? D
--- /etc/bluetooth/input.conf 2023-03-21 08:04:20.023928226 -0500
+++ /etc/bluetooth/input.conf.dpkg-new 2023-11-29 05:31:28.0 -0600
@@ -17,8 +17,8 @@
# platforms may want to make sure that input connections only come from bonded
# device connections. Several older mice have been known for not supporting
# pairing/encryption.
-# Defaults to false to maximize device compatibility.
-ClassicBondedOnly=true
+# Defaults to true for security.
+#ClassicBondedOnly=true
# LE upgrade security
# Enables upgrades of security automatically if required.
Configuration file '/etc/bluetooth/input.conf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** input.conf (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/bluetooth/input.conf ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for dbus (1.12.20-2ubuntu4.1) ...
```
[0] https://ubuntu.com/security/notices/USN-6540-1
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-45866
** Information type changed from Private Security to Public
--
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/2045855
Title:
package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file
on stdin at conffile prompt
Status in bluez package in Ubuntu:
New
Bug description:
I did not recognized the error.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: bluez 5.64-0ubuntu1.1
ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
AptOrdering:
bluez:amd64: Install
NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Dec 7 15:44:57 2023
ErrorMessage: end of file on stdin at conffile prompt
InstallationDate: Installed on 2021-01-30 (1040 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. OptiPlex 7010
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic
root=UUID=1aa27b2f-8d22-4b4e-931f-bd8e304ed0d4 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.10, Python 3.10.12, unpackaged
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.21.1ubuntu2.2
apt 2.4.11
SourcePackage: bluez
Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file
on stdin at conffile prompt
UpgradeStatus: Upgraded to jammy on 2023-03-28 (253 days ago)
dmi.bios.date: 03/25/2013
dmi.bios.release: 4.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.name: 0GY6Y8
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
[Touch-packages] [Bug 2033639] Re: debug-me 1.20221231-1 FTBFS on ppc64el due to internal ld.gold error
** Changed in: debug-me (Debian) Status: Fix Released => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2033639 Title: debug-me 1.20221231-1 FTBFS on ppc64el due to internal ld.gold error Status in binutils package in Ubuntu: New Status in debug-me package in Ubuntu: Fix Released Status in debug-me package in Debian: New Bug description: debug-me 1.20221231-1 fails to build from source on ppc64el due to internal ld.gold error (binutils 2.41-4ubuntu1): ``` Linking dist/build/debug-me/debug-me ... /usr/bin/ld.gold: internal error in set_xindex, at ../../gold/object.h:1050 collect2: error: ld returned 1 exit status `powerpc64le-linux-gnu-gcc' failed in phase `Linker'. (Exit code: 1) ``` Full log: https://launchpadlibrarian.net/684538812/buildlog_ubuntu- mantic-ppc64el.debug-me_1.20221231-1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2033639/+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 2044104] Re: [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with zdev:early=0 set
** Tags removed: rls-ff-incoming rls-jj-incoming ** Tags added: foundations-todo ** Also affects: s390-tools (Ubuntu Noble) Importance: Medium Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Also affects: initramfs-tools (Ubuntu Noble) Importance: Medium Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2044104 Title: [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with zdev:early=0 set Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: New Status in s390-tools package in Ubuntu: New Status in initramfs-tools source package in Noble: New Status in s390-tools source package in Noble: New Bug description: Versions: Ubuntu 20.04.5 s390-tools version 2.12.0-0ubuntu3.7.s390x Ubuntu 22.04.2 s390-tools version 2.20.0-0ubuntu3.2.s390x When I configure a zfcp LUN persistently via chzdev, the initrd is being rebuilt even with parameter zdev:early=0 root@a8315003:~# chzdev -e zfcp-lun 0.0.1803:0x500507630910d430:0x40194092 zdev:early=0 zFCP LUN 0.0.1803:0x500507630910d430:0x40194092 configured Note: The initial RAM-disk must be updated for these changes to take effect: - zFCP LUN 0.0.1803:0x500507630910d430:0x40194092 update-initramfs: Generating /boot/initrd.img-5.15.0-60-generic I: The initramfs will attempt to resume from /dev/dasdb1 I: (UUID=e70ecb80-4d1e-4074-9cda-ce231ad6e698) I: Set the RESUME variable to override this. Using config file '/etc/zipl.conf' Building bootmap in '/boot' Adding IPL section 'ubuntu' (default) Preparing boot device: dasda (c00a). Done. root@a8315003:~# == Comment: - Thorsten Diehl - 2023-03-01 06:55:47 == @BOE-dev This behaviour is unexpected. https://www.ibm.com/docs/en/linux-on-systems?topic=commands-chzdev says: Activating a device early during the boot process Use the zdev:early device attribute to activate a device early during the boot process and to override any existing auto-configuration with a persistent device configuration. zdev:early=1 The device is activated during the initial RAM disc phase according to the persistent configuration. zdev:early=0 The device is activated as usual during the boot process. This is the default. If auto-configuration data is present, the device is activated during the initial RAM disc phase according to the auto-configuration. I can't interprete a SCSI LUN as a device with auto configuration data. (At least, if the zfcp device hasn't NPIV enabled) == Comment: #5 - Peter Oberparleiter - 2023-03-01 11:18:28 == (In reply to comment #2) > @BOE-dev > This behaviour is unexpected. > https://www.ibm.com/docs/en/linux-on-systems?topic=commands-chzdev says: > Activating a device early during the boot process > > Use the zdev:early device attribute to activate a device early during the > boot process and to override any existing auto-configuration with a > persistent device configuration. > > zdev:early=1 > The device is activated during the initial RAM disc phase according to > the persistent configuration. > > zdev:early=0 > The device is activated as usual during the boot process. This is the > default. If auto-configuration data is present, the device is activated > during the initial RAM disc phase according to the auto-configuration. The documentation is incorrect for Ubuntu. Canonical specifically builds zdev in a way that every change to persistent device configuration causes an update to the initial RAM-disk. See also: https://bugzilla.linux.ibm.com/show_bug.cgi?id=187578#c35 https://github.com/ibm-s390-linux/s390-tools/commit/7dd03eaeecdd0e2674f145aca34be1275d291bd8 > I can't interprete a SCSI LUN as a device with auto configuration data. (At > least, if the zfcp device hasn't NPIV enabled) This is related to auto-configuration as implemented for DPM. == Comment: #6 - Thorsten Diehl - 2023-03-03 12:41:44 == So, IIUC, chzdev is built for Ubuntu with ZDEV_ALWAYS_UPDATE_INITRD=1, which make the parameter zdev:early=0 ineffective. Correct? If you confirm, you may also close this bug. Not nice - then we have to find an alternate solution. == Comment: #7 - Peter Oberparleiter - 2023-03-07 06:48:07 == (In reply to comment #6) > So, IIUC, chzdev is built for Ubuntu with ZDEV_ALWAYS_UPDATE_INITRD=1, which > make the parameter zdev:early=0 ineffective. Correct? > If you confirm, you may also close this bug. > > Not nice - then we have to find an alternate solution. chzdev -p on Ubuntu will by default rebuild the initrd. This is intended behavior by Canonical and controlled by the ZDEV_ALWAYS_UPDATE_INITRD build-time switch. You can suppress it by adding option --no-root-update to
[Touch-packages] [Bug 2043713] Re: TestApportValgrind.test_valgrind_min_installed fails on armhf: Invalid write of size 4
** Changed in: apport (Ubuntu) Importance: Undecided => High -- 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/2043713 Title: TestApportValgrind.test_valgrind_min_installed fails on armhf: Invalid write of size 4 Status in apport package in Ubuntu: In Progress Bug description: autopkgtests are pretty reliably failing[1] on armhf due to the following (single) test failure: 517s === FAILURES === 517s TestApportValgrind.test_valgrind_min_installed 517s 517s self = 517s 517s def test_valgrind_min_installed(self): 517s """Valgrind is installed and recent enough.""" 517s cmd = ["valgrind", "-q", "--extra-debuginfo-path=./", "ls"] 517s (ret, out, err) = self._call(cmd) 517s > self.assertEqual(err, "") 517s E AssertionError: "==2567== Invalid write of size 4\n==2567[1064 chars]= \n" != '' 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4843040: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a7e4 is on thread 1's stack 517s E - ==2567== 64 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842F96: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a758 is on thread 1's stack 517s E - ==2567== 160 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x484958C: selinuxfs_exists (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a7bc is on thread 1's stack 517s E - ==2567== 48 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842F0E: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a690 is on thread 1's stack 517s E - ==2567== 16 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842E62: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a6a0 is on thread 1's stack 517s E - ==2567== 8 bytes below stack pointer 517s E - ==2567== 517s 517s tests/integration/test_apport_valgrind.py:45: AssertionError 517s === warnings summary === This is caused by -fstack-clash-protection. Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1522678 [1] https://autopkgtest.ubuntu.com/packages/a/apport/noble/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2043713/+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 2043713] Re: TestApportValgrind.test_valgrind_min_installed fails on armhf: Invalid write of size 4
It should be fixed by the last libselinux upload which has migrated, but keeping it "In Progress" until a successful autopkgtest run of apport -- 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/2043713 Title: TestApportValgrind.test_valgrind_min_installed fails on armhf: Invalid write of size 4 Status in apport package in Ubuntu: In Progress Bug description: autopkgtests are pretty reliably failing[1] on armhf due to the following (single) test failure: 517s === FAILURES === 517s TestApportValgrind.test_valgrind_min_installed 517s 517s self = 517s 517s def test_valgrind_min_installed(self): 517s """Valgrind is installed and recent enough.""" 517s cmd = ["valgrind", "-q", "--extra-debuginfo-path=./", "ls"] 517s (ret, out, err) = self._call(cmd) 517s > self.assertEqual(err, "") 517s E AssertionError: "==2567== Invalid write of size 4\n==2567[1064 chars]= \n" != '' 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4843040: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a7e4 is on thread 1's stack 517s E - ==2567== 64 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842F96: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a758 is on thread 1's stack 517s E - ==2567== 160 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x484958C: selinuxfs_exists (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a7bc is on thread 1's stack 517s E - ==2567== 48 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842F0E: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a690 is on thread 1's stack 517s E - ==2567== 16 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842E62: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a6a0 is on thread 1's stack 517s E - ==2567== 8 bytes below stack pointer 517s E - ==2567== 517s 517s tests/integration/test_apport_valgrind.py:45: AssertionError 517s === warnings summary === This is caused by -fstack-clash-protection. Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1522678 [1] https://autopkgtest.ubuntu.com/packages/a/apport/noble/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2043713/+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 2043713] Re: TestApportValgrind.test_valgrind_min_installed fails on armhf: Invalid write of size 4
** Changed in: apport (Ubuntu) Status: New => In Progress ** Changed in: apport (Ubuntu) Assignee: (unassigned) => Mate Kukri (mkukri) -- 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/2043713 Title: TestApportValgrind.test_valgrind_min_installed fails on armhf: Invalid write of size 4 Status in apport package in Ubuntu: In Progress Bug description: autopkgtests are pretty reliably failing[1] on armhf due to the following (single) test failure: 517s === FAILURES === 517s TestApportValgrind.test_valgrind_min_installed 517s 517s self = 517s 517s def test_valgrind_min_installed(self): 517s """Valgrind is installed and recent enough.""" 517s cmd = ["valgrind", "-q", "--extra-debuginfo-path=./", "ls"] 517s (ret, out, err) = self._call(cmd) 517s > self.assertEqual(err, "") 517s E AssertionError: "==2567== Invalid write of size 4\n==2567[1064 chars]= \n" != '' 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4843040: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a7e4 is on thread 1's stack 517s E - ==2567== 64 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842F96: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a758 is on thread 1's stack 517s E - ==2567== 160 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x484958C: selinuxfs_exists (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a7bc is on thread 1's stack 517s E - ==2567== 48 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842F0E: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a690 is on thread 1's stack 517s E - ==2567== 16 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842E62: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a6a0 is on thread 1's stack 517s E - ==2567== 8 bytes below stack pointer 517s E - ==2567== 517s 517s tests/integration/test_apport_valgrind.py:45: AssertionError 517s === warnings summary === This is caused by -fstack-clash-protection. Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1522678 [1] https://autopkgtest.ubuntu.com/packages/a/apport/noble/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2043713/+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 2043713] Re: TestApportValgrind.test_valgrind_min_installed fails on armhf: Invalid write of size 4
** Tags removed: rls-nn-incoming -- 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/2043713 Title: TestApportValgrind.test_valgrind_min_installed fails on armhf: Invalid write of size 4 Status in apport package in Ubuntu: In Progress Bug description: autopkgtests are pretty reliably failing[1] on armhf due to the following (single) test failure: 517s === FAILURES === 517s TestApportValgrind.test_valgrind_min_installed 517s 517s self = 517s 517s def test_valgrind_min_installed(self): 517s """Valgrind is installed and recent enough.""" 517s cmd = ["valgrind", "-q", "--extra-debuginfo-path=./", "ls"] 517s (ret, out, err) = self._call(cmd) 517s > self.assertEqual(err, "") 517s E AssertionError: "==2567== Invalid write of size 4\n==2567[1064 chars]= \n" != '' 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4843040: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a7e4 is on thread 1's stack 517s E - ==2567== 64 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842F96: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a758 is on thread 1's stack 517s E - ==2567== 160 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x484958C: selinuxfs_exists (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a7bc is on thread 1's stack 517s E - ==2567== 48 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842F0E: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a690 is on thread 1's stack 517s E - ==2567== 16 bytes below stack pointer 517s E - ==2567== 517s E - ==2567== Invalid write of size 4 517s E - ==2567== at 0x4842E62: ??? (in /usr/lib/arm-linux-gnueabihf/libselinux.so.1) 517s E - ==2567== Address 0xfec9a6a0 is on thread 1's stack 517s E - ==2567== 8 bytes below stack pointer 517s E - ==2567== 517s 517s tests/integration/test_apport_valgrind.py:45: AssertionError 517s === warnings summary === This is caused by -fstack-clash-protection. Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1522678 [1] https://autopkgtest.ubuntu.com/packages/a/apport/noble/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2043713/+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 1831747] Re: fixrtc hook requires e2fsprogs package, but that is not a dependency
** Tags removed: rls-nn-incoming ** Tags added: foundations-todo ** Also affects: initramfs-tools (Ubuntu Noble) Importance: Low Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1831747 Title: fixrtc hook requires e2fsprogs package, but that is not a dependency Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools source package in Noble: Confirmed Bug description: Package "initramfs-tools-core" provides "/usr/share/initramfs- tools/hooks/fixrtc" which runs during the update or regeneration of the initramfs and requires the file "/sbin/dumpe2fs" (available from "e2fsprogs") to be present, otherwise it fails and aborts the whole process, leading e.g. to an inconsistent package system. The problem/cause seems to be that "initramfs-tools-core" package has no direct or indirect hard dependency on "e2fsprogs". I believe either the package dependency should be added, or the fixrtc hook script should be rewritten so that it just outputs a warning instead of aborting with a failure if missing "dumpe2fs" is not a critical problem. This issue seems to affect at least Ubuntu 16.04 and 18.04. It has been brought to my attention at https://askubuntu.com/q/1148791/367990 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831747/+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 2045886] Re: Please merge 8.5.0-1 into noble
hmm an autopkgtest is segfaulting (also in Debian) 2813s ldap_send_server_request 2813s ## Something failed, gathering logs 2813s 2813s ## syslog 2813s Segmentation fault (core dumped) ... 2813s curl-ldapi-test FAIL non-zero exit status 139 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2045886 Title: Please merge 8.5.0-1 into noble Status in curl package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2045886/+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 2044104] Re: [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with zdev:early=0 set
Tagging this to discuss this during the Foundations weekly meeting ** Tags added: rls-ff-incoming rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2044104 Title: [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with zdev:early=0 set Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: New Status in s390-tools package in Ubuntu: New Bug description: Versions: Ubuntu 20.04.5 s390-tools version 2.12.0-0ubuntu3.7.s390x Ubuntu 22.04.2 s390-tools version 2.20.0-0ubuntu3.2.s390x When I configure a zfcp LUN persistently via chzdev, the initrd is being rebuilt even with parameter zdev:early=0 root@a8315003:~# chzdev -e zfcp-lun 0.0.1803:0x500507630910d430:0x40194092 zdev:early=0 zFCP LUN 0.0.1803:0x500507630910d430:0x40194092 configured Note: The initial RAM-disk must be updated for these changes to take effect: - zFCP LUN 0.0.1803:0x500507630910d430:0x40194092 update-initramfs: Generating /boot/initrd.img-5.15.0-60-generic I: The initramfs will attempt to resume from /dev/dasdb1 I: (UUID=e70ecb80-4d1e-4074-9cda-ce231ad6e698) I: Set the RESUME variable to override this. Using config file '/etc/zipl.conf' Building bootmap in '/boot' Adding IPL section 'ubuntu' (default) Preparing boot device: dasda (c00a). Done. root@a8315003:~# == Comment: - Thorsten Diehl - 2023-03-01 06:55:47 == @BOE-dev This behaviour is unexpected. https://www.ibm.com/docs/en/linux-on-systems?topic=commands-chzdev says: Activating a device early during the boot process Use the zdev:early device attribute to activate a device early during the boot process and to override any existing auto-configuration with a persistent device configuration. zdev:early=1 The device is activated during the initial RAM disc phase according to the persistent configuration. zdev:early=0 The device is activated as usual during the boot process. This is the default. If auto-configuration data is present, the device is activated during the initial RAM disc phase according to the auto-configuration. I can't interprete a SCSI LUN as a device with auto configuration data. (At least, if the zfcp device hasn't NPIV enabled) == Comment: #5 - Peter Oberparleiter - 2023-03-01 11:18:28 == (In reply to comment #2) > @BOE-dev > This behaviour is unexpected. > https://www.ibm.com/docs/en/linux-on-systems?topic=commands-chzdev says: > Activating a device early during the boot process > > Use the zdev:early device attribute to activate a device early during the > boot process and to override any existing auto-configuration with a > persistent device configuration. > > zdev:early=1 > The device is activated during the initial RAM disc phase according to > the persistent configuration. > > zdev:early=0 > The device is activated as usual during the boot process. This is the > default. If auto-configuration data is present, the device is activated > during the initial RAM disc phase according to the auto-configuration. The documentation is incorrect for Ubuntu. Canonical specifically builds zdev in a way that every change to persistent device configuration causes an update to the initial RAM-disk. See also: https://bugzilla.linux.ibm.com/show_bug.cgi?id=187578#c35 https://github.com/ibm-s390-linux/s390-tools/commit/7dd03eaeecdd0e2674f145aca34be1275d291bd8 > I can't interprete a SCSI LUN as a device with auto configuration data. (At > least, if the zfcp device hasn't NPIV enabled) This is related to auto-configuration as implemented for DPM. == Comment: #6 - Thorsten Diehl - 2023-03-03 12:41:44 == So, IIUC, chzdev is built for Ubuntu with ZDEV_ALWAYS_UPDATE_INITRD=1, which make the parameter zdev:early=0 ineffective. Correct? If you confirm, you may also close this bug. Not nice - then we have to find an alternate solution. == Comment: #7 - Peter Oberparleiter - 2023-03-07 06:48:07 == (In reply to comment #6) > So, IIUC, chzdev is built for Ubuntu with ZDEV_ALWAYS_UPDATE_INITRD=1, which > make the parameter zdev:early=0 ineffective. Correct? > If you confirm, you may also close this bug. > > Not nice - then we have to find an alternate solution. chzdev -p on Ubuntu will by default rebuild the initrd. This is intended behavior by Canonical and controlled by the ZDEV_ALWAYS_UPDATE_INITRD build-time switch. You can suppress it by adding option --no-root-update to the command line. Specifying zdev:early=0 to chzdev has exactly the effect that it is supposed to have: it tells zdev not to enable that device during initrd processing, resulting in the corresponding udev rule not being copied to the initrd [1]. Unfortunately there is another Ubuntu-initrd script
[Touch-packages] [Bug 1958019]
It seems the sound no longer works for the legion 7 16achg6 on kernel 6.6. It's been working great for the last year on all kernels, but 6.6 just doesn't work. I'm not sure if anyone else is having similar issues? Manjaro Linux here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 2045907] [NEW] GtkFileChooserDialog hangs on large folder with 300000 files
Public bug reported: when I paste filename into the location bar (Ctrl+L) the file chooser hangs. The file happens to be in a folder with 30 other files and GtkFileChooserDialog tries to offer a filename typing suggestion dropdown which is slow and eventually crashes. When I then kill chrome or firefox then wayland session gets logouted. Ubuntu version is 23.10 ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2045907 Title: GtkFileChooserDialog hangs on large folder with 30 files Status in gtk+3.0 package in Ubuntu: New Bug description: when I paste filename into the location bar (Ctrl+L) the file chooser hangs. The file happens to be in a folder with 30 other files and GtkFileChooserDialog tries to offer a filename typing suggestion dropdown which is slow and eventually crashes. When I then kill chrome or firefox then wayland session gets logouted. Ubuntu version is 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2045907/+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 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs
Waiting for 6.5.13 to actually build but on 6.6.0-14 from proposed now
which is based on 6.6.3 which probably has all the fancy patches too
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2045899
Title:
More amdgpu crashes: pagefaults, ring timeouts and parser bugs
Status in linux package in Ubuntu:
Incomplete
Status in mesa package in Ubuntu:
New
Bug description:
I think running the Mattermost snap forced to Wayland rendering
*eventually* seems to crash amdgpu, it recovers at the kernel level
but the GUI doesn't actually recover and I also can switch tty with
the keyboard.
I have attached the two crashes from yesterday, they look slightly
different but may be the same cause:
LastDmesg.txt contains the journalctl -k -b of the last failed boot,
OlderDmesg.txt contains the same for the crash before that.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.5.0-14-generic 6.5.0-14.14
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Dec 7 13:09:42 2023
InstallationDate: Installed on 2022-11-26 (376 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-14-generic N/A
linux-backports-modules-6.5.0-14-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2023
dmi.bios.release: 1.47
dmi.bios.vendor: LENOVO
dmi.bios.version: R23ET71W (1.47 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CF004PGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76538 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.28
dmi.modalias:
dmi:bvnLENOVO:bvrR23ET71W(1.47):bd09/14/2023:br1.47:efr1.28:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
dmi.product.family: ThinkPad T14 Gen 3
dmi.product.name: 21CF004PGE
dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
dmi.product.version: ThinkPad T14 Gen 3
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+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 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs
please try a later point release mainline kernel:
https://kernel.ubuntu.com/mainline/v6.5.13/
which is also the last one for 6.5
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2045899
Title:
More amdgpu crashes: pagefaults, ring timeouts and parser bugs
Status in linux package in Ubuntu:
Incomplete
Status in mesa package in Ubuntu:
New
Bug description:
I think running the Mattermost snap forced to Wayland rendering
*eventually* seems to crash amdgpu, it recovers at the kernel level
but the GUI doesn't actually recover and I also can switch tty with
the keyboard.
I have attached the two crashes from yesterday, they look slightly
different but may be the same cause:
LastDmesg.txt contains the journalctl -k -b of the last failed boot,
OlderDmesg.txt contains the same for the crash before that.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.5.0-14-generic 6.5.0-14.14
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Dec 7 13:09:42 2023
InstallationDate: Installed on 2022-11-26 (376 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-14-generic N/A
linux-backports-modules-6.5.0-14-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2023
dmi.bios.release: 1.47
dmi.bios.vendor: LENOVO
dmi.bios.version: R23ET71W (1.47 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CF004PGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76538 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.28
dmi.modalias:
dmi:bvnLENOVO:bvrR23ET71W(1.47):bd09/14/2023:br1.47:efr1.28:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
dmi.product.family: ThinkPad T14 Gen 3
dmi.product.name: 21CF004PGE
dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
dmi.product.version: ThinkPad T14 Gen 3
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+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 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs
These ones I don't remember seeing before:
[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2045899
Title:
More amdgpu crashes: pagefaults, ring timeouts and parser bugs
Status in linux package in Ubuntu:
Incomplete
Status in mesa package in Ubuntu:
New
Bug description:
I think running the Mattermost snap forced to Wayland rendering
*eventually* seems to crash amdgpu, it recovers at the kernel level
but the GUI doesn't actually recover and I also can switch tty with
the keyboard.
I have attached the two crashes from yesterday, they look slightly
different but may be the same cause:
LastDmesg.txt contains the journalctl -k -b of the last failed boot,
OlderDmesg.txt contains the same for the crash before that.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.5.0-14-generic 6.5.0-14.14
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Dec 7 13:09:42 2023
InstallationDate: Installed on 2022-11-26 (376 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-14-generic N/A
linux-backports-modules-6.5.0-14-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2023
dmi.bios.release: 1.47
dmi.bios.vendor: LENOVO
dmi.bios.version: R23ET71W (1.47 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CF004PGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76538 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.28
dmi.modalias:
dmi:bvnLENOVO:bvrR23ET71W(1.47):bd09/14/2023:br1.47:efr1.28:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
dmi.product.family: ThinkPad T14 Gen 3
dmi.product.name: 21CF004PGE
dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
dmi.product.version: ThinkPad T14 Gen 3
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+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 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs
I saw similar messages in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032386 but that
only caused hangs and not block the entire desktop (and Firefox is good
now so I don't know)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2045899
Title:
More amdgpu crashes: pagefaults, ring timeouts and parser bugs
Status in linux package in Ubuntu:
Incomplete
Status in mesa package in Ubuntu:
New
Bug description:
I think running the Mattermost snap forced to Wayland rendering
*eventually* seems to crash amdgpu, it recovers at the kernel level
but the GUI doesn't actually recover and I also can switch tty with
the keyboard.
I have attached the two crashes from yesterday, they look slightly
different but may be the same cause:
LastDmesg.txt contains the journalctl -k -b of the last failed boot,
OlderDmesg.txt contains the same for the crash before that.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.5.0-14-generic 6.5.0-14.14
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Dec 7 13:09:42 2023
InstallationDate: Installed on 2022-11-26 (376 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-14-generic N/A
linux-backports-modules-6.5.0-14-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2023
dmi.bios.release: 1.47
dmi.bios.vendor: LENOVO
dmi.bios.version: R23ET71W (1.47 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CF004PGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76538 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.28
dmi.modalias:
dmi:bvnLENOVO:bvrR23ET71W(1.47):bd09/14/2023:br1.47:efr1.28:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
dmi.product.family: ThinkPad T14 Gen 3
dmi.product.name: 21CF004PGE
dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
dmi.product.version: ThinkPad T14 Gen 3
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+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 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs
** Attachment added: "OlderDmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+attachment/5727266/+files/OlderDmesg.txt
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2045899
Title:
More amdgpu crashes: pagefaults, ring timeouts and parser bugs
Status in linux package in Ubuntu:
Incomplete
Status in mesa package in Ubuntu:
New
Bug description:
I think running the Mattermost snap forced to Wayland rendering
*eventually* seems to crash amdgpu, it recovers at the kernel level
but the GUI doesn't actually recover and I also can switch tty with
the keyboard.
I have attached the two crashes from yesterday, they look slightly
different but may be the same cause:
LastDmesg.txt contains the journalctl -k -b of the last failed boot,
OlderDmesg.txt contains the same for the crash before that.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.5.0-14-generic 6.5.0-14.14
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Dec 7 13:09:42 2023
InstallationDate: Installed on 2022-11-26 (376 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-14-generic N/A
linux-backports-modules-6.5.0-14-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2023
dmi.bios.release: 1.47
dmi.bios.vendor: LENOVO
dmi.bios.version: R23ET71W (1.47 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CF004PGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76538 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.28
dmi.modalias:
dmi:bvnLENOVO:bvrR23ET71W(1.47):bd09/14/2023:br1.47:efr1.28:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
dmi.product.family: ThinkPad T14 Gen 3
dmi.product.name: 21CF004PGE
dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
dmi.product.version: ThinkPad T14 Gen 3
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+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 2045886] [NEW] Please merge 8.5.0-1 into noble
Public bug reported: tracking bug ** Affects: curl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2045886 Title: Please merge 8.5.0-1 into noble Status in curl package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2045886/+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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
The ubuntu-sponsors team has been subscribed to the bug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2039873 Title: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases Status in lxc package in Ubuntu: Confirmed Bug description: [ Impact ] LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release build we should have LXC_DEVEL=0. LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. Having LXC_DEVEL=1 makes problems for the users who want to build projects those are depend on liblxc from source (for example, LXD, go-lxc: https://github.com/canonical/lxd/pull/12420). Q: Why it was not a problem for so long? A: Because LXC API was stable for a long time, but recently we have extended liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). This change was developed properly to be backward compatible with the old versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro check VERSION_AT_LEAST (https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. [ Test Plan ] Install liblxc-dev package and check /usr/include/lxc/version.h file LXC_DEVEL should be 0 [ Where problems could occur ] Theoretically, build of a software which depends on liblxc-dev may start to fail if it assumes that LXC_DEVEL is 1. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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
