[Touch-packages] [Bug 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke
First I would need some feedback that this is indeed fixing the problem. PPA is for maintaining software outside of the repos, I don't intend to maintain it, the ubuntu team needs to fix this, which they should be able to do easily if there is a patch. -- 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/1881549 Title: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Incomplete Status in wpa package in Ubuntu: New Bug description: Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1438 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-09 (329 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+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 1880041] Re: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later
This also affect me on Ubuntu 18.04.4 LTS with kernel 5.3.0-53-generic * AMD® Ryzen 7 3750h with radeon vega mobile gfx × 8 * GeForce GTX 1650/PCIe/SSE2 Rolling back to 5.3.0-51-generic will solves the problem -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later Status in DRI: Unknown Status in libdrm package in Ubuntu: Confirmed Status in linux-meta-hwe package in Ubuntu: Confirmed Bug description: When booting up Ubuntu 18.04 with a kernel version of 5.3.0-52 or later (including 5.3.0-53), everything seems to be working as usual. However, when I shutdown, the system will only soft shutdown, with the CPU still running at full power, forcing me to hold down the power button to fully power off affected systems. If I reboot, it will cause the system to hang and not respond. Either way, a hard reset or poweroff will be required, and this is not an option for systems being remotely accessed. It is not possible for me to collect kernel logs at this point, unless something wrong is happening in those kernel versions before the actual shutdown. It is possible that this may also occur on Ubuntu 20.04 with kernel versions 5.4.0-29 and later, but I have not yet tested this out. This problem is occurring on both my desktop and laptop computers which respectively are: * AsRock B450 Pro4 with AMD Ryzen 3 3200G APU * Lenovo ThinkPad A485 with AMD Ryzen 5 Pro 2500U mobile APU In the meantime, I am stuck on kernel version 5.3.0-51, as that is the last working 5.3.x kernel version offered in the standard Ubuntu repositories that doesn't have this problem, without me having to use PPAs. I don't know if this problem also occurs on systems with Intel CPUs, as I don't own any recently-made system (last 3 years from 2017) with such CPUs to test if this problem occurs on them. To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+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 1745963] Re: no displaY
** Package changed: xorg (Ubuntu) => xorg-server (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/1745963 Title: no displaY Status in xorg-server package in Ubuntu: New Bug description: DISPLAY fades out after standby mode ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jan 29 08:19:44 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter [1039:6351] (rev 10) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Technology Solutions 771/671 PCIE VGA Display Adapter [1734:1125] InstallationDate: Installed on 2018-01-26 (2 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 15d9:0a4d Trust International B.V. Optical Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: FUJITSU SIEMENS ESPRIMO Mobile V5535 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) LANG=pt_PT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=086e92bc-3d33-4968-a4b8-3a36e8a3e993 ro quiet plymouth:debug=1 splash Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/07 dmi.bios.vendor: Phoenix dmi.bios.version: V1.03 dmi.board.name: Z17M2.0 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: V1.02 dmi.chassis.asset.tag: User Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnPhoenix:bvrV1.03:bd11/30/07:svnFUJITSUSIEMENS:pnESPRIMOMobileV5535:pvrV1.02:rvnFUJITSUSIEMENS:rnZ17M2.0:rvrV1.02:cvnFUJITSUSIEMENS:ct1:cvrV1.02: dmi.product.name: ESPRIMO Mobile V5535 dmi.product.version: V1.02 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Jan 28 23:35:43 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1745963/+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 1752047] Re: Xdiagnose
What was the original problem you experienced? Is it still happening? ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (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/1752047 Title: Xdiagnose Status in xorg-server package in Ubuntu: Incomplete Bug description: Comme suite aux résultats du programme XDIAGNOSE. J'utilise unity depuis son origine mais je ne suis pas un as de l'informatique. salutations et bravo pour ce que vous réaliser pour un retraité de 76 ans; ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Feb 27 11:12:54 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.40, 4.13.0-32-generic, x86_64: installed virtualbox, 5.0.40, 4.13.0-36-generic, x86_64: installed GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated Graphics Controller [1179:ff40] Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated Graphics Controller [1179:ff40] InstallationDate: Installed on 2018-02-02 (24 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: TOSHIBA SATELLITE U500 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=b5991ca8-7ff6-4b0c-b575-2f859c57a519 ro plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd06/08/2009:svnTOSHIBA:pnSATELLITEU500:pvrPSU52E-01200GFR:rvnTOSHIBA:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: SATELLITE U500 dmi.product.version: PSU52E-01200GFR dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Feb 27 11:10:55 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1752047/+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 1881970] Re: [Satellite Pro L550, Realtek ALC272, Speaker, Internal] No sound at all
Please uninstall these packages if you have them: jackd timidity and then reboot. Does the problem still occur? ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881970 Title: [Satellite Pro L550, Realtek ALC272, Speaker, Internal] No sound at all Status in pulseaudio package in Ubuntu: Incomplete Bug description: Problem of son. Sortie Fictive. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: auguen 1324 F pulseaudio /dev/snd/controlC0: auguen 1324 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 23:10:09 2020 InstallationDate: Installed on 2020-06-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Audio interne - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: auguen 1324 F pulseaudio /dev/snd/controlC0: auguen 1324 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Satellite Pro L550, Realtek ALC272, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2009 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.90 dmi.board.name: KTWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.90:bd12/18/2009:svnTOSHIBA:pnSatelliteProL550:pvrPSLW9E-01600GFR:rvnTOSHIBA:rnKTWAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: Satellite Pro L550 dmi.product.sku: 012345678912345678912345678 dmi.product.version: PSLW9E-01600GFR dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881970/+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 1873384] Re: [Dell Inspiron 5577] Headphone has no sound out
*** This bug is a duplicate of bug 1876065 *** https://bugs.launchpad.net/bugs/1876065 Just in case this can help anybody. On Ubuntu Studio 20.04 (Xfce), headphones audio started to work after I selected "Audio mixer..." -> "Input Devices" -> "Headset Microphone (plugged in)". It was "Microphone (plugged in) before I changed. No idea why I had to change something in "Input Devices" to make work something else in "Output Devices" ;-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1873384 Title: [Dell Inspiron 5577] Headphone has no sound out Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Computer: Dell inspiron 15 5577 Gaming intel i5 7300HQ version System: Kubuntu 20.04 Bug: Plug-in headphone has no sound out, meanwhile computer's speaker is okay when unplugged the headphone. Additional information: Headphone is okay when kubuntu 18.04.3 is installed on the computer. Alsamixer is checked and headphone are not mute. Headphone plugin state can be correctly detected, and speaker can automatically mute until headphone unplugged. External usb soundcard is usable with headphone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.12 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 17 11:14:43 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200416) ProcEnviron: LANGUAGE=zh_CN:zh TERM=xterm-256color PATH=(custom, no user) LANG=zh_CN.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sherlockholmes 1242 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200416) MachineType: Dell Inc. Inspiron 5577 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=18303cc3-5e85-4677-8bca-60324bae9608 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 090HMC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd12/02/2018:svnDellInc.:pnInspiron5577:pvr1.1.3:rvnDellInc.:rn090HMC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5577 dmi.product.sku: 07E1 dmi.product.version: 1.1.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873384/+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 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content
** Branch linked: lp:~ubuntu-core-dev/ubuntu/focal/apport/ubuntu -- 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/1427600 Title: apport-unpack: ValueError: ['UserGroups'] has no binary content Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Triaged Status in apport source package in Focal: In Progress Status in apport source package in Groovy: Fix Released Bug description: [Impact] apport-unpack crashes when trying to unpack a crash [Test Case] On a system running 20.04 LTS: 1) create an additional user who is only a member of their own group e.g. bdmurray@clean-focal-amd64:~$ id crashy uid=1001(crashy) gid=1001(crashy) groups=1001(crashy) 2) Launch a process as that user 3) kill -11 that process 4) Confirm there is a crash file in /var/crash for that process 5) Run apport-unpack on that .crash file With the version of apport from -proposed you will not get another crash file when unpacking the crash file. [Regression Potential] We are just setting UserGroups to ' ' as opposed to having it be completely empty so there isn't any chance for regression. When running apport-unpack to get at a core dump laney@raleigh> sudo apport-unpack _usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz [sudo] password for laney: Traceback (most recent call last): File "/usr/bin/apport-unpack", line 73, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in extract_keys [item for item, element in b64_block.items() if element is False]) ValueError: ['UserGroups'] has no binary content laney@raleigh> apport-cli --version 2.16.2 It's not terrible, because most files are unpacked (those which sort before UserGroups, I guess). ProblemType: BugDistroRelease: Ubuntu 15.04 Package: apport 2.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportLog: ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 10:09:26 2015 InstallationDate: Installed on 2012-10-07 (876 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) PackageArchitecture: allSourcePackage: apport UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+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 1881970] Re: [Satellite Pro L550, Realtek ALC272, Speaker, Internal] No sound at all
** Package changed: ubuntu => pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881970 Title: [Satellite Pro L550, Realtek ALC272, Speaker, Internal] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: Problem of son. Sortie Fictive. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: auguen 1324 F pulseaudio /dev/snd/controlC0: auguen 1324 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 23:10:09 2020 InstallationDate: Installed on 2020-06-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Audio interne - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: auguen 1324 F pulseaudio /dev/snd/controlC0: auguen 1324 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Satellite Pro L550, Realtek ALC272, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2009 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.90 dmi.board.name: KTWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.90:bd12/18/2009:svnTOSHIBA:pnSatelliteProL550:pvrPSLW9E-01600GFR:rvnTOSHIBA:rnKTWAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: Satellite Pro L550 dmi.product.sku: 012345678912345678912345678 dmi.product.version: PSLW9E-01600GFR dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881970/+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 1668049] Re: lxd cannot shutdown container
** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1668049 Title: lxd cannot shutdown container Status in systemd package in Ubuntu: Fix Released Bug description: I found this issue when working with lxd and submitted a ticket there but the lxc people said it was related to systemd, not lxc. The issue is: I have a container running under lxc/lxd. lxc stop of the container does not work whereas if I execute "shutdown now" inside the container it does stop as expected. The associated lxd ticket is here: https://github.com/lxc/lxd/issues/2947 The output of journalctl -a is at the end of this message The syslog of that same run can be found here: http://paste.ubuntu.com/24071244/ and this is the output of ps aux: USERPID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.1 37808 4576 ?Ss 11:19 0:00 /sbin/init root 48 0.0 0.0 35276 3004 ?Ss 11:19 0:00 /lib/systemd/systemd-journald root 49 0.0 0.0 41724 1912 ?Ss 11:19 0:00 /lib/systemd/systemd-udevd message+514 0.0 0.0 42900 2460 ?Ss 11:19 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation root704 0.0 0.0 18252 2508 ?Ss 11:55 0:00 bash root720 0.0 0.0 34556 1992 ?R+ 11:59 0:00 ps aux Note that this may be timing related. If I stop the container immediately after starting things work. If I stop after a minute or so, the stop will not get through. (even not on a 2nd or 3rd attempt). However if I leave the container for a while then a new lxc stop will terminate the container. (this happened after an hour or so). The issue is reproducible but seems to be dependend on what is running inside the container. container runs ubuntu 16.04 on a 16.04 host. systemd --version says: systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN lxc sends SIGRTMIN+3 to systemd to stop. This was apparently discussed here: https://github.com/lxc/lxc/issues/1085 Let me know if more info is needed. Frans -- Logs begin at Sun 2017-02-26 11:19:12 UTC, end at Sun 2017-02-26 11:23:05 UTC. -- Feb 26 11:19:12 D-wan-61-1 systemd-journald[48]: Runtime journal (/run/log/journal/) is 8.0M, max 196.7M, 188.7M free. Feb 26 11:19:12 D-wan-61-1 systemd-journald[48]: Journal started Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '4 4 1 7' to 'kernel/printk', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '176' to 'kernel/sysrq', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '1' to 'fs/protected_symlinks', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '1' to 'net/ipv4/tcp_syncookies', ignoring: No such file or directory Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '1' to 'kernel/kptr_restrict', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '1' to 'fs/protected_hardlinks', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '1' to 'kernel/yama/ptrace_scope', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '65536' to 'vm/mmap_min_addr', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE Feb 26 11:19:12 D-wan-61-1 systemd[1]: Failed to start Apply Kernel Variables. Feb 26 11:19:12 D-wan-61-1 systemd[1]: systemd-sysctl.service: Unit entered failed state. Feb 26 11:19:12 D-wan-61-1 systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'. Feb 26 11:19:12 D-wan-61-1 systemd-journald[48]: Forwarding to syslog missed 1 messages. Feb 26 11:19:12 D-wan-61-1 systemd[1]: Started Uncomplicated firewall. Feb 26 11:19:12 D-wan-61-1 systemd[1]: Failed to reset devices.list on /system.slice/ufw.service: Operation not permitted Feb 26 11:19:12 D-wan-61-1 systemd[1]: Started udev Kernel Device Manager. Feb 26 11:19:12 D-wan-61-1 mount[45]: mount: permission denied Feb 26 11:19:12 D-wan-61-1 systemd[1]: Started Nameserver information manager. Feb 26 11:19:12 D-wan-61-1 systemd[1]: dev-hugepages.mount: Mount process exited, code=exited status=32 Feb 26 11:19:12 D-wan-61-1 systemd[1]: Failed to mount Huge Pages File System. Feb 26 11:19:12 D-wan-61-1 systemd[1]: dev-hugepages.mount: Unit entered failed state. Feb 26 11:19:12 D-wan-61-1 systemd-remount-fs[44]: mount: can't find
[Touch-packages] [Bug 1881970] [NEW] [Satellite Pro L550, Realtek ALC272, Speaker, Internal] No sound at all
You have been subscribed to a public bug: Problem of son. Sortie Fictive. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: auguen 1324 F pulseaudio /dev/snd/controlC0: auguen 1324 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 23:10:09 2020 InstallationDate: Installed on 2020-06-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Audio interne - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: auguen 1324 F pulseaudio /dev/snd/controlC0: auguen 1324 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Satellite Pro L550, Realtek ALC272, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2009 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.90 dmi.board.name: KTWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.90:bd12/18/2009:svnTOSHIBA:pnSatelliteProL550:pvrPSLW9E-01600GFR:rvnTOSHIBA:rnKTWAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: Satellite Pro L550 dmi.product.sku: 012345678912345678912345678 dmi.product.version: PSLW9E-01600GFR dmi.sys.vendor: TOSHIBA ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- [Satellite Pro L550, Realtek ALC272, Speaker, Internal] No sound at all https://bugs.launchpad.net/bugs/1881970 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio 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 1857769] Re: program linked to protobuf crashes before main
This is still crashing on an up to date 20.04 build. This is a show
stopper for me using 20.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1857769
Title:
program linked to protobuf crashes before main
Status in protobuf package in Ubuntu:
New
Bug description:
This simple test crashes on a system that I installed Ubuntu Server 20.04
daily build on yesterday:
echo "syntax = \"proto2\";" >| test.pbc
echo "message TestMsg" >> test.pbc
echo "{" >> test.pbc
echo " required double f1 = 1;" >> test.pbc
echo "}" >> test.pbc
echo "int main() {return 0;}" >| test.cc
protoc --cpp_out=. ./test.pbc
g++ -c -o test.pbc.pb.o test.pbc.pb.cc
g++ -c -o test.o test.cc
g++ -o test test.o test.pbc.pb.o -lprotobuf
./test
terminate called after throwing an instance of 'std::system_error'
what(): Unknown error -1
Aborted (core dumped)
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: protobuf-compiler 3.6.1.3-2ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
Date: Sat Dec 28 19:10:20 2019
InstallationDate: Installed on 2019-12-27 (1 days ago)
InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64
(20191227)
SourcePackage: protobuf
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protobuf/+bug/1857769/+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 1881859] Re: RaspberryPi and "openssl:Error: 'rehash' is an invalid command"
What's the output of "openssl version -a"? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1881859 Title: RaspberryPi and "openssl:Error: 'rehash' is an invalid command" Status in ca-certificates package in Ubuntu: New Bug description: Hi Everyone, I ran dist-upgrade today on my RPI-3. It resulted in: ``` Calculating upgrade... Done The following packages will be upgraded: armbian-bionic-desktop armbian-config armbian-firmware ca-certificates chromium-browser chromium-chromedriver chromium-codecs-ffmpeg-extra python3-software-properties software-properties-common 9 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ``` And: ``` ... Setting up chromium-codecs-ffmpeg-extra (83.0.4103.61-0ubuntu0.18.04.1) ... Setting up python3-software-properties (0.96.24.32.13) ... Setting up ca-certificates (20190110~18.04.1) ... Updating certificates in /etc/ssl/certs... openssl:Error: 'rehash' is an invalid command. Standard commands asn1parse caciphers cms crl crl2pkcs7 dgst dh dhparam dsa dsaparam ec ... 127 added, 8 removed; done. Setting up software-properties-common (0.96.24.32.13) ... Setting up chromium-browser (83.0.4103.61-0ubuntu0.18.04.1) ... ``` Operating System: ``` $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic ``` And finally: ``` $ apt-cache show ca-certificates Package: ca-certificates Architecture: all Version: 20190110~18.04.1 Multi-Arch: foreign Priority: important Section: misc Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Michael Shuler Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 382 Depends: openssl (>= 1.1.0), debconf (>= 0.5) | debconf-2.0 Breaks: ca-certificates-java (<< 20121112+nmu1) Enhances: openssl Filename: pool/main/c/ca-certificates/ca-certificates_20190110~18.04.1_all.deb Size: 145500 MD5sum: f0c73db6f5e857f13af04aaa736f87f0 SHA1: 8a3d4583491b426691a986ef11b1c805c2d4cf54 SHA256: fcfa84619207690491a3f9ab898de3fb2d46eeb7a73d525b91d05e7655815f5b Description: Common CA certificates Description-md5: e867d2a359bea1800b5bff209fc65bd1 Task: minimal Supported: 5y Package: ca-certificates Architecture: all Version: 20180409 Multi-Arch: foreign Priority: important Section: misc Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Michael Shuler Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 392 Depends: openssl (>= 1.1.0), debconf (>= 0.5) | debconf-2.0 Breaks: ca-certificates-java (<< 20121112+nmu1) Enhances: openssl Filename: pool/main/c/ca-certificates/ca-certificates_20180409_all.deb Size: 150932 MD5sum: eae40792673dcb994af86284d0a01f36 SHA1: 8ac5ac1506810b0483f0b80b0652071348459fc4 SHA256: 195ffe05ae7d060146f890b1db225f5e8c3a8c505ffbea1fba30a520a1cd58d8 Description: Common CA certificates Description-md5: e867d2a359bea1800b5bff209fc65bd1 Task: minimal Supported: 5y $ apt-cache show openssl Package: openssl Architecture: armhf Version: 1.1.1-1ubuntu2.1~18.04.6 Multi-Arch: foreign Priority: important Section: utils Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian OpenSSL Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 986 Depends: libc6 (>= 2.15), libssl1.1 (>= 1.1.1) Suggests: ca-certificates Filename: pool/main/o/openssl/openssl_1.1.1-1ubuntu2.1~18.04.6_armhf.deb Size: 589160 MD5sum: 37a31fce651134a5b057c9f6f356aaf2 SHA1: 476816221f03bae71ecd760e1e4e6d155f85e7c1 SHA256: 2787b66aba181e230f36ce49600b3a7d9dea7695aa332da0496a5e1a62281d39 Homepage: https://www.openssl.org/ Description: Secure Sockets Layer toolkit - cryptographic utility Description-md5: 9b6de2bb6e1d9016aeb0f00bcf6617bd Task: minimal Supported: 5y Package: openssl Architecture: armhf Version: 1.1.0g-2ubuntu4 Multi-Arch: foreign Priority: important Section: utils Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian OpenSSL Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 883 Depends: libc6 (>= 2.15), libssl1.1 (>= 1.1.0) Suggests: ca-certificates Filename: pool/main/o/openssl/openssl_1.1.0g-2ubuntu4_armhf.deb Size: 509616 MD5sum: 0645cdd015e63ab37fcebf6b5c81b823 SHA1: 89852170f97d4dc2e6a0e83b045318fd05342634 SHA256: 57adec97bf6dec47c6079ea8b94598e853334e99c88c5e86afa838cbc57fcd32 Homepage: https://www.openssl.org/ Description: Secure Sockets Layer toolkit - cryptographic utility Description-md5:
[Touch-packages] [Bug 1881972] Re: systemd-networkd crashes with invalid pointer
can you attach one of the coredumps? That will significantly help with
finding where exactly the problem is.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
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/1881972
Title:
systemd-networkd crashes with invalid pointer
Status in systemd package in Ubuntu:
Incomplete
Bug description:
This is a serious regression with systemd-networkd that I ran in to
while setting up a NAT router in AWS. The AWS AMI ubuntu/images/hvm-
ssd/ubuntu-bionic-18.04-amd64-server-20200131 with
systemd-237-3ubuntu10.33 does NOT have the problem, but the next most
recent AWS AMI ubuntu/images/hvm-ssd/ubuntu-
bionic-18.04-amd64-server-20200311 with systemd-including
237-3ubuntu10.39 does.
Also, a system booted from the (good) 20200131 AMI starts showing the
problem after updating only systemd (to 237-3ubuntu10.41) and its
direct dependencies (e.g. 'apt-get install systemd'). So I'm fairly
confident that a change to the systemd package between
237-3ubuntu10.33 and 237-3ubuntu10.39 introduced the problem and it is
still present.
On the NAT router I use three interfaces and have separate routing
tables for admin and forwarded traffic. Things come up fine initially
but every 30-60 minutes (DHCP lease renewal time?) one or more
interfaces is reconfigured and most of the time systemd-networkd will
crash and need to be restarted. Eventually the system becomes
unreachable when the default crash loop backoff logic prevents the
network service from being restarted at all. The log excerpt attached
illustrates the crash loop.
Also including the netplan and networkd config files below.
# grep . /etc/netplan/*
/etc/netplan/50-cloud-init.yaml:# This file is generated from information
provided by the datasource. Changes
/etc/netplan/50-cloud-init.yaml:# to it will not persist across an instance
reboot. To disable cloud-init's
/etc/netplan/50-cloud-init.yaml:# network configuration capabilities, write a
file
/etc/netplan/50-cloud-init.yaml:#
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
/etc/netplan/50-cloud-init.yaml:# network: {config: disabled}
/etc/netplan/50-cloud-init.yaml:network:
/etc/netplan/50-cloud-init.yaml:version: 2
/etc/netplan/50-cloud-init.yaml:ethernets:
/etc/netplan/50-cloud-init.yaml:ens5:
/etc/netplan/50-cloud-init.yaml:dhcp4: true
/etc/netplan/50-cloud-init.yaml:match:
/etc/netplan/50-cloud-init.yaml:macaddress: xx:xx:xx:xx:xx:xx
/etc/netplan/50-cloud-init.yaml:set-name: ens5
/etc/netplan/99_config.yaml:network:
/etc/netplan/99_config.yaml: version: 2
/etc/netplan/99_config.yaml: renderer: networkd
/etc/netplan/99_config.yaml: ethernets:
/etc/netplan/99_config.yaml:ens6:
/etc/netplan/99_config.yaml: match:
/etc/netplan/99_config.yaml:macaddress: yy:yy:yy:yy:yy:yy
/etc/netplan/99_config.yaml: dhcp4: true
/etc/netplan/99_config.yaml: dhcp4-overrides:
/etc/netplan/99_config.yaml:use-routes: false
/etc/netplan/99_config.yaml:ens7:
/etc/netplan/99_config.yaml: match:
/etc/netplan/99_config.yaml:macaddress: zz:zz:zz:zz:zz:zz
/etc/netplan/99_config.yaml: mtu: 1500
/etc/netplan/99_config.yaml: dhcp4: true
/etc/netplan/99_config.yaml: dhcp4-overrides:
/etc/netplan/99_config.yaml:use-mtu: false
/etc/netplan/99_config.yaml:use-routes: false
# grep . /etc/networkd-dispatcher/*/*
/etc/networkd-dispatcher/configured.d/nat:#!/bin/bash
/etc/networkd-dispatcher/configured.d/nat:# Do additional configuration for
the inside and outside interfaces
/etc/networkd-dispatcher/configured.d/nat:# route table used for
forwarded/routed/natted traffic
/etc/networkd-dispatcher/configured.d/nat:FWD_TABLE=99
/etc/networkd-dispatcher/configured.d/nat:if [ "${IFACE}" = "ens6" ]; then
/etc/networkd-dispatcher/configured.d/nat: # delete link-local route for
inside in default table
/etc/networkd-dispatcher/configured.d/nat: /sbin/ip route delete 10.0.3.0/24
2>/dev/null || true
/etc/networkd-dispatcher/configured.d/nat: # add link-local route for inside
in table 99
/etc/networkd-dispatcher/configured.d/nat: /sbin/ip route replace
10.0.3.0/24 dev ens6 scope link src 10.0.3.171 table ${FWD_TABLE}
/etc/networkd-dispatcher/configured.d/nat: # add routes to VPC cidrs via
inside gateway in table 99
/etc/networkd-dispatcher/configured.d/nat: /sbin/ip route replace
10.0.0.0/16 via 10.0.3.1 table ${FWD_TABLE}
/etc/networkd-dispatcher/configured.d/nat: # add rules to use table 99
/etc/networkd-dispatcher/configured.d/nat: /sbin/ip rule add iif ens6
lookup ${FWD_TABLE}
/etc/networkd-dispatcher/configured.d/nat: /sbin/ip rule add oif ens6
[Touch-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
** Changed in: pulseaudio (Ubuntu Focal) Milestone: None => ubuntu-20.04.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Focal: In Progress Status in pulseaudio source package in Groovy: In Progress Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1866194/+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 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks
** Tags added: rls-ff-incoming -- 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/1867007 Title: zfs-initramfs fails with multiple rpool on separate disks Status in grub2 package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: Fix Released Bug description: == Test Case == 1. On a multi disks setup, install Ubuntu with ZFS on disk 1 2. Reboot and make sure everything works as expected 3. Do a second installation and install Ubuntu with ZFS on disk 2 4. Reboot * Expected Result * GRUB should display all the machines available and let the user select which installation to boot * Actual result * - Only one machine is listed - initramfs crashes because there are several pool with the same name but different IDs and import the pools by name - Same problem in the systemd generator which will try to import all the rpools. == Original Description == I had an Ubuntu old installation that used a ZFS root, using the layout described in the ZFS on Linux docs. Consequently, the pool name for my Ubuntu installation was "rpool". I'm currently encountering an issue with that pool that only allows me to mount it read-only. So, I'd like to replicate the datasets from there to a new device. On the new device, I've set up a ZFS system using the Ubuntu 20.04 daily installer (March 9, 2020). This setup creates a new pool named "rpool". So, with both devices inserted, I have two distinct pools each named "rpool", one of which will kernel panic if I try to mount it read-write. ZFS is fine with having multiple pools with the same name. In these cases, you use `zfs import` with the pool's GUID and give it a distinct pool name on import. However, the grub config for booting from ZFS doesn't appear to handle multiple pools with the same rpool name very well. Rather than using the pool's GUID, it uses the name, and as such, it's unable to boot properly when another pool with the name "rpool" is attached to the system. I think it'd be better if the config were written in such a way that `update-grub` generated boot config bound to whatever pool it found at the time of its invocation, and not start searching through all pools dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system with a ZFS root that boots just fine. But, the moment I attach the old pool, also named "rpool", I'm no longer able to boot up my system even though I haven't removed the good pool and I haven't re-run `update- grub`. Instead of booting, I'm thrown into the grub command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+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 1881859] Re: RaspberryPi and "openssl:Error: 'rehash' is an invalid command"
Hello Jeffrey, this is quite surprising; what's your PATH look like in the shell where you performed this update? I'm curious if you may have a locally-supplied openssl that is shadowing the system-provided openssl binary. Can you include the output from: apt policy openssl debsums -sa openssl Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1881859 Title: RaspberryPi and "openssl:Error: 'rehash' is an invalid command" Status in ca-certificates package in Ubuntu: New Bug description: Hi Everyone, I ran dist-upgrade today on my RPI-3. It resulted in: ``` Calculating upgrade... Done The following packages will be upgraded: armbian-bionic-desktop armbian-config armbian-firmware ca-certificates chromium-browser chromium-chromedriver chromium-codecs-ffmpeg-extra python3-software-properties software-properties-common 9 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ``` And: ``` ... Setting up chromium-codecs-ffmpeg-extra (83.0.4103.61-0ubuntu0.18.04.1) ... Setting up python3-software-properties (0.96.24.32.13) ... Setting up ca-certificates (20190110~18.04.1) ... Updating certificates in /etc/ssl/certs... openssl:Error: 'rehash' is an invalid command. Standard commands asn1parse caciphers cms crl crl2pkcs7 dgst dh dhparam dsa dsaparam ec ... 127 added, 8 removed; done. Setting up software-properties-common (0.96.24.32.13) ... Setting up chromium-browser (83.0.4103.61-0ubuntu0.18.04.1) ... ``` Operating System: ``` $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic ``` And finally: ``` $ apt-cache show ca-certificates Package: ca-certificates Architecture: all Version: 20190110~18.04.1 Multi-Arch: foreign Priority: important Section: misc Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Michael Shuler Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 382 Depends: openssl (>= 1.1.0), debconf (>= 0.5) | debconf-2.0 Breaks: ca-certificates-java (<< 20121112+nmu1) Enhances: openssl Filename: pool/main/c/ca-certificates/ca-certificates_20190110~18.04.1_all.deb Size: 145500 MD5sum: f0c73db6f5e857f13af04aaa736f87f0 SHA1: 8a3d4583491b426691a986ef11b1c805c2d4cf54 SHA256: fcfa84619207690491a3f9ab898de3fb2d46eeb7a73d525b91d05e7655815f5b Description: Common CA certificates Description-md5: e867d2a359bea1800b5bff209fc65bd1 Task: minimal Supported: 5y Package: ca-certificates Architecture: all Version: 20180409 Multi-Arch: foreign Priority: important Section: misc Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Michael Shuler Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 392 Depends: openssl (>= 1.1.0), debconf (>= 0.5) | debconf-2.0 Breaks: ca-certificates-java (<< 20121112+nmu1) Enhances: openssl Filename: pool/main/c/ca-certificates/ca-certificates_20180409_all.deb Size: 150932 MD5sum: eae40792673dcb994af86284d0a01f36 SHA1: 8ac5ac1506810b0483f0b80b0652071348459fc4 SHA256: 195ffe05ae7d060146f890b1db225f5e8c3a8c505ffbea1fba30a520a1cd58d8 Description: Common CA certificates Description-md5: e867d2a359bea1800b5bff209fc65bd1 Task: minimal Supported: 5y $ apt-cache show openssl Package: openssl Architecture: armhf Version: 1.1.1-1ubuntu2.1~18.04.6 Multi-Arch: foreign Priority: important Section: utils Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian OpenSSL Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 986 Depends: libc6 (>= 2.15), libssl1.1 (>= 1.1.1) Suggests: ca-certificates Filename: pool/main/o/openssl/openssl_1.1.1-1ubuntu2.1~18.04.6_armhf.deb Size: 589160 MD5sum: 37a31fce651134a5b057c9f6f356aaf2 SHA1: 476816221f03bae71ecd760e1e4e6d155f85e7c1 SHA256: 2787b66aba181e230f36ce49600b3a7d9dea7695aa332da0496a5e1a62281d39 Homepage: https://www.openssl.org/ Description: Secure Sockets Layer toolkit - cryptographic utility Description-md5: 9b6de2bb6e1d9016aeb0f00bcf6617bd Task: minimal Supported: 5y Package: openssl Architecture: armhf Version: 1.1.0g-2ubuntu4 Multi-Arch: foreign Priority: important Section: utils Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian OpenSSL Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 883 Depends: libc6 (>= 2.15), libssl1.1 (>= 1.1.0) Suggests: ca-certificates Filename: pool/main/o/openssl/openssl_1.1.0g-2ubuntu4_armhf.deb Size: 509616 MD5sum:
[Touch-packages] [Bug 1871154] Re: Error message displayed during boot (mountroot hook, premount)
Hello Laurent, or anyone else affected, Accepted initramfs-tools into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.136ubuntu6.1 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: initramfs-tools (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 lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in initramfs-tools package in Ubuntu: Fix Released Status in lvm2 package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: Fix Committed Status in lvm2 source package in Focal: Invalid Bug description: [Impact] * People using lvm2 on ubuntu focal are getting a strange and weird message due to a wrong path [Test Case] * Install lvm2 on Ubuntu 20.04 [Regression Potential] * Low, the fix is already part of groovy [Other info] Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871154/+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 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances
Hello Sorah, or anyone else affected, Accepted initramfs-tools into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.136ubuntu6.1 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: initramfs-tools (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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1880853 Title: libc6-lse lets update-initramfs fail on AWS m6g instances Status in cloud-images: New Status in btrfs-progs package in Ubuntu: Invalid Status in glibc package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Status in btrfs-progs source package in Focal: Invalid Status in glibc source package in Focal: Invalid Status in initramfs-tools source package in Focal: Fix Committed Bug description: [Impact] * update-initramfs -u fails on arm64 m6g instances in AWS [Test Case] * launch m6g instance in AWS * install libc6-lse (if not installed) * run $ update-initramfs -u * It should suceed [Regression Potential] * Adding one more path to libgcc_s1 resolution. This will still fail if something compiles libc6 for _two_ optimisations like /lib/$arch/foo/bar/libpthread. [Other Info] * libphtread dlopens libgcc_s1, thus whenever libpthread is needed in the initrd libgcc_s1 must be copied in too. However the logic to find matching libgcc_s1 is broken for optimizied builds of libc6 without optimized build of libgcc_s1. I think libpthread should link against libgcc_s1 to prevent these issues. * Original bug report With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse lets update-initramfs always fail with the following error: ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1. ## Steps to reproduce (on AWS) ### With focal 20200423 AMI 1. Find the following AMI and launch on m6g instance family ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423 2. Run: sudo apt update && sudo apt install libc6-lse 3. Try: sudo update-initramfs -u ### With focal 20200522 AMI 1. Find the following AMI and launch on m6g instance family ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522 2. Try: sudo update-initramfs -u ## Note - The entire log of the above steps performed on 20200423 AMI is attached. - Latest cloud-image AMI "ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse manually. - This doesn't reproduce on EC2 a1.* instance family. ## Expected behavior Does not fail. ## Background to find this bug As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get upgrade pulls newer package that triggers update-initramfs, apt-get upgrade always fail on 20200522 AMI. the following is an apport report on 20200423 AMI: ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: arm64 CasperMD5CheckResult: skip Date: Wed May 27 09:52:16 2020 Dependencies: gcc-10-base 10-20200411-0ubuntu1 libc6 2.31-0ubuntu9 libcrypt1 1:4.4.10-10ubuntu4 libgcc-s1 10-20200411-0ubuntu1 libidn2-0 2.2.0-2 libunistring2 0.9.10-2 DistroRelease: Ubuntu 20.04 Ec2AMI: ami-061102f51d47b1c24 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-northeast-1c Ec2InstanceType: m6g.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: libc6-lse 2.31-0ubuntu9 PackageArchitecture: arm64 ProcCpuinfoMinimal: processor
[Touch-packages] [Bug 1881972] Re: systemd-networkd crashes with invalid pointer
The system I pulled the networkd log from had not yet become unreachable
but here's a snippet from one that did:
May 27 07:38:18 ip-10-0-4-228 systemd[1]: systemd-networkd.service: Failed with
result 'core-dump'.
May 27 07:38:18 ip-10-0-4-228 systemd[1]: Failed to start Network Service.
May 27 07:38:18 ip-10-0-4-228 systemd[1]: Dependency failed for Wait for
Network to be Configured.
May 27 07:38:18 ip-10-0-4-228 systemd[1]: systemd-networkd-wait-online.service:
Job systemd-networkd-wait-online.service/start failed with result 'dependency'
May 27 07:38:18 ip-10-0-4-228 systemd[1]: systemd-networkd.socket: Failed with
result 'service-start-limit-hit'.
--
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/1881972
Title:
systemd-networkd crashes with invalid pointer
Status in systemd package in Ubuntu:
New
Bug description:
This is a serious regression with systemd-networkd that I ran in to
while setting up a NAT router in AWS. The AWS AMI ubuntu/images/hvm-
ssd/ubuntu-bionic-18.04-amd64-server-20200131 with
systemd-237-3ubuntu10.33 does NOT have the problem, but the next most
recent AWS AMI ubuntu/images/hvm-ssd/ubuntu-
bionic-18.04-amd64-server-20200311 with systemd-including
237-3ubuntu10.39 does.
Also, a system booted from the (good) 20200131 AMI starts showing the
problem after updating only systemd (to 237-3ubuntu10.41) and its
direct dependencies (e.g. 'apt-get install systemd'). So I'm fairly
confident that a change to the systemd package between
237-3ubuntu10.33 and 237-3ubuntu10.39 introduced the problem and it is
still present.
On the NAT router I use three interfaces and have separate routing
tables for admin and forwarded traffic. Things come up fine initially
but every 30-60 minutes (DHCP lease renewal time?) one or more
interfaces is reconfigured and most of the time systemd-networkd will
crash and need to be restarted. Eventually the system becomes
unreachable when the default crash loop backoff logic prevents the
network service from being restarted at all. The log excerpt attached
illustrates the crash loop.
Also including the netplan and networkd config files below.
# grep . /etc/netplan/*
/etc/netplan/50-cloud-init.yaml:# This file is generated from information
provided by the datasource. Changes
/etc/netplan/50-cloud-init.yaml:# to it will not persist across an instance
reboot. To disable cloud-init's
/etc/netplan/50-cloud-init.yaml:# network configuration capabilities, write a
file
/etc/netplan/50-cloud-init.yaml:#
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
/etc/netplan/50-cloud-init.yaml:# network: {config: disabled}
/etc/netplan/50-cloud-init.yaml:network:
/etc/netplan/50-cloud-init.yaml:version: 2
/etc/netplan/50-cloud-init.yaml:ethernets:
/etc/netplan/50-cloud-init.yaml:ens5:
/etc/netplan/50-cloud-init.yaml:dhcp4: true
/etc/netplan/50-cloud-init.yaml:match:
/etc/netplan/50-cloud-init.yaml:macaddress: xx:xx:xx:xx:xx:xx
/etc/netplan/50-cloud-init.yaml:set-name: ens5
/etc/netplan/99_config.yaml:network:
/etc/netplan/99_config.yaml: version: 2
/etc/netplan/99_config.yaml: renderer: networkd
/etc/netplan/99_config.yaml: ethernets:
/etc/netplan/99_config.yaml:ens6:
/etc/netplan/99_config.yaml: match:
/etc/netplan/99_config.yaml:macaddress: yy:yy:yy:yy:yy:yy
/etc/netplan/99_config.yaml: dhcp4: true
/etc/netplan/99_config.yaml: dhcp4-overrides:
/etc/netplan/99_config.yaml:use-routes: false
/etc/netplan/99_config.yaml:ens7:
/etc/netplan/99_config.yaml: match:
/etc/netplan/99_config.yaml:macaddress: zz:zz:zz:zz:zz:zz
/etc/netplan/99_config.yaml: mtu: 1500
/etc/netplan/99_config.yaml: dhcp4: true
/etc/netplan/99_config.yaml: dhcp4-overrides:
/etc/netplan/99_config.yaml:use-mtu: false
/etc/netplan/99_config.yaml:use-routes: false
# grep . /etc/networkd-dispatcher/*/*
/etc/networkd-dispatcher/configured.d/nat:#!/bin/bash
/etc/networkd-dispatcher/configured.d/nat:# Do additional configuration for
the inside and outside interfaces
/etc/networkd-dispatcher/configured.d/nat:# route table used for
forwarded/routed/natted traffic
/etc/networkd-dispatcher/configured.d/nat:FWD_TABLE=99
/etc/networkd-dispatcher/configured.d/nat:if [ "${IFACE}" = "ens6" ]; then
/etc/networkd-dispatcher/configured.d/nat: # delete link-local route for
inside in default table
/etc/networkd-dispatcher/configured.d/nat: /sbin/ip route delete 10.0.3.0/24
2>/dev/null || true
/etc/networkd-dispatcher/configured.d/nat: # add link-local route for inside
in table 99
/etc/networkd-dispatcher/configured.d/nat: /sbin/ip route replace
10.0.3.0/24 dev ens6 scope link src 10.0.3.171
[Touch-packages] [Bug 1881972] Re: systemd-networkd crashes with invalid pointer
Also of note is that on systems with systemd-237-3ubuntu10.33 or older I
don't see the "ens5: Configured" log messages at all after initial
configuration, even though I'm sure DHCP renewals are happening.
--
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/1881972
Title:
systemd-networkd crashes with invalid pointer
Status in systemd package in Ubuntu:
New
Bug description:
This is a serious regression with systemd-networkd that I ran in to
while setting up a NAT router in AWS. The AWS AMI ubuntu/images/hvm-
ssd/ubuntu-bionic-18.04-amd64-server-20200131 with
systemd-237-3ubuntu10.33 does NOT have the problem, but the next most
recent AWS AMI ubuntu/images/hvm-ssd/ubuntu-
bionic-18.04-amd64-server-20200311 with systemd-including
237-3ubuntu10.39 does.
Also, a system booted from the (good) 20200131 AMI starts showing the
problem after updating only systemd (to 237-3ubuntu10.41) and its
direct dependencies (e.g. 'apt-get install systemd'). So I'm fairly
confident that a change to the systemd package between
237-3ubuntu10.33 and 237-3ubuntu10.39 introduced the problem and it is
still present.
On the NAT router I use three interfaces and have separate routing
tables for admin and forwarded traffic. Things come up fine initially
but every 30-60 minutes (DHCP lease renewal time?) one or more
interfaces is reconfigured and most of the time systemd-networkd will
crash and need to be restarted. Eventually the system becomes
unreachable when the default crash loop backoff logic prevents the
network service from being restarted at all. The log excerpt attached
illustrates the crash loop.
Also including the netplan and networkd config files below.
# grep . /etc/netplan/*
/etc/netplan/50-cloud-init.yaml:# This file is generated from information
provided by the datasource. Changes
/etc/netplan/50-cloud-init.yaml:# to it will not persist across an instance
reboot. To disable cloud-init's
/etc/netplan/50-cloud-init.yaml:# network configuration capabilities, write a
file
/etc/netplan/50-cloud-init.yaml:#
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
/etc/netplan/50-cloud-init.yaml:# network: {config: disabled}
/etc/netplan/50-cloud-init.yaml:network:
/etc/netplan/50-cloud-init.yaml:version: 2
/etc/netplan/50-cloud-init.yaml:ethernets:
/etc/netplan/50-cloud-init.yaml:ens5:
/etc/netplan/50-cloud-init.yaml:dhcp4: true
/etc/netplan/50-cloud-init.yaml:match:
/etc/netplan/50-cloud-init.yaml:macaddress: xx:xx:xx:xx:xx:xx
/etc/netplan/50-cloud-init.yaml:set-name: ens5
/etc/netplan/99_config.yaml:network:
/etc/netplan/99_config.yaml: version: 2
/etc/netplan/99_config.yaml: renderer: networkd
/etc/netplan/99_config.yaml: ethernets:
/etc/netplan/99_config.yaml:ens6:
/etc/netplan/99_config.yaml: match:
/etc/netplan/99_config.yaml:macaddress: yy:yy:yy:yy:yy:yy
/etc/netplan/99_config.yaml: dhcp4: true
/etc/netplan/99_config.yaml: dhcp4-overrides:
/etc/netplan/99_config.yaml:use-routes: false
/etc/netplan/99_config.yaml:ens7:
/etc/netplan/99_config.yaml: match:
/etc/netplan/99_config.yaml:macaddress: zz:zz:zz:zz:zz:zz
/etc/netplan/99_config.yaml: mtu: 1500
/etc/netplan/99_config.yaml: dhcp4: true
/etc/netplan/99_config.yaml: dhcp4-overrides:
/etc/netplan/99_config.yaml:use-mtu: false
/etc/netplan/99_config.yaml:use-routes: false
# grep . /etc/networkd-dispatcher/*/*
/etc/networkd-dispatcher/configured.d/nat:#!/bin/bash
/etc/networkd-dispatcher/configured.d/nat:# Do additional configuration for
the inside and outside interfaces
/etc/networkd-dispatcher/configured.d/nat:# route table used for
forwarded/routed/natted traffic
/etc/networkd-dispatcher/configured.d/nat:FWD_TABLE=99
/etc/networkd-dispatcher/configured.d/nat:if [ "${IFACE}" = "ens6" ]; then
/etc/networkd-dispatcher/configured.d/nat: # delete link-local route for
inside in default table
/etc/networkd-dispatcher/configured.d/nat: /sbin/ip route delete 10.0.3.0/24
2>/dev/null || true
/etc/networkd-dispatcher/configured.d/nat: # add link-local route for inside
in table 99
/etc/networkd-dispatcher/configured.d/nat: /sbin/ip route replace
10.0.3.0/24 dev ens6 scope link src 10.0.3.171 table ${FWD_TABLE}
/etc/networkd-dispatcher/configured.d/nat: # add routes to VPC cidrs via
inside gateway in table 99
/etc/networkd-dispatcher/configured.d/nat: /sbin/ip route replace
10.0.0.0/16 via 10.0.3.1 table ${FWD_TABLE}
/etc/networkd-dispatcher/configured.d/nat: # add rules to use table 99
/etc/networkd-dispatcher/configured.d/nat: /sbin/ip rule add iif ens6
lookup ${FWD_TABLE}
/etc/networkd-dispatcher/configured.d/nat: /sbin/ip
[Touch-packages] [Bug 1881972] [NEW] systemd-networkd crashes with invalid pointer
Public bug reported:
This is a serious regression with systemd-networkd that I ran in to
while setting up a NAT router in AWS. The AWS AMI ubuntu/images/hvm-ssd
/ubuntu-bionic-18.04-amd64-server-20200131 with systemd-237-3ubuntu10.33
does NOT have the problem, but the next most recent AWS AMI
ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20200311 with
systemd-including 237-3ubuntu10.39 does.
Also, a system booted from the (good) 20200131 AMI starts showing the
problem after updating only systemd (to 237-3ubuntu10.41) and its direct
dependencies (e.g. 'apt-get install systemd'). So I'm fairly confident
that a change to the systemd package between 237-3ubuntu10.33 and
237-3ubuntu10.39 introduced the problem and it is still present.
On the NAT router I use three interfaces and have separate routing
tables for admin and forwarded traffic. Things come up fine initially
but every 30-60 minutes (DHCP lease renewal time?) one or more
interfaces is reconfigured and most of the time systemd-networkd will
crash and need to be restarted. Eventually the system becomes
unreachable when the default crash loop backoff logic prevents the
network service from being restarted at all. The log excerpt attached
illustrates the crash loop.
Also including the netplan and networkd config files below.
# grep . /etc/netplan/*
/etc/netplan/50-cloud-init.yaml:# This file is generated from information
provided by the datasource. Changes
/etc/netplan/50-cloud-init.yaml:# to it will not persist across an instance
reboot. To disable cloud-init's
/etc/netplan/50-cloud-init.yaml:# network configuration capabilities, write a
file
/etc/netplan/50-cloud-init.yaml:#
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
/etc/netplan/50-cloud-init.yaml:# network: {config: disabled}
/etc/netplan/50-cloud-init.yaml:network:
/etc/netplan/50-cloud-init.yaml:version: 2
/etc/netplan/50-cloud-init.yaml:ethernets:
/etc/netplan/50-cloud-init.yaml:ens5:
/etc/netplan/50-cloud-init.yaml:dhcp4: true
/etc/netplan/50-cloud-init.yaml:match:
/etc/netplan/50-cloud-init.yaml:macaddress: xx:xx:xx:xx:xx:xx
/etc/netplan/50-cloud-init.yaml:set-name: ens5
/etc/netplan/99_config.yaml:network:
/etc/netplan/99_config.yaml: version: 2
/etc/netplan/99_config.yaml: renderer: networkd
/etc/netplan/99_config.yaml: ethernets:
/etc/netplan/99_config.yaml:ens6:
/etc/netplan/99_config.yaml: match:
/etc/netplan/99_config.yaml:macaddress: yy:yy:yy:yy:yy:yy
/etc/netplan/99_config.yaml: dhcp4: true
/etc/netplan/99_config.yaml: dhcp4-overrides:
/etc/netplan/99_config.yaml:use-routes: false
/etc/netplan/99_config.yaml:ens7:
/etc/netplan/99_config.yaml: match:
/etc/netplan/99_config.yaml:macaddress: zz:zz:zz:zz:zz:zz
/etc/netplan/99_config.yaml: mtu: 1500
/etc/netplan/99_config.yaml: dhcp4: true
/etc/netplan/99_config.yaml: dhcp4-overrides:
/etc/netplan/99_config.yaml:use-mtu: false
/etc/netplan/99_config.yaml:use-routes: false
# grep . /etc/networkd-dispatcher/*/*
/etc/networkd-dispatcher/configured.d/nat:#!/bin/bash
/etc/networkd-dispatcher/configured.d/nat:# Do additional configuration for the
inside and outside interfaces
/etc/networkd-dispatcher/configured.d/nat:# route table used for
forwarded/routed/natted traffic
/etc/networkd-dispatcher/configured.d/nat:FWD_TABLE=99
/etc/networkd-dispatcher/configured.d/nat:if [ "${IFACE}" = "ens6" ]; then
/etc/networkd-dispatcher/configured.d/nat: # delete link-local route for
inside in default table
/etc/networkd-dispatcher/configured.d/nat: /sbin/ip route delete 10.0.3.0/24
2>/dev/null || true
/etc/networkd-dispatcher/configured.d/nat: # add link-local route for inside
in table 99
/etc/networkd-dispatcher/configured.d/nat: /sbin/ip route replace 10.0.3.0/24
dev ens6 scope link src 10.0.3.171 table ${FWD_TABLE}
/etc/networkd-dispatcher/configured.d/nat: # add routes to VPC cidrs via
inside gateway in table 99
/etc/networkd-dispatcher/configured.d/nat: /sbin/ip route replace 10.0.0.0/16
via 10.0.3.1 table ${FWD_TABLE}
/etc/networkd-dispatcher/configured.d/nat: # add rules to use table 99
/etc/networkd-dispatcher/configured.d/nat: /sbin/ip rule add iif ens6 lookup
${FWD_TABLE}
/etc/networkd-dispatcher/configured.d/nat: /sbin/ip rule add oif ens6 lookup
${FWD_TABLE}
/etc/networkd-dispatcher/configured.d/nat: /sbin/ip rule add from
10.0.3.171/32 lookup ${FWD_TABLE}
/etc/networkd-dispatcher/configured.d/nat:elif [ "${IFACE}" = "ens7" ]; then
/etc/networkd-dispatcher/configured.d/nat: # delete link-local route for
outside in default table
/etc/networkd-dispatcher/configured.d/nat: /sbin/ip route delete 10.0.2.0/24
2>/dev/null || true
/etc/networkd-dispatcher/configured.d/nat: # add link-local route for outside
in table 99
/etc/networkd-dispatcher/configured.d/nat: /sbin/ip route replace 10.0.2.0/24
dev ens7 scope link src
[Touch-packages] [Bug 1881941] Re: Ubuntu dock behaves crazy when hidden
** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock (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/1881941 Title: Ubuntu dock behaves crazy when hidden Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: I had put the dock on the bottom of the screen and also set to hide automatically. The dock works fine as expected but there are sometimes (actually like 90% of the time) that it behaves weird when I try to access it with the mouse pointer, the dock starts to bounce quickly without stopping and then it's kind of hard to press the icons on it (when I'm lucky I can click the icon), other times I had to move away the pointer from the bottom and then move it back to access the dock. I made a video of it although it's very short but you can see for a brief of time how the dock starts to bounce. I haven't installed new packages or applications that change the behaviour of the dock in any way. tavoge@e6430s:~$ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 tavoge@e6430s:~$ apt-cache policy xorg xorg: Instalados: 1:7.7+19ubuntu14 Candidato: 1:7.7+19ubuntu14 Tabla de versión: *** 1:7.7+19ubuntu14 500 500 http://mx.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 11:40:48 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:057d] InstallationDate: Installed on 2020-05-29 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Latitude E6430s ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0XHTPW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd11/30/2018:svnDellInc.:pnLatitudeE6430s:pvr01:rvnDellInc.:rn0XHTPW:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6430s dmi.product.sku: Latitude E6430s dmi.product.version: 01 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.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/gnome-shell-extension-ubuntu-dock/+bug/1881941/+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 1881950] Re: Wireless mouse does not work
** Package changed: xorg (Ubuntu) => linux (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/1881950 Title: Wireless mouse does not work Status in linux package in Ubuntu: Confirmed Bug description: Wireless mouse does not work, it is not detected ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 20:38:12 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:236a] Subsystem: ASUSTeK Computer Inc. GeForce 820M [1043:236a] InstallationDate: Installed on 2019-08-25 (282 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: ASUSTeK COMPUTER INC. X555LDB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=68cdded4-86f5-4f37-b6be-86a1a345547a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LDB.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LDB 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.:bvrX555LDB.303:bd12/19/2014:svnASUSTeKCOMPUTERINC.:pnX555LDB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LDB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LDB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881950/+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 1880864] Re: networkmanager IKE VPN connection causes DNS leak
Thank you for your bug report, could you perhaps report it upstream on https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/ ? -- 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/1880864 Title: networkmanager IKE VPN connection causes DNS leak Status in network-manager package in Ubuntu: New Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 network-manager: Installé : 1.22.10-1ubuntu1 Candidat : 1.22.10-1ubuntu1 Table de version : *** 1.22.10-1ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Connecting to a IPSEC IKE VPN does not update correctly update systemd-resolve dns parameters: DNS provided by the VPN tunnel is seen by systemd-resolve but not use to resolve dns queries resulting to a DNS leak. I tried to play with network manager priority which as no effect: default setting seems to be fine as the dns provided by the vpn appears on top of dns list provided by "systemd-resolve --status" result bellow. I found out a way to get it working by restarting systemd-resolve service after the vpn connection is established. I think (pure speculation, I don't know how systemd-resolve works) systemd-resolve evaluate which dns use, the one provided by the vpn is the first one then it decide to use it. This evaluation should be triggered when tunnel is bringed up. Bringing up an IPSEC IKE VPN does not create a new interface, it will use the same used by the default network interface where is configured the gateway. I think a fix would be to find out a way to triggered the dns election of systemd-resolve to update the "Current DNS Server". Maybe it is a bug with systemd-resolve but as I don't know how everything work together, I choose to report this here. You will find my network manager config for this particular ipsec tunnel bellow. Before systemctl restart systemd-resolved.service Global LLMNR setting: no MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no 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 (eno1) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Current DNS Server: 192.168.10.1 DNS Servers: 192.168.1.1 #DNS from VPN 192.168.10.1 #DNS from DHCP DNS Domain: lan ~. after systemctl restart systemd-resolved.service Global LLMNR setting: no MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no 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
[Touch-packages] [Bug 1880614] Re: Network Manager and the Menu Bar display a question mark, as though it wasn't able to connect to the internet, but Ubuntu can access the internet just fine; this was
Thank you for your bug report. What's the output of $ nmcli device when you get the issue? ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1880614 Title: Network Manager and the Menu Bar display a question mark, as though it wasn't able to connect to the internet, but Ubuntu can access the internet just fine; this was a false flag Status in network-manager package in Ubuntu: Incomplete Bug description: A false flag of reporting a network without wifi access. This happens when leaving the computer idle for 20 minutes or more. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 25 19:01:36 2020 InstallationDate: Installed on 2020-05-07 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 20600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880614/+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 1880575] Re: Cuenta Online en Google
Thank you for taking the time to report this issue and helping to make Ubuntu better. We noticed that some of the sentences in this bug report are not in English. If they were translated to English they would be more understandable to triagers. Could you please translate them? ** Changed in: gnome-online-accounts (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1880575 Title: Cuenta Online en Google Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: Hasta la versión 18.04.4 LTS podía conectar la cuenta online de la universidad (@uoc.edu) sin problemas y sincronizar calendarios y contactos con evolution, es una cuenta que se accede a ella via google. Cuando lo intento con esta versión de ubuntu 20.04 LTS me da un error justo después de ingresar la cuenta de correo. "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough). Y no puedo continuar con el registro de la cuenta. Puedo hacer algo yo a nivel local para solucionar este problema? Me resulta muy útil poder sincronizar los calendarios de actividades con la universidad y los contactos con mi tutor y los profesores de cada asignatura. Muchas gracias de antemano. Un saludo, quedo a la espera de alguna solución. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1880575/+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 1879625] Re: [Precision 5530, Realtek ALC3266] No sound after reboot until headphones are unplugged and plugged back in
Sorry, I just saw the question from Hui and it seemed to need confirmation if it was the same issue, since it's not I'm setting it back to New ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => New -- 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/1879625 Title: [Precision 5530, Realtek ALC3266] No sound after reboot until headphones are unplugged and plugged back in Status in alsa-driver package in Ubuntu: New Bug description: Looks like a frequent problem that hits my system : I have no sound on my headphones after I reboot my laptop until I unplug and plug back in the headphones. I *may* have sound through the PC speaker. I used to have none, but today sound came out of it. As I have upgraded to 20.04 and have done some modifications in config files some time ago with 19.xx, I'm unsure this is reliable information. I've tried to apply some solutions found here or there, without success. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stan 2001 F pulseaudio /dev/snd/pcmC0D0p: stan 2001 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 20 08:08:37 2020 InstallationDate: Installed on 2019-04-26 (389 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1570 F pulseaudio stan 2001 F pulseaudio /dev/snd/pcmC0D0p: stan 2001 F...m pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Precision 5530, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: Upgraded to focal on 2020-05-07 (12 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0N0DK2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0N0DK2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-10T16:49:20.600250 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879625/+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 1874247] Re: Don't work wired connection regression focal
Thanks, closing if it works now ** Changed in: network-manager (Ubuntu) Status: Incomplete => Invalid -- 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/1874247 Title: Don't work wired connection regression focal Status in network-manager package in Ubuntu: Invalid Bug description: After upgrade to focal I can't connect to wired network. It was ok in 19.10 before ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 15:44:52 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.254 dev wlp7s0 proto dhcp metric 600 169.254.0.0/16 dev wlp7s0 scope link metric 1000 192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.67 metric 600 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1874247/+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 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content
An alternative fix for report.py would be if there are no UserGroups DO NOT add the UserGroups field at all. Adding it with an empty string or whitespace is the problem. If it's not present at all apport-unpack will not throw the error. -- 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/1427600 Title: apport-unpack: ValueError: ['UserGroups'] has no binary content Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Triaged Status in apport source package in Focal: In Progress Status in apport source package in Groovy: Fix Released Bug description: [Impact] apport-unpack crashes when trying to unpack a crash [Test Case] On a system running 20.04 LTS: 1) create an additional user who is only a member of their own group e.g. bdmurray@clean-focal-amd64:~$ id crashy uid=1001(crashy) gid=1001(crashy) groups=1001(crashy) 2) Launch a process as that user 3) kill -11 that process 4) Confirm there is a crash file in /var/crash for that process 5) Run apport-unpack on that .crash file With the version of apport from -proposed you will not get another crash file when unpacking the crash file. [Regression Potential] We are just setting UserGroups to ' ' as opposed to having it be completely empty so there isn't any chance for regression. When running apport-unpack to get at a core dump laney@raleigh> sudo apport-unpack _usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz [sudo] password for laney: Traceback (most recent call last): File "/usr/bin/apport-unpack", line 73, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in extract_keys [item for item, element in b64_block.items() if element is False]) ValueError: ['UserGroups'] has no binary content laney@raleigh> apport-cli --version 2.16.2 It's not terrible, because most files are unpacked (those which sort before UserGroups, I guess). ProblemType: BugDistroRelease: Ubuntu 15.04 Package: apport 2.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportLog: ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 10:09:26 2015 InstallationDate: Installed on 2012-10-07 (876 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) PackageArchitecture: allSourcePackage: apport UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+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 1844426] Re: Impossible to set up Livepatch on Ubuntu MATE
Understood that gnome-control-centre isn't meant to be used outside GNOME. However, software-properties *is* meant to be used outside GNOME, so perhaps it should detect whether it's running in GNOME and not show a button for a GNOME-only bit of software in that situation? -- 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/1844426 Title: Impossible to set up Livepatch on Ubuntu MATE Status in Ubuntu MATE: Confirmed Status in software-properties package in Ubuntu: Confirmed Bug description: In Ubuntu MATEE 18.04, in the Software Properties window (available from Software Boutique > Preferences > Show Software Sources > Manage Repositories, among other places), there is a Livepatch tab. This tab says "To use Livepatch, you need to sign in" and provides a "Sign In..." button. This button launches an empty version of gnome-control-center with no icons in it. If one is technically adept, it is possible to do what (I think) that button is trying to do by launching g-c-c directly in a terminal and overriding the desktop, thus: env XDG_CURRENT_DESKTOP=GNOME gnome-control-center online-accounts This online accounts window permits attempting to add an Ubuntu One account. However, when one tries, a window pops up with a place to add one's Ubuntu One username and password, but the window has no Submit button; there is no way to actually initiate sign in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1844426/+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 1847543] Re: libatk1.0-dev multiarch conflict
** Changed in: atk1.0 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to atk1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1847543 Title: libatk1.0-dev multiarch conflict Status in atk1.0 package in Ubuntu: New Bug description: It is not possible to install libatk1.0-dev:i386 and libatk1.0-dev:amd64 together: # apt install libatk1.0-dev:i386 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: gir1.2-atk-1.0:i386 The following NEW packages will be installed: gir1.2-atk-1.0:i386 libatk1.0-dev:i386 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 109 kB of archives. After this operation, 1.370 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://de.archive.ubuntu.com/ubuntu disco/main i386 gir1.2-atk-1.0 i386 2.32.0-1 [18,0 kB] Get:2 http://de.archive.ubuntu.com/ubuntu disco/main i386 libatk1.0-dev i386 2.32.0-1 [91,3 kB] Fetched 109 kB in 0s (457 kB/s) Selecting previously unselected package gir1.2-atk-1.0:i386. (Reading database ... 295431 files and directories currently installed.) Preparing to unpack .../gir1.2-atk-1.0_2.32.0-1_i386.deb ... Unpacking gir1.2-atk-1.0:i386 (2.32.0-1) ... Selecting previously unselected package libatk1.0-dev:i386. Preparing to unpack .../libatk1.0-dev_2.32.0-1_i386.deb ... Unpacking libatk1.0-dev:i386 (2.32.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libatk1.0-dev_2.32.0-1_i386.deb (--unpack): trying to overwrite shared '/usr/share/gir-1.0/Atk-1.0.gir', which is different from other instances of package libatk1.0-dev:i386 Errors were encountered while processing: /var/cache/apt/archives/libatk1.0-dev_2.32.0-1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) I need this for cross compiling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atk1.0/+bug/1847543/+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 1864215] Re: Please add webp loader to gdk-pixbuf
** Changed in: gdk-pixbuf (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1864215 Title: Please add webp loader to gdk-pixbuf Status in gdk-pixbuf package in Ubuntu: New Bug description: Attempting to load a webp image -- for instance, https://images.theweek.com/sites/default/files/styles/tw_image_9_4/public/FKK78W.jpg.webp or https://cdn.vox-cdn.com/thumbor/2YtWB5zH7sPycyc0FYv3JSB6SFw=/60x0:1140x720/920x613/filters:focal(60x0:1140x720):format(webp)/cdn.vox-cdn.com/uploads/chorus_image/image/49663815/timburton.0.0.jpg -- in a gdk-pixbuf app results in a "Couldn’t recognize the image file format" error. Bug 1318327 covers this issue in eye of gnome, and bug 1407644 in libwebp, but isn't this really a gdk-pixbuf issue? If it really does belong to libwebp, my apologies, please dup this bug to 1407644 (I'm confident it doesn't belong to eog since I don't use that program; I have other programs that use libgdk-pixbuf). You can probably use eog to test this, or run /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders | grep -i webp (I assume the loader would mention webp if there was a loader for it). I have these packages installed in addition to libgdk-pixbuf2.0-0: libwebp-dev libwebp6 libwebpdemux2 libwebpmux3 webp. file recognizes the format: $ file /tmp/FKK78W.jpg.webp /tmp/FKK78W.jpg.webp: RIFF (little-endian) data, Web/P image, VP8 encoding, 1200x533, Scaling: [none]x[none], YUV color, decoders should clamp ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-1build1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 Date: Fri Feb 21 08:48:36 2020 InstallationDate: Installed on 2019-10-10 (133 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1864215/+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 1860267] Re: software-properties-gtk crashed with AttributeError in run(): 'SoftwarePropertiesGtk' object has no attribute 'on_keyboard_Interrupt'
** Changed in: software-properties (Ubuntu) Importance: Medium => Low -- 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/1860267 Title: software-properties-gtk crashed with AttributeError in run(): 'SoftwarePropertiesGtk' object has no attribute 'on_keyboard_Interrupt' Status in software-properties package in Ubuntu: New Bug description: Steps to reproduce: 1. Open terminal and execute `software-properties-gtk` 2. Wait it to open 3. Press + in the terminal to stop it. Expected result: * Software & Updates window closed quietly and clean Actual results: * Software & Updates window closed with errors in terminal focal@focal-VirtualBox:~$ software-properties-gtk ^CTraceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SimpleGtkbuilderApp.py", line 54, in run Gtk.Application.run(self, None) File "/usr/lib/python3/dist-packages/gi/overrides/Gio.py", line 44, in run return Gio.Application.run(self, *args, **kwargs) File "/usr/lib/python3.7/contextlib.py", line 119, in __exit__ next(self.gen) File "/usr/lib/python3/dist-packages/gi/_ossighelper.py", line 251, in register_sigint_fallback signal.default_int_handler(signal.SIGINT, None) KeyboardInterrupt During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 101, in app.run() File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SimpleGtkbuilderApp.py", line 56, in run self.on_keyboard_Interrupt() AttributeError: 'SoftwarePropertiesGtk' object has no attribute 'on_keyboard_Interrupt' focal@focal-VirtualBox:~$ and "Crash report" dialog afterwards. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CrashCounter: 1 CurrentDesktop: MATE Date: Sun Jan 19 13:10:46 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2020-01-16 (2 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200115) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 3.7.5-1ubuntu1 PythonArgs: ['/usr/bin/software-properties-gtk'] PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 SourcePackage: software-properties Title: software-properties-gtk crashed with AttributeError in run(): 'SoftwarePropertiesGtk' object has no attribute 'on_keyboard_Interrupt' 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/software-properties/+bug/1860267/+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 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content
Unfortunately the fix you added by inserting an empty space string ' '
for the UserGroups field does not resolve the bug at all. This is
because when reading the report in (problem_report.py) all fields which
are empty get ignored, and a field which is all whitespace counts as
empty. Prior to the fix the report already contained the UserGroups
field, it just didn't have an empty space after it. So nothing really
changed.
This is the new stacktrace when running apport-unpack with a crash
report generated with the fixed report.py
Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 77, in
pr.extract_keys(f, bin_keys, dir)
File "/usr/lib/python3/dist-packages/problem_report.py", line 269, in
extract_keys
raise ValueError('%s has no binary content' %
ValueError: ['UserGroups'] has no binary content
The UserGroups field can't be empty. For example if I add a group in the
UserGroups field, apport-unpack runs without errors. This is my current
fix to not deal with the constant stacktrace from apport-unpack.
sed -i -E 's/(UserGroups:)/\1 nogroup/' /var/crash/_crashfile
--
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/1427600
Title:
apport-unpack: ValueError: ['UserGroups'] has no binary content
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Xenial:
Triaged
Status in apport source package in Focal:
In Progress
Status in apport source package in Groovy:
Fix Released
Bug description:
[Impact]
apport-unpack crashes when trying to unpack a crash
[Test Case]
On a system running 20.04 LTS:
1) create an additional user who is only a member of their own group e.g.
bdmurray@clean-focal-amd64:~$ id crashy
uid=1001(crashy) gid=1001(crashy) groups=1001(crashy)
2) Launch a process as that user
3) kill -11 that process
4) Confirm there is a crash file in /var/crash for that process
5) Run apport-unpack on that .crash file
With the version of apport from -proposed you will not get another
crash file when unpacking the crash file.
[Regression Potential]
We are just setting UserGroups to ' ' as opposed to having it be completely
empty so there isn't any chance for regression.
When running apport-unpack to get at a core dump
laney@raleigh> sudo apport-unpack
_usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz
[sudo] password for laney:
Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 73, in
pr.extract_keys(f, bin_keys, dir)
File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in
extract_keys
[item for item, element in b64_block.items() if element is False])
ValueError: ['UserGroups'] has no binary content
laney@raleigh> apport-cli --version
2.16.2
It's not terrible, because most files are unpacked (those which sort
before UserGroups, I guess).
ProblemType: BugDistroRelease: Ubuntu 15.04
Package: apport 2.16.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
ApportLog:
ApportVersion: 2.16.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar 3 10:09:26 2015
InstallationDate: Installed on 2012-10-07 (876 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
PackageArchitecture: allSourcePackage: apport
UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+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 1826617] Re: package libtiffxx5 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/usr/share/doc/libtiffxx5/changelog.Debian.gz', 它与软件包 libtiffxx5:amd64 中的其他实例不同
** Changed in: tiff (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1826617 Title: package libtiffxx5 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/usr/share/doc/libtiffxx5/changelog.Debian.gz', 它与软件包 libtiffxx5:amd64 中的其他实例不同 Status in tiff package in Ubuntu: New Bug description: Synaptic cannot install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libtiffxx5 (not installed) ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Apr 27 08:27:27 2019 ErrorMessage: 尝试覆盖共享的 '/usr/share/doc/libtiffxx5/changelog.Debian.gz', 它与软件包 libtiffxx5:amd64 中的其他实例不同 InstallationDate: Installed on 2019-04-26 (0 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: tiff Title: package libtiffxx5 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/usr/share/doc/libtiffxx5/changelog.Debian.gz', 它与软件包 libtiffxx5:amd64 中的其他实例不同 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1826617/+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 1844426] Re: Impossible to set up Livepatch on Ubuntu MATE
The issue is that gnome-control-center isn't meant to be used outside of GNOME ** Changed in: software-properties (Ubuntu) Importance: Undecided => Low -- 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/1844426 Title: Impossible to set up Livepatch on Ubuntu MATE Status in Ubuntu MATE: Confirmed Status in software-properties package in Ubuntu: Confirmed Bug description: In Ubuntu MATEE 18.04, in the Software Properties window (available from Software Boutique > Preferences > Show Software Sources > Manage Repositories, among other places), there is a Livepatch tab. This tab says "To use Livepatch, you need to sign in" and provides a "Sign In..." button. This button launches an empty version of gnome-control-center with no icons in it. If one is technically adept, it is possible to do what (I think) that button is trying to do by launching g-c-c directly in a terminal and overriding the desktop, thus: env XDG_CURRENT_DESKTOP=GNOME gnome-control-center online-accounts This online accounts window permits attempting to add an Ubuntu One account. However, when one tries, a window pops up with a place to add one's Ubuntu One username and password, but the window has no Submit button; there is no way to actually initiate sign in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1844426/+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 1707341] Re: nm-dispatcher caused kernel crash.
thank you for your bug report, if the kernel crash it's a bug there, it should be robust to anything userpace is doing, reassigning ** Package changed: network-manager (Ubuntu) => linux (Ubuntu) -- 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/1707341 Title: nm-dispatcher caused kernel crash. Status in linux package in Ubuntu: Confirmed Bug description: After "waking" (shaking my mouse) to revive the display server my machine was usable for about 1 minute after the wake. Then all of the sudden all of my USB devices lost power completely, my hard drives stopped spinning and the system was at a stand still. Reading into the log files I find that the last thing the system did before it died. It was in the process of a "dhcp4 change". I would also like to mention I was running 3 VNC server sessions at the same time, but none of the viewers were active. I also confirmed that the power supply is defiantly not the reason its a 1000 watt platinum PSU that is under a year old and the system was usable again after a reboot. I am using Kernel version 4.11.7 built from the mainline with the Ubuntu configuration. There were no custom modules loaded (nothing outside of the 16.04.2 repo) here is the log /var/log/syslog Jul 28 22:27:43 Nova-Omega dhclient[3065]: DHCPACK of 10.10.20.115 from 10.10.20.1 Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5871] address 10.10.20.115 Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5871] plen 24 (255.255.255.0) Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5871] gateway 10.10.20.1 Jul 28 22:27:43 Nova-Omega dhclient[3065]: bound to 10.10.20.115 -- renewal in 243 seconds. Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5871] server identifier 10.10.20.1 Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5872] lease time 600 Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5872] nameserver '8.8.8.8' Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5872] nameserver '8.8.4.4' Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5872] dhcp4 (enp35s0): state changed bound -> bound Jul 28 22:27:43 Nova-Omega dbus[1039]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Jul 28 22:27:43 Nova-Omega systemd[1]: Starting Network Manager Script Dispatcher Service... Jul 28 22:27:43 Nova-Omega dbus[1039]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jul 28 22:27:43 Nova-Omega systemd[1]: Started Network Manager Script Dispatcher Service. Jul 28 22:27:43 Nova-Omega nm-dispatcher: req:1 'dhcp4-change' [enp35s0]: new request (2 scripts) Jul 28 22:27:43 Nova-Omega nm-dispatcher: req:1 'dhcp4-change' [enp35s0]: start running ordered scripts... Jul 28 22:31:46 Nova-Omega dhclient[3065]: DHCPREQUEST of 10.10.20.115 on enp35s0 to 10.10.20.1 port 67 (xid=0x2d7aba42) Jul 28 22:31:46 Nova-Omega dhclient[3065]: DHCPACK of 10.10.20.115 from 10.10.20.1 Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1854] address 10.10.20.115 Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1854] plen 24 (255.255.255.0) Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1855] gateway 10.10.20.1 Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1855] server identifier 10.10.20.1 Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1855] lease time 600 Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1855] nameserver '8.8.8.8' Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1855] nameserver '8.8.4.4' Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1856] dhcp4 (enp35s0): state changed bound -> bound Jul 28 22:31:46 Nova-Omega dbus[1039]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Jul 28 22:31:46 Nova-Omega systemd[1]: Starting Network Manager Script Dispatcher Service... Jul 28 22:31:46 Nova-Omega dhclient[3065]: bound to 10.10.20.115 -- renewal in 298 seconds. Jul 28 22:31:46 Nova-Omega dbus[1039]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jul 28 22:31:46 Nova-Omega systemd[1]: Started Network Manager Script Dispatcher Service. Jul 28 22:31:46 Nova-Omega nm-dispatcher: req:1 'dhcp4-change' [enp35s0]: new request (2 scripts) Jul 28 22:31:46 Nova-Omega nm-dispatcher: req:1 'dhcp4-change' [enp35s0]: start running ordered scripts... Jul 28 22:33:16 Nova-Omega smartd[1021]: Device: /dev/sda [SAT], SMART Usage Attribute: 189 Airflow_Temperature_Cel changed from 27 to 26 Jul 28 22:33:16 Nova-Omega
[Touch-packages] [Bug 1669156] Re: Fails writing with Caps Lock
** Changed in: lightdm (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1669156 Title: Fails writing with Caps Lock Status in lightdm package in Ubuntu: Incomplete Bug description: On Ubuntu 16.04: When clicking on the following 3 keyboard keys simultaneously: Left-CTRL + Left-ALT + F1 Then you get to a textual terminal (CLI) where you can type commands. But there is a problem when typing English letters with Caps Lock turned on: Instead of English capital letters - you see squares, so actually you can't login to your user that way if the username/password has Capital letters. The only method which allows you to write capital English letters is to simultaneously click Left-Shift + 'a letter'. That is the only method that works well. Note that the Caps Lock key works well with the graphical terminal (pseudo / pts) that appears on Ubuntu when hitting simultaneously: Left-CTRL + Left-ALT + T --- I assumed the bug report is relevant to "shadow" package because that the "/bin/login" binary comes from that package. Package version of 'shadow' is: 1:4.2-3.1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1669156/+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 1881964] [NEW] PCI/internal sound card not detected
Public bug reported: right after the system update, after i restarted my computer. there is no sound and on the sound setting only the dummy output is detected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-73.94-generic 4.4.59 Uname: Linux 4.4.0-73-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Jun 3 23:21:17 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2020-06-03 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.6 dmi.board.name: 0YDF7T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.6:bd10/25/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0YDF7T:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 5570 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1881964 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: right after the system update, after i restarted my computer. there is no sound and on the sound setting only the dummy output is detected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-73.94-generic 4.4.59 Uname: Linux 4.4.0-73-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Jun 3 23:21:17 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2020-06-03 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.6 dmi.board.name: 0YDF7T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.6:bd10/25/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0YDF7T:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 5570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1881964/+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 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content
** Description changed: + [Impact] + apport-unpack crashes when trying to unpack a crash + + [Test Case] + On a system running 20.04 LTS: + 1) create an additional user who is only a member of their own group e.g. + bdmurray@clean-focal-amd64:~$ id crashy + uid=1001(crashy) gid=1001(crashy) groups=1001(crashy) + 2) Launch a process as that user + 3) kill -11 that process + 4) Confirm there is a crash file in /var/crash for that process + 5) Run apport-unpack on that .crash file + + With the version of apport from -proposed you will not get another crash + file when unpacking the crash file. + + [Regression Potential] + We are just setting UserGroups to ' ' as opposed to having it be completely empty so there isn't any chance for regression. + When running apport-unpack to get at a core dump laney@raleigh> sudo apport-unpack _usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz - [sudo] password for laney: + [sudo] password for laney: Traceback (most recent call last): - File "/usr/bin/apport-unpack", line 73, in - pr.extract_keys(f, bin_keys, dir) - File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in extract_keys - [item for item, element in b64_block.items() if element is False]) + File "/usr/bin/apport-unpack", line 73, in + pr.extract_keys(f, bin_keys, dir) + File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in extract_keys + [item for item, element in b64_block.items() if element is False]) ValueError: ['UserGroups'] has no binary content laney@raleigh> apport-cli --version 2.16.2 It's not terrible, because most files are unpacked (those which sort before UserGroups, I guess). - ProblemType: Bug - DistroRelease: Ubuntu 15.04 + ProblemType: BugDistroRelease: Ubuntu 15.04 Package: apport 2.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportLog: - + ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 10:09:26 2015 InstallationDate: Installed on 2012-10-07 (876 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) - PackageArchitecture: all - SourcePackage: apport + PackageArchitecture: allSourcePackage: apport UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago) ** Also affects: apport (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: apport (Ubuntu Focal) Status: New => In Progress ** Changed in: apport (Ubuntu Focal) Assignee: (unassigned) => Brian Murray (brian-murray) -- 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/1427600 Title: apport-unpack: ValueError: ['UserGroups'] has no binary content Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Triaged Status in apport source package in Focal: In Progress Status in apport source package in Groovy: Fix Released Bug description: [Impact] apport-unpack crashes when trying to unpack a crash [Test Case] On a system running 20.04 LTS: 1) create an additional user who is only a member of their own group e.g. bdmurray@clean-focal-amd64:~$ id crashy uid=1001(crashy) gid=1001(crashy) groups=1001(crashy) 2) Launch a process as that user 3) kill -11 that process 4) Confirm there is a crash file in /var/crash for that process 5) Run apport-unpack on that .crash file With the version of apport from -proposed you will not get another crash file when unpacking the crash file. [Regression Potential] We are just setting UserGroups to ' ' as opposed to having it be completely empty so there isn't any chance for regression. When running apport-unpack to get at a core dump laney@raleigh> sudo apport-unpack _usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz [sudo] password for laney: Traceback (most recent call last): File "/usr/bin/apport-unpack", line 73, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in extract_keys [item for item, element in b64_block.items() if element is False]) ValueError: ['UserGroups'] has no binary content laney@raleigh> apport-cli --version 2.16.2 It's not terrible, because most files are unpacked (those which sort before UserGroups, I guess). ProblemType: BugDistroRelease: Ubuntu 15.04 Package: apport 2.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportLog: ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 10:09:26 2015 InstallationDate: Installed on 2012-10-07 (876 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) PackageArchitecture: allSourcePackage: apport
[Touch-packages] [Bug 1881278] Re: Ship 2018 Archive key in xenial's ubuntu-keyring
# apt install ubuntu-keyring Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: ubuntu-keyring 1 upgraded, 0 newly installed, 0 to remove and 90 not upgraded. Need to get 18.4 kB of archives. After this operation, 14.3 kB disk space will be freed. Get:1 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 ubuntu-keyring all 2012.05.19.1 [18.4 kB] Fetched 18.4 kB in 0s (194 kB/s) (Reading database ... 12323 files and directories currently installed.) Preparing to unpack .../ubuntu-keyring_2012.05.19.1_all.deb ... Unpacking ubuntu-keyring (2012.05.19.1) over (2012.05.19) ... Setting up ubuntu-keyring (2012.05.19.1) ... gpg: key 437D05B5: "Ubuntu Archive Automatic Signing Key " not changed gpg: key FBB75451: "Ubuntu CD Image Automatic Signing Key " not changed gpg: key C0B21F32: "Ubuntu Archive Automatic Signing Key (2012) " not changed gpg: key EFE21092: "Ubuntu CD Image Automatic Signing Key (2012) " not changed gpg: key 991BC93C: public key "Ubuntu Archive Automatic Signing Key (2018) " import ed gpg: Total number processed: 5 gpg: imported: 1 (RSA: 1) gpg: unchanged: 4 Correctly tested that there were 4 keys, 5 keys including the 2018 one after installing the upgraded, and that just the 3 keysnippets are present upon dist-upgrade to bionic. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1881278 Title: Ship 2018 Archive key in xenial's ubuntu-keyring Status in ubuntu-keyring package in Ubuntu: Invalid Status in ubuntu-keyring source package in Xenial: Fix Committed Bug description: [Impact] * Xenial systems will not be able to debootstrap Groovy archives when it finally switches to be signed by single 2018 key. To have support for xenial to operate against Groovy+ archives it needs access to 2018 archive key. Ship it. [Test Case] * Start xenial chroot or lxd container. * Observe that 4 keys are trusted - the original 2004 archive & cdimage, 2012 archive & cdimage # apt-key list --fingerprint /etc/apt/trusted.gpg pub 1024D/437D05B5 2004-09-12 Key fingerprint = 6302 39CC 130E 1A7F D81A 27B1 4097 6EAF 437D 05B5 uid Ubuntu Archive Automatic Signing Key sub 2048g/79164387 2004-09-12 pub 4096R/C0B21F32 2012-05-11 Key fingerprint = 790B C727 7767 219C 42C8 6F93 3B4F E6AC C0B2 1F32 uid Ubuntu Archive Automatic Signing Key (2012) pub 4096R/EFE21092 2012-05-11 Key fingerprint = 8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092 uid Ubuntu CD Image Automatic Signing Key (2012) pub 1024D/FBB75451 2004-12-30 Key fingerprint = C598 6B4F 1257 FFA8 6632 CBA7 4618 1433 FBB7 5451 uid Ubuntu CD Image Automatic Signing Key * Install the new ubuntu-keyring package * Observe that 5 keys are now trusted, including the 2018 archive key # apt-key list --fingerprint /etc/apt/trusted.gpg pub 1024D/437D05B5 2004-09-12 Key fingerprint = 6302 39CC 130E 1A7F D81A 27B1 4097 6EAF 437D 05B5 uid Ubuntu Archive Automatic Signing Key sub 2048g/79164387 2004-09-12 pub 4096R/C0B21F32 2012-05-11 Key fingerprint = 790B C727 7767 219C 42C8 6F93 3B4F E6AC C0B2 1F32 uid Ubuntu Archive Automatic Signing Key (2012) pub 4096R/EFE21092 2012-05-11 Key fingerprint = 8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092 uid Ubuntu CD Image Automatic Signing Key (2012) pub 1024D/FBB75451 2004-12-30 Key fingerprint = C598 6B4F 1257 FFA8 6632 CBA7 4618 1433 FBB7 5451 uid Ubuntu CD Image Automatic Signing Key pub 4096R/991BC93C 2018-09-17 Key fingerprint = F6EC B376 2474 EDA9 D21B 7022 8719 20D1 991B C93C uid Ubuntu Archive Automatic Signing Key (2018) * Dist upgrade to bionic * Observe that only 3 keys are trusted the 2012 cdimage + 2018 key, and that none of them are in /etc/apt/trusted.gpg but are key snippets in /etc/apt/trusted.gpg.d/ # apt-key list /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg -- pub rsa4096 2012-05-11 [SC] 790B C727 7767 219C 42C8 6F93 3B4F E6AC C0B2 1F32 uid [ unknown] Ubuntu Archive Automatic Signing Key (2012) /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg -- pub rsa4096 2012-05-11 [SC] 8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092 uid [
[Touch-packages] [Bug 1860394] Re: package lvm2 2.03.02-2ubuntu7 failed to install/upgrade: o subprocesso instalado, do pacote lvm2, o script post-installation retornou erro do status de saída 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lvm2 (Ubuntu) Status: New => Confirmed -- 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/1860394 Title: package lvm2 2.03.02-2ubuntu7 failed to install/upgrade: o subprocesso instalado, do pacote lvm2, o script post-installation retornou erro do status de saída 1 Status in lvm2 package in Ubuntu: Confirmed Bug description: ??? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.02-2ubuntu7 ProcVersionSignature: Ubuntu 5.4.0-11.14-generic 5.4.8 Uname: Linux 5.4.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Mon Jan 20 22:27:33 2020 ErrorMessage: o subprocesso instalado, do pacote lvm2, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2020-01-02 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200102) Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 3.7.5-1ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.7 SourcePackage: lvm2 Title: package lvm2 2.03.02-2ubuntu7 failed to install/upgrade: o subprocesso instalado, do pacote lvm2, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1860394/+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 1881278] Autopkgtest regression report (ubuntu-keyring/2012.05.19.1)
All autopkgtests for the newly accepted ubuntu-keyring (2012.05.19.1) for xenial have finished running. The following regressions have been reported in tests triggered by the package: apt/1.2.32ubuntu0.1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/xenial/update_excuses.html#ubuntu-keyring [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1881278 Title: Ship 2018 Archive key in xenial's ubuntu-keyring Status in ubuntu-keyring package in Ubuntu: Invalid Status in ubuntu-keyring source package in Xenial: Fix Committed Bug description: [Impact] * Xenial systems will not be able to debootstrap Groovy archives when it finally switches to be signed by single 2018 key. To have support for xenial to operate against Groovy+ archives it needs access to 2018 archive key. Ship it. [Test Case] * Start xenial chroot or lxd container. * Observe that 4 keys are trusted - the original 2004 archive & cdimage, 2012 archive & cdimage # apt-key list --fingerprint /etc/apt/trusted.gpg pub 1024D/437D05B5 2004-09-12 Key fingerprint = 6302 39CC 130E 1A7F D81A 27B1 4097 6EAF 437D 05B5 uid Ubuntu Archive Automatic Signing Key sub 2048g/79164387 2004-09-12 pub 4096R/C0B21F32 2012-05-11 Key fingerprint = 790B C727 7767 219C 42C8 6F93 3B4F E6AC C0B2 1F32 uid Ubuntu Archive Automatic Signing Key (2012) pub 4096R/EFE21092 2012-05-11 Key fingerprint = 8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092 uid Ubuntu CD Image Automatic Signing Key (2012) pub 1024D/FBB75451 2004-12-30 Key fingerprint = C598 6B4F 1257 FFA8 6632 CBA7 4618 1433 FBB7 5451 uid Ubuntu CD Image Automatic Signing Key * Install the new ubuntu-keyring package * Observe that 5 keys are now trusted, including the 2018 archive key # apt-key list --fingerprint /etc/apt/trusted.gpg pub 1024D/437D05B5 2004-09-12 Key fingerprint = 6302 39CC 130E 1A7F D81A 27B1 4097 6EAF 437D 05B5 uid Ubuntu Archive Automatic Signing Key sub 2048g/79164387 2004-09-12 pub 4096R/C0B21F32 2012-05-11 Key fingerprint = 790B C727 7767 219C 42C8 6F93 3B4F E6AC C0B2 1F32 uid Ubuntu Archive Automatic Signing Key (2012) pub 4096R/EFE21092 2012-05-11 Key fingerprint = 8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092 uid Ubuntu CD Image Automatic Signing Key (2012) pub 1024D/FBB75451 2004-12-30 Key fingerprint = C598 6B4F 1257 FFA8 6632 CBA7 4618 1433 FBB7 5451 uid Ubuntu CD Image Automatic Signing Key pub 4096R/991BC93C 2018-09-17 Key fingerprint = F6EC B376 2474 EDA9 D21B 7022 8719 20D1 991B C93C uid Ubuntu Archive Automatic Signing Key (2018) * Dist upgrade to bionic * Observe that only 3 keys are trusted the 2012 cdimage + 2018 key, and that none of them are in /etc/apt/trusted.gpg but are key snippets in /etc/apt/trusted.gpg.d/ # apt-key list /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg -- pub rsa4096 2012-05-11 [SC] 790B C727 7767 219C 42C8 6F93 3B4F E6AC C0B2 1F32 uid [ unknown] Ubuntu Archive Automatic Signing Key (2012) /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg -- pub rsa4096 2012-05-11 [SC] 8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092 uid [ unknown] Ubuntu CD Image Automatic Signing Key (2012) /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg -- pub rsa4096 2018-09-17 [SC] F6EC B376 2474 EDA9 D21B 7022 8719 20D1 991B C93C uid [ unknown] Ubuntu Archive Automatic Signing Key (2018) [Regression Potential] * Adding additional new trust key can trigger support request (aka why are you adding this key on xenial). The reason to add this key on xenial, is for xenial to allow securely debootstrap and operate on Groovy+ repositories which are about to drop 2012 key signatures. [Other Info] * Bionic switched from shipping keys in /etc/apt/trusted.gpg keyring, to individual snippets. Thus xenial's upload that adds the future key to /etc/apt/trusted.gpg should also remove it, during upgrade to bionic. To ensure that the systems upgraded from xenial to bionic,
[Touch-packages] [Bug 1881950] [NEW] Wireless mouse does not work
Public bug reported: Wireless mouse does not work, it is not detected ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 20:38:12 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:236a] Subsystem: ASUSTeK Computer Inc. GeForce 820M [1043:236a] InstallationDate: Installed on 2019-08-25 (282 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: ASUSTeK COMPUTER INC. X555LDB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=68cdded4-86f5-4f37-b6be-86a1a345547a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LDB.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LDB 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.:bvrX555LDB.303:bd12/19/2014:svnASUSTeKCOMPUTERINC.:pnX555LDB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LDB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LDB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1881950 Title: Wireless mouse does not work Status in xorg package in Ubuntu: New Bug description: Wireless mouse does not work, it is not detected ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 20:38:12 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:236a] Subsystem: ASUSTeK Computer Inc. GeForce 820M [1043:236a] InstallationDate: Installed on 2019-08-25 (282 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: ASUSTeK COMPUTER INC. X555LDB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=68cdded4-86f5-4f37-b6be-86a1a345547a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LDB.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LDB 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.:bvrX555LDB.303:bd12/19/2014:svnASUSTeKCOMPUTERINC.:pnX555LDB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LDB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LDB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
[Touch-packages] [Bug 1881947] [NEW] Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function main(). Aborting.
Public bug reported: Observed in an focal/arm64 autopkgtest failure of systemd 245.4-4ubuntu3.1: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20200603_071743_738b2@/log.gz [...] PASS: test-journal-enum == test-journal-flush === Root directory /var/log/journal removed. Directory /var/log/journal/3286b2469d224077b1026d239d625b0d removed. mmap cache statistics: 739 hit, 5 miss journal_file_copy_entry failed: Bad message Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function main(). Aborting. FAIL: test-journal-flush (code: 134) Aborted (core dumped) == test-journal-importer === [...] autopkgtest [07:17:29]: summary timedatedPASS hostnamedPASS localed-locale PASS localed-x11-keymap PASS logind PASS unit-config PASS storage PASS networkd-test.py PASS build-login PASS boot-and-servicesPASS udev PASS root-unittests FAIL non-zero exit status 134 upstream PASS boot-smoke PASS systemd-fsckdPASS Exit request sent. [...] ** 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/1881947 Title: Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function main(). Aborting. Status in systemd package in Ubuntu: New Bug description: Observed in an focal/arm64 autopkgtest failure of systemd 245.4-4ubuntu3.1: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20200603_071743_738b2@/log.gz [...] PASS: test-journal-enum == test-journal-flush === Root directory /var/log/journal removed. Directory /var/log/journal/3286b2469d224077b1026d239d625b0d removed. mmap cache statistics: 739 hit, 5 miss journal_file_copy_entry failed: Bad message Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function main(). Aborting. FAIL: test-journal-flush (code: 134) Aborted (core dumped) == test-journal-importer === [...] autopkgtest [07:17:29]: summary timedatedPASS hostnamedPASS localed-locale PASS localed-x11-keymap PASS logind PASS unit-config PASS storage PASS networkd-test.py PASS build-login PASS boot-and-servicesPASS udev PASS root-unittests FAIL non-zero exit status 134 upstream PASS boot-smoke PASS systemd-fsckdPASS Exit request sent. [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1881947/+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 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content
This bug was fixed in the package apport - 2.20.11-0ubuntu37 --- apport (2.20.11-0ubuntu37) groovy; urgency=medium * apport/report.py: If the user is not a part of any system groups then set UserGroups to an empty string. (LP: #1427600) -- Brian Murray Tue, 02 Jun 2020 10:19:45 -0700 ** Changed in: apport (Ubuntu Groovy) Status: In Progress => Fix Released -- 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/1427600 Title: apport-unpack: ValueError: ['UserGroups'] has no binary content Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Triaged Status in apport source package in Groovy: Fix Released Bug description: When running apport-unpack to get at a core dump laney@raleigh> sudo apport-unpack _usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz [sudo] password for laney: Traceback (most recent call last): File "/usr/bin/apport-unpack", line 73, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in extract_keys [item for item, element in b64_block.items() if element is False]) ValueError: ['UserGroups'] has no binary content laney@raleigh> apport-cli --version 2.16.2 It's not terrible, because most files are unpacked (those which sort before UserGroups, I guess). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apport 2.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportLog: ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 10:09:26 2015 InstallationDate: Installed on 2012-10-07 (876 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+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 1879080] Re: error message when installing pyodbc in a venv
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python3-defaults (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1879080
Title:
error message when installing pyodbc in a venv
Status in python3-defaults package in Ubuntu:
Confirmed
Bug description:
I have a fresh install of Ubuntu 20.04. I have the following packages
installed:
python3-venv
python3-pip
python3-wheel
unixodbc-dev
If I run these commands:
python3 -m venv ./test_env
. ./test_env/bin/activate
pip3 install pyodbc
This is the output I get. The package does seem to install
successfully, in spite of the fact that this is an error, not a
warning.
Collecting pyodbc
Downloading pyodbc-4.0.30.tar.gz (266 kB)
|| 266 kB 3.5 MB/s
Building wheels for collected packages: pyodbc
Building wheel for pyodbc (setup.py) ... error
ERROR: Command errored out with exit status 1:
command: /tmp/test_env/bin/python3 -u -c 'import sys, setuptools,
tokenize; sys.argv[0] = '"'"'/tmp/pip-install-5uh1fr89/pyodbc/setup.py'"'"';
__file__='"'"'/tmp/pip-install-5uh1fr89/pyodbc/setup.py'"'"';f=getattr(tokenize,
'"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"',
'"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))'
bdist_wheel -d /tmp/pip-wheel-snlh9z0l
cwd: /tmp/pip-install-5uh1fr89/pyodbc/
Complete output (6 lines):
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
error: invalid command 'bdist_wheel'
ERROR: Failed building wheel for pyodbc
Running setup.py clean for pyodbc
Failed to build pyodbc
Installing collected packages: pyodbc
Running setup.py install for pyodbc ... done
Successfully installed pyodbc-4.0.30
Note that I do not get this error if I install pyodbc outside the
venv. Also, if I install it outside the venv FIRST, then pip will
cache the wheel package and use it when installing in the venv, and I
don't get the above error in that case.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: python3 3.8.2-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat May 16 10:14:28 2020
InstallationDate: Installed on 2020-05-16 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: python3-defaults
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1879080/+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 1881942] [NEW] default configuration forwards sshd failures to port 7070
Public bug reported:
ubuntu eoan (19.10)
---
While investigating why my fail2ban client was not blocking the usual
script-kiddie SSH attempts, I discovered that no sshd failures were
appearing in /var/log/auth.log. Upon opening
/etc/rsyslog.d/50-default.conf I discovered that sshd failures are being
transformed and forwarded to localhost:7070. Here's the section of
configuration:
if $programname == 'sshd' then {
if $msg startswith ' Failed' then {
# Transform and forward data!
action(type="omfwd" target="127.0.0.1" port="7070" protocol="tcp"
template="ip-json")
}
stop
}
For me, nothing is bound to port 7070.
I assume you have a good reason for such a default but it seems
suboptimal to stop processing after forwarding. I commented out the
stop line and restarted rsyslog and found that logs appeared in
/var/log/auth.log and that my fail2ban is now banning IPs, as expected.
I suggest changing the default configuration so that sshd failures reach
/var/log/auth.log.
** Affects: rsyslog (Ubuntu)
Importance: Undecided
Status: New
** Tags: eoan
--
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/1881942
Title:
default configuration forwards sshd failures to port 7070
Status in rsyslog package in Ubuntu:
New
Bug description:
ubuntu eoan (19.10)
---
While investigating why my fail2ban client was not blocking the usual
script-kiddie SSH attempts, I discovered that no sshd failures were
appearing in /var/log/auth.log. Upon opening
/etc/rsyslog.d/50-default.conf I discovered that sshd failures are
being transformed and forwarded to localhost:7070. Here's the section
of configuration:
if $programname == 'sshd' then {
if $msg startswith ' Failed' then {
# Transform and forward data!
action(type="omfwd" target="127.0.0.1" port="7070" protocol="tcp"
template="ip-json")
}
stop
}
For me, nothing is bound to port 7070.
I assume you have a good reason for such a default but it seems
suboptimal to stop processing after forwarding. I commented out the
stop line and restarted rsyslog and found that logs appeared in
/var/log/auth.log and that my fail2ban is now banning IPs, as
expected.
I suggest changing the default configuration so that sshd failures
reach /var/log/auth.log.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1881942/+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 1881943] [NEW] [Inspiron 5391, Realtek ALC3204] Sound stopped to work, errors in dmesg
Public bug reported: Sound worked, but accidentally stopped to work at all. Just before it I had plugged and unplugged HDMI display (but without sound via HDMI). Only restart helped. Here is dmesg output while the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tenikeev 4612 F pulseaudio /dev/snd/pcmC0D0p: tenikeev 4612 F...m pulseaudio /dev/snd/pcmC0D6c: tenikeev 4612 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Jun 3 20:42:33 2020 InstallationDate: Installed on 2020-05-28 (5 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: июн 03 20:04:56 tenikeev-5391 dbus-daemon[3386]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=114 pid=4302 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") июн 03 20:04:59 tenikeev-5391 systemd[4295]: pulseaudio.service: Succeeded. июн 03 20:05:09 tenikeev-5391 systemd[4295]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 5391, Realtek ALC3204, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 07DM2C dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd11/21/2019:svnDellInc.:pnInspiron5391:pvr:rvnDellInc.:rn07DM2C:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5391 dmi.product.sku: 096E dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "dmesg output" https://bugs.launchpad.net/bugs/1881943/+attachment/5380086/+files/dmesg_snd -- 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/1881943 Title: [Inspiron 5391, Realtek ALC3204] Sound stopped to work, errors in dmesg Status in alsa-driver package in Ubuntu: New Bug description: Sound worked, but accidentally stopped to work at all. Just before it I had plugged and unplugged HDMI display (but without sound via HDMI). Only restart helped. Here is dmesg output while the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tenikeev 4612 F pulseaudio /dev/snd/pcmC0D0p: tenikeev 4612 F...m pulseaudio /dev/snd/pcmC0D6c: tenikeev 4612 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Jun 3 20:42:33 2020 InstallationDate: Installed on 2020-05-28 (5 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: июн 03 20:04:56 tenikeev-5391 dbus-daemon[3386]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=114 pid=4302 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") июн 03 20:04:59 tenikeev-5391 systemd[4295]: pulseaudio.service: Succeeded. июн 03 20:05:09 tenikeev-5391 systemd[4295]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 5391, Realtek ALC3204, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 07DM2C dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd11/21/2019:svnDellInc.:pnInspiron5391:pvr:rvnDellInc.:rn07DM2C:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5391 dmi.product.sku: 096E dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1881943/+subscriptions --
[Touch-packages] [Bug 1881941] [NEW] Ubuntu dock behaves crazy when hidden
Public bug reported: I had put the dock on the bottom of the screen and also set to hide automatically. The dock works fine as expected but there are sometimes (actually like 90% of the time) that it behaves weird when I try to access it with the mouse pointer, the dock starts to bounce quickly without stopping and then it's kind of hard to press the icons on it (when I'm lucky I can click the icon), other times I had to move away the pointer from the bottom and then move it back to access the dock. I made a video of it although it's very short but you can see for a brief of time how the dock starts to bounce. I haven't installed new packages or applications that change the behaviour of the dock in any way. tavoge@e6430s:~$ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 tavoge@e6430s:~$ apt-cache policy xorg xorg: Instalados: 1:7.7+19ubuntu14 Candidato: 1:7.7+19ubuntu14 Tabla de versión: *** 1:7.7+19ubuntu14 500 500 http://mx.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 11:40:48 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:057d] InstallationDate: Installed on 2020-05-29 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Latitude E6430s ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0XHTPW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd11/30/2018:svnDellInc.:pnLatitudeE6430s:pvr01:rvnDellInc.:rn0XHTPW:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6430s dmi.product.sku: Latitude E6430s dmi.product.version: 01 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.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 ** Attachment added: "ubuntu dock bouncing crazy" https://bugs.launchpad.net/bugs/1881941/+attachment/5380067/+files/WhatsApp%20Video%202020-06-03%20at%2012.23.40%20PM.mp4 -- 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/1881941 Title: Ubuntu dock behaves crazy when hidden Status in xorg package in Ubuntu: New Bug description: I had put the dock on the bottom of the screen and also set to hide automatically. The dock works fine as expected but there are sometimes (actually like 90% of the time) that it behaves weird when I try to access it with the mouse pointer, the dock starts to bounce quickly without stopping and then it's kind of hard to press the icons on it (when I'm lucky I can click the icon), other times I had to move away the pointer from the bottom and then move it back to access the dock. I made a video of it although it's very short but you can see for a brief of time how the dock starts to bounce. I haven't installed new packages or applications that change the behaviour of the dock in any way. tavoge@e6430s:~$ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 tavoge@e6430s:~$ apt-cache policy xorg xorg: Instalados: 1:7.7+19ubuntu14 Candidato: 1:7.7+19ubuntu14 Tabla de versión: *** 1:7.7+19ubuntu14 500 500 http://mx.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 1881935] Re: Minimum inode size should be raised to 256 for forward compatibility (Y2038)
Actually this is not an installer issue, just indirectly.
** Package changed: ubiquity (Ubuntu) => e2fsprogs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1881935
Title:
Minimum inode size should be raised to 256 for forward compatibility
(Y2038)
Status in e2fsprogs package in Ubuntu:
New
Bug description:
mke2fs in all supported Ubuntu releases to date creates 'small' ext4
file systems with an inode size of 128. This is said to be
insufficient to store time stamps referring to year 2038 and later
(when the Unix epoch exceeds a signed 32-bit integer -
https://en.wikipedia.org/wiki/Year_2038_problem). When such file
systems are mounted by the kernel, such as a /boot file system created
by the Ubuntu 20.04.0 Desktop installer (ubiquity 20.04.15), the
kernel will warn about this fact:
kernel: ext4 filesystem being mounted at /boot supports timestamps
until 2038 (0x7fff)
Cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953494
Admittedly, that's another 18 years, by when most systems installed
now will be no longer in use, or will have been reinstalled.
Also, on a /boot file system the 5.4.0-33-generic #37 Ubuntu (20.04) kernel
warned about this, I was able to
$ touch -t 203812312359 /tmp/test
and got
$ ls -l /tmp/test
-rw-r--r-- 1 root root 0 Dez 31 2038 /tmp/test
so this warning may not always apply, or patches may have been applied to
handle this situation more gracefully already.
Ubuntu 20.04 comes with e2fsprogs 1.45.5-2ubuntu1. Theodore Y. Ts'o
has submitted patches for Debian's 1.45.6-1 - but (strictly speaking
based on the changelog) these seem to be limited to documentation
changes.
Still, creating such file systems may seem undesirable in terms of
forward compatibility. I therefore suggest to change the minimum inode
size for mke2fs, as defined in /etc/mke2fs.conf, to 256 for all file
systems which do not already use this value (maybe with the exception
of floppies). That is, I suggest the following change to Ubuntu
20.04's /etc/mke2fs.conf:
Before change:
small = {
inode_size = 128
inode_ratio = 4096
}
After change:
small = {
inode_ratio = 4096
}
This assumes that the default inode size is already set to 256 further
above.
As a WORKAROUND, after backing up the file system (this command is not well
tested, according to the lead ext4 file system developer), users can unmount
the affected file system and run
tune2fs -I 256 /path/to/block_device
where /path/to/block_device should be replaced by the path to the block
device which contains the file system the kernel reports the warning for. For
example, for the file system mounted at /boot, the
findmnt /boot
command would return the block device path in the SOURCE column.
Please note I prefer not to use apport for this bug report, I believe it is
already sufficiently complete.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1881935/+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 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke
Maybe push it to PPA? -- 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/1881549 Title: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Incomplete Status in wpa package in Ubuntu: New Bug description: Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1438 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-09 (329 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+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 1881935] [NEW] Minimum inode size should be raised to 256 for forward compatibility (Y2038)
You have been subscribed to a public bug:
mke2fs in all supported Ubuntu releases to date creates 'small' ext4
file systems with an inode size of 128. This is said to be insufficient
to store time stamps referring to year 2038 and later (when the Unix
epoch exceeds a signed 32-bit integer -
https://en.wikipedia.org/wiki/Year_2038_problem). When such file systems
are mounted by the kernel, such as a /boot file system created by the
Ubuntu 20.04.0 Desktop installer (ubiquity 20.04.15), the kernel will
warn about this fact:
kernel: ext4 filesystem being mounted at /boot supports timestamps
until 2038 (0x7fff)
Cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953494
Admittedly, that's another 18 years, by when most systems installed now
will be no longer in use, or will have been reinstalled.
Also, on a /boot file system the 5.4.0-33-generic #37 Ubuntu (20.04) kernel
warned about this, I was able to
$ touch -t 203812312359 /tmp/test
and got
$ ls -l /tmp/test
-rw-r--r-- 1 root root 0 Dez 31 2038 /tmp/test
so this warning may not always apply, or patches may have been applied to
handle this situation more gracefully already.
Ubuntu 20.04 comes with e2fsprogs 1.45.5-2ubuntu1. Theodore Y. Ts'o has
submitted patches for Debian's 1.45.6-1 - but (strictly speaking based
on the changelog) these seem to be limited to documentation changes.
Still, creating such file systems may seem undesirable in terms of
forward compatibility. I therefore suggest to change the minimum inode
size for mke2fs, as defined in /etc/mke2fs.conf, to 256 for all file
systems which do not already use this value (maybe with the exception of
floppies). That is, I suggest the following change to Ubuntu 20.04's
/etc/mke2fs.conf:
Before change:
small = {
inode_size = 128
inode_ratio = 4096
}
After change:
small = {
inode_ratio = 4096
}
This assumes that the default inode size is already set to 256 further
above.
As a WORKAROUND, after backing up the file system (this command is not well
tested, according to the lead ext4 file system developer), users can unmount
the affected file system and run
tune2fs -I 256 /path/to/block_device
where /path/to/block_device should be replaced by the path to the block device
which contains the file system the kernel reports the warning for. For example,
for the file system mounted at /boot, the
findmnt /boot
command would return the block device path in the SOURCE column.
Please note I prefer not to use apport for this bug report, I believe it is
already sufficiently complete.
** Affects: e2fsprogs (Ubuntu)
Importance: Undecided
Status: New
** Tags: focal
--
Minimum inode size should be raised to 256 for forward compatibility (Y2038)
https://bugs.launchpad.net/bugs/1881935
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to e2fsprogs 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 1881278] Re: Ship 2018 Archive key in xenial's ubuntu-keyring
Hello Dimitri, or anyone else affected, Accepted ubuntu-keyring into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- keyring/2012.05.19.1 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- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. 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: ubuntu-keyring (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1881278 Title: Ship 2018 Archive key in xenial's ubuntu-keyring Status in ubuntu-keyring package in Ubuntu: Invalid Status in ubuntu-keyring source package in Xenial: Fix Committed Bug description: [Impact] * Xenial systems will not be able to debootstrap Groovy archives when it finally switches to be signed by single 2018 key. To have support for xenial to operate against Groovy+ archives it needs access to 2018 archive key. Ship it. [Test Case] * Start xenial chroot or lxd container. * Observe that 4 keys are trusted - the original 2004 archive & cdimage, 2012 archive & cdimage # apt-key list --fingerprint /etc/apt/trusted.gpg pub 1024D/437D05B5 2004-09-12 Key fingerprint = 6302 39CC 130E 1A7F D81A 27B1 4097 6EAF 437D 05B5 uid Ubuntu Archive Automatic Signing Key sub 2048g/79164387 2004-09-12 pub 4096R/C0B21F32 2012-05-11 Key fingerprint = 790B C727 7767 219C 42C8 6F93 3B4F E6AC C0B2 1F32 uid Ubuntu Archive Automatic Signing Key (2012) pub 4096R/EFE21092 2012-05-11 Key fingerprint = 8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092 uid Ubuntu CD Image Automatic Signing Key (2012) pub 1024D/FBB75451 2004-12-30 Key fingerprint = C598 6B4F 1257 FFA8 6632 CBA7 4618 1433 FBB7 5451 uid Ubuntu CD Image Automatic Signing Key * Install the new ubuntu-keyring package * Observe that 5 keys are now trusted, including the 2018 archive key # apt-key list --fingerprint /etc/apt/trusted.gpg pub 1024D/437D05B5 2004-09-12 Key fingerprint = 6302 39CC 130E 1A7F D81A 27B1 4097 6EAF 437D 05B5 uid Ubuntu Archive Automatic Signing Key sub 2048g/79164387 2004-09-12 pub 4096R/C0B21F32 2012-05-11 Key fingerprint = 790B C727 7767 219C 42C8 6F93 3B4F E6AC C0B2 1F32 uid Ubuntu Archive Automatic Signing Key (2012) pub 4096R/EFE21092 2012-05-11 Key fingerprint = 8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092 uid Ubuntu CD Image Automatic Signing Key (2012) pub 1024D/FBB75451 2004-12-30 Key fingerprint = C598 6B4F 1257 FFA8 6632 CBA7 4618 1433 FBB7 5451 uid Ubuntu CD Image Automatic Signing Key pub 4096R/991BC93C 2018-09-17 Key fingerprint = F6EC B376 2474 EDA9 D21B 7022 8719 20D1 991B C93C uid Ubuntu Archive Automatic Signing Key (2018) * Dist upgrade to bionic * Observe that only 3 keys are trusted the 2012 cdimage + 2018 key, and that none of them are in /etc/apt/trusted.gpg but are key snippets in /etc/apt/trusted.gpg.d/ # apt-key list /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg -- pub rsa4096 2012-05-11 [SC] 790B C727 7767 219C 42C8 6F93 3B4F E6AC C0B2 1F32 uid [ unknown] Ubuntu Archive Automatic Signing Key (2012) /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg -- pub rsa4096 2012-05-11 [SC] 8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092 uid [ unknown] Ubuntu CD Image Automatic Signing Key (2012)
[Touch-packages] [Bug 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke
I built a fixed version here if you're willing to trust a stranger on the internet: https://drive.google.com/file/d/1BrXOZH-E_cw93HBmk7id1LzUJtnYVsQn/view?usp=sharing -- 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/1881549 Title: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Incomplete Status in wpa package in Ubuntu: New Bug description: Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1438 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-09 (329 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+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 682445] Re: configure_networking doesn't wait for udev to populate available nics
This was fixed long ago. initramfs-tools (0.100) unstable; urgency=low Release "singing in the snow ☃☃☃" [...] [ Alkis Georgopoulos ] * [b938c7e] configure_networking() wait for udev to populate available nics (LP: #682445) [...] -- Michael Prokop Tue, 14 Feb 2012 14:42:23 +0100 ** Changed in: initramfs-tools (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/682445 Title: configure_networking doesn't wait for udev to populate available nics Status in initramfs-tools package in Ubuntu: Fix Released Bug description: Binary package hint: initramfs-tools Been seeing that since Karmic, and just reproduced it with Natty. In /usr/share/initramfs-tools/scripts/functions, function configure_networking() is called from the initramfs to setup a network connection for e.g. diskless booting. This function doesn't call `udevadm settle` or anything similar to wait until the NICs are made available by udev. So many times booting fails with messages like "ipconfig: no devices to configure" etc. Attaching a screenshot that displays the problem. configure_networking tried to call ipconfig before the NIC was available, so booting failed. After a couple of secs udev initialized the NIC. A workaround is to pass "break=mount" in the kernel options, wait until udev initializes, and then press Ctrl+D to continue booting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/682445/+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 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke
Prior to this commit https://w1.fi/cgit/hostap/commit/?id=23dc196fde951b3d508f367a603cddffbd053490 hostapd doesn't check if the driver supports 802.11R aka. FT. -- 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/1881549 Title: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Incomplete Status in wpa package in Ubuntu: New Bug description: Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1438 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-09 (329 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+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 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
The only time i got sound from my speakers is when i was using the live pen drive to test to make sure i had sound. i checked all i had-you tubes, mp3's, mscz, flv...on two different occasions. everything worked fine. i did the install and nothing after that. except for One Night some time after the install...i swear they worked, and i listened to music four hours. the next time i logged in they were gone again and never came back. i thought maybe some update had been done and then it had to be removed, dont know what to think. i didnt try the config thing because i was of the understanding that it wasnt a permanent fix-not to mention the fact that i am scared of messing with config files. by the way, i never had the problem of 'no sound' described in the bug report, i always had the internal speakers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Focal: In Progress Status in pulseaudio source package in Groovy: In Progress Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1866194/+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 1880041] Re: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later
Upgrading Kubuntu 19.10 to 20.04 and thus to 5.4.0-33-generic solved this issue for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later Status in DRI: Unknown Status in libdrm package in Ubuntu: Confirmed Status in linux-meta-hwe package in Ubuntu: Confirmed Bug description: When booting up Ubuntu 18.04 with a kernel version of 5.3.0-52 or later (including 5.3.0-53), everything seems to be working as usual. However, when I shutdown, the system will only soft shutdown, with the CPU still running at full power, forcing me to hold down the power button to fully power off affected systems. If I reboot, it will cause the system to hang and not respond. Either way, a hard reset or poweroff will be required, and this is not an option for systems being remotely accessed. It is not possible for me to collect kernel logs at this point, unless something wrong is happening in those kernel versions before the actual shutdown. It is possible that this may also occur on Ubuntu 20.04 with kernel versions 5.4.0-29 and later, but I have not yet tested this out. This problem is occurring on both my desktop and laptop computers which respectively are: * AsRock B450 Pro4 with AMD Ryzen 3 3200G APU * Lenovo ThinkPad A485 with AMD Ryzen 5 Pro 2500U mobile APU In the meantime, I am stuck on kernel version 5.3.0-51, as that is the last working 5.3.x kernel version offered in the standard Ubuntu repositories that doesn't have this problem, without me having to use PPAs. I don't know if this problem also occurs on systems with Intel CPUs, as I don't own any recently-made system (last 3 years from 2017) with such CPUs to test if this problem occurs on them. To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+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 1881917] [NEW] [S451LA, Realtek ALC3236, Speaker, Internal] No sound at all
Public bug reported: Yesterday my notebook was working like a charm, but today it does not make any sound, and does not hear anything also. I have checked the sound tab at system settings, and the output device bar was working when I played music, altough I could not hear anything at all. Also, the input device bar did not move when I did speak. I do belive this bug is somehow related to the headphone. Yesterday before shutting down the PC, I was listening to music with a headphone pluged at the 3.5mm jack, but today before powering it up, i took it off. Also, when I change the volume, the popup display showing the volume level is labled with "Headphones". Oh, and of course, I tried to restart the PC, it did not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guilherme 1173 F pulseaudio /dev/snd/controlC0: guilherme 1173 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 10:20:18 2020 InstallationDate: Installed on 2020-05-26 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guilherme 1173 F pulseaudio /dev/snd/controlC0: guilherme 1173 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [S451LA, Realtek ALC3236, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S451LA.403 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: S451LA 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.:bvrS451LA.403:bd01/17/2014:svnASUSTeKCOMPUTERINC.:pnS451LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS451LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: S dmi.product.name: S451LA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1881917 Title: [S451LA, Realtek ALC3236, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Yesterday my notebook was working like a charm, but today it does not make any sound, and does not hear anything also. I have checked the sound tab at system settings, and the output device bar was working when I played music, altough I could not hear anything at all. Also, the input device bar did not move when I did speak. I do belive this bug is somehow related to the headphone. Yesterday before shutting down the PC, I was listening to music with a headphone pluged at the 3.5mm jack, but today before powering it up, i took it off. Also, when I change the volume, the popup display showing the volume level is labled with "Headphones". Oh, and of course, I tried to restart the PC, it did not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guilherme 1173 F pulseaudio /dev/snd/controlC0: guilherme 1173 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 10:20:18 2020 InstallationDate: Installed on 2020-05-26 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guilherme 1173 F pulseaudio /dev/snd/controlC0: guilherme 1173 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [S451LA, Realtek ALC3236, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.vendor:
Re: [Touch-packages] [Bug 1870550] Re: PCI/internal sound card not detected
@Hui Again so sorry for the delay I've removed all instances of the dmic_detect=0 and attached the dmesg for both the 5.3.0-46 and 5.3.0-53 versions. Thank you so much On Wed, May 13, 2020 at 9:55 PM Hui Wang wrote: > @Eric, > > please run "sudo grep dmic_detect /etc/* -r" to find where set the > dmic_detect=0, then remove it, and install the latest 5.3 kernel > (5.3.0-46 or later), then reboot and upolad the output of dmesg. > > thx. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1870550 > > Title: > PCI/internal sound card not detected > > Status in alsa-driver package in Ubuntu: > New > > Bug description: > The sound card is not detected on my machine > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu5 > ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 > Uname: Linux 5.3.0-45-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.14 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CurrentDesktop: ubuntu:GNOME > Date: Sat Apr 4 00:51:33 2020 > InstallationDate: Installed on 2020-02-25 (37 days ago) > InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 > (20200203.1) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Title: PCI/internal sound card not detected > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 03/02/2020 > dmi.bios.vendor: AMI > dmi.bios.version: F.13 > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name: 86FA > dmi.board.vendor: HP > dmi.board.version: 87.46 > dmi.chassis.type: 31 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnAMI:bvrF.13:bd03/02/2020:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.46:cvnHP:ct31:cvrChassisVersion: > dmi.product.family: 103C_5335KV HP Spectre > dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx > dmi.product.sku: 8UR41PA#ABG > dmi.sys.vendor: HP > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870550/+subscriptions > ** Attachment added: "dmesg_out-v5.3.0-53.txt" https://bugs.launchpad.net/bugs/1870550/+attachment/5380045/+files/dmesg_out-v5.3.0-53.txt ** Attachment added: "dmesg_out-v5.3.0-46.txt" https://bugs.launchpad.net/bugs/1870550/+attachment/5380046/+files/dmesg_out-v5.3.0-46.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/1870550 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: The sound card is not detected on my machine ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 00:51:33 2020 InstallationDate: Installed on 2020-02-25 (37 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2020 dmi.bios.vendor: AMI dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FA dmi.board.vendor: HP dmi.board.version: 87.46 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.13:bd03/02/2020:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.46:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx dmi.product.sku: 8UR41PA#ABG dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870550/+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 1871154] Re: Error message displayed during boot (mountroot hook, premount)
Thanks a lot! And I confirm that the error message no longer appears :>. -- 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/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in initramfs-tools package in Ubuntu: Fix Released Status in lvm2 package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: In Progress Status in lvm2 source package in Focal: Invalid Bug description: [Impact] * People using lvm2 on ubuntu focal are getting a strange and weird message due to a wrong path [Test Case] * Install lvm2 on Ubuntu 20.04 [Regression Potential] * Low, the fix is already part of groovy [Other info] Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871154/+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 1881909] [NEW] Screen tearing [Optimus - GeForce 610m]
Public bug reported: I have screen tearing when using nvidia card with 390 driver, affect browsers such as firefox and chromium also desktop since I have screen tearing when moving window around. I have no such problem when using using 18.04.4 and nvidia card with 390 driver. Intel graphic have no such problem weather in 18.04 or 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 21:18:49 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:1652] NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GeForce GT 610M [1043:1652] InstallationDate: Installed on 2020-06-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK Computer Inc. K43SD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=8f02391a-a313-4598-b702-db7eccd55312 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K43SD.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K43SD 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.:bvrK43SD.208:bd08/10/2012:svnASUSTeKComputerInc.:pnK43SD:pvr1.0:rvnASUSTeKComputerInc.:rnK43SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K43SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Summary changed: - Screen tearing [Optimus] + Screen tearing [Optimus - GeForce 610m] ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-390 (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/1881909 Title: Screen tearing [Optimus - GeForce 610m] Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I have screen tearing when using nvidia card with 390 driver, affect browsers such as firefox and chromium also desktop since I have screen tearing when moving window around. I have no such problem when using using 18.04.4 and nvidia card with 390 driver. Intel graphic have no such problem weather in 18.04 or 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 21:18:49 2020 DistUpgraded: Fresh install
[Touch-packages] [Bug 1881783] Re: external audio device shown in pulseaudio but sound emitted through internal laptop speakers after fresh install
*** This bug is a duplicate of bug 1866194 *** https://bugs.launchpad.net/bugs/1866194 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881783 Title: external audio device shown in pulseaudio but sound emitted through internal laptop speakers after fresh install Status in pulseaudio package in Ubuntu: Confirmed Bug description: bug #1866194 appears the same but fix directed to upraders. not sure if you have all the information you need from me... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: salima 1081 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXDE Date: Tue Jun 2 21:54:50 2020 InstallationDate: Installed on 2020-05-19 (14 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 07JM0H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd05/20/2016:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn07JM0H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.product.sku: 06B2 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881783/+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 1771033] Re: [needs-packaging] python3-avahi is not available in Ubuntu/debian
** Changed in: avahi (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1771033 Title: [needs-packaging] python3-avahi is not available in Ubuntu/debian Status in avahi package in Ubuntu: Fix Committed Status in avahi package in Debian: Fix Released Bug description: Under Ubuntu 18.04 if you install the package Gajim the local account is permanently disabled because of missing dependencies. https://dev.gajim.org/gajim/gajim/issues/9125 The required package is python3-avahi The python3-avahi package is missing, apt-get is unable to find it. This is a vital feature for us, we use Gajim internally without internet, and this simply works, no adding accounts, no information or messages sent over the internet, it all works locally. I hope this package can be added, if this is the wrong place to file this bug I applologize. I don't have a lot of experience reporting bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1771033/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1872564] Re: /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice
On 2020-06-02 8:50 p.m., Chris Halse Rogers wrote:
> You don't *have* to include the full output of the test cases when
> verifying a bug (although, depending on how much output there is, it can
> be nice).
OK, good, thanks for clarifying!
> I don't think it was clear that you *had* gone through the full test-
> case in your verification comment - I'm not entirely sure what gave that
> impression, but I think it might have been the combination of *some*
> output (the apt/dpkg bit) and saying “the bug is fixed, thanks” without
> making reference to the test case.
True, I should have been more explicit, duly noted!
--
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/1872564
Title:
/proc/sys/kernel/random/boot_id rule missing from
abstractions/nameservice
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor source package in Focal:
Fix Released
Bug description:
[Impact]
On a default Focal install, systemd is used when looking up passwd and
group information:
# grep systemd /etc/nsswitch.conf
passwd: files systemd
group: files systemd
Daemons confined by Apparmor that also query those "databases" will
cause this Apparmor denial:
audit: type=1400 audit(1586825456.411:247): apparmor="DENIED"
operation="open" namespace="root//lxd-fb1_"
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id"
pid=7370 comm="named" requested_mask="r" denied_mask="r" fsuid=100
ouid=100
Many daemons confined by Apparmor also happen to downgrade their
privileges so they always end up looking up user/group information.
To fix this problem, we had to backport an upstream patch which adds
new directives to the 'nameservices' apparmor profile.
[Test Case]
In order to reproduce the bug, one can:
1) launch a Focal container (named fb1 here)
$ lxc launch images:ubuntu/focal fb1
2) setup apparmor inside the container (already done on official Ubuntu
images)
$ lxc exec fb1 -- apt update && lxc exec fb1 -- apt install apparmor -y
3) install bind9
$ lxc exec fb1 -- apt install bind9 -y
4) check kernel logs for DENIED
$ journalctl -o cat -b0 -k | grep 'apparmor="DENIED"' | grep -F
'profile="/usr/sbin/named"'
or, depending on how logging is configured:
$ dmesg | grep 'apparmor="DENIED"' | grep -F
'profile="/usr/sbin/named"'
Step 4, should not return anything. Because systemd is involved in the
user/group lookups, it currently returns the following:
audit: type=1400 audit(1586826072.115:266): apparmor="DENIED"
operation="open" namespace="root//lxd-fb1_"
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
audit: type=1400 audit(1586826072.115:267): apparmor="DENIED"
operation="open" namespace="root//lxd-fb1_"
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
audit: type=1400 audit(1586826072.115:268): apparmor="DENIED"
operation="open" namespace="root//lxd-fb1_"
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
audit: type=1400 audit(1586826072.115:269): apparmor="DENIED"
operation="open" namespace="root//lxd-fb1_"
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
audit: type=1400 audit(1586826072.115:270): apparmor="DENIED"
operation="open" namespace="root//lxd-fb1_"
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
[Regression Potential]
In order to fix this issue, 3 separate patches had to be backported.
They are simple and self-contained, especially two of them, whose
purposes are to add the definition of the @{run} variable and then to
add a trailing slash at the end of the "/run" pathname.
The other patch, albeit very simple, adds three statements to the
'nameservice' profile in order to let processes access (read-only)
files under "/run/systemd/userdb" and
"/proc/sys/kernel/random/boot_id". After thinking about the possible
cases, the only possible problem I could envision was for a program
that, not being able to access some of these files before, will now be
able to do that and therefore exercise a part of its codebase which
was not being used, possibly uncovering latent bugs in this software.
But this is not a regression of apparmor per se.
[Original Description]
(Description and Test Case were moved above)
# Workaround
1) remove systemd from nsswitch.conf
$ lxc exec fb1 -- sed -i 's/ systemd$/ # systemd/'
[Touch-packages] [Bug 1881888] Re: Bluetooth Always Disconnected After Suspend
** Package changed: bluez (Ubuntu) => linux (Ubuntu) -- 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/1881888 Title: Bluetooth Always Disconnected After Suspend Status in linux package in Ubuntu: New Bug description: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 L2CAP: Connection Response (0x03) ident 16 len 8 Destination CID: 0 Source CID: 68 Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:CF:5E:0F:06:FB ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:3010 acl:50 sco:0 events:153 errors:0 TX bytes:5047 acl:50 sco:0 commands:67 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881888/+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 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke
Not conclusive this's a kernel driver issue yet, also affects to "wpa" as wpasupplicant could be related. ** Also affects: wpa (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1881549 Title: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Incomplete Status in wpa package in Ubuntu: New Bug description: Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1438 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-09 (329 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+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 1659534] Re: userdel doesn't supports extrausers
Big thanks guys! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1659534 Title: userdel doesn't supports extrausers Status in Snappy: Fix Released Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Xenial: Fix Released Status in shadow source package in Bionic: Fix Released Status in shadow source package in Cosmic: Won't Fix Bug description: TEST CASE: - run userdel --extrausers foo on a ubuntu core system REGRESSION POTENTIAL: - low, this option will only take effect when "userdel --extrauser" is used. On an Ubuntu Core system is impossible to delete an user from the extrausers db: root@localhost:/# userdel --extrausers alice userdel: unrecognized option '--extrausers' To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659534/+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 1881888] Re: Bluetooth Always Disconnected After Suspend
** Attachment added: "hciconfig adapter info" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+attachment/5380006/+files/hciconfig ** Description changed: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 - L2CAP: Connection Response (0x03) ident 16 len 8 - Destination CID: 0 - Source CID: 68 - Result: Connection refused - PSM not supported (0x0002) - Status: No further information available (0x) + L2CAP: Connection Response (0x03) ident 16 len 8 + Destination CID: 0 + Source CID: 68 + Result: Connection refused - PSM not supported (0x0002) + Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) + bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer hciconfig: - hci0:Type: Primary Bus: USB - BD Address: 18:CF:5E:0F:06:FB ACL MTU: 1022:8 SCO MTU: 183:5 - UP RUNNING PSCAN - RX bytes:3010 acl:50 sco:0 events:153 errors:0 - TX bytes:5047 acl:50 sco:0 commands:67 errors:0 + hci0:Type: Primary Bus: USB + BD Address: 18:CF:5E:0F:06:FB ACL MTU: 1022:8 SCO MTU: 183:5 + UP RUNNING PSCAN + RX bytes:3010 acl:50 sco:0 events:153 errors:0 + TX bytes:5047 acl:50 sco:0 commands:67 errors:0 -- 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/1881888 Title: Bluetooth Always Disconnected After Suspend Status in bluez package in Ubuntu: New Bug description: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 L2CAP: Connection Response (0x03) ident 16 len 8 Destination CID: 0 Source CID: 68 Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia:
[Touch-packages] [Bug 1881888] Re: Bluetooth Always Disconnected After Suspend
** Attachment added: "vivo device (bluetoothctl)" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+attachment/5380005/+files/bluetoothctl.vivo.info -- 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/1881888 Title: Bluetooth Always Disconnected After Suspend Status in bluez package in Ubuntu: New Bug description: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 L2CAP: Connection Response (0x03) ident 16 len 8 Destination CID: 0 Source CID: 68 Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:CF:5E:0F:06:FB ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:3010 acl:50 sco:0 events:153 errors:0 TX bytes:5047 acl:50 sco:0 commands:67 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+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 1881888] [NEW] Bluetooth Always Disconnected After Suspend
Public bug reported: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 L2CAP: Connection Response (0x03) ident 16 len 8 Destination CID: 0 Source CID: 68 Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer hciconfig: hci0: Type: Primary Bus: USB BD Address: 18:CF:5E:0F:06:FB ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:3010 acl:50 sco:0 events:153 errors:0 TX bytes:5047 acl:50 sco:0 commands:67 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "hcitrace from btmon" https://bugs.launchpad.net/bugs/1881888/+attachment/5379984/+files/btmon.hcitrace.txt -- 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/1881888 Title: Bluetooth Always Disconnected After Suspend Status in bluez package in Ubuntu: New Bug description: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 L2CAP: Connection Response (0x03) ident 16 len 8 Destination CID: 0 Source CID: 68 Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer
[Touch-packages] [Bug 1881888] Re: Bluetooth Always Disconnected After Suspend
** Attachment added: "show output (bluetoothctl)" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+attachment/5380004/+files/bluetoothctl.show -- 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/1881888 Title: Bluetooth Always Disconnected After Suspend Status in bluez package in Ubuntu: New Bug description: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 L2CAP: Connection Response (0x03) ident 16 len 8 Destination CID: 0 Source CID: 68 Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:CF:5E:0F:06:FB ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:3010 acl:50 sco:0 events:153 errors:0 TX bytes:5047 acl:50 sco:0 commands:67 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+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 1881888] Re: Bluetooth Always Disconnected After Suspend
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+attachment/5380002/+files/bugreport.syslog -- 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/1881888 Title: Bluetooth Always Disconnected After Suspend Status in bluez package in Ubuntu: New Bug description: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 L2CAP: Connection Response (0x03) ident 16 len 8 Destination CID: 0 Source CID: 68 Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:CF:5E:0F:06:FB ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:3010 acl:50 sco:0 events:153 errors:0 TX bytes:5047 acl:50 sco:0 commands:67 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+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 1881888] Re: Bluetooth Always Disconnected After Suspend
** Attachment added: "devices list (bluetoothctl)" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+attachment/5380003/+files/bluetoothctl.devices -- 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/1881888 Title: Bluetooth Always Disconnected After Suspend Status in bluez package in Ubuntu: New Bug description: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 L2CAP: Connection Response (0x03) ident 16 len 8 Destination CID: 0 Source CID: 68 Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:CF:5E:0F:06:FB ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:3010 acl:50 sco:0 events:153 errors:0 TX bytes:5047 acl:50 sco:0 commands:67 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+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 1881888] Re: Bluetooth Always Disconnected After Suspend
** Attachment added: "hcitrace from btmon (snoop format)" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+attachment/5380001/+files/btmon.hcitrace.snoop -- 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/1881888 Title: Bluetooth Always Disconnected After Suspend Status in bluez package in Ubuntu: New Bug description: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 L2CAP: Connection Response (0x03) ident 16 len 8 Destination CID: 0 Source CID: 68 Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:CF:5E:0F:06:FB ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:3010 acl:50 sco:0 events:153 errors:0 TX bytes:5047 acl:50 sco:0 commands:67 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+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 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
I had this problem these days. I wasn't upgrading, I was just migrating my /home user data around on ZFS. To fix I did the same thing, deleted the ~/.config/pulse directory. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Focal: In Progress Status in pulseaudio source package in Groovy: In Progress Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1866194/+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 1871154] Re: Error message displayed during boot (mountroot hook, premount)
initramfs-tools - 0.136ubuntu6.20.04.3 in my ppa now! -- 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/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in initramfs-tools package in Ubuntu: Fix Released Status in lvm2 package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: In Progress Status in lvm2 source package in Focal: Invalid Bug description: [Impact] * People using lvm2 on ubuntu focal are getting a strange and weird message due to a wrong path [Test Case] * Install lvm2 on Ubuntu 20.04 [Regression Potential] * Low, the fix is already part of groovy [Other info] Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871154/+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 1881859] Re: RaspberryPi and "openssl:Error: 'rehash' is an invalid command"
I think I incorrectly filed this against OpenSSL. I think it should be the ca-certificates package. ** Package changed: openssl (Ubuntu) => ca-certificates (Ubuntu) ** Description changed: Hi Everyone, I ran dist-upgrade today on my RPI-3. It resulted in: ``` Calculating upgrade... Done The following packages will be upgraded: - armbian-bionic-desktop armbian-config armbian-firmware ca-certificates - chromium-browser chromium-chromedriver chromium-codecs-ffmpeg-extra - python3-software-properties software-properties-common + armbian-bionic-desktop armbian-config armbian-firmware ca-certificates + chromium-browser chromium-chromedriver chromium-codecs-ffmpeg-extra + python3-software-properties software-properties-common 9 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ``` And: ``` ... Setting up chromium-codecs-ffmpeg-extra (83.0.4103.61-0ubuntu0.18.04.1) ... Setting up python3-software-properties (0.96.24.32.13) ... Setting up ca-certificates (20190110~18.04.1) ... Updating certificates in /etc/ssl/certs... openssl:Error: 'rehash' is an invalid command. Standard commands asn1parse caciphers cms crl crl2pkcs7 dgst dh dhparam dsa dsaparam ec ... 127 added, 8 removed; done. Setting up software-properties-common (0.96.24.32.13) ... Setting up chromium-browser (83.0.4103.61-0ubuntu0.18.04.1) ... ``` Operating System: ``` $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic ``` And finally: ``` + $ apt-cache show ca-certificates + Package: ca-certificates + Architecture: all + Version: 20190110~18.04.1 + Multi-Arch: foreign + Priority: important + Section: misc + Origin: Ubuntu + Maintainer: Ubuntu Developers + Original-Maintainer: Michael Shuler + Bugs: https://bugs.launchpad.net/ubuntu/+filebug + Installed-Size: 382 + Depends: openssl (>= 1.1.0), debconf (>= 0.5) | debconf-2.0 + Breaks: ca-certificates-java (<< 20121112+nmu1) + Enhances: openssl + Filename: pool/main/c/ca-certificates/ca-certificates_20190110~18.04.1_all.deb + Size: 145500 + MD5sum: f0c73db6f5e857f13af04aaa736f87f0 + SHA1: 8a3d4583491b426691a986ef11b1c805c2d4cf54 + SHA256: fcfa84619207690491a3f9ab898de3fb2d46eeb7a73d525b91d05e7655815f5b + Description: Common CA certificates + Description-md5: e867d2a359bea1800b5bff209fc65bd1 + Task: minimal + Supported: 5y + + Package: ca-certificates + Architecture: all + Version: 20180409 + Multi-Arch: foreign + Priority: important + Section: misc + Origin: Ubuntu + Maintainer: Ubuntu Developers + Original-Maintainer: Michael Shuler + Bugs: https://bugs.launchpad.net/ubuntu/+filebug + Installed-Size: 392 + Depends: openssl (>= 1.1.0), debconf (>= 0.5) | debconf-2.0 + Breaks: ca-certificates-java (<< 20121112+nmu1) + Enhances: openssl + Filename: pool/main/c/ca-certificates/ca-certificates_20180409_all.deb + Size: 150932 + MD5sum: eae40792673dcb994af86284d0a01f36 + SHA1: 8ac5ac1506810b0483f0b80b0652071348459fc4 + SHA256: 195ffe05ae7d060146f890b1db225f5e8c3a8c505ffbea1fba30a520a1cd58d8 + Description: Common CA certificates + Description-md5: e867d2a359bea1800b5bff209fc65bd1 + Task: minimal + Supported: 5y + + $ apt-cache show openssl Package: openssl Architecture: armhf Version: 1.1.1-1ubuntu2.1~18.04.6 Multi-Arch: foreign Priority: important Section: utils Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian OpenSSL Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 986 Depends: libc6 (>= 2.15), libssl1.1 (>= 1.1.1) Suggests: ca-certificates Filename: pool/main/o/openssl/openssl_1.1.1-1ubuntu2.1~18.04.6_armhf.deb Size: 589160 MD5sum: 37a31fce651134a5b057c9f6f356aaf2 SHA1: 476816221f03bae71ecd760e1e4e6d155f85e7c1 SHA256: 2787b66aba181e230f36ce49600b3a7d9dea7695aa332da0496a5e1a62281d39 Homepage: https://www.openssl.org/ Description: Secure Sockets Layer toolkit - cryptographic utility Description-md5: 9b6de2bb6e1d9016aeb0f00bcf6617bd Task: minimal Supported: 5y Package: openssl Architecture: armhf Version: 1.1.0g-2ubuntu4 Multi-Arch: foreign Priority: important Section: utils Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian OpenSSL Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 883 Depends: libc6 (>= 2.15), libssl1.1 (>= 1.1.0) Suggests: ca-certificates Filename: pool/main/o/openssl/openssl_1.1.0g-2ubuntu4_armhf.deb Size: 509616 MD5sum: 0645cdd015e63ab37fcebf6b5c81b823 SHA1: 89852170f97d4dc2e6a0e83b045318fd05342634 SHA256: 57adec97bf6dec47c6079ea8b94598e853334e99c88c5e86afa838cbc57fcd32 Homepage: https://www.openssl.org/ Description: Secure Sockets Layer
[Touch-packages] [Bug 1881859] [NEW] RaspberryPi and "openssl:Error: 'rehash' is an invalid command"
Public bug reported: Hi Everyone, I ran dist-upgrade today on my RPI-3. It resulted in: ``` Calculating upgrade... Done The following packages will be upgraded: armbian-bionic-desktop armbian-config armbian-firmware ca-certificates chromium-browser chromium-chromedriver chromium-codecs-ffmpeg-extra python3-software-properties software-properties-common 9 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ``` And: ``` ... Setting up chromium-codecs-ffmpeg-extra (83.0.4103.61-0ubuntu0.18.04.1) ... Setting up python3-software-properties (0.96.24.32.13) ... Setting up ca-certificates (20190110~18.04.1) ... Updating certificates in /etc/ssl/certs... openssl:Error: 'rehash' is an invalid command. Standard commands asn1parse caciphers cms crl crl2pkcs7 dgst dh dhparam dsa dsaparam ec ... 127 added, 8 removed; done. Setting up software-properties-common (0.96.24.32.13) ... Setting up chromium-browser (83.0.4103.61-0ubuntu0.18.04.1) ... ``` Operating System: ``` $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic ``` And finally: ``` $ apt-cache show openssl Package: openssl Architecture: armhf Version: 1.1.1-1ubuntu2.1~18.04.6 Multi-Arch: foreign Priority: important Section: utils Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian OpenSSL Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 986 Depends: libc6 (>= 2.15), libssl1.1 (>= 1.1.1) Suggests: ca-certificates Filename: pool/main/o/openssl/openssl_1.1.1-1ubuntu2.1~18.04.6_armhf.deb Size: 589160 MD5sum: 37a31fce651134a5b057c9f6f356aaf2 SHA1: 476816221f03bae71ecd760e1e4e6d155f85e7c1 SHA256: 2787b66aba181e230f36ce49600b3a7d9dea7695aa332da0496a5e1a62281d39 Homepage: https://www.openssl.org/ Description: Secure Sockets Layer toolkit - cryptographic utility Description-md5: 9b6de2bb6e1d9016aeb0f00bcf6617bd Task: minimal Supported: 5y Package: openssl Architecture: armhf Version: 1.1.0g-2ubuntu4 Multi-Arch: foreign Priority: important Section: utils Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian OpenSSL Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 883 Depends: libc6 (>= 2.15), libssl1.1 (>= 1.1.0) Suggests: ca-certificates Filename: pool/main/o/openssl/openssl_1.1.0g-2ubuntu4_armhf.deb Size: 509616 MD5sum: 0645cdd015e63ab37fcebf6b5c81b823 SHA1: 89852170f97d4dc2e6a0e83b045318fd05342634 SHA256: 57adec97bf6dec47c6079ea8b94598e853334e99c88c5e86afa838cbc57fcd32 Homepage: https://www.openssl.org/ Description: Secure Sockets Layer toolkit - cryptographic utility Description-md5: 9b6de2bb6e1d9016aeb0f00bcf6617bd Task: minimal Supported: 5y ``` ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1881859 Title: RaspberryPi and "openssl:Error: 'rehash' is an invalid command" Status in openssl package in Ubuntu: New Bug description: Hi Everyone, I ran dist-upgrade today on my RPI-3. It resulted in: ``` Calculating upgrade... Done The following packages will be upgraded: armbian-bionic-desktop armbian-config armbian-firmware ca-certificates chromium-browser chromium-chromedriver chromium-codecs-ffmpeg-extra python3-software-properties software-properties-common 9 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ``` And: ``` ... Setting up chromium-codecs-ffmpeg-extra (83.0.4103.61-0ubuntu0.18.04.1) ... Setting up python3-software-properties (0.96.24.32.13) ... Setting up ca-certificates (20190110~18.04.1) ... Updating certificates in /etc/ssl/certs... openssl:Error: 'rehash' is an invalid command. Standard commands asn1parse caciphers cms crl crl2pkcs7 dgst dh dhparam dsa dsaparam ec ... 127 added, 8 removed; done. Setting up software-properties-common (0.96.24.32.13) ... Setting up chromium-browser (83.0.4103.61-0ubuntu0.18.04.1) ... ``` Operating System: ``` $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic ``` And finally: ``` $ apt-cache show openssl Package: openssl Architecture: armhf Version: 1.1.1-1ubuntu2.1~18.04.6 Multi-Arch: foreign Priority: important Section: utils Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian OpenSSL Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 986 Depends: libc6
[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
** Changed in: oem-priority Status: Confirmed => Fix Committed ** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Fix Released Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Released Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1869819] Update Released
The verification of the Stable Release Update for pulseaudio has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Released Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
This bug was fixed in the package pulseaudio - 1:11.1-1ubuntu7.8 --- pulseaudio (1:11.1-1ubuntu7.8) bionic; urgency=medium [Kai-Heng Feng] * alsa-mixer: Support dual Front Headphone Jack (lp: #1869819) * alsa-mixer: Handle the index for ALSA mixer jack identifiers [Tanu Kaskinen ] * alsa-mixer: autodetect the ELD device * alsa-mixer: autodetect the HDMI jack PCM device * alsa-mixer: add hw_device_index to pa_alsa_mapping -- Kai-Heng Feng Thu, 14 May 2020 13:26:03 +0800 ** Changed in: pulseaudio (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Released Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+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
