[Touch-packages] [Bug 1860042] Re: openCL application gives error after update
please do, the other bug does mention that mesa master works, but there have been no changes to that file other than a single commit which doesn't look related.. -- 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/1860042 Title: openCL application gives error after update Status in mesa package in Ubuntu: Incomplete Bug description: My OpenCL program was working normally until a software update. The program prints out: ac_rtld error: !s->is_rx LLVM failed to upload shader when clEnqueueNDRangeKernel is called. I've downloaded the source for mesa and traced the problem to the gallium radeon driver. The first error message is from mesa-19.2.1/src/amd/common/ac_rtld.c and the second error message is from mesa-19.2.1/src/gallium/drivers/radeonsi/si_compute.c ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libllvm9 1:9-2~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-lowlatency 4.15.18 Uname: Linux 4.15.0-74-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 14:35:15 2020 InstallationDate: Installed on 2018-04-28 (628 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mesa-opencl-icd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: mesa (Ubuntu) Status: Incomplete => New ** Summary changed: - [nouveau] screen background overlaid with scan type artifact in red + [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red -- 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/1860483 Title: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 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/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://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 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
Yes. Re-installed. uname reports 5.5.0. and the screen is back to the red raster diagonal mess. On 1/23/20 11:58 PM, Daniel van Vugt wrote: > Please run: > >uname -a > > to confirm the newer kernel version is active. > -- 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/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 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/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860754] Re: Graphic driver Intel x5-Z8500
This is correct. Setting i915.modeset=0 will disable the Intel graphics driver so you should not do that. What are you trying to achieve? ** 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/1860754 Title: Graphic driver Intel x5-Z8500 Status in Ubuntu: Incomplete Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1860754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
Please run: uname -a to confirm the newer kernel version is active. -- 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/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 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/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://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 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
Doesn't look like it - uname returned 4.16.0-74-generic #84-Ubuntu SMP. May have overlaid the new generic by running APT upgrade. I'll try re-installing. On 1/23/20 11:39 PM, Daniel van Vugt wrote: > Please run: > >uname -a > > to confirm the newer kernel version is active. > -- 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/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 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/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
** Attachment added: "Screenshot from 2020-01-23 23-40-25.png" https://bugs.launchpad.net/bugs/1860483/+attachment/5322561/+files/Screenshot%20from%202020-01-23%2023-40-25.png -- 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/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 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/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://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 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
OTOH, I tried APT update and upgrade after the installation didn't change things and I did get a screen change. Attached is a post-restart screenshot. On 1/23/20 11:29 PM, Paul Collinsworth wrote: > Installed and that wasn't the root cause. Still the same problem. > > On 1/23/20 8:03 PM, Daniel van Vugt wrote: >> It's not important whether dkms is in use or not. You can just assume >> the worst case and install the four packages in comment #17. >> > -- 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/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 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/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860754] [NEW] Graphic driver Intel x5-Z8500
Public bug reported: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan 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/1860754 Title: Graphic driver Intel x5-Z8500 Status in xorg package in Ubuntu: New Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg
[Touch-packages] [Bug 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
Please run: uname -a to confirm the newer kernel version is active. -- 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/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 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/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://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 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
Installed and that wasn't the root cause. Still the same problem. On 1/23/20 8:03 PM, Daniel van Vugt wrote: > It's not important whether dkms is in use or not. You can just assume > the worst case and install the four packages in comment #17. > -- 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/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 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/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860606] Re: TypeError: _fetch_archives() missing 1 required positional argument: 'allow_unauthenticated'
** No longer affects: ubuntu-release-upgrader (Ubuntu) ** No longer affects: ubuntu-release-upgrader (Ubuntu Xenial) ** No longer affects: ubuntu-release-upgrader (Ubuntu Bionic) ** No longer affects: ubuntu-release-upgrader (Ubuntu Disco) ** No longer affects: ubuntu-release-upgrader (Ubuntu Eoan) ** No longer affects: ubuntu-release-upgrader (Ubuntu Focal) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1860606 Title: TypeError: _fetch_archives() missing 1 required positional argument: 'allow_unauthenticated' Status in python-apt package in Ubuntu: Confirmed Status in python-apt source package in Xenial: Fix Released Status in python-apt source package in Bionic: Fix Released Status in python-apt source package in Disco: Fix Released Status in python-apt source package in Eoan: Fix Released Status in python-apt source package in Focal: Confirmed Bug description: I was upgrading my workstation from 19.04 to 19.10 and following that to 20.04. In each case I used do-release-upgrade (without and with -d respectively). The 20.04 upgrade failed as the tool crashed on invalid function signature: Original exception was: Traceback (most recent call last): File "/tmp/ubuntu-release-upgrader-f_816ncr/focal", line 8, in sys.exit(main()) File "/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeMain.py", line 238, in main if app.run(): File "/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeController.py", line 2082, in run return self.fullUpgrade() File "/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeController.py", line 1998, in fullUpgrade if not self.doDistUpgradeFetching(): File "/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeController.py", line 1233, in doDistUpgradeFetching self.cache._fetch_archives(self.fetcher, pm) TypeError: _fetch_archives() missing 1 required positional argument: 'allow_unauthenticated' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1860606/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860741] Re: package initramfs-tools 0.122ubuntu8.16 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1860741 Title: package initramfs-tools 0.122ubuntu8.16 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in initramfs-tools package in Ubuntu: New Bug description: This problem occurred trying to upgrade the ubuntu from 16.04 to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.122ubuntu8.16 ProcVersionSignature: Ubuntu 4.15.0-74.83~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Jan 23 23:42:23 2020 DuplicateSignature: package:initramfs-tools:0.122ubuntu8.16 Processing triggers for initramfs-tools (0.122ubuntu8.16) ... /usr/sbin/update-initramfs: 222: /usr/sbin/update-initramfs: awk: not found dpkg: error processing package initramfs-tools (--unpack): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2019-07-25 (182 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.16 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to bionic on 2020-01-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1860741/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860741] [NEW] package initramfs-tools 0.122ubuntu8.16 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
Public bug reported: This problem occurred trying to upgrade the ubuntu from 16.04 to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.122ubuntu8.16 ProcVersionSignature: Ubuntu 4.15.0-74.83~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Jan 23 23:42:23 2020 DuplicateSignature: package:initramfs-tools:0.122ubuntu8.16 Processing triggers for initramfs-tools (0.122ubuntu8.16) ... /usr/sbin/update-initramfs: 222: /usr/sbin/update-initramfs: awk: not found dpkg: error processing package initramfs-tools (--unpack): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2019-07-25 (182 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.16 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to bionic on 2020-01-23 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1860741 Title: package initramfs-tools 0.122ubuntu8.16 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in initramfs-tools package in Ubuntu: New Bug description: This problem occurred trying to upgrade the ubuntu from 16.04 to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.122ubuntu8.16 ProcVersionSignature: Ubuntu 4.15.0-74.83~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Jan 23 23:42:23 2020 DuplicateSignature: package:initramfs-tools:0.122ubuntu8.16 Processing triggers for initramfs-tools (0.122ubuntu8.16) ... /usr/sbin/update-initramfs: 222: /usr/sbin/update-initramfs: awk: not found dpkg: error processing package initramfs-tools (--unpack): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2019-07-25 (182 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.16 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to bionic on 2020-01-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1860741/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
It's not important whether dkms is in use or not. You can just assume the worst case and install the four packages in comment #17. -- 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/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 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/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://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 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
I thought that might be the case, and looked in a couple of the /var subdirectories and didn't see dkms. I may run a more exhaustive search before trying the new linux install. I'll be doing that within an hour or so; had to be out most of the day on other business. At the moment the system with the fault is backing up a bunch of work files. I have another drive on the system and may install 18.04.3 if the issue doesn't resolve with the new linux install (that alternate drive is just sitting there with 16.04 and hasn't been in use). On 1/23/2020 6:47 PM, Daniel van Vugt wrote: > It would be putting files in /var/lib/dkms if it was in use. You would > also have a deb package called 'dkms' installed. > -- 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/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 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/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860736] Re: Driver load at boot
Thanks for the bug report but ideally each bug should only describe a single problem and you have described two. Please reproduce each problem separately and log a new bug for each while it is happening so that we can see the current state of the machine. ** Tags added: nouveau nvidia ** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1860736 Title: Driver load at boot Status in xorg package in Ubuntu: Invalid Bug description: At normal boot If use xorg driver display remain black after boot If use nvidia driver display and keyboard backlight flickers At recovery mode Boots normally ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.9 Architecture: i386 CompositorRunning: None Date: Thu Jan 23 19:32:44 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-65-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-74-generic, i686: installed virtualbox, 5.2.34, 4.15.0-65-generic, i686: installed virtualbox, 5.2.34, 4.15.0-74-generic, i686: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation MCP89 [GeForce 320M] [10de:08a0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. MCP89 [GeForce 320M] [106b:00c2] InstallationDate: Installed on 2018-08-13 (528 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release i386 (20180725) MachineType: Apple Inc. MacBookPro7,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=c9b3b341-3777-4a4a-b9dd-d5bb2d942cbf ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP71.88Z.003F.B00.1802021458 dmi.board.name: Mac-F222BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F222BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP71.88Z.003F.B00.1802021458:bd02/02/18:svnAppleInc.:pnMacBookPro7,1:pvr1.0:rvnAppleInc.:rnMac-F222BEC8:rvr:cvnAppleInc.:ct10:cvrMac-F222BEC8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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: Thu Jan 23 19:29:35 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1860736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860720] Re: Xorg freeze
Thanks for the bug report. It would be easiest for us to identify the cause of this problem if we had a clean log covering just the period of time when it happened. To do that please: 1. Reboot the machine. 2. Reproduce the bug and do nothing else. 3. Immediately run these commands: dmesg > dmesg.txt journalctl -b0 > journal.txt 4. Attach the above two text files to this bug. ** Tags added: suspend-resume ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: nvidia -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1860720 Title: Xorg freeze Status in Ubuntu: Incomplete Bug description: whenever I open my laptop after closing the lid, it gets freeze for a few minutes after some time I can see the lock screen and able to log in. when I don't close my lid just lock my laptop It's work completely fine. I think is an issue of susped- resume. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.44 Sun Dec 8 03:38:56 UTC 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 23 16:57:06 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GpuHangFrequency: Continuously GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1343] NVIDIA Corporation Device [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1343] InstallationDate: Installed on 2020-01-17 (5 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Acer Predator PH315-52 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=17b8f9c5-43c8-4757-a350-4a52d917434d ro nouveau.modeset=0 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Covini_CFS dmi.board.vendor: CFL dmi.board.version: V1.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd04/15/2019:svnAcer:pnPredatorPH315-52:pvrV1.02:rvnCFL:rnCovini_CFS:rvrV1.02:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Predator Helios 300 dmi.product.name: Predator PH315-52 dmi.product.sku: dmi.product.version: V1.02 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1860720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
That's bug 1550779, as mentioned in comment #7. -- 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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install 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-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
It would be putting files in /var/lib/dkms if it was in use. You would also have a deb package called 'dkms' installed. -- 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/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 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/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860622] Re: Dependency error installing pulseaudio-esound-compat
I've just asked its author to look at it again and maybe give us an update. -- 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/1860622 Title: Dependency error installing pulseaudio-esound-compat Status in pulseaudio package in Ubuntu: Fix Committed Bug description: Running: apt-get install pulseaudio-esound-compat I get the following error: The following packages have unmet dependencies: pulseaudio-esound-compat : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: pulseaudio (= 1:11.1-1ubuntu7.4) Seems like pulseaudio-esound-compat has not been updated for the latest package versions of libpulse0 and pulseaudio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1860622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860736] [NEW] Driver load at boot
Public bug reported: At normal boot If use xorg driver display remain black after boot If use nvidia driver display and keyboard backlight flickers At recovery mode Boots normally ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.9 Architecture: i386 CompositorRunning: None Date: Thu Jan 23 19:32:44 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-65-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-74-generic, i686: installed virtualbox, 5.2.34, 4.15.0-65-generic, i686: installed virtualbox, 5.2.34, 4.15.0-74-generic, i686: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation MCP89 [GeForce 320M] [10de:08a0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. MCP89 [GeForce 320M] [106b:00c2] InstallationDate: Installed on 2018-08-13 (528 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release i386 (20180725) MachineType: Apple Inc. MacBookPro7,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=c9b3b341-3777-4a4a-b9dd-d5bb2d942cbf ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP71.88Z.003F.B00.1802021458 dmi.board.name: Mac-F222BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F222BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP71.88Z.003F.B00.1802021458:bd02/02/18:svnAppleInc.:pnMacBookPro7,1:pvr1.0:rvnAppleInc.:rnMac-F222BEC8:rvr:cvnAppleInc.:ct10:cvrMac-F222BEC8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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: Thu Jan 23 19:29:35 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 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/1860736 Title: Driver load at boot Status in xorg package in Ubuntu: New Bug description: At normal boot If use xorg driver display remain black after boot If use nvidia driver display and keyboard backlight flickers At recovery mode Boots normally ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.9 Architecture: i386 CompositorRunning: None Date: Thu Jan 23 19:32:44 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-65-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-74-generic, i686: installed virtualbox, 5.2.34, 4.15.0-65-generic, i686: installed virtualbox, 5.2.34, 4.15.0-74-generic, i686: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation MCP89 [GeForce 320M] [10de:08a0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. MCP89 [GeForce 320M] [106b:00c2] InstallationDate: Installed on 2018-08-13 (528 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release i386 (20180725) MachineType: Apple Inc. MacBookPro7,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=c9b3b341-3777-4a4a-b9dd-d5bb2d942cbf ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP71.88Z.003F.B00.1802021458 dmi.board.name: Mac-F222BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F222BEC8 dmi.modalias:
[Touch-packages] [Bug 1509717] Autopkgtest regression report (lvm2/2.03.02-2ubuntu6.1)
All autopkgtests for the newly accepted lvm2 (2.03.02-2ubuntu6.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package: ganeti/2.16.0-5ubuntu1 (ppc64el) systemd/242-7ubuntu3.2 (amd64) resource-agents/1:4.2.0-1ubuntu2 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#lvm2 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Fix Committed Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to VM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860268] Re: window titlebar is disturbed on all non-maximized windows
** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-signed-hwe (Ubuntu) -- 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/1860268 Title: window titlebar is disturbed on all non-maximized windows Status in mesa package in Ubuntu: New Bug description: * After todays package update, the window titlebar area of all windows is rendered in a disturbed way. * Package update include a kernel change to 5.3 from 5.0. The bug is not related to the kernel; it also happen with the last one. Therefore, it's related to the new graphic packages. * This don't happen if the window is maximized. * This was also on a second PC with idential hardware (Dell 755 & Radeon HD 6450 video card) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-26-generic 5.3.0-26.28~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 19 12:44:46 2020 SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860268/+subscriptions -- Mailing list: https://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 1860042] Re: openCL application gives error after update
I've upgraded to Ubuntu 19.10 and used the PPA that you recommended and the error is still there. I could give you a patch with the changes that I made to ac_rtld.c that fixed the problem for my computer. On Wed, Jan 22, 2020 at 5:35 AM Timo Aaltonen wrote: > could you test with a newer mesa from this ppa > > https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/updates > > it's got latest bugfix release of the series, 19.2.8, and it's now > pending as a distro update as well > > ** Changed in: mesa (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1860042 > > Title: > openCL application gives error after update > > Status in mesa package in Ubuntu: > Incomplete > > Bug description: > My OpenCL program was working normally until a software update. > > The program prints out: > > ac_rtld error: !s->is_rx > LLVM failed to upload shader > > when clEnqueueNDRangeKernel is called. > > I've downloaded the source for mesa and traced the problem to the > gallium radeon driver. The first error message is from > > mesa-19.2.1/src/amd/common/ac_rtld.c > > and the second error message is from > > mesa-19.2.1/src/gallium/drivers/radeonsi/si_compute.c > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: libllvm9 1:9-2~ubuntu18.04.1 > ProcVersionSignature: Ubuntu 4.15.0-74.84-lowlatency 4.15.18 > Uname: Linux 4.15.0-74-lowlatency x86_64 > ApportVersion: 2.20.9-0ubuntu7.9 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Thu Jan 16 14:35:15 2020 > InstallationDate: Installed on 2018-04-28 (628 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > SourcePackage: mesa-opencl-icd > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860042/+subscriptions > -- 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/1860042 Title: openCL application gives error after update Status in mesa package in Ubuntu: Incomplete Bug description: My OpenCL program was working normally until a software update. The program prints out: ac_rtld error: !s->is_rx LLVM failed to upload shader when clEnqueueNDRangeKernel is called. I've downloaded the source for mesa and traced the problem to the gallium radeon driver. The first error message is from mesa-19.2.1/src/amd/common/ac_rtld.c and the second error message is from mesa-19.2.1/src/gallium/drivers/radeonsi/si_compute.c ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libllvm9 1:9-2~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-lowlatency 4.15.18 Uname: Linux 4.15.0-74-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 14:35:15 2020 InstallationDate: Installed on 2018-04-28 (628 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mesa-opencl-icd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860720] [NEW] Xorg freeze
Public bug reported: whenever I open my laptop after closing the lid, it gets freeze for a few minutes after some time I can see the lock screen and able to log in. when I don't close my lid just lock my laptop It's work completely fine. I think is an issue of susped- resume. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.44 Sun Dec 8 03:38:56 UTC 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 23 16:57:06 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GpuHangFrequency: Continuously GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1343] NVIDIA Corporation Device [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1343] InstallationDate: Installed on 2020-01-17 (5 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Acer Predator PH315-52 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=17b8f9c5-43c8-4757-a350-4a52d917434d ro nouveau.modeset=0 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Covini_CFS dmi.board.vendor: CFL dmi.board.version: V1.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd04/15/2019:svnAcer:pnPredatorPH315-52:pvrV1.02:rvnCFL:rnCovini_CFS:rvrV1.02:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Predator Helios 300 dmi.product.name: Predator PH315-52 dmi.product.sku: dmi.product.version: V1.02 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze possible-manual-nvidia-install 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/1860720 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: whenever I open my laptop after closing the lid, it gets freeze for a few minutes after some time I can see the lock screen and able to log in. when I don't close my lid just lock my laptop It's work completely fine. I think is an issue of susped- resume. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.44 Sun Dec 8 03:38:56 UTC 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 23 16:57:06 2020 DistUpgraded: Fresh
[Touch-packages] [Bug 1860516] Re: Cannot login to microsoft office365 account with 2fa enabled
Ok, you can close this issue then. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1860516 Title: Cannot login to microsoft office365 account with 2fa enabled Status in gnome-online-accounts package in Ubuntu: New Bug description: I have just enabled 2fa via time based codes on my office365 account. Now, when I try to relogin to the account again via settings > Online Accounts > Add Microsoft Exchange, I get an error, and I am never asked to input my time based code from my authenticator app. > Error connecting to Microsoft Exchange server: > Code: 456 -- Unexpected response from server Perhaps there should be an external login window, just like google login, to get 2fa working? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1860516/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860686] Re: package dnsmasq-base 2.75-1ubuntu0.16.04.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu
While the error message mentions dnsmasq, the only errors I'm spotting in the log file involve corefonts: Err:1 http://downloads.sourceforge.net/corefonts/impact32.exe Protocol "http" not supported or disabled in libcurl 0% [Working] E: Failed to fetch https://managedway.dl.sourceforge.net/project/corefonts/the fonts/final/impact32.exe Protocol "http" not supported or disabled in libcurl Perhaps this relates to upstream bug https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=912956 ? ** Bug watch added: Debian Bug tracker #912956 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912956 ** Changed in: dnsmasq (Ubuntu) Status: New => Incomplete ** Package changed: dnsmasq (Ubuntu) => msttcorefonts (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1860686 Title: package dnsmasq-base 2.75-1ubuntu0.16.04.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in msttcorefonts package in Ubuntu: Incomplete Bug description: Continues throwing errors ProblemType: Package DistroRelease: Ubuntu 16.04 Package: dnsmasq-base 2.75-1ubuntu0.16.04.5 ProcVersionSignature: Ubuntu 4.4.0-171.200-generic 4.4.203 Uname: Linux 4.4.0-171-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Jan 23 10:48:05 2020 DuplicateSignature: package:dnsmasq-base:2.75-1ubuntu0.16.04.5 Processing triggers for systemd (229-4ubuntu21.23) ... dpkg: error processing package dnsmasq-base (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-01-19 (1829 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: dnsmasq Title: package dnsmasq-base 2.75-1ubuntu0.16.04.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1860686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
Thanks Timo, I will comment on some effect, however in the log viewer several messages disappeared that I had before, for example (drm: intel_cpu_fifo_underrun_irq_handler [i915]] * ERROR * CPU pipe A FIFO underrun) ** Attachment added: "mensajes de registro" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1859730/+attachment/5322405/+files/mensajes%20de%20registro -- 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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install 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-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
** Tags added: champagne -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1509717] Please test proposed package
Hello MegaBrutal, or anyone else affected, Accepted lvm2 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lvm2/2.02.176-4.1ubuntu3.18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Fix Committed Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to VM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
Hello MegaBrutal, or anyone else affected, Accepted lvm2 into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lvm2/2.03.02-2ubuntu6.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: lvm2 (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan ** Changed in: lvm2 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- 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/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Fix Committed Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to VM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
it came preinstalled with 4.15.0-1042-oem yes, you can edit /etc/default/grub but you miswrote the parameter, it has to be literally 'i915.enable_psr=0' without any spaces or it won't work -- 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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install 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-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781428] Re: please enable snap mediation support
Now with the updated snap packages published, (see Bug #1856196 ), when will the pulseaudio packages be re-published? Everyone on Xenial and Bionic who did a package update between 2019-12-11 and 2019-12-12 now has orphaned pulseaudio packages installed, blocking the installation of additional pulseaudio packages! see Bug #1858164 Bug #1858164 -- 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/1781428 Title: please enable snap mediation support Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Committed Status in pulseaudio source package in Bionic: Fix Committed Bug description: [Impact] Ubuntu 16.10 added rudimentary snap support to disable audio recording if the connecting process was a snap. By Ubuntu 18.04, something changed in the build resulting in 'Enable Snappy support: no' with audio recording no longer being mediated by pulseaudio (access to the pulseaudio socket continued to be mediated by snapd's apparmor policy). This resulted in any application with the pulseaudio interface connected to be able to also record. Ubuntu 16.04 never had mediation patches and always allowed recording when the pulseaudio interface was connected. To correct this situation but not regress existing behavior, Ubuntu 19.04's pulseaudio was updated patch to allow playback to all connected clients (snaps or not), record by classic snaps (see bug 1787324) and record by strict mode snaps if either the pulseaudio or new-in-snapd-2.41 audio-record interfaces were connected. With this change, snapd is in a position to migrate snaps to the new audio- playback and audio-record interfaces and properly mediate audio recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio- interface-deprecation/13418). The patch to pulseaudio consists of adding a module, enabling it in default.pa and then when it is enabled, pulseaudio when faced with a record operation will, when the connecting process is a snap (ie, its security label (ie, apparmor label) starts with 'snap.'), query snapd via its control socket to ask if the snap is classic and if not, whether the pulseaudio or audio-record interfaces are connected. Adjusting pulseaudio in the manner does not require coordination with any release of snapd. It does need a newer version of snapd-glib, which was recently updated to 1.49 in the last SRU. [Test Case] IMPORTANT: if updating pulseaudio while the session is running, either need to reboot for the test or kill pulseaudio so it can restart with the new snap policy For unconfined applications: $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes For confined, non-snap applications: $ sudo apt-get install evince $ aa-exec -p /usr/bin/evince -- paplay /usr/share/sounds/alsa/Noise.wav && echo yes $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes" yes For classic snaps: $ sudo snap install test-snapd-classic-confinement --classic $ snap run --shell test-snapd-classic-confinement $ cat /proc/self/attr/current # verify we are classic confined snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain) $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes $ exit # out of snap run --shell For strict snaps with pulseaudio: $ sudo snap install test-snapd-pulseaudio --edge $ snap connections test-snapd-pulseaudio Interface Plug Slot Notes pulseaudio test-snapd-pulseaudio:pulseaudio :pulseaudio - $ test-snapd-pulseaudio.play --help # ensure SNAP dirs are created ... $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd- pulseaudio/common/ $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav && echo yes xcb_connection_has_error() returned true yes (note, the xcb_connection_has_error() message is due to the x11 interface not being connecting which is unrelated to mediation. x11 is left out to ensure that just audio-playback/audio-record are tested) $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass ... ^Cyes $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes ... yes For strict snaps with audio-playback/audio-record: $ sudo snap refresh core --candidate # make sure have 2.41. 'install' on 16.04 $ sudo snap install test-snapd-audio-record --edge $
[Touch-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd
Sebastien Bacher (seb128)wrote on 2019-12-12: #5 The Xenial/Bionic SRUs have been removed until the Recommends on snapd gets lowered to a Suggest And when will they be re-published? -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Won't Fix Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860695] [NEW] 20.04 often have no panel and default desktop
Public bug reported: I have 20.04 running on a couple of different machines. Sometimes when I have a problem of some sort and reboot, I'll have a desktop with the default wallpaper and no panel. This happened this morning after I had a networking problem. Adding a panel by right-clicking the desktop does not work. Usually the only fix is to delete the .kde, .config, .cache, and .local directories from my $HOME. Needless to say this is a royal pita. When I have this problem I can display the available windows with Alt-F4; they appear in a panel on the left-hand side of the screen. I've tried to determine just where the problem lies but without much success. I run a pretty vanilla setup with just a custom wallpaper and customized program menu. This has happened so frequently to me in the past couple of weeks that I expected to see a bug report filed already. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1860695 Title: 20.04 often have no panel and default desktop Status in ubuntu-meta package in Ubuntu: New Bug description: I have 20.04 running on a couple of different machines. Sometimes when I have a problem of some sort and reboot, I'll have a desktop with the default wallpaper and no panel. This happened this morning after I had a networking problem. Adding a panel by right-clicking the desktop does not work. Usually the only fix is to delete the .kde, .config, .cache, and .local directories from my $HOME. Needless to say this is a royal pita. When I have this problem I can display the available windows with Alt-F4; they appear in a panel on the left-hand side of the screen. I've tried to determine just where the problem lies but without much success. I run a pretty vanilla setup with just a custom wallpaper and customized program menu. This has happened so frequently to me in the past couple of weeks that I expected to see a bug report filed already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1860695/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 874120] Re: Online accounts credentials keep expiring when reading email in Evolution
By the way, Evolution running on Pantheon (Elementary OS native desktop) didn't generate this bug. It begun to appear when I changed from Pantheon to Gnome desktop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/874120 Title: Online accounts credentials keep expiring when reading email in Evolution Status in gnome-online-accounts package in Ubuntu: Confirmed Status in evolution package in Arch Linux: Won't Fix Status in gnome-online-accounts package in Fedora: Won't Fix Bug description: I have set up "online accounts" to connect to my personal GMail account and the Google Apps account set up by my employer. When I started Evolution, I saw that both accounts are already configured for reading email (and for calendering, though no calendar was actually selected so it didn't work - but that is another issue altogether). It worked fine initially, but after a while it started having authentication problems and I got a yellow warning messages at the top of the screen saying: Error while Refreshing folder 'INBOX'. [sic about weird capitalization] GDBus.Error:org.gnome.OnlineAccounts.Error.NotAuthorized: Credentials not found in keyring (goa-error-quark, 0): Failed to retrieve credentials from the keyring: Error communicating with gnome-keyring-daemon When I open "online accounts" again, I see that for both accounts have the message "Expired Credentials. Please log in again." I can do the log in again and it works, until the next day when I have to do the whole process over again. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 13:39:12 2011 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash LANGUAGE= SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/874120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 874120] Re: Online accounts credentials keep expiring when reading email in Evolution
At Juanuary 23th, 2020, still the same bug, among many others. Elementary OS Hera on Ubuntu 18.04 LTS here. Almost 10 years of people reporting the bug and Gnome hasn't been able to find a solution. Incredible. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/874120 Title: Online accounts credentials keep expiring when reading email in Evolution Status in gnome-online-accounts package in Ubuntu: Confirmed Status in evolution package in Arch Linux: Won't Fix Status in gnome-online-accounts package in Fedora: Won't Fix Bug description: I have set up "online accounts" to connect to my personal GMail account and the Google Apps account set up by my employer. When I started Evolution, I saw that both accounts are already configured for reading email (and for calendering, though no calendar was actually selected so it didn't work - but that is another issue altogether). It worked fine initially, but after a while it started having authentication problems and I got a yellow warning messages at the top of the screen saying: Error while Refreshing folder 'INBOX'. [sic about weird capitalization] GDBus.Error:org.gnome.OnlineAccounts.Error.NotAuthorized: Credentials not found in keyring (goa-error-quark, 0): Failed to retrieve credentials from the keyring: Error communicating with gnome-keyring-daemon When I open "online accounts" again, I see that for both accounts have the message "Expired Credentials. Please log in again." I can do the log in again and it works, until the next day when I have to do the whole process over again. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 13:39:12 2011 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash LANGUAGE= SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/874120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860693] [NEW] curl segfaults during network access with invalid -F argument
Public bug reported: mjt@i4-desktop:~/tmp$ vi 1.html mjt@i4-desktop:~/tmp$ curl -F'file=1.html' http://0x0.st Segmentation fault mjt@i4-desktop:~/tmp$ curl -v -F'file=1.html' http://0x0.st * Rebuilt URL to: http://0x0.st/ * Trying 136.243.89.164... * TCP_NODELAY set * Connected to 0x0.st (136.243.89.164) port 80 (#0) > POST / HTTP/1.1 > Host: 0x0.st > User-Agent: curl/7.58.0 > Accept: */* > Content-Length: 145 > Content-Type: multipart/form-data; > boundary=ee207a15c83a6272 > < HTTP/1.1 400 BAD REQUEST < Server: nginx < Date: Thu, 23 Jan 2020 16:36:43 GMT < Content-Type: text/html; charset=utf-8 < Content-Length: 19 < Connection: keep-alive * HTTP error before end of send, stop sending < Segmentation fault * Closing connection 0 mjt@i4-desktop:~/tmp$ curl --version curl 7.58.0 (x86_64-pc-linux-gnu) libcurl/7.58.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3 Release-Date: 2018-01-24 Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smb smbs smtp smtps telnet tftp Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz TLS-SRP HTTP2 UnixSockets HTTPS-proxy PSL mjt@i4-desktop:~/tmp$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic ** Affects: curl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1860693 Title: curl segfaults during network access with invalid -F argument Status in curl package in Ubuntu: New Bug description: mjt@i4-desktop:~/tmp$ vi 1.html mjt@i4-desktop:~/tmp$ curl -F'file=1.html' http://0x0.st Segmentation fault mjt@i4-desktop:~/tmp$ curl -v -F'file=1.html' http://0x0.st * Rebuilt URL to: http://0x0.st/ * Trying 136.243.89.164... * TCP_NODELAY set * Connected to 0x0.st (136.243.89.164) port 80 (#0) > POST / HTTP/1.1 > Host: 0x0.st > User-Agent: curl/7.58.0 > Accept: */* > Content-Length: 145 > Content-Type: multipart/form-data; boundary=ee207a15c83a6272 > < HTTP/1.1 400 BAD REQUEST < Server: nginx < Date: Thu, 23 Jan 2020 16:36:43 GMT < Content-Type: text/html; charset=utf-8 < Content-Length: 19 < Connection: keep-alive * HTTP error before end of send, stop sending < Segmentation fault * Closing connection 0 mjt@i4-desktop:~/tmp$ curl --version curl 7.58.0 (x86_64-pc-linux-gnu) libcurl/7.58.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3 Release-Date: 2018-01-24 Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smb smbs smtp smtps telnet tftp Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz TLS-SRP HTTP2 UnixSockets HTTPS-proxy PSL mjt@i4-desktop:~/tmp$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1860693/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845909] Re: [SRU] IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4
This bug was fixed in the package systemd - 244.1-0ubuntu2 --- systemd (244.1-0ubuntu2) focal; urgency=medium [ Dimitri John Ledkov ] * shutdown: do not detach autoclear loopback devices Author: Dimitri John Ledkov File: debian/patches/shutdown-do-not-detach-autoclear-loopback-devices.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3978d34b59e98cdd01836c41a10442967636b8fc [ Balint Reczey ] * Revert upstream commit breaking IPv4 DHCP in LXC containers in 244.1 (LP: #1857123) File: debian/patches/Revert-network-if-sys-is-rw-then-udev-should-be-around.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=39c12f8e736afd1b7bdeb13ff6bccaea85020873 systemd (244.1-0ubuntu1) focal; urgency=medium * New upstream version 244.1 - network: set ipv6 mtu after link-up or device mtu change (LP: #1671951) - & other changes * Refresh patches. - Dropped changes: * d/p/lp-1853852-*: fix issues with muliplexed shmat calls (LP: #1853852) Files: - debian/patches/lp-1853852-seccomp-fix-multiplexed-system-calls.patch - debian/patches/lp-1853852-seccomp-mmap-test-results-depend-on-kernel-libseccom.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=382271662c60c339b0a404c7a1772fe5670516ef * d/p/lp1671951-network-set-ipv6-mtu-after-link-up-or-device-mtu-cha.patch: set ipv6 mtu at correct time * pstore: Don't start systemd-pstore.service in containers. Usually it is not useful and can also fail making boot-and-services autopkgtest fail. (LP: #1856729) File: debian/patches/pstore-Don-t-start-systemd-pstore.service-in-containers.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=28b5a03769cbed9d3170ebac38508b867530a2d6 * Revert: network: do not drop foreign config if interface is in initialized state. This fixes FTBFS with the other network-related reverts. File: debian/patches/Revert-network-do-not-drop-foreign-config-if-interface-is.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=22a9fa3bb03ba2a629926af39ea7df81fe33c9b8 systemd (244-3ubuntu5) focal; urgency=medium [ Dariusz Gadomski ] * d/p/lp1762391/0001-user-util-Add-helper-functions-for-gid-lists-operati.patch, d/p/lp1762391/0002-execute-Restore-call-to-pam_setcred.patch, d/p/lp1762391/0003-execute-Detect-groups-added-by-PAM-and-merge-them-wi.patch, d/p/lp1762391/0004-test-Add-tests-for-gid-list-ops.patch, d/p/lp1762391/0005-execute-add-const-to-array-parameters-where-possible.patch, d/p/lp1762391/0006-execute-allow-pam_setcred-to-fail-ignore-errors.patch: - Restore call to pam_setcred (LP: #1762391) [ Dan Streetman ] * d/t/storage: without scsi_debug, skip test (LP: #1847816) systemd (244-3ubuntu4) focal; urgency=medium * d/p/lp1671951-network-set-ipv6-mtu-after-link-up-or-device-mtu-cha.patch: set ipv6 mtu at correct time (LP: #1671951) * d/p/0001-network-rename-linux_configure_after_setting_mtu-to-linux.patch, d/p/0002-network-add-link-setting_genmode-flag.patch, d/p/0003-network-if-ipv6ll-is-disabled-enumerate-tentative-ipv6-ad.patch, d/p/0004-network-drop-foreign-config-after-addr_gen_mode-has-been-.patch: - drop foreign config and raise interface after setting genmode (LP: #1845909) systemd (244-3ubuntu3) focal; urgency=medium * shutdown: cherry-pick PR#14409 to fix detach of loopback devices for Ubuntu Core 20 File: debian/patches/shutdown-modernizations-pr-14409.patch https://github.com/systemd/systemd/pull/14409.diff systemd (244-3ubuntu2) focal; urgency=medium * d/p/debian/UBUNTU-Support-system-image-read-only-etc.patch: - re-add missing bits for timedated.c (LP: #1778936) -- Balint Reczey Wed, 22 Jan 2020 16:27:49 +0100 ** Changed in: systemd (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1845909 Title: [SRU] IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4 Status in systemd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: In Progress Status in systemd source package in Focal: Fix Released Bug description: [impact] in some situations when a networkd interface is configured with LinkLocalAddressing=no, networkd still assigns a link-local address to it [test case] see comment 3. note I was only able to reproduce this at boot time; if the vlan interface is removed (i.e. 'sudo ip l del pppoe') and then networkd restarted, the pppoe interface is created and does
[Touch-packages] [Bug 1847816] Re: storage autopkgtest always fails with linux-{kvm, azure, etc} kernels that don't include scsi_debug module
This bug was fixed in the package systemd - 244.1-0ubuntu2
---
systemd (244.1-0ubuntu2) focal; urgency=medium
[ Dimitri John Ledkov ]
* shutdown: do not detach autoclear loopback devices
Author: Dimitri John Ledkov
File: debian/patches/shutdown-do-not-detach-autoclear-loopback-devices.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3978d34b59e98cdd01836c41a10442967636b8fc
[ Balint Reczey ]
* Revert upstream commit breaking IPv4 DHCP in LXC containers in 244.1
(LP: #1857123)
File:
debian/patches/Revert-network-if-sys-is-rw-then-udev-should-be-around.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=39c12f8e736afd1b7bdeb13ff6bccaea85020873
systemd (244.1-0ubuntu1) focal; urgency=medium
* New upstream version 244.1
- network: set ipv6 mtu after link-up or device mtu change (LP: #1671951)
- & other changes
* Refresh patches.
- Dropped changes:
* d/p/lp-1853852-*: fix issues with muliplexed shmat calls (LP: #1853852)
Files:
- debian/patches/lp-1853852-seccomp-fix-multiplexed-system-calls.patch
-
debian/patches/lp-1853852-seccomp-mmap-test-results-depend-on-kernel-libseccom.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=382271662c60c339b0a404c7a1772fe5670516ef
*
d/p/lp1671951-network-set-ipv6-mtu-after-link-up-or-device-mtu-cha.patch:
set ipv6 mtu at correct time
* pstore: Don't start systemd-pstore.service in containers.
Usually it is not useful and can also fail making
boot-and-services autopkgtest fail. (LP: #1856729)
File:
debian/patches/pstore-Don-t-start-systemd-pstore.service-in-containers.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=28b5a03769cbed9d3170ebac38508b867530a2d6
* Revert: network: do not drop foreign config if interface is in initialized
state.
This fixes FTBFS with the other network-related reverts.
File:
debian/patches/Revert-network-do-not-drop-foreign-config-if-interface-is.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=22a9fa3bb03ba2a629926af39ea7df81fe33c9b8
systemd (244-3ubuntu5) focal; urgency=medium
[ Dariusz Gadomski ]
*
d/p/lp1762391/0001-user-util-Add-helper-functions-for-gid-lists-operati.patch,
d/p/lp1762391/0002-execute-Restore-call-to-pam_setcred.patch,
d/p/lp1762391/0003-execute-Detect-groups-added-by-PAM-and-merge-them-wi.patch,
d/p/lp1762391/0004-test-Add-tests-for-gid-list-ops.patch,
d/p/lp1762391/0005-execute-add-const-to-array-parameters-where-possible.patch,
d/p/lp1762391/0006-execute-allow-pam_setcred-to-fail-ignore-errors.patch:
- Restore call to pam_setcred (LP: #1762391)
[ Dan Streetman ]
* d/t/storage: without scsi_debug, skip test (LP: #1847816)
systemd (244-3ubuntu4) focal; urgency=medium
* d/p/lp1671951-network-set-ipv6-mtu-after-link-up-or-device-mtu-cha.patch:
set ipv6 mtu at correct time (LP: #1671951)
* d/p/0001-network-rename-linux_configure_after_setting_mtu-to-linux.patch,
d/p/0002-network-add-link-setting_genmode-flag.patch,
d/p/0003-network-if-ipv6ll-is-disabled-enumerate-tentative-ipv6-ad.patch,
d/p/0004-network-drop-foreign-config-after-addr_gen_mode-has-been-.patch:
- drop foreign config and raise interface after setting genmode
(LP: #1845909)
systemd (244-3ubuntu3) focal; urgency=medium
* shutdown: cherry-pick PR#14409 to fix detach of loopback devices
for Ubuntu Core 20
File: debian/patches/shutdown-modernizations-pr-14409.patch
https://github.com/systemd/systemd/pull/14409.diff
systemd (244-3ubuntu2) focal; urgency=medium
* d/p/debian/UBUNTU-Support-system-image-read-only-etc.patch:
- re-add missing bits for timedated.c (LP: #1778936)
-- Balint Reczey Wed, 22 Jan 2020 16:27:49 +0100
** Changed in: systemd (Ubuntu Focal)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1847816
Title:
storage autopkgtest always fails with linux-{kvm,azure,etc} kernels
that don't include scsi_debug module
Status in autopkgtest-cloud:
New
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
In Progress
Status in systemd source package in Bionic:
In Progress
Status in systemd source package in Disco:
Won't Fix
Status in systemd source package in Eoan:
In Progress
Status in systemd source package in Focal:
Fix Released
Bug description:
[impact]
the 'storage' autopkgtest requires the 'scsi_debug' module, and if it
can't load it (and it's not built-in), the test fails. On some custom
kernels, this module is included in the new 'linux-modules-extra-*'
deb which isn't installed by default, so the test always
[Touch-packages] [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal
This bug was fixed in the package systemd - 244.1-0ubuntu2 --- systemd (244.1-0ubuntu2) focal; urgency=medium [ Dimitri John Ledkov ] * shutdown: do not detach autoclear loopback devices Author: Dimitri John Ledkov File: debian/patches/shutdown-do-not-detach-autoclear-loopback-devices.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3978d34b59e98cdd01836c41a10442967636b8fc [ Balint Reczey ] * Revert upstream commit breaking IPv4 DHCP in LXC containers in 244.1 (LP: #1857123) File: debian/patches/Revert-network-if-sys-is-rw-then-udev-should-be-around.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=39c12f8e736afd1b7bdeb13ff6bccaea85020873 systemd (244.1-0ubuntu1) focal; urgency=medium * New upstream version 244.1 - network: set ipv6 mtu after link-up or device mtu change (LP: #1671951) - & other changes * Refresh patches. - Dropped changes: * d/p/lp-1853852-*: fix issues with muliplexed shmat calls (LP: #1853852) Files: - debian/patches/lp-1853852-seccomp-fix-multiplexed-system-calls.patch - debian/patches/lp-1853852-seccomp-mmap-test-results-depend-on-kernel-libseccom.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=382271662c60c339b0a404c7a1772fe5670516ef * d/p/lp1671951-network-set-ipv6-mtu-after-link-up-or-device-mtu-cha.patch: set ipv6 mtu at correct time * pstore: Don't start systemd-pstore.service in containers. Usually it is not useful and can also fail making boot-and-services autopkgtest fail. (LP: #1856729) File: debian/patches/pstore-Don-t-start-systemd-pstore.service-in-containers.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=28b5a03769cbed9d3170ebac38508b867530a2d6 * Revert: network: do not drop foreign config if interface is in initialized state. This fixes FTBFS with the other network-related reverts. File: debian/patches/Revert-network-do-not-drop-foreign-config-if-interface-is.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=22a9fa3bb03ba2a629926af39ea7df81fe33c9b8 systemd (244-3ubuntu5) focal; urgency=medium [ Dariusz Gadomski ] * d/p/lp1762391/0001-user-util-Add-helper-functions-for-gid-lists-operati.patch, d/p/lp1762391/0002-execute-Restore-call-to-pam_setcred.patch, d/p/lp1762391/0003-execute-Detect-groups-added-by-PAM-and-merge-them-wi.patch, d/p/lp1762391/0004-test-Add-tests-for-gid-list-ops.patch, d/p/lp1762391/0005-execute-add-const-to-array-parameters-where-possible.patch, d/p/lp1762391/0006-execute-allow-pam_setcred-to-fail-ignore-errors.patch: - Restore call to pam_setcred (LP: #1762391) [ Dan Streetman ] * d/t/storage: without scsi_debug, skip test (LP: #1847816) systemd (244-3ubuntu4) focal; urgency=medium * d/p/lp1671951-network-set-ipv6-mtu-after-link-up-or-device-mtu-cha.patch: set ipv6 mtu at correct time (LP: #1671951) * d/p/0001-network-rename-linux_configure_after_setting_mtu-to-linux.patch, d/p/0002-network-add-link-setting_genmode-flag.patch, d/p/0003-network-if-ipv6ll-is-disabled-enumerate-tentative-ipv6-ad.patch, d/p/0004-network-drop-foreign-config-after-addr_gen_mode-has-been-.patch: - drop foreign config and raise interface after setting genmode (LP: #1845909) systemd (244-3ubuntu3) focal; urgency=medium * shutdown: cherry-pick PR#14409 to fix detach of loopback devices for Ubuntu Core 20 File: debian/patches/shutdown-modernizations-pr-14409.patch https://github.com/systemd/systemd/pull/14409.diff systemd (244-3ubuntu2) focal; urgency=medium * d/p/debian/UBUNTU-Support-system-image-read-only-etc.patch: - re-add missing bits for timedated.c (LP: #1778936) -- Balint Reczey Wed, 22 Jan 2020 16:27:49 +0100 ** Changed in: systemd (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1762391 Title: pam_group.so is not evaluated by gnome-terminal Status in systemd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: New Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Eoan: In Progress Status in systemd source package in Focal: Fix Released Bug description: [Impact] pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that processes were never getting group membership they were expected to get via pam_group module. [Test Case] * Add a
[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU
This bug was fixed in the package systemd - 244.1-0ubuntu2 --- systemd (244.1-0ubuntu2) focal; urgency=medium [ Dimitri John Ledkov ] * shutdown: do not detach autoclear loopback devices Author: Dimitri John Ledkov File: debian/patches/shutdown-do-not-detach-autoclear-loopback-devices.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3978d34b59e98cdd01836c41a10442967636b8fc [ Balint Reczey ] * Revert upstream commit breaking IPv4 DHCP in LXC containers in 244.1 (LP: #1857123) File: debian/patches/Revert-network-if-sys-is-rw-then-udev-should-be-around.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=39c12f8e736afd1b7bdeb13ff6bccaea85020873 systemd (244.1-0ubuntu1) focal; urgency=medium * New upstream version 244.1 - network: set ipv6 mtu after link-up or device mtu change (LP: #1671951) - & other changes * Refresh patches. - Dropped changes: * d/p/lp-1853852-*: fix issues with muliplexed shmat calls (LP: #1853852) Files: - debian/patches/lp-1853852-seccomp-fix-multiplexed-system-calls.patch - debian/patches/lp-1853852-seccomp-mmap-test-results-depend-on-kernel-libseccom.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=382271662c60c339b0a404c7a1772fe5670516ef * d/p/lp1671951-network-set-ipv6-mtu-after-link-up-or-device-mtu-cha.patch: set ipv6 mtu at correct time * pstore: Don't start systemd-pstore.service in containers. Usually it is not useful and can also fail making boot-and-services autopkgtest fail. (LP: #1856729) File: debian/patches/pstore-Don-t-start-systemd-pstore.service-in-containers.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=28b5a03769cbed9d3170ebac38508b867530a2d6 * Revert: network: do not drop foreign config if interface is in initialized state. This fixes FTBFS with the other network-related reverts. File: debian/patches/Revert-network-do-not-drop-foreign-config-if-interface-is.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=22a9fa3bb03ba2a629926af39ea7df81fe33c9b8 systemd (244-3ubuntu5) focal; urgency=medium [ Dariusz Gadomski ] * d/p/lp1762391/0001-user-util-Add-helper-functions-for-gid-lists-operati.patch, d/p/lp1762391/0002-execute-Restore-call-to-pam_setcred.patch, d/p/lp1762391/0003-execute-Detect-groups-added-by-PAM-and-merge-them-wi.patch, d/p/lp1762391/0004-test-Add-tests-for-gid-list-ops.patch, d/p/lp1762391/0005-execute-add-const-to-array-parameters-where-possible.patch, d/p/lp1762391/0006-execute-allow-pam_setcred-to-fail-ignore-errors.patch: - Restore call to pam_setcred (LP: #1762391) [ Dan Streetman ] * d/t/storage: without scsi_debug, skip test (LP: #1847816) systemd (244-3ubuntu4) focal; urgency=medium * d/p/lp1671951-network-set-ipv6-mtu-after-link-up-or-device-mtu-cha.patch: set ipv6 mtu at correct time (LP: #1671951) * d/p/0001-network-rename-linux_configure_after_setting_mtu-to-linux.patch, d/p/0002-network-add-link-setting_genmode-flag.patch, d/p/0003-network-if-ipv6ll-is-disabled-enumerate-tentative-ipv6-ad.patch, d/p/0004-network-drop-foreign-config-after-addr_gen_mode-has-been-.patch: - drop foreign config and raise interface after setting genmode (LP: #1845909) systemd (244-3ubuntu3) focal; urgency=medium * shutdown: cherry-pick PR#14409 to fix detach of loopback devices for Ubuntu Core 20 File: debian/patches/shutdown-modernizations-pr-14409.patch https://github.com/systemd/systemd/pull/14409.diff systemd (244-3ubuntu2) focal; urgency=medium * d/p/debian/UBUNTU-Support-system-image-read-only-etc.patch: - re-add missing bits for timedated.c (LP: #1778936) -- Balint Reczey Wed, 22 Jan 2020 16:27:49 +0100 ** Changed in: systemd (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6 MTU Status in systemd: Unknown Status in cloud-init package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in cloud-init source package in Bionic: Confirmed Status in netplan.io source package in Bionic: Fix Released Status in systemd source package in Bionic: In Progress Status in cloud-init source package in Disco: New Status in netplan.io source package in Disco: Fix Released Status in systemd source package in Disco: Won't Fix Status in cloud-init source package in Eoan: New Status in netplan.io source package in Eoan: Fix Released Status in systemd source package in Eoan: In Progress Status in cloud-init source package in
[Touch-packages] [Bug 1778936] Re: please re-add Support-system-image-read-only-etc.patch
This bug was fixed in the package systemd - 244.1-0ubuntu2 --- systemd (244.1-0ubuntu2) focal; urgency=medium [ Dimitri John Ledkov ] * shutdown: do not detach autoclear loopback devices Author: Dimitri John Ledkov File: debian/patches/shutdown-do-not-detach-autoclear-loopback-devices.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3978d34b59e98cdd01836c41a10442967636b8fc [ Balint Reczey ] * Revert upstream commit breaking IPv4 DHCP in LXC containers in 244.1 (LP: #1857123) File: debian/patches/Revert-network-if-sys-is-rw-then-udev-should-be-around.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=39c12f8e736afd1b7bdeb13ff6bccaea85020873 systemd (244.1-0ubuntu1) focal; urgency=medium * New upstream version 244.1 - network: set ipv6 mtu after link-up or device mtu change (LP: #1671951) - & other changes * Refresh patches. - Dropped changes: * d/p/lp-1853852-*: fix issues with muliplexed shmat calls (LP: #1853852) Files: - debian/patches/lp-1853852-seccomp-fix-multiplexed-system-calls.patch - debian/patches/lp-1853852-seccomp-mmap-test-results-depend-on-kernel-libseccom.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=382271662c60c339b0a404c7a1772fe5670516ef * d/p/lp1671951-network-set-ipv6-mtu-after-link-up-or-device-mtu-cha.patch: set ipv6 mtu at correct time * pstore: Don't start systemd-pstore.service in containers. Usually it is not useful and can also fail making boot-and-services autopkgtest fail. (LP: #1856729) File: debian/patches/pstore-Don-t-start-systemd-pstore.service-in-containers.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=28b5a03769cbed9d3170ebac38508b867530a2d6 * Revert: network: do not drop foreign config if interface is in initialized state. This fixes FTBFS with the other network-related reverts. File: debian/patches/Revert-network-do-not-drop-foreign-config-if-interface-is.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=22a9fa3bb03ba2a629926af39ea7df81fe33c9b8 systemd (244-3ubuntu5) focal; urgency=medium [ Dariusz Gadomski ] * d/p/lp1762391/0001-user-util-Add-helper-functions-for-gid-lists-operati.patch, d/p/lp1762391/0002-execute-Restore-call-to-pam_setcred.patch, d/p/lp1762391/0003-execute-Detect-groups-added-by-PAM-and-merge-them-wi.patch, d/p/lp1762391/0004-test-Add-tests-for-gid-list-ops.patch, d/p/lp1762391/0005-execute-add-const-to-array-parameters-where-possible.patch, d/p/lp1762391/0006-execute-allow-pam_setcred-to-fail-ignore-errors.patch: - Restore call to pam_setcred (LP: #1762391) [ Dan Streetman ] * d/t/storage: without scsi_debug, skip test (LP: #1847816) systemd (244-3ubuntu4) focal; urgency=medium * d/p/lp1671951-network-set-ipv6-mtu-after-link-up-or-device-mtu-cha.patch: set ipv6 mtu at correct time (LP: #1671951) * d/p/0001-network-rename-linux_configure_after_setting_mtu-to-linux.patch, d/p/0002-network-add-link-setting_genmode-flag.patch, d/p/0003-network-if-ipv6ll-is-disabled-enumerate-tentative-ipv6-ad.patch, d/p/0004-network-drop-foreign-config-after-addr_gen_mode-has-been-.patch: - drop foreign config and raise interface after setting genmode (LP: #1845909) systemd (244-3ubuntu3) focal; urgency=medium * shutdown: cherry-pick PR#14409 to fix detach of loopback devices for Ubuntu Core 20 File: debian/patches/shutdown-modernizations-pr-14409.patch https://github.com/systemd/systemd/pull/14409.diff systemd (244-3ubuntu2) focal; urgency=medium * d/p/debian/UBUNTU-Support-system-image-read-only-etc.patch: - re-add missing bits for timedated.c (LP: #1778936) -- Balint Reczey Wed, 22 Jan 2020 16:27:49 +0100 ** Changed in: systemd (Ubuntu Focal) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1778936 Title: please re-add Support-system-image-read-only-etc.patch Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [Impact] * core18 systems fail to update hostname * this happens due to /etc/hostname actually being a symlink to a file under /etc/writable/, adjust hostnamed to take that into account when trying to update /etc/hostname [Test Case] * run a core18 system, check that dhcp acquire hostname is correctly updated in /etc/writable/hostname [Regression Potential] * This is cherrypick of code that has gone missing since xenial. * There is no change of
[Touch-packages] [Bug 1860686] Re: package dnsmasq-base 2.75-1ubuntu0.16.04.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1860686 Title: package dnsmasq-base 2.75-1ubuntu0.16.04.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in dnsmasq package in Ubuntu: New Bug description: Continues throwing errors ProblemType: Package DistroRelease: Ubuntu 16.04 Package: dnsmasq-base 2.75-1ubuntu0.16.04.5 ProcVersionSignature: Ubuntu 4.4.0-171.200-generic 4.4.203 Uname: Linux 4.4.0-171-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Jan 23 10:48:05 2020 DuplicateSignature: package:dnsmasq-base:2.75-1ubuntu0.16.04.5 Processing triggers for systemd (229-4ubuntu21.23) ... dpkg: error processing package dnsmasq-base (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-01-19 (1829 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: dnsmasq Title: package dnsmasq-base 2.75-1ubuntu0.16.04.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1860686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860686] [NEW] package dnsmasq-base 2.75-1ubuntu0.16.04.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi
Public bug reported: Continues throwing errors ProblemType: Package DistroRelease: Ubuntu 16.04 Package: dnsmasq-base 2.75-1ubuntu0.16.04.5 ProcVersionSignature: Ubuntu 4.4.0-171.200-generic 4.4.203 Uname: Linux 4.4.0-171-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Jan 23 10:48:05 2020 DuplicateSignature: package:dnsmasq-base:2.75-1ubuntu0.16.04.5 Processing triggers for systemd (229-4ubuntu21.23) ... dpkg: error processing package dnsmasq-base (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-01-19 (1829 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: dnsmasq Title: package dnsmasq-base 2.75-1ubuntu0.16.04.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1860686 Title: package dnsmasq-base 2.75-1ubuntu0.16.04.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in dnsmasq package in Ubuntu: New Bug description: Continues throwing errors ProblemType: Package DistroRelease: Ubuntu 16.04 Package: dnsmasq-base 2.75-1ubuntu0.16.04.5 ProcVersionSignature: Ubuntu 4.4.0-171.200-generic 4.4.203 Uname: Linux 4.4.0-171-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Jan 23 10:48:05 2020 DuplicateSignature: package:dnsmasq-base:2.75-1ubuntu0.16.04.5 Processing triggers for systemd (229-4ubuntu21.23) ... dpkg: error processing package dnsmasq-base (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-01-19 (1829 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: dnsmasq Title: package dnsmasq-base 2.75-1ubuntu0.16.04.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1860686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1857123] Re: IPv4 addresses are not assigned in LXC with systemd 244.1
This bug was fixed in the package systemd - 244.1-0ubuntu2 --- systemd (244.1-0ubuntu2) focal; urgency=medium [ Dimitri John Ledkov ] * shutdown: do not detach autoclear loopback devices Author: Dimitri John Ledkov File: debian/patches/shutdown-do-not-detach-autoclear-loopback-devices.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3978d34b59e98cdd01836c41a10442967636b8fc [ Balint Reczey ] * Revert upstream commit breaking IPv4 DHCP in LXC containers in 244.1 (LP: #1857123) File: debian/patches/Revert-network-if-sys-is-rw-then-udev-should-be-around.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=39c12f8e736afd1b7bdeb13ff6bccaea85020873 systemd (244.1-0ubuntu1) focal; urgency=medium * New upstream version 244.1 - network: set ipv6 mtu after link-up or device mtu change (LP: #1671951) - & other changes * Refresh patches. - Dropped changes: * d/p/lp-1853852-*: fix issues with muliplexed shmat calls (LP: #1853852) Files: - debian/patches/lp-1853852-seccomp-fix-multiplexed-system-calls.patch - debian/patches/lp-1853852-seccomp-mmap-test-results-depend-on-kernel-libseccom.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=382271662c60c339b0a404c7a1772fe5670516ef * d/p/lp1671951-network-set-ipv6-mtu-after-link-up-or-device-mtu-cha.patch: set ipv6 mtu at correct time * pstore: Don't start systemd-pstore.service in containers. Usually it is not useful and can also fail making boot-and-services autopkgtest fail. (LP: #1856729) File: debian/patches/pstore-Don-t-start-systemd-pstore.service-in-containers.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=28b5a03769cbed9d3170ebac38508b867530a2d6 * Revert: network: do not drop foreign config if interface is in initialized state. This fixes FTBFS with the other network-related reverts. File: debian/patches/Revert-network-do-not-drop-foreign-config-if-interface-is.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=22a9fa3bb03ba2a629926af39ea7df81fe33c9b8 systemd (244-3ubuntu5) focal; urgency=medium [ Dariusz Gadomski ] * d/p/lp1762391/0001-user-util-Add-helper-functions-for-gid-lists-operati.patch, d/p/lp1762391/0002-execute-Restore-call-to-pam_setcred.patch, d/p/lp1762391/0003-execute-Detect-groups-added-by-PAM-and-merge-them-wi.patch, d/p/lp1762391/0004-test-Add-tests-for-gid-list-ops.patch, d/p/lp1762391/0005-execute-add-const-to-array-parameters-where-possible.patch, d/p/lp1762391/0006-execute-allow-pam_setcred-to-fail-ignore-errors.patch: - Restore call to pam_setcred (LP: #1762391) [ Dan Streetman ] * d/t/storage: without scsi_debug, skip test (LP: #1847816) systemd (244-3ubuntu4) focal; urgency=medium * d/p/lp1671951-network-set-ipv6-mtu-after-link-up-or-device-mtu-cha.patch: set ipv6 mtu at correct time (LP: #1671951) * d/p/0001-network-rename-linux_configure_after_setting_mtu-to-linux.patch, d/p/0002-network-add-link-setting_genmode-flag.patch, d/p/0003-network-if-ipv6ll-is-disabled-enumerate-tentative-ipv6-ad.patch, d/p/0004-network-drop-foreign-config-after-addr_gen_mode-has-been-.patch: - drop foreign config and raise interface after setting genmode (LP: #1845909) systemd (244-3ubuntu3) focal; urgency=medium * shutdown: cherry-pick PR#14409 to fix detach of loopback devices for Ubuntu Core 20 File: debian/patches/shutdown-modernizations-pr-14409.patch https://github.com/systemd/systemd/pull/14409.diff systemd (244-3ubuntu2) focal; urgency=medium * d/p/debian/UBUNTU-Support-system-image-read-only-etc.patch: - re-add missing bits for timedated.c (LP: #1778936) -- Balint Reczey Wed, 22 Jan 2020 16:27:49 +0100 ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1857123 Title: IPv4 addresses are not assigned in LXC with systemd 244.1 Status in systemd package in Ubuntu: Fix Released Bug description: triaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1857123/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856729] Re: autopkgtest: boot-and-services test fails in armhf containers
This bug was fixed in the package systemd - 244.1-0ubuntu2 --- systemd (244.1-0ubuntu2) focal; urgency=medium [ Dimitri John Ledkov ] * shutdown: do not detach autoclear loopback devices Author: Dimitri John Ledkov File: debian/patches/shutdown-do-not-detach-autoclear-loopback-devices.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3978d34b59e98cdd01836c41a10442967636b8fc [ Balint Reczey ] * Revert upstream commit breaking IPv4 DHCP in LXC containers in 244.1 (LP: #1857123) File: debian/patches/Revert-network-if-sys-is-rw-then-udev-should-be-around.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=39c12f8e736afd1b7bdeb13ff6bccaea85020873 systemd (244.1-0ubuntu1) focal; urgency=medium * New upstream version 244.1 - network: set ipv6 mtu after link-up or device mtu change (LP: #1671951) - & other changes * Refresh patches. - Dropped changes: * d/p/lp-1853852-*: fix issues with muliplexed shmat calls (LP: #1853852) Files: - debian/patches/lp-1853852-seccomp-fix-multiplexed-system-calls.patch - debian/patches/lp-1853852-seccomp-mmap-test-results-depend-on-kernel-libseccom.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=382271662c60c339b0a404c7a1772fe5670516ef * d/p/lp1671951-network-set-ipv6-mtu-after-link-up-or-device-mtu-cha.patch: set ipv6 mtu at correct time * pstore: Don't start systemd-pstore.service in containers. Usually it is not useful and can also fail making boot-and-services autopkgtest fail. (LP: #1856729) File: debian/patches/pstore-Don-t-start-systemd-pstore.service-in-containers.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=28b5a03769cbed9d3170ebac38508b867530a2d6 * Revert: network: do not drop foreign config if interface is in initialized state. This fixes FTBFS with the other network-related reverts. File: debian/patches/Revert-network-do-not-drop-foreign-config-if-interface-is.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=22a9fa3bb03ba2a629926af39ea7df81fe33c9b8 systemd (244-3ubuntu5) focal; urgency=medium [ Dariusz Gadomski ] * d/p/lp1762391/0001-user-util-Add-helper-functions-for-gid-lists-operati.patch, d/p/lp1762391/0002-execute-Restore-call-to-pam_setcred.patch, d/p/lp1762391/0003-execute-Detect-groups-added-by-PAM-and-merge-them-wi.patch, d/p/lp1762391/0004-test-Add-tests-for-gid-list-ops.patch, d/p/lp1762391/0005-execute-add-const-to-array-parameters-where-possible.patch, d/p/lp1762391/0006-execute-allow-pam_setcred-to-fail-ignore-errors.patch: - Restore call to pam_setcred (LP: #1762391) [ Dan Streetman ] * d/t/storage: without scsi_debug, skip test (LP: #1847816) systemd (244-3ubuntu4) focal; urgency=medium * d/p/lp1671951-network-set-ipv6-mtu-after-link-up-or-device-mtu-cha.patch: set ipv6 mtu at correct time (LP: #1671951) * d/p/0001-network-rename-linux_configure_after_setting_mtu-to-linux.patch, d/p/0002-network-add-link-setting_genmode-flag.patch, d/p/0003-network-if-ipv6ll-is-disabled-enumerate-tentative-ipv6-ad.patch, d/p/0004-network-drop-foreign-config-after-addr_gen_mode-has-been-.patch: - drop foreign config and raise interface after setting genmode (LP: #1845909) systemd (244-3ubuntu3) focal; urgency=medium * shutdown: cherry-pick PR#14409 to fix detach of loopback devices for Ubuntu Core 20 File: debian/patches/shutdown-modernizations-pr-14409.patch https://github.com/systemd/systemd/pull/14409.diff systemd (244-3ubuntu2) focal; urgency=medium * d/p/debian/UBUNTU-Support-system-image-read-only-etc.patch: - re-add missing bits for timedated.c (LP: #1778936) -- Balint Reczey Wed, 22 Jan 2020 16:27:49 +0100 ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1856729 Title: autopkgtest: boot-and-services test fails in armhf containers Status in systemd package in Ubuntu: Fix Released Bug description: systemd-pstore.service fails but should not be running in a container anyway: test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.z4wDHc/build.x55/src/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['systemd-pstore.service loaded failed fai[37 chars]val'] != []
[Touch-packages] [Bug 1859610] Re: python-gi/arm64 segfaults with the focal-proposed libffi version
** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libffi in Ubuntu. https://bugs.launchpad.net/bugs/1859610 Title: python-gi/arm64 segfaults with the focal-proposed libffi version Status in libffi package in Ubuntu: Fix Committed Status in pygobject package in Ubuntu: Fix Committed Status in libffi source package in Focal: Fix Committed Status in pygobject source package in Focal: Fix Committed Bug description: Testcase, on focal/arm64 $ sudo apt install python3-goocalendar $ python3 -c "import goocalendar ; print(goocalendar.__version__)" -> works fine install the python3-gi package from focal-proposed it segfaults in libffi Program received signal SIGSEGV, Segmentation fault. 0x in ?? () (gdb) bt #0 0x in ?? () #1 0xf7390ff8 in ffi_call_SYSV () at ../src/aarch64/sysv.S:114 #2 0xf7390634 in ffi_call_int (cif=0xa12d78, fn=, orig_rvalue=, avalue=0x0, closure=) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1859610/+subscriptions -- Mailing list: https://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 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
If dkms is installed, where is it in the filesystem? I checked /var and it isn't there - and I run a (more-or-less) standard system, with regard to file organization; don't know that I have any modules that require dkms. On 1/23/20 12:34 AM, Timo Aaltonen wrote: > and can skip the headers too, if there are no dkms modules that need > those > -- 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/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 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/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
** Changed in: lvm2 (Ubuntu Eoan) Status: Triaged => In Progress ** Changed in: lvm2 (Ubuntu Bionic) Status: New => In Progress -- 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/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: In Progress Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to VM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+subscriptions -- Mailing list: https://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 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
Thanks. I'll try the install shortly. On 1/23/20 12:23 AM, Daniel van Vugt wrote: > I know, this is a common question and we should do better to make it > clear. You only need the non-lowlatency packages: > > https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc7/linux- > headers-5.5.0-050500rc7_5.5.0-050500rc7.202001192030_all.deb > > https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc7/linux- > headers-5.5.0-050500rc7-generic_5.5.0-050500rc7.202001192030_amd64.deb > > https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc7/linux-image- > unsigned-5.5.0-050500rc7-generic_5.5.0-050500rc7.202001192030_amd64.deb > > https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc7/linux- > modules-5.5.0-050500rc7-generic_5.5.0-050500rc7.202001192030_amd64.deb > -- 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/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 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/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860622] Re: Dependency error installing pulseaudio-esound-compat
Do you know when 1:11.1-1ubuntu7.5 will be re-released? My update Ubuntu installation has the last version installed on Nov 22, 2019. Also, my apt package manager doesn't seem to know about "withdrawals" so the rest of my pulseaudio files remain from 1:11.1-1ubuntu7.5 BTW, I was able to install pulseaudio-esound-compate 11.1-1ubuntu7.5 manually from the site you linked above so your diagnosis seems right. -- 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/1860622 Title: Dependency error installing pulseaudio-esound-compat Status in pulseaudio package in Ubuntu: Fix Committed Bug description: Running: apt-get install pulseaudio-esound-compat I get the following error: The following packages have unmet dependencies: pulseaudio-esound-compat : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: pulseaudio (= 1:11.1-1ubuntu7.4) Seems like pulseaudio-esound-compat has not been updated for the latest package versions of libpulse0 and pulseaudio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1860622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860504] Re: software-properties-gtk fails to launch via "Additional Drivers" or via terminal
Thank you for your bug report. Could you include the output of the $ software-properties-gtk command? Could you also include the 'journalctl -b 0' log after getting the issue? ** Changed in: software-properties (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1860504 Title: software-properties-gtk fails to launch via "Additional Drivers" or via terminal Status in software-properties package in Ubuntu: Incomplete Bug description: Issue present since reinstall of Ubuntu. Originally thought similar to (https://askubuntu.com/questions/789966/software-updates-crashes-and- will-not-open) but solutions did not work, even though terminal output (https://pastebin.com/FpD1MFC3) is highly similar. I have tested using a new user and the issue remains. 1) Description: Ubuntu 19.10 Release: 19.10 Linux version 5.3.0-26-generic (buildd@lgw01-amd64-013) (gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)) 2) software-properties-gtk: Installed: 0.98.5 Candidate: 0.98.5 Version table: *** 0.98.5 500 500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status 3) Additional Drivers utility should launch when executing command "software-properties-gtk" with or without root. 4) Long error fight between dbus and python3. A note on attempted solutions. Reinstalling dbus/dbus-x11 and following the noted askubuntu thread did not help. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: software-properties-gtk 0.98.5 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 03:48:12 2020 InstallationDate: Installed on 2020-01-14 (8 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1860504/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860516] Re: Cannot login to microsoft office365 account with 2fa enabled
Thank you for your bug report. Ubuntu doesn't have an active gnome- online-accounts maintainer, could you maybe report to the project developers upstream on https://gitlab.gnome.org/GNOME/gnome-online- accounts/issues/ ? ** Changed in: gnome-online-accounts (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1860516 Title: Cannot login to microsoft office365 account with 2fa enabled Status in gnome-online-accounts package in Ubuntu: New Bug description: I have just enabled 2fa via time based codes on my office365 account. Now, when I try to relogin to the account again via settings > Online Accounts > Add Microsoft Exchange, I get an error, and I am never asked to input my time based code from my authenticator app. > Error connecting to Microsoft Exchange server: > Code: 456 -- Unexpected response from server Perhaps there should be an external login window, just like google login, to get 2fa working? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1860516/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860676] [NEW] apt-get dist-upgrade -y hangs during e2fsprogs update
Public bug reported: My recent apt-get dist-upgrade -y hung here: ... update-initramfs: deferring update (trigger activated) e2scrub_all.service is a disabled or a static unit not running, not starting it. I did a pstree on the apt-get process and saw this: apt-get(31290)───dpkg(562)───e2fsprogs.posti(587)───systemctl(722 )───systemd-tty-ask(863) Relevant processes: root 863 0.0 0.0 15976 5996 pts/12 S+ 09:13 0:00 /bin/systemd-tty-ask-password-agent --watch root 722 0.0 0.0 19668 3672 pts/12 S+ 09:13 0:00 /bin/systemctl restart e2scrub_all.timer e2scrub_reap.service I killed the systemd-tty-ask-password-agent process, and it became defunct but didn't die. So I killed the systemctl restart process, and the upgrade continued, apparently without noticing that the systemctl restart failed, which is a separate issue. When I ran "sudo systemctl restart e2scrub_all.timer e2scrub_reap.service" from the command line after the upgrade, it also hung with systemd-tty-ask-password-agent apparently waiting for something, so this problem isn't unique to upgrades. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: e2fsprogs 1.45.3-4ubuntu2.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 23 09:37:04 2020 InstallationDate: Installed on 2019-09-12 (132 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: e2fsprogs UpgradeStatus: Upgraded to eoan on 2019-09-20 (125 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 ** Affects: e2fsprogs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- 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/1860676 Title: apt-get dist-upgrade -y hangs during e2fsprogs update Status in e2fsprogs package in Ubuntu: New Bug description: My recent apt-get dist-upgrade -y hung here: ... update-initramfs: deferring update (trigger activated) e2scrub_all.service is a disabled or a static unit not running, not starting it. I did a pstree on the apt-get process and saw this: apt-get(31290)───dpkg(562)───e2fsprogs.posti(587)───systemctl(722 )───systemd-tty-ask(863) Relevant processes: root 863 0.0 0.0 15976 5996 pts/12 S+ 09:13 0:00 /bin/systemd-tty-ask-password-agent --watch root 722 0.0 0.0 19668 3672 pts/12 S+ 09:13 0:00 /bin/systemctl restart e2scrub_all.timer e2scrub_reap.service I killed the systemd-tty-ask-password-agent process, and it became defunct but didn't die. So I killed the systemctl restart process, and the upgrade continued, apparently without noticing that the systemctl restart failed, which is a separate issue. When I ran "sudo systemctl restart e2scrub_all.timer e2scrub_reap.service" from the command line after the upgrade, it also hung with systemd-tty-ask-password-agent apparently waiting for something, so this problem isn't unique to upgrades. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: e2fsprogs 1.45.3-4ubuntu2.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 23 09:37:04 2020 InstallationDate: Installed on 2019-09-12 (132 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: e2fsprogs UpgradeStatus: Upgraded to eoan on 2019-09-20 (125 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860676/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860676] Re: apt-get dist-upgrade -y hangs during e2fsprogs update
e2scrub_all.timer restarts just fine; it's the e2scrub_reap.service restart that's hanging. -- 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/1860676 Title: apt-get dist-upgrade -y hangs during e2fsprogs update Status in e2fsprogs package in Ubuntu: New Bug description: My recent apt-get dist-upgrade -y hung here: ... update-initramfs: deferring update (trigger activated) e2scrub_all.service is a disabled or a static unit not running, not starting it. I did a pstree on the apt-get process and saw this: apt-get(31290)───dpkg(562)───e2fsprogs.posti(587)───systemctl(722 )───systemd-tty-ask(863) Relevant processes: root 863 0.0 0.0 15976 5996 pts/12 S+ 09:13 0:00 /bin/systemd-tty-ask-password-agent --watch root 722 0.0 0.0 19668 3672 pts/12 S+ 09:13 0:00 /bin/systemctl restart e2scrub_all.timer e2scrub_reap.service I killed the systemd-tty-ask-password-agent process, and it became defunct but didn't die. So I killed the systemctl restart process, and the upgrade continued, apparently without noticing that the systemctl restart failed, which is a separate issue. When I ran "sudo systemctl restart e2scrub_all.timer e2scrub_reap.service" from the command line after the upgrade, it also hung with systemd-tty-ask-password-agent apparently waiting for something, so this problem isn't unique to upgrades. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: e2fsprogs 1.45.3-4ubuntu2.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 23 09:37:04 2020 InstallationDate: Installed on 2019-09-12 (132 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: e2fsprogs UpgradeStatus: Upgraded to eoan on 2019-09-20 (125 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860676/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860432] Re: juju agent fails to start on focal
Initial patch for support in 2.7 is here: https://github.com/juju/juju/pull/11147 Other patches for upgrade paths will follow. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1860432 Title: juju agent fails to start on focal Status in juju: In Progress Status in systemd package in Ubuntu: New Bug description: during bootstrap, add-machine, deploy Juju fails on Focal due to systemd not finding the service. ll /etc/systemd/system jujud-machine-1.service -> /lib/systemd/system/jujud-machine-1/jujud-machine-1.service which is linked and calls ExecStart=/lib/systemd/system/jujud-machine-1/exec-start.sh The fact that it's in a jujud-machine-1 folder vs /system itself appears to be causing systemd to not be able to run it. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1860432/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries
I just installed the 19.10 server iso and the machine doesn't use the DNS server provided through DHCP. As a workaround I had to: $ sudo rm /etc/resolv.conf $ sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf -- 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/1624320 Title: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries Status in systemd package in Ubuntu: Confirmed Status in Ubuntu RTM: New Bug description: systemd-resolved, or more precisely the hook script /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. The effect is similar to bug 1624071 but for applications doing their own DNS lookups. It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, bypassing validation failures. And it makes failing queries take twice as long. /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1624320 Title: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries Status in systemd package in Ubuntu: Confirmed Status in Ubuntu RTM: New Bug description: systemd-resolved, or more precisely the hook script /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. The effect is similar to bug 1624071 but for applications doing their own DNS lookups. It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, bypassing validation failures. And it makes failing queries take twice as long. /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856056] Re: libassuan: autopkgtest regression in -release on amd64
This bug was fixed in the package libassuan - 2.5.3-7ubuntu2 --- libassuan (2.5.3-7ubuntu2) focal; urgency=medium * Fix testsuite flags being incorrectly passed (patch taken from libgpg-error). (LP: #1856056) -- Gianfranco Costamagna Thu, 23 Jan 2020 12:30:00 +0100 ** Changed in: libassuan (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libassuan in Ubuntu. https://bugs.launchpad.net/bugs/1856056 Title: libassuan: autopkgtest regression in -release on amd64 Status in glibc package in Ubuntu: Fix Released Status in libassuan package in Ubuntu: Fix Released Status in wine package in Ubuntu: Fix Released Bug description: libassuan's autopkgtest seems to have regressed in -release on amd64 autopkgtest /usr/bin/i686-w64-mingw32-ld: /usr/x86_64-w64-mingw32/lib/libgpg-error.a: error adding symbols: file format not recognized collect2: error: ld returned 1 exit status autopkgtest [18:27:28]: test win32: ---] win32FAIL non-zero exit status 1 This regression is preventing glibc and wine from migrating from -proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1856056/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860544] Re: package uuid-runtime 2.34-0.1ubuntu2.1 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: util-linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1860544 Title: package uuid-runtime 2.34-0.1ubuntu2.1 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1 Status in util-linux package in Ubuntu: Confirmed Bug description: during update, the updater sent this message ProblemType: Package DistroRelease: Ubuntu 19.10 Package: uuid-runtime 2.34-0.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Wed Jan 22 13:12:14 2020 ErrorMessage: installed uuid-runtime package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-06-01 (964 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: util-linux Title: package uuid-runtime 2.34-0.1ubuntu2.1 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2019-10-22 (91 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1860544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
Hi, I do not remember what was the kernel that came with the machine, but if it was a 4. etc, the current kernel I have is 5.4.0-12-generic # 15-Ubuntu SMP. How can I edit the grub i915.enable_psr = 0 ?. Are these steps that I found on the internet right? sudo nano /etc/default/grub edit line with GRUB_CMDLINE_LINUX_DEFAULT = "quiet splash i915.enable_psr = 0” save sudo update-grub reboot Those steps are done, I will comment if it has no effect. Thank you! -- 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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install 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-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860199] Re: OpenCL programs give error messages
I have the same issues with my AMD A10-7850K (Radeon R7) and the same mesa-opencl version. Oibaf's OpenCL 1.1 Mesa 20.0.0-devel works fine on my system. -- 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/1860199 Title: OpenCL programs give error messages Status in mesa package in Ubuntu: Confirmed Bug description: OpenCL programs print ac_rtld error: !s->is_rx LLVM failed to upload shader when calling clEnqueueNDRangeKernel. lsb_release -rd displays: Description: Ubuntu 19.10 Release: 19.10 apt-cache policy mesa-opencl-icd displays: mesa-opencl-icd: Installed: 19.2.1-1ubuntu1 Candidate: 19.2.1-1ubuntu1 Version table: *** 19.2.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mesa-opencl-icd 19.2.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.427 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 23:09:17 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev e1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:82fe] LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Pavilion Desktop PC 570-p0xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed quiet splash --- SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2017 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: CNV7500FYH dmi.board.name: 82FE dmi.board.vendor: HP dmi.board.version: 11 dmi.chassis.asset.tag: CNV7500FYH dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.20:bd10/30/2017:svnHP:pnHPPavilionDesktopPC570-p0xx:pvr:rvnHP:rn82FE:rvr11:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Pavilion dmi.product.name: HP Pavilion Desktop PC 570-p0xx dmi.product.sku: Z5P18AA#ABL dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860199/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856056] Re: libassuan: autopkgtest regression in -release on amd64
meh, got the issue -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libassuan in Ubuntu. https://bugs.launchpad.net/bugs/1856056 Title: libassuan: autopkgtest regression in -release on amd64 Status in glibc package in Ubuntu: Fix Released Status in libassuan package in Ubuntu: New Status in wine package in Ubuntu: Fix Released Bug description: libassuan's autopkgtest seems to have regressed in -release on amd64 autopkgtest /usr/bin/i686-w64-mingw32-ld: /usr/x86_64-w64-mingw32/lib/libgpg-error.a: error adding symbols: file format not recognized collect2: error: ld returned 1 exit status autopkgtest [18:27:28]: test win32: ---] win32FAIL non-zero exit status 1 This regression is preventing glibc and wine from migrating from -proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1856056/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845909] Re: [SRU] IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4
re-uploaded with the added error handling mentioned by @vorlon in comment 11 removed; error handling behavior is unchanged now, and while it's not really the correct error handling behavior, that is a separate issue to this bug. -- 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/1845909 Title: [SRU] IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4 Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: In Progress Status in systemd source package in Focal: In Progress Bug description: [impact] in some situations when a networkd interface is configured with LinkLocalAddressing=no, networkd still assigns a link-local address to it [test case] see comment 3. note I was only able to reproduce this at boot time; if the vlan interface is removed (i.e. 'sudo ip l del pppoe') and then networkd restarted, the pppoe interface is created and does not have a link- local address. This is due to this bug being triggered by timing, as a vlan interface is raised by the kernel when its parent interface is raised, in this case by networkd itself. [regression potential] this changes how ipv6ll addresses are managed and dropped, as well as changing when foreign addresses are dropped (later in config process). Any regressions would likely be around incorrectly setting ipv6ll addresses, or complete failure to complete interface configuration. [scope] this is fixed upstream by: https://github.com/systemd/systemd/pull/13927 and also requires the upstream PR referenced in the original description: upstream patch: https://github.com/systemd/systemd/pull/13565 this is required for focal (uploaded already), eoan, and bionic. It may be required for xenial. [other info] Note, the original description below is incorrect, the issue/patch it references is not enough to fix this issue. original description: -- upstream issue: https://github.com/systemd/systemd/issues/12886 upstream patch: https://github.com/systemd/systemd/pull/13565 The upstream fix will be available in systemd 244. Backport please. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1845909/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856056] Re: libassuan: autopkgtest regression in -release on amd64
on debian: root@Unimatrix05-Bionic:/# ar x /usr/i686-w64-mingw32/lib/libgpg-error.a root@Unimatrix05-Bionic:/# file *.o libgpg_error_la-argparse.o:Intel 80386 COFF object file, no line number info, not stripped, 13 sections, symbol offset=0xf264, 79 symbols libgpg_error_la-b64dec.o: Intel 80386 COFF object file, no line number info, not stripped, 13 sections, symbol offset=0x5c06, 38 symbols libgpg_error_la-b64enc.o: Intel 80386 COFF object file, no line number info, not stripped, 13 sections, symbol offset=0x6bb4, 47 symbols libgpg_error_la-code-from-errno.o: Intel 80386 COFF object file, no line number info, not stripped, 12 sections, symbol offset=0x42d2, 29 symbols libgpg_error_la-code-to-errno.o: Intel 80386 COFF object file, no line number info, not stripped, 12 sections, symbol offset=0x87e2, 29 symbols libgpg_error_la-estream-printf.o: Intel 80386 COFF object file, no line number info, not stripped, 13 sections, symbol offset=0xb298, 56 symbols libgpg_error_la-estream.o: Intel 80386 COFF object file, no line number info, not stripped, 13 sections, symbol offset=0x25066, 217 symbols libgpg_error_la-init.o:Intel 80386 COFF object file, no line number info, not stripped, 13 sections, symbol offset=0x90f0, 88 symbols libgpg_error_la-logging.o: Intel 80386 COFF object file, no line number info, not stripped, 13 sections, symbol offset=0xe742, 117 symbols libgpg_error_la-spawn-w32.o: Intel 80386 COFF object file, no line number info, not stripped, 13 sections, symbol offset=0xd002, 74 symbols libgpg_error_la-strerror.o:Intel 80386 COFF object file, no line number info, not stripped, 13 sections, symbol offset=0x7a72, 40 symbols libgpg_error_la-strsource.o: Intel 80386 COFF object file, no line number info, not stripped, 13 sections, symbol offset=0xed2, 33 symbols libgpg_error_la-syscall-clamp.o: Intel 80386 COFF object file, no line number info, not stripped, 10 sections, symbol offset=0xbd4, 27 symbols libgpg_error_la-sysutils.o:Intel 80386 COFF object file, no line number info, not stripped, 12 sections, symbol offset=0x98de, 51 symbols libgpg_error_la-version.o: Intel 80386 COFF object file, no line number info, not stripped, 12 sections, symbol offset=0x1a4e, 32 symbols libgpg_error_la-visibility.o: Intel 80386 COFF object file, no line number info, not stripped, 15 sections, symbol offset=0xf010, 318 symbols libgpg_error_la-w32-estream.o: Intel 80386 COFF object file, no line number info, not stripped, 12 sections, symbol offset=0xadfc, 60 symbols libgpg_error_la-w32-gettext.o: Intel 80386 COFF object file, no line number info, not stripped, 13 sections, symbol offset=0xe0d6, 76 symbols libgpg_error_la-w32-iconv.o: Intel 80386 COFF object file, no line number info, not stripped, 13 sections, symbol offset=0xd4f0, 65 symbols libgpg_error_la-w32-lock.o:Intel 80386 COFF object file, no line number info, not stripped, 11 sections, symbol offset=0x6d88, 39 symbols libgpg_error_la-w32-reg.o: Intel 80386 COFF object file, no line number info, not stripped, 12 sections, symbol offset=0x3728, 37 symbols libgpg_error_la-w32-thread.o: Intel 80386 COFF object file, no line number info, not stripped, 10 sections, symbol offset=0x595a, 27 symbols versioninfo.o: Intel 80386 COFF object file, no line number info, not stripped, 1 section, symbol offset=0x7c8, 1 symbols -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libassuan in Ubuntu. https://bugs.launchpad.net/bugs/1856056 Title: libassuan: autopkgtest regression in -release on amd64 Status in glibc package in Ubuntu: Fix Released Status in libassuan package in Ubuntu: New Status in wine package in Ubuntu: Fix Released Bug description: libassuan's autopkgtest seems to have regressed in -release on amd64 autopkgtest /usr/bin/i686-w64-mingw32-ld: /usr/x86_64-w64-mingw32/lib/libgpg-error.a: error adding symbols: file format not recognized collect2: error: ld returned 1 exit status autopkgtest [18:27:28]: test win32: ---] win32FAIL non-zero exit status 1 This regression is preventing glibc and wine from migrating from -proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1856056/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856056] Re: libassuan: autopkgtest regression in -release on amd64
file *o libgpg_error_la-argparse.o:Intel amd64 COFF object file, no line number info, not stripped, 15 sections, symbol offset=0x10ae8, 83 symbols libgpg_error_la-b64dec.o: Intel amd64 COFF object file, no line number info, not stripped, 15 sections, symbol offset=0x60a0, 42 symbols libgpg_error_la-b64enc.o: Intel amd64 COFF object file, no line number info, not stripped, 15 sections, symbol offset=0x71ee, 51 symbols libgpg_error_la-code-from-errno.o: Intel amd64 COFF object file, no line number info, not stripped, 14 sections, symbol offset=0x44a2, 33 symbols libgpg_error_la-code-to-errno.o: Intel amd64 COFF object file, no line number info, not stripped, 14 sections, symbol offset=0x87f4, 33 symbols libgpg_error_la-estream-printf.o: Intel amd64 COFF object file, no line number info, not stripped, 15 sections, symbol offset=0xd400, 58 symbols libgpg_error_la-estream.o: Intel amd64 COFF object file, no line number info, not stripped, 16 sections, symbol offset=0x31a74, 223 symbols libgpg_error_la-init.o:Intel amd64 COFF object file, no line number info, not stripped, 15 sections, symbol offset=0xa2e4, 92 symbols libgpg_error_la-logging.o: Intel amd64 COFF object file, no line number info, not stripped, 15 sections, symbol offset=0x10d0c, 121 symbols libgpg_error_la-spawn-w32.o: Intel amd64 COFF object file, no line number info, not stripped, 15 sections, symbol offset=0xe32e, 78 symbols libgpg_error_la-strerror.o:Intel amd64 COFF object file, no line number info, not stripped, 15 sections, symbol offset=0x80c6, 44 symbols libgpg_error_la-strsource.o: Intel amd64 COFF object file, no line number info, not stripped, 14 sections, symbol offset=0xed8, 35 symbols libgpg_error_la-syscall-clamp.o: Intel amd64 COFF object file, no line number info, not stripped, 12 sections, symbol offset=0xc34, 31 symbols libgpg_error_la-sysutils.o:Intel amd64 COFF object file, no line number info, not stripped, 14 sections, symbol offset=0x9dd6, 55 symbols libgpg_error_la-version.o: Intel amd64 COFF object file, no line number info, not stripped, 14 sections, symbol offset=0x1f06, 36 symbols libgpg_error_la-visibility.o: Intel amd64 COFF object file, no line number info, not stripped, 19 sections, symbol offset=0x1a230, 326 symbols libgpg_error_la-w32-estream.o: Intel amd64 COFF object file, no line number info, not stripped, 14 sections, symbol offset=0xbd2c, 64 symbols libgpg_error_la-w32-gettext.o: Intel amd64 COFF object file, no line number info, not stripped, 15 sections, symbol offset=0x1004a, 73 symbols libgpg_error_la-w32-iconv.o: Intel amd64 COFF object file, no line number info, not stripped, 15 sections, symbol offset=0xfc7a, 69 symbols libgpg_error_la-w32-lock.o:Intel amd64 COFF object file, no line number info, not stripped, 14 sections, symbol offset=0x7616, 45 symbols libgpg_error_la-w32-reg.o: Intel amd64 COFF object file, no line number info, not stripped, 14 sections, symbol offset=0x38fc, 41 symbols libgpg_error_la-w32-thread.o: Intel amd64 COFF object file, no line number info, not stripped, 12 sections, symbol offset=0x5960, 31 symbols versioninfo.o: Intel amd64 COFF object file, no line number info, not stripped, 1 section, symbol offset=0x7c8, 1 symbols -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libassuan in Ubuntu. https://bugs.launchpad.net/bugs/1856056 Title: libassuan: autopkgtest regression in -release on amd64 Status in glibc package in Ubuntu: Fix Released Status in libassuan package in Ubuntu: New Status in wine package in Ubuntu: Fix Released Bug description: libassuan's autopkgtest seems to have regressed in -release on amd64 autopkgtest /usr/bin/i686-w64-mingw32-ld: /usr/x86_64-w64-mingw32/lib/libgpg-error.a: error adding symbols: file format not recognized collect2: error: ld returned 1 exit status autopkgtest [18:27:28]: test win32: ---] win32FAIL non-zero exit status 1 This regression is preventing glibc and wine from migrating from -proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1856056/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856056] Re: libassuan: autopkgtest regression in -release on amd64
looks like libgpg-error.a contains 64bit symbols even on 686 builds. Investigating... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libassuan in Ubuntu. https://bugs.launchpad.net/bugs/1856056 Title: libassuan: autopkgtest regression in -release on amd64 Status in glibc package in Ubuntu: Fix Released Status in libassuan package in Ubuntu: New Status in wine package in Ubuntu: Fix Released Bug description: libassuan's autopkgtest seems to have regressed in -release on amd64 autopkgtest /usr/bin/i686-w64-mingw32-ld: /usr/x86_64-w64-mingw32/lib/libgpg-error.a: error adding symbols: file format not recognized collect2: error: ld returned 1 exit status autopkgtest [18:27:28]: test win32: ---] win32FAIL non-zero exit status 1 This regression is preventing glibc and wine from migrating from -proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1856056/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860647] [NEW] block migration, removing unversioned packages
Public bug reported: block migration, removing unversioned packages. Make the migration explicit. ** Affects: python-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: block-proposed ** Tags added: block-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1860647 Title: block migration, removing unversioned packages Status in python-defaults package in Ubuntu: New Bug description: block migration, removing unversioned packages. Make the migration explicit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1860647/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
Oh actually, try booting with i915.enable_psr=0 It's possible the panel model has changed, and the platform was certified with another model which didn't support panel self refresh. -- 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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install 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-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
