[Touch-packages] [Bug 1851385] Re: ubuntu 19.10 / print bug : requires authentication
*** This bug is a duplicate of bug 1849859 *** https://bugs.launchpad.net/bugs/1849859 Same issue on Ubuntu 19.10 trying to access printer on samba share. Used to work on 18.04. Not obvious if related to bug #1849859, al least error message is different. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1851385 Title: ubuntu 19.10 / print bug : requires authentication Status in cups package in Ubuntu: Confirmed Bug description: Hello, I have 2 computers(one laptop and one desktop) which have a dual boot Windows / Ubuntu. My printer (Xerox WorkCentre 6015B) is plugged on a USB port from my modem on which my computers are connected using Wi- Fi. Since the upgrade of Ubuntu to version 19.10, I cannot print. On both computers I get the same message : [The printer] requires authentication / credentials required in order to print. With Ubuntu 19.04, I had absolutely no problem. I tried with a live USB with Ubuntu 19.04, there is no problem, the printer works. With a Ubuntu live 19.10, it doesn't work. If I plug the printer directly on a USB port on my computer, I get the same error message : [The printer] requires authentication / credentials required in order to print. It's the same behaviour on both computers, no I guess it must be a bug. Anyway I don't know which authentication I could do, with which ID and password ? Thank you very much ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 15:12:07 2019 Lpstat: device for Xerox_WorkCentre_6015B_Wi-Fi: smb://FREEBOX_SERVER/Xerox%20WorkCentre%206015B MachineType: Acer Aspire V5-571 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=fb8ccf3e-9970-4066-bae2-26fe4387c122 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571 dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd12/21/2012:svnAcer:pnAspireV5-571:pvrV2.15:rvnAcer:rnAspireV5-571:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: Aspire V5-571 dmi.product.name: Aspire V5-571 dmi.product.sku: Aspire V5-571_072A_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1851385/+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 1860335] Re: Additional Drivers tab claims i8260 wifi card is not working
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- 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/1860335 Title: Additional Drivers tab claims i8260 wifi card is not working Status in software-properties package in Ubuntu: Confirmed Bug description: Recently upgraded to Focal, and despite having a stable, working wifi connection I see that the "Additional Drivers" tab of the GTK application shows that my wifi card is not working. Note there is only a single adapter in my laptop. From dmesg: [7.237957] iwlwifi :04:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208 From lspci: 04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) ProblemType: Bug 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 20 15:20:11 2020 InstallationDate: Installed on 2016-11-01 (1175 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-01-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1860335/+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 1860335] Re: Additional Drivers tab claims i8260 wifi card is not working
Confirmed also with an 8265. ** Changed in: software-properties (Ubuntu) Importance: Undecided => Medium -- 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/1860335 Title: Additional Drivers tab claims i8260 wifi card is not working Status in software-properties package in Ubuntu: Confirmed Bug description: Recently upgraded to Focal, and despite having a stable, working wifi connection I see that the "Additional Drivers" tab of the GTK application shows that my wifi card is not working. Note there is only a single adapter in my laptop. From dmesg: [7.237957] iwlwifi :04:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208 From lspci: 04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) ProblemType: Bug 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 20 15:20:11 2020 InstallationDate: Installed on 2016-11-01 (1175 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-01-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1860335/+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 1861472] Re: upgrade from fresh bionic to focal needlessly prompts user
** Patch added: "The proposed changes" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1861472/+attachment/5324364/+files/sshd_config.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1861472 Title: upgrade from fresh bionic to focal needlessly prompts user Status in openssh package in Ubuntu: New Bug description: Upgrading from a fresh 18.04 LTS install to focal unexpectedly prompts for how to handle a change to /etc/ssh/sshd_config To reproduce the issue: lxc launch ubuntu:18.04 u18 lxc exec u18 -- bash # within container do-release-upgrade -d # select restart services when prompted Eventually you'll be prompted to accept changes to /etc/ssh/sshd_config or not because of "local changes". Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.1p1-5 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Fri Jan 31 03:37:55 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: openssh UpgradeStatus: Upgraded to focal on 2020-01-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1861472/+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 1861472] [NEW] upgrade from fresh bionic to focal needlessly prompts user
Public bug reported: Upgrading from a fresh 18.04 LTS install to focal unexpectedly prompts for how to handle a change to /etc/ssh/sshd_config To reproduce the issue: lxc launch ubuntu:18.04 u18 lxc exec u18 -- bash # within container do-release-upgrade -d # select restart services when prompted Eventually you'll be prompted to accept changes to /etc/ssh/sshd_config or not because of "local changes". Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.1p1-5 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Fri Jan 31 03:37:55 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: openssh UpgradeStatus: Upgraded to focal on 2020-01-31 (0 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1861472 Title: upgrade from fresh bionic to focal needlessly prompts user Status in openssh package in Ubuntu: New Bug description: Upgrading from a fresh 18.04 LTS install to focal unexpectedly prompts for how to handle a change to /etc/ssh/sshd_config To reproduce the issue: lxc launch ubuntu:18.04 u18 lxc exec u18 -- bash # within container do-release-upgrade -d # select restart services when prompted Eventually you'll be prompted to accept changes to /etc/ssh/sshd_config or not because of "local changes". Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.1p1-5 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Fri Jan 31 03:37:55 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: openssh UpgradeStatus: Upgraded to focal on 2020-01-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1861472/+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 1861307] Re: [HP Laptop 14-bs0xx][HDA-Intel - HDA Intel PCH, playback] No sound at all
** Summary changed: - [HDA-Intel - HDA Intel PCH, playback] No sound at all + [HP Laptop 14-bs0xx][HDA-Intel - HDA Intel PCH, playback] No sound at all -- 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/1861307 Title: [HP Laptop 14-bs0xx][HDA-Intel - HDA Intel PCH, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: No sound at all in ubuntu 16.4 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-171.200-generic 4.4.203 Uname: Linux 4.4.0-171-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: andre 1507 F...m pulseaudio /dev/snd/pcmC0D0p: andre 1507 F...m pulseaudio /dev/snd/controlC0: andre 1507 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 29 11:18:59 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-atami161222-xenial-amd64-20170321-0 InstallationDate: Installed on 2019-05-16 (258 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20170321-07:27 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio Interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: andre 1507 F...m pulseaudio /dev/snd/pcmC0D0p: andre 1507 F...m pulseaudio /dev/snd/controlC0: andre 1507 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.44 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 831E dmi.board.vendor: HP dmi.board.version: 17.42 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.44:bd12/13/2018:svnHP:pnHPLaptop14-bs0xx:pvrType1ProductConfigId:rvnHP:rn831E:rvr17.42:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Laptop 14-bs0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861307/+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 1861363] Re: /etc/environment.d cannot be used to add to PATH
I've found out that `/etc/environment.d` is not intended for setting environment variables for login shells. From poettering at https://github.com/systemd/systemd/issues/12938: @dschepler is right. systemd-environment-d-generator gets run by systemd --user, and thus set environment variables for the systemd per- user service manager and their child processes only. Login shells (such as those started via getty on the console or ssh) are not children of systemd and hence the generators have no effect on them whatsoever. For login sessions use pam_env or some .profile script or similar to set env vars... Sorry. ** Bug watch added: github.com/systemd/systemd/issues #12938 https://github.com/systemd/systemd/issues/12938 ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1861363 Title: /etc/environment.d cannot be used to add to PATH Status in systemd package in Ubuntu: Invalid Bug description: I've added an executable file `/etc/environment.d/60-haskell.conf` with the following contents: PATH=/opt/ghc/bin:$PATH According to `man environment.d`, this is a proper procedure for altering the PATH variable via systemd. However, it does not work on Ubuntu. The PATH on reboot does not include `/opt/ghc/bin`. This is due to `/etc/profile` incorrectly overwriting the PATH according to comment #10 on https://github.com/systemd/systemd/issues/6414. There is a Debian bug at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=869144 that was prematurely closed because on the Debian side **because it was a Debian issue** rather than a systemd issue, which seems quite nonsensical. Perhaps that issue can be reopened or another can be opened. == Description:Ubuntu 18.04.3 LTS Release:18.04 systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.33 Version table: *** 237-3ubuntu10.33 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.33 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Jan 29 19:07:31 2020 InstallationDate: Installed on 2019-10-10 (111 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=111df9fc-1d42-47eb-82a6-3a80a0aba4c7 ro consoleblank=0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.1 dmi.sys.vendor: QEMU modified.conffile..etc.systemd.timesyncd.conf: [modified] mtime.conffile..etc.systemd.timesyncd.conf: 2019-10-10T02:35:05.488000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861363/+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 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
The simplest first test would be to try booting Ubuntu 20.04 from USB: http://cdimage.ubuntu.com/daily-live/current/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN 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.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/linux/+bug/1860754/+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 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
Most likely this is a kernel bug so the next step would be to try some newer or older kernels and see if any of them DO NOT have the same bug. Then hopefully we can identify when things changed. https://kernel.ubuntu.com/~kernel-ppa/mainline/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN 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.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/linux/+bug/1860754/+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 1857708] Re: Uses GNU awk specific option in bash completions, but gawk is not a dependency
Great, thanks! ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Jarno Suni (jarnos) ** Tags added: fixed-in-14.0 fixed-upstream -- 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/1857708 Title: Uses GNU awk specific option in bash completions, but gawk is not a dependency Status in pulseaudio package in Ubuntu: Triaged Bug description: The following command tells the files: grep awk $(dpkg-query -L pulseaudio | grep /usr/share/bash-completion/completions/) /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ Only pulseaudio is a regular file; other ones are symbolic links, so it is enough to modify the first one. gawk has -e option, but it is not installed by default at least in Xubuntu, so (very) old mawk may be used. Solution: Either use "awk --" instead of "awk -e" or use "gawk -e" and put gawk as dependency. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarnos 1200 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1200 F...m pulseaudio /dev/snd/controlC0: jarnos 1200 F pulseaudio /dev/snd/pcmC0D0p: jarnos 1200 F...m pulseaudio CurrentDesktop: XFCE Date: Fri Dec 27 18:44:55 2019 InstallationDate: Installed on 2019-12-05 (21 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1857708/+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 1861363] Re: /etc/environment.d cannot be used to add to PATH
To add to the issue, `/etc/environment` has one line setting `PATH` and throwing out any old versions of `PATH` (it doesn't contain `$PATH`). Changing that changed my `PATH` consistently on reboot: $ cat /etc/environment PATH="/opt/ghc/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games" $ printenv PATH /home/ubuntu/.cargo/bin:/home/ubuntu/bin:/opt/ghc/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin I tried adding a line to `/etc/environment.d/60-haskell.conf` setting `ZOMG=zomg`, but it wasn't picked up on reboot, so it appears that files in `/etc/environment.d` do nothing at all, not that they're just overwritten by `/etc/environment`. -- 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/1861363 Title: /etc/environment.d cannot be used to add to PATH Status in systemd package in Ubuntu: New Bug description: I've added an executable file `/etc/environment.d/60-haskell.conf` with the following contents: PATH=/opt/ghc/bin:$PATH According to `man environment.d`, this is a proper procedure for altering the PATH variable via systemd. However, it does not work on Ubuntu. The PATH on reboot does not include `/opt/ghc/bin`. This is due to `/etc/profile` incorrectly overwriting the PATH according to comment #10 on https://github.com/systemd/systemd/issues/6414. There is a Debian bug at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=869144 that was prematurely closed because on the Debian side **because it was a Debian issue** rather than a systemd issue, which seems quite nonsensical. Perhaps that issue can be reopened or another can be opened. == Description:Ubuntu 18.04.3 LTS Release:18.04 systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.33 Version table: *** 237-3ubuntu10.33 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.33 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Jan 29 19:07:31 2020 InstallationDate: Installed on 2019-10-10 (111 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=111df9fc-1d42-47eb-82a6-3a80a0aba4c7 ro consoleblank=0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.1 dmi.sys.vendor: QEMU modified.conffile..etc.systemd.timesyncd.conf: [modified] mtime.conffile..etc.systemd.timesyncd.conf: 2019-10-10T02:35:05.488000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861363/+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 1846988] Re: [Audio playback] No 'Speaker - Built-in Audio'
Hi there, the same device currently has ubuntu 19.10 and I have updates installed every 2-3 days. This is still an issue for my device, and currently I use a duel boot of windows to get audio (works fine) I intend to update to major releases when they drop (ie 20.04) when they become available. -- 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/1846988 Title: [Audio playback] No 'Speaker - Built-in Audio' Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Installation details: Ubuntu 19.04 alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://au.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://au.archive.ubuntu.com/ubuntu disco/main i386 Packages 100 /var/lib/dpkg/status Expected behaviour: Expected a 'Speaker - Built-in Audio' option in my Audio settings. Actual behaviour: Seems the 'Speakers - Built-in Audio' playback device is not available in my settings. Instead there is 'Headphones - Built-in Audio' which obviously shouldn't exist. When actual headphones are attached, the do not playback either. Playback only works when connected via bluetooth or HDMI, but there are extra options, that do not work... not sure what it is detecting, as there is only one HDMI output. I followed this document to debug myself: https://help.ubuntu.com/community/SoundTroubleshooting. However, the second step works fine when connected via bluetooth or HDMI, as stated before. I have tried booting the Live USB, and audio works perfectly fine here, so this is not a hardware issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lawrence 2033 F pulseaudio /dev/snd/controlC0: lawrence 2033 F pulseaudio lawrence 23649 F alsamixer /dev/snd/pcmC0D0c: lawrence 2033 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 09:27:18 2019 InstallationDate: Installed on 2019-09-07 (29 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lawrence 2033 F pulseaudio /dev/snd/controlC0: lawrence 2033 F pulseaudio lawrence 23649 F alsamixer Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06TMB dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: IT Channel Pty Ltd dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: IT Channel Pty Ltd dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06TMB:bd04/10/2019:svnITChannelPtyLtd:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnITChannelPtyLtd:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnITChannelPtyLtd:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: IT Channel Pty Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-09-07T11:50:26.934452 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846988/+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 1861363] Re: /etc/environment.d cannot be used to add to PATH
The issue you describe seems different from the upstream bug you referenced, could be worth opening another systemd upstream issue report? -- 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/1861363 Title: /etc/environment.d cannot be used to add to PATH Status in systemd package in Ubuntu: New Bug description: I've added an executable file `/etc/environment.d/60-haskell.conf` with the following contents: PATH=/opt/ghc/bin:$PATH According to `man environment.d`, this is a proper procedure for altering the PATH variable via systemd. However, it does not work on Ubuntu. The PATH on reboot does not include `/opt/ghc/bin`. This is due to `/etc/profile` incorrectly overwriting the PATH according to comment #10 on https://github.com/systemd/systemd/issues/6414. There is a Debian bug at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=869144 that was prematurely closed because on the Debian side **because it was a Debian issue** rather than a systemd issue, which seems quite nonsensical. Perhaps that issue can be reopened or another can be opened. == Description:Ubuntu 18.04.3 LTS Release:18.04 systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.33 Version table: *** 237-3ubuntu10.33 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.33 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Jan 29 19:07:31 2020 InstallationDate: Installed on 2019-10-10 (111 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=111df9fc-1d42-47eb-82a6-3a80a0aba4c7 ro consoleblank=0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.1 dmi.sys.vendor: QEMU modified.conffile..etc.systemd.timesyncd.conf: [modified] mtime.conffile..etc.systemd.timesyncd.conf: 2019-10-10T02:35:05.488000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861363/+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 1861446] Re: on focal 'ubuntu-bug linux' doesn't automatically collect kernel artifacts
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1861446 Title: on focal 'ubuntu-bug linux' doesn't automatically collect kernel artifacts Status in apport package in Ubuntu: New Bug description: Hello, on focal I ran 'ubuntu-bug linux' to report a kernel issue. The issue was filed against linux-signed-5.4 (Ubuntu) rather than linux (Ubuntu), and none of the logs usually included with kernel bug reports were included. After the bug was changed from linux-signed-5.4 to linux, I was prompted to run apport-collect by the kernel team's triagebot and that worked successfully: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861359/+activity My guess is that apport needs to be updated to understand a change in kernel packaging. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu16 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CrashReports: 640:1000:1000:40192:2020-01-30 03:32:41.717296496 +:2020-01-30 03:32:41.717296496 +:/var/crash/_usr_bin_apport-bug.1000.crash 600:0:0:467987:2020-01-24 20:40:35.855434497 +:2020-01-24 20:40:35.819434494 +:/var/crash/zfsutils-linux.0.crash 640:0:0:386063:2020-01-24 20:42:09.391725398 +:2020-01-24 20:42:08.887728256 +:/var/crash/_usr_sbin_zfs.0.crash Date: Thu Jan 30 18:44:47 2020 PackageArchitecture: all ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1861446/+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 1861363] Re: /etc/environment.d cannot be used to add to PATH
My `/etc/profile` doesn't seem to set the PATH, so the systemd bug
resolution may not be applicable:
$ grep PATH /etc/profile
$
I have Ubuntu 18.04 (Server, I assume) installed on a cloud server. I
access it only via SSH/Mosh and have no GUI (X or Wayland) installed as
far as I know.
I'm not sure in what order the PATH is set during boot, login, etc. All
I know is that `man environment.d` is incorrect when it says `PATH` can
be changed in a `.conf` file located in `/etc/environment.d`:
Example
Example 1. Setup environment to allow access to a program installed in
/opt/foo
/etc/environment.d/60-foo.conf:
FOO_DEBUG=force-software-gl,log-verbose
PATH=/opt/foo/bin:$PATH
LD_LIBRARY_PATH=/opt/foo/lib${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}
XDG_DATA_DIRS=/opt/foo/share:${XDG_DATA_DIRS:-/usr/local/share/:/usr/share/}
--
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/1861363
Title:
/etc/environment.d cannot be used to add to PATH
Status in systemd package in Ubuntu:
New
Bug description:
I've added an executable file `/etc/environment.d/60-haskell.conf`
with the following contents:
PATH=/opt/ghc/bin:$PATH
According to `man environment.d`, this is a proper procedure for
altering the PATH variable via systemd. However, it does not work on
Ubuntu. The PATH on reboot does not include `/opt/ghc/bin`.
This is due to `/etc/profile` incorrectly overwriting the PATH
according to comment #10 on
https://github.com/systemd/systemd/issues/6414.
There is a Debian bug at https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=869144 that was prematurely closed because on
the Debian side **because it was a Debian issue** rather than a
systemd issue, which seems quite nonsensical. Perhaps that issue can
be reopened or another can be opened.
==
Description:Ubuntu 18.04.3 LTS
Release:18.04
systemd:
Installed: 237-3ubuntu10.33
Candidate: 237-3ubuntu10.33
Version table:
*** 237-3ubuntu10.33 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
100 /var/lib/dpkg/status
237-3ubuntu10.29 500
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
237-3ubuntu10 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.33
ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
Uname: Linux 4.15.0-74-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
Date: Wed Jan 29 19:07:31 2020
InstallationDate: Installed on 2019-10-10 (111 days ago)
InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcEnviron:
TERM=screen
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic
root=UUID=111df9fc-1d42-47eb-82a6-3a80a0aba4c7 ro consoleblank=0
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-3.1
dmi.modalias:
dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-3.1
dmi.sys.vendor: QEMU
modified.conffile..etc.systemd.timesyncd.conf: [modified]
mtime.conffile..etc.systemd.timesyncd.conf: 2019-10-10T02:35:05.488000
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861363/+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 1861450] Re: `ubuntu-bug` claims that all packages on minimal cloud images are unofficial
*** This bug is a duplicate of bug 1775219 *** https://bugs.launchpad.net/bugs/1775219 This is because there are no indexes in /var/lib/apt/lists/, I'm going to mark this as a duplicate of bug 1775219. ** This bug has been marked a duplicate of bug 1775219 incorrectly reports package as unsupported if apt cache is empty -- 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/1861450 Title: `ubuntu-bug` claims that all packages on minimal cloud images are unofficial Status in apport package in Ubuntu: New Bug description: Steps to reproduce: 1) Install multipass. 2) `multipass launch http://cloud-images.ubuntu.com/minimal/daily/bionic/current/bionic-minimal-cloudimg-amd64.img -n reproducer` 3) `multipass shell reproducer` 4) `ubuntu-bug apport` (I also tried `ubuntu-bug cloud-init` and `ubuntu-bug wget`) Expected result: Be taken through the usual bug reporting flow. Actual result: *** Problem in wget The problem cannot be reported: This is not an official Ubuntu package. Please remove any third party package and try again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1861450/+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 1861440] Re: wget does not honor dot-prefixed domains in no_proxy env variable
Just another data point. I searched Debian packages and there is not an associated release impacted by this issue. Debian oldstable (stretch) ships wget 1.18 (pre-regression release). See https://packages.debian.org/stretch/wget Debian stable (buster) ships wget 1.20 (regression fixed release). See https://packages.debian.org/buster/wget ** Summary changed: - wget does not honor dot-prefixed domains in no_proxy env variable + [upstream regression] wget does not honor dot-prefixed domains in no_proxy env variable -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1861440 Title: [upstream regression] wget does not honor dot-prefixed domains in no_proxy env variable Status in wget package in Ubuntu: New Bug description: Traditionally (AFAIK for at least the last decade), tools that support the no_proxy environment variable support specifying an entire subdomain by prefixing it with a "dot". For example, to exclude any website under example.com from using the proxy, you would set no_proxy to .example.com (export no_proxy=.example.com). A regression in wget 1.19 changed this behavior to expect non-prefixed domains (example.com vs .example.com). This regression was ultimately fixed and released with the 1.20 release of wget. bionic includes the regressed behavior version of wget. The regression was apparently introduced in wget 1.19.3. This bug should not effect other Ubuntu releases (xenial contains 1.17.1 and both disco and eoan contain 1.20.x versions that have the upstream fix). For more details, see references below and my additional comments on the RHEL8 bug filed for this issue (RH bug 1763702 linked below). What happens: no_proxy=.example.com in bionic sends requests to the proxy server for URLs like http://www.example.com/ despite requesting proxy exception via no_proxy. What should happen: Request should bypass the proxy and go directly to the web server. (works in xenial, disco and eoan as expected). System/software information: $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 $ apt-cache policy wget wget: Installed: 1.19.4-1ubuntu2.2 Candidate: 1.19.4-1ubuntu2.2 Version table: *** 1.19.4-1ubuntu2.2 500 500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic-updates/main amd64 Packages 500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 1.19.4-1ubuntu2 500 500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic/main amd64 Packages References: * Upstream wget bug report: GNU Wget - Bugs: bug #53622 wget no_proxy leading dot on (sub)domains not working contradicting man page https://savannah.gnu.org/bugs/?53622 * Upstream commit reference that introduces the regression http://git.savannah.gnu.org/cgit/wget.git/commit/?id=fd85ac9cc623847e9d94d9f9241ab34e2c146cbf * Upstream commit reference that introduces the fix http://git.savannah.gnu.org/cgit/wget.git/commit/?id=fd85ac9cc623847e9d94d9f9241ab34e2c146cbf * Expected behavior of no_proxy as documented in the GNU Emacs manual: https://www.gnu.org/software/emacs/manual/html_node/url/Proxies.html * Red Hat Bugzilla entry for this issue (Reported against RHEL8.1) Bug 1763702 - wget is ignoring no_proxy environment variable https://bugzilla.redhat.com/show_bug.cgi?id=1763702 * Red Hat Bugzilla entry tracking the (now released) errata package for RHEL8.1 Bug 1772821 - wget is ignoring no_proxy environment variable [rhel-8.1.0.z] https://bugzilla.redhat.com/show_bug.cgi?id=1772821 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1861440/+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 1861450] [NEW] `ubuntu-bug` claims that all packages on minimal cloud images are unofficial
Public bug reported: Steps to reproduce: 1) Install multipass. 2) `multipass launch http://cloud-images.ubuntu.com/minimal/daily/bionic/current/bionic-minimal-cloudimg-amd64.img -n reproducer` 3) `multipass shell reproducer` 4) `ubuntu-bug apport` (I also tried `ubuntu-bug cloud-init` and `ubuntu-bug wget`) Expected result: Be taken through the usual bug reporting flow. Actual result: *** Problem in wget The problem cannot be reported: This is not an official Ubuntu package. Please remove any third party package and try again. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Summary changed: - `ubuntu-bug` claims that all packages on minimal images are unofficial + `ubuntu-bug` claims that all packages on minimal cloud images are unofficial -- 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/1861450 Title: `ubuntu-bug` claims that all packages on minimal cloud images are unofficial Status in apport package in Ubuntu: New Bug description: Steps to reproduce: 1) Install multipass. 2) `multipass launch http://cloud-images.ubuntu.com/minimal/daily/bionic/current/bionic-minimal-cloudimg-amd64.img -n reproducer` 3) `multipass shell reproducer` 4) `ubuntu-bug apport` (I also tried `ubuntu-bug cloud-init` and `ubuntu-bug wget`) Expected result: Be taken through the usual bug reporting flow. Actual result: *** Problem in wget The problem cannot be reported: This is not an official Ubuntu package. Please remove any third party package and try again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1861450/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861451] [NEW] apport's cloud-init-specific handling tracebacks on minimal cloud images
Public bug reported: Steps to reproduce: 1) Install multipass. 2) `multipass launch http://cloud-images.ubuntu.com/minimal/daily/bionic/current/bionic-minimal-cloudimg-amd64.img -n reproducer` 3) `multipass shell reproducer` 4) `ubuntu-bug cloud-init` Expected behaviour: Usual bug reporting flow (though, currently, I would really expect to see just the issue reported in bug 1861450). Actual behaviour: ERROR: hook /usr/share/apport/package-hooks/cloud-init.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/package-hooks/cloud-init.py", line 6, in add_info return cloudinit_add_info(report, ui) File "/usr/lib/python3/dist-packages/cloudinit/apport.py", line 123, in add_info attach_cloud_init_logs(report, ui) File "/usr/lib/python3/dist-packages/cloudinit/apport.py", line 57, in attach_cloud_init_logs 'cloud-init-output.log.txt': 'cat /var/log/cloud-init-output.log'}) File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 444, in attach_root_command_outputs sp = subprocess.Popen(_root_command_prefix() + [wrapper_path, script_path]) File "/usr/lib/python3.6/subprocess.py", line 729, in __init__ restore_signals, start_new_session) File "/usr/lib/python3.6/subprocess.py", line 1364, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'pkexec': 'pkexec' (As alluded to above, this also demonstrates bug 1861450 after the traceback is emitted.) ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1861451 Title: apport's cloud-init-specific handling tracebacks on minimal cloud images Status in apport package in Ubuntu: New Bug description: Steps to reproduce: 1) Install multipass. 2) `multipass launch http://cloud-images.ubuntu.com/minimal/daily/bionic/current/bionic-minimal-cloudimg-amd64.img -n reproducer` 3) `multipass shell reproducer` 4) `ubuntu-bug cloud-init` Expected behaviour: Usual bug reporting flow (though, currently, I would really expect to see just the issue reported in bug 1861450). Actual behaviour: ERROR: hook /usr/share/apport/package-hooks/cloud-init.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/package-hooks/cloud-init.py", line 6, in add_info return cloudinit_add_info(report, ui) File "/usr/lib/python3/dist-packages/cloudinit/apport.py", line 123, in add_info attach_cloud_init_logs(report, ui) File "/usr/lib/python3/dist-packages/cloudinit/apport.py", line 57, in attach_cloud_init_logs 'cloud-init-output.log.txt': 'cat /var/log/cloud-init-output.log'}) File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 444, in attach_root_command_outputs sp = subprocess.Popen(_root_command_prefix() + [wrapper_path, script_path]) File "/usr/lib/python3.6/subprocess.py", line 729, in __init__ restore_signals, start_new_session) File "/usr/lib/python3.6/subprocess.py", line 1364, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'pkexec': 'pkexec' (As alluded to above, this also demonstrates bug 1861450 after the traceback is emitted.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1861451/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
> 3. mtr ping test > --- > GoodSystem..0.0% Loss; 0.2 Avg; 0.1 Best, 0.9 Worst, 0.1 StdDev > BadSystem2...11.7% Loss; 0.1 Avg; 0.1 Best, 0.2 Worst, 0.0 StdDev The mtr packet loss is an interesting result. What mtr options did you use? Is this a UDP or ICMP test? -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card, possibly on a ubuntu driver??? Note, Dell have said there is
[Touch-packages] [Bug 1861446] [NEW] on focal 'ubuntu-bug linux' doesn't automatically collect kernel artifacts
Public bug reported: Hello, on focal I ran 'ubuntu-bug linux' to report a kernel issue. The issue was filed against linux-signed-5.4 (Ubuntu) rather than linux (Ubuntu), and none of the logs usually included with kernel bug reports were included. After the bug was changed from linux-signed-5.4 to linux, I was prompted to run apport-collect by the kernel team's triagebot and that worked successfully: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861359/+activity My guess is that apport needs to be updated to understand a change in kernel packaging. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu16 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CrashReports: 640:1000:1000:40192:2020-01-30 03:32:41.717296496 +:2020-01-30 03:32:41.717296496 +:/var/crash/_usr_bin_apport-bug.1000.crash 600:0:0:467987:2020-01-24 20:40:35.855434497 +:2020-01-24 20:40:35.819434494 +:/var/crash/zfsutils-linux.0.crash 640:0:0:386063:2020-01-24 20:42:09.391725398 +:2020-01-24 20:42:08.887728256 +:/var/crash/_usr_sbin_zfs.0.crash Date: Thu Jan 30 18:44:47 2020 PackageArchitecture: all ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) ** Affects: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1861446 Title: on focal 'ubuntu-bug linux' doesn't automatically collect kernel artifacts Status in apport package in Ubuntu: New Bug description: Hello, on focal I ran 'ubuntu-bug linux' to report a kernel issue. The issue was filed against linux-signed-5.4 (Ubuntu) rather than linux (Ubuntu), and none of the logs usually included with kernel bug reports were included. After the bug was changed from linux-signed-5.4 to linux, I was prompted to run apport-collect by the kernel team's triagebot and that worked successfully: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861359/+activity My guess is that apport needs to be updated to understand a change in kernel packaging. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu16 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CrashReports: 640:1000:1000:40192:2020-01-30 03:32:41.717296496 +:2020-01-30 03:32:41.717296496 +:/var/crash/_usr_bin_apport-bug.1000.crash 600:0:0:467987:2020-01-24 20:40:35.855434497 +:2020-01-24 20:40:35.819434494 +:/var/crash/zfsutils-linux.0.crash 640:0:0:386063:2020-01-24 20:42:09.391725398 +:2020-01-24 20:42:08.887728256 +:/var/crash/_usr_sbin_zfs.0.crash Date: Thu Jan 30 18:44:47 2020 PackageArchitecture: all ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1861446/+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 1860432] Re: juju agent fails to start on focal
** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Tags removed: 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/1860432 Title: juju agent fails to start on focal Status in juju: Fix Committed Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Focal: Confirmed Bug description: during bootstrap, add-machine, deploy Juju fails on Focal due to systemd not finding the service. ll /etc/systemd/system jujud-machine-1.service -> /lib/systemd/system/jujud-machine-1/jujud-machine-1.service which is linked and calls ExecStart=/lib/systemd/system/jujud-machine-1/exec-start.sh The fact that it's in a jujud-machine-1 folder vs /system itself appears to be causing systemd to not be able to run it. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1860432/+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 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
With respect to one of these situations, this is the following system: > Dell PowerEdge R440/0XP8V5, BIOS 2.2.11 06/14/2019 > > Note that a similar system does not have any issues: > > Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.3.4 11/08/2016 > > So the NIC in the "bad" environment is: > > BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet Controller (rev 01) > Product Name: Broadcom Adv. Dual 10G SFP+ Ethernet > > The NIC in the "good" environment is: > > Broadcom Inc. and subsidiaries NetXtreme II BCM57810 > 10 Gigabit Ethernet [14e4:1006] > Product Name: QLogic 57810 10 Gigabit Ethernet There are more than one variable at play here. Does the problem follow the NIC if you swap the NICs between systems? Are OS / kernel and driver versions the same on both systems? -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done!
[Touch-packages] [Bug 1861440] [NEW] wget does not honor dot-prefixed domains in no_proxy env variable
Public bug reported: Traditionally (AFAIK for at least the last decade), tools that support the no_proxy environment variable support specifying an entire subdomain by prefixing it with a "dot". For example, to exclude any website under example.com from using the proxy, you would set no_proxy to .example.com (export no_proxy=.example.com). A regression in wget 1.19 changed this behavior to expect non-prefixed domains (example.com vs .example.com). This regression was ultimately fixed and released with the 1.20 release of wget. bionic includes the regressed behavior version of wget. The regression was apparently introduced in wget 1.19.3. This bug should not effect other Ubuntu releases (xenial contains 1.17.1 and both disco and eoan contain 1.20.x versions that have the upstream fix). For more details, see references below and my additional comments on the RHEL8 bug filed for this issue (RH bug 1763702 linked below). What happens: no_proxy=.example.com in bionic sends requests to the proxy server for URLs like http://www.example.com/ despite requesting proxy exception via no_proxy. What should happen: Request should bypass the proxy and go directly to the web server. (works in xenial, disco and eoan as expected). System/software information: $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 $ apt-cache policy wget wget: Installed: 1.19.4-1ubuntu2.2 Candidate: 1.19.4-1ubuntu2.2 Version table: *** 1.19.4-1ubuntu2.2 500 500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic-updates/main amd64 Packages 500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 1.19.4-1ubuntu2 500 500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic/main amd64 Packages References: * Upstream wget bug report: GNU Wget - Bugs: bug #53622 wget no_proxy leading dot on (sub)domains not working contradicting man page https://savannah.gnu.org/bugs/?53622 * Upstream commit reference that introduces the regression http://git.savannah.gnu.org/cgit/wget.git/commit/?id=fd85ac9cc623847e9d94d9f9241ab34e2c146cbf * Upstream commit reference that introduces the fix http://git.savannah.gnu.org/cgit/wget.git/commit/?id=fd85ac9cc623847e9d94d9f9241ab34e2c146cbf * Expected behavior of no_proxy as documented in the GNU Emacs manual: https://www.gnu.org/software/emacs/manual/html_node/url/Proxies.html * Red Hat Bugzilla entry for this issue (Reported against RHEL8.1) Bug 1763702 - wget is ignoring no_proxy environment variable https://bugzilla.redhat.com/show_bug.cgi?id=1763702 * Red Hat Bugzilla entry tracking the (now released) errata package for RHEL8.1 Bug 1772821 - wget is ignoring no_proxy environment variable [rhel-8.1.0.z] https://bugzilla.redhat.com/show_bug.cgi?id=1772821 ** Affects: wget (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1861440 Title: wget does not honor dot-prefixed domains in no_proxy env variable Status in wget package in Ubuntu: New Bug description: Traditionally (AFAIK for at least the last decade), tools that support the no_proxy environment variable support specifying an entire subdomain by prefixing it with a "dot". For example, to exclude any website under example.com from using the proxy, you would set no_proxy to .example.com (export no_proxy=.example.com). A regression in wget 1.19 changed this behavior to expect non-prefixed domains (example.com vs .example.com). This regression was ultimately fixed and released with the 1.20 release of wget. bionic includes the regressed behavior version of wget. The regression was apparently introduced in wget 1.19.3. This bug should not effect other Ubuntu releases (xenial contains 1.17.1 and both disco and eoan contain 1.20.x versions that have the upstream fix). For more details, see references below and my additional comments on the RHEL8 bug filed for this issue (RH bug 1763702 linked below). What happens: no_proxy=.example.com in bionic sends requests to the proxy server for URLs like http://www.example.com/ despite requesting proxy exception via no_proxy. What should happen: Request should bypass the proxy and go directly to the web server. (works in xenial, disco and eoan as expected). System/software information: $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 $ apt-cache policy wget wget: Installed: 1.19.4-1ubuntu2.2 Candidate: 1.19.4-1ubuntu2.2 Version table: *** 1.19.4-1ubuntu2.2 500 500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic-updates/main amd64 Packages 500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 1.19.4-1ubuntu2
[Touch-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
Here is the Ettus benchmark tool https://kb.ettus.com/Verifying_the_Operation_of_the_USRP_Using_UHD_and_GNU_Radio You would need an Ettus device to run those tests. I cant test the affected node now as it is in production unfortunately. -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card, possibly on a ubuntu driver??? Note, Dell have said there is no hardware problem with the 10G interfaces I have
[Touch-packages] [Bug 1855009] Re: autopkgtests all fail on s390x
autopkgtests are now all skipped on s390. ** Tags removed: verification-needed ** Tags added: verification-done-eoan ** Tags removed: verification-needed-eoan -- 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/1855009 Title: autopkgtests all fail on s390x Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in network-manager source package in Bionic: Fix Committed Status in network-manager source package in Disco: Fix Committed Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] all autopkgtests fail on s390x [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/n/network- manager/20191130_001946_a5512@/log.gz autopkgtest [00:19:32]: summary wpa-dhclient FAIL non-zero exit status 1 nm.pyFAIL non-zero exit status 1 killswitches-no-urfkill FAIL non-zero exit status 1 urfkill-integration FAIL non-zero exit status 1 [regression potential] this essentially skips all the autopkgtests for network-manager on s390x, so regressions could occur now or in the future due to lack of testing on s390x. However, all the tests already fail on s390x and have since xenial (or earlier), so there hasn't been any useful test coverage on s390x before; this doesn't change that. [other info] as mentioned in comment 2, wireless networking is specifically excluded on s390 systems: menuconfig WIRELESS bool "Wireless" depends on !S390 default y The 'wpa-dhclient' test is specific to wireless, and both 'killswitches-no-urfkill' and 'urfkill-integration' require rfkill which requires wireless, so none of those tests are valid on s390x, since it doesn't have any wireless support. However the 'nm.py' test does have some test cases that don't rely on wireless capability, but it would be much more intrusive to update the test to split out wired vs. wireless testing, and that might introduce test regressions on other archs. The use case for network-manager on s390x in general is questionable, since s390x has no wireless support and obviously is never 'mobile', which are 2 main reasons to use network-manager instead of systemd-networkd. Additionally, all tests are currently skipped on armhf due to the requirement for machine isolation (and armhf tests run in containers), so s390x is not the first arch to simply skip all network-manager autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+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 1855183] Re: autopkgtest fails on i386 because linux-headers-generic no longer built for i386
eoan i386 autopkgtest skips urfkill tests, and all other tests pass. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan/eoan/i386/n/network- manager/20200130_131800_17227@/log.gz ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- 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/1855183 Title: autopkgtest fails on i386 because linux-headers-generic no longer built for i386 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] the kernel is no longer built for i386, starting with Eoan. However some of the autopkgtests depend on linux-headers-generic, which isn't available for i386, so the test fails with bad dependency. [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager/focal/i386 Broken autopkgtest-satdep:i386 Depends on linux-headers-generic:i386 < none @un H > Removing autopkgtest-satdep:i386 because I can't find linux-headers-generic:i386 [regression potential] test case fix only, regressions would involve more/continued test failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855183/+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 1861422] Re: packagekitd crashed with SIGSEGV
*** This bug is a duplicate of bug 1860855 *** https://bugs.launchpad.net/bugs/1860855 ** This bug has been marked a duplicate of bug 1860855 packagekitd crashed with SIGSEGV -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1861422 Title: packagekitd crashed with SIGSEGV Status in apt package in Ubuntu: New Bug description: I updated my focal system and rebooted. Shortly after logging in, I see that PackageKit crashed. Here is the systemctl log from the time that PackageKit started. Recording it here just in case it happens again. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: packagekit 1.1.13-2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Sat Jan 25 06:27:04 2020 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2019-09-11 (141 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: /usr/lib/packagekit/packagekitd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/sh Signal: 11 SourcePackage: packagekit StacktraceTop: () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 Title: packagekitd crashed with SIGSEGV UpgradeStatus: Upgraded to focal on 2020-01-17 (12 days ago) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1861422/+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 1859858] Re: udev has truncated ID_SERIAL value for scsi disk
** Tags removed: 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/1859858 Title: udev has truncated ID_SERIAL value for scsi disk Status in systemd package in Ubuntu: New Status in systemd source package in Focal: New Bug description: 1. root@ubuntu:/home/ubuntu# cat /etc/cloud/build.info build_name: server serial: 20200106 root@ubuntu:/home/ubuntu# lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 2. root@ubuntu:/home/ubuntu# apt-cache policy systemd systemd: Installed: 244-3ubuntu1 Candidate: 244-3ubuntu1 Version table: *** 244-3ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. ID_SERIAL value should be 322dc58dc023c7008 4. ID_SERIAL value is 3 -- Launching a qemu VM with the same extra scsi disk like so: -drive file=extra_disk_1.img,id=drv4,if=none,format=raw,index=4,cache=unsafe \ -device scsi-hd,drive=drv4,serial=0x22dc58dc023c7008,wwn=0x22dc58dc023c7008 On Focal udevadm info output: root@ubuntu:/home/ubuntu# udevadm info --query=property /dev/sdc DEVPATH=/devices/pci:00/:00:03.0/virtio0/host2/target2:0:2/2:0:2:0/block/sdc DEVNAME=/dev/sdc DEVTYPE=disk MAJOR=8 MINOR=32 SUBSYSTEM=block USEC_INITIALIZED=1497555 SCSI_TPGS=0 SCSI_TYPE=disk SCSI_VENDOR=QEMU SCSI_VENDOR_ENC=QEMU\x20\x20\x20\x20 SCSI_MODEL=QEMU_HARDDISK SCSI_MODEL_ENC=QEMU\x20HARDDISK\x20\x20\x20 SCSI_REVISION=2.5+ ID_SCSI=1 ID_SCSI_INQUIRY=1 ID_VENDOR=QEMU ID_VENDOR_ENC=QEMU\x20\x20\x20\x20 ID_MODEL=QEMU_HARDDISK ID_MODEL_ENC=QEMU\x20HARDDISK\x20\x20\x20 ID_REVISION=2.5+ ID_TYPE=disk SCSI_IDENT_SERIAL=0x22dc58dc023c7008 SCSI_IDENT_LUN_VENDOR=0x22dc58dc023c7008 SCSI_IDENT_LUN_NAA_EXT=22dc58dc023c7008 ID_WWN=0x22dc58dc023c7008 ID_WWN_WITH_EXTENSION=0x22dc58dc023c7008 ID_BUS=scsi ID_SERIAL=3 ID_SERIAL_SHORT=22dc58dc023c7008 MPATH_SBIN_PATH=/sbin DM_MULTIPATH_DEVICE_PATH=0 ID_PATH=pci-:00:03.0-scsi-0:0:2:0 ID_PATH_TAG=pci-_00_03_0-scsi-0_0_2_0 ID_FS_UUID=b20cf5c1-15ae-48a7-a5d9-dfcfd37df494 ID_FS_UUID_ENC=b20cf5c1-15ae-48a7-a5d9-dfcfd37df494 ID_FS_UUID_SUB=e06d861c-c6e2-497c-b14f-265ae37060e2 ID_FS_UUID_SUB_ENC=e06d861c-c6e2-497c-b14f-265ae37060e2 ID_FS_TYPE=btrfs ID_FS_USAGE=filesystem ID_BTRFS_READY=1 DEVLINKS=/dev/disk/by-id/scsi-3 /dev/disk/by-id/scsi-0QEMU_QEMU_HARDDISK_0x22dc58dc023c7008 /dev/disk/by-path/pci-:00:03.0-scsi-0:0:2:0 /dev/disk/by-id/wwn-0x22dc58dc023c7008 /dev/disk/by-id/scsi-SQEMU_QEMU_HARDDISK_0x22dc58dc023c7008 /dev/disk/by-uuid/b20cf5c1-15ae-48a7-a5d9-dfcfd37df494 /dev/disk/by-id/scsi-322dc58dc023c7008 TAGS=:systemd: On Bionic: root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20200112 root@ubuntu:~# lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 root@ubuntu:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.33 Version table: *** 237-3ubuntu10.33 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@ubuntu:~# udevadm info --query=property /dev/sdc DEVLINKS=/dev/disk/by-uuid/13a8a15f-4f6b-4904-b307-339b825c445b /dev/disk/by-path/pci-:00:03.0-scsi-0:0:2:0 /dev/disk/by-id/wwn-0x22dc58dc023c7008 /dev/disk/by-id/scsi-322dc58dc023c7008 DEVNAME=/dev/sdc DEVPATH=/devices/pci:00/:00:03.0/virtio0/host2/target2:0:2/2:0:2:0/block/sdc DEVTYPE=disk ID_BTRFS_READY=1 ID_BUS=scsi ID_FS_TYPE=btrfs ID_FS_USAGE=filesystem ID_FS_UUID=13a8a15f-4f6b-4904-b307-339b825c445b ID_FS_UUID_ENC=13a8a15f-4f6b-4904-b307-339b825c445b ID_FS_UUID_SUB=81178585-f7c0-429a-b02d-aeb2f245342c ID_FS_UUID_SUB_ENC=81178585-f7c0-429a-b02d-aeb2f245342c ID_MODEL=QEMU_HARDDISK ID_MODEL_ENC=QEMU\x20HARDDISK\x20\x20\x20 ID_PATH=pci-:00:03.0-scsi-0:0:2:0 ID_PATH_TAG=pci-_00_03_0-scsi-0_0_2_0 ID_REVISION=2.5+ ID_SCSI=1 ID_SCSI_SERIAL=0x22dc58dc023c7008 ID_SERIAL=322dc58dc023c7008 ID_SERIAL_SHORT=22dc58dc023c7008 ID_TYPE=disk ID_VENDOR=QEMU ID_VENDOR_ENC=QEMU\x20\x20\x20\x20 ID_WWN=0x22dc58dc023c7008 ID_WWN_WITH_EXTENSION=0x22dc58dc023c7008 MAJOR=8 MINOR=32 SUBSYSTEM=block TAGS=:systemd: USEC_INITIALIZED=2069797 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 244-3ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10 Uname: Linux 5.3.0-24-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
[Touch-packages] [Bug 1861422] Re: packagekitd crashed with SIGSEGV
it's segfaulting in libapt-pkg's code, reassigning to apt ** Package changed: packagekit (Ubuntu) => apt (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1861422 Title: packagekitd crashed with SIGSEGV Status in apt package in Ubuntu: New Bug description: I updated my focal system and rebooted. Shortly after logging in, I see that PackageKit crashed. Here is the systemctl log from the time that PackageKit started. Recording it here just in case it happens again. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: packagekit 1.1.13-2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Sat Jan 25 06:27:04 2020 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2019-09-11 (141 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: /usr/lib/packagekit/packagekitd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/sh Signal: 11 SourcePackage: packagekit StacktraceTop: () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 Title: packagekitd crashed with SIGSEGV UpgradeStatus: Upgraded to focal on 2020-01-17 (12 days ago) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1861422/+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 1860522] Re: Mesa 19.2.8 stable release
verified mesa on bionic, T470s with intel GPU ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1860522 Title: Mesa 19.2.8 stable release Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Eoan: Fix Released Bug description: [Impact] 19.10 released with mesa 19.2.1. We need the last point release of the 19.2.x series in eoan and backported for bionic. [Test case] Check on intel/radeon hw that things still work fine. [Regression potential] This is the last update of the series, all regressions should be shaken off at this point by upstream CI/community To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860522/+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 1861422] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1861422/+attachment/5324250/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1861422 Title: packagekitd crashed with SIGSEGV Status in packagekit package in Ubuntu: New Bug description: I updated my focal system and rebooted. Shortly after logging in, I see that PackageKit crashed. Here is the systemctl log from the time that PackageKit started. Recording it here just in case it happens again. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: packagekit 1.1.13-2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Sat Jan 25 06:27:04 2020 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2019-09-11 (141 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: /usr/lib/packagekit/packagekitd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/sh Signal: 11 SourcePackage: packagekit StacktraceTop: () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 Title: packagekitd crashed with SIGSEGV UpgradeStatus: Upgraded to focal on 2020-01-17 (12 days ago) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1861422/+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 1861422] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1861422/+attachment/5324252/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1861422/+attachment/5324239/+files/CoreDump.gz ** Changed in: packagekit (Ubuntu) Importance: Undecided => Medium ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1861422 Title: packagekitd crashed with SIGSEGV Status in packagekit package in Ubuntu: New Bug description: I updated my focal system and rebooted. Shortly after logging in, I see that PackageKit crashed. Here is the systemctl log from the time that PackageKit started. Recording it here just in case it happens again. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: packagekit 1.1.13-2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Sat Jan 25 06:27:04 2020 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2019-09-11 (141 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: /usr/lib/packagekit/packagekitd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/sh Signal: 11 SourcePackage: packagekit StacktraceTop: () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 Title: packagekitd crashed with SIGSEGV UpgradeStatus: Upgraded to focal on 2020-01-17 (12 days ago) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1861422/+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 1861422] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1861422/+attachment/5324251/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1861422 Title: packagekitd crashed with SIGSEGV Status in packagekit package in Ubuntu: New Bug description: I updated my focal system and rebooted. Shortly after logging in, I see that PackageKit crashed. Here is the systemctl log from the time that PackageKit started. Recording it here just in case it happens again. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: packagekit 1.1.13-2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Sat Jan 25 06:27:04 2020 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2019-09-11 (141 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: /usr/lib/packagekit/packagekitd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/sh Signal: 11 SourcePackage: packagekit StacktraceTop: () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 Title: packagekitd crashed with SIGSEGV UpgradeStatus: Upgraded to focal on 2020-01-17 (12 days ago) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1861422/+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 1861422] packagekitd crashed with SIGSEGV
StacktraceTop: pkgCacheGenerator::WriteStringInMap (String=..., this=0x7fa798c21240) at include/apt-pkg/string_view.h:111 pkgCacheGenerator::NewGroup (this=0x7fa798c21240, Grp=..., Name=...) at ../apt-pkg/pkgcachegen.cc:560 pkgCache::GrpIterator::GrpIterator (this=0x7fa798c21240) at include/apt-pkg/cacheiterators.h:135 debListParser::NewVersion (this=0x7fa784088400, Ver=...) at ../apt-pkg/deb/deblistparser.cc:214 pkgCacheGenerator::MergeListVersion (this=0x7fa784095900, List=..., Pkg=..., Version=..., OutVer=@0x7fa798c213b8: 0x0) at include/apt-pkg/cacheiterators.h:145 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1861422 Title: packagekitd crashed with SIGSEGV Status in packagekit package in Ubuntu: New Bug description: I updated my focal system and rebooted. Shortly after logging in, I see that PackageKit crashed. Here is the systemctl log from the time that PackageKit started. Recording it here just in case it happens again. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: packagekit 1.1.13-2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Sat Jan 25 06:27:04 2020 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2019-09-11 (141 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: /usr/lib/packagekit/packagekitd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/sh Signal: 11 SourcePackage: packagekit StacktraceTop: () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 Title: packagekitd crashed with SIGSEGV UpgradeStatus: Upgraded to focal on 2020-01-17 (12 days ago) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1861422/+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 1861422] [NEW] packagekitd crashed with SIGSEGV
Public bug reported: I updated my focal system and rebooted. Shortly after logging in, I see that PackageKit crashed. Here is the systemctl log from the time that PackageKit started. Recording it here just in case it happens again. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: packagekit 1.1.13-2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Sat Jan 25 06:27:04 2020 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2019-09-11 (141 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: /usr/lib/packagekit/packagekitd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/sh Signal: 11 SourcePackage: packagekit StacktraceTop: () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 Title: packagekitd crashed with SIGSEGV UpgradeStatus: Upgraded to focal on 2020-01-17 (12 days ago) UserGroups: separator: ** Affects: packagekit (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash focal ** Attachment added: "systemctl.log" https://bugs.launchpad.net/bugs/1861422/+attachment/5324238/+files/systemctl.log ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1861422 Title: packagekitd crashed with SIGSEGV Status in packagekit package in Ubuntu: New Bug description: I updated my focal system and rebooted. Shortly after logging in, I see that PackageKit crashed. Here is the systemctl log from the time that PackageKit started. Recording it here just in case it happens again. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: packagekit 1.1.13-2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Sat Jan 25 06:27:04 2020 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2019-09-11 (141 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: /usr/lib/packagekit/packagekitd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/sh Signal: 11 SourcePackage: packagekit StacktraceTop: () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 () at /lib/x86_64-linux-gnu/libapt-pkg.so.5.90 Title: packagekitd crashed with SIGSEGV UpgradeStatus: Upgraded to focal on 2020-01-17 (12 days ago) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1861422/+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 1860540] Re: network password entry has no way of displaying what you type
Thank you for the bug report, you should be able to find an item to show the password in the right click menu, that's not obvious though which is reported upstream on https://gitlab.gnome.org/GNOME/gnome- shell/issues/1022 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1022 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1022 ** Package changed: ubuntu-meta (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1860540 Title: network password entry has no way of displaying what you type Status in gnome-shell package in Ubuntu: New Bug description: In Focal the network password / passphrase entry form has no way of displaying what is being typed. I'd expect a checkbox or something... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.442 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CasperVersion: 1.438 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 11:13:41 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860540/+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 1861177] Re: seccomp_rule_add is very slow
I'll take a look at measuring this with snapd $SOON ** Changed in: snapd Assignee: (unassigned) => Ian Johnson (anonymouse67) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1861177 Title: seccomp_rule_add is very slow Status in snapd: Triaged Status in libseccomp package in Ubuntu: Triaged Bug description: There is a known and patched issue with version 2.4 of libseccomp where certain operations have a large performance regression. This is causing some packages that use libseccomp such as container orchestration systems to occasionally time out or otherwise fail under certain workloads. Please consider porting the patch into the various Ubuntu versions that have version 2.4 of libseccomp and into the backports. The performance patch from version 2.5 (yet to be released) applies cleanly on top of the 2.4 branch of libseccomp. For more information, and for a copy of the patch (which can also be cherry picked from the upstream libseccomp repos) see the similar Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1861177/+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 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
Hi Daniel, What should I do for this issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN 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.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/linux/+bug/1860754/+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 1861082] Re: ubuntu-bug doesn't know how to file bugs against snaps
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1861082 Title: ubuntu-bug doesn't know how to file bugs against snaps Status in apport package in Ubuntu: Confirmed Bug description: Hello, I had problems with subiquity in the focal live server install image. I tried to use 'ubuntu-bug subiquity' to report the bug, but ubuntu-bug apparently cannot file bug reports against snaps. This is frustrating that users need to know which portions of Ubuntu are delivered via debs, which portions are delivered by snaps, and try to find a way to report bugs correctly. ubuntu-bug should know how to report bugs for Canonical software. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1861082/+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 123920] Re: Bluetooth Logitech Dinovo Keyboard/Mouse don't work
Yes. My hardware is still working as well as the day I got it. I only charge it rarely, maybe once every other month. I always turn it off when not in use and don't leave it attached to the charging base. Maybe that helped the longevity, or maybe i just got lucky. > On January 28, 2020 at 10:36 PM Rob Bruce <123...@bugs.launchpad.net> wrote: > > > It seems a shame that my affected hardware didn't live to see this day > :( If it had held on another year and a half, I would've been able to > test this out. Glad Martin's was still working to check it out over > _eleven years_ (!) after he first commented on this issue! > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/123920 > > Title: > Bluetooth Logitech Dinovo Keyboard/Mouse don't work > > To manage notifications about this bug go to: > https://bugs.launchpad.net/bluez-utils-old/+bug/123920/+subscriptions "Don't fear the penguin" Dr. Martin G. Miller mgmil...@optonline.net -- 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/123920 Title: Bluetooth Logitech Dinovo Keyboard/Mouse don't work Status in Bluez-utils: New Status in Linux Mint: Invalid Status in Unity: Invalid Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-source-2.6.22 package in Ubuntu: Won't Fix Status in udev package in Ubuntu: Invalid Bug description: Testing Gutsy Gibbon Tribe 2 LiveCD and bluetooth keyboard and mouse will work until Nautilus starts. After Nautilus starts the keyboard and mouse are unresponsive and do not work. I tried reconnecting the keyboard and mouse by using the discovery buttons on both the Bluetooth Dongle and Input device. The problem still persists. Using Intel P4 2.8 Ghz Processor, 3 GB ddr400 ram, Intel D875PBZ motherboard. Logitech Dinovo media keyboard and mx1000 laser bluetooth mouse, with logitech mini bluetooth receiver. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez-utils-old/+bug/123920/+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 1856560] Re: ds-identify - stuck in uninterruptible sleep state
Here is the output of `ls -latr /proc//fd` root 3377 0.0 0.0 11980 3352 ?DJan24 0:00 blkid -c /dev/null -o export root 6293 0.0 0.0 11980 3316 ?DJan24 0:00 blkid -c /dev/null -o export root 10422 0.0 0.0 11980 3556 ?DJan26 0:00 blkid -c /dev/null -o export root 13020 0.0 0.0 11980 3492 ?DJan24 0:00 blkid -c /dev/null -o export root 13192 0.0 0.0 11980 3752 ?DJan26 0:00 blkid -c /dev/null -o export root 15494 0.0 0.0 11980 3704 ?DJan27 0:00 blkid -c /dev/null -o export root 15506 0.0 0.0 11212 2532 ?DJan23 0:00 blkid -c /dev/null -o export root 15630 0.0 0.0 11980 3456 ?DJan24 0:00 blkid -c /dev/null -o export root 15768 0.0 0.0 11980 3700 ?DJan26 0:00 blkid -c /dev/null -o export root 16282 0.0 0.0 11980 3704 ?DJan27 0:00 blkid -c /dev/null -o export root 18328 0.0 0.0 11980 3616 ?DJan27 0:00 blkid -c /dev/null -o export root 18364 0.0 0.0 11980 3432 ?DJan23 0:00 blkid -c /dev/null -o export root 18549 0.0 0.0 11980 3324 ?DJan24 0:00 blkid -c /dev/null -o export root 18755 0.0 0.0 11980 3620 ?DJan26 0:00 blkid -c /dev/null -o export root 19266 0.0 0.0 11980 3556 ?DJan27 0:00 blkid -c /dev/null -o export root 20480 0.0 0.0 11980 3616 ?DJan26 0:00 blkid -c /dev/null -o export root 21131 0.0 0.0 11980 3504 ?DJan23 0:00 blkid -c /dev/null -o export root 21149 0.0 0.0 11980 3636 ?DJan27 0:00 blkid -c /dev/null -o export root 21378 0.0 0.0 11980 3180 ?DJan24 0:00 blkid -c /dev/null -o export root 21927 0.0 0.0 11980 3624 ?DJan27 0:00 blkid -c /dev/null -o export root 23165 0.0 0.0 11980 3704 ?DJan26 0:00 blkid -c /dev/null -o export root 23795 0.0 0.0 11980 3616 ?DJan27 0:00 blkid -c /dev/null -o export root 23911 0.0 0.0 11980 3456 ?DJan23 0:00 blkid -c /dev/null -o export root 24554 0.0 0.0 11980 3592 ?DJan27 0:00 blkid -c /dev/null -o export root 25672 0.0 0.0 11980 3752 ?DJan26 0:00 blkid -c /dev/null -o export root 28344 0.0 0.0 11980 3704 ?DJan26 0:00 blkid -c /dev/null -o export root 30382 0.0 0.0 11980 3216 ?DJan24 0:00 blkid -c /dev/null -o export dr-xr-xr-x 9 root root 0 Jan 30 06:29 .. lr-x-- 1 root root 64 Jan 30 15:22 4 -> /proc/partitions l-wx-- 1 root root 64 Jan 30 15:22 3 -> /run/cloud-init/ds-identify.log lrwx-- 1 root root 64 Jan 30 15:22 2 -> /dev/null l-wx-- 1 root root 64 Jan 30 15:22 1 -> 'pipe:[399588299]' lrwx-- 1 root root 64 Jan 30 15:22 0 -> /dev/null dr-x-- 2 root root 0 Jan 30 15:22 . root@ubuntuapp02:/# ls -latr /proc/23795/fd total 0 dr-xr-xr-x 9 root root 0 Jan 30 06:29 .. lr-x-- 1 root root 64 Jan 30 15:23 4 -> /proc/partitions l-wx-- 1 root root 64 Jan 30 15:23 3 -> /run/cloud-init/ds-identify.log lrwx-- 1 root root 64 Jan 30 15:23 2 -> /dev/null l-wx-- 1 root root 64 Jan 30 15:23 1 -> 'pipe:[415355377]' lrwx-- 1 root root 64 Jan 30 15:23 0 -> /dev/null dr-x-- 2 root root 0 Jan 30 15:23 . -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1856560 Title: ds-identify - stuck in uninterruptible sleep state Status in cloud-init: Invalid Status in util-linux package in Ubuntu: New Bug description: We got recurring issues with the cloud-init/ds-identify process. It spawns sub-processes "blkid -c /dev/null -o export" which gets stuck in the "D" uninterruptible sleep state. The processes cannot be killed, so the only solution is to reboot the affected server. root 3839 0.0 0.0 4760 1840 ? S Dec05 0:00 /bin/sh /usr/lib/cloud-init/ds-identify root 3844 0.0 0.0 11212 2836 ? D Dec05 0:00 \_ blkid -c /dev/null -o export root 6943 0.0 0.0 4760 1880 ? S Dec05 0:00 /bin/sh /usr/lib/cloud-init/ds-identify root 6948 0.0 0.0 11212 2844 ? D Dec05 0:00 \_ blkid -c /dev/null -o export root 6111 0.0 0.0 4760 1916 ? S Dec12 0:00 /bin/sh /usr/lib/cloud-init/ds-identify root 6149 0.0 0.0 11212 2940 ? D Dec12 0:00 \_ blkid -c /dev/null -o export root 8765 0.0 0.3 926528 24968 ? Ssl Dec12 0:12 /usr/lib/snapd/snapd root 9179 0.0 0.0 4760 1892 ? S Dec12 0:00 /bin/sh /usr/lib/cloud-init/ds-identify root 9185 0.0 0.0 11980 3552 ? D Dec12 0:00 \_ blkid -c /dev/null -o export Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To
[Touch-packages] [Bug 1311056] Re: apt-add-repository adds duplicate commented/disabled source lines
** Description changed: + Impact + == + + Under most circumstances, the impact is minimal (a few extra redundant + comment lines in apt sources. However, if users are automating source + removal / addition on a machine (as in comment 11), there is the + potential to wind up with an excessively large (and thus slow to parse) + apt sources configuration. + + Test Case + = + + * sudo add-apt-repository -y ppa:deadsnakes/ppa + * cat /etc/apt/sources.list.d/deadsnakes*.list + * Note the presence of one uncommented "deb" line, and one commented "deb-src" line + * sudo add-apt-repository -y ppa:deadsnakes/ppa + * cat /etc/apt/sources.list.d/deadsnakes*.list + * Note the uncommented "deb" line is still there but the commented "deb-src" line has now been duplicated + * Upgrade python-apt to 1.9.3ubuntu2 (or later) + * sudo add-apt-repository -y ppa:deadsnakes/ppa + * cat /etc/apt/sources.list.d/deadsnakes*.list + * Note there has been no further duplication of the commented "deb-src" line + + Regression Potential + + + Minimal; test cases have been added to cover the duplication case, and + to cover the enabling of sources (which was not covered by existing + tests, but was part of the code altered to fix the duplication case), + and insertion of sources at a position (again, not covered by existing + tests but modified as part of the fix). The test case has been used + successfully on all targeted releases (xenial, bionic, and eoan). + + Original Description + + Trusty Tahr 14.04 - 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list + 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y ppa:aims/aims-desktop gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d# That deb-src line should have stayed commented out, and not been duplicated. (Commented deb lines should of course be uncommented, as already fixed per https://bugs.launchpad.net/ubuntu/+source/python- apt/+bug/1042916 .) ** Summary changed: - apt-add-repository adds duplicate commented/disabled source lines + [SRU] apt-add-repository adds duplicate commented/disabled source lines ** Description changed: Impact == Under most circumstances, the impact is minimal (a few extra redundant comment lines in apt sources. However, if users are automating source removal / addition on a machine (as in comment 11), there is the potential to wind up with an excessively large (and thus slow to parse) apt sources configuration. Test Case = * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the presence of one uncommented "deb" line, and one commented "deb-src" line * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the uncommented "deb" line is still there but the commented "deb-src" line has now been duplicated - * Upgrade python-apt to 1.9.3ubuntu2 (or later) + * sudo add-apt-repository ppa:waveform/python-apt + * sudo apt upgrade # update python-apt to fixed version * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note there has been no further duplication of the commented "deb-src" line Regression Potential Minimal; test cases have been added to cover the duplication case, and to cover the enabling of sources (which was not covered by existing tests, but was part of the code altered to fix the duplication case), and insertion of sources at a position (again, not covered by existing tests but modified as part of the fix). The test case has been used successfully on all targeted releases (xenial, bionic, and eoan). Original Description Trusty Tahr 14.04 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d#apt-add-repository
[Touch-packages] [Bug 1855009] Re: autopkgtests all fail on s390x
Hello Dan, or anyone else affected, Accepted network-manager into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.20.4-2ubuntu2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. 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. ** Tags removed: verification-done verification-done-eoan ** Tags added: verification-needed verification-needed-eoan -- 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/1855009 Title: autopkgtests all fail on s390x Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in network-manager source package in Bionic: Fix Committed Status in network-manager source package in Disco: Fix Committed Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] all autopkgtests fail on s390x [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/n/network- manager/20191130_001946_a5512@/log.gz autopkgtest [00:19:32]: summary wpa-dhclient FAIL non-zero exit status 1 nm.pyFAIL non-zero exit status 1 killswitches-no-urfkill FAIL non-zero exit status 1 urfkill-integration FAIL non-zero exit status 1 [regression potential] this essentially skips all the autopkgtests for network-manager on s390x, so regressions could occur now or in the future due to lack of testing on s390x. However, all the tests already fail on s390x and have since xenial (or earlier), so there hasn't been any useful test coverage on s390x before; this doesn't change that. [other info] as mentioned in comment 2, wireless networking is specifically excluded on s390 systems: menuconfig WIRELESS bool "Wireless" depends on !S390 default y The 'wpa-dhclient' test is specific to wireless, and both 'killswitches-no-urfkill' and 'urfkill-integration' require rfkill which requires wireless, so none of those tests are valid on s390x, since it doesn't have any wireless support. However the 'nm.py' test does have some test cases that don't rely on wireless capability, but it would be much more intrusive to update the test to split out wired vs. wireless testing, and that might introduce test regressions on other archs. The use case for network-manager on s390x in general is questionable, since s390x has no wireless support and obviously is never 'mobile', which are 2 main reasons to use network-manager instead of systemd-networkd. Additionally, all tests are currently skipped on armhf due to the requirement for machine isolation (and armhf tests run in containers), so s390x is not the first arch to simply skip all network-manager autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+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 1858092] Re: Network Manager not saving OpenVPN password
Hello Duarte, or anyone else affected, Accepted network-manager into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.20.4-2ubuntu2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. 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: network-manager (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+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 1855183] Re: autopkgtest fails on i386 because linux-headers-generic no longer built for i386
Hello Dan, or anyone else affected, Accepted network-manager into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.20.4-2ubuntu2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. 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. ** Tags removed: verification-done verification-done-eoan ** Tags added: verification-needed verification-needed-eoan -- 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/1855183 Title: autopkgtest fails on i386 because linux-headers-generic no longer built for i386 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] the kernel is no longer built for i386, starting with Eoan. However some of the autopkgtests depend on linux-headers-generic, which isn't available for i386, so the test fails with bad dependency. [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager/focal/i386 Broken autopkgtest-satdep:i386 Depends on linux-headers-generic:i386 < none @un H > Removing autopkgtest-satdep:i386 because I can't find linux-headers-generic:i386 [regression potential] test case fix only, regressions would involve more/continued test failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855183/+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 1855009] Re: autopkgtests all fail on s390x
** Tags removed: block-proposed-eoan -- 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/1855009 Title: autopkgtests all fail on s390x Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in network-manager source package in Bionic: Fix Committed Status in network-manager source package in Disco: Fix Committed Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] all autopkgtests fail on s390x [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/n/network- manager/20191130_001946_a5512@/log.gz autopkgtest [00:19:32]: summary wpa-dhclient FAIL non-zero exit status 1 nm.pyFAIL non-zero exit status 1 killswitches-no-urfkill FAIL non-zero exit status 1 urfkill-integration FAIL non-zero exit status 1 [regression potential] this essentially skips all the autopkgtests for network-manager on s390x, so regressions could occur now or in the future due to lack of testing on s390x. However, all the tests already fail on s390x and have since xenial (or earlier), so there hasn't been any useful test coverage on s390x before; this doesn't change that. [other info] as mentioned in comment 2, wireless networking is specifically excluded on s390 systems: menuconfig WIRELESS bool "Wireless" depends on !S390 default y The 'wpa-dhclient' test is specific to wireless, and both 'killswitches-no-urfkill' and 'urfkill-integration' require rfkill which requires wireless, so none of those tests are valid on s390x, since it doesn't have any wireless support. However the 'nm.py' test does have some test cases that don't rely on wireless capability, but it would be much more intrusive to update the test to split out wired vs. wireless testing, and that might introduce test regressions on other archs. The use case for network-manager on s390x in general is questionable, since s390x has no wireless support and obviously is never 'mobile', which are 2 main reasons to use network-manager instead of systemd-networkd. Additionally, all tests are currently skipped on armhf due to the requirement for machine isolation (and armhf tests run in containers), so s390x is not the first arch to simply skip all network-manager autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+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 1855183] Re: autopkgtest fails on i386 because linux-headers-generic no longer built for i386
** Tags removed: block-proposed-eoan -- 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/1855183 Title: autopkgtest fails on i386 because linux-headers-generic no longer built for i386 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] the kernel is no longer built for i386, starting with Eoan. However some of the autopkgtests depend on linux-headers-generic, which isn't available for i386, so the test fails with bad dependency. [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager/focal/i386 Broken autopkgtest-satdep:i386 Depends on linux-headers-generic:i386 < none @un H > Removing autopkgtest-satdep:i386 because I can't find linux-headers-generic:i386 [regression potential] test case fix only, regressions would involve more/continued test failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855183/+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 1861247] Re: Evince: Wrong font and wrong line height in PDF view
Thank you for your bug report. The rendering is done by poppler so probably an issue there, could you maybe also report it upstream on https://gitlab.freedesktop.org/poppler/poppler/issues ? ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Package changed: evince (Ubuntu) => poppler (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1861247 Title: Evince: Wrong font and wrong line height in PDF view Status in poppler package in Ubuntu: New Bug description: The attached pdf file is generated using Spyder 4, a Python IDE. The file contains embeded fonts UbuntuMono Regular and UbuntuMono Bold. When open with Evince, it seems using wrong font, and the line height is not correct. The file looks OK when open with other PDF viewer such as Firefox. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 29 11:53:43 2020 InstallationDate: Installed on 2019-12-14 (45 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1861247/+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 1861322] Re: PPTP VPN doesn't work out of the box - nf_conntrack_pptp missing
Thank you for your bug report. Is that issue new to focal? Could you add
a 'journalctl -b 0' log after triggering the error?
The code does
char *conntrack_module[] = { "/sbin/modprobe", "nf_conntrack_pptp",
NULL };
if (!g_spawn_sync (NULL, conntrack_module, NULL, 0, NULL, NULL, NULL,
NULL, NULL, )) {
_LOGW ("modprobing nf_conntrack_pptp failed: %s",
error->message);
so it should either load the module or print an error...
** Package changed: network-manager (Ubuntu) => network-manager-pptp
(Ubuntu)
** Changed in: network-manager-pptp (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/1861322
Title:
PPTP VPN doesn't work out of the box - nf_conntrack_pptp missing
Status in network-manager-pptp package in Ubuntu:
Incomplete
Bug description:
PPTP based VPN doesn't work out of the box on Focal Fossa. From
syslog:
Jan 29 19:41:35 thinkpad pppd[8734]: Plugin
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Jan 29 19:41:35 thinkpad NetworkManager[8734]: Plugin
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Jan 29 19:41:35 thinkpad pptp[8739]: nm-pptp-service-8722
log[main:pptp.c:353]: The synchronous pptp option is NOT activated
Jan 29 19:41:35 thinkpad pptp[8750]: nm-pptp-service-8722
log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 1
'Start-Control-Connection-Request'
Jan 29 19:41:35 thinkpad pptp[8750]: nm-pptp-service-8722
log[ctrlp_disp:pptp_ctrl.c:781]: Received Start Control Connection Reply
Jan 29 19:41:35 thinkpad pptp[8750]: nm-pptp-service-8722
log[ctrlp_disp:pptp_ctrl.c:815]: Client connection established.
Jan 29 19:41:36 thinkpad pptp[8750]: nm-pptp-service-8722
log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 7
'Outgoing-Call-Request'
Jan 29 19:41:36 thinkpad pptp[8750]: nm-pptp-service-8722
log[ctrlp_disp:pptp_ctrl.c:900]: Received Outgoing Call Reply.
Jan 29 19:41:36 thinkpad pptp[8750]: nm-pptp-service-8722
log[ctrlp_disp:pptp_ctrl.c:938]: Outgoing call established (call ID 44616,
peer's call ID 0).
Jan 29 19:42:03 thinkpad pptp[8750]: nm-pptp-service-8722
log[ctrlp_disp:pptp_ctrl.c:976]: Call disconnect notification received (call id
44616)
Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722
log[logecho:pptp_ctrl.c:719]: Echo Request received.
Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722
log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 6 'Echo-Reply'
Jan 29 19:42:06 thinkpad pptp[8739]: nm-pptp-service-8722
warn[decaps_hdlc:pptp_gre.c:226]: short read (-1): Input/output error
Jan 29 19:42:06 thinkpad pptp[8739]: nm-pptp-service-8722
warn[decaps_hdlc:pptp_gre.c:238]: pppd may have shutdown, see pppd log
Jan 29 19:42:06 thinkpad pppd[8734]: Child process /usr/sbin/pptp
161.53.xxx.yyy --nolaunchpppd --loglevel 0 --logstring nm-pptp-service-8722
(pid 8737) terminated with signal 15
Jan 29 19:42:06 thinkpad NetworkManager[8734]: Child process /usr/sbin/pptp
161.53.xxx.yyy --nolaunchpppd --loglevel 0 --logstring nm-pptp-service-8722
(pid 8737) terminated with signal 15
Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722
log[callmgr_main:pptp_callmgr.c:245]: Closing connection (unhandled)
Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722
log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 12
'Call-Clear-Request'
Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722
log[call_callback:pptp_callmgr.c:84]: Closing connection (call state)
Once nf_conntrack_pptp kernel module is loaded, VPN connection
succeeds:
Jan 29 19:44:02 thinkpad pppd[10166]: Plugin
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Jan 29 19:44:02 thinkpad NetworkManager[10166]: Plugin
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Jan 29 19:44:02 thinkpad pptp[10170]: nm-pptp-service-10156
log[main:pptp.c:353]: The synchronous pptp option is NOT activated
Jan 29 19:44:02 thinkpad pptp[10183]: nm-pptp-service-10156
log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 1
'Start-Control-Connection-Request'
Jan 29 19:44:02 thinkpad pptp[10183]: nm-pptp-service-10156
log[ctrlp_disp:pptp_ctrl.c:781]: Received Start Control Connection Reply
Jan 29 19:44:02 thinkpad pptp[10183]: nm-pptp-service-10156
log[ctrlp_disp:pptp_ctrl.c:815]: Client connection established.
Jan 29 19:44:03 thinkpad pptp[10183]: nm-pptp-service-10156
log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 7
'Outgoing-Call-Request'
Jan 29 19:44:03 thinkpad pptp[10183]: nm-pptp-service-10156
log[ctrlp_disp:pptp_ctrl.c:900]: Received Outgoing Call Reply.
Jan 29 19:44:03 thinkpad pptp[10183]: nm-pptp-service-10156
log[ctrlp_disp:pptp_ctrl.c:938]: Outgoing call established (call ID 61223,
peer's call ID 0).
To manage notifications about this bug go to:
[Touch-packages] [Bug 1861247] [NEW] Evince: Wrong font and wrong line height in PDF view
You have been subscribed to a public bug: The attached pdf file is generated using Spyder 4, a Python IDE. The file contains embeded fonts UbuntuMono Regular and UbuntuMono Bold. When open with Evince, it seems using wrong font, and the line height is not correct. The file looks OK when open with other PDF viewer such as Firefox. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 29 11:53:43 2020 InstallationDate: Installed on 2019-12-14 (45 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: poppler (Ubuntu) Importance: Low Status: New ** Tags: amd64 apparmor apport-bug bionic -- Evince: Wrong font and wrong line height in PDF view https://bugs.launchpad.net/bugs/1861247 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler 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 1861363] Re: /etc/environment.d cannot be used to add to PATH
Thank you for your bug report. In what session is the issue happening? The upstream comments suggest it's wayland session specific? Also how is /etc/profile setting up PATH for you? ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- 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/1861363 Title: /etc/environment.d cannot be used to add to PATH Status in systemd package in Ubuntu: New Bug description: I've added an executable file `/etc/environment.d/60-haskell.conf` with the following contents: PATH=/opt/ghc/bin:$PATH According to `man environment.d`, this is a proper procedure for altering the PATH variable via systemd. However, it does not work on Ubuntu. The PATH on reboot does not include `/opt/ghc/bin`. This is due to `/etc/profile` incorrectly overwriting the PATH according to comment #10 on https://github.com/systemd/systemd/issues/6414. There is a Debian bug at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=869144 that was prematurely closed because on the Debian side **because it was a Debian issue** rather than a systemd issue, which seems quite nonsensical. Perhaps that issue can be reopened or another can be opened. == Description:Ubuntu 18.04.3 LTS Release:18.04 systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.33 Version table: *** 237-3ubuntu10.33 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.33 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Jan 29 19:07:31 2020 InstallationDate: Installed on 2019-10-10 (111 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=111df9fc-1d42-47eb-82a6-3a80a0aba4c7 ro consoleblank=0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.1 dmi.sys.vendor: QEMU modified.conffile..etc.systemd.timesyncd.conf: [modified] mtime.conffile..etc.systemd.timesyncd.conf: 2019-10-10T02:35:05.488000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861363/+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 1861364] Re: /etc/environment.d cannot be used to add to PATH
*** This bug is a duplicate of bug 1861363 *** https://bugs.launchpad.net/bugs/1861363 ** This bug has been marked a duplicate of bug 1861363 /etc/environment.d cannot be used to add to PATH -- 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/1861364 Title: /etc/environment.d cannot be used to add to PATH Status in systemd: Fix Released Status in systemd package in Ubuntu: New Bug description: I've added an executable file `/etc/environment.d/60-haskell.conf` with the following contents: PATH=/opt/ghc/bin:$PATH According to `man environment.d`, this is a proper procedure for altering the PATH variable via systemd. However, it does not work on Ubuntu. The PATH on reboot does not include `/opt/ghc/bin`. This is due to `/etc/profile` incorrectly overwriting the PATH according to comment #10 on https://github.com/systemd/systemd/issues/6414. There is a Debian bug at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=869144 that was prematurely closed because on the Debian side **because it was a Debian issue** rather than a systemd issue, which seems quite nonsensical. Perhaps that issue can be reopened or another can be opened. == Description:Ubuntu 18.04.3 LTS Release:18.04 systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.33 Version table: *** 237-3ubuntu10.33 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.33 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Jan 29 19:07:31 2020 InstallationDate: Installed on 2019-10-10 (111 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=111df9fc-1d42-47eb-82a6-3a80a0aba4c7 ro consoleblank=0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.1 dmi.sys.vendor: QEMU modified.conffile..etc.systemd.timesyncd.conf: [modified] mtime.conffile..etc.systemd.timesyncd.conf: 2019-10-10T02:35:05.488000 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1861364/+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 1858092] Re: Network Manager not saving OpenVPN password
> Is there a rough timeline when this will be available in eoan? It's been in the upload queue for Eoan since Jan 8, hopefully it will be reviewed/accepted soon. -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: In Progress Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+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 1858092] Re: Network Manager not saving OpenVPN password
P.S. The bug is indeed fixed in focal. -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: In Progress Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+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 1857708] Re: Uses GNU awk specific option in bash completions, but gawk is not a dependency
** Description changed: - The following command tells the files: + The following command tells the files: grep awk $(dpkg-query -L pulseaudio | grep /usr/share/bash-completion/completions/) /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ + Only pulseaudio is a regular file; other ones are symbolic links, so it + is enough to modify the first one. + gawk has -e option, but it is not installed by default at least in Xubuntu, so (very) old mawk may be used. Solution: Either use "awk --" instead of "awk -e" or use "gawk -e" and put gawk as dependency. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: jarnos 1200 F pulseaudio - /dev/snd/pcmC1D0p: jarnos 1200 F...m pulseaudio - /dev/snd/controlC0: jarnos 1200 F pulseaudio - /dev/snd/pcmC0D0p: jarnos 1200 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: jarnos 1200 F pulseaudio + /dev/snd/pcmC1D0p: jarnos 1200 F...m pulseaudio + /dev/snd/controlC0: jarnos 1200 F pulseaudio + /dev/snd/pcmC0D0p: jarnos 1200 F...m pulseaudio CurrentDesktop: XFCE Date: Fri Dec 27 18:44:55 2019 InstallationDate: Installed on 2019-12-05 (21 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. -- 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/1857708 Title: Uses GNU awk specific option in bash completions, but gawk is not a dependency Status in pulseaudio package in Ubuntu: Triaged Bug description: The following command tells the files: grep awk $(dpkg-query -L pulseaudio | grep /usr/share/bash-completion/completions/) /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e
[Touch-packages] [Bug 1858092] Re: Network Manager not saving OpenVPN password
Hi Pete, I will try to re-check the status of this for eoan today after work. Sorry for the delay, I have been very busy lately ;) Cheers. -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: In Progress Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+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 1861177] Re: seccomp_rule_add is very slow
** Changed in: snapd Status: New => Triaged ** Changed in: snapd Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1861177 Title: seccomp_rule_add is very slow Status in snapd: Triaged Status in libseccomp package in Ubuntu: Triaged Bug description: There is a known and patched issue with version 2.4 of libseccomp where certain operations have a large performance regression. This is causing some packages that use libseccomp such as container orchestration systems to occasionally time out or otherwise fail under certain workloads. Please consider porting the patch into the various Ubuntu versions that have version 2.4 of libseccomp and into the backports. The performance patch from version 2.5 (yet to be released) applies cleanly on top of the 2.4 branch of libseccomp. For more information, and for a copy of the patch (which can also be cherry picked from the upstream libseccomp repos) see the similar Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1861177/+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 1857708] Re: Uses GNU awk specific option in bash completions, but gawk is not a dependency
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/243 -- 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/1857708 Title: Uses GNU awk specific option in bash completions, but gawk is not a dependency Status in pulseaudio package in Ubuntu: Triaged Bug description: The following command tells the files: grep awk $(dpkg-query -L pulseaudio | grep /usr/share/bash-completion/completions/) /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ gawk has -e option, but it is not installed by default at least in Xubuntu, so (very) old mawk may be used. Solution: Either use "awk --" instead of "awk -e" or use "gawk -e" and put gawk as dependency. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarnos 1200 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1200 F...m pulseaudio /dev/snd/controlC0: jarnos 1200 F pulseaudio /dev/snd/pcmC0D0p: jarnos 1200 F...m pulseaudio CurrentDesktop: XFCE Date: Fri Dec 27 18:44:55 2019 InstallationDate: Installed on 2019-12-05 (21 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1857708/+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 1861177] Re: seccomp_rule_add is very slow
I'm leaving the snapd bug task as New so mvo or ian can take a look when it's their triage day, at the latest; I have nothing useful to do here other than "ouch". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1861177 Title: seccomp_rule_add is very slow Status in snapd: Triaged Status in libseccomp package in Ubuntu: Triaged Bug description: There is a known and patched issue with version 2.4 of libseccomp where certain operations have a large performance regression. This is causing some packages that use libseccomp such as container orchestration systems to occasionally time out or otherwise fail under certain workloads. Please consider porting the patch into the various Ubuntu versions that have version 2.4 of libseccomp and into the backports. The performance patch from version 2.5 (yet to be released) applies cleanly on top of the 2.4 branch of libseccomp. For more information, and for a copy of the patch (which can also be cherry picked from the upstream libseccomp repos) see the similar Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1861177/+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 1860565] Re: Remove ubuntu-web-launchers from 18.04.4
This bug was fixed in the package ubuntu-meta - 1.417.4 --- ubuntu-meta (1.417.4) bionic; urgency=medium * Refreshed dependencies * Removed ubuntu-web-launchers from desktop-recommends (LP: #1860565) -- Iain Lane Wed, 22 Jan 2020 15:25:25 + ** Changed in: ubuntu-meta (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 ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1860565 Title: Remove ubuntu-web-launchers from 18.04.4 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-meta source package in Bionic: Fix Released Status in ubuntu-settings source package in Bionic: Fix Released Bug description: ubuntu-web-launchers only contains the amazon launcher and should be removed from 18.04.4 like focal. [Test Case] 1. On a freshly installed system, uninstall ubuntu-web-launchers, logout/login. 2. Boot an ISO without ubuntu-web-launchers being seeded to the live session 3. Do a default installation from an ISO without ubuntu-web-launchers being seeded 4. Customise your launcher by adding or removing some icons. Remove ubuntu-web-launchers and make sure that your custom icons are all there 5. *With the default set of launcher favourites*, update to ubuntu-settings 18.04.7 For all cases, verify that the Amazon launcher is not in the dock [Impact] None [Risk of regression] If the shell handles this removal badly on existing systems then maybe favourites wouldn't be displayed or you'd see a weird icon not found icon (test cases #4). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:41:43 2020 InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1860565/+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 1860522] Update Released
The verification of the Stable Release Update for mesa 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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1860522 Title: Mesa 19.2.8 stable release Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Eoan: Fix Released Bug description: [Impact] 19.10 released with mesa 19.2.1. We need the last point release of the 19.2.x series in eoan and backported for bionic. [Test case] Check on intel/radeon hw that things still work fine. [Regression potential] This is the last update of the series, all regressions should be shaken off at this point by upstream CI/community To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860522/+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 1860522] Re: Mesa 19.2.8 stable release
This bug was fixed in the package mesa - 19.2.8-0ubuntu0~19.10.1 --- mesa (19.2.8-0ubuntu0~19.10.1) eoan; urgency=medium * New bugfix release. (LP: #1860522) * Revert-meson-fix-logic-for-generating-.pc-files-with.patch: Dropped, fixed upstream. * rules: GLESv2 libs aren't built anymore, drop removing them. * mesa-common-dev: Drop mangled GL/GLX headers, they're not generated anymore. -- Timo Aaltonen Wed, 22 Jan 2020 11:57:11 +0200 ** Changed in: mesa (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1860522 Title: Mesa 19.2.8 stable release Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Eoan: Fix Released Bug description: [Impact] 19.10 released with mesa 19.2.1. We need the last point release of the 19.2.x series in eoan and backported for bionic. [Test case] Check on intel/radeon hw that things still work fine. [Regression potential] This is the last update of the series, all regressions should be shaken off at this point by upstream CI/community To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860522/+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 1860565] Update Released
The verification of the Stable Release Update for ubuntu-settings 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 ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1860565 Title: Remove ubuntu-web-launchers from 18.04.4 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-meta source package in Bionic: Fix Committed Status in ubuntu-settings source package in Bionic: Fix Released Bug description: ubuntu-web-launchers only contains the amazon launcher and should be removed from 18.04.4 like focal. [Test Case] 1. On a freshly installed system, uninstall ubuntu-web-launchers, logout/login. 2. Boot an ISO without ubuntu-web-launchers being seeded to the live session 3. Do a default installation from an ISO without ubuntu-web-launchers being seeded 4. Customise your launcher by adding or removing some icons. Remove ubuntu-web-launchers and make sure that your custom icons are all there 5. *With the default set of launcher favourites*, update to ubuntu-settings 18.04.7 For all cases, verify that the Amazon launcher is not in the dock [Impact] None [Risk of regression] If the shell handles this removal badly on existing systems then maybe favourites wouldn't be displayed or you'd see a weird icon not found icon (test cases #4). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:41:43 2020 InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1860565/+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 1860565] Re: Remove ubuntu-web-launchers from 18.04.4
This bug was fixed in the package ubuntu-settings - 18.04.7 --- ubuntu-settings (18.04.7) bionic; urgency=medium * Make ubuntu-web-launchers an empty package and drop amazon launcher from favourites. For the bionic SRU, it is safest to leave this as an empty package. Users can remove it if they want to. (LP: #1860565) -- Iain Lane Wed, 22 Jan 2020 16:22:04 + ** Changed in: ubuntu-settings (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 ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1860565 Title: Remove ubuntu-web-launchers from 18.04.4 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-meta source package in Bionic: Fix Committed Status in ubuntu-settings source package in Bionic: Fix Released Bug description: ubuntu-web-launchers only contains the amazon launcher and should be removed from 18.04.4 like focal. [Test Case] 1. On a freshly installed system, uninstall ubuntu-web-launchers, logout/login. 2. Boot an ISO without ubuntu-web-launchers being seeded to the live session 3. Do a default installation from an ISO without ubuntu-web-launchers being seeded 4. Customise your launcher by adding or removing some icons. Remove ubuntu-web-launchers and make sure that your custom icons are all there 5. *With the default set of launcher favourites*, update to ubuntu-settings 18.04.7 For all cases, verify that the Amazon launcher is not in the dock [Impact] None [Risk of regression] If the shell handles this removal badly on existing systems then maybe favourites wouldn't be displayed or you'd see a weird icon not found icon (test cases #4). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:41:43 2020 InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1860565/+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 1834875] Re: cloud-init growpart race with udev
Oh yeah and one other thing I don't understand: why udev is processing the partition while sgdisk is still running. -- 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/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: New Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+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 1834875] Re: cloud-init growpart race with udev
Ah, no I think this might be along right lines: udev is calling blkid on the _partition_ of course, so it can probe for filesystem etc without looking at the partition table. After it's done that, it does look for the partition table so it can read the ID_PART_ENTRY_* values from it, but if it fails to load the partition table it just gives up and still returns success. As to how this might happen, well there are certainly moments during sgdisk's writing of the partition table when the gpt data is not completely consistent (it contains checksums and is not written atomically). Two things are still a bit unsatisfactory about this explanation though: 1) it's a mighty tight race, hitting this with any regularity borders on the incredible and 2) I have no idea why this only occurs on Azure on Cosmic up. Although I guess 1) may explain 2) I suppose. Setting LIBBLKID_DEBUG=lowprobe in systemd-udevd's environment during a failing boot would be very interesting to confirm or deny this line of reasoning -- although this will make udevd produce gobs of output and possibly disturb any race. -- 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/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: New Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+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
