[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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: defa
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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 dmi.board.vendor: LENOVO dm
[Desktop-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 Desktop 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 dmi.board.vendor: LENOVO
[Desktop-packages] [Bug 1865391] [NEW] Firefox starts to open PDFs in Libreoffice Draw
Private bug reported: 1) lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 2) apt-cache policy firefox firefox: Installiert: 73.0.1+build1-0ubuntu1 Installationskandidat: 73.0.1+build1-0ubuntu1 Versionstabelle: *** 73.0.1+build1-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) All of a sudden, PDFs from the web are opened in Libreoffice Draw. 4) The default program on KDE is Okular. I changed the PDF program back in Firefox settings to Okular. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1865391/+attachment/5332519/+files/AlsaInfo.txt ** Attachment removed: "Profile0Prefs.txt" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1865391/+attachment/5332527/+files/Profile0Prefs.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1865391/+attachment/5332520/+files/CurrentDmesg.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1865391/+attachment/5332521/+files/Dependencies.txt ** Attachment removed: "IpAddr.txt" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1865391/+attachment/5332522/+files/IpAddr.txt ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1865391/+attachment/5332528/+files/PulseList.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1865391/+attachment/5332525/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1865391/+attachment/5332523/+files/Lspci.txt ** Attachment removed: "PciNetwork.txt" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1865391/+attachment/5332524/+files/PciNetwork.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1865391/+attachment/5332526/+files/ProcEnviron.txt ** Description changed: 1) lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 2) apt-cache policy firefox firefox: - Installiert: 73.0.1+build1-0ubuntu1 - Installationskandidat: 73.0.1+build1-0ubuntu1 - Versionstabelle: - *** 73.0.1+build1-0ubuntu1 500 - 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages - 100 /var/lib/dpkg/status - + Installiert: 73.0.1+build1-0ubuntu1 + Installationskandidat: 73.0.1+build1-0ubuntu1 + Versionstabelle: + *** 73.0.1+build1-0ubuntu1 500 + 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages + 100 /var/lib/dpkg/status 3) All of a sudden, PDFs from the web are opened in Libreoffice Draw. - 4) The default program on KDE is Okular. I changed the PDF program back in Firefox settings to Okular. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 73.0.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: hotryce1756 F pulseaudio - /dev/snd/controlC0: hotryce1756 F pulseaudio - BuildID: 20200217142647 - Channel: Unavailable - CurrentDesktop: KDE - Date: Mon Mar 2 00:49:39 2020 - DefaultProfileExtensions: extensions.sqlite corrupt or missing - DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) - DefaultProfileLocales: extensions.sqlite corrupt or missing - DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:737 - DefaultProfileThemes: extensions.sqlite corrupt or missing - ForcedLayersAccel: False - InstallationDate: Installed on 2020-02-17 (13 days ago) - InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) - IpRoute: - default via 192.168.178.1 dev wlp3s0 proto dhcp metric 600 - 169.254.0.0/16 dev wlp3s0 scope link metric 1000 - 192.168.178.0/24 dev wlp3s0 proto kernel scope link src 192.168.178.39 metric 600 - Profile0Extensions: extensions.sqlite corrupt or missing - Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) - Profile0Locales: extensions.sqlite corrupt or missing - Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:737 - Profile0PrefSources: prefs.js - Profile0Themes: extensions.sqlite corrupt or missing - Profiles: - Profile1 (Default) - LastVersion=None/None (Out of date) - Profile0 - LastVersion=73.0.1/2020
[Desktop-packages] [Bug 1865388] [NEW] CDs are not mounted in file managers
Public bug reported: In a fresh LUbuntu Desktop 18.04 installation in VirtualBox 6.0, in both pcmanfm and nautilus I get the same error message when trying to insert a CD: Error mounting /dev/sr0 at /media/user/VBox_GAs_6.0.18: wrong fs type, bad option, bad superblock on /dev/sr0, missing codepage or helper program, or other error The inserted CDs can be perfectly mounted by root into other empty directory and read by normal mount command without any additional work. Suggested directory does not exist. If I created it manually as root, the other name was suggested. $ ls -ld /media/user drwxr-x---+ 2 root root 4096 Mar 2 01:55 /media/user $ ps aux| grep gv user 1152 0.0 0.3 286084 6944 ?Ssl 00:52 0:00 /usr/lib/gvfs/gvfsd user 1157 0.0 0.2 416112 5332 ?Sl 00:52 0:00 /usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes user 1321 0.0 0.4 300560 8420 ?Ssl 00:52 0:00 /usr/lib/gvfs/gvfs-udisks2-volume-monitor user 1325 0.0 0.3 372936 7656 ?Ssl 00:52 0:00 /usr/lib/gvfs/gvfs-afc-volume-monitor user 1330 0.0 0.2 268160 5852 ?Ssl 00:52 0:00 /usr/lib/gvfs/gvfs-goa-volume-monitor user 1334 0.0 0.2 269984 4792 ?Ssl 00:52 0:00 /usr/lib/gvfs/gvfs-mtp-volume-monitor user 1338 0.0 0.2 282772 5696 ?Ssl 00:52 0:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor user 1350 0.0 0.3 362220 7064 ?Sl 00:52 0:00 /usr/lib/gvfs/gvfsd-trash --spawner :1.5 /org/gtk/gvfs/exec_spaw/0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Mar 2 01:44:21 2020 SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: In a fresh LUbuntu Desktop 18.04 installation in VirtualBox 6.0, in both pcmanfm and nautilus I get the same error message when trying to insert a CD: - Error mounting /dev/sr0 at /media/user/VBox_GAs_6.0.18: wrong fs type, - bad option, bad superblock on /dev/sr0, missing codepage or helper - program, or other error + + Error mounting /dev/sr0 at /media/user/VBox_GAs_6.0.18: wrong fs type, bad option, bad superblock on /dev/sr0, missing codepage or helper program, or other error + - Suggested directory does not exist. + Suggested directory does not exist. If I created it manually, the other + name was suggested. $ ls -ld /media/user drwxr-x---+ 2 root root 4096 Mar 2 01:55 /media/user $ ps aux| grep gv user 1152 0.0 0.3 286084 6944 ?Ssl 00:52 0:00 /usr/lib/gvfs/gvfsd user 1157 0.0 0.2 416112 5332 ?Sl 00:52 0:00 /usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes user 1321 0.0 0.4 300560 8420 ?Ssl 00:52 0:00 /usr/lib/gvfs/gvfs-udisks2-volume-monitor user 1325 0.0 0.3 372936 7656 ?Ssl 00:52 0:00 /usr/lib/gvfs/gvfs-afc-volume-monitor user 1330 0.0 0.2 268160 5852 ?Ssl 00:52 0:00 /usr/lib/gvfs/gvfs-goa-volume-monitor user 1334 0.0 0.2 269984 4792 ?Ssl 00:52 0:00 /usr/lib/gvfs/gvfs-mtp-volume-monitor user 1338 0.0 0.2 282772 5696 ?Ssl 00:52 0:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor user 1350 0.0 0.3 362220 7064 ?Sl 00:52 0:00 /usr/lib/gvfs/gvfsd-trash --spawner :1.5 /org/gtk/gvfs/exec_spaw/0 - - The inserted CDs can be perfectly mounted by root into other empty directory and read by normal mount command without any additional work. + The inserted CDs can be perfectly mounted by root into other empty + directory and read by normal mount command without any additional work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Mar 2 01:44:21 2020 SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: In a fresh LUbuntu Desktop 18.04 installation in VirtualBox 6.0, in both pcmanfm and nautilus I get the same error message when trying to insert a CD: Error mounting /dev/sr0 at /media/user/VBox_GAs_6.0.18: wrong fs type, bad option, bad superblock on /dev/sr0, missing codepage or helper program, or other error - Suggested directory does not exist. If I created it manually, the other - name was suggested. + The inserted CDs can be perfectly mounted by root into other empty + directory and read by normal mount command without any additional work.
[Desktop-packages] [Bug 1835024] Re: Links triggered within most snap apps open in a separate browser session
Setting the default profile to `default-release` fixed the problem for me as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1835024 Title: Links triggered within most snap apps open in a separate browser session Status in snapd: Confirmed Status in xdg-utils package in Ubuntu: Confirmed Bug description: Hi, I've recently made a clean install of Ubuntu 19.10 (development release) and have noticed that whenever I try to open a link from one of the snap apps (being it Slack or Skype) the links although opened in the default browser are being opened in a separate session of the web browser. I am using Firefox and it is installed as a regular deb package (default). This is wrong and causes issues with history, sessions and settings not being shared between these windows. Now I have the default browser I use + a separate session for Slack and another one for Skype. Not to mention Firefox also acts just like another Slack/Skype window so dash displays these as two instances of the same app. To reproduce: * Install Ubuntu 19.10 (not sure if upgrade from 19.04 would lead to the same behaviour). * Confirm FFox is installed as a regular deb package. * Install I suppose almost any snap app, although I've only reproduced this with Slack and Skype and haven't tried to install other apps. System monitor also seems to be installed but when trying to open links from the about window - translators - individual names, it seems to do nothing. On the other hand Gnome calculator which is also installed as a snap package opens the link in the about dialog correctly = in my default browser session. ``` :~# which gnome-calculator /snap/bin/gnome-calculator ``` Thank you very much for looking into that. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1835024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865385] [NEW] eog doesn't appear as an option when opening images in "open with..."
Public bug reported: After updating to focal dev, when opening a jpg or png file, it is opened by Gimp instead of eog as it was in eoan. Also, eog doesn't even appear as an option in the "open with..." menu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: eog 3.35.91-0ubuntu1 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 18:42:07 2020 InstallationDate: Installed on 2018-02-23 (736 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: eog UpgradeStatus: Upgraded to focal on 2020-03-01 (0 days ago) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Summary changed: - eog doesn't as an option when opening images in "open with..." + eog doesn't appear as an option when opening images in "open with..." -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1865385 Title: eog doesn't appear as an option when opening images in "open with..." Status in eog package in Ubuntu: New Bug description: After updating to focal dev, when opening a jpg or png file, it is opened by Gimp instead of eog as it was in eoan. Also, eog doesn't even appear as an option in the "open with..." menu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: eog 3.35.91-0ubuntu1 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 18:42:07 2020 InstallationDate: Installed on 2018-02-23 (736 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: eog UpgradeStatus: Upgraded to focal on 2020-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1865385/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865379] [NEW] Raspberry Pi fails to wake from login
Public bug reported: Raspberry Pi 4 running Ubuntu server 20.04 Focal (and perhaps 19.10 Eoan) fails to wake from sleep when no user is logged in and the screen is sitting at the gdm login prompt. This has happened on two different systems. One system uses the official RPi 7 inch touchscreen. The other system has a 10 inch non- touchscreen from SunFounder. Nothing wakes the Pi: Keyboard, mouse, or touchscreen. After a user logs in and the screen locks on sleep the system wakes just fine with a lock screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8 Uname: Linux 5.4.0-1001-raspi2 armv7l ApportVersion: 2.20.11-0ubuntu18 Architecture: armhf CurrentDesktop: XFCE Date: Sun Mar 1 20:03:12 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-02-28 (2 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf focal uec-images -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1865379 Title: Raspberry Pi fails to wake from login Status in gdm3 package in Ubuntu: New Bug description: Raspberry Pi 4 running Ubuntu server 20.04 Focal (and perhaps 19.10 Eoan) fails to wake from sleep when no user is logged in and the screen is sitting at the gdm login prompt. This has happened on two different systems. One system uses the official RPi 7 inch touchscreen. The other system has a 10 inch non- touchscreen from SunFounder. Nothing wakes the Pi: Keyboard, mouse, or touchscreen. After a user logs in and the screen locks on sleep the system wakes just fine with a lock screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8 Uname: Linux 5.4.0-1001-raspi2 armv7l ApportVersion: 2.20.11-0ubuntu18 Architecture: armhf CurrentDesktop: XFCE Date: Sun Mar 1 20:03:12 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-02-28 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1865379/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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 UpgradeStatus: No upgrade
[Desktop-packages] [Bug 1865370] [NEW] login messagebox re-occurs despite autologin=true
Public bug reported: 'Enter password to unlock your keyring' I had to install seahorse and enter null password for a temporary fix to lightdm.conf not being sticky. This worked for a week or so, but today reverted back to keyring prompt. This thing has been plaguing several variants of Linux for many years on and off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-keyring 3.35.90-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: Budgie:GNOME Date: Mon Mar 2 08:25:30 2020 InstallationDate: Installed on 2020-01-23 (38 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200119) SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1865370 Title: login messagebox re-occurs despite autologin=true Status in gnome-keyring package in Ubuntu: New Bug description: 'Enter password to unlock your keyring' I had to install seahorse and enter null password for a temporary fix to lightdm.conf not being sticky. This worked for a week or so, but today reverted back to keyring prompt. This thing has been plaguing several variants of Linux for many years on and off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-keyring 3.35.90-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: Budgie:GNOME Date: Mon Mar 2 08:25:30 2020 InstallationDate: Installed on 2020-01-23 (38 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200119) SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1865370/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865371] [NEW] Mouse Cursor or Touchpad indicator/pointer not working
Public bug reported: after some updates this week, my mouse/touchapad cursor/indicator/pointer started not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 Uname: Linux 5.5.7-050507-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 20:29:07 2020 InstallationDate: Installed on 2017-07-14 (960 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170714) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-10-29T04:23:27.400327 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1865371 Title: Mouse Cursor or Touchpad indicator/pointer not working Status in gdm3 package in Ubuntu: New Bug description: after some updates this week, my mouse/touchapad cursor/indicator/pointer started not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 Uname: Linux 5.5.7-050507-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 20:29:07 2020 InstallationDate: Installed on 2017-07-14 (960 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170714) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-10-29T04:23:27.400327 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1865371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865365] Re: When saving any text in GEDIT the icons on the desktop disappear, return and change positions.
Here is another video showing the problem and verifying that the desktop icons disappear and change places when saving anything with gedit. https://imgur.com/F9BSAxg ** Attachment added: "Icons disappear from the desktop when saving text with gedit" https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1865365/+attachment/5332400/+files/deepin-screen-recorder_Opera_20200301153943.gif -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1865365 Title: When saving any text in GEDIT the icons on the desktop disappear, return and change positions. Status in gedit package in Ubuntu: New Bug description: Hello Ubuntu Team When saving any text in GEDIT the icons on the desktop disappear, return and change positions automatically, as can be seen in the video below. This defect was already presented in another situation in Ubuntu 18.04 Distros, but strangely it was excluded and I no longer find it in my sent BUGs. https://imgur.com/VPktWjY In Ubuntu 20.04 version the same situation is happening. Is it no longer allowed to have icons saved on the desktop? I hope that this time, the GEDIT and Ubuntu team will definitely find a solution to this problem that drags on from distro to this. I recorded the defect presented so that they can see and not disregard the information, let alone the video. I thank you for your attention. Serial. with ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.35.90-1 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 15:01:33 2020 InstallationDate: Installed on 2019-04-28 (308 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gedit UpgradeStatus: Upgraded to focal on 2020-02-04 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1865365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865365] [NEW] When saving any text in GEDIT the icons on the desktop disappear, return and change positions.
Public bug reported: Hello Ubuntu Team When saving any text in GEDIT the icons on the desktop disappear, return and change positions automatically, as can be seen in the video below. This defect was already presented in another situation in Ubuntu 18.04 Distros, but strangely it was excluded and I no longer find it in my sent BUGs. https://imgur.com/VPktWjY In Ubuntu 20.04 version the same situation is happening. Is it no longer allowed to have icons saved on the desktop? I hope that this time, the GEDIT and Ubuntu team will definitely find a solution to this problem that drags on from distro to this. I recorded the defect presented so that they can see and not disregard the information, let alone the video. I thank you for your attention. Serial. with ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.35.90-1 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 15:01:33 2020 InstallationDate: Installed on 2019-04-28 (308 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gedit UpgradeStatus: Upgraded to focal on 2020-02-04 (26 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Icons disappear from the desktop when saving texts with Gedit" https://bugs.launchpad.net/bugs/1865365/+attachment/5332365/+files/01.03.2020_14.57.36_REC.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1865365 Title: When saving any text in GEDIT the icons on the desktop disappear, return and change positions. Status in gedit package in Ubuntu: New Bug description: Hello Ubuntu Team When saving any text in GEDIT the icons on the desktop disappear, return and change positions automatically, as can be seen in the video below. This defect was already presented in another situation in Ubuntu 18.04 Distros, but strangely it was excluded and I no longer find it in my sent BUGs. https://imgur.com/VPktWjY In Ubuntu 20.04 version the same situation is happening. Is it no longer allowed to have icons saved on the desktop? I hope that this time, the GEDIT and Ubuntu team will definitely find a solution to this problem that drags on from distro to this. I recorded the defect presented so that they can see and not disregard the information, let alone the video. I thank you for your attention. Serial. with ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.35.90-1 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 15:01:33 2020 InstallationDate: Installed on 2019-04-28 (308 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gedit UpgradeStatus: Upgraded to focal on 2020-02-04 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1865365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865363] [NEW] nm-applet unstable behaviour when multiple AP have the same name
Public bug reported: Hi, I'm using a public wifi network to access the internet (in the spirit of FON - https://fon.com/). Let's name it XXX. There are multiple access points with the same name that "offer" this network. Many are in conflict with one another, using the same channel. Also, each AP is regularly switching channel, so I cannot associate a channel to a bssid and work with bssids instead of network name. nm-applet manages this situation very badly: - nm-applet seems to select the AP with the strongest signal, even if it is in conflict with 10s of others APs, leading to a very bad connexion, while still displaying an icon showing very good signal; - Also, as a consequence of its selection, quite often, nm-applet switches from one AP to the other, creating very instable situations, leading to even worse connexions throughput; - Trying to solve the problem, I saved the network, modified the connexion manually to fix one channel (let's name it YYY1), saved the connexion as "XXX-c[han]YYY1", then disconnected. Then I reconnected to the network, but nm-applet seemed to have switched to another AP using another chanel (YYY2), so I repeated the operation, and saved a "XXX-c[han]YYY2" network. Now, nm-applet, in its list of available networks, now randomly displays either simply "XXX", or at times "XXX >" (with a triangular char showing that there are sunetworks available) with "XXX-channelYYY1" are "XXX-channelYYY2" as sub networks. In the second case, if I select the network with less/no channel conflict, then the connexion is quite good and stable. > As can be seen in the attached picture, in the terminal, there are many access points available for XXX network, several using channel 11 or 7. As can also be seen there are 2 saved networks in nm-applet "Edit networks", one fixed to chan7, one fixed to chan11. However, nm-applet just lists "XXX" in its list of available networks... - Finally, there is no simple way in "Edit connections" to copy an existing configuration, so I cannot easily create a connection for each possible chanel. So, even if point above would be solved and nm-applet always display the avaliable "XXX-c[han]YYY" sub networks, I cannot simply create an entry for each channel and manually select the channel that is less in conflict than the others, based on my script that lists all the APs and the channels they use. Does anyone has a solution to this kind of situation? ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Attachment added: "nm-applet does not present saved networks as available" https://bugs.launchpad.net/bugs/1865363/+attachment/5332360/+files/2020-03-01-190718_1600x900_scrot.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1865363 Title: nm-applet unstable behaviour when multiple AP have the same name Status in network-manager-applet package in Ubuntu: New Bug description: Hi, I'm using a public wifi network to access the internet (in the spirit of FON - https://fon.com/). Let's name it XXX. There are multiple access points with the same name that "offer" this network. Many are in conflict with one another, using the same channel. Also, each AP is regularly switching channel, so I cannot associate a channel to a bssid and work with bssids instead of network name. nm-applet manages this situation very badly: - nm-applet seems to select the AP with the strongest signal, even if it is in conflict with 10s of others APs, leading to a very bad connexion, while still displaying an icon showing very good signal; - Also, as a consequence of its selection, quite often, nm-applet switches from one AP to the other, creating very instable situations, leading to even worse connexions throughput; - Trying to solve the problem, I saved the network, modified the connexion manually to fix one channel (let's name it YYY1), saved the connexion as "XXX-c[han]YYY1", then disconnected. Then I reconnected to the network, but nm-applet seemed to have switched to another AP using another chanel (YYY2), so I repeated the operation, and saved a "XXX-c[han]YYY2" network. Now, nm-applet, in its list of available networks, now randomly displays either simply "XXX", or at times "XXX >" (with a triangular char showing that there are sunetworks available) with "XXX-channelYYY1" are "XXX-channelYYY2" as sub networks. In the second case, if I select the network with less/no channel conflict, then the connexion is quite good and stable. > As can be seen in the attached picture, in the terminal, there are many access points available for XXX network, several using channel 11 or 7. As can also be seen there are 2 saved networks in nm-applet "Edit networks", one fixed to chan7, one fixed to chan11. However, nm- applet just lists "XXX" in its li
[Desktop-packages] [Bug 1865069] Re: Transmission doesn't use appindicator on focal
"Show transmission in the notification area" was checked. But it didn't show up in indicator. After reboot it does. Looks like some issue with the indicator. Thanks ** Changed in: transmission (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1865069 Title: Transmission doesn't use appindicator on focal Status in transmission package in Ubuntu: Invalid Bug description: Transmission is exiting after closing even when torrent is running. Usually it minimizes to app indicator when indicator application installed. I am testing this on both Unity & mate session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1865069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827428] Re: Mouse cursor left frozen copy of itself
Has this bug been re-added somewhere? If so, could someone post a link? I'm experiencing a dead cursor appearing in Ubuntu 19.10. I always run my monitors at 100% scaling and have dual monitors. I am also running an AMD RX Vega 56. I've been running in Wayland. I haven't seen if the issue occurs on X11 or not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1827428 Title: Mouse cursor left frozen copy of itself Status in mutter package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Bug description: Mouse cursor left freezed copy of itself over all the windows after login after lock screen. Functionality is not broken. It's just not aesthetic. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 2 16:10:09 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8392] InstallationDate: Installed on 2019-04-29 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 17-an0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8392 dmi.board.vendor: HP dmi.board.version: 40.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-an0xx dmi.product.sku: 2FP35EA#ACB dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-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.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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/mutter/+bug/1827428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865283] Re: gnome calendar icon missing Ubuntu 20.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-calendar (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1865283 Title: gnome calendar icon missing Ubuntu 20.04 Status in gnome-calendar package in Ubuntu: Confirmed Bug description: see screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1865283/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865337] [NEW] Gnome 3 keeps adding VLC in Alt+Tab
Public bug reported: Hi, I have these two settings on: https://askubuntu.com/questions/464946/force-alt-tab-to-switch-only-on-current-workspace-in-gnome-shell and https://superuser.com/questions/394376/how-to-prevent-gnome-shells-alttab-from-grouping-windows-from-similar-apps I would thus expect that Alt+Tab would only show apps from the current workspace. However, I have VLC on another workspace, and Gnome 3 always show VLC as first app in Alt+Tab. To remove the app, I have to go to VLC’s workspace, and focus its window. But then when VLC will switch song, it will go again as first app in Gnome 3’s Alt+Tab shortcut in ALL workspace. This is my number 1 issue in Gnome 3 that just makes me crazy: as VLC is shown as first app when I do Alt+Tab and that the current app is thus shwn second, doing Alt+tab quickly leaves the current app as current. Because VLC was shown first and the current app second, Alt+Tab goes to the second element, that is, the current one. This basically makes Alt+Tab completely useless for me, and I have to press the super key each time to switch windows. This is extremely annoying. Of course, I could just type Alt+tab+tab to switch to the third app, expect that (1) this is extremely counter-intuitive, and (2) depending on whether VLC is adding this “all workspace Alt+Tab notification” or not, the semantics is not the same. Note that I have prevented VLC to display any notification. This prevents VLC from adding overlay notification, but does not prevent VLC to do this Alt+Tab notification. This is incredibly annoying. As the semantics of “/org/gnome/shell/app- switcher/current-workspace-only” is *not* to only switch between current workspace (as it always adds VLC’s notificationsm whichever workspace VLC is), I suggest to either rename it or fix its behaviour to match its name. Attachment: a screenshot of my screen when I do the Alt+Tab. As the print-screen button in Gnome 3 frustratingly does not work when pressing Alt+Tab, I took it with my phone. In this case, I have Firefox opened as well as a console in this workspace, and VLC is in another workspace. I have a lot of other apps in other workspaces too, but they do not trigger this “Alt+Tab notification”. Regards, Martin. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 11:51:56 2020 DisplayManager: gdm3 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+berlinetta-cfl-r+X77 GsettingsChanges: b'org.gnome.shell' b'enable-hot-corners' b'true' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'show-battery-percentage' b'true' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2019-08-28 (185 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ** Attachment added: "Screenshot" https://bugs.launchpad.net/bugs/1865337/+attachment/5332335/+files/IMG_20200301_120334.jpg ** Description changed: Hi, I have these two settings on: https://askubuntu.com/questions/464946/force-alt-tab-to-switch-only-on-current-workspace-in-gnome-shell and https://superuser.com/questions/394376/how-to-prevent-gnome-shells-alttab-from-grouping-windows-from-similar-apps I would thus expect that Alt+Tab would only show apps from the current workspace. However, I have VLC on another workspace, and Gnome 3 always show VLC as first app in Alt+Tab. To remove the app, I have to go to VLC’s workspace, and focus its window. But then when VLC will switch song, it will go again as first app in Gnome 3’s Alt+Tab shortcut in ALL workspace. This is my number 1 issue in Gnome 3 that just makes me crazy: as VLC is shown as first app when I do Alt+Tab and that the current app is thus shwn second, doing Alt+tab quickly leaves the current app as current. Because VLC was shown first and the current app second, Alt+Tab goes to the second element, that is, the current one. This basically makes Alt+Tab completely useless for me, and I have to press the super key each time to switch windows. This is extremely annoying. Of course, I could just type Alt+tab+tab to switch to the third app, expect that (1)
[Desktop-packages] [Bug 1853120] Re: Xorg crashes with SIGBUS in drmmode_load_cursor_argb_check
Is there an ETA or workaround yet? Also having the issue when connected
to second display (4K30, HDMI via USB-C), perhaps coincidentally on an
XPS 13 9370.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1853120
Title:
Xorg crashes with SIGBUS in drmmode_load_cursor_argb_check
Status in xorg-server package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/af88d9cd45acf4632e47789e4661be6a47b4dbf1
---
I'm using a Dell XPS 9380 ("developer edition") connected to an
external monitor via USB C.
I've been running Ubuntu 19.04 for months with an external monitor
with no issues. On upgrading to 19.10 xorg crashes with a bus error
within a few seconds or minutes of using the external monitor.
The xorg package installed is 1:7.7+19ubuntu12
The system is stable without the external monitor.
The crash is consistently repeatable and the stack trace looks very
similar each time.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Nov 19 09:50:40 2019
DistUpgraded: 2019-11-17 14:04:28,024 ERROR got error from PostInstallScript
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00
[VGA controller])
Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
InstallationDate: Installed on 2019-07-09 (132 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
MachineType: Dell Inc. XPS 13 9380
ProcEnviron:
LANGUAGE=en_IE:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_IE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic
root=UUID=6b08154b-c421-45b7-bc75-c4feccc18654 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to eoan on 2019-11-17 (1 days ago)
dmi.bios.date: 10/01/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.0
dmi.board.name: 088MRW
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.8.0:bd10/01/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn088MRW:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9380
dmi.product.sku: 08AF
dmi.sys.vendor: Dell 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 19.2.1-1ubuntu1
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/xorg-server/+bug/1853120/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865314] Re: Suggest removal of xkeystone
** Bug watch added: Debian Bug tracker #579185 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579185 ** Also affects: x11-xserver-utils (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579185 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/1865314 Title: Suggest removal of xkeystone Status in x11-xserver-utils package in Ubuntu: New Status in x11-xserver-utils package in Debian: Unknown Bug description: Originally posted this as a question https://answers.launchpad.net/ubuntu/+question/689060 and was directed here. x11-xserver-utils includes the script /usr/bin/xkeystone xkeystone is a nickle script, and x11-xserver-utils does not depend on nickle, and even if you install nickle the script fails with a massive amount of syntax errors. (as tested with both bionic and focal packages). It's not clear to me what xkeystone is supposed to do - there's no man page or any documentation I could find. The only thing I was able to find are various threads where other distros remove this binary, so I suggest we remove it from ubuntu as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/1865314/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
