[Touch-packages] [Bug 1970015] Re: [Inspiron 5675, Realtek ALC3861, Green Headphone Out, Front] fails when unplugging and replugging the headphones
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1970015 Title: [Inspiron 5675, Realtek ALC3861, Green Headphone Out, Front] fails when unplugging and replugging the headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: Insert a headset to line-out jack. Expected results: System should detect line-out port and sound output through line-out jack. Actual results: Can't detect external headset via line-out jack. -- Every time that I unplug my headphones from my front plug and that I re-plug them, the system doesn't detect that they've been re-plugged. My solution so far has been to kill the pulseaudio process and to force alsa to reload manually in order to have my headphones detected back again. One other option is to reboot the system. When the headphones are not working, they do not show up in the sound settings. I've had this bug on Ubuntu 20.04, Ubuntu 21.10, Ubuntu 22.04, Linux Mint LMDE 5, Linux Mint 20.3 and on Fedora 35. On Windows 10 and AlmaLinux 8.5, I don't have this problem, so it is not a hardware issue. Edit: I have done some testing and I have realized that this issue only affects me when using a Linux kernel above version 5. I have just tried to run Ubuntu 18.04.1 (kernel 4.15) and I didn't run into the same issue. Meanwhile, on Ubuntu 18.04.6 (kernel 5.4), I have run into the same issue. AlmaLinux 8.5 runs on kernel 4.18, so it looks like the issue appeared with the version 5 of the Linux kernel, regardless of the distro being used. Edit 2: It really looks like the same type of issue as mentioned here. It says that the bug was fixed in kernel 4.13, but it looks like it reappeared again. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740971 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-40.45-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: emile 2624 F pulseaudio /dev/snd/pcmC1D0c: emile 2624 F...m pulseaudio /dev/snd/pcmC1D0p: emile 2624 F...m pulseaudio /dev/snd/controlC0: emile 2624 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 23 03:14:31 2022 InstallationDate: Installed on 2021-10-30 (174 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Headphone Out, Front Symptom_PulseAudioLog: avr 23 03:10:36 emile-Inspiron-5675 systemd[1394]: pulseaudio.service: Deactivated successfully. avr 23 03:10:46 emile-Inspiron-5675 systemd[1394]: pulseaudio.socket: Deactivated successfully. Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 5675, Realtek ALC3861, Green Headphone Out, Front] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2020 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 07PR60 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.4.1 dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd10/14/2020:br5.3:svnDellInc.:pnInspiron5675:pvr1.4.1:rvnDellInc.:rn07PR60:rvrA00:cvnDellInc.:ct3:cvr1.4.1:sku07EE: dmi.product.family: Inspiron dmi.product.name: Inspiron 5675 dmi.product.sku: 07EE dmi.product.version: 1.4.1 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.apport.crashdb.conf: 2022-01-08T17:09:20.988917 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1970015/+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 257135] Re: notify-send(1) can't replace an existing notification
** Changed in: libnotify (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/257135 Title: notify-send(1) can't replace an existing notification Status in libnotify package in Ubuntu: Confirmed Status in libnotify package in Debian: Fix Released Bug description: Binary package hint: libnotify-bin Ubuntu 8.04, libnotify-bin 0.4.4-3build1. notify-send(1) is very useful but it doesn't tell me the notification ID that's been created, nor does it let me specify that to replace an earlier notification. See http://www.galago- project.org/specs/notification/0.9/x408.html#command-notify, in particular the replaces_id parameter and the return value. I'd like to be able to use it something like id=$(notify-send --show-id foo) sleep 60 notify-send --replace $id bar This would be great for long-running shell scripts that are monitoring something. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/257135/+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 1959345] Re: vulkaninfo reports error
** Package changed: linux (Ubuntu) => mesa (Ubuntu) ** Changed in: mesa (Ubuntu) Status: Expired => Confirmed -- 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/1959345 Title: vulkaninfo reports error Status in mesa package in Ubuntu: Confirmed Bug description: Tracker says mesa-vulkan-drivers is not in Ubuntu!? mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 [installed] Ubuntu 18.04.6 LTS AMD Ryzen 7 2700x eight-core processor x 16 AMD Radeon rx 5700 xt apt-cache show says that vulkan-mesa-drivers provides vulkan-icd. find / -name vulkan-icd finds nothing vulkaninfo reports: ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd64.json There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in /usr/share/vulkan/icd.d/ Either the error is a false positive or I should have amd_icd64.json - and then maybe all the other problems with the GPU would go away! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gary 12435 F pulseaudio /dev/snd/controlC2: gary 12435 F pulseaudio /dev/snd/controlC0: gary 12435 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c InstallationDate: Installed on 2020-02-14 (740 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162 RelatedPackageVersions: linux-restricted-modules-5.4.0-99-generic N/A linux-backports-modules-5.4.0-99-generic N/A linux-firmware1.173.20 RfKill: Tags: bionic Uname: Linux 5.4.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F63d dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B450 MB dmi.product.name: B450 AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+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 1959345] [NEW] vulkaninfo reports error
You have been subscribed to a public bug: Tracker says mesa-vulkan-drivers is not in Ubuntu!? mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 [installed] Ubuntu 18.04.6 LTS AMD Ryzen 7 2700x eight-core processor x 16 AMD Radeon rx 5700 xt apt-cache show says that vulkan-mesa-drivers provides vulkan-icd. find / -name vulkan-icd finds nothing vulkaninfo reports: ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd64.json There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in /usr/share/vulkan/icd.d/ Either the error is a false positive or I should have amd_icd64.json - and then maybe all the other problems with the GPU would go away! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gary 12435 F pulseaudio /dev/snd/controlC2: gary 12435 F pulseaudio /dev/snd/controlC0: gary 12435 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c InstallationDate: Installed on 2020-02-14 (740 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162 RelatedPackageVersions: linux-restricted-modules-5.4.0-99-generic N/A linux-backports-modules-5.4.0-99-generic N/A linux-firmware1.173.20 RfKill: Tags: bionic Uname: Linux 5.4.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F63d dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B450 MB dmi.product.name: B450 AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: mesa (Ubuntu) Importance: Undecided Status: Expired ** Tags: apport-collected bionic -- vulkaninfo reports error https://bugs.launchpad.net/bugs/1959345 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. -- 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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts
Verified: root@146e5ef6a792:/# dpkg -l libc6 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--= ii libc6:armhf2.31-0ubuntu9.9 armhfGNU C Library: Shared libraries root@146e5ef6a792:/# file /lib/*/ld-2.31.so /lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=f0c9b30abd834697ef550b427b9de729d737b169, with debug_info, not stripped root@focal-vm:~# dpkg -l libc6 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--= ii libc6:amd642.31-0ubuntu9.9 amd64GNU C Library: Shared libraries root@focal-vm:~# file /lib/x86_64-linux-gnu/ld-2.31.so /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=4587364908de169dec62ffa538170118c1c3a078, stripped ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Released Status in gdb source package in Focal: Fix Released Status in glibc source package in Focal: Fix Committed Status in gdb source package in Groovy: Won't Fix Status in glibc source package in Groovy: Won't Fix Status in gdb source package in Hirsute: Won't Fix Status in glibc source package in Hirsute: Won't Fix Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Released Bug description: [Impact] * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not installed. [Test Plan] * Check that ld.so is not stripped on armhf: $ /lib/*/ld-2.31.so libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not stripped * Check that ld.so is stripped on amd64: $ file /lib/x86_64-linux-gnu/ld-2.31.so /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped [Where problems could occur] * The fix is not stripping ld.so on armhf. Not stripping it comes with a notable increase in file size and it may be performance critical 109K stripped vs 1.3M unstripped. Accidentally ld.so could be left unstripped on other architectures, but the test plan covers checking that, at least on amd64. Other than those not stripping ld.so should not cause any issue. [Original Bug Text] see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+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 1967038] Re: Add mic mute key for HP Elite x360 series
This bug was fixed in the package systemd - 249.11-0ubuntu3.1 --- systemd (249.11-0ubuntu3.1) jammy; urgency=medium [ Andy Chi ] * Add mic mute key support for HP Elite x360 series (LP: #1967038) Author: Andy Chi File: debian/patches/hwdb-Add-mic-mute-key-mapping-for-HP-Elite-x360.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=45e809103de9c356c75b692d35089e8770602617 -- Lukas Märdian Thu, 21 Apr 2022 14:14:26 +0200 ** Changed in: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1967038 Title: Add mic mute key for HP Elite x360 series Status in OEM Priority Project: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Committed Bug description: Upstream commit: https://github.com/systemd/systemd/commit/f09f6dc2c8f59b2b58159cc413b605a547c8646e [Impact] * User can't use mic mute key if they buy Elite x360 G9 series. [Test Plan] * Test mic mute key on Elite x360 G9 series. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1967038/+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 1949603] Re: iptables-save -c shows incorrect counters with iptables-nft
And s390x =(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1949603
Title:
iptables-save -c shows incorrect counters with iptables-nft
Status in iptables package in Ubuntu:
Fix Released
Status in iptables source package in Impish:
Fix Committed
Status in iptables source package in Jammy:
Fix Released
Bug description:
[Impact]
Starting with Impish I noticed that the kernel selftest xfrm_policy.sh
is always failing. Initially I thought it was a kernel issue, but
debugging further I found that the reason is that with Impish we're
using iptables-nft by default instead of iptables-legacy.
This test (./tools/testing/selftests/net/xfrm_policy.sh in the kernel
source directory) is creating a bunch of network namespaces and
checking the iptables counters for the defined policies, in particular
this is the interesting part:
check_ipt_policy_count()
{
ns=$1
ip netns exec $ns iptables-save -c |grep policy | ( read c rest
ip netns exec $ns iptables -Z
if [ x"$c" = x'[0:0]' ]; then
exit 0
elif [ x"$c" = x ]; then
echo "ERROR: No counters"
ret=1
exit 111
else
exit 1
fi
)
}
If I use iptables-nft the counters are never [0:0] as they should be,
so the test is failing. With iptables-legacy they are [0:0] and the
test is passing.
[Test case]
tools/testing/selftests/net/xfrm_policy.sh from the Linux kernel
source code.
[Fix]
Apply iptables upstream commit:
5f1fcace ("iptables-nft: fix -Z option")
In this way also with iptables-nft the counters are reported
correctly.
[Regression potential]
We may require other upstream commits now that the -Z option is
working properly with iptables-nft.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1949603/+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 1949603] Re: iptables-save -c shows incorrect counters with iptables-nft
The newly enabled autopkgtest appears to regress on i386 =/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1949603
Title:
iptables-save -c shows incorrect counters with iptables-nft
Status in iptables package in Ubuntu:
Fix Released
Status in iptables source package in Impish:
Fix Committed
Status in iptables source package in Jammy:
Fix Released
Bug description:
[Impact]
Starting with Impish I noticed that the kernel selftest xfrm_policy.sh
is always failing. Initially I thought it was a kernel issue, but
debugging further I found that the reason is that with Impish we're
using iptables-nft by default instead of iptables-legacy.
This test (./tools/testing/selftests/net/xfrm_policy.sh in the kernel
source directory) is creating a bunch of network namespaces and
checking the iptables counters for the defined policies, in particular
this is the interesting part:
check_ipt_policy_count()
{
ns=$1
ip netns exec $ns iptables-save -c |grep policy | ( read c rest
ip netns exec $ns iptables -Z
if [ x"$c" = x'[0:0]' ]; then
exit 0
elif [ x"$c" = x ]; then
echo "ERROR: No counters"
ret=1
exit 111
else
exit 1
fi
)
}
If I use iptables-nft the counters are never [0:0] as they should be,
so the test is failing. With iptables-legacy they are [0:0] and the
test is passing.
[Test case]
tools/testing/selftests/net/xfrm_policy.sh from the Linux kernel
source code.
[Fix]
Apply iptables upstream commit:
5f1fcace ("iptables-nft: fix -Z option")
In this way also with iptables-nft the counters are reported
correctly.
[Regression potential]
We may require other upstream commits now that the -Z option is
working properly with iptables-nft.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1949603/+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 1964401] Re: Software Sources/software-properties-qt privilege escalation not accepting password
*** This bug is a duplicate of bug 1965439 *** https://bugs.launchpad.net/bugs/1965439 ** This bug has been marked a duplicate of bug 1965439 software-properties-qt can no longer launch when called by pkexec -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1964401 Title: Software Sources/software-properties-qt privilege escalation not accepting password Status in plasma-discover package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) package version - apt-cache policy pkgname' plasma-discover: Installed: 5.24.2.1-0ubuntu1 software-properties-qt: Installed: 0.99.19 3) expected to happen * In Discover: Settings > Software Sources * opens a privilege escalation dialogue * enter user password * software-properties-qt opens 4) happened instead * In Discover: Settings > Software Sources * opens a privilege escalation dialogue * insert known-correct user password * **does not accept known-correct user password** # Additional Info Note: described behaviour is for a post 20.04->22.04 devel daily upgrade found during a QA Testcase. Behaviour exists, but has slightly different symptoms in a virgin live 22.04 daily session (see below) * launching from terminal works as expected sudo software-properties-qt ## process & errors - post 20.04->22.04 devel daily upgrade * running Discover from terminal $ plasma-discover * Settings > Software Sources gives error on terminal: > org.kde.kdesu: Daemon not safe (not sgid), not using it. * insert known-correct user password gives error on terminal: > kf.su: [ ./src/stubprocess.cpp : 225 ] Unknown request: "stop" > end * close password window gives error on terminal > Usage: /usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu [options] command > Runs a program with elevated privileges. > Options: > -h, --help Displays help on commandline options. > [...] ## process & errors - live Kubuntu 22.04 daily similar behaviour, hoever password-asking window never appears. Terminal errors differ from above: * Settings > Software Sources gives error on terminal: > org.kde.kdesu: Daemon not safe (not sgid), not using it. > > Don't need password!! > >kf.su: [./src/stubprocess.cpp : 255 ] Unknown request: "ok" --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-07 (2 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: plasma-discover 5.24.2.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy third-party-packages Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1964401/+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 1933491] Re: kmod add zstd support
# dpkg-query -W kmod kmod27-1ubuntu2 # modinfo ./zstd.ko.zst modinfo: ERROR: Module alias ./zstd.ko.zst not found. upgraded to new kmod: # dpkg-query -W kmod kmod27-1ubuntu2.1 # modinfo ./zstd.ko.zst filename: /lib/modules/5.4.0-109-generic/kernel/crypto/./zstd.ko.zst alias: crypto-zstd alias: zstd description:Zstd Compression Algorithm license:GPL srcversion: C007A20DBED7E012AF5A0A8 depends:zstd_compress retpoline: Y intree: Y name: zstd vermagic: 5.4.0-109-generic SMP mod_unload modversions sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:2E:88:51:F0:25:CE:CD:BB:F2:FC:76:4E:F5:71:F2:A4:3F:3E:DC:F3 sig_hashalgo: sha512 signature: 62:91:50:E8:5F:FA:96:05:E8:CA:F4:9F:03:0A:5A:56:04:02:37:2D: 06:56:A8:A7:40:02:95:61:78:5F:F3:73:8B:EB:EA:FB:62:F6:B1:B7: 68:4F:A7:87:88:44:E1:85:41:C9:ED:BB:CD:34:02:A1:3E:7A:9A:E8: D8:24:84:94:64:D3:9F:FE:A7:3A:91:10:F3:90:B1:E7:71:25:26:BA: B8:CE:B8:59:E1:B9:DD:C0:0C:82:E3:9B:96:CF:E5:DB:BD:8F:77:11: 87:E4:BB:BC:84:57:49:A3:D8:CE:D6:33:25:86:35:50:67:B5:0A:13: 26:08:4D:66:E9:97:70:B5:F6:87:69:D2:89:EA:2A:40:38:30:88:AA: AD:ED:6C:0A:51:1E:62:E4:F1:13:47:8F:0B:AF:FB:53:A9:74:82:52: 78:53:F2:8D:4D:DB:15:5C:76:4F:9A:77:C0:7F:6E:87:16:B3:DB:FD: C7:D6:C6:8E:14:D1:A6:F0:0B:03:4C:33:68:E8:75:29:93:E6:4F:AE: 43:6D:90:4D:32:4B:A1:42:C1:AD:99:7C:C3:E2:B9:48:E6:F5:0D:DF: 2F:09:C2:46:A6:98:55:47:16:92:EF:28:AB:41:9E:4D:E8:03:2C:21: AF:21:CD:13:1D:C5:A3:FE:03:99:12:03:88:9E:65:1A:82:85:2B:71: DD:EB:F8:7E:C3:B8:84:A1:AD:25:25:DC:FD:58:77:1A:CE:EA:F8:04: C2:E1:DF:AB:A1:17:00:26:96:E5:FA:3F:84:CC:98:ED:31:E2:A0:2F: E6:7D:20:13:D1:57:8C:AA:74:2D:04:7C:48:34:E0:7B:DF:3C:F6:66: 4D:7A:E9:EF:5D:ED:66:7D:87:D6:98:2F:F7:92:3F:C7:CD:16:7B:D0: CE:B4:5B:A3:D9:9A:79:72:23:47:49:E0:69:B2:ED:44:E8:7F:7C:D6: 12:BB:66:A7:5E:F6:0D:2C:9B:7B:DA:8E:76:A9:66:B1:71:44:12:30: 83:DB:09:EE:4C:28:93:BD:50:51:E5:67:C3:B3:79:1C:27:86:82:02: 21:B9:EB:59:54:99:A9:93:02:D3:32:F5:D0:43:05:62:ED:C6:E9:4B: F9:09:9D:40:A2:83:74:25:65:30:BF:59:3A:42:64:28:94:9C:34:79: 42:59:81:22:CE:D0:80:56:A4:65:F8:A0:11:20:0F:A9:F2:F6:52:8C: D1:04:F6:D8:09:D0:D4:66:6E:21:12:AB:68:FD:34:1C:59:AF:9F:E9: AD:5C:A5:6F:AC:51:80:41:4C:62:28:A1:51:5B:C9:E0:C1:17:44:F1: A2:92:1E:39:00:07:96:E6:90:D9:CC:94 ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1933491 Title: kmod add zstd support Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Focal: Fix Committed Status in kmod source package in Impish: Fix Released Status in kmod source package in Jammy: Fix Released Status in kmod package in Debian: New Bug description: [Impact] * To safe diskspace, upcoming devel series / hwe kernels may turn on zstd kernel module compression. Kmod since impish support zstd support. But in order to keep hwe kernels at parity, or allow inspecting jammy modules from focal host, it would be beneficial for kmod in focal to support zstd compressed modules. [Test Plan] * Pick any kernel module * Compress it with zstd: $ zstd *.ko * Check that modinfo can read it: $ modinfo *.ko.zst [Where problems could occur] * kmod will gain a new dependecy on libzstd1, however it should already be present, because dpkg in focal depends on libzstd1 already. * initramfs-tools already supports compressed modules, but in focal at the moment it does so in an inefficient manner (regresses bootspeed), this has been improved in https://launchpad.net/ubuntu/+source/initramfs-tools/0.140ubuntu8 and is yet to be SRUed into Focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1933491/+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 1969396] Re: Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout
Now I have tested a bit more back and forth, and here is a new attempt to describe the nature of the issue: Whether Right Alt works as the compose key or not depends mostly on where in the list of input sources the keyboard layout in effect is present. If the layout in effect is the first one in the list, Right Alt works fine as compose key. This is true whether Alternate Characters Key is switched off or set to "None". (No problem with "English (Dvorak, alt., intl.)" either, in other words, if that layout is first in the list of input sources.) If the layout in effect is further down in the list, Right Alt may or may not work as compose key. Not sure about the exact pattern here. As regards Alternate Characters Key, I notice a marginal impact. If the English (US) layout is not the first layout in the list, Right Alt works as compose key with that layout if Alternate Characters Key is switched off, but not if it's set to "None". It should be noted that English (US) does not set Right Alt to the 3rd level key by default. Steve, does the above description reflect your observations too? Over to the question whether this is a g-c-c bug to some extent. I still think that g-c-c sets sensible options, and that the unexpected behavior is rather an XKB issue. The reason why Alternate Characters Key sets "lv3:ralt_alt" is that it assumes that a user who picks something else but Right Alt wants to be able to use Right Alt as any Alt key. OTOH, given this issue wrt Right Alt as compose key, you can argue that g-c-c should better not provide Right Alt as a compose key option... ** Summary changed: - Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout + Right Alt not working reliably as compose key unless the layout in effect is first in the list of sources -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1969396 Title: Right Alt not working reliably as compose key unless the layout in effect is first in the list of sources Status in gnome-control-center package in Ubuntu: New Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: I noticed after upgrade from impish to jammy that my compose key is not working correctly. Going into gnome-control-center -> Keyboard, I see that 'Alternate Characters Key' and 'Compose Key' are both set to Right Alt. Setting Alternate Characters Key to None, and moving the Compose Key setting around between different options (and then back to Right Alt), the behavior of the Right Alt key is still AltGr and not Compose. From xev: KeyPress event, serial 37, synthetic NO, window 0x401, root 0x50e, subw 0x0, time 287242336, (310,502), root:(434,617), state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x401, root 0x50e, subw 0x0, time 287242456, (310,502), root:(434,617), state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XFilterEvent returns: False ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu12 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 18 16:01:10 2022 InstallationDate: Installed on 2019-12-23 (847 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-04-15 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969396/+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 1969960] Update Released
The verification of the Stable Release Update for base-files has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1969960 Title: Jammy's /etc/os-release missing LTS string in VERSION Status in base-files package in Ubuntu: Fix Committed Status in base-files source package in Jammy: Fix Released Bug description: [Description] In Jammy (base-files 12ubuntu4) we have: $ grep VERSION= /etc/os-release VERSION="22.04 (Jammy Jellyfish)" but expected is: VERSION="22.04 LTS (Jammy Jellyfish)" Compare with Focal: $ grep VERSION= /etc/os-release VERSION="20.04.4 LTS (Focal Fossa)" [Impact] Having VERSION without LTS is inconsistent with the previous LTS releases and is wrong, as the official name of the release is "22.04 LTS". This can confuse users. Any script relying on VERSION to detect if the Ubuntu version it is running on in an LTS won't be work as expected. [Test Plan] 1. grep VERSION= /etc/os-release 2. check that it is: VERSION="22.04 LTS (Jammy Jellyfish)" [Where problems could occur] Software already packaged in Jammy may already have adapted to the fact that VERSION doesn't have the LTS string in it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1969960/+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 1969960] Re: Jammy's /etc/os-release missing LTS string in VERSION
This bug was fixed in the package base-files - 12ubuntu4.1 --- base-files (12ubuntu4.1) jammy; urgency=medium * /etc/os-release: add missing LTS to VERSION (LP: #1969960) -- Paride Legovini Fri, 22 Apr 2022 16:34:19 +0200 ** Changed in: base-files (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1969960 Title: Jammy's /etc/os-release missing LTS string in VERSION Status in base-files package in Ubuntu: Fix Committed Status in base-files source package in Jammy: Fix Released Bug description: [Description] In Jammy (base-files 12ubuntu4) we have: $ grep VERSION= /etc/os-release VERSION="22.04 (Jammy Jellyfish)" but expected is: VERSION="22.04 LTS (Jammy Jellyfish)" Compare with Focal: $ grep VERSION= /etc/os-release VERSION="20.04.4 LTS (Focal Fossa)" [Impact] Having VERSION without LTS is inconsistent with the previous LTS releases and is wrong, as the official name of the release is "22.04 LTS". This can confuse users. Any script relying on VERSION to detect if the Ubuntu version it is running on in an LTS won't be work as expected. [Test Plan] 1. grep VERSION= /etc/os-release 2. check that it is: VERSION="22.04 LTS (Jammy Jellyfish)" [Where problems could occur] Software already packaged in Jammy may already have adapted to the fact that VERSION doesn't have the LTS string in it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1969960/+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 1969960] Re: Jammy's /etc/os-release missing LTS string in VERSION
... After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 base-files amd64 12ubuntu4.1 [62.8 kB] Fetched 62.8 kB in 1s (123 kB/s) The system does not support apt-btrfs-snapshot (Reading database ... 454507 files and directories currently installed.) Preparing to unpack .../base-files_12ubuntu4.1_amd64.deb ... Unpacking base-files (12ubuntu4.1) over (12ubuntu4) ... Setting up base-files (12ubuntu4.1) ... motd-news.service is a disabled or a static unit not running, not starting it. Processing triggers for cracklib-runtime (2.9.6-3.4build4) ... ... $ grep VERSION /etc/os-release VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1969960 Title: Jammy's /etc/os-release missing LTS string in VERSION Status in base-files package in Ubuntu: Fix Committed Status in base-files source package in Jammy: Fix Released Bug description: [Description] In Jammy (base-files 12ubuntu4) we have: $ grep VERSION= /etc/os-release VERSION="22.04 (Jammy Jellyfish)" but expected is: VERSION="22.04 LTS (Jammy Jellyfish)" Compare with Focal: $ grep VERSION= /etc/os-release VERSION="20.04.4 LTS (Focal Fossa)" [Impact] Having VERSION without LTS is inconsistent with the previous LTS releases and is wrong, as the official name of the release is "22.04 LTS". This can confuse users. Any script relying on VERSION to detect if the Ubuntu version it is running on in an LTS won't be work as expected. [Test Plan] 1. grep VERSION= /etc/os-release 2. check that it is: VERSION="22.04 LTS (Jammy Jellyfish)" [Where problems could occur] Software already packaged in Jammy may already have adapted to the fact that VERSION doesn't have the LTS string in it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1969960/+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 1267866] Re: usb audio: cannot get ctl value: req = 0x81, wValue = 0x0, wIndex = 0x1400, type = 3
The pulsemixer workaround works for me, thanks. I can reproduce the problem by changing the the Output Configuration to Analog Stereo input (yes that probably shouldn't be here to select). The problem then persists after a reboot. OS: Ubuntu 21.10 - Kernel 5.13.0-41 Device: Schiit - Fulla 3 USB Headphone Amp w/ Mic input Only syslog message is: "gsd-media-keys[1761]: Unable to get default sink" -- 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/1267866 Title: usb audio: cannot get ctl value: req = 0x81, wValue = 0x0, wIndex = 0x1400, type = 3 Status in alsa-driver package in Ubuntu: Expired Bug description: I typed in terminal: alsamixer Then I wanted to change the sound card (I have connected an external sound card via USB). I pressed F6, selected the external sound card and pressed enter. alsamixer crashed and outputed: cannot load mixer controls: Broken pipe My ALSA information is located at http://www.alsa- project.org/db/?f=1871c086b58a2965d18cfb38483794788187edfb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1267866/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
Can someone explain how to fix "0A0C0103:SSL routines::internal error" ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1970647] [NEW] notify-send exit code doesn't match result
Public bug reported: No error exit code is returned by notify-send on failure [ Test case ] 1. Run: jhbuild run env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo error 2. In a terminal "error" should be printed [ Regression potential ] Programs relying on notify-send may have errors when they did not. ** Affects: libnotify (Ubuntu) Importance: Medium Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1970647 Title: notify-send exit code doesn't match result Status in libnotify package in Ubuntu: In Progress Bug description: No error exit code is returned by notify-send on failure [ Test case ] 1. Run: jhbuild run env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo error 2. In a terminal "error" should be printed [ Regression potential ] Programs relying on notify-send may have errors when they did not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1970647/+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 537208] Re: pidgin crashed with SIGSEGV in notify_get_server_caps()
** Changed in: libnotify (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/537208 Title: pidgin crashed with SIGSEGV in notify_get_server_caps() Status in libnotify package in Ubuntu: Invalid Status in libnotify source package in Lucid: Won't Fix Bug description: Binary package hint: pidgin bug occurs after enable/disable notify applet ProblemType: Crash Architecture: i386 Date: Thu Mar 11 11:12:51 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/bin/pidgin InstallationMedia: Error: [Errno 13] Отказано в доступе: '/var/log/installer/media-info' Package: pidgin 1:2.6.6-1ubuntu4 ProcCmdline: pidgin ProcEnviron: SHELL=/bin/bash LANG=ru_UA.utf8 ProcVersionSignature: Ubuntu 2.6.32-16.25-generic SegvAnalysis: Segfault happened at: 0x16441cb :mov 0x8(%eax),%eax PC (0x016441cb) ok source "0x8(%eax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: pidgin StacktraceTop: notify_get_server_caps () from /usr/lib/libnotify.so.1 ?? () from /usr/lib/purple-2/pidgin-libnotify.so purple_plugin_load () from /usr/lib/libpurple.so.0 ?? () g_cclosure_marshal_VOID__STRING () Title: pidgin crashed with SIGSEGV in notify_get_server_caps() Uname: Linux 2.6.32-16-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare XsessionErrors: (polkit-gnome-authentication-agent-1:8260): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (bluetooth-applet:8262): Gtk-CRITICAL **: gtk_action_set_sensitive: assertion `GTK_IS_ACTION (action)' failed (gnome-terminal:8443): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/537208/+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 1255591] Re: [Feature request] notify-send option to change the "notify-send" app name that appears in all my notifications.
This was fixed in
https://gitlab.gnome.org/GNOME/libnotify/commit/b873c61ecc85c1a87c9471046f3d25ecd2446959
included in old revisions
** Changed in: libnotify (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libnotify in Ubuntu.
https://bugs.launchpad.net/bugs/1255591
Title:
[Feature request] notify-send option to change the "notify-send" app
name that appears in all my notifications.
Status in libnotify package in Ubuntu:
Fix Released
Bug description:
(I wasn't sure if feature requests counted as bug reports or
questions. My apologies if I guessed wrong. I also apologize if this
is the wrong place for a patch, but I couldn't find a repo to fork.)
I use notify-send in a number of shell scripts. I would like it to be
able to accurately report which script is sending the notification.
Instead I'm stuck with "notify-send" as the application responsible
for creating all the notifications.
I saw that the string "notify-send" appears exactly once in notify-
send.c. So I added a cli option, -l/--app-label, to change it.
Here's the patch:
```
128a129
> static char*app_label = NULL;
151a153,154
> {"app-label", 'l', 0, G_OPTION_ARG_STRING, &app_label,
> N_("Specifies the label shown in the notification
(default: notify-send)"), N_("APP_LABEL")},
223c226
< if (!notify_init ("notify-send"))
---
> if (!notify_init (app_label != NULL ? app_label : "notify-send"))
```
This is for libnotify-0.7.6 downloaded with apt-get source libnotify.
I figure the patch is trivial enough that the version probably doesn't
matter too much. I'd appreciate it if this functionality could make
it into libnotify, but I don't care if it's implemented with my patch
or some other method.
Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1255591/+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 1968845] Re: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot
Can confirm #10 works for me too. Can be confusing, but luckily I checked for this bug first. The upgrade will block on the message "Please reboot your system..." but after waiting some time it unblocked on its own. -- 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/1968845 Title: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot Status in dbus package in Ubuntu: Confirmed Bug description: Upgrading on a virtual machine from 20.04 to 22.04. I have had this happen twice now, I got one upgrade done without this bug. Basically the package installation stops at dbus package asking for a reboot as it was unable to upgrade as dbus-daemon was running. And rebooting at this stage obviously will cause a non-functioning system. Added a screenshot of the upgrade window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+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 1933491] Re: kmod add zstd support
initramfs-tools ADT test passed on retry. the kernel tests mentioned above are now for EOL kernels that have since all rolled to 5.13. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1933491 Title: kmod add zstd support Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Focal: Fix Committed Status in kmod source package in Impish: Fix Released Status in kmod source package in Jammy: Fix Released Status in kmod package in Debian: New Bug description: [Impact] * To safe diskspace, upcoming devel series / hwe kernels may turn on zstd kernel module compression. Kmod since impish support zstd support. But in order to keep hwe kernels at parity, or allow inspecting jammy modules from focal host, it would be beneficial for kmod in focal to support zstd compressed modules. [Test Plan] * Pick any kernel module * Compress it with zstd: $ zstd *.ko * Check that modinfo can read it: $ modinfo *.ko.zst [Where problems could occur] * kmod will gain a new dependecy on libzstd1, however it should already be present, because dpkg in focal depends on libzstd1 already. * initramfs-tools already supports compressed modules, but in focal at the moment it does so in an inefficient manner (regresses bootspeed), this has been improved in https://launchpad.net/ubuntu/+source/initramfs-tools/0.140ubuntu8 and is yet to be SRUed into Focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1933491/+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 1968581] Re: Invalid transition after update to 1.18.6-1
Lenovo-shipped EM7455, 1199:9079 Adding the symlink didn't solve the problem. I found that the qmicli was not installed ! After installing libqmi-utils package I could solve the problem. Does the upgrade to ubuntu 22.04 uninstalled me the libqmi-utils package? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1968581 Title: Invalid transition after update to 1.18.6-1 Status in modemmanager package in Ubuntu: Incomplete Bug description: Unable to connect. Log information: [1649685973.4066] device (cdc-wdm2): Activation: starting connection 'Sunrise Default 1' (78490efe-5f5f-4b6f-a951-399fca325d19) NetworkManager[1004]: [1649685973.4071] audit: op="connection-activate" uuid="78490efe-5f5f-4b6f-a951-399fca325d19" name="Sunrise Default 1" pid=3375 uid=1000 result="success" NetworkManager[1004]: [1649685973.4075] device (cdc-wdm2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4094] device (cdc-wdm2): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4122] device (cdc-wdm2): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4126] device (cdc-wdm2): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685978.4260] device (cdc-wdm2): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') ModemManager[9630]: [modem0] simple connect started... ModemManager[9630]: [modem0] simple connect state (3/8): enable ModemManager[9630]: [modem0] state changed (disabled -> enabling) ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] couldn't enable interface: 'Invalid transition' ModemManager[9630]: [modem0] state changed (enabling -> disabled) NetworkManager[1004]: [1649685978.6019] device (cdc-wdm2): state change: prepare -> disconnected (reason 'user-requested', sys-iface-state: 'managed') ModemManager[9630]: [modem0] simple connect started... ModemManager[9630]: [modem0] simple connect state (3/8): enable ModemManager[9630]: [modem0] state changed (disabled -> enabling) ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] Failure AModemManager[9630]: [modem0] couldn't enable interface: 'Invalid transition' ModemManager[9630]: [modem0] state changed (enabling -> disabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1968581/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
The workaround linked to in #11 has worked for me: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834/comments/7 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
The workaround from post #22 doesn't work for me too :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1970144] Re: [vmwgfx] Qt Creator windows don't render correctly, VMware 16, Ubuntu 22.04
In ubuntu20.04.4, this doesn't happen -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1970144 Title: [vmwgfx] Qt Creator windows don't render correctly, VMware 16, Ubuntu 22.04 Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: xdpyinfo name of display::0 version number:11.0 vendor string:The X.Org Foundation vendor release number:12201001 X.Org version: 1.22.1.1 maximum request size: 16777212 bytes motion buffer size: 256 bitmap unit, bit order, padding:32, LSBFirst, 32 image byte order:LSBFirst number of supported pixmap formats:7 supported pixmap formats: depth 1, bits_per_pixel 1, scanline_pad 32 depth 4, bits_per_pixel 8, scanline_pad 32 depth 8, bits_per_pixel 8, scanline_pad 32 depth 15, bits_per_pixel 16, scanline_pad 32 depth 16, bits_per_pixel 16, scanline_pad 32 depth 24, bits_per_pixel 32, scanline_pad 32 depth 32, bits_per_pixel 32, scanline_pad 32 keycode range:minimum 8, maximum 255 focus: None number of extensions:23 BIG-REQUESTS Composite DAMAGE DOUBLE-BUFFER DRI3 GLX Generic Event Extension MIT-SHM Present RANDR RECORD RENDER SHAPE SYNC X-Resource XC-MISC XFIXES XFree86-VidModeExtension XINERAMA XInputExtension XKEYBOARD XTEST XVideo default screen number:0 number of screens:1 screen #0: dimensions:3838x1781 pixels (1015x471 millimeters) resolution:96x96 dots per inch depths (7):24, 1, 4, 8, 15, 16, 32 root window id:0x2bb depth of root window:24 planes number of colormaps:minimum 1, maximum 1 default colormap:0x43 default number of colormap cells:256 preallocated pixels:black 0, white 16777215 options:backing-store WHEN MAPPED, save-unders NO largest cursor:3838x1781 current input event mask:0xda0030 EnterWindowMask LeaveWindowMask StructureNotifyMask SubstructureNotifyMask SubstructureRedirectMask PropertyChangeMask ColormapChangeMask ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 25 09:25:33 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2022-04-25 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=e6bcbb51-635a-42a1-ab99-75af8c14475f ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-
[Touch-packages] [Bug 1968581] Re: Invalid transition after update to 1.18.6-1
Which modem are you using? Also if it's a fcc unlock issue, then as document it's not a bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1968581 Title: Invalid transition after update to 1.18.6-1 Status in modemmanager package in Ubuntu: Incomplete Bug description: Unable to connect. Log information: [1649685973.4066] device (cdc-wdm2): Activation: starting connection 'Sunrise Default 1' (78490efe-5f5f-4b6f-a951-399fca325d19) NetworkManager[1004]: [1649685973.4071] audit: op="connection-activate" uuid="78490efe-5f5f-4b6f-a951-399fca325d19" name="Sunrise Default 1" pid=3375 uid=1000 result="success" NetworkManager[1004]: [1649685973.4075] device (cdc-wdm2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4094] device (cdc-wdm2): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4122] device (cdc-wdm2): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4126] device (cdc-wdm2): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685978.4260] device (cdc-wdm2): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') ModemManager[9630]: [modem0] simple connect started... ModemManager[9630]: [modem0] simple connect state (3/8): enable ModemManager[9630]: [modem0] state changed (disabled -> enabling) ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] couldn't enable interface: 'Invalid transition' ModemManager[9630]: [modem0] state changed (enabling -> disabled) NetworkManager[1004]: [1649685978.6019] device (cdc-wdm2): state change: prepare -> disconnected (reason 'user-requested', sys-iface-state: 'managed') ModemManager[9630]: [modem0] simple connect started... ModemManager[9630]: [modem0] simple connect state (3/8): enable ModemManager[9630]: [modem0] state changed (disabled -> enabling) ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] Failure AModemManager[9630]: [modem0] couldn't enable interface: 'Invalid transition' ModemManager[9630]: [modem0] state changed (enabling -> disabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1968581/+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 1940528] Re: curl 7.68 does not init OpenSSL correctly
1) downgraded openssl to 1.1.1f-1ubuntu2.9 such that it doesn't have double free fix that was released in https://launchpad.net/ubuntu/+source/openssl/1.1.1f-1ubuntu2.10 2) installed old pka module from commit b0f32fa05298bf9e3997ea43fc1c11b90e0d662f 3) installed focal-updates version of curl Observed double free core dump: # dpkg-query -W | grep -e 1.1.1f -e curl -e pka curl7.68.0-1ubuntu2.7 libcurl3-gnutls:arm64 7.68.0-1ubuntu2.7 libcurl4:arm64 7.68.0-1ubuntu2.7 libpka1:arm64 1.3-1 libssl-dev:arm641.1.1f-1ubuntu2.9 libssl1.1:arm64 1.1.1f-1ubuntu2.9 openssl 1.1.1f-1ubuntu2.9 # curl -o /dev/null https://start.ubuntu.com/connectivity-check.html % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance 100 576 100 5760 0 2117 0 --:--:-- --:--:-- --:--:-- 2117 double free or corruption (out) Aborted (core dumped) Upgraded to new curl: # dpkg-query -W | grep -e 1.1.1f -e curl -e pka curl7.68.0-1ubuntu2.8 libcurl3-gnutls:arm64 7.68.0-1ubuntu2.8 libcurl4:arm64 7.68.0-1ubuntu2.8 libpka1:arm64 1.3-1 libssl-dev:arm641.1.1f-1ubuntu2.9 libssl1.1:arm64 1.1.1f-1ubuntu2.9 openssl 1.1.1f-1ubuntu2.9 # curl -o /dev/null https://start.ubuntu.com/connectivity-check.html % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance 100 576 100 5760 0 1894 0 --:--:-- --:--:-- --:--:-- 1888 Observed success without any double-free or segfault in openssl. Although this particular issue has already been fixed in openssl, it still makes sense to release this update of curl which includes correct openssl engine API usage. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1940528 Title: curl 7.68 does not init OpenSSL correctly Status in curl package in Ubuntu: Fix Released Status in curl source package in Bionic: New Status in curl source package in Focal: Fix Committed Bug description: [Impact] * curl 7.68 does not correctly use OpenSSL 1.1.0+ api to init OpenSSL global state prior to executing any OpenSSL APIs. This may lead to duplicate engine initiation, which upon engine unload may cause use- after-free or double-free of any methods that engine installs. This has been fixed in curl 7.74 by correctly calling OpenSSL init api prior to any other calls to OpenSSL apis. [Test Plan] * This should be reproducible with any engines that allocate & register methods, and free them upon engine unload. Then use curl with openssl backend to test for corrupted stack. * I.e. on arm64, compile and configure pka engine from https://github.com/Mellanox/pka/commit/b0f32fa05298bf9e3997ea43fc1c11b90e0d662f (i.e. without the double-free protections proposed in https://github.com/Mellanox/pka/pull/37 ) on any arm64 hardware, there is no need for the engine to actually work or have access to anything, as the issue is reproducible when engine is enabled but cannot be effectively used. * curl any https website ... PKA_DEV: pka_dev_open_ring_vfio: error: failed to get ring 50 device name PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance 100 338 100 3380 0 3520 0 --:--:-- --:--:-- --:--:-- 3520 (exit status 0) is good output from fixed curl. Whereas: PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance 100 338 100 3380 0 1169 0 --:--:-- --:--:-- --:--:-- 1169 Segmentation fault (core dumped) (exit status non-zero) is bad output from currently broken curl. [Where problems could occur] * Correctly calling OpenSSL init function prior to any other OpenSSL apis change
[Touch-packages] [Bug 1968581] Re: Invalid transition after update to 1.18.6-1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: modemmanager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1968581 Title: Invalid transition after update to 1.18.6-1 Status in modemmanager package in Ubuntu: Incomplete Bug description: Unable to connect. Log information: [1649685973.4066] device (cdc-wdm2): Activation: starting connection 'Sunrise Default 1' (78490efe-5f5f-4b6f-a951-399fca325d19) NetworkManager[1004]: [1649685973.4071] audit: op="connection-activate" uuid="78490efe-5f5f-4b6f-a951-399fca325d19" name="Sunrise Default 1" pid=3375 uid=1000 result="success" NetworkManager[1004]: [1649685973.4075] device (cdc-wdm2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4094] device (cdc-wdm2): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4122] device (cdc-wdm2): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4126] device (cdc-wdm2): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685978.4260] device (cdc-wdm2): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') ModemManager[9630]: [modem0] simple connect started... ModemManager[9630]: [modem0] simple connect state (3/8): enable ModemManager[9630]: [modem0] state changed (disabled -> enabling) ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] couldn't enable interface: 'Invalid transition' ModemManager[9630]: [modem0] state changed (enabling -> disabled) NetworkManager[1004]: [1649685978.6019] device (cdc-wdm2): state change: prepare -> disconnected (reason 'user-requested', sys-iface-state: 'managed') ModemManager[9630]: [modem0] simple connect started... ModemManager[9630]: [modem0] simple connect state (3/8): enable ModemManager[9630]: [modem0] state changed (disabled -> enabling) ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] Failure AModemManager[9630]: [modem0] couldn't enable interface: 'Invalid transition' ModemManager[9630]: [modem0] state changed (enabling -> disabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1968581/+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 1969593] Re: rules to prevent non-root users from rebooting not taken into account
Additional information. Reboot is not authorized when the (non-root) user is connected via SSH. We got the following message: $ reboot Failed to set wall message, ignoring: Interactive authentication required. Failed to reboot system via logind: Access denied Failed to open initctl fifo: Permission non accordée Failed to talk to init daemon. The problem seems to only appear in graphical or TTY session. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1969593 Title: rules to prevent non-root users from rebooting not taken into account Status in policykit-1 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: On fresh Ubuntu Jammy installation, I add a "/etc/polkit-1/localauthority/90-mandatory.d/restriction.pkla" file with the following contents : [Disable power-off] Identity=unix-user:* Action=org.freedesktop.login1.power-off ResultActive=no ResultInactive=no ResultAny=no [Disable power-off when others are logged in] Identity=unix-user:* Action=org.freedesktop.login1.power-off-multiple-sessions ResultActive=no ResultInactive=no ResultAny=no [Disable_reboot] Identity=unix-user:* Action=org.freedesktop.login1.reboot ResultActive=no ResultInactive=no ResultAny=no [Disable_reboot_when_others_are_logged_in] Identity=unix-user:* Action=org.freedesktop.login1.reboot-multiple-sessions ResultActive=no ResultInactive=no ResultAny=no It must prevent non-root users from shutdowning and rebooting the system. But it only prevent shutdowning. Rebooting is still possible for a non-root user. We can see it using pkcheck command (as a non-root user) : $ pkcheck --action-id org.freedesktop.login1.power-off --process $PPID ; echo $? Not authorized. 1 $ pkcheck --action-id org.freedesktop.login1.reboot --process $PPID ; echo $? 0 As this problem can lead to unexpected reboot on multi-users systems (a disponibilty concern), I checked the "This bug is a security vulnerability" box. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: policykit-1 0.105-33 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 10:53:27 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1969593/+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 1902109]
(In reply to Dmitry V. Levin from comment #4)
> Just letting you know that we reverted commit
> 6b89c385d8bd0700b25bac2c2d0bebe68d5cc05d in our glibc build shortly after
> reporting this issue.
Reading rsync bug report, I really think that EOPNOTSUPP is the correct
error code to return in this case. The configure was done on a build
system where lchmod does work (since it has procps mounted). So I do not
fully agree this really characterizes as a regression.
And I don't think reverting lchmod support since propcs might be not
available is the correct approach, best option would try to ask kernel
to have proper syscall support which does not require userland hacks.
Rick Felker already sent a patch, but it seems to be stuck.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1902109
Title:
rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted
Status in GLibC:
Confirmed
Status in glibc package in Ubuntu:
Invalid
Status in rsync package in Ubuntu:
Triaged
Status in glibc source package in Groovy:
Invalid
Status in rsync source package in Groovy:
Won't Fix
Bug description:
Rsync in Ubuntu 20.10 fails when /proc isn't mounted, while it worked before.
This happens because AC_CHECK_FUNC(lchmod) returns "yes" in 20.10, while it
returned "no" before.
Steps to reproduce:
# Emulate /proc not being mounted
$ mount --bind / /mnt
$ chroot /mnt rsync -a /bin/ls .
rsync: [receiver] failed to set permissions on "/.ls.CDExhu": Operation not
supported (95)
rsync error: some files/attrs were not transferred (see previous errors)
(code 3) at main.c(1330) [sender=3.2.3]
I reported this issue upstream in
https://github.com/WayneD/rsync/issues/109 but the rsync developer
says it's a problem in libc, and it might well be.
Simple C code to reproduce the problem without rsync:
printf("lchmod returned: %d\n", lchmod("/tmp/ls", 0755));
If /tmp/ls is e.g. mode=0123, and needs to be changed, lchmod fails
when /proc isn't mounted, yet it succeeds if it is mounted.
Python had a similar issue, and they ended up avoiding
AC_CHECK_FUNC(lchmod) under Linux:
https://bugs.python.org/issue34652
https://github.com/python/cpython/commit/69e96910153219b0b15a18323b917bd74336d229#diff-49473dca262eeab3b4a43002adb08b4db31020d190caaad1594b47f1d5daa810R3140
```c
if test "$MACHDEP" != linux; then
AC_CHECK_FUNC(lchmod)
fi
```
So I'm not sure which package is causing the bug here. Should autoconf
return false? Should libc implement lchown without the bug? Or should
rsync skip lchmod under Linux, like python did?
To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1902109/+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 1902109]
Just letting you know that we reverted commit
6b89c385d8bd0700b25bac2c2d0bebe68d5cc05d in our glibc build shortly
after reporting this issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1902109
Title:
rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted
Status in GLibC:
Confirmed
Status in glibc package in Ubuntu:
Invalid
Status in rsync package in Ubuntu:
Triaged
Status in glibc source package in Groovy:
Invalid
Status in rsync source package in Groovy:
Won't Fix
Bug description:
Rsync in Ubuntu 20.10 fails when /proc isn't mounted, while it worked before.
This happens because AC_CHECK_FUNC(lchmod) returns "yes" in 20.10, while it
returned "no" before.
Steps to reproduce:
# Emulate /proc not being mounted
$ mount --bind / /mnt
$ chroot /mnt rsync -a /bin/ls .
rsync: [receiver] failed to set permissions on "/.ls.CDExhu": Operation not
supported (95)
rsync error: some files/attrs were not transferred (see previous errors)
(code 3) at main.c(1330) [sender=3.2.3]
I reported this issue upstream in
https://github.com/WayneD/rsync/issues/109 but the rsync developer
says it's a problem in libc, and it might well be.
Simple C code to reproduce the problem without rsync:
printf("lchmod returned: %d\n", lchmod("/tmp/ls", 0755));
If /tmp/ls is e.g. mode=0123, and needs to be changed, lchmod fails
when /proc isn't mounted, yet it succeeds if it is mounted.
Python had a similar issue, and they ended up avoiding
AC_CHECK_FUNC(lchmod) under Linux:
https://bugs.python.org/issue34652
https://github.com/python/cpython/commit/69e96910153219b0b15a18323b917bd74336d229#diff-49473dca262eeab3b4a43002adb08b4db31020d190caaad1594b47f1d5daa810R3140
```c
if test "$MACHDEP" != linux; then
AC_CHECK_FUNC(lchmod)
fi
```
So I'm not sure which package is causing the bug here. Should autoconf
return false? Should libc implement lchown without the bug? Or should
rsync skip lchmod under Linux, like python did?
To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1902109/+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 1902109]
I think there is no much glibc can do without proper kernel support [1].
[1] https://sourceware.org/pipermail/libc-alpha/2020-July/116513.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1902109
Title:
rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted
Status in GLibC:
Confirmed
Status in glibc package in Ubuntu:
Invalid
Status in rsync package in Ubuntu:
Triaged
Status in glibc source package in Groovy:
Invalid
Status in rsync source package in Groovy:
Won't Fix
Bug description:
Rsync in Ubuntu 20.10 fails when /proc isn't mounted, while it worked before.
This happens because AC_CHECK_FUNC(lchmod) returns "yes" in 20.10, while it
returned "no" before.
Steps to reproduce:
# Emulate /proc not being mounted
$ mount --bind / /mnt
$ chroot /mnt rsync -a /bin/ls .
rsync: [receiver] failed to set permissions on "/.ls.CDExhu": Operation not
supported (95)
rsync error: some files/attrs were not transferred (see previous errors)
(code 3) at main.c(1330) [sender=3.2.3]
I reported this issue upstream in
https://github.com/WayneD/rsync/issues/109 but the rsync developer
says it's a problem in libc, and it might well be.
Simple C code to reproduce the problem without rsync:
printf("lchmod returned: %d\n", lchmod("/tmp/ls", 0755));
If /tmp/ls is e.g. mode=0123, and needs to be changed, lchmod fails
when /proc isn't mounted, yet it succeeds if it is mounted.
Python had a similar issue, and they ended up avoiding
AC_CHECK_FUNC(lchmod) under Linux:
https://bugs.python.org/issue34652
https://github.com/python/cpython/commit/69e96910153219b0b15a18323b917bd74336d229#diff-49473dca262eeab3b4a43002adb08b4db31020d190caaad1594b47f1d5daa810R3140
```c
if test "$MACHDEP" != linux; then
AC_CHECK_FUNC(lchmod)
fi
```
So I'm not sure which package is causing the bug here. Should autoconf
return false? Should libc implement lchown without the bug? Or should
rsync skip lchmod under Linux, like python did?
To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1902109/+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 1970605] Re: New video recording feature in new screenshot tool crashes
Thank you for your bug report, could you do this $ apport-collect 1970605 after triggering the issue? also how did you report the issue (wondering how it ended up with 'xorg' as the source with no package set on launchpad) ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1970605 Title: New video recording feature in new screenshot tool crashes Status in gnome-shell package in Ubuntu: Incomplete Bug description: The new screenshot tool with the video recording feature keeps crashing every time I try to record a part of my screen or the whole screen. The red timer shows up for less than a second on the top right of my screen and then it disappears. I've tried restarting my PC but it doesn't fix it. I have also tried OBS Studio to see if it crashes there, but it doesn't. Only the new screenshot tool in Ubuntu 22.04 does it. Screenshotting works fine, only the video recording has a problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 27 13:40:04 2022 DistUpgraded: 2022-04-25 15:08:16,726 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.60.02, 5.15.0-25-generic, x86_64: installed nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP107 [GeForce GTX 1050 Ti] [1458:3733] InstallationDate: Installed on 2021-11-08 (169 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-25 (1 days ago) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970605/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
I applied comment #22 WA but it didn't work me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1970605] Re: New video recording feature in new screenshot tool crashes
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1970605 Title: New video recording feature in new screenshot tool crashes Status in xorg package in Ubuntu: New Bug description: The new screenshot tool with the video recording feature keeps crashing every time I try to record a part of my screen or the whole screen. The red timer shows up for less than a second on the top right of my screen and then it disappears. I've tried restarting my PC but it doesn't fix it. I have also tried OBS Studio to see if it crashes there, but it doesn't. Only the new screenshot tool in Ubuntu 22.04 does it. Screenshotting works fine, only the video recording has a problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 27 13:40:04 2022 DistUpgraded: 2022-04-25 15:08:16,726 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.60.02, 5.15.0-25-generic, x86_64: installed nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP107 [GeForce GTX 1050 Ti] [1458:3733] InstallationDate: Installed on 2021-11-08 (169 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-25 (1 days ago) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1970605/+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 1970605] [NEW] New video recording feature in new screenshot tool crashes
You have been subscribed to a public bug: The new screenshot tool with the video recording feature keeps crashing every time I try to record a part of my screen or the whole screen. The red timer shows up for less than a second on the top right of my screen and then it disappears. I've tried restarting my PC but it doesn't fix it. I have also tried OBS Studio to see if it crashes there, but it doesn't. Only the new screenshot tool in Ubuntu 22.04 does it. Screenshotting works fine, only the video recording has a problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 27 13:40:04 2022 DistUpgraded: 2022-04-25 15:08:16,726 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.60.02, 5.15.0-25-generic, x86_64: installed nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP107 [GeForce GTX 1050 Ti] [1458:3733] InstallationDate: Installed on 2021-11-08 (169 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-25 (1 days ago) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- New video recording feature in new screenshot tool crashes https://bugs.launchpad.net/bugs/1970605 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- 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 1894907] Re: FTBFS with sphinx 3.2
** Changed in: cyrus-sasl2 Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1894907 Title: FTBFS with sphinx 3.2 Status in Cyrus-sasl2: Fix Released Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in cyrus-sasl2 package in Debian: Fix Released Bug description: cyrus-sasl2 ships with a sphinx extension to build its documentation, and this extension was based on a very old sphinx version. It no longer builds with sphinx 3.2.1 from groovy, failing in several places: a) "NoUri" Extension error: Could not import extension sphinxlocal.builders.manpage (exception: cannot import name 'NoUri' from 'sphinx.environment' (/usr/lib/python3/dist-packages/sphinx/environment/__init__.py)) make[2]: *** [Makefile:1166: man/.sphinx-build.stamp] Error 2 make[2]: Leaving directory '/home/ubuntu/deb/cyrus-sasl2-2.1.27+dfsg/build-heimdal' make[1]: *** [Makefile:686: all-recursive] Error 1 make[1]: Leaving directory '/home/ubuntu/deb/cyrus-sasl2-2.1.27+dfsg/build-heimdal' make: *** [Makefile:556: all] Error 2 Debian has a bug report already at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=955095 b) MACRO_DEF Extension error: Could not import extension sphinxlocal.builders.manpage (exception: cannot import name 'MACRO_DEF' from 'sphinx.writers.manpage' (/usr/lib/python3/dist-packages/sphinx/writers/manpage.py)) make[4]: *** [Makefile:1166: man/.sphinx-build.stamp] Error 2 make[4]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal' make[3]: *** [Makefile:686: all-recursive] Error 1 make[3]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal' make[2]: *** [Makefile:556: all] Error 2 make[2]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal' dh_auto_build: error: cd build-heimdal && make -j4 sasldir=/usr/lib/x86_64-linux-gnu/sasl2 returned exit code 2 make[1]: *** [debian/rules:164: override_dh_auto_build] Error 25 make[1]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2' make: *** [debian/rules:122: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/1894907/+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 1970585] Re: Logic for PermitRootLogin in config script is flipped
Oh, I did just see the explanation in the postinst and templates file: Template: openssh-server/permit-root-login Type: boolean Default: true Description: Disable SSH password authentication for root? ** Changed in: openssh (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1970585 Title: Logic for PermitRootLogin in config script is flipped Status in openssh package in Ubuntu: Invalid Bug description: In the config script of openssh-server, the debconf database is updated with the values that are read from sshd_config. But if I'm not mistaken the yes/no logic is flipped: if [ "$permit_root_login" = yes ]; then db_set openssh-server/permit-root-login false else db_set openssh-server/permit-root-login true fi Discovered this in openssh-server 7.6p1-4ubuntu0.5 on Ubuntu 18.04.5 LTS. Checked that this is still unchcanged in 8.9p1-3 on jammy. I marked this a vulnerability as this might lead to unintended flipped settings of permitting root to log in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970585/+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 1968581] Re: Invalid transition after update to 1.18.6-1
There is a description of the problem here: https://modemmanager.org/docs/modemmanager/fcc-unlock/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1968581 Title: Invalid transition after update to 1.18.6-1 Status in modemmanager package in Ubuntu: New Bug description: Unable to connect. Log information: [1649685973.4066] device (cdc-wdm2): Activation: starting connection 'Sunrise Default 1' (78490efe-5f5f-4b6f-a951-399fca325d19) NetworkManager[1004]: [1649685973.4071] audit: op="connection-activate" uuid="78490efe-5f5f-4b6f-a951-399fca325d19" name="Sunrise Default 1" pid=3375 uid=1000 result="success" NetworkManager[1004]: [1649685973.4075] device (cdc-wdm2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4094] device (cdc-wdm2): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4122] device (cdc-wdm2): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4126] device (cdc-wdm2): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685978.4260] device (cdc-wdm2): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') ModemManager[9630]: [modem0] simple connect started... ModemManager[9630]: [modem0] simple connect state (3/8): enable ModemManager[9630]: [modem0] state changed (disabled -> enabling) ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] couldn't enable interface: 'Invalid transition' ModemManager[9630]: [modem0] state changed (enabling -> disabled) NetworkManager[1004]: [1649685978.6019] device (cdc-wdm2): state change: prepare -> disconnected (reason 'user-requested', sys-iface-state: 'managed') ModemManager[9630]: [modem0] simple connect started... ModemManager[9630]: [modem0] simple connect state (3/8): enable ModemManager[9630]: [modem0] state changed (disabled -> enabling) ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] Failure AModemManager[9630]: [modem0] couldn't enable interface: 'Invalid transition' ModemManager[9630]: [modem0] state changed (enabling -> disabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1968581/+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 1970585] Re: Logic for PermitRootLogin in config script is flipped
** Description changed: In the config script of openssh-server, the debconf database is updated with the values that are read from sshd_config. But if I'm not mistaken the yes/no logic is flipped: if [ "$permit_root_login" = yes ]; then - db_set openssh-server/permit-root-login false + db_set openssh-server/permit-root-login false else - db_set openssh-server/permit-root-login true + db_set openssh-server/permit-root-login true fi Discovered this in openssh-server 7.6p1-4ubuntu0.5 on Ubuntu 18.04.5 - LTS. Checked that this still unchcanged in 8.9p1-3 on jammy. + LTS. Checked that this is still unchcanged in 8.9p1-3 on jammy. I marked this a vulnerability as this might lead to unintended flipped settings of permitting root to log in. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1970585 Title: Logic for PermitRootLogin in config script is flipped Status in openssh package in Ubuntu: New Bug description: In the config script of openssh-server, the debconf database is updated with the values that are read from sshd_config. But if I'm not mistaken the yes/no logic is flipped: if [ "$permit_root_login" = yes ]; then db_set openssh-server/permit-root-login false else db_set openssh-server/permit-root-login true fi Discovered this in openssh-server 7.6p1-4ubuntu0.5 on Ubuntu 18.04.5 LTS. Checked that this is still unchcanged in 8.9p1-3 on jammy. I marked this a vulnerability as this might lead to unintended flipped settings of permitting root to log in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970585/+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 1970585] Re: Logic for PermitRootLogin in config script is flipped
** Information type changed from Private Security to Public Security ** Description changed: In the config script of openssh-server, the debconf database is updated with the values that are read from sshd_config. But if I'm not mistaken the yes/no logic is flipped: if [ "$permit_root_login" = yes ]; then - db_set openssh-server/permit-root-login false + db_set openssh-server/permit-root-login false else - db_set openssh-server/permit-root-login true + db_set openssh-server/permit-root-login true fi Discovered this in openssh-server 7.6p1-4ubuntu0.5 on Ubuntu 18.04.5 LTS. Checked that this still unchcanged in 8.9p1-3 on jammy. - I marked this a vulnerability as this might lead to unintend flipped + I marked this a vulnerability as this might lead to unintended flipped settings of permitting root to log in. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1970585 Title: Logic for PermitRootLogin in config script is flipped Status in openssh package in Ubuntu: New Bug description: In the config script of openssh-server, the debconf database is updated with the values that are read from sshd_config. But if I'm not mistaken the yes/no logic is flipped: if [ "$permit_root_login" = yes ]; then db_set openssh-server/permit-root-login false else db_set openssh-server/permit-root-login true fi Discovered this in openssh-server 7.6p1-4ubuntu0.5 on Ubuntu 18.04.5 LTS. Checked that this still unchcanged in 8.9p1-3 on jammy. I marked this a vulnerability as this might lead to unintended flipped settings of permitting root to log in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970585/+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 1747499] Re: 98-reboot-required and Interaction with livepatch
** Also affects: update-notifier (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1747499 Title: 98-reboot-required and Interaction with livepatch Status in unattended-upgrades package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Status in unattended-upgrades source package in Focal: New Status in update-notifier source package in Focal: New Bug description: [Impact] * If a system is using canonical livepatch, has it enabled, and patches are applied, it could be confusing for a user to receive a "system restart required" messages in the MOTD when logging in. * Livepatch is available on LTS releases. Thus, the users can be confused following a kernel update on 20.04. * The upload prevents update-notifier and unattended-ugprades hooks from adding "system restart"-related messages to motd when Livepatch is enabled. Livepatch, when enabled, already contributes to the motd message so there is no need to have duplicate (and sometimes contradictory) information. [Test Plan] * how to reproduce the bug: 1. Install and boot a 20.04 server VM 2. Make sure it runs a generic kernel (or another flavour that supports Livepatch) 3. Enable Livepatch using the following command: $ ua attach # replace by an actual contract token 4. Upgrade the kernel (if you are already running the latest available kernel update, you can install a different flavour) 5. Upon logging in again, the motd will show ***System restart required***. * other testing appropriate to perform before landing this update: * Making sure that the patch has no impact when livepatch is not enabled. * The motd should show ***System restart required*** after upgrading the kernel if livepatch is not enabled. [Where problems could occur] * The change updates a hook script in /etc/kernel/postinst.d/. Scripts in this directory are executing when upgrading / installing a kernel. If somehow the script is broken, it can prevent dpkg for succeeding when upgrading / installing the kernel. * If the implementation is wrong, we might end up "losing" the ***System restart required*** message when livepatch is disabled [Original bug description] If a system is using canonical livepatch, has it enabled, and patches are applied, it could be confusing for a user to receive a "system restart required" messages in the MOTD when logging in. That message, when present, is printed by 98-reboot-required which essentially just cats /var/run/reboot-required to stdout. That file is placed by packages that require a reboot so that they are properly used in their updated versions. Examples that come to mind are libc and the kernel. There is a secondary file that can be created which says which packages requested the reboot. That would be /var/run/reboot- required.pkgs Ideally that script should not print out the reboot required message if a) livepatch is installed and enabled; b) the only trigger for the reboot is a kernel update. For (a), one can use the command "ubuntu-advantage is-livepatch- enabled" and check $?. That is in the ubuntu-advantage-tools package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1747499/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
It's definitely the infrastructure that's using old TLS. As for the unsafe renegotiation, that happens because the server does not send a renegotiation_info extension in its ServerHello message. See https://datatracker.ietf.org/doc/html/rfc5746. See specifically section 4.1, which discusses client behavior. OpenSSL 3 defaults to the secure client behavior, which requires the server to support RFC5746. For the "0A0C0103:SSL routines::internal error" the issue is that these servers only offer TLS 1.1 or older, which uses MD5-SHA1 as digest in its signature algorithm. Due to recent collision attacks on SHA1, this no longer meets OpenSSL default level of security of 80 bits (see https://sha-mbles.github.io/, which reduced the chosen-prefix collision to 63.4 bits). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1970076] Re: "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade
Oh I assumed this was running s390x VM on s390x Host. @Ryan - is this s390x emulation on a non-s390x host? ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1970076 Title: "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade Status in openssh package in Ubuntu: Incomplete Bug description: This s390x VM has been upgraded to Jammy, including the host (qemu- system-s390x 1:6.2+dfsg-2ubuntu6). Now any attempt to use ssh, or any incoming sshd attempt immediately results in e.g.: ryan@s390x-dev:~$ ssh g...@github.com [ 433.672800] User process fault: interruption code 0011 ilc:3 in libc.so.6[3ffa6c0+1ca000] [ 433.672946] Failing address: 02aa0b84d000 TEID: 02aa0b84d800 [ 433.672977] Fault in primary space mode while using user ASCE. [ 433.673030] AS:02bc01c7 R3:087cc007 S:0798a000 P:0400 Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970076/+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 1970068] Re: L2TP+IPSec not working after upgrade to 22.04 LTS
*** This bug is a duplicate of bug 1951832 *** https://bugs.launchpad.net/bugs/1951832 ** This bug has been marked a duplicate of bug 1951832 xl2tpd "Can not find tunnel" in jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1970068 Title: L2TP+IPSec not working after upgrade to 22.04 LTS Status in network-manager package in Ubuntu: New Status in network-manager-l2tp package in Ubuntu: New Status in ppp package in Ubuntu: New Status in xl2tpd package in Ubuntu: New Bug description: In 20.04LTS i was able to connect to my work over the L2TP tunel. Now it seems like this in journald: kwi 24 01:00:37 nm-l2tp-service[11368]: xl2tpd started with pid 11433 kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Not looking for kernel SAref support. kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Using l2tp kernel support. kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: xl2tpd version xl2tpd-1.3.16 started on crushXnitro PID:11433 kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Written by Mark Spencer, Copyright (C) 1998, Adtran, Inc. kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Forked by Scott Balmos and David Stipp, (C) 2001 kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Inherited by Jeff McAdams, (C) 2002 kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Forked again by Xelerance (www.xelerance.com) (C) 2006-2016 kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Listening on IP address 0.0.0.0, port 49636 kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Connecting to host X.X.X.X, port 1701 kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Connection established to X.X.X.X, 1701. Local: 19994, Remote: 201 (ref=0/0). kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Calling on tunnel 19994 kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Call established with X.X.X.X, Local: 65441, Remote: 142, Serial: 1 (ref=0/0) kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: start_pppd: I'm running: kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "/usr/sbin/pppd" kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "plugin" kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "pppol2tp.so" kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "pppol2tp" kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "7" kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "passive" kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "nodetach" kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: ":" kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "file" kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "/run/nm-l2tp-bd8ac49b-a2e9-4094-91dc-17a13ce61ec8/ppp-options" kwi 24 01:00:37 pppd[11434]: Plugin pppol2tp.so loaded. kwi 24 01:00:37 pppd[11434]: Plugin /usr/lib/pppd/2.4.9/nm-l2tp-pppd-plugin.so loaded. kwi 24 01:00:37 pppd[11434]: pppd 2.4.9 started by root, uid 0 kwi 24 01:00:37 pppd[11434]: Using interface ppp0 kwi 24 01:00:37 pppd[11434]: Connect: ppp0 <--> kwi 24 01:00:37 pppd[11434]: Overriding mtu 1500 to 1400 kwi 24 01:00:37 pppd[11434]: Overriding mru 1500 to mtu value 1400 kwi 24 01:00:37 NetworkManager[1017]: [1650754837.9839] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/6) kwi 24 01:00:38 pppd[11434]: CHAP authentication succeeded kwi 24 01:00:38 charon[11397]: 10[KNL] interface ppp0 activated kwi 24 01:00:38 charon[11397]: 13[KNL] fe80::81ee:6717:6637:2084 appeared on ppp0 kwi 24 01:00:38 charon[11397]: 14[KNL] flags changed for fe80::81ee:6717:6637:2084 on ppp0 kwi 24 01:00:38 pppd[11434]: local LL address fe80::81ee:6717:6637:2084 kwi 24 01:00:38 pppd[11434]: remote LL address fe80::::00f0:0c0e kwi 24 01:00:38 charon[11397]: 16[KNL] 192.168.57.181 appeared on ppp0 kwi 24 01:00:38 NetworkManager[1017]: [1650754838.0741] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') kwi 24 01:00:38 charon[11397]: 08[KNL] 192.168.57.181 disappeared from ppp0 kwi 24 01:00:38 charon[11397]: 10[KNL] 192.168.57.181 appeared on ppp0 kwi 24 01:00:38 NetworkManager[1017]: [1650754838.0751] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') kwi 24 01:00:38 pppd[11434]: local IP address 192.168.57.181 kwi 24 01:00:38 pppd[11434]: remote IP address X.X.X.X kwi 24 01:00:38 pppd[11434]: primary DNS address 192.168.56.19 kwi 24 01:00:38 NetworkManager[1017]: [1650754838.0952] policy: set 'xyyyxyyyx' (ppp0) as default for IPv4 routing and DNS kwi 24 01:01:03 charon[11397]: 12[IKE] sending keep alive to 91.X.63.182[4500] kwi 24 01:01:23 charon[11397]: 15[IKE] sending keep alive to X.X.X.X[4500] kwi 24 01:01:38 NetworkManage
[Touch-packages] [Bug 1966849] Re: gzip exec format error under WSL
I download the file https://ftp.gnu.org/gnu/gzip/gzip-1.12.tar.gz I Untar it tar xvzf with ubuntu 20 I copy all the files to Ubuntu 22 I run the ./configure I run make I run sudo make install I exit the terminal I log in again and the new gzip 1.12 work very good -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1966849 Title: gzip exec format error under WSL Status in gzip: New Status in gzip package in Ubuntu: Confirmed Bug description: gzip version 1.10-4ubuntu3 fails to run under WSL1 on Windows 19044.1620, making WSL pretty much unusable. bash: /usr/bin/gzip: cannot execute binary file: Exec format error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gzip 1.10-4ubuntu3 ProcVersionSignature: Microsoft 4.4.0-19041.1237-Microsoft 4.4.35 Uname: Linux 4.4.0-19041-Microsoft x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 29 06:40:33 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/usr/bin/fish SourcePackage: gzip UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gzip/+bug/1966849/+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 1968135] Re: BTRFS root subvolume @ mounted always as readonly (... ro rootflags=subvol=@ ...) on Jammy beta
The ro flag should not be on booted system, unfortunately this bug passed to the release. This caused jammy LTS unusable if rootfs is on BTRFS (without workaround above). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1968135 Title: BTRFS root subvolume @ mounted always as readonly (... ro rootflags=subvol=@ ...) on Jammy beta Status in systemd package in Ubuntu: New Bug description: = Description = On Ubuntu Jammy Jellyfish (beta 220330) where root (/) is installed on single BTRFS formated partition (no LVM, no separate /boot), then root subvolume (subvol=@) is always mounted as read only. There is a kernel flag (ro) appended to GRUB configuration file /boot/grub/grub.cfg created by script /usr/sbin/update-grub during every kernel update. Only home subvolume (@home) remains mounted as rw according to fstab which is correct. Read-only mounted root (/) leads to many issues. Image: Jammy Beta (220330) = Steps to Reproduce = 1. Install Jammy Beta (220330) on EFI PC x86_64 GPT partitioning and select FS root (/) to one single BTRFS partition (where subvolumes @ and @home are created). There are only 3 partitions EFI system partition (/dev/sda1), one swap (sda2), and one BTRFS formated (/dev/sda3) for FS root (/). 2. Launch the kernel via the default grub entry (or look for kernel boot parameters pressing ) - root subvolume (@) is mounted as readonly. = Expected Results = root / should be mounted as rw (mount -v | grep @), there should be no (ro) flag in /proc/cmdline for FS root. It is possible to temporarily avoid this behaviour in /etc/defaul/grub: GRUB_CMDLINE_LINUX_DEFAULT="rw quiet splash" Then there still remains "ro" kernel parameter which is followed by "rw quiet splash" at the end. = Actual Results = in grub.cfg: linux /@/boot/vmlinuz-5.15.0-23-generic root=UUID=--... rootflags=subvol=@ ro quiet splash $vt_handoff in /proc/cmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic root=UUID=981dd6de-02fc-41a9-9e2a-09dbbc776b2b ro rootflags=subvol=@ quiet splash vt.handoff=7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1968135/+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 1722713] Re: Hud spams systeem-log with "No such interface 'com.canonical.dbusmenu' (Artful)
I'm on ubuntu 20.04 and I got a similar error. Is this the same issue? ``` Apr 27 14:59:33 hurlee-X510 hud-service[4254]: #033[31mvoid DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)#033[0m: "No such interface “com.canonical.dbusmenu” on object at path /org/ayatana/bamf/window/90253910" ``` My problem is Nemo file manager freezes a few seconds when I open a document file. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1722713 Title: Hud spams systeem-log with "No such interface 'com.canonical.dbusmenu' (Artful) Status in hud package in Ubuntu: Confirmed Bug description: For gtk-header apps, hud spams system-log like: #033[31mvoid DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)#033[0m: "No such interface 'com.canonical.dbusmenu' on object at path /org/ayatana/bamf/window/62914572" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1722713/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
Same issue here. Workarounded it by downgrading wpasupplicant from 2:2.10-6 to 2:2.9.0-21build1. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Triaged Status in wpa source package in Jammy: Triaged Bug description: WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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
