[Touch-packages] [Bug 1524215] Re: Lenovo B50-70 inverted internal microphone
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1524215 Title: Lenovo B50-70 inverted internal microphone Status in alsa-driver package in Ubuntu: Expired Bug description: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978 Attached the alsa-info txt to this bug --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marian 1981 F pulseaudio /dev/snd/pcmC1D0c: marian 1981 F...m pulseaudio /dev/snd/pcmC1D0p: marian 1981 F...m pulseaudio /dev/snd/controlC1: marian 1981 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=10570c82-8e52-4379-9a8e-2e30baae9f63 InstallationDate: Installed on 2015-09-10 (90 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20384 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=1791e4c1-12de-4fef-88b1-31716c981648 ro quiet splash ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 Tags: wily Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-10-24 (45 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9DCN34WW(V3.04) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo B50-70 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo B50-70 dmi.modalias: dmi:bvnLENOVO:bvr9DCN34WW(V3.04):bd07/21/2015:svnLENOVO:pn20384:pvrLenovoB50-70:rvnLENOVO:rnLenovoB50-70:rvrNODPK:cvnLENOVO:ct10:cvrLenovoB50-70: dmi.product.name: 20384 dmi.product.version: Lenovo B50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1524215/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1839603] Re: Wifi breaks and needs restart after Laptop's wake up
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- 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/1839603 Title: Wifi breaks and needs restart after Laptop's wake up Status in network-manager package in Ubuntu: Expired Bug description: This is constant struggle for me, it seems that in the initial days after installation of Ubuntu 19.10 this problem of Wifi stopping to work after wake up does not happen. I'm sure, I reinstalled Ubuntu many times, the issue still persist. Breaking of Wifi after computer wake up starts to appear, on average, after a week of computer usage. On my laptop, this Wifi problem existed in the previous Ubuntu versions as well. What works: It seems a simple Wifi turn off and turn on is sufficient, for the bug to go away. But I'm getting tired of this after years of doing it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1839603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846140] Re: Realtek RTL8723BU doesn't work well in ubuntu
This may fix the issue: https://lore.kernel.org/lkml/20191002121808.59376-1-c...@endlessm.com/ -- 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/1846140 Title: Realtek RTL8723BU doesn't work well in ubuntu Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: I have one laptop with Realtek RTL8723BU wifi card. It runs, but signal is weak (it only works if the router is less than a meter away), and even if it gets signal it's slow and it gets interrupted frequently. In windows it works normally, and with a much stronger signal. I tested it on Ubuntu 18.04.3 and 19.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846140/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847399] Re: Help me
Please describe the kind of problem you are experiencing. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1847399 Title: Help me Status in Ubuntu: Incomplete Bug description: Sorry I don't understand ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Oct 9 03:56:09 2019 DistUpgraded: 2018-09-18 19:18:07,768 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio "./xorg_fix_proprietary.py" non riuscita (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: No GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GF119 [GeForce GT 620 OEM] [10de:1049] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF119 [GeForce GT 620 OEM] [1043:84a3] InstallationDate: Installed on 2015-04-17 (1635 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. K30AD_M31AD_M51AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=12b53c52-cdca-4b0e-917f-4f4568ed643a ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-18 (385 days ago) dmi.bios.date: 11/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0402 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K30AD_M31AD_M51AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0402:bd11/29/2013:svnASUSTeKCOMPUTERINC.:pnK30AD_M31AD_M51AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnK30AD_M31AD_M51AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Desktop dmi.product.name: K30AD_M31AD_M51AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Sep 18 15:20:24 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1847399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846692] Re: PCI/internal sound card not detected
If we use 5.0 generic kernel, the kernel should load the legacy hda driver because there is no sof driver in the 5.0 generic kernel. For this problem, the legacy hda driver is not loaded, maybe users forget to install linux-modules-extra- -- 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/1846692 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: As discussed with Rex Tsai 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 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Oct 4 09:43:52 2019 InstallationDate: Installed on 2019-09-23 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET37W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET37W(1.20):bd09/11/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846692/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847399] [NEW] Help me
Public bug reported: Sorry I don't understand ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Oct 9 03:56:09 2019 DistUpgraded: 2018-09-18 19:18:07,768 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio "./xorg_fix_proprietary.py" non riuscita (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: No GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GF119 [GeForce GT 620 OEM] [10de:1049] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF119 [GeForce GT 620 OEM] [1043:84a3] InstallationDate: Installed on 2015-04-17 (1635 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. K30AD_M31AD_M51AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=12b53c52-cdca-4b0e-917f-4f4568ed643a ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-18 (385 days ago) dmi.bios.date: 11/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0402 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K30AD_M31AD_M51AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0402:bd11/29/2013:svnASUSTeKCOMPUTERINC.:pnK30AD_M31AD_M51AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnK30AD_M31AD_M51AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Desktop dmi.product.name: K30AD_M31AD_M51AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Sep 18 15:20:24 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1847399 Title: Help me Status in xorg package in Ubuntu: New Bug description: Sorry I don't understand ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Oct 9 03:56:09 2019 DistUpgraded: 2018-09-18 19:18:07,768 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio "./xorg_fix_proprietary.py" non riuscita (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: No GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GF119 [GeForce GT 620 OEM] [10de:1049] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF119 [GeForce GT 620 OEM] [1043:84a3] InstallationDate: Installed on 2015-04-17 (1635 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. K30AD_M31AD_M51AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=12b53c52-cdca-4b0e-917f-4f4568ed643a ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-18 (385 days ago) dmi.bios.date:
[Touch-packages] [Bug 1846140] Re: Realtek RTL8723BU doesn't work well in ubuntu
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1846140 Title: Realtek RTL8723BU doesn't work well in ubuntu Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: I have one laptop with Realtek RTL8723BU wifi card. It runs, but signal is weak (it only works if the router is less than a meter away), and even if it gets signal it's slow and it gets interrupted frequently. In windows it works normally, and with a much stronger signal. I tested it on Ubuntu 18.04.3 and 19.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846140/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769132] Re: ubuntu18.04's libfreetype6 2.8.1 has a bug of rendering bitmap font
xenial version working fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1769132 Title: ubuntu18.04's libfreetype6 2.8.1 has a bug of rendering bitmap font Status in freetype package in Ubuntu: Fix Released Status in freetype source package in Bionic: Confirmed Bug description: ubuntu18.04's libfreetype6 version 2.8.1 has a bug of rendering bitmap font like ZFull gb, should be upgrade to version 2.9. I checked libfreetype 2.9 fix this bug. I post this bug in: https://savannah.nongnu.org/bugs/?53798 there are some picture I grab for this bug: http://forum.ubuntu.org.cn/viewtopic.php?f=186=487304 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1769132/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846506] Re: autopkgtest fail in Eoan
the latest autopkgtest retries show that the problem is present in the release pocket, so I have hinted away the failure and am closing the tasks on the reverse-dependencies, since they will no longer be blocked. ** Changed in: python-cryptography (Ubuntu) Status: New => Invalid ** Changed in: python3-defaults (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1846506 Title: autopkgtest fail in Eoan Status in python-azure package in Ubuntu: New Status in python-cryptography package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Invalid Bug description: The python-azure autopkgtest is failing on Eoan, currently blocking the migration of: - python-cryptography - python-defaults I had a look at the test log but it's not clear to me where the problem is. The autopkgtest history suggests that the failure is not actually caused by the two packages held in the migration queue. The python-azure autopkgtest is python3-only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-azure/+bug/1846506/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847152] Re: printf escape sentences are insufficiently documented
Hello Christopher, thank you for opening this bug and helping make Ubuntu (and coreutils!) better. I am somewhat confused here. Are you suggesting a change in wording? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1847152 Title: printf escape sentences are insufficiently documented Status in coreutils package in Ubuntu: New Bug description: The info page for ‘printf’ is misleading because the C ‘printf’ function does not interpret any escape sequences. So, interpreting this specification literally, all escape sequences are differences but not all of them are listed below. In particular, the sequence ‘\e’ is not listed. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 19.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 8.30-1ubuntu1 3) What you expected to happen ‘printf’ prints the FORMAT string, interpreting ‘\’ escapes as specified below and interpreting ‘%’ directives to format numeric and string arguments in a way that is mostly similar to the C ‘printf’ function. *Note ‘printf’ format directives: (libc)Output Conversion Syntax, for details. The differences are listed below. 4) What happened instead ‘printf’ prints the FORMAT string, interpreting ‘%’ directives and ‘\’ escapes to format numeric and string arguments in a way that is mostly similar to the C ‘printf’ function. *Note ‘printf’ format directives: (libc)Output Conversion Syntax, for details. The differences are listed below. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: coreutils 8.30-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 23:24:39 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1847152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently
It's still broken, even though I haven't received any suggestions on what to try. Sometimes the network is lost when resuming after suspend, sometimes, just because it feels like it. ** Changed in: network-manager (Ubuntu) Status: Expired => New -- 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/1838836 Title: network-manager needs to be restarted frequently Status in network-manager package in Ubuntu: New Bug description: I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops working frequently and the network-manager service needs to be restarted. It will die on its own, but can be triggered by switching wifi 3 times (sometimes more, sometimes fewer)! When it is working, I have: ``` % usr/bin/sudo nmcli device DEVICE TYPE STATE CONNECTION wlp62s0 wifi connected ATT964 p2p-dev-wlp62s0 wifi-p2p disconnected -- enp59s0 ethernet unavailable -- lo loopback unmanaged -- % /usr/bin/sudo lshw -C network ...snip... *-network description: Wireless interface product: Wireless 8260 vendor: Intel Corporation physical id: 0 bus info: pci@:3e:00.0 logical name: wlp62s0 version: 3a serial: e4:b3:18:e3:11:e7 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:133 memory:dc20-dc201fff % /usr/bin/sudo lspci -vnnn | grep -A 9 Network 3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010] Flags: bus master, fast devsel, latency 0, IRQ 133 Memory at dc20 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7 Capabilities: [14c] Latency Tolerance Reporting ``` If I switch between my two wifi routers three times (sometimes more times) using the Select Network command on the taskbar, wifi stops working. Issuing the commands above yields the following differences: ``` % /usr/bin/sudo nmcli device DEVICE TYPE STATECONNECTION enp59s0 ethernet unavailable -- wlp62s0 wifi unavailable -- p2p-dev-wlp62s0 wifi-p2p unavailable -- lo loopback unmanaged % /usr/bin/sudo lshw -C network ...snip... *-network ...snip... configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 ``` /var/log/syslog reports the following after failing to switch wifi networks: ``` Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): disconnecting for new activation request. Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5485] manager: NetworkManager state is now DISCONNECTING Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5548] audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" name="ATT964" pid=21476 uid=1010 result="success" Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5550] device (wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING)
[Touch-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently
Network shutdown still happens in Ubuntu 19.10. -- 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/1838836 Title: network-manager needs to be restarted frequently Status in network-manager package in Ubuntu: New Bug description: I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops working frequently and the network-manager service needs to be restarted. It will die on its own, but can be triggered by switching wifi 3 times (sometimes more, sometimes fewer)! When it is working, I have: ``` % usr/bin/sudo nmcli device DEVICE TYPE STATE CONNECTION wlp62s0 wifi connected ATT964 p2p-dev-wlp62s0 wifi-p2p disconnected -- enp59s0 ethernet unavailable -- lo loopback unmanaged -- % /usr/bin/sudo lshw -C network ...snip... *-network description: Wireless interface product: Wireless 8260 vendor: Intel Corporation physical id: 0 bus info: pci@:3e:00.0 logical name: wlp62s0 version: 3a serial: e4:b3:18:e3:11:e7 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:133 memory:dc20-dc201fff % /usr/bin/sudo lspci -vnnn | grep -A 9 Network 3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010] Flags: bus master, fast devsel, latency 0, IRQ 133 Memory at dc20 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7 Capabilities: [14c] Latency Tolerance Reporting ``` If I switch between my two wifi routers three times (sometimes more times) using the Select Network command on the taskbar, wifi stops working. Issuing the commands above yields the following differences: ``` % /usr/bin/sudo nmcli device DEVICE TYPE STATECONNECTION enp59s0 ethernet unavailable -- wlp62s0 wifi unavailable -- p2p-dev-wlp62s0 wifi-p2p unavailable -- lo loopback unmanaged % /usr/bin/sudo lshw -C network ...snip... *-network ...snip... configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 ``` /var/log/syslog reports the following after failing to switch wifi networks: ``` Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): disconnecting for new activation request. Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5485] manager: NetworkManager state is now DISCONNECTING Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5548] audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" name="ATT964" pid=21476 uid=1010 result="success" Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5550] device (wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: CTRL-EVENT-DISCONNECTED bssid=10:7b:ef:cc:ab:a3 reason=3 locally_generated=1 Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0:
[Touch-packages] [Bug 1847176] Re: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card
@gunnarl, did your audio work correctly in kernel 5.0.0-29, and broke when you updated to 5.0.0-31? If you boot 5.0.0-29 by selecting it in grub when you turn your computer on, does your audio work? Might this be related to Bug 1846991? -- 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/1847176 Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: No Sound on laptop speaker after upgrading ubuntu 19.04 a few days ago. Soundcard is found in alsamixer but only "dummy" is available in gnome settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 20:18:10 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ec963f21-6d46-4fd7-a5b5-286e29729b6b InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:5620 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Laptop 13-ad1xx Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=d203e9e9-3d32-4223-b420-e5ce61567401 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-31-generic x86_64 UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop
[Touch-packages] [Bug 1843394] Re: FTBFS in Eoan - Error: operand type mismatch for `push' - gcc 9.2.1 / binutils 2.32.51.20190905-0ubuntu1
This bug was fixed in the package binutils - 2.33-1ubuntu1 --- binutils (2.33-1ubuntu1) eoan; urgency=medium * Don't generate control file entries for any native mips* packages. binutils (2.33-1) unstable; urgency=medium * Binutils 2.33 release (taken from the binutils-2_33 tag). * Update from the binutils 2.33 branch: - Fix PR 24942, change objcopy's --set-section-alignment option so that it takes a byte alignment value rather than a power of two alignment value. - x86-64: fix handling of PUSH/POP of segment register. LP: #1843394. * Merge changes from binutils-mipsen. * Bump standards version. -- Matthias Klose Tue, 08 Oct 2019 12:41:06 +0200 ** Changed in: binutils (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1843394 Title: FTBFS in Eoan - Error: operand type mismatch for `push' - gcc 9.2.1 / binutils 2.32.51.20190905-0ubuntu1 Status in binutils: Fix Released Status in binutils package in Ubuntu: Fix Released Status in ipxe package in Ubuntu: Invalid Bug description: This might be due to new gcc-9 being more strict, but the build that worked before now fails with: arch/x86_64/core/gdbidt.S: Assembler messages: arch/x86_64/core/gdbidt.S:109: Error: operand type mismatch for `push' arch/x86_64/core/gdbidt.S:110: Error: operand type mismatch for `push' arch/x86_64/core/gdbidt.S:161: Error: operand type mismatch for `pop' arch/x86_64/core/gdbidt.S:162: Error: operand type mismatch for `pop' make[2]: *** [Makefile.housekeeping:937: bin-x86_64-efi/gdbidt.o] Error 1 Full log at: https://launchpadlibrarian.net/441262285/buildlog_ubuntu- eoan-amd64.ipxe_1.0.0+git-20190109.133f4c4-0ubuntu2_BUILDING.txt.gz Now all of this is about push/pop of %fs and %gs. That needs to match the size of the registers which depend on the current running mode. In this particular case in ./src/arch/x86_64/core/gdbidt.S The failing file is in ".code64" mode. In that I'd expect %gs/%fs to be 64 bit. Usually we see push/pop "w" in .code16 (word), l in .code32 (long) but in that sense here q (quad word) seems right at first (should be what correctly matches the .code64). That matches what I see throughout the ipxe code but also throughout the archive https://codesearch.debian.net/search?q=pop%5Ba-z%5D.*%25fs=0=2 Maybe I misread the mode it is in, or it is actually a false positives. Or the sizes of FS/GS do not change - haven't touched them in a lng time. Was it that segment registers didn't change size? I'll need to do a few checks to first see what the compiler would expect there and from there need to understand this. The command used also points to AS being in 64 bit mode when this happens: gcc -E -DARCH=x86_64 -DPLATFORM=efi -DSECUREBOOT=0 -fstrength-reduce -fomit-frame-pointer -falign-jumps=1 -falign-loops=1 -falign-functions=1 -m64 -mno-mmx -mno-sse -fshort-wchar -Ui386 -Ulinux -DNVALGRIND -fpie -mno-red-zone -Iinclude -I. -Iarch/x86/include -Iarch/x86_64/include -Iarch/x86_64/include/efi -Os -g -ffreestanding -Wall -W -Wformat-nonliteral -fno-stack-protector -fno-dwarf2-cfi-asm -fno-exceptions -fno-unwind-tables -fno-asynchronous-unwind-tables -Wno-address -Wno-stringop-truncation -ffunction-sections -fdata-sections -include include/compiler.h -DASM_TCHAR='@' -DASM_TCHAR_OPS='@' -DASSEMBLY -DOBJECT=gdbidt arch/x86_64/core/gdbidt.S | as --64-o bin-x86_64-efi/gdbidt.o To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1843394/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846506] Re: autopkgtest fail in Eoan
Given the tests pass locally in a container (autopkgtest ... -- lxd ubuntu-daily;eoan), I'm trying a bileto run (https://bileto.ubuntu.com/#/ticket/3818) to see if that reproduces the test failure. If yes, then I can use that platform for troubleshooting. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1846506 Title: autopkgtest fail in Eoan Status in python-azure package in Ubuntu: New Status in python-cryptography package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Bug description: The python-azure autopkgtest is failing on Eoan, currently blocking the migration of: - python-cryptography - python-defaults I had a look at the test log but it's not clear to me where the problem is. The autopkgtest history suggests that the failure is not actually caused by the two packages held in the migration queue. The python-azure autopkgtest is python3-only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-azure/+bug/1846506/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835464] Re: nginx service fails after libssl update due to low entropy at boot
** Tags added: bionic-openssl-1.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1835464 Title: nginx service fails after libssl update due to low entropy at boot Status in nginx package in Ubuntu: Opinion Status in openssl package in Ubuntu: New Status in nginx source package in Bionic: Opinion Status in openssl source package in Bionic: New Bug description: After updating libssl and related packages, nginx will no longer autostart at system boot. Immediately after boot, nginx.service is in a failed state. # service nginx status ● nginx.service - A high performance web server and a reverse proxy server Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled) Active: failed (Result: timeout) since Fri 2018-08-24 21:27:51 UTC; 32min ago Docs: man:nginx(8) systemd[1]: Starting A high performance web server and a reverse proxy server... systemd[1]: nginx.service: Start-pre operation timed out. Terminating. systemd[1]: nginx.service: Failed with result 'timeout'. systemd[1]: Failed to start A high performance web server and a reverse proxy server. The service can be manually started after boot. # service nginx start # service nginx status ● nginx.service - A high performance web server and a reverse proxy server Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2018-08-24 22:02:06 UTC; 2s ago Docs: man:nginx(8) Process: 2704 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=0/SUCCESS) Process: 2703 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS) Main PID: 2705 (nginx) CGroup: /system.slice/nginx.service ├─2705 nginx: master process /usr/sbin/nginx -g daemon on; master_process on; └─2706 nginx: worker process systemd[1]: Starting A high performance web server and a reverse proxy server... systemd[1]: nginx.service: Failed to parse PID from file /run/nginx.pid: Invalid argument systemd[1]: Started A high performance web server and a reverse proxy server. This happens on an ARMHF based microcontroller running ubuntu 18.04.2 raspi server distribution with a stock kernel.org 4.9-181 kernel. Ubuntu repositories are not accessible from the device, so packages are copied to the device, and apt install is used to upgrade them: apt install --no-install-recommends $dir/updates/system/*.deb | logger 2>&1 The following is a list of packages that, when upgraded, cause the nginx systemd service to fail to autostart at boot. 201,205c201,205 < ii libpython2.7:armhf 2.7.15-4ubuntu4~18.04 armhf Shared Python runtime library (version 2.7) < ii libpython2.7-minimal:armhf 2.7.15-4ubuntu4~18.04 armhf Minimal subset of the Python language (version 2.7) < ii libpython2.7-stdlib:armhf 2.7.15-4ubuntu4~18.04 armhf Interactive high-level object-oriented language (standard library, version 2.7) < ii libpython3.6-minimal:armhf 3.6.8-1~18.04.1 armhf Minimal subset of the Python language (version 3.6) < ii libpython3.6-stdlib:armhf 3.6.8-1~18.04.1 armhf Interactive high-level object-oriented language (standard library, version 3.6) --- > ii libpython2.7:armhf 2.7.15~rc1-1ubuntu0.1 armhf Shared Python runtime library (version 2.7) > ii libpython2.7-minimal:armhf 2.7.15~rc1-1ubuntu0.1 armhf Minimal subset of the Python language (version 2.7) > ii libpython2.7-stdlib:armhf 2.7.15~rc1-1ubuntu0.1 armhf Interactive high-level object-oriented language (standard library, version 2.7) > ii libpython3.6-minimal:armhf 3.6.7-1~18.04 armhf Minimal subset of the Python language (version 3.6) > ii libpython3.6-stdlib:armhf 3.6.7-1~18.04 armhf Interactive high-level object-oriented language (standard library, version 3.6) 225c225 < ii libssl1.1:armhf 1.1.1-1ubuntu2.1~18.04.2 armhf Secure Sockets Layer toolkit - shared libraries --- > ii libssl1.1:armhf 1.1.0g-2ubuntu4.3 armhf Secure Sockets Layer toolkit - shared libraries 272c272 < ii openssl 1.1.1-1ubuntu2.1~18.04.2 armhf Secure Sockets Layer toolkit - cryptographic utility --- > ii openssl 1.1.0g-2ubuntu4.3 armhf Secure Sockets Layer toolkit - cryptographic utility 282,283c282,283 < ii python3.6
[Touch-packages] [Bug 1847347] [NEW] 1.42.13-1ubuntu1.1 breaks debootstrap in Xenial
Public bug reported: At my company we prepare system disk images which start from deboostrap pointing at an internal mirror containing packages from xenial, xenial- updates, and elsewhere. As of September 30, our image preparation begun failing during the initial debootstrap. We narrowed it down to this update— when we remove version 1.42.13-1ubuntu1.1 of this package from our mirror, everything works as before. Apologies that I don't have more details at this time, as we're still digging. But just wanted to get the ball rolling on a discussion here. ** Affects: e2fsprogs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1847347 Title: 1.42.13-1ubuntu1.1 breaks debootstrap in Xenial Status in e2fsprogs package in Ubuntu: New Bug description: At my company we prepare system disk images which start from deboostrap pointing at an internal mirror containing packages from xenial, xenial-updates, and elsewhere. As of September 30, our image preparation begun failing during the initial debootstrap. We narrowed it down to this update— when we remove version 1.42.13-1ubuntu1.1 of this package from our mirror, everything works as before. Apologies that I don't have more details at this time, as we're still digging. But just wanted to get the ball rolling on a discussion here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1847347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1816530] Re: DNS servers are not being set in the system correctly when you upgrade from 16.04 to 18.04
> During the upgrade which was done using Wi-Fi, the connection went down but it was after the download completed so the upgrade ended. sorry, it's not clear to me, are you saying the upgrade completed successfully? And do you mean that currently, your dns does not work? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1816530 Title: DNS servers are not being set in the system correctly when you upgrade from 16.04 to 18.04 Status in resolvconf package in Ubuntu: Invalid Bug description: I upgraded my 16.04 to 18.04 before the official release. After the upgrade I noticed that I don't have internet access. The wired network and the wifi settings looked good, but the internet didn't work. After the login the system always switched itself into airplane mode. I tethered the network via USB and Bluetooth by my mobile but they also didn't work. I found a useful answer from @andrew-woodhead666: https://answers.launchpad.net/ubuntu/+question/665374 it seems this bug is still not fixed for the upgraded dists in the main release and affects a few dozens of ubuntu users. https://askubuntu.com/questions/1021884/no-internet-after-upgrade-from-16-04-to-18-04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1816530/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845652] Re: rsync sends everything, not just changes
On a prior OS (16.04 or 18.04, cannot remember which) the following rsync -v -a -r -W -p -o -g -t --delete --stats ~/Pictures /media/$USER /USB-128GB-1/ >bkp_log would only send differences on subsequent runs with a fat32 USB key. Your test above seems to indicate that subsequent runs on 19.04 send everything for vfat. Therefore, my initial test on 19.04 must have been a fat32 USB key and not a LUKS/ext4 USB key. Please close this case if you are satisfied with these explanations. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1845652 Title: rsync sends everything, not just changes Status in rsync package in Ubuntu: Incomplete Bug description: Repeated runs of rsync from PC to USB key send everything, not just the changes. This is reproducible. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: rsync 3.1.3-6 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 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 09:18:19 2019 InstallationDate: Installed on 2019-06-10 (109 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1845652/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843381] Re: Dell system takes a long time to connect network with external dock
Thanks @cktenn - I commented there and also opened https://salsa.debian.org/systemd-team/systemd/merge_requests/56, but I have not tested with that, can you see if that fixes this problem? Assuming I'm understanding the problem correctly, that you just want 73 -special-net-names.rules to ignore the second duplicated-mac interface. -- 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/1843381 Title: Dell system takes a long time to connect network with external dock Status in OEM Priority Project: New Status in systemd package in Ubuntu: New Bug description: This is a bug reopen from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837700 The original one caused systemd regressed. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842651 This issue needs an alternative solution. Dell has a feature called MAC addrss passthrough[1] that would force usb ethernet adapters to be assigned with a predefined MAC address stored in BIOS or so. This feature has been landed to mainline kernel in driver r8152[2]. So whenever a r8152 managed device is plugged into Dell devices with MAC addrss passthrough enabled, this driver will set NIC MAC to a predefined one. And some Dell devices have already one built-in r8152 NIC port. On these devices, when a second r8152 NIC is plugged in, a Debian originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev built-in command `net_id` to give a persistent name, and that will be based on MAC address. However, since the system has already initialized the built-in r8152 NIC with that name, renaming the second interface with this name will always fail. While Debian still carries a patch called "Revert-udev-network-device- renaming-immediately-give.patch"[4] that tries to keep support of already deprecated "75-persistent-net-generator.rules" based interface renaming mechanism, this patch also propagated into Ubuntu[5]. This patch will retry renaming with a 90 seconds timeout when the error code is -EEXIST, so the uevent processing will always be blocked in the last ifrename step in the victim system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules lib/udev/rules.d/50-udev-default.rules lib/udev/rules.d/73-special-net-names.rules lib/udev/rules.d/73-usb-net-by-mac.rules] ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18 Uname: Linux 4.15.0-1043-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules Date: Wed Jul 24 15:30:59 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90 InstallationDate: Installed on 2019-07-03 (20 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Latitude 7424 Rugged Extreme ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0Y7FK3 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7424 Rugged Extreme dmi.sys.vendor: Dell Inc. [1]: https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c [3]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules [4]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch [5]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/tree/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch?h=ubuntu-bionic To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1843381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1843733] Re: fftw3 ftbfs in eoan (armhf only)
Reported upstream on https://github.com/FFTW/fftw3/issues/182 , with some luck they have an idea about the bug ** Bug watch added: github.com/FFTW/fftw3/issues #182 https://github.com/FFTW/fftw3/issues/182 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fftw3 in Ubuntu. https://bugs.launchpad.net/bugs/1843733 Title: fftw3 ftbfs in eoan (armhf only) Status in fftw3 package in Ubuntu: Confirmed Status in fftw3 source package in Eoan: Confirmed Bug description: fftw3 ftbfs in eoan (armhf only). https://launchpadlibrarian.net/441265031/buildlog_ubuntu-eoan- armhf.fftw3_3.3.8-2_BUILDING.txt.gz ( cd tests ; /usr/bin/make smallcheck ) make[1]: Entering directory '/<>/tests' perl -w ./check.pl -r -c=1 -v `pwd`/bench Executing "/<>/tests/bench --verbose=1 --verify 'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304'" ok7e10x12bv29 1.71318e-07 1.44516e-06 2.00887e-07 ik7e10x12bv29 1.66737e-07 1.44901e-06 1.76717e-07 Segmentation fault (core dumped) FAILED /<>/tests/bench: --verify 'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304' make[1]: *** [Makefile:723: smallcheck] Error 1 make[1]: Leaving directory '/<>/tests' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1843733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843381] Re: Dell system takes a long time to connect network with external dock
@Dan I've submitted a merge request to Debian that only applies to Dell system the idea mentioned in comment #4, it modifies the rule 73 -special-net-names.rules. https://salsa.debian.org/systemd-team/systemd/merge_requests/55 Please help to review this. -- 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/1843381 Title: Dell system takes a long time to connect network with external dock Status in OEM Priority Project: New Status in systemd package in Ubuntu: New Bug description: This is a bug reopen from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837700 The original one caused systemd regressed. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842651 This issue needs an alternative solution. Dell has a feature called MAC addrss passthrough[1] that would force usb ethernet adapters to be assigned with a predefined MAC address stored in BIOS or so. This feature has been landed to mainline kernel in driver r8152[2]. So whenever a r8152 managed device is plugged into Dell devices with MAC addrss passthrough enabled, this driver will set NIC MAC to a predefined one. And some Dell devices have already one built-in r8152 NIC port. On these devices, when a second r8152 NIC is plugged in, a Debian originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev built-in command `net_id` to give a persistent name, and that will be based on MAC address. However, since the system has already initialized the built-in r8152 NIC with that name, renaming the second interface with this name will always fail. While Debian still carries a patch called "Revert-udev-network-device- renaming-immediately-give.patch"[4] that tries to keep support of already deprecated "75-persistent-net-generator.rules" based interface renaming mechanism, this patch also propagated into Ubuntu[5]. This patch will retry renaming with a 90 seconds timeout when the error code is -EEXIST, so the uevent processing will always be blocked in the last ifrename step in the victim system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules lib/udev/rules.d/50-udev-default.rules lib/udev/rules.d/73-special-net-names.rules lib/udev/rules.d/73-usb-net-by-mac.rules] ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18 Uname: Linux 4.15.0-1043-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules Date: Wed Jul 24 15:30:59 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90 InstallationDate: Installed on 2019-07-03 (20 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Latitude 7424 Rugged Extreme ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0Y7FK3 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7424 Rugged Extreme dmi.sys.vendor: Dell Inc. [1]: https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c [3]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules [4]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch [5]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/tree/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch?h=ubuntu-bionic To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1843381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1845652] Re: rsync sends everything, not just changes
I have run 2 test scenarios. A trivial folder containing 3 text files as source. A real world case of ~/ as source. Both cases work as expected on an LUKS encrypted ext4 USB key. I will do some more testing on fat32 and report back. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1845652 Title: rsync sends everything, not just changes Status in rsync package in Ubuntu: Incomplete Bug description: Repeated runs of rsync from PC to USB key send everything, not just the changes. This is reproducible. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: rsync 3.1.3-6 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 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 09:18:19 2019 InstallationDate: Installed on 2019-06-10 (109 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1845652/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1827842] [pulseaudio/disco] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for disco for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- 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/1827842 Title: pulseaudio should not load module-x11-bell in gnome-shell Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Disco: Fix Committed Bug description: * Impact The package force load a bell sound which can conflicts with the user configuration * Test case - Enable a login sound in session - Login into a GNOME/Ubuntu session -> the configured sound should be played * Regression potential Try other desktop environments to make sure their login sound behaviour isn't changed, it shouldn't since the customization dropped was specific to the Ubuntu sound theme --- The package `pulseaudio` installs a startup script in `/etc/xdg/autostart/pulseaudio.desktop`, which itself runs `/usr/bin/start-pulseaudio-x11`, which loads a number of x11 related modules in `pulseaudio`. One of these modules is `module-x11-bell`, which makes `pulseaudio` play a sound each time a system bell is emitted (usually by terminal applications, such as bash or vim). This is redundant with gnome-shell, which is also able to handle the system bell (through the gsetting key `org.gnome.desktop.sound event-sounds`). The gnome system bell is directly configurable by the user (Settings > Sound), so it should be preferred over pulseaudio's own system bell. I suggest to patch the `/usr/bin/start-pulseaudio-x11`, to avoid loading `start-pulseaudio-x11` if it detects it is running in Gnome Shell (e.g. if GNOME_SHELL_SESSION_MODE is set). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1827842/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843733] Re: fftw3 ftbfs in eoan (armhf only)
Trying to debug a bit on a canonistack instance ==5906== Command: ./bench --verify ofr108*118 ==5906== ==5906== Invalid write of size 8 ==5906==at 0x49174A8: vst1_f32 (arm_neon.h:10876) ==5906==by 0x49174A8: ST (simd-neon.h:119) ==5906==by 0x49174A8: n1fv_9 (n1fv_9.c:230) ==5906==by 0x4884F4F: dobatch (direct.c:51) ==5906==by 0x48850B5: apply_buf (direct.c:87) ==5906==by 0x48869B1: fftwf_dft_solve (solve.c:29) ==5906==by 0x4882407: measure (timer.c:136) ==5906==by 0x4882407: fftwf_measure_execution_time (timer.c:159) ==5906==by 0x4880725: evaluate_plan (planner.c:460) ==5906==by 0x48808B9: search0 (planner.c:529) ==5906==by 0x48809B1: search (planner.c:600) ==5906==by 0x48809B1: mkplan (planner.c:711) ==5906==by 0x4880D2D: fftwf_mkplan_d (planner.c:970) ==5906==by 0x48B5A0F: mkplan (ct-hc2c.c:198) ==5906==by 0x48807E3: invoke_solver (planner.c:486) ==5906==by 0x48807E3: search0 (planner.c:529) ==5906==by 0x48809B1: search (planner.c:600) ==5906==by 0x48809B1: mkplan (planner.c:711) ==5906== Address 0x96bafa8 is not stack'd, malloc'd or (recently) free'd ==5906== ==5906== ==5906== Process terminating with default action of signal 11 (SIGSEGV) ==5906== Access not within mapped region at address 0x96BAFA8 ==5906==at 0x49174A8: vst1_f32 (arm_neon.h:10876) ==5906==by 0x49174A8: ST (simd-neon.h:119) ==5906==by 0x49174A8: n1fv_9 (n1fv_9.c:230) ==5906==by 0x4884F4F: dobatch (direct.c:51) ==5906==by 0x48850B5: apply_buf (direct.c:87) ==5906==by 0x48869B1: fftwf_dft_solve (solve.c:29) ==5906==by 0x4882407: measure (timer.c:136) ==5906==by 0x4882407: fftwf_measure_execution_time (timer.c:159) ==5906==by 0x4880725: evaluate_plan (planner.c:460) ==5906==by 0x48808B9: search0 (planner.c:529) ==5906==by 0x48809B1: search (planner.c:600) ==5906==by 0x48809B1: mkplan (planner.c:711) ==5906==by 0x4880D2D: fftwf_mkplan_d (planner.c:970) ==5906==by 0x48B5A0F: mkplan (ct-hc2c.c:198) ==5906==by 0x48807E3: invoke_solver (planner.c:486) ==5906==by 0x48807E3: search0 (planner.c:529) ==5906==by 0x48809B1: search (planner.c:600) ==5906==by 0x48809B1: mkplan (planner.c:711) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fftw3 in Ubuntu. https://bugs.launchpad.net/bugs/1843733 Title: fftw3 ftbfs in eoan (armhf only) Status in fftw3 package in Ubuntu: Confirmed Status in fftw3 source package in Eoan: Confirmed Bug description: fftw3 ftbfs in eoan (armhf only). https://launchpadlibrarian.net/441265031/buildlog_ubuntu-eoan- armhf.fftw3_3.3.8-2_BUILDING.txt.gz ( cd tests ; /usr/bin/make smallcheck ) make[1]: Entering directory '/<>/tests' perl -w ./check.pl -r -c=1 -v `pwd`/bench Executing "/<>/tests/bench --verbose=1 --verify 'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304'" ok7e10x12bv29 1.71318e-07 1.44516e-06 2.00887e-07 ik7e10x12bv29 1.66737e-07 1.44901e-06 1.76717e-07 Segmentation fault (core dumped) FAILED /<>/tests/bench: --verify 'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304' make[1]: *** [Makefile:723: smallcheck] Error 1 make[1]: Leaving directory '/<>/tests' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1843733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846821] Re: Qt print dialog has wrong default page size
The fix is included in Qt 5.11, so I am marking it as affecting only Bionic. ** Also affects: qtbase-opensource-src (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1846821 Title: Qt print dialog has wrong default page size Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: New Bug description: Please backport Qt patch 213677 to qtbase-opensource-src https://codereview.qt-project.org/c/qt/qtbase/+/213677 In Qt5 applications, print dialog (Printer Properties) always defaults to A4 paper size, even when Letter is set as a default in all system and KDE preferences. After changing manually, Letter-size pages print correctly, but the setting does not stick. The issue also affects other print settings, e.g. margins, though the aforementioned patch does not deal with these. A similar issue regarding the duplex setting was reported as Launchpad bug 1776173, and subsequently fixed, but other print settings continue to cause problems. Behavior expected: Print dialog would default to Letter paper size, which is set in all available system and KDE preferences, and that was selected for previous prints. Behavior observed: Print dialog always defaults to A4, and page size needs to be changed manually before every print. Software versions: lsb_release: Ubuntu 18.04.3 LTS libqt5core5a: 5.9.5+dfsg-0ubuntu2.3 Kernel: 5.0.0-25-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1846821/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843381] Re: Dell system takes a long time to connect network with external dock
@cktenn that could work (using special-net-names), however I'm concerned that the rule should not apply to all r8152 devices, everywhere, on everyone's systems. It should apply *only* on Dell systems where this magical MAC passthrough is enabled. What can be checked to see if the system is a Dell with the special MAC passthrough enabled? Alternately, if the only problem is 73-usb-net-by-mac.rules fails due to the system having multiple nics with the same mac, that rule could be adjusted to check if an interface with the name already exists, and if so don't try re-setting it (since that would fail). That might be an easier sell to Debian. What do you think? -- 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/1843381 Title: Dell system takes a long time to connect network with external dock Status in OEM Priority Project: New Status in systemd package in Ubuntu: New Bug description: This is a bug reopen from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837700 The original one caused systemd regressed. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842651 This issue needs an alternative solution. Dell has a feature called MAC addrss passthrough[1] that would force usb ethernet adapters to be assigned with a predefined MAC address stored in BIOS or so. This feature has been landed to mainline kernel in driver r8152[2]. So whenever a r8152 managed device is plugged into Dell devices with MAC addrss passthrough enabled, this driver will set NIC MAC to a predefined one. And some Dell devices have already one built-in r8152 NIC port. On these devices, when a second r8152 NIC is plugged in, a Debian originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev built-in command `net_id` to give a persistent name, and that will be based on MAC address. However, since the system has already initialized the built-in r8152 NIC with that name, renaming the second interface with this name will always fail. While Debian still carries a patch called "Revert-udev-network-device- renaming-immediately-give.patch"[4] that tries to keep support of already deprecated "75-persistent-net-generator.rules" based interface renaming mechanism, this patch also propagated into Ubuntu[5]. This patch will retry renaming with a 90 seconds timeout when the error code is -EEXIST, so the uevent processing will always be blocked in the last ifrename step in the victim system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules lib/udev/rules.d/50-udev-default.rules lib/udev/rules.d/73-special-net-names.rules lib/udev/rules.d/73-usb-net-by-mac.rules] ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18 Uname: Linux 4.15.0-1043-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules Date: Wed Jul 24 15:30:59 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90 InstallationDate: Installed on 2019-07-03 (20 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Latitude 7424 Rugged Extreme ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0Y7FK3 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7424 Rugged Extreme dmi.sys.vendor: Dell Inc. [1]: https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c [3]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules [4]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch [5]:
[Touch-packages] [Bug 1776626] Re: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part
Verified with systemd/237-3ubuntu10.31: ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo vi /etc/crypttab ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo systemctl daemon-reload ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo service systemd-cryptsetup@vdb_crypt start Please enter passphrase for disk vdb_crypt! ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ cat /etc/crypttab vdb_crypt /dev/vdb none luks,sector-size=4096 ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo service systemd-cryptsetup@vdb_crypt status ● systemd-cryptsetup@vdb_crypt.service - Cryptography Setup for vdb_crypt Loaded: loaded (/etc/crypttab; generated) Active: active (exited) since Tue 2019-10-08 21:05:11 CEST; 13s ago Docs: man:crypttab(5) man:systemd-cryptsetup-generator(8) man:systemd-cryptsetup@.service(8) Process: 1999 ExecStart=/lib/systemd/systemd-cryptsetup attach vdb_crypt /dev/vdb none luks,sector-size=4096 (cod Main PID: 1999 (code=exited, status=0/SUCCESS) okt 08 21:05:06 ubuntu-Standard-PC-i440FX-PIIX-1996 systemd[1]: Starting Cryptography Setup for vdb_crypt... okt 08 21:05:09 ubuntu-Standard-PC-i440FX-PIIX-1996 systemd-cryptsetup[1999]: Set cipher aes, mode xts-plain64, key okt 08 21:05:11 ubuntu-Standard-PC-i440FX-PIIX-1996 systemd[1]: Started Cryptography Setup for vdb_crypt. ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo fdisk /dev/mapper/vdb_crypt Welcome to fdisk (util-linux 2.31.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Device does not contain a recognized partition table. Created a new DOS disklabel with disk identifier 0x313e0336. Command (m for help): p Disk /dev/mapper/vdb_crypt: 5 GiB, 5366611968 bytes, 1310208 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x313e0336 Command (m for help): q ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ ** 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1776626 Title: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part Status in Ubuntu on IBM z Systems: Fix Released Status in cryptsetup package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in cryptsetup source package in Bionic: Won't Fix Status in systemd source package in Bionic: Fix Committed Bug description: [Impact] * cryptsetup in bionic supports creating luks volumes with a non- standard sector-size option, and thus this option also needs to be used when activating the LUKS volumes. Add sector-size= option support to /etc/crypttab. [Test Case] * Create a plain LUKS volume with sector-size 4096 * Specify sector-size=4096 option in /etc/crypttab * reload systemd, start systemd-cryptsetup@.service for that volume * check the journal, to ensure that `sector-size` option was recognized and is active. (i.e. there is not error messages about unrecognized option `sector-size` from systemd-cryptsetup) [Regression Potential] * This is an optional argument, not used by default. Currently custom sector-size crypttab does not work correctly, and thus cannot regress. [Other Info] * Original bug report Support fast clear key dm-crypt with 4k support Extend /etc/crypttab to enable 4k sector support in plain mode The proposed enhancements are posted on github, see https://github.com/systemd/systemd/issues/8881 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1776626/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
Yes, based on the analysis that the failure is caused by buggy *rm scripts in an obsolete and already-uninstalled version of the systemd- shim package, I expected to still see failures with the new version. But this should not block the SRU, even though the Conflicts is not actually doing anything. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: Fix Committed Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial, ie. lxc launch ubuntu-daily:xenial test-shim-upgrade lxc exec test-shim-upgrade apt update apt install systemd-shim wget https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb apt install ./systemd-shim_10-3_amd64.deb sed 's/xenial/bionic/' -i /etc/apt/sources.list apt update apt install systemd this currently passes, however, systemd-shim remains installed. It should be removed instead. Apt install systemd should have lines like this: The following packages will be REMOVED: systemd-shim ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' ... [Regression Potential] * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823076] Re: System wakes up immediately after suspend if Bluetooth is still enabled
Newer firmwares [1] may be required. [1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/ -- 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/1823076 Title: System wakes up immediately after suspend if Bluetooth is still enabled Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate: Installed on 2019-02-09 (53 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems NUC8i3BEH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:BB:60:50:92:5D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1912660 acl:106009 sco:0 events:337 errors:0 TX bytes:12331 acl:74 sco:0 commands:204 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1722478] Re: Two-finger scrolling and click-and-drag no longer works after resuming from suspend
** Also affects: kmod (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling and click-and-drag no longer works after resuming from suspend Status in Linux: Confirmed Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647285] Re: SSL trust not system-wide
This isn't "just" a bug, it's a roadmap item in my view, as many products are affected. It needs a spec, like in the fedora case. I agree that it would be awesome to have this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1647285 Title: SSL trust not system-wide Status in ca-certificates package in Ubuntu: Confirmed Status in nss package in Ubuntu: Confirmed Status in p11-kit package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: When I install a corporate CA trust root with update-ca-certificates, it doesn't seem to work everywhere. Various things like Firefox, Evolution, Chrome, etc. all fail to trust the newly-installed trusted CA. This ought to work, and does on other distributions. In p11-kit there is a module p11-kit-trust.so which can be used as a drop-in replacement for NSS's own libnssckbi.so trust root module, but which reads from the system's configured trust setup instead of the hard- coded version. This allows us to install the corporate CAs just once, and then file a bug against any package that *doesn't* then trust them. See https://fedoraproject.org/wiki/Features/SharedSystemCertificates for some of the historical details from when this feature was first implemented, but this is all now supported upstream and not at all distribution-specific. There shouldn't be any significant work required; it's mostly just a case of configuring and building it to make use of this functionality. (With 'alternatives' to let you substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773148] Re: /lib/systemd/systemd-journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate
Verified with systemd/237-3ubuntu10.31: root@x-lp1773859:~# systemctl show systemd-journald.service | grep Watch WatchdogUSec=0 WatchdogTimestamp=Tue 2019-10-08 16:06:56 UTC WatchdogTimestampMonotonic=176241732389 root@x-lp1773859:~# dpkg -l systemd Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== ii systemd237-3ubuntu10.31 amd64system and service manager The fix is applied in .31, but the crash was still be observed once: https://errors.ubuntu.com/?release=Ubuntu%2018.04=systemd=month=237-3ubuntu10.31 This seem to have been misreported against the version, since the ExecutableTimestamp is 1567655991 (date -d @1567655991 : Thu Sep 5 03:59:51 UTC 2019) , which matches the timestamp of /lib/systemd /systemd-journald in 237-3ubuntu10.29 . ** 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1773148 Title: /lib/systemd/systemd- journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate Status in systemd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * systemd aborts journald, upon watchdog expiry and generates lots of crash reports * it appears that journald is simply stuck in fsync * it has been agreed to disable watchdog timer on journald [Test Case] * watch drop-off of errors w.r.t. watchdog timer [Regression Potential] * Potentially journald does get stuck, and thus is no longer automatically restarted with a sigabrt crash. However, so far, it is not known to do that. [Other Info] * Original bug report The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 237-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1773148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
https://errors.ubuntu.com/?release=Ubuntu%2018.04=systemd=month=237-3ubuntu10.31 For the record the 16.04 -> 18.04 upgrade issue is still seen: https://errors.ubuntu.com/?release=Ubuntu%2018.04=systemd=month=237-3ubuntu10.31 While the added Conflicts does work in the test case it does not seem to fix the upgrade in all cases and a follow-up fix may be needed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: Fix Committed Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial, ie. lxc launch ubuntu-daily:xenial test-shim-upgrade lxc exec test-shim-upgrade apt update apt install systemd-shim wget https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb apt install ./systemd-shim_10-3_amd64.deb sed 's/xenial/bionic/' -i /etc/apt/sources.list apt update apt install systemd this currently passes, however, systemd-shim remains installed. It should be removed instead. Apt install systemd should have lines like this: The following packages will be REMOVED: systemd-shim ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' ... [Regression Potential] * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797415] Re: DNS stops working when disconnecting PPTP VPN on desktop
*** This bug is a duplicate of bug 1778946 *** https://bugs.launchpad.net/bugs/1778946 This is happening for me as well. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1797415 Title: DNS stops working when disconnecting PPTP VPN on desktop Status in systemd package in Ubuntu: Confirmed Bug description: On Cosmic I was testing some VPN setups. I created a PPTP VPN connection to my server. Everything connected and worked as it should. When I disconnect the VPN, DNS resolution stops working. Looking at "systemd-resolve --status" shows that the correct DNS server is listed for the interface when the connection is torn down, and I can ping it. Doing a nslookup setting the server to the IP address shown in --status shows that DNS resolution is working correctly. resolv.conf says nameserver 127.0.0.53 Restart resolved makes things work again. (Also, restarting Network Manager makes it work again.) Trying to ping a hostname from the cli when in the broken state yields zero output from resolved logs when in debug mode. Almost like it's not even hitting resolved, so this bug could very well be somewhere else. I've checked, and I can ping 127.0.0.1 and the default routes look OK, although there is a route to the VPN server left over. I'm all out of ideas. Any ideas? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
Verified with systemd 237-3ubuntu10.31: root@x-lp1773859:~# apt install ./systemd-shim_10-3_amd64.deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'systemd-shim' instead of './systemd-shim_10-3_amd64.deb' The following package was automatically installed and is no longer required: libfreetype6 Use 'apt autoremove' to remove it. Suggested packages: pm-utils The following packages will be upgraded: systemd-shim 1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Need to get 0 B/20.0 kB of archives. After this operation, 6144 B of additional disk space will be used. Get:1 /root/systemd-shim_10-3_amd64.deb systemd-shim amd64 10-3 [20.0 kB] (Reading database ... 25776 files and directories currently installed.) Preparing to unpack .../systemd-shim_10-3_amd64.deb ... Leaving 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' Unpacking systemd-shim (10-3) over (9-1bzr4ubuntu1) ... Processing triggers for dbus (1.10.6-1ubuntu3.4) ... Setting up systemd-shim (10-3) ... N: Can't drop privileges for downloading as file '/root/systemd-shim_10-3_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) root@x-lp1773859:~# sed 's/xenial/bionic/' -i /etc/apt/sources.list root@x-lp1773859:~# apt update Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB] ... Get:32 http://security.ubuntu.com/ubuntu bionic-security/multiverse Translation-en [2428 B] Fetched 19.7 MB in 3s (5284 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 396 packages can be upgraded. Run 'apt list --upgradable' to see them. root@x-lp1773859:~# sed -i s/backports/proposed/ /etc/apt/sources.list root@x-lp1773859:~# apt update Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease Get:3 http://archive.ubuntu.com/ubuntu bionic-proposed InRelease [242 kB] Hit:4 http://security.ubuntu.com/ubuntu bionic-security InRelease ... Get:12 http://archive.ubuntu.com/ubuntu bionic-proposed/multiverse Translation-en [572 B] Fetched 401 kB in 1s (349 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 396 packages can be upgraded. Run 'apt list --upgradable' to see them. root@x-lp1773859:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: cgmanager libcgmanager0 libfreetype6 Use 'apt autoremove' to remove them. The following additional packages will be installed: libargon2-0 libc-bin libc6 libcryptsetup12 libgcrypt20 libgpg-error0 libip4tc0 libjson-c3 libpam-systemd libsystemd0 locales networkd-dispatcher Suggested packages: glibc-doc rng-tools iw | wireless-tools systemd-container The following packages will be REMOVED: systemd-shim The following NEW packages will be installed: libargon2-0 libcryptsetup12 libip4tc0 libjson-c3 networkd-dispatcher The following packages will be upgraded: libc-bin libc6 libgcrypt20 libgpg-error0 libpam-systemd libsystemd0 locales systemd 8 upgraded, 5 newly installed, 1 to remove and 388 not upgraded. Need to get 11.0 MB of archives. After this operation, 4192 kB disk space will be freed. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic/main amd64 locales all 2.27-3ubuntu1 [3612 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic/main amd64 libc6 amd64 2.27-3ubuntu1 [2824 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic/main amd64 libc-bin amd64 2.27-3ubuntu1 [641 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic/main amd64 libgpg-error0 amd64 1.27-6 [38.0 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libgcrypt20 amd64 1.8.1-4ubuntu1.1 [418 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic/main amd64 libargon2-0 amd64 0~20161029-1.1 [19.9 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic/main amd64 libjson-c3 amd64 0.12.1-1.3 [21.4 kB] Get:8 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libcryptsetup12 amd64 2:2.0.2-1ubuntu1.1 [134 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic/main amd64 libip4tc0 amd64 1.6.1-2ubuntu2 [19.6 kB] Get:10 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libpam-systemd amd64 237-3ubuntu10.31 [108 kB] Get:11 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libsystemd0 amd64 237-3ubuntu10.31 [204 kB] Get:12 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 systemd amd64 237-3ubuntu10.31 [2904 kB] Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 networkd-dispatcher all 1.7-0ubuntu3.3 [13.3 kB] Fetched 11.0 MB in 0s (82.4 MB/s) Preconfiguring
[Touch-packages] [Bug 1843394]
Thank you Jan! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1843394 Title: FTBFS in Eoan - Error: operand type mismatch for `push' - gcc 9.2.1 / binutils 2.32.51.20190905-0ubuntu1 Status in binutils: Fix Released Status in binutils package in Ubuntu: New Status in ipxe package in Ubuntu: Invalid Bug description: This might be due to new gcc-9 being more strict, but the build that worked before now fails with: arch/x86_64/core/gdbidt.S: Assembler messages: arch/x86_64/core/gdbidt.S:109: Error: operand type mismatch for `push' arch/x86_64/core/gdbidt.S:110: Error: operand type mismatch for `push' arch/x86_64/core/gdbidt.S:161: Error: operand type mismatch for `pop' arch/x86_64/core/gdbidt.S:162: Error: operand type mismatch for `pop' make[2]: *** [Makefile.housekeeping:937: bin-x86_64-efi/gdbidt.o] Error 1 Full log at: https://launchpadlibrarian.net/441262285/buildlog_ubuntu- eoan-amd64.ipxe_1.0.0+git-20190109.133f4c4-0ubuntu2_BUILDING.txt.gz Now all of this is about push/pop of %fs and %gs. That needs to match the size of the registers which depend on the current running mode. In this particular case in ./src/arch/x86_64/core/gdbidt.S The failing file is in ".code64" mode. In that I'd expect %gs/%fs to be 64 bit. Usually we see push/pop "w" in .code16 (word), l in .code32 (long) but in that sense here q (quad word) seems right at first (should be what correctly matches the .code64). That matches what I see throughout the ipxe code but also throughout the archive https://codesearch.debian.net/search?q=pop%5Ba-z%5D.*%25fs=0=2 Maybe I misread the mode it is in, or it is actually a false positives. Or the sizes of FS/GS do not change - haven't touched them in a lng time. Was it that segment registers didn't change size? I'll need to do a few checks to first see what the compiler would expect there and from there need to understand this. The command used also points to AS being in 64 bit mode when this happens: gcc -E -DARCH=x86_64 -DPLATFORM=efi -DSECUREBOOT=0 -fstrength-reduce -fomit-frame-pointer -falign-jumps=1 -falign-loops=1 -falign-functions=1 -m64 -mno-mmx -mno-sse -fshort-wchar -Ui386 -Ulinux -DNVALGRIND -fpie -mno-red-zone -Iinclude -I. -Iarch/x86/include -Iarch/x86_64/include -Iarch/x86_64/include/efi -Os -g -ffreestanding -Wall -W -Wformat-nonliteral -fno-stack-protector -fno-dwarf2-cfi-asm -fno-exceptions -fno-unwind-tables -fno-asynchronous-unwind-tables -Wno-address -Wno-stringop-truncation -ffunction-sections -fdata-sections -include include/compiler.h -DASM_TCHAR='@' -DASM_TCHAR_OPS='@' -DASSEMBLY -DOBJECT=gdbidt arch/x86_64/core/gdbidt.S | as --64-o bin-x86_64-efi/gdbidt.o To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1843394/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350096] Re: [Apps Scope] Creating a new account directly on the phone leads to an unconfirmed account without informing the user
** Changed in: canonical-identity-provider Status: New => Won't Fix ** Changed in: ubuntuone-servers Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntuone-credentials in Ubuntu. https://bugs.launchpad.net/bugs/1350096 Title: [Apps Scope] Creating a new account directly on the phone leads to an unconfirmed account without informing the user Status in Canonical SSO provider: Won't Fix Status in Software Center Agent: Fix Released Status in Ubuntu UX: Fix Released Status in Ubuntu One Servers: Won't Fix Status in ubuntuone-credentials package in Ubuntu: Invalid Status in unity-scope-click package in Ubuntu: Invalid Bug description: Steps to reproduce: * Remove any Ubuntu One account from the phone * Try to install an app from the apps store * Set up a *new* Ubuntu One account (not signing in with an existing one) => The account seems to be fully set up, however, installing apps results in an error "Installation failed". What happens is the email address is not confirmed yet and thus the login doesn't work yet. There should be some indication that the user should check emails and confirm the address. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-identity-provider/+bug/1350096/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
no-one knows what to backport -- 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in mesa package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845652] Re: rsync sends everything, not just changes
When using vfat and running rsync twice, this is the diff in the stats output: --- log1.vfat 2019-10-08 11:43:04.381667860 -0300 +++ log2.vfat 2019-10-08 11:43:17.609728451 -0300 @@ -1,5 +1,5 @@ Number of files: 78 (reg: 77, dir: 1) -Number of created files: 77 (reg: 77) +Number of created files: 0 Number of deleted files: 0 Number of regular files transferred: 77 Total file size: 3,990,531 bytes @@ -12,6 +12,6 @@ Total bytes sent: 3,996,271 Total bytes received: 8,830 -sent 3,996,271 bytes received 8,830 bytes 534,013.47 bytes/sec +sent 3,996,271 bytes received 8,830 bytes 2,670,067.33 bytes/sec total size is 3,990,531 speedup is 1.00 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1196) [sender=3.1.2] As expected, the files are transferred again, because rsync couldn't set the permissions or ownership. These concepts don't exist in vfat. When using ext4, the same rsync command, the diff between the two runs shows a different story: --- log1.ext4 2019-10-08 11:49:01.687411326 -0300 +++ log2.ext4 2019-10-08 11:49:11.795461543 -0300 @@ -1,16 +1,16 @@ Number of files: 78 (reg: 77, dir: 1) -Number of created files: 77 (reg: 77) -Number of deleted files: 1 (dir: 1) -Number of regular files transferred: 77 +Number of created files: 0 +Number of deleted files: 0 +Number of regular files transferred: 0 Total file size: 3,990,531 bytes -Total transferred file size: 3,990,531 bytes -Literal data: 3,990,531 bytes +Total transferred file size: 0 bytes +Literal data: 0 bytes Matched data: 0 bytes File list size: 0 File list generation time: 0.001 seconds File list transfer time: 0.000 seconds -Total bytes sent: 3,996,271 -Total bytes received: 1,504 +Total bytes sent: 1,598 +Total bytes received: 19 -sent 3,996,271 bytes received 1,504 bytes 7,995,550.00 bytes/sec -total size is 3,990,531 speedup is 1.00 +sent 1,598 bytes received 19 bytes 3,234.00 bytes/sec +total size is 3,990,531 speedup is 2,467.86 The rsync command I used was: rsync -v -a -r -W -p -o -g -t --delete --stats /testdata/ /media/andreas/dataext4/ /testdata was populated with a copy of all files in /usr/bin that start with "b*". I don't think the --exclusion parameters you used play a factor here. Can you please verify the target filesystem in your test case, and if rsync reported errors? And there are other scenarios, like outlined in comment #2. I guess, to summarize, we need a testcase. I showed you two cases with pendrives (vfat, and ext4), where what you describe does NOT happen. ** Changed in: rsync (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1845652 Title: rsync sends everything, not just changes Status in rsync package in Ubuntu: Incomplete Bug description: Repeated runs of rsync from PC to USB key send everything, not just the changes. This is reproducible. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: rsync 3.1.3-6 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 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 09:18:19 2019 InstallationDate: Installed on 2019-06-10 (109 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1845652/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846208] Re: [MIR] abootimg (dependency of initramfs-tools-ubuntu-core)
To ellaborate, this is used by initramfs-tools-ubuntu-core as needed by snapd for the Ubuntu Core product. If that is all true, imho snappy team should be the bug subscriber and drive the MIR to completion. If it doesn't use/need abootimg the dependency should be dropped. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to abootimg in Ubuntu. https://bugs.launchpad.net/bugs/1846208 Title: [MIR] abootimg (dependency of initramfs-tools-ubuntu-core) Status in abootimg package in Ubuntu: Incomplete Bug description: needs a MIR (or removal of the dependency): abootimg (dependency of initramfs-tools-ubuntu-core) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/abootimg/+bug/1846208/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too
According to the logs in the #1, there is no obvious errors. Please open the gnome-sound-setting, then plug a headphone, does the headphone shows up in the UI after you plug the headphone. If a headphone shows up, then select that headphone from UI, and play some sound to headphone, if there is no sound from headphone, please run alsa-info and pactl list, then upload two logs to lp. thx. -- 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/1846930 Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too Status in alsa-driver package in Ubuntu: New Bug description: Any progress? Cannot hear anything nor record anything out my asrock fm2a75m-dgs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hh 1267 F pulseaudio /dev/snd/controlC0: hh 1267 F pulseaudio CurrentDesktop: XFCE Date: Sun Oct 6 09:27:53 2019 InstallationDate: Installed on 2019-03-31 (188 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hh 1267 F pulseaudio /dev/snd/controlC0: hh 1267 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-25T18:19:18.090642 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846930/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument
** Tags added: disco eoan -- 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/1597415 Title: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Hi, the symptom is this error message in my system's logs: juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument According to /proc/bus/input/devices the corresponding input device is: I: Bus=0019 Vendor= Product= Version= N: Name="Dell WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input10 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=13 B: KEY=1000b0400 0 e 0 B: MSC=10 This laptop is a Dell Latitude E6520. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu6 Uname: Linux 4.6.3-040603-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE CustomUdevRuleFiles: 60-ssd-scheduler.rules Date: Wed Jun 29 17:43:01 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1826639 Title: wpasupplicant: unknown keys in no-mac-addr-change.conf Status in wpa package in Ubuntu: Confirmed Bug description: Hi, NetworkManager warns that no-mac-addr-change.conf contains unknown configuration directives: # journalctl | grep no-mac-addr-change Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 10-globally-managed-devices.conf, default-wifi-powersave-on.conf) Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'ethernet.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: wpasupplicant 2:2.6-21ubuntu3 Uname: Linux 5.0.9-050009-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 27 13:15:27 2019 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847216] Re: motd-news only works with one URL even though docs say mutiple URLs can be configured
** Changed in: base-files (Ubuntu) Status: New => Triaged ** Changed in: base-files (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1847216 Title: motd-news only works with one URL even though docs say mutiple URLs can be configured Status in base-files package in Ubuntu: Triaged Bug description: The motd-news script etc/update-motd/50-motd-news the following section ``` # Loop over any configured URLs for u in $URLS; do # Ensure https:// protocol, for security reasons case $u in https://*) true ;; https://motd.ubuntu.com) u="$u/$codename/$arch" ;; *) continue ;; esac # If we're forced, set the wait to much higher (1 minute) [ "$FORCED" = "1" ] && WAIT=60 # Fetch and print the news motd if curl --connect-timeout "$WAIT" --max-time "$WAIT" -A "$USER_AGENT" -o- "$u" >"$NEWS" 2>"$ERR"; then echo # At most, 10 lines of text, remove control characters, print at most 80 characters per line safe_print "$NEWS" # Try to update the cache safe_print "$NEWS" 2>/dev/null >$CACHE || true else : > "$CACHE" fi done ``` As you can see the $CACHE gets overwritten if multiple URLs are configured in /etc/default/motd-news /etc/default/motd-news has ``` # Configure the source of dynamic MOTD news # White space separated list of 0 to many news services # For security reasons, these must be https # and have a valid certificate # Canonical runs a service at motd.ubuntu.com, and you # can easily run one too URLS="https://motd.ubuntu.com; ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1847216/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
verified with 237-3ubuntu10.31: root@bb-lp1670291:~# dpkg -l systemd Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== ii systemd237-3ubuntu10.31 amd64system and service manager root@bb-lp1670291:~# systemctl mask systemd-logind.service Created symlink /etc/systemd/system/systemd-logind.service → /dev/null. root@bb-lp1670291:~# systemctl stop systemd-logind.service root@bb-lp1670291:~#shutdown +1 Failed to set wall message, ignoring: Unit systemd-logind.service is masked. Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Unit systemd-logind.service is masked. Session terminated, terminating shell...rbalint@yogi:~$ lxc shell bb-lp1670291 Error: Container is not running rbalint@yogi:~$ lxc shell bb-lp1670291 Error: Container is not running rbalint@yogi:~$ lxc start bb-lp1670291 rbalint@yogi:~$ lxc shell bb-lp1670291 mesg: ttyname failed: No such device root@bb-lp1670291:~# uptime 12:23:38 up 0 min, 0 users, load average: 3.02, 2.14, 1.86 root@bb-lp1670291:~# with unfixed reference version: rbalint@yogi:~$ lxc shell bb-lp1670291-ref mesg: ttyname failed: No such device root@bb-lp1670291-ref:~# systemctl mask systemd-logind.service Created symlink /etc/systemd/system/systemd-logind.service → /dev/null. root@bb-lp1670291-ref:~# systemctl stop systemd-logind.service root@bb-lp1670291-ref:~#shutdown +1 Failed to set wall message, ignoring: Unit systemd-logind.service is masked. Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Unit systemd-logind.service is masked. root@bb-lp1670291-ref:~# dpkg -l systemd Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===---=== ii systemd 237-3ubuntu10.29 amd64system and service manager root@bb-lp1670291-ref:~# uptime 12:23:49 up 6 min, 0 users, load average: 2.70, 2.10, 1.85 root@bb-lp1670291-ref:~# ** 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Trusty: Fix Released Status in systemd source package in Trusty: New Status in landscape-client source package in Xenial: Fix Released Status in systemd source package in Xenial: Fix Released Status in landscape-client source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Committed Status in landscape-client source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist =
[Touch-packages] [Bug 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image
I also set verification-done, since it is verified that the bug does not occur with .31 . -- 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/1784454 Title: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image Status in Ubuntu on IBM z Systems: Fix Released Status in debian-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Invalid Bug description: Booting d-i based on kernel 4.4 (from ./boot folder) from the 16.04.5 RC image on a z/VM guest leads to a kernel panic: /lib/debian-installer/start-udev: line 15: can't create /sys/module/scsi_mod/par ameters/scan: Permission denied ¬0.845071| Kernel panic - not syncing: Attempted to kill initÜ exitcode=0x00 000100 ¬0.845071| ¬0.845075| CPU: 0 PID: 1 Comm: /init Not tainted 4.4.0-131-generic #157-Ubun tu ¬0.845077|7d107c20 7d107cb0 0002 000 0 7d107d50 7d107cc8 7d107cc8 00114732 008b 009a304c 009f11d0 000b 7d107d10 7d107cb0 040001cdf800 00114732 7d107cb0 7d107d10 ¬0.845089| Call Trace: ¬0.845093| (¬<0011461a>| show_trace+0xfa/0x150) ¬0.845095| ¬<001146e2>| show_stack+0x72/0xf8 ¬0.845099| ¬<00555752>| dump_stack+0x82/0xb8 ¬0.845101| ¬<00286390>| panic+0x108/0x250 ¬0.845104| ¬<00166228>| do_exit+0xac0/0xba0 ¬0.845106| ¬<001663c8>| do_group_exit+0x50/0xe0 ¬0.845108| ¬<00166488>| __wake_up_parent+0x0/0x28 ¬0.845111| ¬<007eadda>| system_call+0xee/0x28c ¬0.845113| ¬<03ff8953983a>| 0x3ff8953983a 00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 0010F8CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image
@frank-heimes, thank you for the testing and also for your additional comments. This fix was once accepted to bionic-proposed, while it does not have a test case in the bug description nor the description follows the SRU template: https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template . Ensuring that is the job of the SRU uploader, and the first time is was skipped and I also missed that. Since the bug did not exist in 18.04 I'm marking it invalid instead of performing the SRU again. ** Changed in: systemd (Ubuntu Bionic) Status: Incomplete => Invalid ** 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1784454 Title: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image Status in Ubuntu on IBM z Systems: Fix Released Status in debian-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Invalid Bug description: Booting d-i based on kernel 4.4 (from ./boot folder) from the 16.04.5 RC image on a z/VM guest leads to a kernel panic: /lib/debian-installer/start-udev: line 15: can't create /sys/module/scsi_mod/par ameters/scan: Permission denied ¬0.845071| Kernel panic - not syncing: Attempted to kill initÜ exitcode=0x00 000100 ¬0.845071| ¬0.845075| CPU: 0 PID: 1 Comm: /init Not tainted 4.4.0-131-generic #157-Ubun tu ¬0.845077|7d107c20 7d107cb0 0002 000 0 7d107d50 7d107cc8 7d107cc8 00114732 008b 009a304c 009f11d0 000b 7d107d10 7d107cb0 040001cdf800 00114732 7d107cb0 7d107d10 ¬0.845089| Call Trace: ¬0.845093| (¬<0011461a>| show_trace+0xfa/0x150) ¬0.845095| ¬<001146e2>| show_stack+0x72/0xf8 ¬0.845099| ¬<00555752>| dump_stack+0x82/0xb8 ¬0.845101| ¬<00286390>| panic+0x108/0x250 ¬0.845104| ¬<00166228>| do_exit+0xac0/0xba0 ¬0.845106| ¬<001663c8>| do_group_exit+0x50/0xe0 ¬0.845108| ¬<00166488>| __wake_up_parent+0x0/0x28 ¬0.845111| ¬<007eadda>| system_call+0xee/0x28c ¬0.845113| ¬<03ff8953983a>| 0x3ff8953983a 00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 0010F8CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez
there's a lot of people subscribed to this bug, and presumably interested in seeing it fixed on Bionic; can any of you please test with the package from bionic-proposed and report the results? Until you do, it's unlikely this fix will be released into bionic-updates. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Or you can directly download the proposed debs from this (amd64) build page: https://launchpad.net/ubuntu/+source/bluez/5.48-0ubuntu3.2/+build/17810460 please someone test on Bionic! -- 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/1759836 Title: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in bluez source package in Bionic: Fix Committed Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Invalid Status in bluez source package in Disco: Fix Released Status in linux source package in Disco: Invalid Status in systemd source package in Disco: Invalid Status in bluez source package in Eoan: Fix Released Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: Invalid Status in bluez package in Debian: New Bug description: [impact] on specific Dell systems, with a specific usb bluetooth device built- in, the udev rule 'hid2hci' provided by the 'bluez' package causes an endless loop of uevents resulting from 'bind' or 'unbind' kernel uevents. These new events were added to the kernel after the 'hid2hci' udev rule was written. [test case] the specific Dell system is required to be able to reproduce this, or at least the specific usb bluetooth hardware included in that system. Reproducing this is reportedly easy, for example comment 75 indicates it happens on every boot. When this happens, any process monitor (e.g. ps, top, etc) will show the 'udevd' process using 100% of a cpu, and 'udevadm monitor' should show repeated 'bind' and 'unbind' events as mentioned in comment 39. [regression potential] as this alters what kernel uevents the 'hid2hci' udev rule processes, regressions would involve the affected usb bluetooth device failing to be set up, or otherwise not processing the uevents correctly. [other info] this is not fixed yet upstream, as of my last check, but has been submitted upstream as mentioned in comment 95. original description: -- The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd
** Changed in: openldap (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1821343 Title: slapd process failure is not detected by systemd Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Xenial: Fix Released Status in openldap source package in Bionic: Fix Released Status in openldap source package in Cosmic: Fix Released Status in openldap package in Debian: Fix Released Bug description: [Impact] Systemd service reports slapd as active, even though it may have failed [Description] The slapd package for OpenLDAP is shipped with a SysV-style init script (/etc/init.d/slapd). Systemd automatically converts this to a systemd service by generating the unit file using the systemd-sysv-generator(8) utility. The generated unit file contains Type=forking and RemainAfterExit=yes directives. If the slapd daemon process exits due to some failure (e.g., it receives a SIGTERM or SIGKILL), the failure is not detected properly by systemd. The service is still reported as active even though the child (daemon) process has exited with a signal. We can easily fix this by including a proper systemd service file for slapd in the openldap package. Since the init.d script already does most of the necessary work (parsing configs, setting up PID files, etc.), we don't need anything complicated for the systemd unit file. Just making sure that RemainAfterExit is set to "no" makes the systemd service behave in the expected way. [Test Case] 1) Deploy a disco container $ lxc launch images:ubuntu/disco disco 2) Install slapd ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y 3) Verify that slapd is running with the auto-generated service ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) Tasks: 3 (limit: 4915) Memory: 712.6M CGroup: /system.slice/slapd.service └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u openldap -F /etc/ldap/slapd.d 4) SIGKILL the slapd process (PID is displayed in systemctl status output) ubuntu@disco:~$ sudo kill -9 1109 5) Check if systemd service lists slapd as still active, even though it was terminated ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) 6) Check if systemd has loaded both /run/systemd/generator.late/slapd.service & /usr/lib/systemd/system/slapd.service.d/slapd-remain-after-exit.conf $ systemctl cat slapd [Regression Potential] The regression potential for this fix should be very low, if we keep the new systemd unit file close to the one generated by systemd-sysv-generator(8). The only significant change would be the RemainAfterExit directive, and this should make the slapd service behave like a "normal" forking service. Nonetheless, we'll perform scripted test runs to make sure no regressions arise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers
The fix is trivial, so this should be fine. But I'm just back from PTO and a bit swamped by TODOs right now, so bear with me as I'll need some time :-) ** Also affects: rsyslog (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: rsyslog (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: rsyslog (Ubuntu Bionic) Status: New => Triaged ** Changed in: rsyslog (Ubuntu Disco) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1827253 Title: [apparmor] missing 'mr' on binary for usage on containers Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Bionic: Triaged Status in rsyslog source package in Disco: Triaged Bug description: Issue description: Enabling the rsyslog (disabled by default) Apparmor profile causes rsyslog to fail to start when running *inside a container*. Steps to reproduce: 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog Workaround: echo ' /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog Additional information: root@rs1:~# uname -a Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@rs1:~# lsb_release -rd Description: Ubuntu Eoan EANIMAL (development branch) Release: 19.10 root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog' ii apparmor 2.13.2-9ubuntu6 amd64user-space parser utility for AppArmor ii rsyslog 8.32.0-1ubuntu7 amd64reliable system and kernel logging daemon ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: rsyslog 8.32.0-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed May 1 17:36:29 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1746527] Re: Systemd User Service Cannot Start with ECryptFS Due to PAM Misconfiguration
*** This bug is a duplicate of bug 1734290 *** https://bugs.launchpad.net/bugs/1734290 ** This bug has been marked a duplicate of bug 1734290 ecryptfs decrypts home AFTER systemd user daemon is loaded. trouble ensues… -- 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/1746527 Title: Systemd User Service Cannot Start with ECryptFS Due to PAM Misconfiguration Status in systemd package in Ubuntu: Confirmed Bug description: If a user encrypts their home directory using the standard Ubuntu installer GUI, which uses ecryptfs, then the users home directory is encrypted while systemd is trying to start their user services so they cant be read. After consulting with the systemd developers, the problem is remarkably simple to fix Ubuntu releases /etc/pam.d/common-session with the follow entries: session optionalpam_systemd.so session optionalpam_ecryptfs.so unwrap they need to be swapped to session optionalpam_ecryptfs.so unwrap session optionalpam_systemd.so so that decryption happens before systemd user services are started. Check the thread on the systemd developers mailing list at https://lists.freedesktop.org/archives/systemd- devel/2018-January/040301.html for further information ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.1 Uname: Linux 4.14.4-acso x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 09:25:10 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (87 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. XPS 15 9560 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.14.4-acso root=/dev/mapper/ubuntu--vg-root ro quiet splash intel_iommu=on pci=noaer pcie_acs_override=downstream vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1746527/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838525] Re: LVM setup fails to install grub on virtio storage
** Changed in: debian-installer (Ubuntu) Status: In Progress => Invalid ** Changed in: lvm2 (Ubuntu) Status: In Progress => Invalid ** Changed in: debian-installer (Ubuntu) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: lvm2 (Ubuntu) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: debian-installer (Ubuntu) Importance: Critical => Undecided ** Changed in: lvm2 (Ubuntu) Importance: Critical => Undecided -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1838525 Title: LVM setup fails to install grub on virtio storage Status in debian-installer package in Ubuntu: Invalid Status in grub2 package in Ubuntu: Fix Committed Status in lvm2 package in Ubuntu: Invalid Status in debian-installer package in Debian: New Bug description: [Impact] * Any Eoan installation that depends on latest installer will face this issue when final user chooses LVM full disk partitioning type. * Grub won't be able to install due to bad bootdevice variable in the installer. It will try to install grub to "/dev/mapper" and will fail. The default boot option will also be "/dev/mapper". [Test Case] * Download netboot files from current installer (vmlinuz and initrd files). * Create a KVM guest running from these files, with a NIC connected to the internet. * Initiate a network installation inside the KVM guest, choosing the Entire Disk - LVM partitioning option. * Wait installation to finish and to start the grub-install phase. It will ask where to install grub, having, as default, "/dev/mapper". By default, it might simply try to grub-install /dev/mapper, which will also fail. * That happens because /dev/disk/by-id/ has an unexpected (by the installer) symlink added by lvm2 package that grub-installer (used by debian-installer) does not expect (when using grub-mkdevice command). [Simplified Test Case] * To add a PV + VG + LVM in a KVM guest to an empty virtio disk, for example, and to check if the command: grub-mkdevicemap --no-floppy -m - lists /dev/vdX1 in front of /dev/vdX. This will be a sign that: /dev/disk/by-id/*lvm* file exists and will be enough to confuse installer. [Regression Potential] There are 3 alternatives to fix this and I have chosen the one I believe has the smaller potential for any type of regression. Comment #30 describes what caused the regression and these 3 alternatives: (1) To revert this change for current release, since this rule was added to "make navigation a bit easier using PV UUIDs", as the commit says. We would worry about installer changes in the next release. (2) Another possibility would be to change the logic inside "grub- mkdevicemap.c: make_device_map()->grub_util_iterate_devices()" to ignore all symlinks from /dev/disk/by-id/ containing lvm-pv-uuid-*. We would not have to worry about this in the next release if using debian-installer. (3) Another option would be to change grub-installer package/logic. Unfortunately, a few days before the full freeze, I don't think messing with the installer would be a good option to avoid regressions (potential regression item would grow in significance). => I'm choosing (2) because ubuntu foundations already faced a similar situation, when grub-mkdevicemap.c file was removed from grub2 code and they re-added it by using a quilt patch, assuming it was the easiest and better to maintain. I'm doing something similar, patching the patch that creates grub-mkdevicemap.c file again to ignore /dev/disk/by-id/lvm-pv-uuid-* files (like it already does for other symlinks, actually). [Other Info] Comment #26 has the TL;DR version of the problem. https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/comments/26 [Original Description] The Eoan debian-installer ISO fails to install GRUB on LVM installs with virtio storage, as it runs grub-install with /dev/mapper as a target (a directory), even if instructed to target a device. The following steps to reproduce have been prepared running the 20190730 build, but this has been broken since about June 18, 2019. Steps to reproduce: $ md5sum eoan-server-amd64.iso f591e30485e5f0b5117f6c116e538c42 eoan-server-amd64.iso $ qemu-img create -f raw disk1.img 8G Formatting 'disk1.img', fmt=raw size=8589934592 $ kvm -m 1024 -boot d -cdrom eoan-server-amd64.iso -drive file=disk1.img,if=virtio Proceed with all the defaults. In the "Partition disk" step select "Guided - use entire disk and set up LVM". Go ahead accepting the defaults. At the "Install the GRUB boot loader" step select "/dev/vda" as the target device. The installer will actually run `grub-install --force /dev/mapper` and fail after a while. The wrong command is
[Touch-packages] [Bug 1843394] Re: FTBFS in Eoan - Error: operand type mismatch for `push' - gcc 9.2.1 / binutils 2.32.51.20190905-0ubuntu1
Now after we have understood it we know the fix is actually in binutils. Furthermore any other third party code (or even a few other FTBFS in Eoan) could be due to that. IMHO that is a high prio to fix before Eoan as it would not be a new bug bur a regression. I'll set it as critical, but it is up to you having more experience in such issues. @Doko - can we get this fixed in Eoan? ** Changed in: ipxe (Ubuntu) Assignee: Christian Ehrhardt (paelzer) => (unassigned) ** Changed in: ipxe (Ubuntu) Status: Triaged => Invalid ** Changed in: binutils (Ubuntu) Importance: Undecided => Critical ** Changed in: binutils (Ubuntu) Assignee: (unassigned) => Matthias Klose (doko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1843394 Title: FTBFS in Eoan - Error: operand type mismatch for `push' - gcc 9.2.1 / binutils 2.32.51.20190905-0ubuntu1 Status in binutils: Fix Released Status in binutils package in Ubuntu: New Status in ipxe package in Ubuntu: Invalid Bug description: This might be due to new gcc-9 being more strict, but the build that worked before now fails with: arch/x86_64/core/gdbidt.S: Assembler messages: arch/x86_64/core/gdbidt.S:109: Error: operand type mismatch for `push' arch/x86_64/core/gdbidt.S:110: Error: operand type mismatch for `push' arch/x86_64/core/gdbidt.S:161: Error: operand type mismatch for `pop' arch/x86_64/core/gdbidt.S:162: Error: operand type mismatch for `pop' make[2]: *** [Makefile.housekeeping:937: bin-x86_64-efi/gdbidt.o] Error 1 Full log at: https://launchpadlibrarian.net/441262285/buildlog_ubuntu- eoan-amd64.ipxe_1.0.0+git-20190109.133f4c4-0ubuntu2_BUILDING.txt.gz Now all of this is about push/pop of %fs and %gs. That needs to match the size of the registers which depend on the current running mode. In this particular case in ./src/arch/x86_64/core/gdbidt.S The failing file is in ".code64" mode. In that I'd expect %gs/%fs to be 64 bit. Usually we see push/pop "w" in .code16 (word), l in .code32 (long) but in that sense here q (quad word) seems right at first (should be what correctly matches the .code64). That matches what I see throughout the ipxe code but also throughout the archive https://codesearch.debian.net/search?q=pop%5Ba-z%5D.*%25fs=0=2 Maybe I misread the mode it is in, or it is actually a false positives. Or the sizes of FS/GS do not change - haven't touched them in a lng time. Was it that segment registers didn't change size? I'll need to do a few checks to first see what the compiler would expect there and from there need to understand this. The command used also points to AS being in 64 bit mode when this happens: gcc -E -DARCH=x86_64 -DPLATFORM=efi -DSECUREBOOT=0 -fstrength-reduce -fomit-frame-pointer -falign-jumps=1 -falign-loops=1 -falign-functions=1 -m64 -mno-mmx -mno-sse -fshort-wchar -Ui386 -Ulinux -DNVALGRIND -fpie -mno-red-zone -Iinclude -I. -Iarch/x86/include -Iarch/x86_64/include -Iarch/x86_64/include/efi -Os -g -ffreestanding -Wall -W -Wformat-nonliteral -fno-stack-protector -fno-dwarf2-cfi-asm -fno-exceptions -fno-unwind-tables -fno-asynchronous-unwind-tables -Wno-address -Wno-stringop-truncation -ffunction-sections -fdata-sections -include include/compiler.h -DASM_TCHAR='@' -DASM_TCHAR_OPS='@' -DASSEMBLY -DOBJECT=gdbidt arch/x86_64/core/gdbidt.S | as --64-o bin-x86_64-efi/gdbidt.o To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1843394/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843733] Re: fftw3 ftbfs in eoan (armhf only)
persists: https://launchpad.net/ubuntu/+archive/test-rebuild-20190906/+build/17546506 ** Changed in: fftw3 (Ubuntu Eoan) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fftw3 in Ubuntu. https://bugs.launchpad.net/bugs/1843733 Title: fftw3 ftbfs in eoan (armhf only) Status in fftw3 package in Ubuntu: Confirmed Status in fftw3 source package in Eoan: Confirmed Bug description: fftw3 ftbfs in eoan (armhf only). https://launchpadlibrarian.net/441265031/buildlog_ubuntu-eoan- armhf.fftw3_3.3.8-2_BUILDING.txt.gz ( cd tests ; /usr/bin/make smallcheck ) make[1]: Entering directory '/<>/tests' perl -w ./check.pl -r -c=1 -v `pwd`/bench Executing "/<>/tests/bench --verbose=1 --verify 'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304'" ok7e10x12bv29 1.71318e-07 1.44516e-06 2.00887e-07 ik7e10x12bv29 1.66737e-07 1.44901e-06 1.76717e-07 Segmentation fault (core dumped) FAILED /<>/tests/bench: --verify 'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304' make[1]: *** [Makefile:723: smallcheck] Error 1 make[1]: Leaving directory '/<>/tests' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1843733/+subscriptions -- Mailing list: https://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 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too
None of them, I cannot also record anything, the alc662 rev 2 analog realtek audio device does not work at all Il lunedì 7 ottobre 2019, 06:25:41 CEST, Hui Wang ha scritto: Do you mean the you can't hear sound from headphone or lineout jack? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1846930 Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too Status in alsa-driver package in Ubuntu: New Bug description: Any progress? Cannot hear anything nor record anything out my asrock fm2a75m-dgs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: hh 1267 F pulseaudio /dev/snd/controlC0: hh 1267 F pulseaudio CurrentDesktop: XFCE Date: Sun Oct 6 09:27:53 2019 InstallationDate: Installed on 2019-03-31 (188 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: hh 1267 F pulseaudio /dev/snd/controlC0: hh 1267 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-25T18:19:18.090642 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846930/+subscriptions -- 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/1846930 Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too Status in alsa-driver package in Ubuntu: New Bug description: Any progress? Cannot hear anything nor record anything out my asrock fm2a75m-dgs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hh 1267 F pulseaudio /dev/snd/controlC0: hh 1267 F pulseaudio CurrentDesktop: XFCE Date: Sun Oct 6 09:27:53 2019 InstallationDate: Installed on 2019-03-31 (188 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hh 1267 F pulseaudio /dev/snd/controlC0: hh 1267 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Touch-packages] [Bug 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken
I'm experiencing this issue with Ubuntu 19.04 resolvconf version: 1.79ubuntu13 Oct 6 21:30:19 miranda systemd[1]: Failed to start resolvconf-pull-resolved.service. Oct 6 21:30:19 miranda systemd[1]: resolvconf-pull-resolved.service: Start request repeated too quickly. Oct 6 21:30:19 miranda systemd[1]: resolvconf-pull-resolved.service: Failed with result 'start-limit-hit'. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1819625 Title: Package resolvconf=1.79ubuntu10.18.04.1 broken Status in resolvconf package in Ubuntu: Confirmed Status in resolvconf source package in Bionic: Fix Released Status in resolvconf source package in Cosmic: Fix Released Bug description: The package resolveconf version 1.79ubuntu10.18.04.1 is broken. Installing the package breaks DNS resolution. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu10.18.04.1 Uname: Linux 4.15.0-46-generic x86_64 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1819625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838525] Re: LVM setup fails to install grub on virtio storage
** Changed in: grub2 (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1838525 Title: LVM setup fails to install grub on virtio storage Status in debian-installer package in Ubuntu: In Progress Status in grub2 package in Ubuntu: Fix Committed Status in lvm2 package in Ubuntu: In Progress Status in debian-installer package in Debian: New Bug description: [Impact] * Any Eoan installation that depends on latest installer will face this issue when final user chooses LVM full disk partitioning type. * Grub won't be able to install due to bad bootdevice variable in the installer. It will try to install grub to "/dev/mapper" and will fail. The default boot option will also be "/dev/mapper". [Test Case] * Download netboot files from current installer (vmlinuz and initrd files). * Create a KVM guest running from these files, with a NIC connected to the internet. * Initiate a network installation inside the KVM guest, choosing the Entire Disk - LVM partitioning option. * Wait installation to finish and to start the grub-install phase. It will ask where to install grub, having, as default, "/dev/mapper". By default, it might simply try to grub-install /dev/mapper, which will also fail. * That happens because /dev/disk/by-id/ has an unexpected (by the installer) symlink added by lvm2 package that grub-installer (used by debian-installer) does not expect (when using grub-mkdevice command). [Simplified Test Case] * To add a PV + VG + LVM in a KVM guest to an empty virtio disk, for example, and to check if the command: grub-mkdevicemap --no-floppy -m - lists /dev/vdX1 in front of /dev/vdX. This will be a sign that: /dev/disk/by-id/*lvm* file exists and will be enough to confuse installer. [Regression Potential] There are 3 alternatives to fix this and I have chosen the one I believe has the smaller potential for any type of regression. Comment #30 describes what caused the regression and these 3 alternatives: (1) To revert this change for current release, since this rule was added to "make navigation a bit easier using PV UUIDs", as the commit says. We would worry about installer changes in the next release. (2) Another possibility would be to change the logic inside "grub- mkdevicemap.c: make_device_map()->grub_util_iterate_devices()" to ignore all symlinks from /dev/disk/by-id/ containing lvm-pv-uuid-*. We would not have to worry about this in the next release if using debian-installer. (3) Another option would be to change grub-installer package/logic. Unfortunately, a few days before the full freeze, I don't think messing with the installer would be a good option to avoid regressions (potential regression item would grow in significance). => I'm choosing (2) because ubuntu foundations already faced a similar situation, when grub-mkdevicemap.c file was removed from grub2 code and they re-added it by using a quilt patch, assuming it was the easiest and better to maintain. I'm doing something similar, patching the patch that creates grub-mkdevicemap.c file again to ignore /dev/disk/by-id/lvm-pv-uuid-* files (like it already does for other symlinks, actually). [Other Info] Comment #26 has the TL;DR version of the problem. https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/comments/26 [Original Description] The Eoan debian-installer ISO fails to install GRUB on LVM installs with virtio storage, as it runs grub-install with /dev/mapper as a target (a directory), even if instructed to target a device. The following steps to reproduce have been prepared running the 20190730 build, but this has been broken since about June 18, 2019. Steps to reproduce: $ md5sum eoan-server-amd64.iso f591e30485e5f0b5117f6c116e538c42 eoan-server-amd64.iso $ qemu-img create -f raw disk1.img 8G Formatting 'disk1.img', fmt=raw size=8589934592 $ kvm -m 1024 -boot d -cdrom eoan-server-amd64.iso -drive file=disk1.img,if=virtio Proceed with all the defaults. In the "Partition disk" step select "Guided - use entire disk and set up LVM". Go ahead accepting the defaults. At the "Install the GRUB boot loader" step select "/dev/vda" as the target device. The installer will actually run `grub-install --force /dev/mapper` and fail after a while. The wrong command is visible both in the d-i screen and by running `ps` on a different console. Full installer syslog: http://paste.ubuntu.com/p/qtZy86dTp6/ It's interesting how this doesn't happen when not using virtio. If from the commands above the "if=virtio" option is dropped then everything works as expected. In this case the target block device is called /dev/sda instead of /dev/vda. To manage notifications about
[Touch-packages] [Bug 1838525] Re: LVM setup fails to install grub on virtio storage
Pushed to https://git.launchpad.net/~ubuntu-core- dev/grub/+git/ubuntu/commit/?id=ef72a249cac219fee2ce5dec9648bb9717b16b30 Test-buiding, and uploading. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1838525 Title: LVM setup fails to install grub on virtio storage Status in debian-installer package in Ubuntu: In Progress Status in grub2 package in Ubuntu: In Progress Status in lvm2 package in Ubuntu: In Progress Status in debian-installer package in Debian: New Bug description: [Impact] * Any Eoan installation that depends on latest installer will face this issue when final user chooses LVM full disk partitioning type. * Grub won't be able to install due to bad bootdevice variable in the installer. It will try to install grub to "/dev/mapper" and will fail. The default boot option will also be "/dev/mapper". [Test Case] * Download netboot files from current installer (vmlinuz and initrd files). * Create a KVM guest running from these files, with a NIC connected to the internet. * Initiate a network installation inside the KVM guest, choosing the Entire Disk - LVM partitioning option. * Wait installation to finish and to start the grub-install phase. It will ask where to install grub, having, as default, "/dev/mapper". By default, it might simply try to grub-install /dev/mapper, which will also fail. * That happens because /dev/disk/by-id/ has an unexpected (by the installer) symlink added by lvm2 package that grub-installer (used by debian-installer) does not expect (when using grub-mkdevice command). [Simplified Test Case] * To add a PV + VG + LVM in a KVM guest to an empty virtio disk, for example, and to check if the command: grub-mkdevicemap --no-floppy -m - lists /dev/vdX1 in front of /dev/vdX. This will be a sign that: /dev/disk/by-id/*lvm* file exists and will be enough to confuse installer. [Regression Potential] There are 3 alternatives to fix this and I have chosen the one I believe has the smaller potential for any type of regression. Comment #30 describes what caused the regression and these 3 alternatives: (1) To revert this change for current release, since this rule was added to "make navigation a bit easier using PV UUIDs", as the commit says. We would worry about installer changes in the next release. (2) Another possibility would be to change the logic inside "grub- mkdevicemap.c: make_device_map()->grub_util_iterate_devices()" to ignore all symlinks from /dev/disk/by-id/ containing lvm-pv-uuid-*. We would not have to worry about this in the next release if using debian-installer. (3) Another option would be to change grub-installer package/logic. Unfortunately, a few days before the full freeze, I don't think messing with the installer would be a good option to avoid regressions (potential regression item would grow in significance). => I'm choosing (2) because ubuntu foundations already faced a similar situation, when grub-mkdevicemap.c file was removed from grub2 code and they re-added it by using a quilt patch, assuming it was the easiest and better to maintain. I'm doing something similar, patching the patch that creates grub-mkdevicemap.c file again to ignore /dev/disk/by-id/lvm-pv-uuid-* files (like it already does for other symlinks, actually). [Other Info] Comment #26 has the TL;DR version of the problem. https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/comments/26 [Original Description] The Eoan debian-installer ISO fails to install GRUB on LVM installs with virtio storage, as it runs grub-install with /dev/mapper as a target (a directory), even if instructed to target a device. The following steps to reproduce have been prepared running the 20190730 build, but this has been broken since about June 18, 2019. Steps to reproduce: $ md5sum eoan-server-amd64.iso f591e30485e5f0b5117f6c116e538c42 eoan-server-amd64.iso $ qemu-img create -f raw disk1.img 8G Formatting 'disk1.img', fmt=raw size=8589934592 $ kvm -m 1024 -boot d -cdrom eoan-server-amd64.iso -drive file=disk1.img,if=virtio Proceed with all the defaults. In the "Partition disk" step select "Guided - use entire disk and set up LVM". Go ahead accepting the defaults. At the "Install the GRUB boot loader" step select "/dev/vda" as the target device. The installer will actually run `grub-install --force /dev/mapper` and fail after a while. The wrong command is visible both in the d-i screen and by running `ps` on a different console. Full installer syslog: http://paste.ubuntu.com/p/qtZy86dTp6/ It's interesting how this doesn't happen when not using virtio. If from the commands above the "if=virtio" option is dropped then everything works as expected. In this case the target block
[Touch-packages] [Bug 1846506] Re: autopkgtest fail in Eoan
** Also affects: python3-defaults (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1846506 Title: autopkgtest fail in Eoan Status in python-azure package in Ubuntu: New Status in python-cryptography package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Bug description: The python-azure autopkgtest is failing on Eoan, currently blocking the migration of: - python-cryptography - python-defaults I had a look at the test log but it's not clear to me where the problem is. The autopkgtest history suggests that the failure is not actually caused by the two packages held in the migration queue. The python-azure autopkgtest is python3-only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-azure/+bug/1846506/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838525] Re: LVM setup fails to install grub on virtio storage
Thanks Rafael, Andreas and everybody for the great work done here! I successfully tested your fix as follows: 1. Followed the steps in the original description of this bug up the point where the installer tries to install grub to /dev/mapper and fails. 2. Replaced /target/usr/sbin/grub-mkdevicemap with the one extracted from the grub-common package in your PPA. 3. Retried the "install boot loader" installer step. 4. Success! Funny how the original grub-mkdevicemap and your fixed version have the same size up to the byte. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1838525 Title: LVM setup fails to install grub on virtio storage Status in debian-installer package in Ubuntu: In Progress Status in grub2 package in Ubuntu: In Progress Status in lvm2 package in Ubuntu: In Progress Status in debian-installer package in Debian: New Bug description: [Impact] * Any Eoan installation that depends on latest installer will face this issue when final user chooses LVM full disk partitioning type. * Grub won't be able to install due to bad bootdevice variable in the installer. It will try to install grub to "/dev/mapper" and will fail. The default boot option will also be "/dev/mapper". [Test Case] * Download netboot files from current installer (vmlinuz and initrd files). * Create a KVM guest running from these files, with a NIC connected to the internet. * Initiate a network installation inside the KVM guest, choosing the Entire Disk - LVM partitioning option. * Wait installation to finish and to start the grub-install phase. It will ask where to install grub, having, as default, "/dev/mapper". By default, it might simply try to grub-install /dev/mapper, which will also fail. * That happens because /dev/disk/by-id/ has an unexpected (by the installer) symlink added by lvm2 package that grub-installer (used by debian-installer) does not expect (when using grub-mkdevice command). [Simplified Test Case] * To add a PV + VG + LVM in a KVM guest to an empty virtio disk, for example, and to check if the command: grub-mkdevicemap --no-floppy -m - lists /dev/vdX1 in front of /dev/vdX. This will be a sign that: /dev/disk/by-id/*lvm* file exists and will be enough to confuse installer. [Regression Potential] There are 3 alternatives to fix this and I have chosen the one I believe has the smaller potential for any type of regression. Comment #30 describes what caused the regression and these 3 alternatives: (1) To revert this change for current release, since this rule was added to "make navigation a bit easier using PV UUIDs", as the commit says. We would worry about installer changes in the next release. (2) Another possibility would be to change the logic inside "grub- mkdevicemap.c: make_device_map()->grub_util_iterate_devices()" to ignore all symlinks from /dev/disk/by-id/ containing lvm-pv-uuid-*. We would not have to worry about this in the next release if using debian-installer. (3) Another option would be to change grub-installer package/logic. Unfortunately, a few days before the full freeze, I don't think messing with the installer would be a good option to avoid regressions (potential regression item would grow in significance). => I'm choosing (2) because ubuntu foundations already faced a similar situation, when grub-mkdevicemap.c file was removed from grub2 code and they re-added it by using a quilt patch, assuming it was the easiest and better to maintain. I'm doing something similar, patching the patch that creates grub-mkdevicemap.c file again to ignore /dev/disk/by-id/lvm-pv-uuid-* files (like it already does for other symlinks, actually). [Other Info] Comment #26 has the TL;DR version of the problem. https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/comments/26 [Original Description] The Eoan debian-installer ISO fails to install GRUB on LVM installs with virtio storage, as it runs grub-install with /dev/mapper as a target (a directory), even if instructed to target a device. The following steps to reproduce have been prepared running the 20190730 build, but this has been broken since about June 18, 2019. Steps to reproduce: $ md5sum eoan-server-amd64.iso f591e30485e5f0b5117f6c116e538c42 eoan-server-amd64.iso $ qemu-img create -f raw disk1.img 8G Formatting 'disk1.img', fmt=raw size=8589934592 $ kvm -m 1024 -boot d -cdrom eoan-server-amd64.iso -drive file=disk1.img,if=virtio Proceed with all the defaults. In the "Partition disk" step select "Guided - use entire disk and set up LVM". Go ahead accepting the defaults. At the "Install the GRUB boot loader" step select "/dev/vda" as the target device. The installer will actually run `grub-install --force /dev/mapper` and
[Touch-packages] [Bug 1847216] [NEW] motd-news only works with one URL even though docs say mutiple URLs can be configured
Public bug reported: The motd-news script etc/update-motd/50-motd-news the following section ``` # Loop over any configured URLs for u in $URLS; do # Ensure https:// protocol, for security reasons case $u in https://*) true ;; https://motd.ubuntu.com) u="$u/$codename/$arch" ;; *) continue ;; esac # If we're forced, set the wait to much higher (1 minute) [ "$FORCED" = "1" ] && WAIT=60 # Fetch and print the news motd if curl --connect-timeout "$WAIT" --max-time "$WAIT" -A "$USER_AGENT" -o- "$u" >"$NEWS" 2>"$ERR"; then echo # At most, 10 lines of text, remove control characters, print at most 80 characters per line safe_print "$NEWS" # Try to update the cache safe_print "$NEWS" 2>/dev/null >$CACHE || true else : > "$CACHE" fi done ``` As you can see the $CACHE gets overwritten if multiple URLs are configured in /etc/default/motd-news /etc/default/motd-news has ``` # Configure the source of dynamic MOTD news # White space separated list of 0 to many news services # For security reasons, these must be https # and have a valid certificate # Canonical runs a service at motd.ubuntu.com, and you # can easily run one too URLS="https://motd.ubuntu.com; ``` ** Affects: base-files (Ubuntu) Importance: Undecided Status: New ** Tags: motd ** Description changed: - The motd-news script etc/update-motd/50-motd-news + The motd-news script etc/update-motd/50-motd-news the following section ``` # Loop over any configured URLs for u in $URLS; do - # Ensure https:// protocol, for security reasons - case $u in - https://*) - true - ;; - https://motd.ubuntu.com) - u="$u/$codename/$arch" - ;; - *) - continue - ;; - esac - # If we're forced, set the wait to much higher (1 minute) - [ "$FORCED" = "1" ] && WAIT=60 - # Fetch and print the news motd - if curl --connect-timeout "$WAIT" --max-time "$WAIT" -A "$USER_AGENT" -o- "$u" >"$NEWS" 2>"$ERR"; then - echo - # At most, 10 lines of text, remove control characters, print at most 80 characters per line - safe_print "$NEWS" - # Try to update the cache - safe_print "$NEWS" 2>/dev/null >$CACHE || true - else - : > "$CACHE" - fi + # Ensure https:// protocol, for security reasons + case $u in + https://*) + true + ;; + https://motd.ubuntu.com) + u="$u/$codename/$arch" + ;; + *) + continue + ;; + esac + # If we're forced, set the wait to much higher (1 minute) + [ "$FORCED" = "1" ] && WAIT=60 + # Fetch and print the news motd + if curl --connect-timeout "$WAIT" --max-time "$WAIT" -A "$USER_AGENT" -o- "$u" >"$NEWS" 2>"$ERR"; then + echo + # At most, 10 lines of text, remove control characters, print at most 80 characters per line + safe_print "$NEWS" + # Try to update the cache + safe_print "$NEWS" 2>/dev/null >$CACHE || true + else + : > "$CACHE" + fi done ``` As you can see the $CACHE gets overwritten if multiple URLs are configured in /etc/default/motd-news /etc/default/motd-news has ``` # Configure the source of dynamic MOTD news # White space separated list of 0 to many news services # For security reasons, these must be https # and have a valid certificate # Canonical runs a service at motd.ubuntu.com, and you # can easily run one too - URLS="https://tprasadtp.github.io/motd/spacex/upcoming https://tprasadtp.github.io/motd/nasa/apod; + URLS="https://motd.ubuntu.com; ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1847216 Title: motd-news only works with one URL even though docs say mutiple URLs can be configured Status in base-files package in Ubuntu: New Bug description: The motd-news script etc/update-motd/50-motd-news the following section ``` # Loop over any configured URLs for u in $URLS; do # Ensure https:// protocol, for security reasons case $u in https://*) true ;;
[Touch-packages] [Bug 1844422] Re: WPA3-SAE support
Those fixes are in 1.20.4 which has been uploaded/is in the review queue, unsubscribing sponsors ** Changed in: network-manager (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: network-manager (Ubuntu) Importance: Undecided => Wishlist -- 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/1844422 Title: WPA3-SAE support Status in gnome-shell package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Fix Committed Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
Each time I am upgrading Xenial to Bionic I'm getting exactly the same message after few minutes: "*** ntp.conf (Y/I/N/O/D/Z) [default=N] ? " Can this fix get delivered to Ubuntu Xenial? ubuntu-release-upgrader-core 1:16.04.26 -- 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/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction Status in apt package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in ubuntu-release-upgrader source package in Bionic: Fix Released Status in apt source package in Cosmic: New Status in ubuntu-release-upgrader source package in Cosmic: Fix Released Status in apt source package in Disco: New Status in ubuntu-release-upgrader source package in Disco: Fix Released Status in apt source package in Eoan: Invalid Status in ubuntu-release-upgrader source package in Eoan: Fix Released Bug description: [Impact] The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing. [Test Case] You need to create a situation where you'll receive a conffile prompt since the handling of those is broken. 1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal 2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade --frontend DistUpgradeViewNonInteractive 3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log "2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades' 2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile" With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging. [Regression Potential] The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one, however additional logging which could result in a Traceback if the syntax of that is wrong. [Original Description] I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Configuration file '/etc/cron.daily/apt-compat' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same: In /var/log/dist-upgrade/main.log, I also found this: 2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat' 2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847201] Re: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 [Failed to restart
** Summary changed: - package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 + package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 [Failed to restart bluetooth.service: Unit -.mount is masked.] -- 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/1847201 Title: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 [Failed to restart bluetooth.service: Unit -.mount is masked.] Status in bluez package in Ubuntu: New Bug description: made upgrade using update-manager ProblemType: Package DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Oct 8 09:52:47 2019 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-05-18 (142 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS40 6QE Phantom ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=84c66d52-4ba6-49d7-8d50-e582f93d9b5c ro quiet nouveau.modeset=0 rd.driver.blacklist=nouveau acpi_osi=! "acpi_osi=Windows 2009" acpi_backlight=vendor resume=UUID=f7c3465a-6b62-428f-8477-67b678e6fe6e Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1.1 apt 1.8.3 SourcePackage: bluez Title: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14A1IMS.113 dmi.board.asset.tag: Default string dmi.board.name: MS-14A1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14A1IMS.113:bd01/15/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS406QEPhantom:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14A1:rvrREV0.C:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: GS40 6QE Phantom dmi.product.sku: Default string dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 9C:B6:D0:0A:FA:40 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN RX bytes:775 acl:0 sco:0 events:59 errors:0 TX bytes:3668 acl:0 sco:0 commands:59 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1847201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847201] Re: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1847201 Title: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 Status in bluez package in Ubuntu: New Bug description: made upgrade using update-manager ProblemType: Package DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Oct 8 09:52:47 2019 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-05-18 (142 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS40 6QE Phantom ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=84c66d52-4ba6-49d7-8d50-e582f93d9b5c ro quiet nouveau.modeset=0 rd.driver.blacklist=nouveau acpi_osi=! "acpi_osi=Windows 2009" acpi_backlight=vendor resume=UUID=f7c3465a-6b62-428f-8477-67b678e6fe6e Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1.1 apt 1.8.3 SourcePackage: bluez Title: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14A1IMS.113 dmi.board.asset.tag: Default string dmi.board.name: MS-14A1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14A1IMS.113:bd01/15/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS406QEPhantom:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14A1:rvrREV0.C:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: GS40 6QE Phantom dmi.product.sku: Default string dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 9C:B6:D0:0A:FA:40 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN RX bytes:775 acl:0 sco:0 events:59 errors:0 TX bytes:3668 acl:0 sco:0 commands:59 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1847201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847201] [NEW] package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1
Public bug reported: made upgrade using update-manager ProblemType: Package DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Oct 8 09:52:47 2019 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-05-18 (142 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS40 6QE Phantom ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=84c66d52-4ba6-49d7-8d50-e582f93d9b5c ro quiet nouveau.modeset=0 rd.driver.blacklist=nouveau acpi_osi=! "acpi_osi=Windows 2009" acpi_backlight=vendor resume=UUID=f7c3465a-6b62-428f-8477-67b678e6fe6e Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1.1 apt 1.8.3 SourcePackage: bluez Title: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14A1IMS.113 dmi.board.asset.tag: Default string dmi.board.name: MS-14A1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14A1IMS.113:bd01/15/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS406QEPhantom:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14A1:rvrREV0.C:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: GS40 6QE Phantom dmi.product.sku: Default string dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. hciconfig: hci0: Type: Primary Bus: USB BD Address: 9C:B6:D0:0A:FA:40 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN RX bytes:775 acl:0 sco:0 events:59 errors:0 TX bytes:3668 acl:0 sco:0 commands:59 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package disco -- 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/1847201 Title: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 Status in bluez package in Ubuntu: New Bug description: made upgrade using update-manager ProblemType: Package DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Oct 8 09:52:47 2019 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-05-18 (142 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS40 6QE Phantom ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=84c66d52-4ba6-49d7-8d50-e582f93d9b5c ro quiet nouveau.modeset=0 rd.driver.blacklist=nouveau acpi_osi=! "acpi_osi=Windows 2009" acpi_backlight=vendor resume=UUID=f7c3465a-6b62-428f-8477-67b678e6fe6e Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1.1 apt 1.8.3 SourcePackage: bluez Title: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1
[Touch-packages] [Bug 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
When can we expect any update on 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in mesa package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847176] Re: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc2/ -- 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/1847176 Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: No Sound on laptop speaker after upgrading ubuntu 19.04 a few days ago. Soundcard is found in alsamixer but only "dummy" is available in gnome settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 20:18:10 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ec963f21-6d46-4fd7-a5b5-286e29729b6b InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:5620 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Laptop 13-ad1xx Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=d203e9e9-3d32-4223-b420-e5ce61567401 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-31-generic x86_64 UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to:
[Touch-packages] [Bug 1844422] Re: WPA3-SAE support
Added gnome-shell task to reflect the fact that GUI support was (will be) added in gnome-shell 3.34.1 ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Tags added: fixed-in-3.34.1 fixed-upstream ** Changed in: gnome-shell (Ubuntu) Importance: Medium => Wishlist -- 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/1844422 Title: WPA3-SAE support Status in gnome-shell package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Confirmed Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847176] Re: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1847176 Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: No Sound on laptop speaker after upgrading ubuntu 19.04 a few days ago. Soundcard is found in alsamixer but only "dummy" is available in gnome settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 20:18:10 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ec963f21-6d46-4fd7-a5b5-286e29729b6b InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:5620 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Laptop 13-ad1xx Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=d203e9e9-3d32-4223-b420-e5ce61567401 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-31-generic x86_64 UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to:
[Touch-packages] [Bug 1847176] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1847176/+attachment/5295296/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1847176 Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: No Sound on laptop speaker after upgrading ubuntu 19.04 a few days ago. Soundcard is found in alsamixer but only "dummy" is available in gnome settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 20:18:10 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ec963f21-6d46-4fd7-a5b5-286e29729b6b InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:5620 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Laptop 13-ad1xx Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=d203e9e9-3d32-4223-b420-e5ce61567401 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-31-generic x86_64 UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP
[Touch-packages] [Bug 1847176] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1847176/+attachment/5295297/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1847176 Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: No Sound on laptop speaker after upgrading ubuntu 19.04 a few days ago. Soundcard is found in alsamixer but only "dummy" is available in gnome settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 20:18:10 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ec963f21-6d46-4fd7-a5b5-286e29729b6b InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:5620 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Laptop 13-ad1xx Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=d203e9e9-3d32-4223-b420-e5ce61567401 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-31-generic x86_64 UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To
[Touch-packages] [Bug 1847176] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1847176/+attachment/5295295/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1847176 Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: No Sound on laptop speaker after upgrading ubuntu 19.04 a few days ago. Soundcard is found in alsamixer but only "dummy" is available in gnome settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 20:18:10 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ec963f21-6d46-4fd7-a5b5-286e29729b6b InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:5620 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Laptop 13-ad1xx Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=d203e9e9-3d32-4223-b420-e5ce61567401 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-31-generic x86_64 UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId
[Touch-packages] [Bug 1847176] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1847176/+attachment/5295292/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1847176 Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: No Sound on laptop speaker after upgrading ubuntu 19.04 a few days ago. Soundcard is found in alsamixer but only "dummy" is available in gnome settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 20:18:10 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ec963f21-6d46-4fd7-a5b5-286e29729b6b InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:5620 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Laptop 13-ad1xx Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=d203e9e9-3d32-4223-b420-e5ce61567401 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-31-generic x86_64 UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId
[Touch-packages] [Bug 1847176] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1847176/+attachment/5295291/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1847176 Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: No Sound on laptop speaker after upgrading ubuntu 19.04 a few days ago. Soundcard is found in alsamixer but only "dummy" is available in gnome settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 20:18:10 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ec963f21-6d46-4fd7-a5b5-286e29729b6b InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:5620 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Laptop 13-ad1xx Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=d203e9e9-3d32-4223-b420-e5ce61567401 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-31-generic x86_64 UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To
[Touch-packages] [Bug 1847176] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1847176/+attachment/5295293/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1847176 Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: No Sound on laptop speaker after upgrading ubuntu 19.04 a few days ago. Soundcard is found in alsamixer but only "dummy" is available in gnome settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 20:18:10 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ec963f21-6d46-4fd7-a5b5-286e29729b6b InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:5620 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Laptop 13-ad1xx Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=d203e9e9-3d32-4223-b420-e5ce61567401 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-31-generic x86_64 UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId
[Touch-packages] [Bug 1847176] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1847176/+attachment/5295294/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1847176 Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: No Sound on laptop speaker after upgrading ubuntu 19.04 a few days ago. Soundcard is found in alsamixer but only "dummy" is available in gnome settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 20:18:10 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ec963f21-6d46-4fd7-a5b5-286e29729b6b InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:5620 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Laptop 13-ad1xx Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=d203e9e9-3d32-4223-b420-e5ce61567401 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-31-generic x86_64 UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId
[Touch-packages] [Bug 1847176] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1847176/+attachment/5295290/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1847176 Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: No Sound on laptop speaker after upgrading ubuntu 19.04 a few days ago. Soundcard is found in alsamixer but only "dummy" is available in gnome settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 20:18:10 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ec963f21-6d46-4fd7-a5b5-286e29729b6b InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:5620 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Laptop 13-ad1xx Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=d203e9e9-3d32-4223-b420-e5ce61567401 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-31-generic x86_64 UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP
[Touch-packages] [Bug 1847176] Re: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card
apport information ** Tags added: apport-collected ** Description changed: No Sound on laptop speaker after upgrading ubuntu 19.04 a few days ago. Soundcard is found in alsamixer but only "dummy" is available in gnome settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 20:18:10 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27.1 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.04 + EcryptfsInUse: Yes + HibernationDevice: RESUME=UUID=ec963f21-6d46-4fd7-a5b5-286e29729b6b + InstallationDate: Installed on 2017-11-25 (681 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 8087:0a2a Intel Corp. + Bus 001 Device 002: ID 0bda:5620 Realtek Semiconductor Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: HP HP ENVY Laptop 13-ad1xx + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=d203e9e9-3d32-4223-b420-e5ce61567401 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-31-generic N/A + linux-backports-modules-5.0.0-31-generic N/A + linux-firmware1.178.3 + Tags: disco + Uname: Linux 5.0.0-31-generic x86_64 + UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers + _MarkForUpload: True + dmi.bios.date: 08/07/2017 + dmi.bios.vendor: Insyde + dmi.bios.version: F.13 + dmi.board.asset.tag: Type2 - Board Asset Tag + dmi.board.name: 83A9 + dmi.board.vendor: HP + dmi.board.version: KBC Version 39.32 + dmi.chassis.type: 10 + dmi.chassis.vendor: HP + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: + dmi.product.family: 103C_5335KV HP Envy + dmi.product.name: HP ENVY Laptop 13-ad1xx + dmi.product.sku: 1KT13UA#ABA + dmi.product.version: Type1ProductConfigId + dmi.sys.vendor: HP ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1847176/+attachment/5295287/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1847176 Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: New Status
[Touch-packages] [Bug 1847176] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1847176/+attachment/5295289/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1847176 Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: No Sound on laptop speaker after upgrading ubuntu 19.04 a few days ago. Soundcard is found in alsamixer but only "dummy" is available in gnome settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 20:18:10 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ec963f21-6d46-4fd7-a5b5-286e29729b6b InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:5620 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Laptop 13-ad1xx Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=d203e9e9-3d32-4223-b420-e5ce61567401 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-31-generic x86_64 UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId
[Touch-packages] [Bug 1847176] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1847176/+attachment/5295288/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1847176 Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: No Sound on laptop speaker after upgrading ubuntu 19.04 a few days ago. Soundcard is found in alsamixer but only "dummy" is available in gnome settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 20:18:10 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ec963f21-6d46-4fd7-a5b5-286e29729b6b InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:5620 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Laptop 13-ad1xx Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=d203e9e9-3d32-4223-b420-e5ce61567401 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-31-generic x86_64 UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage
