[Touch-packages] [Bug 1899797] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1899797 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- 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/1899797 Title: dns does not resolve some names after updating kernel from 4.15.0-117 to a newer sub_version like -118 or -121 Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: This morning i've got a kernel update. After that I could not send mails using thunderbird contacting my mail provider kontent.com. The last working system was: Linux server 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux I tried 4.15.0-118 and 4.15.0-121 but using these I could not resolve: smtp.kontent.com - but I could resolve www.google.de. So it seems that using the newer kernels 118 and 121 I can not resolve some but not all addresses. I returned to kernel 4.15.0-117 and everything works fine again. systemd-resolve --status Global DNS Servers: 172.30.30.1<--- this is an local router next to my "server" DNS Domain: ami.intranet DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (enp0s25) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 172.30.30.1 DNS Domain: ~. ami.intranet andreas@server:~$ host smtp.kontent.com smtp.kontent.com has address 81.88.40.61 doning the same with a newer kernel results in a "SERVERFAIL 2 error" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899797/+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 1899797] Re: dns does not resolve some names after updating kernel from 4.15.0-117 to a newer sub_version like -118 or -121
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1899797 Title: dns does not resolve some names after updating kernel from 4.15.0-117 to a newer sub_version like -118 or -121 Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: This morning i've got a kernel update. After that I could not send mails using thunderbird contacting my mail provider kontent.com. The last working system was: Linux server 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux I tried 4.15.0-118 and 4.15.0-121 but using these I could not resolve: smtp.kontent.com - but I could resolve www.google.de. So it seems that using the newer kernels 118 and 121 I can not resolve some but not all addresses. I returned to kernel 4.15.0-117 and everything works fine again. systemd-resolve --status Global DNS Servers: 172.30.30.1<--- this is an local router next to my "server" DNS Domain: ami.intranet DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (enp0s25) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 172.30.30.1 DNS Domain: ~. ami.intranet andreas@server:~$ host smtp.kontent.com smtp.kontent.com has address 81.88.40.61 doning the same with a newer kernel results in a "SERVERFAIL 2 error" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899797/+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 1854621] Re: ubuntu 20.04 daily boots with no background, selecting other background has warped picture
Ubuntu groovy daily 2020-10-14 (QA-test live) on - dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550) glitches are evident on wallpaper, but not always when it's changed, switch between two photos & 3 of 4 selects will have it glitched, 1 will not, glitches will also be different each time example of glitch is https://photos.app.goo.gl/yZoN34kFBM4UaLh7A I only saw glitches evident on wallpaper itself (background of desktop), NOT on any window opened, so effect is ~minor. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1854621 Title: ubuntu 20.04 daily boots with no background, selecting other background has warped picture Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu 20.04 daily - verified (check disc for defects) prior to boot. dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550) On booting, the 20.04 daily has no background when desktop is loaded? (ie. top panel is there, dock on left side on black screen) When changing background (to any already installed), they are warped when selected and made the bacground as if corrupted (but small image where selection is made looks valid). This issue may relate to video card [radeon] ubuntu@ubuntu:~$ sudo lshw -C video *-display:0 description: VGA compatible controller product: RV516 [Radeon X1300/X1550 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:16 memory:d000-dfff memory:fe9e-fe9e ioport:dc00(size=256) memory:c-d *-display:1 UNCLAIMED description: Display controller product: RV516 [Radeon X1300/X1550 Series] (Secondary) vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0.1 bus info: pci@:01:00.1 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress bus_master cap_list configuration: latency=0 resources: memory:fe9f-fe9f ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.440 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CasperVersion: 1.432 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 1 11:58:33 2019 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191128) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1854621/+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 1586528] Re: Avahi-daemon withdraws address record
Same issue - Dell Precision 7040 Oct 14 20:20:17 ubuntu-Wyse-7040 avahi-daemon[1363]: Withdrawing address record for 192.168.1.121 on enp0s31f6. Oct 14 20:20:17 ubuntu-Wyse-7040 avahi-daemon[1363]: Leaving mDNS multicast group on interface enp0s31f6.IPv4 with address 192.168.1.121. Oct 14 20:20:17 ubuntu-Wyse-7040 avahi-daemon[1363]: Interface enp0s31f6.IPv4 no longer relevant for mDNS. This happens both with DHCP and Static IP. Nothing of note appears to precede these log messages. kern.log does not have any relevant logs. Behavior is a dropped network every ~1.5 days. Did not have this problem with wifi, only when hardwired. Runs with no displays attached. Currently Ubuntu 19.10 - will be upgrading to 20.04 and will update if issue does not resolve -- 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/1586528 Title: Avahi-daemon withdraws address record Status in avahi package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: For some reason, if I leave my Ubuntu VM up for a prolonged period of time the machine will lose connection to the network. ip addr shows that the nic port no longer has an address and an examination of the syslog shows this: May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record for 10.0.2.15 on enp0s3. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast group on interface enp0s3.IPv4 with address 10.0.2.15. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no longer relevant for mDNS. for no known reason. The only reliable way to get the network to come back (that I have found) is a full reboot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 27 15:11:34 2016 InstallationDate: Installed on 2015-10-22 (218 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: avahi UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+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 1899878] Re: Python's test_ssl fails starting from Ubuntu 20.04
Sorry, this is the correct link: https://bugs.python.org/issue41561#msg378103 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1899878 Title: Python's test_ssl fails starting from Ubuntu 20.04 Status in openssl package in Ubuntu: New Bug description: Please take a look at https://bugs.python.org/issue41561. Developers who work on Python think that the issue is due to a change in Ubuntu 20.04 that is best described by https://bugs.python.org/issue41561#msg378089: "It sounds like a Debian/Ubuntu patch is breaking an assumption. Did somebody report the bug with Debian/Ubuntu maintainers of OpenSSL already? Fedora also configures OpenSSL with minimum protocol version of TLS 1.2. The distribution does it in a slightly different way that makes the restriction discoverable and that is compatible with Python's test suite." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1899878/+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 1899878] [NEW] Python's test_ssl fails starting from Ubuntu 20.04
Public bug reported: Please take a look at https://bugs.python.org/issue41561. Developers who work on Python think that the issue is due to a change in Ubuntu 20.04 that is best described by https://bugs.python.org/issue41561#msg378089: "It sounds like a Debian/Ubuntu patch is breaking an assumption. Did somebody report the bug with Debian/Ubuntu maintainers of OpenSSL already? Fedora also configures OpenSSL with minimum protocol version of TLS 1.2. The distribution does it in a slightly different way that makes the restriction discoverable and that is compatible with Python's test suite." ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: python test-ssl ubuntu-20.04 ** Bug watch added: Python Roundup #41561 http://bugs.python.org/issue41561 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1899878 Title: Python's test_ssl fails starting from Ubuntu 20.04 Status in openssl package in Ubuntu: New Bug description: Please take a look at https://bugs.python.org/issue41561. Developers who work on Python think that the issue is due to a change in Ubuntu 20.04 that is best described by https://bugs.python.org/issue41561#msg378089: "It sounds like a Debian/Ubuntu patch is breaking an assumption. Did somebody report the bug with Debian/Ubuntu maintainers of OpenSSL already? Fedora also configures OpenSSL with minimum protocol version of TLS 1.2. The distribution does it in a slightly different way that makes the restriction discoverable and that is compatible with Python's test suite." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1899878/+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 1899853] Re: Screen freezing
Does the problem only happen when playing video? I can see the Discord snap is flooding your system log, which can cause freezes (usually every 5 seconds) when the kernel needs to sync/flush to disk. So please try uninstalling the Discord snap and tell us if the situation improves. If the problem keeps happening then please run 'top' to check for any high CPU users, and please also run (while the problem is happening): journalctl -b0 > journal.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1899853 Title: Screen freezing Status in Ubuntu: Incomplete Bug description: The graphics keeps freezing/sticking for 500 milliseconds to 1 second every 10 seconds roughly and its annoying when watching videos ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 00:18:02 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:398e] InstallationDate: Installed on 2020-10-14 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81EU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5c4e139a-7254-47e5-acee-d795bd1da00d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7PCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 530S-14IKB dmi.modalias: dmi:bvnLENOVO:bvr7PCN43WW:bd11/28/2019:svnLENOVO:pn81EU:pvrLenovoideapad530S-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14IKB: dmi.product.family: ideapad 530S-14IKB dmi.product.name: 81EU dmi.product.sku: LENOVO_MT_81EU_BU_idea_FM_ideapad 530S-14IKB dmi.product.version: Lenovo ideapad 530S-14IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1899853/+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 1899766] Re: Xorg freeze after selecting large cursor
This is going to confuse the situation but your kernel log CurrentDmesg.txt shows the kernel keeps crashing in the video4linux webcam code. I don't *think* that's related to this bug, but it is filling your kernel log with crash reports. As for this bug... Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Tags added: nvidia -- 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/1899766 Title: Xorg freeze after selecting large cursor Status in nvidia-graphics-drivers-435 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: After selecting the largest cursor in accessibility settings, the whole system froze. I had to use Magic SysRq to reboot the system. After reboot, the login screen was OK but after logging in it would immediately freeze again. Workaround: from login screen, switch to a VT with Ctrl-F2, log in and run dconf reset /org/gnome/desktop/interface/cursor-size I was playing with the cursor size because I see different cursor sizes in different apps and it was annoying me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 11:25:23 2020 DistUpgraded: 2020-05-02 16:08:06,720 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d] Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d] InstallationDate: Installed on 2018-12-11 (672 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-02 (164 days ago) dmi.bios.date: 07/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.1:bd07/09/2020:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
[Touch-packages] [Bug 1899218] Re: Incorrect warning from apparmor_parser on force complained profiles
This bug was fixed in the package apparmor - 3.0.0-0ubuntu1 --- apparmor (3.0.0-0ubuntu1) groovy; urgency=medium [ Alex Murray ] * Update to the final AppArmor 3.0 upstream release - d/apparmor.install: + install new aa-features-abi binary to /usr/bin - d/apparmor.manpages: + install new aa-features-abi.1 man page - d/apparmor-profiles.install: + install new usr.lib.dovecot.script-login + adjust for renamed postfix profiles - d/tests/test-installed: + include libraries/ in workdir so tests have access to private headers - Drop the following patches that were originally backported from upstream but are now incorporated in the final release: + d/p/parser-fix_cap_match.patch + d/p/policy-provide-example-and-base-abi-to-pin-pre-3.0-p.patch + d/p/parser-add-abi-warning-flags.patch + d/p/fix-tests-regression-apparmor-prologue-inc-settest.patch + d/p/fix-automatic-adding-of-rule-for-change-hat-iface.patch + d/p/fix-parser-to-emit-proc-attr-access-for-all-situations.patch + d/p/fix-change-profile-stack-abstraction.patch + d/p/ubuntu/stop-loading-snapd-profiles.patch [ Emilia Torino ] * d/control: adjust apparmor-notify to depends on python3-psutil and python3-apparmor (LP: #1899046) [ Steve Beattie ] * d/p/u/parser-Fix-warning-message-when-complain-mode-is-for.patch: Provide better message about caching not happening due to a profile being in force-complain mode. (LP: #1899218) -- Alex Murray Sun, 11 Oct 2020 16:26:32 -0700 ** Changed in: apparmor (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 apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1899218 Title: Incorrect warning from apparmor_parser on force complained profiles Status in apparmor package in Ubuntu: Fix Released Bug description: apparmor_parser on a force complained profile produces an incorrect warning message: $ sudo apparmor_parser -rW /etc/apparmor.d/usr.sbin.sssd Warning: found usr.sbin.sssd in /etc/apparmor.d/force-complain, forcing complain mode Warning from /etc/apparmor.d/usr.sbin.sssd (/etc/apparmor.d/usr.sbin.sssd line 54): Warning failed to create cache: usr.sbin.sssd Even though not generating the cache at all is expected, the warning should describe caching is disabled for force complained profiles instead of failure to create it. $ lsb_release -rd Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 $ apt-cache policy apparmor apparmor: Installed: 3.0.0~beta1-0ubuntu6 Candidate: 3.0.0~beta1-0ubuntu6 Version table: *** 3.0.0~beta1-0ubuntu6 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1899218/+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 1899046] Re: /usr/bin/aa-notify:ModuleNotFoundError:/usr/bin/aa-notify@39
This bug was fixed in the package apparmor - 3.0.0-0ubuntu1 --- apparmor (3.0.0-0ubuntu1) groovy; urgency=medium [ Alex Murray ] * Update to the final AppArmor 3.0 upstream release - d/apparmor.install: + install new aa-features-abi binary to /usr/bin - d/apparmor.manpages: + install new aa-features-abi.1 man page - d/apparmor-profiles.install: + install new usr.lib.dovecot.script-login + adjust for renamed postfix profiles - d/tests/test-installed: + include libraries/ in workdir so tests have access to private headers - Drop the following patches that were originally backported from upstream but are now incorporated in the final release: + d/p/parser-fix_cap_match.patch + d/p/policy-provide-example-and-base-abi-to-pin-pre-3.0-p.patch + d/p/parser-add-abi-warning-flags.patch + d/p/fix-tests-regression-apparmor-prologue-inc-settest.patch + d/p/fix-automatic-adding-of-rule-for-change-hat-iface.patch + d/p/fix-parser-to-emit-proc-attr-access-for-all-situations.patch + d/p/fix-change-profile-stack-abstraction.patch + d/p/ubuntu/stop-loading-snapd-profiles.patch [ Emilia Torino ] * d/control: adjust apparmor-notify to depends on python3-psutil and python3-apparmor (LP: #1899046) [ Steve Beattie ] * d/p/u/parser-Fix-warning-message-when-complain-mode-is-for.patch: Provide better message about caching not happening due to a profile being in force-complain mode. (LP: #1899218) -- Alex Murray Sun, 11 Oct 2020 16:26:32 -0700 ** Changed in: apparmor (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 apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1899046 Title: /usr/bin/aa-notify:ModuleNotFoundError:/usr/bin/aa-notify@39 Status in apparmor package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apparmor. This problem was most recently seen with package version 3.0.0~beta1-0ubuntu6, the problem page at https://errors.ubuntu.com/problem/69bb6832fe7b294bd7e2d75970fdc903f412c409 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1899046/+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 1899857] Re: [SRU] alsa-lib: support the enum value settings both in "" and in ''
This is the debdiff for focal. thx. ** Patch added: "alsa-lib_1.2.2-2.1ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1899857/+attachment/5422370/+files/alsa-lib_1.2.2-2.1ubuntu3.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1899857 Title: [SRU] alsa-lib: support the enum value settings both in "" and in '' Status in HWE Next: New Status in alsa-lib package in Ubuntu: In Progress Status in alsa-lib source package in Focal: In Progress Status in alsa-lib source package in Groovy: In Progress Bug description: [Impact] Recently the ucm added some amixer settings, like this one: cset "name='rt711 ADC 23 Mux' 'MIC2'" This setting is needed for Dell soundwire audio machines, and only this setting is set correctly, the headset-mic could work. And we already backported this ucm to focal. But the alsa-lib ctl parse doesn't support the enum value in the '' yet, so this amixer setting can't be set correctly under current focal and groovy, we need to backport a patch from alsa-lib master branch. [Fix] Backport a patch from upstream, this patch is not in the groovy yet (not in the alsa-lib v1.2.3.2), so both groovy and focal need this patch. [Test Case] On the Dell soundwire audio machine, run alsactl init, then check if the amixer "rt711 ADC 23 Mux" is set to "MIC2" or not, if it is set correctly, it means the alsalib enum ctl parse support both "" and '' now. [Regression Risk] This could introduce failure on setting enum amixer settings, users will experience the failure of audio device like the speaker can't output sound, the mic can't record sound. But this possibility is very low since we have tested this SRU on many LENOVO and Dell machines (with and without soundwire audio), all worked as fine as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899857/+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 1899857] Re: [SRU] alsa-lib: support the enum value settings both in "" and in ''
This is the debdiff for groovy. thx. ** Description changed: - This bug is for tracking purpose. + [Impact] + Recently the ucm added some amixer settings, like this one: + cset "name='rt711 ADC 23 Mux' 'MIC2'" + This setting is needed for Dell soundwire audio machines, and only + this setting is set correctly, the headset-mic could work. And we + already backported this ucm to focal. But the alsa-lib ctl parse + doesn't support the enum value in the '' yet, so this amixer setting + can't be set correctly under current focal and groovy, we need to + backport a patch from alsa-lib master branch. + + [Fix] + Backport a patch from upstream, this patch is not in the groovy + yet (not in the alsa-lib v1.2.3.2), so both groovy and focal need this + patch. + + [Test Case] + On the Dell soundwire audio machine, run alsactl init, then check if + the amixer "rt711 ADC 23 Mux" is set to "MIC2" or not, if it is set + correctly, it means the alsalib enum ctl parse support both "" and '' + now. + + + [Regression Risk] + This could introduce failure on setting enum amixer settings, users + will experience the failure of audio device like the speaker can't output + sound, the mic can't record sound. But this possibility is very low since + we have tested this SRU on many LENOVO and Dell machines (with and without + soundwire audio), all worked as fine as before. ** Patch added: "alsa-lib_1.2.3.2-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1899857/+attachment/5422368/+files/alsa-lib_1.2.3.2-1ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1899857 Title: [SRU] alsa-lib: support the enum value settings both in "" and in '' Status in HWE Next: New Status in alsa-lib package in Ubuntu: In Progress Status in alsa-lib source package in Focal: In Progress Status in alsa-lib source package in Groovy: In Progress Bug description: [Impact] Recently the ucm added some amixer settings, like this one: cset "name='rt711 ADC 23 Mux' 'MIC2'" This setting is needed for Dell soundwire audio machines, and only this setting is set correctly, the headset-mic could work. And we already backported this ucm to focal. But the alsa-lib ctl parse doesn't support the enum value in the '' yet, so this amixer setting can't be set correctly under current focal and groovy, we need to backport a patch from alsa-lib master branch. [Fix] Backport a patch from upstream, this patch is not in the groovy yet (not in the alsa-lib v1.2.3.2), so both groovy and focal need this patch. [Test Case] On the Dell soundwire audio machine, run alsactl init, then check if the amixer "rt711 ADC 23 Mux" is set to "MIC2" or not, if it is set correctly, it means the alsalib enum ctl parse support both "" and '' now. [Regression Risk] This could introduce failure on setting enum amixer settings, users will experience the failure of audio device like the speaker can't output sound, the mic can't record sound. But this possibility is very low since we have tested this SRU on many LENOVO and Dell machines (with and without soundwire audio), all worked as fine as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899857/+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 1899857] [NEW] [SRU] alsa-lib: support the enum value settings both in "" and in ''
Public bug reported: This bug is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: alsa-lib (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: alsa-lib (Ubuntu Focal) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: alsa-lib (Ubuntu Groovy) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Tags: oem-priority originate-from-1894184 somerville ** Package changed: alsa-utils (Ubuntu) => alsa-lib (Ubuntu) ** Also affects: alsa-lib (Ubuntu Groovy) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Also affects: alsa-lib (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: alsa-lib (Ubuntu Focal) Importance: Undecided => High ** Changed in: alsa-lib (Ubuntu Groovy) Importance: Undecided => High ** Changed in: alsa-lib (Ubuntu Focal) Assignee: (unassigned) => Hui Wang (hui.wang) ** Tags added: oem-priority originate-from-1894184 somerville ** Changed in: alsa-lib (Ubuntu Focal) Status: New => In Progress ** Changed in: alsa-lib (Ubuntu Groovy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1899857 Title: [SRU] alsa-lib: support the enum value settings both in "" and in '' Status in HWE Next: New Status in alsa-lib package in Ubuntu: In Progress Status in alsa-lib source package in Focal: In Progress Status in alsa-lib source package in Groovy: In Progress Bug description: This bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899857/+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 1899853] Re: Screen freezing
** Description changed: - The screen keeps freezing for less than 5 milliseconds approximately and - its annoying when watching videos + The screen keeps freezing for 500 milliseconds to 1 second approximately + and its annoying when watching videos ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 00:18:02 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: - Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) -Subsystem: Lenovo UHD Graphics 620 [17aa:398e] + Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) + Subsystem: Lenovo UHD Graphics 620 [17aa:398e] InstallationDate: Installed on 2020-10-14 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81EU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5c4e139a-7254-47e5-acee-d795bd1da00d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7PCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 530S-14IKB dmi.modalias: dmi:bvnLENOVO:bvr7PCN43WW:bd11/28/2019:svnLENOVO:pn81EU:pvrLenovoideapad530S-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14IKB: dmi.product.family: ideapad 530S-14IKB dmi.product.name: 81EU dmi.product.sku: LENOVO_MT_81EU_BU_idea_FM_ideapad 530S-14IKB dmi.product.version: Lenovo ideapad 530S-14IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Description changed: - The screen keeps freezing for 500 milliseconds to 1 second approximately - and its annoying when watching videos + The screen keeps freezing/sticking for 500 milliseconds to 1 second + every 10 seconds roughly and its annoying when watching videos ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 00:18:02 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:398e] InstallationDate: Installed on 2020-10-14 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81EU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5c4e139a-7254-47e5-acee-d795bd1da00d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7PCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 530S-14IKB dmi.modalias: dmi:bvnLENOVO:bvr7PCN43WW:bd11/28/2019:svnLENOVO:pn81EU:pvrLenovoideapad530S-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14IKB: dmi.product.family: ideapad 530S-14IKB dmi.product.name: 81EU dmi.product.sku: LENOVO_MT_81EU_BU_idea_FM_ideapad 530S-14IKB dmi.product.version: Lenovo ideapad 530S-14IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2
[Touch-packages] [Bug 1899853] Re: Screen freezing
** 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/1899853 Title: Screen freezing Status in xorg package in Ubuntu: New Bug description: The screen keeps freezing for less than 5 milliseconds approximately and its annoying when watching videos ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 00:18:02 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:398e] InstallationDate: Installed on 2020-10-14 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81EU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5c4e139a-7254-47e5-acee-d795bd1da00d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7PCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 530S-14IKB dmi.modalias: dmi:bvnLENOVO:bvr7PCN43WW:bd11/28/2019:svnLENOVO:pn81EU:pvrLenovoideapad530S-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14IKB: dmi.product.family: ideapad 530S-14IKB dmi.product.name: 81EU dmi.product.sku: LENOVO_MT_81EU_BU_idea_FM_ideapad 530S-14IKB dmi.product.version: Lenovo ideapad 530S-14IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1899853/+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 1899764] Re: [Realtek ALC257][Lenovo T14 Gen1] Internal mic or headset mic not detected
** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- 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/1899764 Title: [Realtek ALC257][Lenovo T14 Gen1] Internal mic or headset mic not detected Status in alsa-driver package in Ubuntu: Incomplete Bug description: Hello, I've received a brand new Lenovo T14 Gen 1 (Intel), that suffers of some incompatibilities with Ubuntu. The internal mic is not detected (only analog input is displayed). And when a headset is plug, only the output works. I've tried lots of alsa-base.conf snd-hda-intel overrides without success. Tested on U18 and U20. > uname -a Linux julien-ThinkPad-T14-Gen-1 5.9.0-050900-generic #202010112230 SMP Sun Oct 11 22:34:01 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (tried with stock kernel and kernel-oem too) > arecord -l Liste des Périphériques Matériels CAPTURE carte 0: PCH [HDA Intel PCH], périphérique 0: ALC257 Analog [ALC257 Analog] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 2: ALC257 Alt Analog [ALC257 Alt Analog] Sous-périphériques: 2/2 Sous-périphérique #0: subdevice #0 Sous-périphérique #1: subdevice #1 > cat /proc/asound/card0/codec\#0 https://gist.github.com/julienlafont-tabmo/4ba9311bbb1d3d918532279d7578ba28 > hdajackretask (default configuration) - Internal speaker Ox14 - Black headphone, Right Side, 0x21 - All others: not connected > alsa-info http://alsa-project.org/db/?f=a5af631628bef97a85cace2574b7c6694037130a > alba-base.conf settings tried without success: options snd-hda-intel model=laptop-dmic -- options snd-hda-intel dmic_detect=0 options snd-hda-intel index=0 model=laptop-dmic -- options snd-hda-intel dmic_detect=0 options snd-hda-intel index=1 model=laptop-dmic -- options snd-hda-intel model=auto -- options snd-hda-intel model=headset-mic Do you have some idea to make the mic working? Bests, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1899764/+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 1899853] [NEW] Screen freezing
You have been subscribed to a public bug: The screen keeps freezing for less than 5 milliseconds approximately and its annoying when watching videos ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 00:18:02 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:398e] InstallationDate: Installed on 2020-10-14 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81EU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5c4e139a-7254-47e5-acee-d795bd1da00d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7PCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 530S-14IKB dmi.modalias: dmi:bvnLENOVO:bvr7PCN43WW:bd11/28/2019:svnLENOVO:pn81EU:pvrLenovoideapad530S-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14IKB: dmi.product.family: ideapad 530S-14IKB dmi.product.name: 81EU dmi.product.sku: LENOVO_MT_81EU_BU_idea_FM_ideapad 530S-14IKB dmi.product.version: Lenovo ideapad 530S-14IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Screen freezing https://bugs.launchpad.net/bugs/1899853 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 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected
Downloaded the latest 20.04.1 iso today. Performed a clean install which hit the error at the end of the install. Was redirected to this bugreport. System configuration: Main graphics running through NVIDIA GTX 1080Ti Intel core i7-4790 CPU 3.6GHz 16 GB memory Z97 Extreme6 motherboard Samsung SSD 850 EVO 250GB -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails when "Install Third-Party Drivers" is selected Status in GLibC: New Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: In Progress Status in glibc package in Ubuntu: Invalid Status in apt source package in Bionic: Triaged Status in glibc source package in Bionic: Invalid Status in apt source package in Focal: Triaged Status in glibc source package in Focal: Invalid Bug description: Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 20:17:07 2020 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash --- LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: LANGUAGE=es_EC.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1871268/+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 1880193] Re: autofs: Assertion 'set_remove(iterator->links, link) == link' failed at src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting.
This error has gone with the latest updates, but, unfortunately, I still have the same transient issues with autofs. I see some other strange things in logs and will continue investigation on my side. I think this ticket can be closed (I will open a new ticket if any). Thank you a lot. -- 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/1880193 Title: autofs: Assertion 'set_remove(iterator->links, link) == link' failed at src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting. Status in autofs package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Status in autofs source package in Focal: Triaged Status in systemd source package in Focal: Triaged Bug description: autofs has a periodic error on mounting shares in Ubuntu 20.04 (it happens about 1 time out of 5): "Assertion 'set_remove(iterator->links, link) == link' failed at src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting. Aborted (core dumped)" `autofs.service` restart (or `automount` app restart) fixes this issue. However if some of home dirs (like `Desktop` or `Documents`) are mounted by `autofs`, user can't login into Ubuntu Desktop Environment (PC freezes on login with black screen). Since this error can prevent user log in, it might be considered as critical bug. It happens both in `autofs` systemd service and by direct execution of `automount` app (`automount -f -d` command). May be it's an underlying error in `systemd` library (I found the line, mentioned in error, in its source codes). This issue has place in Ubuntu 20.04 (it works correctly in Ubuntu 18.04): > lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 Packages versions: > apt-cache policy autofs systemd autofs: Installed: 5.1.6-2 Candidate: 5.1.6-2 Version table: *** 5.1.6-2 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status systemd: Installed: 245.4-4ubuntu3 Candidate: 245.4-4ubuntu3 Version table: *** 245.4-4ubuntu3 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1. Ubuntu 20.04 clean install 2. `apt install realmd sssd sssd-tools libnss-sss libpam-sss adcli samba-common-bin` 3. `realm join DOMAIN.NAME` 4. Enable makehomedir by command: `pam-auth-update` 5. `apt install cifs-utils` 6. `apt install autofs` 7. Add next line inside [domain/DOMAIN.EXT] section into /etc/sssd/sssd.conf: `krb5_ccname_template = FILE:%d/krb5cc_%U` 8. Reboot 9. Login as domain user and try to open directory, mounted by `autofs` (in my configuration shares are provided by AD). 10. `autofs.service` stops with the error above about 1 time out of 5 (not always). Found workaround: Add `Restart=always` into `[Service]` section in `/lib/systemd/system/autofs.service` file (in other words configure auto-restart on failures for autofs service). Attachments: 1. Full log of `automount -f -d` command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1880193/+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 1899833] Re: [ZenBook UX434FLC_UX434FL, Realtek ALC294, Speaker, Internal] fails after a while
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/1899833 Title: [ZenBook UX434FLC_UX434FL, Realtek ALC294, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: the sound is good for while , then get noisi + lower to nothing, 2 time ago it get solved by turning on secure boot and turning of fast boot ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matinzare 1615 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 23:05:07 2020 InstallationDate: Installed on 2020-08-11 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: اوْکتوْبر 14 19:54:29 matinzare-ZenBook-UX434FLC dbus-daemon[913]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.31' (uid=125 pid=1100 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") اوْکتوْبر 14 19:54:29 matinzare-ZenBook-UX434FLC pulseaudio[1100]: No UCM verb is valid for hw:0 اوْکتوْبر 14 19:54:42 matinzare-ZenBook-UX434FLC systemd[1090]: pulseaudio.service: Succeeded. اوْکتوْبر 14 19:54:52 matinzare-ZenBook-UX434FLC systemd[1090]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX434FLC_UX434FL, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX434FLC.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX434FLC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX434FLC.303:bd12/18/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX434FLC_UX434FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX434FLC_UX434FL dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-08-11T18:28:56.120214 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1899833/+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 1899833] [NEW] [ZenBook UX434FLC_UX434FL, Realtek ALC294, Speaker, Internal] fails after a while
You have been subscribed to a public bug: the sound is good for while , then get noisi + lower to nothing, 2 time ago it get solved by turning on secure boot and turning of fast boot ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matinzare 1615 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 23:05:07 2020 InstallationDate: Installed on 2020-08-11 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: اوْکتوْبر 14 19:54:29 matinzare-ZenBook-UX434FLC dbus-daemon[913]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.31' (uid=125 pid=1100 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") اوْکتوْبر 14 19:54:29 matinzare-ZenBook-UX434FLC pulseaudio[1100]: No UCM verb is valid for hw:0 اوْکتوْبر 14 19:54:42 matinzare-ZenBook-UX434FLC systemd[1090]: pulseaudio.service: Succeeded. اوْکتوْبر 14 19:54:52 matinzare-ZenBook-UX434FLC systemd[1090]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX434FLC_UX434FL, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX434FLC.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX434FLC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX434FLC.303:bd12/18/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX434FLC_UX434FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX434FLC_UX434FL dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-08-11T18:28:56.120214 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- [ZenBook UX434FLC_UX434FL, Realtek ALC294, Speaker, Internal] fails after a while https://bugs.launchpad.net/bugs/1899833 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver 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 1899195] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message
** Also affects: apport (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: apport (Ubuntu Xenial) Status: New => Triaged ** Changed in: apport (Ubuntu Bionic) Status: New => Triaged ** Changed in: apport (Ubuntu Focal) Status: New => Triaged ** Changed in: apport (Ubuntu Xenial) Importance: Undecided => High ** Changed in: apport (Ubuntu Bionic) Importance: Undecided => High ** Changed in: apport (Ubuntu Focal) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1899195 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Triaged Status in apport source package in Bionic: Triaged Status in apport source package in Focal: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu27.10, the problem page at https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. Traceback (most recent call last): File "/usr/share/apport/apport", line 451, in options = parse_arguments() File "/usr/share/apport/apport", line 396, in parse_arguments parser.print_usage() File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage self._print_message(self.format_usage(), file) File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message file.write(message) AttributeError: 'NoneType' object has no attribute 'write' After working on https://bugs.launchpad.net/apport/+bug/1732962, the error tracker started throwing the error above. it appears that print_usage is called and throwing an error because in this context (called with core_pattern) apport doesn't have an stdout or stderr. after looking at traces it seems the kernel is adding 'deleted' to the name of the process which cause argument parsing to fail. The fix below from bdmurray seems to fix it. https://paste.ubuntu.com/p/pVKNP9kWP4/ There is report of this issue in Focal, Bionic and xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899195/+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 1748812] Re: cannot view wifi networks after resume from suspend
** Tags added: suspend-resume -- 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/1748812 Title: cannot view wifi networks after resume from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: Hello, On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I have the same issue: After resume from suspend nm-applet doesn't show any information about connected/available wi-fi connections. Please see screenshot in attach. I can see current connection via CLI: nmcli dev DEVICE TYPE STATE CONNECTION docker0 bridgeconnected docker0 wlp58s0 wifi connected Turris lo loopback unmanaged -- Now I have to run `killall nm-applet && nm-applet &` after every suspend. That fixes my issue I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1589401 but I was asked to submit separate bug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 Uname: Linux 4.15.0-041500rc9-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 11 19:41:21 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-10-06 (493 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IpRoute: default via 192.168.1.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.137 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/1 docker0 440d4ade-78be-45c3-a821-903971861d0c /org/freedesktop/NetworkManager/ActiveConnection/0 wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/3 Turris e963-362e-4e4a-ac98-54af278d348d /org/freedesktop/NetworkManager/ActiveConnection/88 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812/+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 1775219] Re: incorrectly reports package as unsupported if apt cache is empty
** Tags added: fr-28
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1775219
Title:
incorrectly reports package as unsupported if apt cache is empty
Status in apport package in Ubuntu:
Fix Released
Bug description:
Cloud images ship with empty /var/lib/apt/lists/ to save on size.
Running 'ubuntu-bug ' will erroneously report that
the package is unsupported:
$ ubuntu-bug coreutils
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.
*** Problem in coreutils
The problem cannot be reported:
This is not an official Ubuntu package. Please remove any third
party package and try again.
A simpler recreate is:
$ python3 -c 'import
apport;print(apport.packaging.is_distro_package("coreutils"))'
False
$ sudo apt update -qq
All packages are up to date.
$ python3 -c 'import
apport;print(apport.packaging.is_distro_package("coreutils"))'
True
Desired result:
The message should instruct the user to run 'apt update' as root if
they think this is in error. That would improve usability and avoid
false reports about apport incorrectly flagging a package as
unsupported.
Additionally, if the user is root (and optionally if the set of
package candidates only contains a 'now' component)
self._cache.update(); self._cache.open() could be called to download
lists.
Alternatively it could just check to see if lists have been
downloaded.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1775219/+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 1755447] Re: issue 32185: SSLContext.wrap_socket sends SNI Extension when server_hostname is IP
** Tags added: fr-292 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1755447 Title: issue 32185: SSLContext.wrap_socket sends SNI Extension when server_hostname is IP Status in Python: Fix Released Status in python2.7 package in Ubuntu: New Status in python3.6 package in Ubuntu: Fix Released Status in python3.7 package in Ubuntu: Fix Released Status in python2.7 source package in Trusty: Won't Fix Status in python3.4 source package in Trusty: Won't Fix Status in python2.7 source package in Xenial: New Status in python3.5 source package in Xenial: New Status in python2.7 source package in Artful: Won't Fix Status in python3.6 source package in Artful: Won't Fix Status in python3.7 source package in Artful: Won't Fix Status in python2.7 source package in Bionic: New Status in python3.6 source package in Bionic: Fix Released Status in python3.7 source package in Bionic: Fix Released Status in python2.7 package in Debian: New Status in python3.4 package in Debian: New Status in python3.5 package in Debian: New Bug description: the fix for https://bugs.python.org/issue32185 needs backports for the stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1755447/+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 1775457] Re: /usr/bin/pip3:ImportError:/usr/bin/pip3@9
** Tags added: fr-500 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1775457 Title: /usr/bin/pip3:ImportError:/usr/bin/pip3@9 Status in pip: Unknown Status in apport package in Ubuntu: New Status in python-pip package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding python-pip. This problem was most recently seen with package version 9.0.1-2.3~ubuntu1, the problem page at https://errors.ubuntu.com/problem/4e26eab10247fe3383fb8c84ca8a0d8eb21abc83 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/pip/+bug/1775457/+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 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory
** Tags added: fr-14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1860826 Title: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Status in pam package in Ubuntu: Confirmed Status in pam source package in Groovy: Confirmed Status in pam package in Debian: New Bug description: Hello, after upgrading to focal I found the following in my journalctl output: Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory The login package stopped packaging this file: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656 and now forcibly removes the file: https://paste.ubuntu.com/p/myh9cGWrHD/ However, the pam package's pam_unix.so module has not yet been adapted to ignore this file: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25 Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Fri Jan 24 23:35:33 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pam UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1860826/+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 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0)
** Tags added: fr-232 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1842439 Title: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) Status in apport package in Ubuntu: Confirmed Status in apport source package in Focal: Confirmed Bug description: https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5 --- Session suddenly stopped and came back to login screen, all opened windows lost. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: apport-gtk 2.20.11-0ubuntu7 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashReports: 640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash 640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash 640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash CurrentDesktop: ubuntu:GNOME Date: Tue Sep 3 16:20:13 2019 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2018-06-16 (443 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 SegvAnalysis: Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax PC (0x7f532548f8c4) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1842439/+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 1838258] Re: Unable to configure VLAN on an additional OSA interface
** Tags added: fr-585 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1838258 Title: Unable to configure VLAN on an additional OSA interface Status in Ubuntu on IBM z Systems: Incomplete Status in iproute2 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: After installing a base Ubuntu 18.04.1 server, an additional OSA device "e530" is attached and configured with chzdev. Then a VLAN configuration should be applied using the ip command. However this results in the error message "RTNETLINK answers: File exists". >snip ip link add link ence530 name ence530.209 type vlan id 209 RTNETLINK answers: File exists snip< Executing the same steps on an Ubuntu 16.04.5 server, the ip command finishes without an error message but the VLAN interface is also not configured. Reproduction: - Install a 18.04.1 server - attach an additional OSA interface - configure a VLAN using the ip command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1838258/+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 1734104] Re: 'upgrade' in bionic should by default autoremove as well
** Tags added: fr-287 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1734104 Title: 'upgrade' in bionic should by default autoremove as well Status in apt package in Ubuntu: Triaged Bug description: In bionic, apt upgrade should also autoremove by default. I have a few bionic systems (upgrades from xenial mostly) which are not yet showing that behaviour, it may be we haven't implemented that yet so this is just a placeholder bug in that case :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1734104/+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 1835660] Re: initramfs unpacking failed
** Tags added: fr-79 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+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 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"
** Tags added: fr-303 -- 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/1834226 Title: update-notifier doesn't respect "automatically check for updates: Never" Status in software-properties package in Ubuntu: Confirmed Status in software-properties source package in Eoan: Won't Fix Bug description: This has been a long-standing problem with various ubuntu installations, and I'm sensing some reticence in doing anything about it. This attitude also seems to be purposeful to try to cajole updates on people who make bad choices due to confusion/fud/paranoia. apt install fails due to: E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? A great deal of networking is taking place despite setting automatic upgrades to "never". Cycling this doesn't seem to do anything. This action is hostile to programmers and the setting should be respected. Wisdom on threads is to let it update until it's out of updates, and then it supposedly respects the "never" flag, but the experience I'm having is much more non-deterministic. have been using 19.04 for weeks now and still get the background notifier using data and getting in the way of aptitude package installations. I prefer manual update && upgrade once my code is ready to push. Is there another way around this or are people just living with it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1834226/+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 1833174] Re: Shadowing the vim-window results in vim-gtk3 crash
** Tags added: fr-330 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1833174 Title: Shadowing the vim-window results in vim-gtk3 crash Status in vim: Unknown Status in vim package in Ubuntu: Triaged Status in vim source package in Focal: Triaged Status in vim source package in Groovy: Triaged Bug description: With XFCE when I try to "shadow" the vim-gtk3 window (just to show only the title bar) it results in a vim crash and the window just disappears without any core dump neither .swp files on. The only message I get on the terminal is BadMatch (invalid parameter attributes) Vim: Got X error Vim: Finished. This behaviour started from Xubuntu 18.04. The vim-gtk package is not suffering from this problem. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: vim-gtk3 2:8.1.0320-1ubuntu3.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 18 09:10:38 2019 InstallationDate: Installed on 2019-04-23 (55 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/vim/+bug/1833174/+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 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
** Tags added: fr-26
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1829401
Title:
gi.repository.GLib.GError: pk-client-error-quark: could not do
untrusted question as no klass support
Status in packagekit package in Ubuntu:
Triaged
Status in packagekit source package in Eoan:
Won't Fix
Status in packagekit source package in Focal:
Confirmed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.98.2, the problem page at
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
[Back trace]
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support (8)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+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 1825021] Re: apt's dpkgpm.cc WriteApportReport function should gather more data
** Tags added: fr-238
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1825021
Title:
apt's dpkgpm.cc WriteApportReport function should gather more data
Status in apt package in Ubuntu:
New
Status in apt source package in Eoan:
Won't Fix
Bug description:
While fixing bug 1813464 it occurred to me that it is not obvious that
the dist-upgrader tarball includes its own copy of invoke-rc.d and
that this has been complicated to debug more than once. The apport
information in that report was gathered by apt's dpkgpm.cc code and I
think we should extend that to gather additional information from the
environment at the time that the package installation failed. For
example the dist-upgrader sets the following:
os.environ["PATH"] = "%s:%s" % (os.getcwd()+"/imported",
os.environ["PATH"])
Gathering path from the environment would have made diagnosing bug
1813464 a lot easier. I tested modifying dpkgpm.cc with the following:
if(const char* env_p = std::getenv("PATH"))
fprintf(report, "EnvPATH: %s\n", env_p);
I then installed the crash-in-postinst package from the daisy-plucker-
seeds PPA and received a crash report with the EnvPATH key and value.
Its worth noting that when apport gathers environment information only
a white listed set of keys is gathered to prevent disclosing
potentially sensitive information. So we should look at what
environment variables the dist-upgrader sets and gather those at a
minimum.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825021/+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 1821415] Re: pkexec fails in a non-graphical environment
** Tags added: fr-279 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in apport package in Ubuntu: Triaged Status in policykit-1 package in Ubuntu: Triaged Bug description: The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. N.B. you first need to create a /var/log/plymouth-debug.log file for the plymouth apport package hook to actually trigger this. ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. Subsequently, bug reports from servers will contain less information. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1807749] Re: NFS V4 does not mount at system start
** Tags added: fr-631 -- 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/1807749 Title: NFS V4 does not mount at system start Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Bug description: Hi, i'm running a view Ubuntu 18.10 Clients on a Ubuntu 18.04 NFS V4 Server. I'm using Kerberos for user authentication and LDAP for user and group synchronisation. The shares are added to the /etc/fstab on my clients and they should be mounted automatically at system boot. Here is an example line from fstab: nfs.server:/users /home nfs4 sec=krb5i,soft,_netdev,auto 0 0 But after the system has booted and the Login-Screen appears the nfs shares are not mounted on the client. Attached to this bug, you can find an export of my journald entries from my last boot. When I read this log carefully I find the following start order of relevant services: Begin start nss_ldap (from line 822 on) Begin start NetworkManager (from line 1198) Get IP from DHCP (line 2542) NetworkManager Online (line 2551) Try to mount NFS Shares (from line 2253) nss_ldap connected (line 2761) As far as I understand my setup, I do not have DNS before nss_ldap is started. But since mounting the NFS shares needs DNS, the NFS mount sequence should start after nss_ldap is fully started. Thanks for your help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1807749/+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 1818564] Re: directory permission sanity checks
** Tags added: fr-300 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1818564 Title: directory permission sanity checks Status in apport package in Ubuntu: Triaged Bug description: Hello, we've received a surprising number of bug reports that include lines from ufw's sanity checks on / permissions are incorrect; it's been a recurring feature of systemd-tmpfiles bug reports as well. I think apport should include a similar report if / /etc /lib /usr /tmp etc have incorrect user, group, or permissions. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1818564/+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 1809174] Re: apt doesn't detect file corruption in /var/lib/apt/lists
** Tags added: fr-281 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1809174 Title: apt doesn't detect file corruption in /var/lib/apt/lists Status in apt package in Ubuntu: Triaged Bug description: The Problem == /var/lib/apt/lists contains the repository index caches or similar; I'm not sure what the correct apt-terminology is. I've installed Chrome on my laptop, so I have: smacdonald@L247:/var/lib/apt/lists$ dir *goog* -rw-r--r-- 1 root root 943 Dec 19 14:02 dl.google.com_linux_chrome_deb_dists_stable_Release -rw-r--r-- 1 root root 819 Dec 19 14:02 dl.google.com_linux_chrome_deb_dists_stable_Release.gpg -rw-r--r-- 1 root root 4457 Dec 19 14:02 dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages for example. dl.google.com_linux_chrome_deb_dists_stable_Release contains checksums for the dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages file: smacdonald@L247:/var/lib/apt/lists$ cat dl.google.com_linux_chrome_deb_dists_stable_Release Origin: Google LLC Label: Google Suite: stable Codename: stable Version: 1.0 Date: Wed, 19 Dec 2018 18:51:54 UTC Architectures: amd64 Components: main Description: Google chrome-linux software repository MD5Sum: 9e0d0ad6a4f5ccf8e3971c32e9bb22d3 4457 main/binary-amd64/Packages a17f6de0ef487b82af58ccd91df52d04 1109 main/binary-amd64/Packages.gz 156e5ea7a0c6bed5973a68a45e546dc9 151 main/binary-amd64/Release SHA1: 4c2cde4f71476d7881262d9a07e33cf4506232a7 4457 main/binary-amd64/Packages e002924c9ddfe41ee2033594ec768ed9e4545909 1109 main/binary-amd64/Packages.gz 0f4348c2d4d7cc1f8e59b5934d87f1ca872f6e34 151 main/binary-amd64/Release SHA256: fb0e586c2b5ec5afa17965d0bbc6bd46c2071336f75e2b0f0c7f3e7b090a7844 4457 main/binary-amd64/Packages 2462cff732765679a56373a7ca9a5b8b029fdb445e707b1aba10d01fbdb853b3 1109 main/binary-amd64/Packages.gz c1e3c9318381862306adcdc4fd4fe2d85be8aa4c4f3dcbb40fce80413f588286 151 main/binary-amd64/Release If the dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages file has become corrupt in the specific manner of being 0 bytes in length, apt does not detect this, and the repository is effectively unreachable until one of two things occurs: a) the repository has an update causing apt to re-fetch the repository information and accidentally fix-by-over-writing the corrupt 0 byte file, or, b) the user removes the corrupt 0-byte file and does an apt update to refetch the repository information. The Context == Our IoT devices run Ubuntu 16.04, and their main storage is eMMC. Sometimes there are catastrophic power cuts, and, despite other precautions, files are occasionally corrupted in the manner of becoming 0 bytes in length. We're not sure exactly why or how. Today a deployed device suffered the above scenario. We maintain a debian package repository for updating our devices in the field, and we suddenly couldn't install packages from it. A bit of investigation turned up the 0 byte *_Packages file for our repo, and we worked around the problem. Part of the situation is our debian repository doesn't have updates very often, so 'sudo apt-get update' was giving a Hit: instead of a Get: result all the time, and everything from the "normal user command line" side of things looked okay. There were no logs in /var/log/syslog either. We just could not see our packages from our repo, despite 'apt-get update' looking good. What I Expected to Happen == Given that the the *_Release file contains checksums for the *_Package file, I would expect that apt verifies the checksum, and if it fails, refetches the repository information even if there hasn't been an update, during any given 'apt update' operation. Further Information == I checked apt's project in Debian at https://bugs.debian.org/cgi- bin/pkgreport.cgi?pkg=apt and there don't appear to be any bugs about this filed already, so I'm starting by filing one here. The situation occurred on an Ubuntu 16.04 system, but is 100% reproducible with Google's chrome repository on my Ubuntu 18.04.1 laptop. I can provide a set of reproduction steps if needed, but it's fairly straight-forward. The fact that this corruption appears to be "everything working okay" to the end user, except that apt doesn't know about packages it says it knows about, and there is no error logging for any sort, is partly why I'm filing this. Note the "if one of two things happens" case a) above: if the
[Touch-packages] [Bug 1785302] Re: rsync -a should imply -X
** Tags added: fr-245
--
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/1785302
Title:
rsync -a should imply -X
Status in rsync package in Ubuntu:
New
Bug description:
As discussed at https://lists.ubuntu.com/archives/ubuntu-
devel/2018-August/040407.html ff, as of Ubuntu 18.04 an Ubuntu root
filesystem uses xattrs for storing filesystem capabilities. We should
therefore have defaults for our rsync that preserve these attributes
without needing to pass additional commandline options.
Currently the rsync -a ("archive") option is documented as preserving
symlinks (-l), permissions (-p), modification times (-t), groups (-g),
owners (-u), and special files (-D); but not hardlinks (-H), acls
(-A), or xattrs (-X). I haven't looked into the reasoning, but I
expect it's because the first set of options can be assumed supported
on a target POSIX-ish filesystem, and the latter are not guaranteed to
be supported on all POSIX-ish filesystems (although POSIX does require
hardlink support). On Ubuntu, and on modern Linux generally, it
should be safe to assume that any POSIX filesystem currently in use
that supports Unix permissions and special files also supports acls
and xattrs. (Linux filesystems known to support them: ext4, xfs, jfs,
zfs, btrfs.)
Without having looked closely at the implementation, I think a
sensible approach on Ubuntu would be:
- rsync when sending should interpret '-a' to include '-A' and '-X' and send
acls and xattrs as part of the stream.
- if sending to a remote server that doesn't negotiate a protocol high
enough to handle acls and xattrs, do not consider this an error.
- rsync when receiving xattrs and acls appears to already ignore failures to
set them, so no changes would be required for compatibility.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1785302/+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 1804997] Re: Improve timer spread after resume
** Tags added: fr-243 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1804997 Title: Improve timer spread after resume Status in apt package in Ubuntu: Triaged Bug description: When resuming a machine that should have run unattended-upgrades in the time it was down, and it has containers for which the same applies, the host and all containers run their upgrades in parallel, creating a lot of load. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1804997/+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 1799928] Re: [20.10 FEAT] openssl: RNG support
** Tags added: fr-651 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1799928 Title: [20.10 FEAT] openssl: RNG support Status in Ubuntu on IBM z Systems: Fix Released Status in openssl package in Ubuntu: Fix Released Bug description: Provide a CPACF based random number generator for openSSL using PRNO- SHA-512-DRNG to implement a NIST SP800-90A compliant SHA512 hash based deterministic random bit generator (DRBG) seeded true random numbers extracted using the PRNO-TRNG instruction. Planned with > openssl 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1799928/+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 1774136] Re: apport mistakenly duplicates bugs with similar but not identical python stacktraces
** Tags added: fr-241 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1774136 Title: apport mistakenly duplicates bugs with similar but not identical python stacktraces Status in apport package in Ubuntu: New Bug description: apport duplicates bug 1774131 and bug 1269397 with similar but different python stack traces. bug 1269397 update-manager crashed with AttributeError in resize_to_standard_width(): 'NoneType' object has no attribute 'get_resolution' bug 1774131 update-manager crashed with AttributeError in resize_to_standard_width(): 'UpdateManager' object has no attribute 'signal_changed' The following bucket also collect both traces based only on the first part of the trace: update-manager (AttributeError) → resize_to_standard_width https://errors.ubuntu.com/problem/76971c92f002117650d5630a6b13a8ba683e2343 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 09:34:27 2018 InstallationDate: Installed on 2014-07-15 (1414 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to cosmic on 2018-03-24 (66 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1774136/+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 1772222] Re: dangling symlink in /etc/rsyslog.d breaks rsyslogd
** Tags added: fr-257 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/177 Title: dangling symlink in /etc/rsyslog.d breaks rsyslogd Status in rsyslog package in Ubuntu: New Status in rsyslog source package in Bionic: New Bug description: Since upgrading from artful to bionic, I noticed that /var/log/kern.log, etc., were not being updated on my machine. In comparing to another machine running a fresh install of bionic, I discovered that this seems to be the culprit: [agnew(etc)] ls -l /etc/rsyslog.d/99-conjure-up.conf lrwxrwxrwx 1 root root 45 Jun 14 2017 /etc/rsyslog.d/99-conjure-up.conf -> /usr/share/conjure-up/conjure-up-rsyslog.conf [agnew(etc)] ls -l /usr/share/conjure-up/conjure-up-rsyslog.conf ls: cannot access '/usr/share/conjure-up/conjure-up-rsyslog.conf': No such file or directory [agnew(etc)] _ Before deletion: [agnew(etc)] sudo lsof -n -p $(cat /run/rsyslogd.pid) | grep /var/log lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. [agnew(etc)] _ After deletion: [agnew(etc)] sudo rm /etc/rsyslog.d/99-conjure-up.conf [agnew(etc)] sudo service rsyslog restart [agnew(etc)] sudo lsof -n -p $(cat /run/rsyslogd.pid) | grep /var/log lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. rsyslogd 30686 syslog8w REG 253,122782 15213384 /var/log/syslog rsyslogd 30686 syslog9w REG 253,1 2065 15219687 /var/log/auth.log [agnew(etc)] _ It didn't occur to me to check the service status until writing this bug report, but in fact it does report the problem on startup: May 20 14:39:27 agnew rsyslogd[31786]: error during parsing file /etc/rsyslog.d/postfix.conf, on or before line 1: error accessing config file or directory '/etc/rsyslog.d/99-conjure May 20 14:39:27 agnew rsyslogd[31786]: CONFIG ERROR: there are no active actions configured. Inputs will run, but no output whatsoever is created. [v8.32.0 try http://www.rsyslog.com However, it's unlikely this warning will be discovered until it's too late, if ever -- consider a remote syslogging setup on a machine that has since been decommissioned or reinstalled -- and so it would probably better for rsyslogd to cope with dangling symlinks. Indeed, given the age of the symlink, this is a regression from artful or earlier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/177/+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 1798657] Re: gtk3 frontend 'help' window is huge and not resizeable
** Tags added: fr-251 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1798657 Title: gtk3 frontend 'help' window is huge and not resizeable Status in debconf package in Ubuntu: New Bug description: If I click on 'help' on a debconf question when using the gtk3 frontend, I get a huge window with a 'close' button in the bottom right corner and a small amount of text in the middle of the screen. The window can be resized horizontally, but not vertically. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1798657/+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 1798369] Re: Reinstall Ubuntu (with preserving existing data) shows error message due to "Could not get lock /target/var/cache/apt/archives/lock"
** Tags added: fr-177 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1798369 Title: Reinstall Ubuntu (with preserving existing data) shows error message due to "Could not get lock /target/var/cache/apt/archives/lock" Status in APT: New Status in ubiquity: New Status in apt package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Won't Fix Status in apt source package in Eoan: Invalid Status in ubiquity source package in Eoan: Won't Fix Bug description: When trying to reinstall an existing Ubuntu cosmic installation using latest 18.10 desktop images, the install shows an error dialog around the end of the installation with an "Error restoring installed applications". Looking at the syslog such a traceback can be seen: apt_pkg.Error: E:Could not get lock /target/var/cache/apt/archives/lock - open (11: Resource temporarily unavailable), E:Unable to lock directory /target/var/cache/apt/archives/ After reproducing this on a live session, after chrooting into /target indeed any apt-get install operations result in the same lock-file error. The whole syslog of the reinstall attached to the bug. Test case: * Download latest cosmic image * Install cosmic on the whole disk (can be on a VM) * (optional) Boot into the system and leave a file in the home directory (to leave a trace, just in case) * Reboot and install cosmic using the first option in ubiquity: Reinstall Ubuntu * Finish configuration The install itself doesn't fail, but around the end of the installation process the error dialog appears. System is still bootable but left with old packages. To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1798369/+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 1713086] Re: systemd fails to generate .device units inside LXD containers
** Tags added: fr-623 -- 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/1713086 Title: systemd fails to generate .device units inside LXD containers Status in systemd package in Ubuntu: Confirmed Bug description: See LXD issue here for more context: https://github.com/lxc/lxd/issues/3638 After attaching a block device (in my case /dev/sdc3) to a LXD container, the dev-sdc3.device unit is not generated. However, the dev-sdc3.mount unit is generated correctly. Steps to reproduce (from GitHub issue): stgraber@castiana:~$ truncate -s 10G test.img stgraber@castiana:~$ sudo losetup -f test.img stgraber@castiana:~$ sudo losetup -a /dev/loop1: [0022]:169383 (/var/lib/snapd/snaps/core_2381.snap) /dev/loop2: [0022]:770242 (/var/lib/snapd/snaps/core_2312.snap) /dev/loop0: [0022]:1170310 (/var/lib/snapd/snaps/core_2462.snap) /dev/loop3: [0045]:309158 (/home/stgraber/test.img) stgraber@castiana:~$ lxc launch ubuntu:16.04 issue3638 Creating issue3638 Starting issue3638 stgraber@castiana:~$ lxc config device add issue3638 sda unix-block source=/dev/loop3 path=/dev/sda Device sda added to issue3638 stgraber@castiana:~$ lxc exec issue3638 -- mkfs.ext4 /dev/sda mke2fs 1.42.13 (17-May-2015) Discarding device blocks: done Creating filesystem with 2621440 4k blocks and 655360 inodes Filesystem UUID: 77832ca2-b16d-4b94-8f7d-9ea08c5e6913 Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632 Allocating group tables: done Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done stgraber@castiana:~$ echo Y | sudo tee /sys/module/ext4/parameters/userns_mounts Y stgraber@castiana:~$ lxc exec issue3638 -- mount /dev/sda /mnt stgraber@castiana:~$ lxc exec issue3638 bash root@issue3638:~# echo "/dev/sda /mnt ext4 defaults 0 0" >> /etc/fstab root@issue3638:~# cat /etc/fstab LABEL=cloudimg-rootfs /ext4 defaults0 0 /dev/sda /mnt ext4 defaults 0 0 root@issue3638:~# exit stgraber@castiana:~$ lxc exec issue3638 -- umount /mnt stgraber@castiana:~$ lxc exec issue3638 -- mount /mnt stgraber@castiana:~$ lxc stop issue3638 stgraber@castiana:~$ lxc start issue3638 stgraber@castiana:~$ lxc exec issue3638 -- mount | grep mnt stgraber@castiana:~$ lxc exec issue3638 -- systemctl -a | grep mnt mnt.mount loadedinactive dead start /mnt stgraber@castiana:~$ lxc exec issue3638 -- systemctl -a | grep sda dev-sda.device loadedinactive dead start dev-sda.device dev-sda.mount loadedactive mounted /dev/sda stgraber@castiana:~$ lxc exec issue3638 -- ps aux | grep udev root54 0.0 0.0 41720 1864 ?Ss 16:55 0:00 /lib/systemd/systemd-udevd stgraber@castiana:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1713086/+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 1627564] Re: Debconf crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493] (when png loader is missing/during upgrades)
** Tags added: fr-348 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1627564 Title: Debconf crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493] (when png loader is missing/during upgrades) Status in debconf package in Ubuntu: Confirmed Status in debconf source package in Focal: New Bug description: https://errors.ubuntu.com/problem/2b11576fed59ad23c640bc85a266cc82ec30a689 https://errors.ubuntu.com/problem/9d612b3f25168e76adb91fa4eedc301ffa632383 --- bubble opened up indicating there was a failure during the latest update. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: lightdm-gtk-greeter 2.0.1-2ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.4.0-9136-generic i686 ApportVersion: 2.20.3-0ubuntu7 Architecture: i386 Date: Sun Sep 25 20:37:06 2016 ExecutablePath: /usr/sbin/lightdm-gtk-greeter InstallationDate: Installed on 2016-08-04 (52 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727) ProcCmdline: /usr/sbin/lightdm-gtk-greeter ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 6 SourcePackage: lightdm-gtk-greeter UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf: [greeter] theme-name = Lubuntu-dark-panel mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf: 2016-08-14T22:33:57.293011 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1627564/+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 1787480] Re: bugpattern checking not working for a ubiquity bug report
** Tags added: fr-252 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787480 Title: bugpattern checking not working for a ubiquity bug report Status in apport package in Ubuntu: Confirmed Bug description: Phillip Susi wrote a bug pattern for ubiquity / grub-installer at https://bazaar.launchpad.net/~ubuntu-bugcontrol/apport/ubuntu- bugpatterns/revision/584. While the bug pattern works, tested with test-local and search-bugs from that branch new bug reports are still appearing in Launchpad. I confirmed that the pattern exists in https://people.canonical.com /~ubuntu-archive/bugpatterns/bugpatterns.xml and that using that url instead of a local file in test-local works. So it seems to be something with apport's ui.py or report.py when the bug report is being filed. The best way to test this would be a Live CD where the bug will actually occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787480/+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 1780332] Re: vaultlocker does not ensure that udev is triggered to create /dev/disk/by-uuid/ symlink and fails
** Tags added: fr-630
--
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/1780332
Title:
vaultlocker does not ensure that udev is triggered to create /dev/disk
/by-uuid/ symlink and fails
Status in vaultlocker:
Fix Released
Status in cryptsetup package in Ubuntu:
Incomplete
Status in lvm2 package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
Incomplete
Bug description:
When an encrypted device is setup up a UUID (osd_fsid) is passed from
the charm to be used in the cryptsetup command which accepts a UUID to
place into the LUKS header (shown in cryptsetup luksDump ).
https://github.com/openstack/charm-ceph-osd/blob/stable/18.05/lib/ceph/utils.py#L1788-L1804
UUID comes from osd_fsid
https://github.com/openstack-charmers/vaultlocker/blob/8c9cb85dc3ed5dbf18c66a810d189a5230d85c34/vaultlocker/shell.py#L69-L80
# else statement is used here
block_uuid = str(uuid.uuid4()) if not args.uuid else args.uuid
dmcrypt.luks_format(key, block_device, block_uuid) # creates a LUKS
header
# ...
dmcrypt.luks_open(key, block_uuid) # sets up a device with device mapper
decrypting it via dmcrypt
https://github.com/openstack-
charmers/vaultlocker/blob/d813233179bdf2eec8ed101c702a8e552a966f44/vaultlocker/dmcrypt.py#L44-L56
This UUID is visible in blkid output
/dev/sdc: UUID="" TYPE="crypto_LUKS"
and a udev rule exists to create a /dev/disk/by-uuid/ symlink (which is normally used for filesystem -> block device
resolution)
https://git.launchpad.net/~usd-import-team/ubuntu/+source/lvm2/tree/udev/13-dm-disk.rules.in#n25
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*",
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"
Where vaultlocker fails is in luks_open command (right after luks_format)
# cryptsetup --batch-mode --key-file - open UUID=
crypt- --type luks
because it tries to access /dev/disk/by-uuid/ which
does not exist.
This happens since udev rules are not re-triggered to create this
symlink after a LUKS device is created.
Solution: call the command below after luks_format before luks_open
udevadm settle --exit-if-exists=/dev/disk/by-uuid/
To manage notifications about this bug go to:
https://bugs.launchpad.net/vaultlocker/+bug/1780332/+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 1775291] Re: 'df /dev/sda1' (rootfs) returns result for /dev on gce minimal images
** Tags added: fr-231 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1775291 Title: 'df /dev/sda1' (rootfs) returns result for /dev on gce minimal images Status in cloud-images: New Status in coreutils package in Ubuntu: New Bug description: On base images the root FS shows up as /dev/sda1 in mount and df output. For minimized images the root FS shows up in df output as /dev/root. Scripts that call 'df /dev/sda1' to get information about the root FS will instead match to /dev not / To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1775291/+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 1873678] Re: gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name
I verified the test case using version 0.6.55-0ubuntu12~20.04.2 of accountsservice, gir1.2-accountsservice-1.0 and libaccountsservice0 from focal-proposed. ** 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 accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1873678 Title: gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Fix Committed Bug description: [Impact] accountsservice includes a function for checking the validity of locales, and it incorrectly considers "C.UTF-8" to be invalid. It leads to incorrect behavior under certain conditions and also a crash if the function was triggered from language-selector-gnome. Even if this only makes a difference in special corner cases, it happens often enough to justify this SRU: https://errors.ubuntu.com/?release=Ubuntu%2020.04=language- selector=year (It's the top ranked crash type in the list.) The version in focal-proposed fixes the issue. [Test case] Make a fresh install of Ubuntu 20.04 (a VM works fine) Once logged in: * Install accountsservice, gir1.2-accountsservice-1.0 and libaccountsservice0 from focal-proposed * Open /etc/default/locale for editing, replace its contents with the single line: LANG=C.UTF-8 and reboot. Open Language Support and change language (drag any language above the "English" item) Open ~/.pam_environment and find that e.g. LANG is now the locale representing the language you selected, while e.g. LC_TIME is set to "C.UTF-8". [Regression risk] This is a oneliner which white list "C.UTF-8" as a valid locale name. I can't think of a case where this would cause unexpected behavior. [Original description] USB live disk (20.04 beta) ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: language-selector-gnome 0.203 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: MATE Date: Sun Apr 19 17:07:26 2020 ExecutablePath: /usr/bin/gnome-language-selector InterpreterPath: /usr/bin/python3.8 LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/gnome-language-selector ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonArgs: ['/usr/bin/gnome-language-selector'] PythonDetails: N/A SourcePackage: language-selector Title: gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1873678/+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 1726124] Re: DNS domain search paths not updated when VPN started
** Tags added: fr-13 -- 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/1726124 Title: DNS domain search paths not updated when VPN started Status in network-manager package in Ubuntu: Confirmed Status in network-manager-openvpn package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I connect to work with openvpn through network-manager-openvpn. I'm selecting automatic (DHCP) to get an IP address, and "Use this connection only for resources on its network" to support split tunneling. In the last few versions of Ubuntu I used, this all worked fine. In Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both my VPN network and the internet, BUT I have to use FQDN for my VPN network hosts: the updates to the DNS search path provided by my VPN DHCP server are never being applied. Investigating the system I see that /etc/resolv.conf is pointing to /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not have any of the VPN's search path settings in it: # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home In previous versions of Ubuntu, where NetworkManager controlled the resolver not systemd, /etc/resolv.conf pointed to /run/NetworkManager/resolv.conf and there was a local dnsmasq instance that managed all the complexity. In Ubuntu 17.10 when I look in /run/NetworkManager/resolv.conf file, I see that the search paths ARE properly updated there: $ cat /run/NetworkManager/resolv.conf # Generated by NetworkManager search internal.mycorp.com other.mycorp.com home nameserver 127.0.1.1 However this file isn't being used, and also there's no dnsmasq running on the system so if I switch my /etc/resolv.conf to point to this file instead, then all lookups fail. Strangely, if I look at the systemd-resolv status I see that in theory systemd-resolve does seem to know about the proper search paths: $ systemd-resolve --status ... Link 3 (tun0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.3.0.10 10.8.42.2 DNS Domain: ~internal.mycorp.com ~other.mycorp.com but for whatever reason the search domains are not getting put into the resolv.conf file: $ host mydesk ;; connection timed out; no servers could be reached $ host mydesk.internal.mycorp.com mydesk.internal.mycorp.com has address 10.8.37.74 (BTW, the timeout in the failed attempt above takes 10s: it is SUPER frustrating when all your host lookups are taking that long just to fail). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 22 15:08:57 2017 InstallationDate: Installed on 2017-10-21 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications
[Touch-packages] [Bug 1724623] Re: Update ubuntu cloud info
** Tags added: fr-266 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1724623 Title: Update ubuntu cloud info Status in apport package in Ubuntu: New Bug description: add_cloud_info() in data/general-hooks/ubuntu.py needs an overhaul. Issues: - Using the presence of cloud-init to flag an image as a cloud image is incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images) - Using the presence of EC2 metadata source is incorrect as many non-EC2 clouds provide EC2 metadata. Thus we have bugs like bug #1722946 that are tagged as an 'ec2-images' bug which are clearly on openstack - Marking all bugs that have cloud-init but no EC2 metadata source as an 'uec-images' bug uses a name that no longer has meaning. Solution: - If cloud-init is present, check for /etc/cloud/build.info to indicate an Ubuntu cloud images, tag as 'cloud-images'. Pull the build_name and serial from that file into the bug comments. - If cloud-init is present, check for the presence of /run/cloud-init/cloud.cfg. Parse this yaml to determine the datasource type. Add the datasource used to the bug comment. I have filed bug #1724626 to ask cloud-init development to surface more information from ds-identify to help ID the cloud so that we can better tag/annotate the bug. There may also be some info we can get to indicate the image ID on more clouds than just AWS. At a minimum I would like to see dsidentify make the EC2 platform it found available for consumers in cloud.cfg. This would allow us to identify AWS EC2 from look-alike datasources so that we can tag a bug as ec2-images for bug really on AWS and add EC2 specific fields to the description/attachments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1724623/+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 1697959] Re: late package version collection can cause confusion
** Tags added: fr-253 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1697959 Title: late package version collection can cause confusion Status in apport package in Ubuntu: New Bug description: The following OOPS contains some misinformation: https://errors.ubuntu.com/oops/3680877e-5046-11e7-89b7-fa163e54c21f The Date field is from before the package version in the report was accepted into -proposed. This likely happened because the .crash file was created and data collection, including adding the Package key, was done after systemd had been upgraded. This is alluded to in the UnreportableReason of the OOPS. UnreportableReason: Неполадка произошла с программой /lib/systemd/systemd-resolved, в которую были внесены изменения с момента её аварийного завершения работы. It says that systemd-resolved was modified since the error occurred. As we can see in bug 1621396 this ended up confusing the developer and they were concerned about their fix not working. It seems like apport or whoopsie should do something better here. Ideas include not putting a package version in the Package field if the binary has been modified, or not uploading the crash to the Error Tracker if the binary has changed. The latter would require some additional work because the UnreportableReason is translated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1697959/+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 1659719] Re: ssh can't call a binary from a snap without the full path
** Tags added: fr-78 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1659719 Title: ssh can't call a binary from a snap without the full path Status in Snappy: Fix Committed Status in livecd-rootfs package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Confirmed Status in pam package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: New Status in openssh source package in Xenial: Won't Fix Status in pam source package in Xenial: Fix Released Status in livecd-rootfs source package in Bionic: New Status in openssh source package in Bionic: Won't Fix Status in pam source package in Bionic: Fix Released Status in livecd-rootfs source package in Focal: New Status in openssh source package in Focal: Won't Fix Status in pam source package in Focal: Fix Released Status in livecd-rootfs source package in Groovy: Fix Released Status in openssh source package in Groovy: Confirmed Status in pam source package in Groovy: Fix Released Status in openssh package in Debian: New Bug description: [impact] ssh can't call a binary from a snap, it will only work using the full path. [test case] Create a container. Install the go snap (and make sure golang-go is not installed). Run "ssh go version" and check the binary is found. [regression potential] It's a pam change an they are always a bit scary but the code follows the existing pattern for updating PATH in /etc/environment and has been tested in groovy. [original description] Let's say I have the hello snap installed in 192.168.122.24. Then: elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello elopio@192.168.122.24's password: bash: hello: command not found elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello elopio@192.168.122.24's password: Hello, world! To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659719/+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 1424768] Re: Consider switching to path based activation
** Tags added: fr-258 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1424768 Title: Consider switching to path based activation Status in whoopsie package in Ubuntu: Confirmed Status in whoopsie source package in Bionic: Confirmed Bug description: 1) Ubuntu 15.04 2) 0.2.46 3) Whoopsie to only run when it is needed. 4) Instead it runs constantly, using network activity, l See bug (there are more..): https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/991481 also try: sudo fnotifystat -p whoopsie Instead whoopsie should use path based activation to only run when /var/crash has changed. http://www.freedesktop.org/software/systemd/man/systemd.path.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1424768/+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 1615381] Re: apt-get autoremove may remove current kernel
** Tags added: fr-747 -- 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/1615381 Title: apt-get autoremove may remove current kernel Status in apt package in Ubuntu: In Progress Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Won't Fix Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Bug description: This may happen, if you boot one of the older kernels, that is not protected by /etc/apt/apt.conf.d/01autoremove-kernels Workaround: run /etc/kernel/postinst.d/apt-auto-removal during each boot (e.g. by using cron). Note: The workaround breaks autoremoving feature of new unneeded kernels in unattended-upgrades i.e. the setting 'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set in '/etc/apt/apt.conf.d/50unattended-upgrades'. In shell: $ uname -r 4.4.0-22-generic $ apt-get -s autoremove NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22 linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic 0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 16:11:27 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (114 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified] mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 2016-07-30T12:15:32.706300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615381/+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 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home
** Tags added: fr-81 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1874381 Title: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home Status in Ubuntu on IBM z Systems: Confirmed Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Focal: Confirmed Bug description: After upgrading an LPAR configured with LVM from 18.04 to 20.04 /home is no longer mounted. During boot the console shows Timed out waiting for device /dev/mapper/s5lp8--vg-home Please see the attached dist-upgrade logs and console output for more detail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381/+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 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)
** Tags added: fr-27 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1870060 Title: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services) Status in apport package in Ubuntu: Confirmed Status in bluez package in Ubuntu: Invalid Status in apport source package in Focal: Confirmed Status in bluez source package in Focal: Invalid Bug description: bluetoothd never leaves dumps/crash files when it crashes And it seems this is true for everyone. Only supplementary binaries' crash reports are shown: https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870060/+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 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]
** Tags added: fr-204 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1872106 Title: isc-dhcp-server crashing constantly [Ubuntu 20.04] Status in isc-dhcp package in Ubuntu: Confirmed Status in isc-dhcp source package in Focal: Confirmed Bug description: isc-dhcp-server crashing constantly (sometimes within seconds or minutes, sometimes within hours) with the following error messages: Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service. Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ?? Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ?? Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ?? Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ?? Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ?? Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, code=killed, status=6/ABRT Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 'signal'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872106/+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 1880193] Re: autofs: Assertion 'set_remove(iterator->links, link) == link' failed at src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting.
** Tags added: fr-331 -- 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/1880193 Title: autofs: Assertion 'set_remove(iterator->links, link) == link' failed at src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting. Status in autofs package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Status in autofs source package in Focal: Triaged Status in systemd source package in Focal: Triaged Bug description: autofs has a periodic error on mounting shares in Ubuntu 20.04 (it happens about 1 time out of 5): "Assertion 'set_remove(iterator->links, link) == link' failed at src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting. Aborted (core dumped)" `autofs.service` restart (or `automount` app restart) fixes this issue. However if some of home dirs (like `Desktop` or `Documents`) are mounted by `autofs`, user can't login into Ubuntu Desktop Environment (PC freezes on login with black screen). Since this error can prevent user log in, it might be considered as critical bug. It happens both in `autofs` systemd service and by direct execution of `automount` app (`automount -f -d` command). May be it's an underlying error in `systemd` library (I found the line, mentioned in error, in its source codes). This issue has place in Ubuntu 20.04 (it works correctly in Ubuntu 18.04): > lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 Packages versions: > apt-cache policy autofs systemd autofs: Installed: 5.1.6-2 Candidate: 5.1.6-2 Version table: *** 5.1.6-2 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status systemd: Installed: 245.4-4ubuntu3 Candidate: 245.4-4ubuntu3 Version table: *** 245.4-4ubuntu3 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1. Ubuntu 20.04 clean install 2. `apt install realmd sssd sssd-tools libnss-sss libpam-sss adcli samba-common-bin` 3. `realm join DOMAIN.NAME` 4. Enable makehomedir by command: `pam-auth-update` 5. `apt install cifs-utils` 6. `apt install autofs` 7. Add next line inside [domain/DOMAIN.EXT] section into /etc/sssd/sssd.conf: `krb5_ccname_template = FILE:%d/krb5cc_%U` 8. Reboot 9. Login as domain user and try to open directory, mounted by `autofs` (in my configuration shares are provided by AD). 10. `autofs.service` stops with the error above about 1 time out of 5 (not always). Found workaround: Add `Restart=always` into `[Service]` section in `/lib/systemd/system/autofs.service` file (in other words configure auto-restart on failures for autofs service). Attachments: 1. Full log of `automount -f -d` command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1880193/+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 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected
** Tags added: fr-779 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails when "Install Third-Party Drivers" is selected Status in GLibC: New Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: In Progress Status in glibc package in Ubuntu: Invalid Status in apt source package in Bionic: Triaged Status in glibc source package in Bionic: Invalid Status in apt source package in Focal: Triaged Status in glibc source package in Focal: Invalid Bug description: Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 20:17:07 2020 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash --- LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: LANGUAGE=es_EC.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1871268/+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 1861451] Re: apport's cloud-init-specific handling tracebacks on minimal cloud images
** Tags added: fr-191 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1861451 Title: apport's cloud-init-specific handling tracebacks on minimal cloud images Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Released Status in apport source package in Focal: Invalid Bug description: Impact -- It is not possible to run ubuntu-bug for some packages which gather information as root because pkexec does not work in non-graphical environments (LP: #1821415). This was worked around in Ubuntu 19.10 by not gathering any information that would require root access. Test Case - 1) Install multipass. 2) `multipass launch http://cloud-images.ubuntu.com/minimal/daily/bionic/current/bionic-minimal-cloudimg-amd64.img -n reproducer` 3) `multipass shell reproducer` 4) `ubuntu-bug cloud-init` Expected behaviour: Usual bug reporting flow (though, currently, I would really expect to see just the issue reported in bug 1861450). Actual behaviour: ERROR: hook /usr/share/apport/package-hooks/cloud-init.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/package-hooks/cloud-init.py", line 6, in add_info return cloudinit_add_info(report, ui) File "/usr/lib/python3/dist-packages/cloudinit/apport.py", line 123, in add_info attach_cloud_init_logs(report, ui) File "/usr/lib/python3/dist-packages/cloudinit/apport.py", line 57, in attach_cloud_init_logs 'cloud-init-output.log.txt': 'cat /var/log/cloud-init-output.log'}) File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 444, in attach_root_command_outputs sp = subprocess.Popen(_root_command_prefix() + [wrapper_path, script_path]) File "/usr/lib/python3.6/subprocess.py", line 729, in __init__ restore_signals, start_new_session) File "/usr/lib/python3.6/subprocess.py", line 1364, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'pkexec': 'pkexec' (As alluded to above, this also demonstrates bug 1861450 after the traceback is emitted.) Regression Potential Little as we are just returning and empty list if pkexec is not available, however it is always possible that the code is misformated or that there is a logic error in it. A regression test would be to run the ubuntu-bug cloud-init on a system with pkexec installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1861451/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867204] Re: /usr/share/apport/whoopsie-upload-all:FileNotFoundError:/usr/share/apport/whoopsie-upload-all@170:collect_info:process_report
** Tags added: fr-269 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1867204 Title: /usr/share/apport/whoopsie-upload- all:FileNotFoundError:/usr/share/apport/whoopsie-upload- all@170:collect_info:process_report Status in apport package in Ubuntu: New Status in apport source package in Focal: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu19, the problem page at https://errors.ubuntu.com/problem/7a3912ff155870bdb23500abfa48a21a6cb07171 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1867204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1880250] Re: Ctrl-C message displayed without any actual disk check
** Tags added: fr-110 -- 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/1880250 Title: Ctrl-C message displayed without any actual disk check Status in plymouth package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in plymouth source package in Focal: Fix Committed Status in systemd source package in Focal: Confirmed Status in plymouth source package in Groovy: Fix Released Status in systemd source package in Groovy: Confirmed Bug description: [Impact] * fsck messages is shown by plymouth, despite all fscks already completed. [Test Case] * Install Ubuntu Desktop with full disk encryption * Observe that fsck messages (press ctrl+c) is shown, and remains there on screen for a little while as plymouth transitions to gdm * After installing the update, observe that when fsck completes the messages are cleared and the transition to gdm is done without fsck/ctrl+c message present. * After this change lands in -updates, and daily desktop images are built with this, double check that casper-md5sum transition is also smooth. [Regression Potential] * plymouth spinner theme is adjusted to clear the footer, at the end of fsck, even if systemd-fsckd didn't do that. At the moment there are two consumers of the fsck apis systemd-fsckd & casper-md5sum used on installed systems and live-isos respectively. If something else pushes messages to the footer, they might get cleared at the end of fsck. [Other Info] * Original bug report It seems the transition to bgrt lost something with Ubuntu's disk check details. The only thing I see on my screen during a long disk check is the "press Ctrl-C to stop all in progress disk checks" with no progress. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1880250/+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 1889059] Re: [Ubuntu 20.04] zlib on s390x may produce incomplete raw (but not gzip/zlib) streams
** Tags added: fr-176 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1889059 Title: [Ubuntu 20.04] zlib on s390x may produce incomplete raw (but not gzip/zlib) streams Status in Ubuntu on IBM z Systems: Fix Released Status in zlib package in Ubuntu: Fix Released Status in zlib source package in Focal: Fix Released Status in zlib source package in Groovy: Fix Released Bug description: zlib on s390x may produce incomplete raw (but not gzip/zlib) streams ---uname output--- Linux t35lp56.lnxne.boe 5.8.0-20200703.rc3.git0.52a479d42203.300.fc31.s390x #1 SMP Fri Jul 3 00:46:20 CEST 2020 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Create a raw (negative windowBits value) stream with zlib. EOBS might be missing or truncated. This affects all distro levels that contain hardware acceleration (DFLTCC) patch. I've attached the preliminary fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889059/+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 1887372] Re: Cannot create lvm upon IMSM raid array
** Tags added: fr-337 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1887372 Title: Cannot create lvm upon IMSM raid array Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Focal: New Status in lvm2 source package in Groovy: Confirmed Bug description: The issue has been observed on 2.3.7 (Ubuntu 20.04). Reported to lvm team: https://bugzilla.redhat.com/show_bug.cgi?id=1855251 Steps to Reproduce: 1. Create IMSM raid array: #mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1 #mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G 2. Create lvm volume on raid: # pvcreate -ff -y /dev/md/vol # vgcreate group0 /dev/md/vol # lvcreate -Z y -y -l +100%FREE group0 -n lvm0 Actual results: Vg creation fails. Expected results: LVM should be able to determine the best drive and ignore duplicates. Additional info: IMSM metadata is written at the end of the drive. The first drive sector belongs to the raid volume and other metadata saved there (like lvm) can be recognized directly on raid members. The following patches should fix the issue (not verified yet): https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887372/+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 1888726] Re: systemd-udevd regression: some renamed network interfaces stuck in "pending" state
** Tags added: fr-741 -- 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/1888726 Title: systemd-udevd regression: some renamed network interfaces stuck in "pending" state Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in netplan.io source package in Focal: New Status in systemd source package in Focal: Invalid Bug description: Summary: In Ubuntu Server 20.04 LTS and newer, using netplan.io and systemd- networkd, in certain network configurations, renamed network interfaces get stuck in "pending" state and are not configured properly. On boot, system is stuck on "Wait for Network to be Configured" for 2 minutes. How to reproduce: 1. Configure a machine (for example, a virtual machine) with two Ethernet network cards. Make note of MAC addresses of these network cards. 2. Set up netplan with a single configuration file, contents are in the attached "00-static.yaml" file. Replace the MAC addresses to match your setup. IP address configuration is omitted and is not necessary to reproduce the bug. 3. Reboot the system. Expected outcome: 1. System boots in a reasonable time 2. First network interface (wan) is brought up, is not renamed, and is marked as configured by networkd 3. Second network interface (lan) is brought up, renamed, configured for MTU=9000, and is marked as configured by networkd 4. VLAN interface (vlan20) is brought up, renamed, configured for MTU=9000, and is marked as configured by networkd Actual outcome: 1. System boot is delayed by 2 minutes 2. First network interface (wan) is configured as expected 3. Second network interface (lan) is configured as expected 4. VLAN interface (vlan20) seems to be configured as expected, but is stuck in "pending" state according to networkctl list Test environment: Hardware: Virtual machine with the following configuration * 4 amd64 CPU cores (also tested with a single core) * 1 GB RAM * 8 GB disk * 2 network cards (vmxnet3 in VMware, virtio in Parallels) Working as expected: * [1] Ubuntu Server 19.10, kernel 5.3.0-62, netplan.io 0.99-0ubuntu3~19.10.2, systemd+udev 242-7ubuntu3.11 Broken: * [2] Ubuntu Server 19.10, kernel 5.3.0-62, netplan.io 0.99-0ubuntu3~19.10.2, systemd 242-7ubuntu3.11, udev 245.4-4ubuntu3.1 * [3] Ubuntu Server 20.04 LTS, kernel 5.4.0-42, netplan.io 0.99-0ubuntu3~20.04.2, systemd+udev 245.4-4ubuntu3.1 * [4] Ubuntu Server 20.04 LTS, kernel 5.4.0-42, netplan.io 0.99-0ubuntu3~20.04.2, systemd+udev vanilla upstream git e9769453 * [5] Ubuntu Server 20.04 LTS, kernel 5.4.0-42, netplan.io 0.99-0ubuntu3~20.04.2, systemd+udev vanilla upstream git v242 * [6] Ubuntu Server 20.10 daily-live, kernel 5.4.0-26, netplan.io 0.99-0ubuntu5, systemd+udev 245.6-3ubuntu3 [2] As noted above, issue was reproduced in 19.10 by upgrading ONLY udev and libudev1 to ones shipped in focal-updates. [4] It was also reproduced in vanilla upstream systemd, git master commit e9769453. Just installed on top of existing systemd using "sudo ninja -C build install". [5] Interestingly enough, issue also seems to exist in vanilla v242. Either that, or the installation didn't replace the packaged systemd properly. This may hint at some distribution-specific patch that got removed before 20.04. This issue was reproduced in VMware ESXi 6.7U3, VMware Fusion 11.5.5 and Parallels Desktop 15.1.4. This leads me to believe that network card drivers or virtualisation engines do not play part in the issue. Extra observations: To make the example configuration (00-static.yaml) not get stuck in "pending" state, any one of the following options helps: * Remove "set-name" parameter for "lan" interface * Remove "mtu" parameter for "lan" interface * Remove "wan" interface entirely I got some data/logs for each of these scenarios for eoan [1] and focal [3], as well as the original broken config, and put them together in the attached "parallels.tar.gz". Note about Apport: Attached apport report was generated for test environment [2] above. Attachments: * 00-static.yaml: minimalistic broken netplan configuration example * parallels.tar.gz: various logs for eoan [1] and focal [3], as described in "Extra observations" above ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: udev 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 CustomUdevRuleFiles: 70-snap.core.rules Date: Thu Jul 23 18:54:58 2020 InstallationDate: Installed on 2020-07-22 (1 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Error: command ['lsusb']
[Touch-packages] [Bug 1882494] Re: [UBUNTU 20.04] zlib not working on all s390x systems configurations
** Tags added: fr-175 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1882494 Title: [UBUNTU 20.04] zlib not working on all s390x systems configurations Status in Ubuntu on IBM z Systems: Fix Released Status in zlib package in Ubuntu: Fix Released Status in zlib source package in Eoan: Won't Fix Status in zlib source package in Focal: Fix Released Status in zlib source package in Groovy: Fix Released Bug description: Pull request (https://github.com/madler/zlib/pull/410) and tagged https://github.com/iii-i/zlib/tree/dfltcc-20200511. The new code contains the following improvements: * Added support for switching between software and hardware compression. * Added --dfltcc configure flag (the old way of building it still works). Switching between software and hardware compression is not simply a nice-to-have feature, but is actually required by Java - that's why we are requesting an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882494/+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 1889742] Re: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)
** Tags added: fr-222 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1889742 Title: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils) Status in Ubuntu on IBM z Systems: New Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Focal: New Status in binutils source package in Groovy: Fix Released Bug description: == Comment: #0 - Heinz-Werner Seeck - 2020-07-31 03:28:30 == On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Already included within 20.10 via LP: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654 This should also be SRUed for 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889742/+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 1891716] Re: Networking broken after systemd update
** Tags added: fr-188 -- 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/1891716 Title: Networking broken after systemd update Status in systemd package in Ubuntu: Fix Released Status in systemd package in Debian: Unknown Bug description: # Description: After this upgrade in groovy, networking stopped working: Start-Date: 2020-08-14 17:02:50 Commandline: apt-get dist-upgrade --assume-yes Requested-By: ubuntu (1000) Install: motd-news-config:amd64 (11ubuntu11, automatic) Upgrade: libaudit-common:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), alsa-ucm-conf:amd64 (1.2.2-1ubuntu1, 1.2.2-1ubuntu2), libmpfr6:amd64 (4.0.2-1build1, 4.1.0-3), python3-software-properties:amd64 (0.98.10, 0.99.2), cloud-initramfs-dyn-netconf:amd64 (0.45ubuntu1, 0.46ubuntu1), libsystemd0:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libpam-cap:amd64 (1:2.36-1, 1:2.42-2), libgmp10:amd64 (2:6.2.0+dfsg-6, 2:6.2.0+dfsg-6ubuntu1), ubuntu-standard:amd64 (1.452, 1.453), nano:amd64 (4.9.3-1, 5.1-1), udev:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ubuntu-server:amd64 (1.452, 1.453), libpipeline1:amd64 (1.5.2-2build1, 1.5.3-1), isc-dhcp-common:amd64 (4.4.1-2.1ubuntu6, 4.4.1-2.1ubuntu9), libudev1:amd64 (245.7-1ubuntu1, 246-2ubuntu1), systemd-timesyncd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ubuntu-minimal:amd64 (1.452, 1.453), libcap2:amd64 (1:2.36-1, 1:2.42-2), systemd-sysv:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libcap2-bin:amd64 (1:2.36-1, 1:2.42-2), libpam-systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libnss-systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ethtool:amd64 (1:5.4-1, 1:5.8-1), overlayroot:amd64 (0.45ubuntu1, 0.46ubuntu1), cloud-initramfs-copymods:amd64 (0.45ubuntu1, 0.46ubuntu1), isc-dhcp-client:amd64 (4.4.1-2.1ubuntu6, 4.4.1-2.1ubuntu9), libaudit1:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), base-files:amd64 (11ubuntu10, 11ubuntu11), software-properties-common:amd64 (0.98.10, 0.99.2) End-Date: 2020-08-14 17:03:10 # Reproduction steps: $ multipass launch --name groovy-update-test daily:groovy $ multipass connect groovy-update-test # connected to VM $ sudo apt-get update && sudo apt-get dist-upgrade --assume-yes # works fine $ sudo apt-get update Err:1 http://security.ubuntu.com/ubuntu groovy-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:2 http://archive.ubuntu.com/ubuntu groovy InRelease Temporary failure resolving 'archive.ubuntu.com' Err:3 http://archive.ubuntu.com/ubuntu groovy-updates InRelease Temporary failure resolving 'archive.ubuntu.com' Err:4 http://archive.ubuntu.com/ubuntu groovy-backports InRelease Temporary failure resolving 'archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy-updates/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy-backports/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/groovy-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. $ sudo systemctl list-units --failed UNIT LOAD ACTIVE SUBDESCRIPTION ● systemd-networkd.service loaded failed failed Network Service ● systemd-networkd.socket loaded failed failed Network Service Netlink Socket LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 2 loaded units listed. $ systemctl status systemd-networkd.service ● systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-08-14 17:03:01 EDT; 12min ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 2745 (code=exited, status=1/FAILURE) Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. Aug 14 17:03:01 fulfilling-hornet systemd[1]: Failed to start Network Service. Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 5. Aug 14 17:03:01 fulfilling-hornet systemd[1]: Stopped Network Service. Aug 14 17:03:01 fulfilling-hornet systemd[1]:
[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils
** Tags added: fr-126 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1888352 Title: use builtin dump_acpi_tables.py in hookutils Status in Apport: New Status in OEM Priority Project: Fix Committed Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Released Status in apport source package in Groovy: Fix Released Bug description: 1. add apcidump to hookutils.py:attach_hardware and use the builtin dump_acpi_tables.py. 2. remove explicit acpidump from oem-getlogs to use the builtin one. 3. refine usage string in oem-getlogs. To SRU to focal: [Impact] * for OEM project, lts is been used. And collect log is important. With built-in tool to get acpidump, we don't need to install extra tool in the end-customer's machine. That make it much easier for the oem process. * By call built-in utility, we no lounger need to install extra tools to collect data that's both complete and convenient for HWE people to work on. [Test Case] * before this applied, run oem-getlog without install acpidump. we can't get the dump data. After this applied, we can just dump the data HWE need. * test step: install the new package, run sudo -E oem-getlogs [-c case_id] to get the use apport-unpack to unpack the apport file. check the acpidump file. HWE people know much better on check the acpidump file. Give the dump_acpi_tables.py just updated and SRUed by HWE/ACPI/UEFI expert, it's pretty safe to do so. [Regression Potential] * Given the modification change the way to collect log, even it failed, it won't break apport itself. Just the collected log might contain data not so valid. * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they just reviewed and updated the dump_acpi_tables.py script, I believe it will have good quality. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1888352/+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 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
** Tags added: fr-691 -- 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/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in apport source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic
[Touch-packages] [Bug 1891486] Re: vim ftbfs in focal (armhf, ppc64el)
** Tags added: fr-235 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1891486 Title: vim ftbfs in focal (armhf, ppc64el) Status in vim package in Ubuntu: Confirmed Status in vim source package in Focal: New Bug description: seen in a focal test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19801040 https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19801038 --- Executed: 2257 Tests Skipped:31 Tests FAILED: 1 Tests Failures: From test_debugger.vim: Found errors in Test_Debugger(): function RunTheTest[40]..Test_Debugger[157]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..59 line 1: Expected 'No breakpoints defined' but got 'cmd: echo Foo()' function RunTheTest[40]..Test_Debugger[185]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..71 line 1: Expected '19' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[188]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..72 line 1: Expected 'E161: Breakpoint not found: 2' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[192]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..73 line 1: Expected 'Entering Debug mode. Type "cont" to continue.' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[192]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..74 line 1: Expected 'function Bazz' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[192]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..75 line 1: Expected 'line 2: let var1 = 3 + a:var' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[199]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..76 line 1: Expected ' 3 func Bazz line 2' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[199]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..77 line 1: Expected ' 4 expr var3' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..78 line 1: Expected 'Breakpoint in "Bazz" line 5' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..79 line 1: Expected 'Oldval = "''another var''"' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..80 line 1: Expected 'Newval = "''value2''"' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..81 line 1: Expected 'function Bazz' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..82 line 1: Expected 'line 5: catch' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[208]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..83 line 1: Expected 'No breakpoints defined' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[211]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..84 line 1: Expected 'Error detected while processing function Bazz:' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[211]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..85 line 1: Expected 'line5:' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[211]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..86 line 1: Expected 'E475: Invalid argument: abcd' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[215]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..87 line 1: Expected 'E475: Invalid argument: func' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[216]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..88 line 1: Expected 'E475: Invalid argument: func 2' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[217]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..89 line 1: Expected 'E475: Invalid argument: func a()' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[218]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..90 line 1: Expected 'E475: Invalid argument: abcd' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[219]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..91 line 1: Expected 'E475: Invalid argument: func' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[220]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..92 line 1: Expected
[Touch-packages] [Bug 1893899] Re: update alsa/audio related infomation collection code in apport
** Tags added: fr-692 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1893899 Title: update alsa/audio related infomation collection code in apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Fix Released Status in apport source package in Groovy: Fix Released Bug description: what need to change 1. try to use /usr/sbin/alsa-info before try /usr/share/alsa-base/alsa-info.sh (weird for me that two copy of alsa-info co-exists, but anyway) 2. add pa-info (exist after focal) 3. add ucm2 directory. (exist after focal) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893899/+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 1894369] Re: apport-autoreport.service fails to start in groovy after upgrading from focal
*** This bug is a duplicate of bug 1891657 *** https://bugs.launchpad.net/bugs/1891657 ** Tags added: fr-690 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1894369 Title: apport-autoreport.service fails to start in groovy after upgrading from focal Status in apport package in Ubuntu: Confirmed Status in apport source package in Groovy: Confirmed Bug description: apport-autoreport.service fails to start with that CPU load increases significantly making computer unusable. disabling the service and path and stopping both normalizes CPU load as it was supposed to be. for test purposes i started apport-autoreport.service and after checking its status i get state: degraded and 2 units failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1894369/+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 1893170] Re: [Ubuntu 20.10] zlib: DFLTCC compression level switching issues
** Tags added: fr-590 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1893170 Title: [Ubuntu 20.10] zlib: DFLTCC compression level switching issues Status in Ubuntu on IBM z Systems: Fix Released Status in zlib package in Ubuntu: Fix Released Status in zlib source package in Focal: Fix Released Status in zlib source package in Groovy: Fix Released Bug description: SRU Justification: == [Impact] * This SRU fixes a combination of multiple issues: * zlib DFLTCC compression level switching can corrupt data because hardware and software compression states become desynchronized. (LP 1893170) * Since zlib is not working on all s390x system configurations support for switching between software and hardware compression is required especially for Java. (LP 1882494) * zlib on s390x may produce incomplete raw streams (but not gzip/zlib). (LP 1889059) [Test Case] * Since especially DFLTCC requires a s390x generation z15 or LinuxONE III the tests need to be done by IBM. * IBM has a set of tests available, that exercise public zlib APIs by calling them in different sequences with different buffer sizes and flush modes. * Partially these come from the IBM z/OS team, who developed their own zlib support for the hardware accelerator, and partially they are developed by the IBM Linux team based on issues encountered during development as well as fuzzing. * IBM also uses the zlib-ng test-suite as well as squash and stress- ng. * Compress data using zlib/DFLTCC with different compression level and verify state and if data got corrupted or not. (LP 1893170) * On a system with patched zlib package, switch between hardware and software compression and use zlib via the java.util.zip package (http://java.sun.com/developer/technicalArticles/Programming/compression/). (LP 1882494) * On a z15 system with hardware acceleration compression (DFLTCC) enabled, create a raw (negative windowBits value) stream with zlib. Then check if EOBS is missing or truncated. (LP 1889059) [Regression Potential] * There is a certain risk for regressions with the modifications that are introduced by the four LP bugs. * In case the package fails entirely, it will have (in worst case) an impact on all zlib, gzip and DFLTCC compression/decompression functions, that are very wide spread (gzip, tar cfz, everything with zlib) in Linux and would virtually make the system unusable. * If potential issues are limited to hardware assisted compression (which is more likely, since these patches are mostly about hw assisted compression), then issues would be limited to systems that provide this feature (latest s390x generation only). * A switch back to software got introduced (by setting DFLTCC=0 environment variable) that will help to mitigate a potential negative impact of the hw assisted compression. * Only the latest s390x generation (z15 and LinuxONE III) supports hardware assisted DFLTCC and is potentially affected. * A patched test package was made available and got successfully tested by IBM. All four bugs were finally considered as solved with zlib (1:1.2.11.dfsg-2ubuntu2~ppa2) available here: https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+packages?field.name_filter=zlib __ Description: zlib: DFLTCC compression level switching issues Symptom: Switching compression levels corrupts data Problem: Hardware and software compression states become desynchronized. Solution: Improve compression state synchronization. Since zlib project does not accept patches at the moment, the fix has been integrated into the DFLTCC pull request: https://github.com/madler/zlib/pull/410 The commitid is 992a7afc3edfa511dff0650d1c545b11bf64e655. Reproduction: Not possible with popular command line tools. The issues were discovered using example_call_fuzzer from: https://github.com/iii-i/zlib-ng/tree/fuzz/test/fuzz/ This needs also be applied against 20.04 ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1893170/+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 1898078] Re: FIPS OpenSSL crashes Python2.7 hashlib when using MD5
This bug was fixed in the package python2.7 - 2.7.17-1~18.04ubuntu1.2 --- python2.7 (2.7.17-1~18.04ubuntu1.2) bionic-security; urgency=medium * SECURITY UPDATE: CRLF injection - debian/patches/CVE-2020-26116.patch: prevent header injection in http methods in Lib/httplib.py, Lib/test/test_httlib.py. - CVE-2020-26116 * debian/patches/issue9146.patch: re-adding fix FIPS mode environments where MD5 isn't available in Modules/_hashopenssl.c. (LP: #1898078) -- leo.barb...@canonical.com (Leonidas S. Barbosa) Wed, 30 Sep 2020 10:38:04 -0300 ** Changed in: python2.7 (Ubuntu Bionic) Status: New => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-26116 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1898078 Title: FIPS OpenSSL crashes Python2.7 hashlib when using MD5 Status in python2.7 package in Ubuntu: New Status in python2.7 source package in Xenial: New Status in python2.7 source package in Bionic: Fix Released Status in python2.7 source package in Focal: New Status in python2.7 source package in Groovy: New Bug description: LP #1835135 was fixed in python2.7. However, when python2.7 was updated to current verion, the fix was not included. It needs to be included again into current version of python2.7 to prevent FIPS issues when using fips openssl with python's hashlib. This is only a problem in latest python2.7 versions in xenial, bionic, focal, and groovy. python3 versions do not have this problem in these releases. The fix was a backport of https://github.com/python/cpython/pull/1777/commits/5e3e3568d27b99dabe44b8aa6283dc76d70f2dae To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1898078/+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 1898729] Re: shim can end up being removed
** Tags added: fr-807 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1898729 Title: shim can end up being removed Status in apt package in Ubuntu: New Status in shim package in Ubuntu: New Bug description: I just did a set of package updates in focal that ended up with shim shim-signed mokutil being autoremoved. I rebooted without noticing, and had to manually recover the system thereafter. :( Julian says there was a period of time where these were marked auto. I suppose that I installed during this window, and now some dependency change meant that as far as apt was concerned they weren't required any more. Can we please consider never proposing these packages for autoremoval? apt has NeverAutoRemove for this which could be used, or some other appropriate method. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898729/+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 1899349] Re: Jack_control in jackd2 1.9.14 will not accept char parameters
Sebastien, My apologies, I saw you uploaded. Pretty sure this will be accepted for the Groovy cycle since we're not at final freeze yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1899349 Title: Jack_control in jackd2 1.9.14 will not accept char parameters Status in jackd2 package in Ubuntu: Fix Committed Bug description: trying to set self-connect-mode (for example): $ jack_control eps self-connect-mode e gives: --- engine param set "self-connect-mode" -> "e" Traceback (most recent call last): File "/usr/bin/jack_control", line 400, in main() File "/usr/bin/jack_control", line 283, in main configure_iface.SetParameterValue(['engine', param], python_type_to_jackdbus_type(value, type_char)) File "/usr/bin/jack_control", line 46, in python_type_to_jackdbus_type return dbus.Byte(value); TypeError: Expected a bytes or str of length 1, or an int in the range 0-255 This bug has been fixed upstream in commit ba28ffa @@ -43,7 +43,7 @@ def python_type_to_jackdbus_type(value, type_char): if type_char == "b": return bool_convert(value); elif type_char == "y": -return dbus.Byte(value); +return dbus.Byte(ord(value)); elif type_char == "i": return dbus.Int32(value) elif type_char == "u": To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1899349/+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 1576454] Re: Superfluous Xsession.d script: 60x11-common_localhost
Thanks for fixing this! -- 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/1576454 Title: Superfluous Xsession.d script: 60x11-common_localhost Status in xorg package in Ubuntu: Fix Released Bug description: Both of these scripts do the same thing, and both are installed by x11-common: /etc/X11/Xsession.d/35x11-common_xhost-local /etc/X11/Xsession.d/60x11-common_localhost 35x11-common_xhost-local is present in debian, while 60x11-common_localhost is not. I suspect the latter should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576454/+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 1899621] Re: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15
** Changed in: zlib (Ubuntu Groovy) Milestone: ubuntu-20.10 => groovy-updates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1899621 Title: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15 Status in Release Notes for Ubuntu: New Status in Ubuntu on IBM z Systems: New Status in zlib package in Ubuntu: New Status in zlib source package in Focal: New Status in zlib source package in Groovy: New Bug description: Description: zlib: inflateSyncPoint() returns an incorrect result on z15 Symptom: Certain rsync builds fail with "error in rsync protocol data stream" on z15. Problem: inflateSyncPoint() does not take into account the hardware compression state and returns an incorrect result. Solution: Make inflateSyncPoint() fail if the hardware compression is on. The hardware does not provide enough information in order to implement this function. Reproduction: z15 only: printf 1 >1 && rsync -z 1 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1899621/+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 1891407] Re: [journalctl --follow] Wi-Fi auto disconnect randomly, unable to fix (updated: including PCIe Bus Error)
** Summary changed:
- [journalctl --follow] Wi-Fi auto disconnect randomly, unable fix and better
uninstall ubuntu (updated: including PCIe Bus Error)
+ [journalctl --follow] Wi-Fi auto disconnect randomly, unable to fix (updated:
including PCIe Bus Error)
--
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/1891407
Title:
[journalctl --follow] Wi-Fi auto disconnect randomly, unable to fix
(updated: including PCIe Bus Error)
Status in network-manager package in Ubuntu:
New
Bug description:
Ubuntu 20.04.01 LTS (newly installed)
(Moved that device from windows 10, didnt had issue in it)
HP 15T-au000 device.
[lspci]Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE
PCIe Wireless Network Adapter
[lspci | awk '/[Nn]et/ {print $1}' | xargs -i% lspci -ks %]
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI
Express Fast Ethernet controller (rev 0a)
DeviceName: Realtek PCIe FE Family Controller
Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet
controller
Kernel driver in use: r8169
Kernel modules: r8169
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe
Wireless Network Adapter
DeviceName: Realtek Sanji2 RTL8723BE b/g/n 1x1 + BT 4 LE PCIe+USB M.2
Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter
Kernel driver in use: rtl8723be
Kernel modules: rtl8723be
Wi-Fi key is correct (i can use internet to visit sites, watch videos in
youtube etc) however randomly disconnect and appear window to re-connect
(sometimes constantly disconnect)
No network related change has made (IPv6 disabled through settings)
Only one SSID is in use: Dialog 4G
I ran `journalctl --follow` and below is the log. let me know if
required to provide further details
~Updated~
There also `PCIe Bus Error: severity=Corrected, type=Physical Layer` occur
due that wifi card - RTL8723BE
It usually appear when boot the device (before login screen) and currently i
suppressed that issue by adding `pci=noaer` to grub (alternative pci=nomsi)
I found https://github.com/rtlwifi-linux/rtlwifi_new and
https://github.com/silenoth/rtlwifi_new-extended it contain
'RTL8723BE' however most people had used them due wifi card does not
display or unable connect but i dont have such issue and users have
reported installation issues then didnt consider to put to my machine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891407/+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 1899349] Re: Jack_control in jackd2 1.9.14 will not accept char parameters
Sebastien, Example utility or not, this is something that is used by studio- controls for controlling Jack. Whether or not it was intended to be an example utility is irrellevant. If you don't have the time to fix this and upload, I'll do it. ** Changed in: jackd2 (Ubuntu) Importance: Low => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1899349 Title: Jack_control in jackd2 1.9.14 will not accept char parameters Status in jackd2 package in Ubuntu: Fix Committed Bug description: trying to set self-connect-mode (for example): $ jack_control eps self-connect-mode e gives: --- engine param set "self-connect-mode" -> "e" Traceback (most recent call last): File "/usr/bin/jack_control", line 400, in main() File "/usr/bin/jack_control", line 283, in main configure_iface.SetParameterValue(['engine', param], python_type_to_jackdbus_type(value, type_char)) File "/usr/bin/jack_control", line 46, in python_type_to_jackdbus_type return dbus.Byte(value); TypeError: Expected a bytes or str of length 1, or an int in the range 0-255 This bug has been fixed upstream in commit ba28ffa @@ -43,7 +43,7 @@ def python_type_to_jackdbus_type(value, type_char): if type_char == "b": return bool_convert(value); elif type_char == "y": -return dbus.Byte(value); +return dbus.Byte(ord(value)); elif type_char == "i": return dbus.Int32(value) elif type_char == "u": To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1899349/+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 1899797] [NEW] dns does not resolve some names after updating kernel from 4.15.0-117 to a newer sub_version like -118 or -121
Public bug reported: This morning i've got a kernel update. After that I could not send mails using thunderbird contacting my mail provider kontent.com. The last working system was: Linux server 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux I tried 4.15.0-118 and 4.15.0-121 but using these I could not resolve: smtp.kontent.com - but I could resolve www.google.de. So it seems that using the newer kernels 118 and 121 I can not resolve some but not all addresses. I returned to kernel 4.15.0-117 and everything works fine again. systemd-resolve --status Global DNS Servers: 172.30.30.1<--- this is an local router next to my "server" DNS Domain: ami.intranet DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (enp0s25) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 172.30.30.1 DNS Domain: ~. ami.intranet andreas@server:~$ host smtp.kontent.com smtp.kontent.com has address 81.88.40.61 doning the same with a newer kernel results in a "SERVERFAIL 2 error" ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1899797 Title: dns does not resolve some names after updating kernel from 4.15.0-117 to a newer sub_version like -118 or -121 Status in systemd package in Ubuntu: New Bug description: This morning i've got a kernel update. After that I could not send mails using thunderbird contacting my mail provider kontent.com. The last working system was: Linux server 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux I tried 4.15.0-118 and 4.15.0-121 but using these I could not resolve: smtp.kontent.com - but I could resolve www.google.de. So it seems that using the newer kernels 118 and 121 I can not resolve some but not all addresses. I returned to kernel 4.15.0-117 and everything works fine again. systemd-resolve --status Global DNS Servers: 172.30.30.1<--- this is an local router next to my "server" DNS Domain: ami.intranet DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (enp0s25) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 172.30.30.1 DNS Domain: ~. ami.intranet andreas@server:~$ host smtp.kontent.com smtp.kontent.com has address 81.88.40.61 doning the same with a newer kernel results in a "SERVERFAIL 2 error" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1899797/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1873678] Re: gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name
Hello Robert, or anyone else affected, Accepted accountsservice into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/accountsservice/0.6.55-0ubuntu12~20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: accountsservice (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1873678 Title: gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Fix Committed Bug description: [Impact] accountsservice includes a function for checking the validity of locales, and it incorrectly considers "C.UTF-8" to be invalid. It leads to incorrect behavior under certain conditions and also a crash if the function was triggered from language-selector-gnome. Even if this only makes a difference in special corner cases, it happens often enough to justify this SRU: https://errors.ubuntu.com/?release=Ubuntu%2020.04=language- selector=year (It's the top ranked crash type in the list.) The version in focal-proposed fixes the issue. [Test case] Make a fresh install of Ubuntu 20.04 (a VM works fine) Once logged in: * Install accountsservice, gir1.2-accountsservice-1.0 and libaccountsservice0 from focal-proposed * Open /etc/default/locale for editing, replace its contents with the single line: LANG=C.UTF-8 and reboot. Open Language Support and change language (drag any language above the "English" item) Open ~/.pam_environment and find that e.g. LANG is now the locale representing the language you selected, while e.g. LC_TIME is set to "C.UTF-8". [Regression risk] This is a oneliner which white list "C.UTF-8" as a valid locale name. I can't think of a case where this would cause unexpected behavior. [Original description] USB live disk (20.04 beta) ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: language-selector-gnome 0.203 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: MATE Date: Sun Apr 19 17:07:26 2020 ExecutablePath: /usr/bin/gnome-language-selector InterpreterPath: /usr/bin/python3.8 LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/gnome-language-selector ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonArgs: ['/usr/bin/gnome-language-selector'] PythonDetails: N/A SourcePackage: language-selector Title: gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1873678/+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 1898603] Re: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers
I was able to get the regular config back by reinstalling the sound packages with apt but now regardless which kernel I use, it shows my headphones as the speakers So to be clear, even on the kernel with working sound before, now it shows headphones as the "output"... same with most recent kernel... "headphones" are output device... any idea how to fix? -- 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/1898603 Title: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers Status in alsa-driver package in Ubuntu: Incomplete Bug description: Starting in Kernel 5.4.0-48-generic on Mint Linux 20 Cinnamon my sound output is detected as "headphones" instead of Speakers when this laptop doesn't even have any headphones connected at all... reverting to a prior kernel fixes the problem and then the output is correctly Speakers... I cannot possibly use sound on Kernel 5.4.0-48-generic and the Mint Linux support chat said I should file a bug for this because this kernel broke something. See attached detailed log reports for more info... Thanks team!!! Best Regards, -Avery Tarasov --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chr0meice2 2656 F pulseaudio /dev/snd/controlC0: chr0meice2 2656 F pulseaudio /dev/snd/pcmC0D0c: chr0meice2 2656 F...m pulseaudio /dev/snd/pcmC0D0p: chr0meice2 2656 F...m pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-10-05 (0 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 NonfreeKernelModules: nvidia_modeset nvidia Package: alsa-driver (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: ulyana Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/01/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.13:bd10/01/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898603/+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 1899780] [NEW] software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow
Public bug reported: :~$ lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 :~$ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.98.9.2 Candidate: 0.98.9.2 Table version: *** 0.98.9.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main i386 Packages 100 /var/lib/dpkg/status 0.98.9 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9.2 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Wed Oct 14 14:49:36 2020 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal software-properties -- 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/1899780 Title: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow Status in software-properties package in Ubuntu: New Bug description: :~$ lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 :~$ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.98.9.2 Candidate: 0.98.9.2 Table version: *** 0.98.9.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main i386 Packages 100 /var/lib/dpkg/status 0.98.9 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9.2 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Wed Oct 14 14:49:36 2020 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1899780/+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 1899764] Re: [Realtek ALC257][Lenovo T14 Gen1] Internal mic or headset mic not detected
We just enabled the mic for this machine under 20.04. Please run 'sudo apt dist-upgrade' then reboot, please use ubuntu kernel, if it doesn't work, please upload the log of 'painfo > painfo.txt'. -- 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/1899764 Title: [Realtek ALC257][Lenovo T14 Gen1] Internal mic or headset mic not detected Status in alsa-driver package in Ubuntu: New Bug description: Hello, I've received a brand new Lenovo T14 Gen 1 (Intel), that suffers of some incompatibilities with Ubuntu. The internal mic is not detected (only analog input is displayed). And when a headset is plug, only the output works. I've tried lots of alsa-base.conf snd-hda-intel overrides without success. Tested on U18 and U20. > uname -a Linux julien-ThinkPad-T14-Gen-1 5.9.0-050900-generic #202010112230 SMP Sun Oct 11 22:34:01 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (tried with stock kernel and kernel-oem too) > arecord -l Liste des Périphériques Matériels CAPTURE carte 0: PCH [HDA Intel PCH], périphérique 0: ALC257 Analog [ALC257 Analog] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 2: ALC257 Alt Analog [ALC257 Alt Analog] Sous-périphériques: 2/2 Sous-périphérique #0: subdevice #0 Sous-périphérique #1: subdevice #1 > cat /proc/asound/card0/codec\#0 https://gist.github.com/julienlafont-tabmo/4ba9311bbb1d3d918532279d7578ba28 > hdajackretask (default configuration) - Internal speaker Ox14 - Black headphone, Right Side, 0x21 - All others: not connected > alsa-info http://alsa-project.org/db/?f=a5af631628bef97a85cace2574b7c6694037130a > alba-base.conf settings tried without success: options snd-hda-intel model=laptop-dmic -- options snd-hda-intel dmic_detect=0 options snd-hda-intel index=0 model=laptop-dmic -- options snd-hda-intel dmic_detect=0 options snd-hda-intel index=1 model=laptop-dmic -- options snd-hda-intel model=auto -- options snd-hda-intel model=headset-mic Do you have some idea to make the mic working? Bests, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1899764/+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 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties
wpa_supplicant exponse properties of the interface that you can read using dbus command such as. Now if the property is empy you should just expose as empty and not fail as it is in the code. sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1 /fi/w1/wpa_supplicant1/Interfaces/1 org.freedesktop.DBus.Properties.GetAll string:fi.w1.wpa_supplicant1.Interface This kind of interface is used by other network services aka connman. I have tested on ubuntu-core and ubuntu 18.04 -- 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/1899262 Title: Broken dbus GetAll message to wpa supplicant interface properties Status in wpa package in Ubuntu: New Bug description: dbus-send is able to read the properties of interface using GetAll. Those information include interface name, status, encryption method, etc. The regression was introduced when someone try to have the Station attribute supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899262/+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 1898418] Re: imagehash python library won't install due to libffi dependency
Groovy does not use libffi7, it uses libffi8.
Focal has libffi7 still.
Ideally you should install libffi-dev package and rebuild your pyenv
installed packages against matching ABI for your host, as the module you
are installing has extensions with binary dependencies, and is not pure
python.
--
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/1898418
Title:
imagehash python library won't install due to libffi dependency
Status in systemd package in Ubuntu:
Invalid
Bug description:
Steps to reproduce:
pip3 install imagehash
Standard output:
ERROR: Command errored out with exit status 1:
command: /home/adam/.pyenv/versions/3.7.2/bin/python3.7 -c 'import sys,
setuptools, tokenize; sys.argv[0] =
'"'"'/tmp/pip-install-utmdqduu/imagehash/setup.py'"'"';
__file__='"'"'/tmp/pip-install-utmdqduu/imagehash/setup.py'"'"';f=getattr(tokenize,
'"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"',
'"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info
--egg-base /tmp/pip-pip-egg-info-aak1sa__
cwd: /tmp/pip-install-utmdqduu/imagehash/
Complete output (11 lines):
Traceback (most recent call last):
File "", line 1, in
File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/site-packages/setuptools/__init__.py",
line 18, in
from setuptools.dist import Distribution, Feature
File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/site-packages/setuptools/dist.py",
line 31, in
from setuptools import windows_support
File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/site-packages/setuptools/windows_support.py",
line 2, in
import ctypes
File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/ctypes/__init__.py", line 7, in
from _ctypes import Union, Structure, Array
ImportError: libffi.so.7: cannot open shared object file: No such file or
directory
ERROR: Command errored out with exit status 1: python setup.py egg_info Check
the logs for full command output.
Logfile
2020-10-04T10:17:33,752 Collecting imagehash
2020-10-04T10:17:33,753 Created temporary directory:
/tmp/pip-unpack-nj1u3xsb
2020-10-04T10:17:33,755 Using cached ImageHash-4.1.0.tar.gz (291 kB)
2020-10-04T10:17:33,764 Added imagehash from
https://files.pythonhosted.org/packages/1a/5d/cc81830be3c4705a46cdbca74439b67f1017881383ba0127c41c4cecb7b3/ImageHash-4.1.0.tar.gz#sha256=978e25d3df66ae8fa4fb24542e46cea6d0724f02c0c760b2de4931a54d5c7482
to build tracker '/tmp/pip-req-tracker-jayrgcrc'
2020-10-04T10:17:33,764 Running setup.py
(path:/tmp/pip-install-khjz0dgm/imagehash/setup.py) egg_info for package
imagehash
2020-10-04T10:17:33,764 Created temporary directory:
/tmp/pip-pip-egg-info-59aoxqk7
2020-10-04T10:17:33,765 Running command python setup.py egg_info
2020-10-04T10:17:33,848 Traceback (most recent call last):
2020-10-04T10:17:33,848 File "", line 1, in
2020-10-04T10:17:33,848 File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/site-packages/setuptools/__init__.py",
line 18, in
2020-10-04T10:17:33,848 from setuptools.dist import Distribution,
Feature
2020-10-04T10:17:33,848 File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/site-packages/setuptools/dist.py",
line 31, in
2020-10-04T10:17:33,848 from setuptools import windows_support
2020-10-04T10:17:33,848 File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/site-packages/setuptools/windows_support.py",
line 2, in
2020-10-04T10:17:33,849 import ctypes
2020-10-04T10:17:33,849 File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/ctypes/__init__.py", line 7, in
2020-10-04T10:17:33,849 from _ctypes import Union, Structure, Array
2020-10-04T10:17:33,849 ImportError: libffi.so.7: cannot open shared
object file: No such file or directory
2020-10-04T10:17:33,855 ERROR: Command errored out with exit status 1: python
setup.py egg_info Check the logs for full command output.
2020-10-04T10:17:33,855 Exception information:
2020-10-04T10:17:33,855 Traceback (most recent call last):
2020-10-04T10:17:33,855 File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/site-packages/pip/_internal/cli/base_command.py",
line 228, in _main
2020-10-04T10:17:33,855 status = self.run(options, args)
2020-10-04T10:17:33,855 File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/site-packages/pip/_internal/cli/req_command.py",
line 182, in wrapper
2020-10-04T10:17:33,855 return func(self, options, args)
2020-10-04T10:17:33,855 File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/site-packages/pip/_internal/commands/install.py",
line 324, in run
2020-10-04T10:17:33,855 reqs,
[Touch-packages] [Bug 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties
For releasing this as an SRU, https://wiki.ubuntu.com/StableReleaseUpdates needs to be followed. Specifically we will need SRU template completed as outlined in https://wiki.ubuntu.com/StableReleaseUpdates Most importnatly what would be the detailed [Test Case] to reproduce the issue? (Such that we can verify the issue exists, and gets fixed by the proposed update). And what is regression potential of such an update. ** Tags added: rls-bb-incoming rls-ff-incoming rls-gg-incoming rls-hh- incoming -- 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/1899262 Title: Broken dbus GetAll message to wpa supplicant interface properties Status in wpa package in Ubuntu: New Bug description: dbus-send is able to read the properties of interface using GetAll. Those information include interface name, status, encryption method, etc. The regression was introduced when someone try to have the Station attribute supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899262/+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 1897744] Re: VerifyHostKeyDNS not working due to missing trust-ad flag
I just re-debugged into the same case - now marked as dup. You might consider using https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1898590/comments/7 as test steps to verify that once uploaded to focal-proposed. -- 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/1897744 Title: VerifyHostKeyDNS not working due to missing trust-ad flag Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: In Progress Bug description: [impact] without trust-ad resolv.conf option, glibc will strip AD from systemd- resolved responses. one thing this will prevent working is ssh VerifyHostKeyDNS [test case] setup a target system to ssh into, and create a SSHFP DNS record for its public key. on a different source system, setup dns to enable DNSSEC, and attempt to ssh to the target system using the VerifyHostKeyDNS=yes option. setup of the SSHFP is out of scope for this bug, but e.g.: https://en.wikipedia.org/wiki/SSHFP_record https://tools.ietf.org/html/rfc4255 [regression potential] regressions would likely involve DNS lookup failures, probably if DNSSEC is enabled but possibly even without, and likely when the application requesting the dns lookup processes the response AD. [scope] this is needed only in focal. glibc first stripped the AD in version 2.31, so this is not needed in bionic or earlier. this was added upstream in commit a742f9828ea which was included in v246, so this is fixed already in groovy. [original description] Hi, 1) Description: Ubuntu 20.04.1 LTS Release: 20.04 2) systemd:245.4-4ubuntu3.2 3) I set VerifyHostKeyDNS to YES and hosts are automatically verified via sshfp. 4) I still get the security question Matching host key fingerprint found in DNS. Are you sure you want to continue connecting (yes/no/[fingerprint])? The issue is known and fixed in systemd v246. https://github.com/systemd/systemd/pull/16072 Best regards Daniel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897744/+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 1898590] Re: Verify DNS fingerprints not working
*** This bug is a duplicate of bug 1897744 *** https://bugs.launchpad.net/bugs/1897744 @Dan - now I saw your update - that might have shortened my dnssec trip :-) It indeed is a duplicate of that - marking as such. ** This bug has been marked a duplicate of bug 1897744 VerifyHostKeyDNS not working due to missing trust-ad flag -- 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/1898590 Title: Verify DNS fingerprints not working Status in systemd: Unknown Status in glibc package in Ubuntu: Invalid Status in openssh package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in openssh package in Debian: Unknown Bug description: When setting in /etc/ssh/ssh_config VerifyHostKeyDNS to yes the fingerprints are fetched, but the result is always: debug1: found n insecure fingerprints in DNS With dig +dnssec -tsshfp hostname the result is ok: ad flg is set. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1898590/+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 1898590] Re: Verify DNS fingerprints not working
*** This bug is a duplicate of bug 1897744 *** https://bugs.launchpad.net/bugs/1897744 Summary: - we understand what happened - we have a workaround for users by changing a config - we have a systemd change that can be considered to be backported by the systemd package maintainers ** Tags removed: server-next -- 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/1898590 Title: Verify DNS fingerprints not working Status in systemd: Unknown Status in glibc package in Ubuntu: Invalid Status in openssh package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in openssh package in Debian: Unknown Bug description: When setting in /etc/ssh/ssh_config VerifyHostKeyDNS to yes the fingerprints are fetched, but the result is always: debug1: found n insecure fingerprints in DNS With dig +dnssec -tsshfp hostname the result is ok: ad flg is set. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1898590/+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 1898590] Re: Verify DNS fingerprints not working
*** This bug is a duplicate of bug 1897744 *** https://bugs.launchpad.net/bugs/1897744 TL;DR: one affected by this upgrade triggered behavior change needs to set options edns0 trust-ad in /etc/resolv.conf to fix the issue. And as usual, once you already know what things are about - then (but only then :-/ ) you find the important related issues - reported by Laney \o/ Subscribing him to the bug FYI Debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960023 I'll add a bug link to Debian. Discussed and declared to be systed issue and asked to file upstream. Which led to ... Systemd https://github.com/systemd/systemd/issues/15767 This is fixed in newer systemd and will set trust-ad I'll add a systemd task to consider backporting this to Focal -- 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/1898590 Title: Verify DNS fingerprints not working Status in systemd: Unknown Status in glibc package in Ubuntu: Invalid Status in openssh package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in openssh package in Debian: Unknown Bug description: When setting in /etc/ssh/ssh_config VerifyHostKeyDNS to yes the fingerprints are fetched, but the result is always: debug1: found n insecure fingerprints in DNS With dig +dnssec -tsshfp hostname the result is ok: ad flg is set. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1898590/+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 1898590] Re: Verify DNS fingerprints not working
*** This bug is a duplicate of bug 1897744 *** https://bugs.launchpad.net/bugs/1897744 ok up/downgrading just "libc6" is enough to trigger. I also found that libc6 from Eoan version 2.30-0ubuntu2.2 is good. So it is new in 2.31! The changelog mentions soem DNSSEC https://sourceware.org/legacy-ml/libc-announce/2020/msg1.html "* The DNS stub resolver will optionally send the AD (authenticated data) bit in queries if the trust-ad option is set via the options directive in /etc/resolv.conf (or if RES_TRUSTAD is set in _res.options). In this mode, the AD bit, as provided by the name server, is available to applications which call res_search and related functions. In the default mode, the AD bit is not set in queries, and it is automatically cleared in responses, indicating a lack of DNSSEC validation. (Therefore, the name servers and the network path to them are treated as untrusted.)" Once I knew that it was a small step and I found that options edns0 trust-ad in /etc/resolv.conf indeed fixes the issue. I'm not sure if openssh would be entitled to set RES_TRUSTAD is set in _res.options. Maybe not as that is more a decision of the admin setting up and configuring the system than the openssh software. Therefore I think this is actually a little detail that upgraders that use dnssec for openssh (and maybe others) via libc6 resolv need to consider. ** Bug watch added: Debian Bug tracker #960023 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960023 ** Also affects: openssh (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960023 Importance: Unknown Status: Unknown ** Bug watch added: github.com/systemd/systemd/issues #15767 https://github.com/systemd/systemd/issues/15767 ** Also affects: systemd via https://github.com/systemd/systemd/issues/15767 Importance: Unknown Status: Unknown ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Also affects: glibc (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: openssh (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: glibc (Ubuntu Focal) ** Changed in: openssh (Ubuntu) Status: Confirmed => Invalid ** No longer affects: openssh (Ubuntu Focal) ** Changed in: glibc (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/1898590 Title: Verify DNS fingerprints not working Status in systemd: Unknown Status in glibc package in Ubuntu: Invalid Status in openssh package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in openssh package in Debian: Unknown Bug description: When setting in /etc/ssh/ssh_config VerifyHostKeyDNS to yes the fingerprints are fetched, but the result is always: debug1: found n insecure fingerprints in DNS With dig +dnssec -tsshfp hostname the result is ok: ad flg is set. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1898590/+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 1899766] [NEW] Xorg freeze after selecting large cursor
Public bug reported: After selecting the largest cursor in accessibility settings, the whole system froze. I had to use Magic SysRq to reboot the system. After reboot, the login screen was OK but after logging in it would immediately freeze again. Workaround: from login screen, switch to a VT with Ctrl-F2, log in and run dconf reset /org/gnome/desktop/interface/cursor-size I was playing with the cursor size because I see different cursor sizes in different apps and it was annoying me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 11:25:23 2020 DistUpgraded: 2020-05-02 16:08:06,720 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d] Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d] InstallationDate: Installed on 2018-12-11 (672 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-02 (164 days ago) dmi.bios.date: 07/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.1:bd07/09/2020:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze 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/1899766 Title: Xorg freeze after selecting large cursor Status in xorg package in Ubuntu: New Bug description: After selecting the largest cursor in accessibility settings, the whole system froze. I had to use Magic SysRq to reboot the system. After reboot, the login screen was OK but after logging in it would immediately freeze again. Workaround: from login screen, switch to a VT with Ctrl-F2, log in and run dconf reset /org/gnome/desktop/interface/cursor-size I was playing with the cursor size because I see different cursor sizes in different apps and it was annoying me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0
[Touch-packages] [Bug 1898590] Re: Verify DNS fingerprints not working
As a first step I tried to make sure this actually is a change in openssh. Because my reading of the issues referred above has shown that not all of the verification is done inside ssh but partially in glibc. So I upgraded on the bionic test system step by step. The upgrade dependency list for openssh-client is "libc-bin libc6 libgssapi-krb5-2 libkrb5-3 libkrb5support0 locales" I found that the bug is reproducible with openssh-client 1:7.6p1-4ubuntu0.3 running against the newer glibc. I can switch in/out the reported bug be switching on a Bionic system between glibc 2.27-3ubuntu1.2 - Bionic - Good 2.31-0ubuntu9.1 - Focal - Bad ** Also affects: glibc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1898590 Title: Verify DNS fingerprints not working Status in glibc package in Ubuntu: New Status in openssh package in Ubuntu: Confirmed Bug description: When setting in /etc/ssh/ssh_config VerifyHostKeyDNS to yes the fingerprints are fetched, but the result is always: debug1: found n insecure fingerprints in DNS With dig +dnssec -tsshfp hostname the result is ok: ad flg is set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1898590/+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
