[Touch-packages] [Bug 1865437] Re: satpy: autopkgtest unable to run on s390x
This blocks migration of: satpy/0.19.1-3build1 python-xarray/0.15.0-2ubuntu2 python3-defaults/3.8.2-0ubuntu1 python-pyproj/2.5.0+ds-1 ** Also affects: python-xarray (Ubuntu) Importance: Undecided Status: New ** Also affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Also affects: python-pyproj (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1865437 Title: satpy: autopkgtest unable to run on s390x Status in python-pyproj package in Ubuntu: New Status in python-xarray package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Status in satpy package in Ubuntu: New Bug description: satpy now has a test-dependency on python3-zarr which is not installable on s390x due to python3-numcodecs not being available there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pyproj/+bug/1865437/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1865435] Re: package uuid-runtime 2.34-0.1ubuntu2.2 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1865435 Title: package uuid-runtime 2.34-0.1ubuntu2.2 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1 Status in util-linux package in Ubuntu: New Bug description: package uuid-runtime 2.34-0.1ubuntu2.2 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 19.10 Package: uuid-runtime 2.34-0.1ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 Date: Mon Mar 2 12:31:53 2020 ErrorMessage: installed uuid-runtime package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-03-02 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: util-linux Title: package uuid-runtime 2.34-0.1ubuntu2.2 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1865435] [NEW] package uuid-runtime 2.34-0.1ubuntu2.2 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1
Public bug reported: package uuid-runtime 2.34-0.1ubuntu2.2 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 19.10 Package: uuid-runtime 2.34-0.1ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 Date: Mon Mar 2 12:31:53 2020 ErrorMessage: installed uuid-runtime package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-03-02 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: util-linux Title: package uuid-runtime 2.34-0.1ubuntu2.2 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- 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/1865435 Title: package uuid-runtime 2.34-0.1ubuntu2.2 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1 Status in util-linux package in Ubuntu: New Bug description: package uuid-runtime 2.34-0.1ubuntu2.2 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 19.10 Package: uuid-runtime 2.34-0.1ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 Date: Mon Mar 2 12:31:53 2020 ErrorMessage: installed uuid-runtime package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-03-02 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: util-linux Title: package uuid-runtime 2.34-0.1ubuntu2.2 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1865410] Re: Xorg freeze
I had to force-shutdown my machine, and I booted an older kernel (which is the one in the bug report), the proper kernel version in use at the time of the bug was linux-image-5.4.0-14-generic (5.4.0-14.17) -- 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/1865410 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: My Nvidia GPU is set to on-demand mode, so it uses the integrated intel iGPU for most of the every day tasks. This hang seems to happen when watching media (1080p @ 11605 kbps in H.264 in MKV container with EAC3 5.1 sound) and then switching to a resource intensive tab, which loads up lot's of media (ex: Reddit) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-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.59 Thu Jan 30 01:00:41 UTC 2020 GCC version: gcc version 9.2.1 20200224 (Ubuntu 9.2.1-30ubuntu1) ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 22:48:00 2020 DistUpgraded: 2020-02-27 20:01:03,129 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.59, 5.3.0-40-generic, x86_64: installed nvidia, 440.59, 5.4.0-14-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f] NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-01-22 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=126cdadc-728b-44e1-9491-cb5cba23fd10 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-02-28 (3 days ago) dmi.bios.date: 11/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET41W (1.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET41W(1.28):bd11/25/2019:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+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/xorg/+bug/1865410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1865410] [NEW] Xorg freeze
Public bug reported: My Nvidia GPU is set to on-demand mode, so it uses the integrated intel iGPU for most of the every day tasks. This hang seems to happen when watching media (1080p @ 11605 kbps in H.264 in MKV container with EAC3 5.1 sound) and then switching to a resource intensive tab, which loads up lot's of media (ex: Reddit) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-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.59 Thu Jan 30 01:00:41 UTC 2020 GCC version: gcc version 9.2.1 20200224 (Ubuntu 9.2.1-30ubuntu1) ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 22:48:00 2020 DistUpgraded: 2020-02-27 20:01:03,129 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.59, 5.3.0-40-generic, x86_64: installed nvidia, 440.59, 5.4.0-14-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f] NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-01-22 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=126cdadc-728b-44e1-9491-cb5cba23fd10 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-02-28 (3 days ago) dmi.bios.date: 11/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET41W (1.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET41W(1.28):bd11/25/2019:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+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 focal freeze ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1865410 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: My Nvidia GPU is set to on-demand mode, so it uses the integrated intel iGPU for most of the every day tasks. This hang seems to happen when watching media (1080p @ 11605 kbps in H.264 in MKV container with EAC3 5.1 sound) and then switching to a resource intensive tab, which loads up lot's of media (ex: Reddit) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-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
[Touch-packages] [Bug 1865411] [NEW] Need to restart Network Manager frequently
Public bug reported: My WiFi connection keeps stopping to work every once in a while (sometimes as often as every 10 minutes). Restarting NetworkManager usually resolves this problem. But I am not sure why that is the case. I do not think there is a connectivity issue as it happens even when I am right next to the access point. I have a standard Intel Wireless chip and use GNOME shell with some extensions. Nothing exotic. Note this happened on eoan as well as focal (and maybe even before that). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.8-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 19:56:11 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-07-09 (236 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.1.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.1.0/24 dev wlp4s0 proto kernel scope link src 192.168.1.24 metric 600 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/fish SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.8 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1865411 Title: Need to restart Network Manager frequently Status in network-manager package in Ubuntu: New Bug description: My WiFi connection keeps stopping to work every once in a while (sometimes as often as every 10 minutes). Restarting NetworkManager usually resolves this problem. But I am not sure why that is the case. I do not think there is a connectivity issue as it happens even when I am right next to the access point. I have a standard Intel Wireless chip and use GNOME shell with some extensions. Nothing exotic. Note this happened on eoan as well as focal (and maybe even before that). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.8-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 19:56:11 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-07-09 (236 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.1.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.1.0/24 dev wlp4s0 proto kernel scope link src 192.168.1.24 metric 600 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/fish SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.8 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1865411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
Yes, the issue comes up on the last firmware upgrade. Either some bug there or incompatibility, I'm guessing. -- 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/1865130 Title: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! Status in xorg package in Ubuntu: Confirmed Bug description: when trying > DRI_PRIME=1 glxgears , the result in dmesg is as following [ +0.91] radeon :01:00.0: WB enabled [ +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8ac2d26f [ +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0xa848de20 [ +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x1e4494a9 [ +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x98a9748e [ +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0xb6ff734d [ +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0x6b4da526 [ +0.100566] radeon :01:00.0: failed VCE resume (-110). [ +0.179115] [drm] ring test on 0 succeeded in 1 usecs [ +0.04] [drm] ring test on 1 succeeded in 1 usecs [ +0.04] [drm] ring test on 2 succeeded in 1 usecs [ +0.06] [drm] ring test on 3 succeeded in 3 usecs [ +0.04] [drm] ring test on 4 succeeded in 3 usecs [ +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!! [ +0.40] radeon :01:00.0: failed initializing UVD (-1). [ +0.60] [drm] ib test on ring 0 succeeded in 0 usecs [ +0.51] [drm] ib test on ring 1 succeeded in 0 usecs [ +0.32] [drm] ib test on ring 2 succeeded in 0 usecs [ +0.52] [drm] ib test on ring 3 succeeded in 0 usecs [ +0.29] [drm] ib test on ring 4 succeeded in 0 usecs Also it affects the boot time. the used OpenGL renderer is: "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Feb 28 11:50:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:3801] InstallationDate: Installed on 2019-09-17 (163 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20238 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=385a4174-5cfe-49c9-b4c3-9e64a251d432 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 79CN46WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID
[Touch-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
I can confirm that rolling back to linux-firmware=1.173.12 solves the issue with Kernel: 5.3.0-40-generic x86_64. -- 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/1865130 Title: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! Status in xorg package in Ubuntu: Confirmed Bug description: when trying > DRI_PRIME=1 glxgears , the result in dmesg is as following [ +0.91] radeon :01:00.0: WB enabled [ +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8ac2d26f [ +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0xa848de20 [ +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x1e4494a9 [ +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x98a9748e [ +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0xb6ff734d [ +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0x6b4da526 [ +0.100566] radeon :01:00.0: failed VCE resume (-110). [ +0.179115] [drm] ring test on 0 succeeded in 1 usecs [ +0.04] [drm] ring test on 1 succeeded in 1 usecs [ +0.04] [drm] ring test on 2 succeeded in 1 usecs [ +0.06] [drm] ring test on 3 succeeded in 3 usecs [ +0.04] [drm] ring test on 4 succeeded in 3 usecs [ +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!! [ +0.40] radeon :01:00.0: failed initializing UVD (-1). [ +0.60] [drm] ib test on ring 0 succeeded in 0 usecs [ +0.51] [drm] ib test on ring 1 succeeded in 0 usecs [ +0.32] [drm] ib test on ring 2 succeeded in 0 usecs [ +0.52] [drm] ib test on ring 3 succeeded in 0 usecs [ +0.29] [drm] ib test on ring 4 succeeded in 0 usecs Also it affects the boot time. the used OpenGL renderer is: "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Feb 28 11:50:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:3801] InstallationDate: Installed on 2019-09-17 (163 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20238 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=385a4174-5cfe-49c9-b4c3-9e64a251d432 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 79CN46WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID
[Touch-packages] [Bug 359902] Re: ubuntu creash reporting reveals sensitive data
I am currently testing 20.04. If there is no option to edit & remove private data prior to sending, I have little interest in submitting further reports. Why can the program not present the user with the files & info that is going to be submitted? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/359902 Title: ubuntu creash reporting reveals sensitive data Status in apport package in Ubuntu: Won't Fix Bug description: Hi, ubuntu jaunty has a new system to automatically create reports when programs crash. Good work. But the reports contain lists of open files and thus filenames, and core dumps, which (usually) contain a copy of the program's heap and static memory. So uploading that crash report to ubuntu's bug reporting system (i.e. this launchpad) reveals memory contents to the public. Some programs can contain sensible data. For example, the program that crashes most often on my jaunty beta installation is the search tool of tracker, which basically scans *every single one* of my private files. At the moment of crash any contents of my home file system could still remain in the process memory space and thus made publicly available. Would be interesting to download all core dumps and search for private data. Most people won't realize this and just send that automatically generated report. regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/359902/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1865373] [NEW] Authentication Prompt cut off
Public bug reported: Every time the "Authentication Required" prompt pops up, the right side is cut off short. My resolution is currently set to 1600x900 on a 1920x1080 13." screen. The same thing happened at native resolution. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 14:40:57 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:081b] InstallationDate: Installed on 2020-02-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200229) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58ca Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7390 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_evtvik@/vmlinuz-5.4.0-14-generic root=ZFS=rpool/ROOT/ubuntu_evtvik ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7390 dmi.product.sku: 081B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+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 corruption focal reproducible single-occurrence ubuntu ** Attachment added: "Screenshot of cut off authentication prompt" https://bugs.launchpad.net/bugs/1865373/+attachment/5332418/+files/Screenshot%20from%202020-03-01%2014-42-01.png -- 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/1865373 Title: Authentication Prompt cut off Status in xorg package in Ubuntu: New Bug description: Every time the "Authentication Required" prompt pops up, the right side is cut off short. My resolution is currently set to 1600x900 on a 1920x1080 13." screen. The same thing happened at native resolution. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 14:40:57 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:081b] InstallationDate: Installed on 2020-02-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200229) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58ca Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7390 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_evtvik@/vmlinuz-5.4.0-14-generic root=ZFS=rpool/ROOT/ubuntu_evtvik ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display
[Touch-packages] [Bug 1865364] [NEW] SELECT WHERE using COLLATE NOCASE fails using multiple tests and using IN(...)
Public bug reported: COLLATE NOCASE seems to be ignored when using the following constructs in a WHERE clause: Col=value1 COLLATE NOCASE OR Col=value2 Col IN(value COLLATE NOCASE) Col IN(value) COLLATE NOCASE [both are accepted, not sure which is valid syntax] It works in the simple case Col=value1 COLLATE NOCASE I have written a simple test script which demonstrates working queries and failing queries, which is attached, and reproduced here: # demo of sqlite bug with collate nocase # usage: sqlite3 :memory: # > .read sqlite_nocase_bug.sql # create temp table test (col text unique); insert into test (col) values('Test'); select '1:', * from test where col='Test'; -- works select '2:', * from test where col='test' collate nocase; -- works select '3:', * from test where col='test' collate nocase or col='other' collate nocase; -- returns no rows select '4:', * from test where col in ('test') collate nocase; -- returns no rows select '5:', * from test where col in ('test' collate nocase); -- returns no rows ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: sqlite3 3.29.0-2ubuntu0.1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 18:17:53 2020 SourcePackage: sqlite3 UpgradeStatus: Upgraded to eoan on 2019-10-23 (129 days ago) ** Affects: sqlite3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Script with sql statements to demonstrate bug" https://bugs.launchpad.net/bugs/1865364/+attachment/5332361/+files/sqlite_nocase_bug.sql -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1865364 Title: SELECT WHERE using COLLATE NOCASE fails using multiple tests and using IN(...) Status in sqlite3 package in Ubuntu: New Bug description: COLLATE NOCASE seems to be ignored when using the following constructs in a WHERE clause: Col=value1 COLLATE NOCASE OR Col=value2 Col IN(value COLLATE NOCASE) Col IN(value) COLLATE NOCASE [both are accepted, not sure which is valid syntax] It works in the simple case Col=value1 COLLATE NOCASE I have written a simple test script which demonstrates working queries and failing queries, which is attached, and reproduced here: # demo of sqlite bug with collate nocase # usage: sqlite3 :memory: # > .read sqlite_nocase_bug.sql # create temp table test (col text unique); insert into test (col) values('Test'); select '1:', * from test where col='Test'; -- works select '2:', * from test where col='test' collate nocase; -- works select '3:', * from test where col='test' collate nocase or col='other' collate nocase; -- returns no rows select '4:', * from test where col in ('test') collate nocase; -- returns no rows select '5:', * from test where col in ('test' collate nocase); -- returns no rows ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: sqlite3 3.29.0-2ubuntu0.1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 18:17:53 2020 SourcePackage: sqlite3 UpgradeStatus: Upgraded to eoan on 2019-10-23 (129 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1865364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862797] Re: Systemd does not allow hibernation when Chrome/chromium is running
Hmm, I spoke too fast. CanHibernate results initially in "yes" but hibernation actually fails and results in a locked screen. After unlock, second (failed) attempt to hibernate, second unlock, the hibernate button now disappears and $ busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanHibernate s "na" as before. -- 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/1862797 Title: Systemd does not allow hibernation when Chrome/chromium is running Status in systemd package in Ubuntu: Incomplete Bug description: 1/ Linux Mint 19.3/Ubuntu Bionic 18.04 LTS 2/ systemd: Installed: 237-3ubuntu10.38 3/ & 4/ Problem: hibernation stops working as soon as you start Chromium Steps to reproduce $ busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend s "yes" $ busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanHibernate s "yes" start chromium $ busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanHibernate s "na" $ sudo systemctl hibernate Failed to hibernate system via logind: Sleep verb not supported When this happens Cinnamon/Gnome no longer show hibernate buttons of course. $ systemd-inhibit --list Who: ecotech (UID 1000/ecotech, PID 1607/csd-media-keys) What: handle-power-key:handle-suspend-key:handle-hibernate-key Why: Cinnamon handling keypresses Mode: block Who: ModemManager (UID 0/root, PID 996/ModemManager) What: sleep Why: ModemManager needs to reset devices Mode: delay Who: ecotech (UID 1000/ecotech, PID 1656/csd-power) What: sleep Why: Cinnamon needs to lock the screen Mode: delay Who: ecotech (UID 1000/ecotech, PID 1656/csd-power) What: handle-lid-switch Why: Multiple displays attached Mode: block Who: NetworkManager (UID 0/root, PID 1012/NetworkManager) What: sleep Why: NetworkManager needs to turn off networks Mode: delay Who: UPower (UID 0/root, PID 1279/upowerd) What: sleep Why: Pause device polling Mode: delay Systemd-inhibit does not mention anything Chrome/Chromium related Stop Chromium and hibernation works again. Similar issues found: https://bugzilla.redhat.com/show_bug.cgi?id=1346908 $ cat /sys/power/state freeze mem disk $ cat /sys/power/disk [platform] shutdown reboot suspend test_resume Tried logind.conf default (all commented out) and below. No difference. $ cat /etc/systemd/logind.conf [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 HandlePowerKey=poweroff HandleSuspendKey=suspend HandleHibernateKey=hibernate #HandleLidSwitch=suspend #HandleLidSwitchDocked=ignore PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s #IdleAction=ignore #IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 #UserTasksMax=33% Can also not file a bug @ https://github.com/systemd/system since my version is more than 2 versions older than the last version (2.44.1). Thanks in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1862797/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862797] Re: Systemd does not allow hibernation when Chrome/chromium is running
Hi Dan, Here we go: $ free totalusedfree shared buff/cache available Mem: 31690904 185331627397880 1260984 243970828141244 Swap: 35651576 035651576 $ cat /proc/swaps FilenameTypeSizeUsedPriority /swapfile file2097148 0 -2 /dev/sda1 partition 335544280 0 So there is plenty of (unused) swap space. However, today I found out that with the latest SW update the problem can not be (so easily) reproduced: Kernel 5.3.0.28 --> 5.3.0.40 Chromium 79.0.3945 --> 80.0.3987 Systemd 237-3ubuntu10.38 --> 237-3ubuntu10.39 For example, the problem does no longer occur after a (forced) reboot (killing chromium) and letting chrome/chromium do a recovery. This was previously absolutely an easy way to reproduce the problem... $ busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanHibernate s "yes" So, at the moment it is unclear as from when the problem will start to occur, that is, if it is not solved by one of these patches. >From the change logs (http://changelogs.ubuntu.com/changelogs/pool/main/s/systemd/systemd_237-3ubuntu10.39/changelog, https://www.ubuntuupdates.org/bugs?package_name=chromium-browse), it's not obvious what could have fixed this... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1862797 Title: Systemd does not allow hibernation when Chrome/chromium is running Status in systemd package in Ubuntu: Incomplete Bug description: 1/ Linux Mint 19.3/Ubuntu Bionic 18.04 LTS 2/ systemd: Installed: 237-3ubuntu10.38 3/ & 4/ Problem: hibernation stops working as soon as you start Chromium Steps to reproduce $ busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend s "yes" $ busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanHibernate s "yes" start chromium $ busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanHibernate s "na" $ sudo systemctl hibernate Failed to hibernate system via logind: Sleep verb not supported When this happens Cinnamon/Gnome no longer show hibernate buttons of course. $ systemd-inhibit --list Who: ecotech (UID 1000/ecotech, PID 1607/csd-media-keys) What: handle-power-key:handle-suspend-key:handle-hibernate-key Why: Cinnamon handling keypresses Mode: block Who: ModemManager (UID 0/root, PID 996/ModemManager) What: sleep Why: ModemManager needs to reset devices Mode: delay Who: ecotech (UID 1000/ecotech, PID 1656/csd-power) What: sleep Why: Cinnamon needs to lock the screen Mode: delay Who: ecotech (UID 1000/ecotech, PID 1656/csd-power) What: handle-lid-switch Why: Multiple displays attached Mode: block Who: NetworkManager (UID 0/root, PID 1012/NetworkManager) What: sleep Why: NetworkManager needs to turn off networks Mode: delay Who: UPower (UID 0/root, PID 1279/upowerd) What: sleep Why: Pause device polling Mode: delay Systemd-inhibit does not mention anything Chrome/Chromium related Stop Chromium and hibernation works again. Similar issues found: https://bugzilla.redhat.com/show_bug.cgi?id=1346908 $ cat /sys/power/state freeze mem disk $ cat /sys/power/disk [platform] shutdown reboot suspend test_resume Tried logind.conf default (all commented out) and below. No difference. $ cat /etc/systemd/logind.conf [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 HandlePowerKey=poweroff HandleSuspendKey=suspend HandleHibernateKey=hibernate #HandleLidSwitch=suspend #HandleLidSwitchDocked=ignore PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s #IdleAction=ignore #IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 #UserTasksMax=33% Can also not file a bug @ https://github.com/systemd/system since my version is more than 2 versions older than the last version (2.44.1). Thanks in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1862797/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1865351] [NEW] Update to poppler 0.86.0 in Focal
Public bug reported: Please update to poppler 0.86.0 in Focal Release 0.86.0: core: * Fix link content exfiltration attack * Splash: Implement gouraudTriangleShadedFill for some non parametrized shadings * Fix case unsensitive search for Old Hungarian, Warang Citi, Medefaidrin and Adlam * Internal code improvements glib: * Automatic handle of page's cropbox on annots. Issue #129 * Fix memory leak if poppler_document_new_from_file fails * Minor speed optimization on poppler_page_get_annot_mapping utils: * pdfdetach: add 'savefile' option * pdftoppm/pdftocairo: Fix more odd/even mismatch qt5: * Fix loading from iodevice ** Affects: poppler (Ubuntu) Importance: Undecided Status: New ** Tags: focal upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1865351 Title: Update to poppler 0.86.0 in Focal Status in poppler package in Ubuntu: New Bug description: Please update to poppler 0.86.0 in Focal Release 0.86.0: core: * Fix link content exfiltration attack * Splash: Implement gouraudTriangleShadedFill for some non parametrized shadings * Fix case unsensitive search for Old Hungarian, Warang Citi, Medefaidrin and Adlam * Internal code improvements glib: * Automatic handle of page's cropbox on annots. Issue #129 * Fix memory leak if poppler_document_new_from_file fails * Minor speed optimization on poppler_page_get_annot_mapping utils: * pdfdetach: add 'savefile' option * pdftoppm/pdftocairo: Fix more odd/even mismatch qt5: * Fix loading from iodevice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1865351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863080] Re: Unable to use dead keys in Java apps
Thanks for your report. I would suspect that this problem is upstream in nature, so it would be good if you could submit an upstream issue too: https://github.com/ibus/ibus/issues/ If you do, please post the URL to the upstream issue here for tracking purposes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1863080 Title: Unable to use dead keys in Java apps Status in ibus package in Ubuntu: Confirmed Bug description: This is same bug as #540751, as it happens again in Ubuntu 19.10 with Java 11. Way of reproduce it: - Fresh Ubuntu 19.10 install. - Install default-jre. - Download (for example) lastest NetBeans version. - Edit a file in NetBeans, you can't insert characters like 'á'. The workaround is the same, define XMODIFIERS='' before launching the app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1863080/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863080] Re: Unable to use dead keys in Java apps
It worked for me this morning with IntelliJ IDEA, Ubuntu 19.10, and the following setup: $ echo $XMODIFIERS @im=ibus $ java -version openjdk version "11.0.5" 2019-10-15 OpenJDK Runtime Environment (build 11.0.5+10-b520.30) OpenJDK 64-Bit Server VM (build 11.0.5+10-b520.30, mixed mode) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1863080 Title: Unable to use dead keys in Java apps Status in ibus package in Ubuntu: Confirmed Bug description: This is same bug as #540751, as it happens again in Ubuntu 19.10 with Java 11. Way of reproduce it: - Fresh Ubuntu 19.10 install. - Install default-jre. - Download (for example) lastest NetBeans version. - Edit a file in NetBeans, you can't insert characters like 'á'. The workaround is the same, define XMODIFIERS='' before launching the app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1863080/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863080] Re: Unable to use dead keys in Java apps
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1863080 Title: Unable to use dead keys in Java apps Status in ibus package in Ubuntu: Confirmed Bug description: This is same bug as #540751, as it happens again in Ubuntu 19.10 with Java 11. Way of reproduce it: - Fresh Ubuntu 19.10 install. - Install default-jre. - Download (for example) lastest NetBeans version. - Edit a file in NetBeans, you can't insert characters like 'á'. The workaround is the same, define XMODIFIERS='' before launching the app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1863080/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp