[Desktop-packages] [Bug 1915377] [NEW] Nautilus crashes on rename
Public bug reported: Bug Description: I wanted to rename a directory. Nautilus crashes with error 'Files not responding'. Name contains A-Z, a-z, 0-9, Underscore, Hyphen. Versions: Ubuntu Description:Ubuntu 20.10 Release:20.10 Nautilus (Files) 1:3.38.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 11 08:22:41 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(924, 1006)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-02-02 (8 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.38.0-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1 nautilus-share0.7.3-2ubuntu3 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1915377 Title: Nautilus crashes on rename Status in nautilus package in Ubuntu: New Bug description: Bug Description: I wanted to rename a directory. Nautilus crashes with error 'Files not responding'. Name contains A-Z, a-z, 0-9, Underscore, Hyphen. Versions: Ubuntu Description: Ubuntu 20.10 Release: 20.10 Nautilus (Files) 1:3.38.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 11 08:22:41 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(924, 1006)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-02-02 (8 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.38.0-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1915377/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
I've logged it for you: https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' 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+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 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/mesa/+bug/1871959/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
Please try this: sudo apt update sudo apt install linux-generic-hwe-20.04 and then reboot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' 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+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 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/mesa/+bug/1871959/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
Good news: This is only happening in kernel 5.4-5.6. No reports from kernel 5.8. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' 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+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 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/mesa/+bug/1871959/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
Some line number info from bug 1915375: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 _iris_batch_flush (batch=batch@entry=0x557db808c938, file=, file@entry=0x7fbec72f6d68 "../src/gallium/drivers/iris/iris_fence.c", line=line@entry=248) at ../src/gallium/drivers/iris/iris_batch.c:750 iris_fence_flush (ctx=0x557db808c4b0, out_fence=0x0, flags=) at ../src/gallium/drivers/iris/iris_fence.c:248 st_flush (flags=0, fence=0x0, st=0x557db80a9900) at ../src/mesa/state_tracker/st_cb_flush.c:60 ** Summary changed: - Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() + Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #4275 https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275 ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275 Importance: Unknown Status: Unknown -- 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/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' 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+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 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-
[Desktop-packages] [Bug 1907142] Re: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink
*** This bug is a duplicate of bug 1871959 *** https://bugs.launchpad.net/bugs/1871959 Mesa is the core graphics library. Everything uses it and you can't remove it. -- 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/1907142 Title: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink Status in evdi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Since my upgrade from 18.04 to 20.04 I experience rather frequent crashes of the X server. Nothing specific of applications running, presumably at videos (VLC, Youtube in a browser tab ...). If not yet attached, I'll attach the *.old log with the most recent trace. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Dec 7 22:15:34 2020 DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5300 [17aa:222b] InstallationDate: Installed on 2019-02-16 (660 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20CHS10P02 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago) dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N17ETB2W (2.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CHS10P02 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 11 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone: dmi.product.family: ThinkPad Helix 2nd dmi.product.name: 20CHS10P02 dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd dmi.product.version: ThinkPad Helix 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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+git20200226-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/evdi/+bug/1907142/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush()
Hi, I created an account on mesa forum. I don't really know what to tell, and which file send them. Can you help me and tell me what to say and send? Thanks, -- 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/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' 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+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 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/mesa/+bug/1871959/+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 1907142] Re: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink
*** This bug is a duplicate of bug 1871959 *** https://bugs.launchpad.net/bugs/1871959 Hi, Ok thanks. In bug 1871959 you ask to report to mesa, what's "mesa"? I don't think I have installed myself this. If it cause the bug, is it possible to remove it? Thanks, -- 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/1907142 Title: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink Status in evdi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Since my upgrade from 18.04 to 20.04 I experience rather frequent crashes of the X server. Nothing specific of applications running, presumably at videos (VLC, Youtube in a browser tab ...). If not yet attached, I'll attach the *.old log with the most recent trace. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Dec 7 22:15:34 2020 DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5300 [17aa:222b] InstallationDate: Installed on 2019-02-16 (660 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20CHS10P02 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago) dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N17ETB2W (2.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CHS10P02 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 11 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone: dmi.product.family: ThinkPad Helix 2nd dmi.product.name: 20CHS10P02 dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd dmi.product.version: ThinkPad Helix 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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+git20200226-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/evdi/+bug/1907142/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush()
Anyone affected by this crash, please report it to the Mesa developers at: https://gitlab.freedesktop.org/mesa/mesa/-/issues and then tell us the new issue ID. ** Tags added: groovy -- 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/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' 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+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 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/mesa/+bug/1871959/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush()
Weird: The debug symbols for iris_dri.so don't seem to have worked on this bug. They didn't work in comments #4 and #5 above and they didn't work in duplicate bug reports even when the debug symbols were definitely installed before the crash was reproduced. -- 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/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' 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+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 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/mesa/+bug/1871959/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush()
Re comment #9, I don't think mesa#1358 is the same as this. It's crashing with a different signal, in a different function :) -- 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/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' 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+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 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/mesa/+bug/1871959/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush()
** Summary changed: - Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() from dri2_make_current() + Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() -- 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/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' 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+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 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/mesa/+bug/1871959/+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 1914573] Re: kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 ... and then the display server crashes
*** This bug is a duplicate of bug 1871959 *** https://bugs.launchpad.net/bugs/1871959 ** This bug is no longer a duplicate of bug 1907142 [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink ** This bug has been marked a duplicate of bug 1871959 Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() -- 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/1914573 Title: kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 ... and then the display server crashes Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: The bug is that all at a sudden gnome reset to login screen. When i log again, the only "sound output" allowed is simulation, my devices are not displayed. I'm using - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug was present at that moment but i used less my ubuntu station). - Portable PC The bug happen - When I use my PC with screen pluged directly : some times - When I use my docking station with 144Hz display in DVI (https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently - When à Use my docking station and watch some full screen video : very frequently It seems to be linked to displayLink use, but not only because it happen too when i don't use the docking station. It seems to be frequently when i "Stress" the screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 4 10:17:54 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-08 (1183 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914573/+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 1906642] Re: Xorg crashes with abort in iris_dri.so
*** This bug is a duplicate of bug 1871959 *** https://bugs.launchpad.net/bugs/1871959 ** This bug is no longer a duplicate of bug 1907142 [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink ** This bug has been marked a duplicate of bug 1871959 Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() -- 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/1906642 Title: Xorg crashes with abort in iris_dri.so Status in mesa package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: System is crashing, logging out and i am constantly losing all my work if it's not saved Description: Ubuntu 20.04 LTS (fossa-beric-icl X31) Release: 20.04 N: Unable to locate package pkgname I expect not to happen (crash->log out) Instead, it happened ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 Uname: Linux 5.6.0-1033-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 12:33:11 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a2a] InstallationDate: Installed on 2020-09-19 (74 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 3501 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=6b577a12-8585-4836-a5fc-abc3857f42ce ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.name: 01D26F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.0:bd07/06/2020:svnDellInc.:pnVostro3501:pvr:rvnDellInc.:rn01D26F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3501 dmi.product.sku: 0A2A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1906642/+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 1907142] Re: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink
*** This bug is a duplicate of bug 1871959 *** https://bugs.launchpad.net/bugs/1871959 Great, thanks! That's a duplicate of bug 1871959 which has useful debug symbols. Unless/until any evidence can be found that this bug is not the same, I will mark it as a duplicate of bug 1871959. ** This bug has been marked a duplicate of bug 1871959 Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() -- 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/1907142 Title: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink Status in evdi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Since my upgrade from 18.04 to 20.04 I experience rather frequent crashes of the X server. Nothing specific of applications running, presumably at videos (VLC, Youtube in a browser tab ...). If not yet attached, I'll attach the *.old log with the most recent trace. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Dec 7 22:15:34 2020 DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5300 [17aa:222b] InstallationDate: Installed on 2019-02-16 (660 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20CHS10P02 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago) dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N17ETB2W (2.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CHS10P02 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 11 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone: dmi.product.family: ThinkPad Helix 2nd dmi.product.name: 20CHS10P02 dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd dmi.product.version: ThinkPad Helix 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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+git20200226-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/evdi/+bug/1907142/+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 1915125] Re: xorg crash
*** This bug is a duplicate of bug 1871959 *** https://bugs.launchpad.net/bugs/1871959 ** This bug is no longer a duplicate of bug 1907142 [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink ** This bug has been marked a duplicate of bug 1871959 Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() -- 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/1915125 Title: xorg crash Status in xorg-server package in Ubuntu: New Bug description: follow up for https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1914573 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Feb 9 08:49:45 2021 DistUpgraded: 2020-07-01 20:04:15,616 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6509] InstallationDate: Installed on 2017-11-08 (1188 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Notebook W65_W67RZ1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=1dd47b4a-9e41-4e2b-b247-2a3123742422 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-07-01 (222 days ago) dmi.bios.date: 09/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ1 dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/19/2016:svnNotebook:pnW65_W67RZ1:pvrNotApplicable:rvnNotebook:rnW65_W67RZ1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ1 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Thu Feb 4 18:39:51 2021 xserver.configfile: default xserver.errors: modeset(G0): glamor initialization failed modeset(G1): glamor initialization failed modeset(G2): glamor initialization failed modeset(G3): glamor initialization failed xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.9-2ubuntu1.2~20.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1915125/+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 1915375] Re: Xorg crashed with SIGABRT in __GI_raise()
*** This bug is a duplicate of bug 1871959 *** https://bugs.launchpad.net/bugs/1871959 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1871959, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1915375/+attachment/5462544/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1915375/+attachment/5462547/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1915375/+attachment/5462560/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1915375/+attachment/5462562/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1915375/+attachment/5462563/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1915375/+attachment/5462564/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1915375/+attachment/5462565/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1871959 Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() from dri2_make_current() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1915375 Title: Xorg crashed with SIGABRT in __GI_raise() Status in xorg-server package in Ubuntu: New Bug description: This bug report is to help already opened bug : https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1907142 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 14:15:47 2021 DistUpgraded: 2020-07-01 20:04:15,616 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1610874811 GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6509] InstallationDate: Installed on 2017-11-08 (1190 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Notebook W65_W67RZ1 ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcCwd: /home/ppaquin ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=1dd47b4a-9e41-4e2b-b247-2a3123742422 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 _iris_batch_flush (batch=batch@entry=0x557db808c938, file=, file@entry=0x7fbec72f6d68 "../src/gallium/drivers/iris/iris_fence.c", line=line@entry=248) at ../src/gallium/drivers/iris/iris_batch.c:750 iris_fence_flush (ctx=0x557db808c4b0, out_fence=0x0, flags=) at ../src/gallium/drivers/iris/iris_fence.c:248 st_flush (flags=0, fence=0x0, st=0x557db80a9900) at ../src/mesa/state_tracker/st_cb_flush.c:60 Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2020-07-01 (224 days ago) UserGroups: adm cdrom dip kvm lpadmin plugdev sambashare sudo dmi.bios.date: 09/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ1 dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/19/2016:svnNotebook:pnW65_W67RZ1:pvrNotApplicable:rvnNotebook:rnW65_W67RZ1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_
[Desktop-packages] [Bug 1907142] Re: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink
Well if I couldn't use ubuntu bug, I could use that, hope it'll help : apport-cli -c /var/crash/_usr_lib_xorg_Xorg.1000.crash It then create this bug entry : https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1915375 -- 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/1907142 Title: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink Status in evdi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Since my upgrade from 18.04 to 20.04 I experience rather frequent crashes of the X server. Nothing specific of applications running, presumably at videos (VLC, Youtube in a browser tab ...). If not yet attached, I'll attach the *.old log with the most recent trace. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Dec 7 22:15:34 2020 DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5300 [17aa:222b] InstallationDate: Installed on 2019-02-16 (660 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20CHS10P02 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago) dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N17ETB2W (2.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CHS10P02 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 11 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone: dmi.product.family: ThinkPad Helix 2nd dmi.product.name: 20CHS10P02 dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd dmi.product.version: ThinkPad Helix 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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+git20200226-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/evdi/+bug/1907142/+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 1907142] Re: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink
Oh I forgot, Yes, i have installed dbgsym : $ dpkg -l| grep dbgsym ii libgl1-mesa-dri-dbgsym:amd64 20.2.6-0ubuntu0.20.04.1 amd64 debug symbols for libgl1-mesa-dri ii xserver-xorg-core-dbgsym 2:1.20.9-2ubuntu1.2~20.04.1 amd64 debug symbols for xserver-xorg-core -- 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/1907142 Title: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink Status in evdi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Since my upgrade from 18.04 to 20.04 I experience rather frequent crashes of the X server. Nothing specific of applications running, presumably at videos (VLC, Youtube in a browser tab ...). If not yet attached, I'll attach the *.old log with the most recent trace. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Dec 7 22:15:34 2020 DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5300 [17aa:222b] InstallationDate: Installed on 2019-02-16 (660 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20CHS10P02 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago) dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N17ETB2W (2.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CHS10P02 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 11 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone: dmi.product.family: ThinkPad Helix 2nd dmi.product.name: 20CHS10P02 dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd dmi.product.version: ThinkPad Helix 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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+git20200226-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/evdi/+bug/1907142/+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 1907142] Re: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink
Hi, Ok, if there's nothing here about xorg crash, how may I provide you more information about that : ppaquin@PORTABLE-PPAQUIN:/var/crash$ ls -alrt . -rw-r- 1 username whoopsie 17322105 févr. 10 14:15 _usr_lib_xorg_Xorg.1000.crash It seems I have some informations on my system about crash. but the following command doesn't work. I have a message with some "internal error" : sudo ubuntu-bug _usr_lib_xorg_Xorg.1000.crash Thanks, -- 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/1907142 Title: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink Status in evdi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Since my upgrade from 18.04 to 20.04 I experience rather frequent crashes of the X server. Nothing specific of applications running, presumably at videos (VLC, Youtube in a browser tab ...). If not yet attached, I'll attach the *.old log with the most recent trace. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Dec 7 22:15:34 2020 DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5300 [17aa:222b] InstallationDate: Installed on 2019-02-16 (660 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20CHS10P02 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago) dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N17ETB2W (2.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CHS10P02 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 11 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone: dmi.product.family: ThinkPad Helix 2nd dmi.product.name: 20CHS10P02 dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd dmi.product.version: ThinkPad Helix 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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+git20200226-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/evdi/+bug/1907142/+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 1014897] Re: [sound-nua] sound preference does not provide ac3 passthrough spdif in 5.1 speaker test
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1014897 Title: [sound-nua] sound preference does not provide ac3 passthrough spdif in 5.1 speaker test Status in gnome-control-center package in Ubuntu: Won't Fix Bug description: This sound card (Realtek ALC892) is 7.1 channel capable via the digital out (SPDIF). However, Ubuntu is not recognizing it as such and on the sound configuration we can only see the stereo parameters (right and left). As you can see in the attached picture, the rear and subwoofer parameters are grayed out, as if the card didn't support it. I have connected it to a 5.1 amplifier and played a DTS suround file. Unfortunately the sound coming out is simply stereo. No 5.1 surround. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jabss 1592 F pulseaudio jabss 3738 F alsamixer /dev/snd/controlC0: jabss 1592 F pulseaudio Card0.Amixer.info: Card hw:0 'Generic'/'HD-Audio Generic at 0xfef44000 irq 48' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 6 Simple ctrls : 1 Card0.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Card1.Amixer.info: Card hw:1 'Generic_1'/'HD-Audio Generic at 0xfef4 irq 16' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,18498892,00100302' Controls : 40 Simple ctrls : 19 Date: Tue Jun 19 00:29:21 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PackageArchitecture: all ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed Symptom_Card: Built-in Audio - HD-Audio Generic Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: Only some of outputs are working Title: [To Be Filled By O.E.M., Realtek ALC892, Grey SPDIF Out, Rear] Playback problem UpgradeStatus: Upgraded to precise on 2012-04-27 (52 days ago) dmi.bios.date: 02/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: A75M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd02/09/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA75M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1014897/+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 1915322] Re: Xorg freeze
Thanks for the bug report. Next time the freeze happens, please try Ctrl+Alt+F1 or F2 to find the login screen. If that doesn't work then please reboot and then run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. Please also try these instructions in case the freeze is due to something crashing: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Tags added: nvidia ** Tags added: hybrid ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Package changed: ubuntu => nvidia-graphics-drivers-460 (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/1915322 Title: Xorg freeze Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Bug description: Hey guys! First up, I've been using ubuntu on and off since I was about twelve, and I love this os.Thank you guys for the hard work! Second, I've been having an unfortunate bug on my laptop for quite some time now. I'm using an acer aspire e5-575g-55nw and every time my laptop goes into suspend, I can't get back to any kind of GUI after waking it up, instead going to a black screen with a single blinking white - symbol in the top left corner. i've tried just about every fix I could find on the internet, without being able to find any way back to my login screen or desktop. Note that this does not happen when my laptop goes to sleep on it's own after a set ammount of time, only when i put it into suspend or close the lid. I hope I included enough information, please let me know if you need any other information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 15:15:18 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094] Subsystem: Acer Incorporated [ALI] Acer Aspire E5-575G [1025:1094] InstallationDate: Installed on 2021-02-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57f2 Realtek Semiconductor Corp. HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=f1010786-e2a1-44b4-a3b8-6a48523960df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.release: 1.47 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.47 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.47 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.50 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.47:bd09/06/2018:br1.47:efr2.50:svnAcer:pnAspireE5-575G:pvrV1.47:rvnAcer:rnIronman_SK:rvrV1.47:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.sku: Aspire E5-575G_115F_1.47 dmi.product.version: V1.47 dmi
[Desktop-packages] [Bug 1915358] Re: sound hdmi 5.1 subwoofer always disabled
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1915358 Title: sound hdmi 5.1 subwoofer always disabled Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: In System Sound Settings, I chose HDMI 5.1 audio, but there is no sound from my subwoofer in any audio application. The System Sound Settings for HDMI 5.1 always shows a disabled subwoofer slider. When I open the test window and hit the subwoofer icon button, no sound is produced. But if I open Pulse Audio Volume Control -> Output Devices -> (unlock icon), all show mid-volume on the slider except for subwoffer. But the subwoofer slider is enabled. So I slide it to mid-volume, and go back to System Sound Settings -> test window and hit the subwoofer icon button, I hear my subwoofer is working fine. I also then hear the subwoofer in all audio applications. If I were to touch the System Sound Slider for the subwoofer, it immediately stops working again. I can fix it again in Pulse Audio Volumne Control again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 19:47:38 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2021-01-25 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1915358/+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 1915306] Re: Universal Access "Large Text" setting not retained on reboot
** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Tags added: nvidia ** Tags added: a11y ** Tags added: xrandr-scaling -- 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/1915306 Title: Universal Access "Large Text" setting not retained on reboot Status in mutter package in Ubuntu: New Bug description: I am using the Universal Access "Large Text" setting. Upon reboot, the setting appears to be enabled, based on GUI switch appearance, but the font is very small (not sure of scaling factor, but appears to be < 1.00 - I will check this and report back next time I reboot). I have to turn the "Large Text" setting off, which actually makes the text larger, then turn it back on again, which makes it larger still (the size that I need). This does not happen on a log off; only on a reboot. If I simply log out and back in, the setting remains as it should (scaling factor of 1.25). I am aware that there is already a bug report for this problem, but it is marked as resolved last October. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-7642.47~1612288990~20.04~b8113e7~dev-generic 5.8.18 Uname: Linux 5.8.0-7642-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 460.39 Thu Jan 21 21:54:06 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Feb 10 12:37:59 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:50d3] NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:50d3] MachineType: System76 Oryx Pro ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-7642-generic root=UUID=bbcec58e-9495-49a4-9c29-34c6a65e3edf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2021 dmi.bios.release: 4.13 dmi.bios.vendor: coreboot dmi.bios.version: 2021-01-19_d6d37c0 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp6 dmi.chassis.type: 9 dmi.chassis.vendor: System76 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr2021-01-19_d6d37c0:bd01/19/2021:br4.13:efr0.0:svnSystem76:pnOryxPro:pvroryp6:rvnSystem76:rnOryxPro:rvroryp6:cvnSystem76:ct9:cvr: dmi.product.name: Oryx Pro dmi.product.version: oryp6 dmi.sys.vendor: System76 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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+git20200226-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/mutter/+bug/1915306/+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 1915270] Re: Gnome Shell fails to list some apps with .desktop files
Thanks for the bug report. I certainly can't find any other reports of this problem. The first thing to check is whether any of these extensions are causing side effects which might explain the bug: 'sound-output-device-choo...@kgshank.net', 'refresh-w...@kgshank.net', 'wifisignalstren...@tomin.site', 'cast-to...@rafostar.github.com', 'auto-move-wind...@gnome-shell-extensions.gcampax.github.com', 'extensi...@abteil.org', 'places-menu@gnome-shell- extensions.gcampax.github.com', 'drive-menu@gnome-shell- extensions.gcampax.github.com', 'screenshot-window-sizer@gnome-shell- extensions.gcampax.github.com', 'apps-menu@gnome-shell- extensions.gcampax.github.com', 'hidetop...@mathieu.bidon.ca', 'arcm...@arcmenu.com', 'vbox-app...@gs.eros2.info' So please uninstall all of those, restart and retest. If the bug still occurs after that then please report it to the developers at: https://gitlab.gnome.org/GNOME/gnome-shell/issues ** Summary changed: - After upgrade to 20.10 multiple apps dropped + Gnome Shell fails to list some apps with .desktop files ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1915270 Title: Gnome Shell fails to list some apps with .desktop files Status in gnome-shell package in Ubuntu: Incomplete Bug description: VirtualBox does not show up anywhere in Gnome-shell as an application. Wine doesn't show up anywhere in Gnome-shell as an application. Those are two of the more egregious examples. I can run them from the command line. The .desktop entries clearly exist in /usr/share/applications. I've verified and reverified all the .desktop entries and checked them against the Gnome documentation to verify everything is correct. Yet it simply refuses to load these apps. A dump of the VirtualBox entry dumped below (even editted it to use absolute path).Similar problems with Wine which was installed via Ubuntu software so no reason for it to be rejected/disappear. Ubuntu: 20.10 VirtualBox: Installed: 6.1.16-dfsg-6~ubuntu1.20.10.1 (from ubuntu Groovy repository) Wine: Candidate: 5.0-3ubuntu1 (also from Groovy repository) ...so...all are pointing to the current repository (Groovy). I'm at a loss here even how to fix it since I can't really "upgrade" or "fix" the .desktop entry since nothing is wrong with those. They are just "ghosts" as far as Gnome-shell is concerned. [Desktop Entry] Name=VirtualBox GenericName=PC virtualization solution Type=Application Exec=/usr/bin/VirtualBox TryExec=VirtualBox Keywords=virtualization; Keywords[de]=Virtualisierung; Keywords[ru]=виртуализация; MimeType=application/x-virtualbox-vbox;application/x-virtualbox-vbox-extpack;application/x-virtualbox-ovf;application/x-virtualbox-ova; Icon=virtualbox Categories=Emulator;System;Utility; Actions=Manager; Comment=Run several virtual systems on a single host computer Comment[de]=Mehrere virtuelle Maschinen auf einem einzigen Rechner ausführen Comment[it]=Esegui più macchine virtuali su un singolo computer Comment[ko]=가상 머신 Comment[pl]=Uruchamianie wielu systemów wirtualnych na jednym komputerze gospodarza Comment[ru]=Запуск нескольких виртуальных машин на одном компьютере Comment[sv]=Kör flera virtuella system på en enda värddator [Desktop Action Manager] Exec=VirtualBox Name=Open Oracle VM Manager Name[de]=Oracle VM Manager öffnen ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 08:01:17 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-07 (552 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: linux-image-5.8.0-43-generic linux-base RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2021-02-07 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915270/+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 1907142] Re: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink
Thanks, but it looks the same :( (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x557db676a59c] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fbec831b41f] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fbec815818b] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fbec8137859] (EE) unw_get_proc_name failed: no unwind info found [-10] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fbec62a8aec] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fbec6ffac9c] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) If you already have libgl1-mesa-dri- dbgsym_20.2.6-0ubuntu0.20.04.1_amd64.ddeb installed then it seems the problem right now is that Xorg doesn't know how to load debug symbols. https://errors.ubuntu.com/ is also not showing me any Xorg crashes from your system since January. So I think we need to do one of two things: * Attach a debugger to the Xorg process before it crashes; or * Configure Xorg to dump core properly and not try to catch its own crashes. -- 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/1907142 Title: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink Status in evdi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Since my upgrade from 18.04 to 20.04 I experience rather frequent crashes of the X server. Nothing specific of applications running, presumably at videos (VLC, Youtube in a browser tab ...). If not yet attached, I'll attach the *.old log with the most recent trace. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Dec 7 22:15:34 2020 DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5300 [17aa:222b] InstallationDate: Installed on 2019-02-16 (660 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20CHS10P02 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago) dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N17ETB2W (2.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CHS10P02 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 11 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone: dmi.product.family: ThinkPad Helix 2nd dmi.product.name: 20CHS10P02 dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd dmi.product.version: ThinkPad Helix 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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+git20200226-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/evdi/+bug/1907142/+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 1915198] Re: [Toshiba Satellite U300] "Dummy output" instead of the audio device ALC268
** Summary changed: - "Dummy output" instead of the audio device ALC268 + [Toshiba Satellite U300] "Dummy output" instead of the audio device ALC268 ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1915198 Title: [Toshiba Satellite U300] "Dummy output" instead of the audio device ALC268 Status in pulseaudio package in Ubuntu: New Bug description: Hello Support, "Dummy output" in Sound settings. nothing works. $ aplay -l List of PLAYBACK Hardware Devices $ alsa-info.sh link to http://alsa- project.org/db/?f=834b3fe04e2e1c74c7f2a84b6fb698e6e49db8fa. # dmidecode -t system # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 2.4 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: TOSHIBA Product Name: Satellite U300 Version: PSU30E-01M01DRU # lspci |grep Audio 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 03) Subsystem: Toshiba Corporation 82801H (ICH8 Family) HD Audio Controller [1179:ff50] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel Physical device is ALC268. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.10 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 22:37:35 2021 InstallationDate: Installed on 2021-02-09 (0 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2009 dmi.bios.vendor: TOSHIBA dmi.bios.version: V5.10 dmi.board.name: Satellite U300 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV5.10:bd01/15/2009:svnTOSHIBA:pnSatelliteU300:pvrPSU30E-01M01DRU:rvnTOSHIBA:rnSatelliteU300:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U300 dmi.product.version: PSU30E-01M01DRU dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1915198/+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 1915358] [NEW] sound hdmi 5.1 subwoofer always disabled
Public bug reported: In System Sound Settings, I chose HDMI 5.1 audio, but there is no sound from my subwoofer in any audio application. The System Sound Settings for HDMI 5.1 always shows a disabled subwoofer slider. When I open the test window and hit the subwoofer icon button, no sound is produced. But if I open Pulse Audio Volume Control -> Output Devices -> (unlock icon), all show mid-volume on the slider except for subwoffer. But the subwoofer slider is enabled. So I slide it to mid-volume, and go back to System Sound Settings -> test window and hit the subwoofer icon button, I hear my subwoofer is working fine. I also then hear the subwoofer in all audio applications. If I were to touch the System Sound Slider for the subwoofer, it immediately stops working again. I can fix it again in Pulse Audio Volumne Control again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 19:47:38 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2021-01-25 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (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-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1915358 Title: sound hdmi 5.1 subwoofer always disabled Status in gnome-control-center package in Ubuntu: New Bug description: In System Sound Settings, I chose HDMI 5.1 audio, but there is no sound from my subwoofer in any audio application. The System Sound Settings for HDMI 5.1 always shows a disabled subwoofer slider. When I open the test window and hit the subwoofer icon button, no sound is produced. But if I open Pulse Audio Volume Control -> Output Devices -> (unlock icon), all show mid-volume on the slider except for subwoffer. But the subwoofer slider is enabled. So I slide it to mid-volume, and go back to System Sound Settings -> test window and hit the subwoofer icon button, I hear my subwoofer is working fine. I also then hear the subwoofer in all audio applications. If I were to touch the System Sound Slider for the subwoofer, it immediately stops working again. I can fix it again in Pulse Audio Volumne Control again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 19:47:38 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2021-01-25 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1915358/+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 1894593] Re: Fractional scaling switch doesn't work in Wayland sessions
This bug was fixed in the package gnome-control-center - 1:3.38.3-1ubuntu3 --- gnome-control-center (1:3.38.3-1ubuntu3) hirsute; urgency=medium * d/p/0024-display-Allow-fractional-scaling-to-be-enabled.patch: - Support kms renderer in fractional scaling toggle (LP: #1894593) - Change logical layout mode when switching mode in wayland -- Marco Trevisan (Treviño) Wed, 10 Feb 2021 13:43:55 +0100 ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1894593 Title: Fractional scaling switch doesn't work in Wayland sessions Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Hitting the “fractional scaling” toggle in the “Screen Display” tab in gnome-control-centre page doesn't work - although the toggle changes to the “enabled” state there's no visible effect, and if I switch to a different page (or close g-c-c) and then switch back (or reopen g-c-c) then the toggle is back in the disabled state. Running from the command line, I see; (gnome-control-center:171131): display-cc-panel-WARNING **: 13:34:19.407: no sunset data, using 16.00 (gnome-control-center:171131): display-cc-panel-WARNING **: 13:34:19.407: no sunrise data, using 8.00 (gnome-control-center:171131): display-cc-panel-CRITICAL **: 13:34:21.972: file ../panels/display/cc-display-config.c: line 452 (get_fractional_scaling_key): should not be reached ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.37.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0+bcachefs.git20200701.7e04f345-1-generic 5.8.4 Uname: Linux 5.8.0+bcachefs.git20200701.7e04f345-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 7 13:34:44 2020 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to groovy on 2020-06-22 (76 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1894593/+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 1908921] Re: No system tray detected by hp-systray
I have found a workaround by adding a sleep period of 5s in the startup application command line for my synergy and hplip-systray on ubuntu 20.04: sh -c "sleep 5 ; exec /usr/bin/synergy" sh -c "sleep 5 ; exec hp-systray -x" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1908921 Title: No system tray detected by hp-systray Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: I have hp-systray -x as one of the startup applications when I login. This app exits with the following error: HPLIP Status service No system tray detected on this system. Unable to start, exiting. Once logged in, if I start hp-systray -x from the terminal it works fine. This started happening after updating gnome-shell-extension- appindicator from version 33-1 to version 33.1-0ubuntu0.20.04.1. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 11:41:23 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-10 (1655 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1908921/+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 1846334] Re: cupsd assert failure: free(): invalid pointer
I confirm the hirsute version fixes the issue. I created https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/ recently without having seen this bug report, and I'm pretty confident it's the same issue. I reinstalled groovy on a VM, confirmed the bug occurred (it did), rebuilt 2.3.3op1 from hirsute and installed it. The problem no longer occurs after that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1846334 Title: cupsd assert failure: free(): invalid pointer Status in cups package in Ubuntu: Fix Committed Bug description: Just running in the background, no user action (printing) ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: cups-daemon 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: free(): invalid pointer Date: Tue Oct 1 19:41:35 2019 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2019-02-09 (234 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) Lpstat: device for HP_LaserJet_CM1415fn_44A808_: implicitclass://HP_LaserJet_CM1415fn_44A808_/ device for Samsung_C48x_Series_SEC84251900EE44_: implicitclass://Samsung_C48x_Series_SEC84251900EE44_/ MachineType: Dell Inc. Latitude E6530 Papersize: letter PpdFiles: HP_LaserJet_CM1415fn_44A808_: LaserJet CM1415fn - IPP Everywhere Samsung_C48x_Series_SEC84251900EE44_: C48x Series - IPP Everywhere ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f923ecb83a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f923ecb652a "free(): invalid pointer") at malloc.c:5332 _int_free (av=, p=, have_lock=0) at malloc.c:4173 ?? () from /lib/x86_64-linux-gnu/libcups.so.2 ippDelete () from /lib/x86_64-linux-gnu/libcups.so.2 Title: cupsd assert failure: free(): invalid pointer UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A22 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.sku: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1846334/+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 699922]
Probably https://searchfox.org/comm- central/source/mailnews/base/src/nsMessengerUnixIntegration.cpp#370 should pass in the windowwatcher activeWindow instead of 0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/699922 Title: Thunderbird displays notification on wrong monitor Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird In a multiple monitor setup, Thunderbird displays its notification in the bottom right of the leftmost monitor, rather than the window on which it is currently active. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: thunderbird 3.1.7+build3+nobinonly-0ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.35-24.42-generic-pae 2.6.35.8 Uname: Linux 2.6.35-24-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Jan 7 16:01:00 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/699922/+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 1915175] Re: wifi network stops working and shows a green wifi icon
** Description changed: I recently started using ubuntu 20.04, I connected it to my 2.4ghz Wi-Fi, at first the wifi worked fine, but suddenly the wifi stopped connecting, and after a few seconds it said "unable to activate network". I checked the "additional drivers tab" and it showed my wifi adapter, but it said "this device is using an alternate driver". right now I'm using my 5ghz Wi-Fi network, but sometimes it happens that it stops working, usually after suspend. + + UPDATE #1: Apparently it's working now, I suppose it's from an update. + Anyways I guess it's ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 12:09:28 2021 InstallationDate: Installed on 2021-02-08 (0 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) IpRoute: - default via 192.168.1.254 dev wlp1s0 proto dhcp metric 600 - 169.254.0.0/16 dev wlp1s0 scope link metric 1000 - 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.8 metric 600 + default via 192.168.1.254 dev wlp1s0 proto dhcp metric 600 + 169.254.0.0/16 dev wlp1s0 scope link metric 1000 + 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.8 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: - [connection] - wifi.powersave = 2 + [connection] + wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2021-02-08T22:50:26.196692 nmcli-dev: - DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH - wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 Betancur 5G cda009c8-c845-4366-8436-8e9c44da2cbf /org/freedesktop/NetworkManager/ActiveConnection/1 - lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- + DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH + wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 Betancur 5G cda009c8-c845-4366-8436-8e9c44da2cbf /org/freedesktop/NetworkManager/ActiveConnection/1 + lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.22.10 connected started full enabled enabled enabled enabled enabled + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.22.10 connected started full enabled enabled enabled enabled enabled ** Description changed: I recently started using ubuntu 20.04, I connected it to my 2.4ghz Wi-Fi, at first the wifi worked fine, but suddenly the wifi stopped connecting, and after a few seconds it said "unable to activate network". I checked the "additional drivers tab" and it showed my wifi adapter, but it said "this device is using an alternate driver". right now I'm using my 5ghz Wi-Fi network, but sometimes it happens that it stops working, usually after suspend. UPDATE #1: Apparently it's working now, I suppose it's from an update. - Anyways I guess it's + Anyways I guess it's fixed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 12:09:28 2021 InstallationDate: Installed on 2021-02-08 (0 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) IpRoute: default via 192.168.1.254 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.8 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersa
[Desktop-packages] [Bug 1890924] Re: Location services work with location services off, 20.04
I'm marking this fixed as geoclue 2.5.7 is already in the development series (hirsute). I have added the rls-gg-incoming and rls-hh-incoming tags to mark it as a candidate for a SRU to groovy (20.10) and focal (20.04). This will be reviewed at the next desktop team meeting. ** Tags added: rls-ff-incoming rls-gg-incoming ** Changed in: geoclue-2.0 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1890924 Title: Location services work with location services off, 20.04 Status in geoclue-2.0 package in Ubuntu: Fix Released Bug description: Not sure if this is the right package, but in the privacy -> location settings, in 18.04 I had to have my application be approved by user to access location with Geoclue. Now it seems this is working without the location services "enabled"?? My application is repeater-START: https://sourceforge.net/projects /repeater-start/ Steps to see issue: 1) install Repeater-START and click the locate me button circle to the left. It goes to your rough location on map. 2) Go to settings, privacy, location, note that location is turned off!? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Aug 8 19:38:12 2020 InstallationDate: Installed on 2017-07-29 (1106 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to focal on 2020-06-22 (47 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1890924/+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 1915175] Re: wifi network stops working and shows a green wifi icon
** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => Gustavo Wills (gus-wb77) -- 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/1915175 Title: wifi network stops working and shows a green wifi icon Status in network-manager package in Ubuntu: New Bug description: I recently started using ubuntu 20.04, I connected it to my 2.4ghz Wi-Fi, at first the wifi worked fine, but suddenly the wifi stopped connecting, and after a few seconds it said "unable to activate network". I checked the "additional drivers tab" and it showed my wifi adapter, but it said "this device is using an alternate driver". right now I'm using my 5ghz Wi-Fi network, but sometimes it happens that it stops working, usually after suspend. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 12:09:28 2021 InstallationDate: Installed on 2021-02-08 (0 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) IpRoute: default via 192.168.1.254 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.8 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2021-02-08T22:50:26.196692 nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 Betancur 5G cda009c8-c845-4366-8436-8e9c44da2cbf /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 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/1915175/+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 1915322] [NEW] Xorg freeze
Public bug reported: Hey guys! First up, I've been using ubuntu on and off since I was about twelve, and I love this os.Thank you guys for the hard work! Second, I've been having an unfortunate bug on my laptop for quite some time now. I'm using an acer aspire e5-575g-55nw and every time my laptop goes into suspend, I can't get back to any kind of GUI after waking it up, instead going to a black screen with a single blinking white - symbol in the top left corner. i've tried just about every fix I could find on the internet, without being able to find any way back to my login screen or desktop. Note that this does not happen when my laptop goes to sleep on it's own after a set ammount of time, only when i put it into suspend or close the lid. I hope I included enough information, please let me know if you need any other information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 15:15:18 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094] Subsystem: Acer Incorporated [ALI] Acer Aspire E5-575G [1025:1094] InstallationDate: Installed on 2021-02-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57f2 Realtek Semiconductor Corp. HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=f1010786-e2a1-44b4-a3b8-6a48523960df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.release: 1.47 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.47 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.47 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.50 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.47:bd09/06/2018:br1.47:efr2.50:svnAcer:pnAspireE5-575G:pvrV1.47:rvnAcer:rnIronman_SK:rvrV1.47:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.sku: Aspire E5-575G_115F_1.47 dmi.product.version: V1.47 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 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.9-2ubuntu1.2~20.04.1 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+git20200226-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/1915322 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Hey guys! First up, I've been using ubuntu on and off si
[Desktop-packages] [Bug 1816674] Re: Update-mime-database is getting very slow during apps installation
Could you give some details on how you workarounded the startup issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1816674 Title: Update-mime-database is getting very slow during apps installation Status in shared-mime-info package in Ubuntu: Confirmed Bug description: The installation of some apps has become very slow due to the update- mime-database command that takes up a lot of time. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: shared-mime-info 1.10-1 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 19 22:37:53 2019 InstallationDate: Installed on 2019-01-16 (34 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: shared-mime-info UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1816674/+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 1915306] Re: Universal Access "Large Text" setting not retained on reboot
** Package changed: ubuntu => xorg (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/1915306 Title: Universal Access "Large Text" setting not retained on reboot Status in xorg package in Ubuntu: New Bug description: I am using the Universal Access "Large Text" setting. Upon reboot, the setting appears to be enabled, based on GUI switch appearance, but the font is very small (not sure of scaling factor, but appears to be < 1.00 - I will check this and report back next time I reboot). I have to turn the "Large Text" setting off, which actually makes the text larger, then turn it back on again, which makes it larger still (the size that I need). This does not happen on a log off; only on a reboot. If I simply log out and back in, the setting remains as it should (scaling factor of 1.25). I am aware that there is already a bug report for this problem, but it is marked as resolved last October. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-7642.47~1612288990~20.04~b8113e7~dev-generic 5.8.18 Uname: Linux 5.8.0-7642-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 460.39 Thu Jan 21 21:54:06 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Feb 10 12:37:59 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:50d3] NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:50d3] MachineType: System76 Oryx Pro ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-7642-generic root=UUID=bbcec58e-9495-49a4-9c29-34c6a65e3edf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2021 dmi.bios.release: 4.13 dmi.bios.vendor: coreboot dmi.bios.version: 2021-01-19_d6d37c0 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp6 dmi.chassis.type: 9 dmi.chassis.vendor: System76 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr2021-01-19_d6d37c0:bd01/19/2021:br4.13:efr0.0:svnSystem76:pnOryxPro:pvroryp6:rvnSystem76:rnOryxPro:rvroryp6:cvnSystem76:ct9:cvr: dmi.product.name: Oryx Pro dmi.product.version: oryp6 dmi.sys.vendor: System76 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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+git20200226-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/1915306/+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 1915306] [NEW] Universal Access "Large Text" setting not retained on reboot
You have been subscribed to a public bug: I am using the Universal Access "Large Text" setting. Upon reboot, the setting appears to be enabled, based on GUI switch appearance, but the font is very small (not sure of scaling factor, but appears to be < 1.00 - I will check this and report back next time I reboot). I have to turn the "Large Text" setting off, which actually makes the text larger, then turn it back on again, which makes it larger still (the size that I need). This does not happen on a log off; only on a reboot. If I simply log out and back in, the setting remains as it should (scaling factor of 1.25). I am aware that there is already a bug report for this problem, but it is marked as resolved last October. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-7642.47~1612288990~20.04~b8113e7~dev-generic 5.8.18 Uname: Linux 5.8.0-7642-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 460.39 Thu Jan 21 21:54:06 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Feb 10 12:37:59 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:50d3] NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:50d3] MachineType: System76 Oryx Pro ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-7642-generic root=UUID=bbcec58e-9495-49a4-9c29-34c6a65e3edf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2021 dmi.bios.release: 4.13 dmi.bios.vendor: coreboot dmi.bios.version: 2021-01-19_d6d37c0 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp6 dmi.chassis.type: 9 dmi.chassis.vendor: System76 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr2021-01-19_d6d37c0:bd01/19/2021:br4.13:efr0.0:svnSystem76:pnOryxPro:pvroryp6:rvnSystem76:rnOryxPro:rvroryp6:cvnSystem76:ct9:cvr: dmi.product.name: Oryx Pro dmi.product.version: oryp6 dmi.sys.vendor: System76 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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+git20200226-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 fonts third-party-packages ubuntu -- Universal Access "Large Text" setting not retained on reboot https://bugs.launchpad.net/bugs/1915306 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- 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 1915316] [NEW] Impossible-to-disable background auto-update randomly causes loss of data
Public bug reported: Firefox from Ubuntu 20.04 repository. Version after update is: 85.0.1+build1-0ubuntu0.20.04.1 I am fairly certain that before this update, I was on the latest version available. Problem description: Whenever an update is automatically installed in the background, a restart is required. The auto-updates occur in background at seemingly random times, and are, AFAIK impossible to disable (workaround seems to be to install Firefox from different source). The user always learns about the update only after it has happened already, and it is impossible to open new tabs. Before the restart, strange behavior often occurs, such as inexplicable tab crashes, pages not loading and staying blank, or new tabs being blank or crashing instead of showing the restart prompt. Sometimes, the restart prompt only appears after minutes of fighting with the previously described problems. This is alarming and frustrating on its own, but in the following cases this leads to loss of data (I have experienced all of them more than once): -When any content is open in private window, that the user wishes to continue working on. (Because private windows don't get restored after restart) -When a download is running which is impossible to resume, is from a one-time-download link, or when download is running in a private window. -When user is working on any work that requires opening a new window to finish, but progress will be lost when browser is closed. -When a browser with any unfinished work just crashes randomly, most often after following a link or submitting a form. Steps to reproduce: 1) Install the older version of Firefox from the Ubuntu 20.04 repository (it is likely that this hasn't been fixed in current one either). 2) Start to do any work filling forms, and requiring long downloads and opning new tabs, open few tabs in private window. 3) Wait for it to automatically install an update in background. 4) Wait until restart is prompted or stuff breaks randomly. 5) Restart 6) Your download is failed now, your unsubmitted forms are empty and your private windows are lost. Things that need to be fixed (in order from most severe): -Automatic installation of an update should never happen unprompted, while the user is working, and without their knowledge (unless this no longer leads to loss of data). With things like they are now, the absolute minimum is for the updates to happen at start-up, before the user is allowed to do any work. -User should be allowed to refuse an automatic update if it happens in a way that can lead to loss of data. User should be able to disable automatic updates. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1915316 Title: Impossible-to-disable background auto-update randomly causes loss of data Status in firefox package in Ubuntu: New Bug description: Firefox from Ubuntu 20.04 repository. Version after update is: 85.0.1+build1-0ubuntu0.20.04.1 I am fairly certain that before this update, I was on the latest version available. Problem description: Whenever an update is automatically installed in the background, a restart is required. The auto-updates occur in background at seemingly random times, and are, AFAIK impossible to disable (workaround seems to be to install Firefox from different source). The user always learns about the update only after it has happened already, and it is impossible to open new tabs. Before the restart, strange behavior often occurs, such as inexplicable tab crashes, pages not loading and staying blank, or new tabs being blank or crashing instead of showing the restart prompt. Sometimes, the restart prompt only appears after minutes of fighting with the previously described problems. This is alarming and frustrating on its own, but in the following cases this leads to loss of data (I have experienced all of them more than once): -When any content is open in private window, that the user wishes to continue working on. (Because private windows don't get restored after restart) -When a download is running which is impossible to resume, is from a one-time-download link, or when download is running in a private window. -When user is working on any work that requires opening a new window to finish, but progress will be lost when browser is closed. -When a browser with any unfinished work just crashes randomly, most often after following a link or submitting a form. Steps to reproduce: 1) Install the older version of Firefox from the Ubuntu 20.04 repository (it is likely that this hasn't been fixed in current one either). 2) Start to do any work filling forms, and requiring long downloads and opning new tabs, open few tabs in private window. 3) Wait for it to automatically install
[Desktop-packages] [Bug 1915315] [NEW] Add elementary Files to AppArmor profiles
Public bug reported: Currently there some exceptions in the apparmor profiles for common file browsers, but this list does not include elementary Files: ``` # 'Show Containing Folder' (LP: #1022962) /usr/bin/nautilus Cx -> sanitized_helper, # Gnome /usr/bin/pcmanfm Cx -> sanitized_helper, # LXDE /usr/bin/krusader Cx -> sanitized_helper, # KDE /usr/bin/thunar Cx -> sanitized_helper, # XFCE ``` We're currently patching this in: ``` /usr/bin/io.elementary.files Cx -> sanitized_helper, # Pantheon ``` Would be great if it was included upstream! :) ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1915315 Title: Add elementary Files to AppArmor profiles Status in evince package in Ubuntu: New Bug description: Currently there some exceptions in the apparmor profiles for common file browsers, but this list does not include elementary Files: ``` # 'Show Containing Folder' (LP: #1022962) /usr/bin/nautilus Cx -> sanitized_helper, # Gnome /usr/bin/pcmanfm Cx -> sanitized_helper, # LXDE /usr/bin/krusader Cx -> sanitized_helper, # KDE /usr/bin/thunar Cx -> sanitized_helper, # XFCE ``` We're currently patching this in: ``` /usr/bin/io.elementary.files Cx -> sanitized_helper, # Pantheon ``` Would be great if it was included upstream! :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915315/+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 195982] Re: Shift key (and caps lock) stop working when using VMWare
Ok, so I went back and re-read some of the most recent comments here - especially #226 and #229. This is what works for me: $ alias vmware="xmodmap -e 'remove control = Caps_Lock ' && /usr/lib/vmware/bin/vmplayer" If I start vmware with this alias, the keyboard on the host does not get corrupted when the mouse leaves the window. Well, sorta. I've used this for a few days and it was working until just now as i type this message. So this fix is not perfect. But this 2 step fix seems to get around the issue: $ setxkbmap $ alias vmware="xmodmap -e 'remove control = Caps_Lock ' To me this really looks more like a vmware bug. I plan on filing an issue there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/195982 Title: Shift key (and caps lock) stop working when using VMWare Status in Linux: Invalid Status in linux package in Ubuntu: Won't Fix Status in xkeyboard-config package in Ubuntu: Invalid Status in Gentoo Linux: New Bug description: [Problem] VMWare's keyboard mapping is imperfect, sometimes resulting in certain keys stopping functionality when running under VMWare, requiring the user to setup their configuration settings manually in VMWare. For a detailed explanation see the following article: http://www.vmware.com/support/ws55/doc/ws_devices_keymap_linux_longer.html [Original Report] After a day or so of running the shift key mysteriously stops working as does the cap lock. In other words I cannot enter shifted characters of any kind. The keyboard is connected to a KVM and all other systems respond to it properly. In additional any VMWare sessions I have open respond correctly. So I have the condition where all non-vmware applications in Ubuntu Hardy (all updates applied as of 2008-02-26 at 12:43 UTC) fail to recognize the shift key BUT applications within an active (a paused/restarted session also works) VMWare sessions running DO recognize the key. When this condition occurs ALL applications (except those within a VMWare session) are also unstable and will usually crash within a few keystrokes.If I continue to operate in this mode. I cannot pinpoint what, if any, application triggers this. It has always happened while working within terminal/browser/vmware sessions and NOT when opening a new application. It could be related to the KVM switch, but none of my other systems (2 Mandriva, 1 Windows) are affected by this. This bug has been present on my system for a number of days across daily updates and reboots (if the update requested it) and I think since I installed Hardy Alpha 1. A work around: log off and back on. A reboot/restart does not appear to be needed. Error logs show some unusual activity. --- MARK ... ... kernel ... rtc lost 7 interrupts ... --- MARK --- Plus some segfaults indicating which application crashed as I tried to type into it (mouse works fine). System: HP dv9743cl (which otherwise works lovely) Ubuntu: Hardy 8.04 (from lsb-release) TEST CASE: 1. Click inside the VM and 2. Hold any of the Ctrl, Alt and/or shift keys while releasing the keyboard/mouse to the host OS (which you obviously do when you press Crtl-Alt to revert back to windowed mode, as the cursor is then released from the VM). WORKAROUND: After this happens to recover your keyboard execute 'setxkbmap' in a terminal To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/195982/+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 1915198] Re: "Dummy output" instead of the audio device ALC268
Hello Daniel, Packages named 'timidity' or 'pipewire' are not installed. File packages.txt in attachment. Regards, Dmitriy. ** Attachment added: "packages.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1915198/+attachment/5462367/+files/packages.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1915198 Title: "Dummy output" instead of the audio device ALC268 Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello Support, "Dummy output" in Sound settings. nothing works. $ aplay -l List of PLAYBACK Hardware Devices $ alsa-info.sh link to http://alsa- project.org/db/?f=834b3fe04e2e1c74c7f2a84b6fb698e6e49db8fa. # dmidecode -t system # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 2.4 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: TOSHIBA Product Name: Satellite U300 Version: PSU30E-01M01DRU # lspci |grep Audio 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 03) Subsystem: Toshiba Corporation 82801H (ICH8 Family) HD Audio Controller [1179:ff50] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel Physical device is ALC268. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.10 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 22:37:35 2021 InstallationDate: Installed on 2021-02-09 (0 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2009 dmi.bios.vendor: TOSHIBA dmi.bios.version: V5.10 dmi.board.name: Satellite U300 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV5.10:bd01/15/2009:svnTOSHIBA:pnSatelliteU300:pvrPSU30E-01M01DRU:rvnTOSHIBA:rnSatelliteU300:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U300 dmi.product.version: PSU30E-01M01DRU dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1915198/+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 1877879] Re: segfault in iris_dri.so
*** This bug is a duplicate of bug 1876219 *** https://bugs.launchpad.net/bugs/1876219 I have a similar hardware configuration (Intel(R) Core(TM) i5-8265U and Mesa Intel(R) UHD Graphics 620) and see this issue as well. I don't believe it's the same bug as bug 1876219. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1877879 Title: segfault in iris_dri.so Status in mesa package in Ubuntu: Confirmed Bug description: As of Ubuntu 20.04, on intel graphics with intel driver (not modesetting), I got segfault whenever anything tries to use GL. This happens unless I export MESA_LOADER_DRIVER_OVERRIDE=i965. One says that it does not happen with modesetting driver. (gdb) run Starting program: /usr/bin/glxgears [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x717cf700 (LWP 97070)] [New Thread 0x7fffebfff700 (LWP 97071)] [New Thread 0x70fce700 (LWP 97072)] [New Thread 0x7fffeb7fe700 (LWP 97073)] Thread 1 "glxgears" received signal SIGSEGV, Segmentation fault. 0x76a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (gdb) where #0 0x76a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #1 0x76c42de4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #2 0x76a59e5d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #3 0x76a5aa95 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x76099774 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x711e in ?? () #6 0x6c88 in ?? () #7 0x77ace0b3 in __libc_start_main (main=0x6410, argc=1, argv=0x7fffe698, init=, fini=, rtld_fini=, stack_end=0x7fffe688) at ../csu/libc-start.c:308 #8 0x6f0a in ?? () (gdb) I believe, this is a bug in mesa tracked here: https://gitlab.freedesktop.org/mesa/mesa/issues/1358 packages versions: libgl1-mesa-dri:amd64 20.0.4-2ubuntu1 amd64 xserver-xorg-video-intel 2:2.99.917+git20200226-1 amd64 xserver-xorg-core 2:1.20.8-2ubuntu2 amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1877879/+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 1907142] Re: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink
Hi, one more crash for me, you'll find iris_dri error at 14:15:47 time ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1907142/+attachment/5462347/+files/prevboot.txt -- 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/1907142 Title: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink Status in evdi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Since my upgrade from 18.04 to 20.04 I experience rather frequent crashes of the X server. Nothing specific of applications running, presumably at videos (VLC, Youtube in a browser tab ...). If not yet attached, I'll attach the *.old log with the most recent trace. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Dec 7 22:15:34 2020 DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5300 [17aa:222b] InstallationDate: Installed on 2019-02-16 (660 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20CHS10P02 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago) dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N17ETB2W (2.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CHS10P02 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 11 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone: dmi.product.family: ThinkPad Helix 2nd dmi.product.name: 20CHS10P02 dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd dmi.product.version: ThinkPad Helix 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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+git20200226-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/evdi/+bug/1907142/+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 1915247] Re: Display viewbox zoomed in when using fractional scaling
*** This bug is a duplicate of bug 1870736 *** https://bugs.launchpad.net/bugs/1870736 ** This bug has been marked a duplicate of bug 1870736 [nvidia] Screen scaling 125% gives 200% -- 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/1915247 Title: Display viewbox zoomed in when using fractional scaling Status in xorg package in Ubuntu: New Bug description: With fractional scaling set at 125%--175% display is zoomed in at top left of every display. Display size is 3072 x 1728 however only the top left 1920 x 1080 is visible. Taking a screenshot includes the area outside of the display. I am not sure if this is a xorg, xrandr, or mutter bug. Expected: The entire screen to be visible when using fractional scaling. Kernel: 5.8.0-43-generic Release: Ubuntu 20.04.2 LTS XOrg: 1:7.7+19ubuntu14 GPU: amd(3.20191218.1ubuntu1), nvidia(460) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 11:45:53 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.32.03, 5.8.0-40-generic, x86_64: installed nvidia, 460.32.03, 5.8.0-43-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-40-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bb1] Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Picasso [1043:1bb1] InstallationDate: Installed on 2020-07-08 (216 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X570DD_M570DD ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-43-generic root=UUID=9f488e6e-27a3-42de-945f-85568219ed82 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X570DD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X570DD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX570DD.302:bd10/24/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_M570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X570DD_M570DD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 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.9-2ubuntu1.2~20.04.1 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+git20200226-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/1915247/+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 1915181] Re: cups crashes with SIGABRT every other printing attempt
Looks like it may be a duplicate of https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1846334. The backtrace I got from the core dump locates the errorneous free() call in ippDelete as well. Plus it's also a samsung printer. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1915181 Title: cups crashes with SIGABRT every other printing attempt Status in cups package in Ubuntu: New Bug description: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. Cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-01-28 (12 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) KernLog: Lpstat: device for Samsung_C48x_Series_SEC842519933D78_: implicitclass://Samsung_C48x_Series_SEC842519933D78_/ MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root resume_offset=6731776 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root resume_offset=6731776 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 RebootRequiredPkgs: linux-image-5.8.0-43-generic linux-base Tags: groovy Uname: Linux 5.8.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX434DA_UM433DA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX434DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX434DA_UM433DA.302:bd09/05/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX434DA_UM433DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+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 1915283] [NEW] [ThinkPad X1 Yoga G5, Realtek ALC285] TRS-Microphone recognized as Headphone
Public bug reported: Expected If I plug in a 3-contact TRS microphone, PulseAudio should show it as a plugged in microphone. Actual -- Pulse Audio still reports the "Headphones Stereo Microphone" as unplugged. The meter shows no signal. The main output changes its Port form "Speaker" to "Headphones (plugged in)" and the speakers are muted. Additional Information -- Microphone Model: König CMP-MIC8 (https://www.amazon.de/Konig-CMP-MIC8 -Mikrofon-mit-Kabel-Schwarz/dp/B000WGW96K?language=en_GB). It features a 3-contact, TRS plug. It is the same plug as for a standard stereo headphone. The microphone worked on another Windows PC and a Zoom H5 pocket recorder. It requires plug-in power. A 4-contact TRRS headset works as expected (speakers are muted, headphone output and microphone input are enabled, microphone meter shows input signal). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Feb 10 15:52:50 2021 InstallationDate: Installed on 2020-09-12 (151 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: None of the above Title: [20UCS03S00, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: Upgraded to groovy on 2021-02-10 (0 days ago) dmi.bios.date: 10/15/2020 dmi.bios.release: 1.14 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET24W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UCS03S00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN2WET24W(1.14):bd10/15/2020:br1.14:efr1.8:svnLENOVO:pn20UCS03S00:pvrThinkPadX1YogaGen5:rvnLENOVO:rn20UCS03S00:rvrNotDefined:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga Gen 5 dmi.product.name: 20UCS03S00 dmi.product.sku: LENOVO_MT_20UC_BU_Think_FM_ThinkPad X1 Yoga Gen 5 dmi.product.version: ThinkPad X1 Yoga Gen 5 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy kernel-sound -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1915283 Title: [ThinkPad X1 Yoga G5, Realtek ALC285] TRS-Microphone recognized as Headphone Status in alsa-driver package in Ubuntu: New Bug description: Expected If I plug in a 3-contact TRS microphone, PulseAudio should show it as a plugged in microphone. Actual -- Pulse Audio still reports the "Headphones Stereo Microphone" as unplugged. The meter shows no signal. The main output changes its Port form "Speaker" to "Headphones (plugged in)" and the speakers are muted. Additional Information -- Microphone Model: König CMP-MIC8 (https://www.amazon.de/Konig-CMP-MIC8 -Mikrofon-mit-Kabel-Schwarz/dp/B000WGW96K?language=en_GB). It features a 3-contact, TRS plug. It is the same plug as for a standard stereo headphone. The microphone worked on another Windows PC and a Zoom H5 pocket recorder. It requires plug-in power. A 4-contact TRRS headset works as expected (speakers are muted, headphone output and microphone input are enabled, microphone meter shows input signal). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Feb 10 15:52:50 2021 InstallationDate: Installed on 2020-09-12 (151 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: None of the above Title: [20UCS03S00, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: Upgraded to groovy on 2021-02-10 (0 days ago) dmi.bios.date: 10/15/2020 dmi.bios.release: 1.14 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET24W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UCS03S00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.cha
[Desktop-packages] [Bug 1914918] Re: The snap being updated in the background causes both old and new tabs to die to SIGTRAP
I'm seeing similar problem. The only solution I found is to close and
reopen browser.
snap2.48.3+20.10
snapd 2.48.3+20.10
series 16
ubuntu 20.10
kernel 5.8.0-41-generic
dasm@dell:~/git/canonical$ sudo snap get system
experimental.refresh-app-awareness
error: snap "core" has no "experimental" configuration option
dasm@dell:~/git/canonical$ sudo snap get core experimental.refresh-app-awareness
error: snap "core" has no "experimental" configuration option
dasm@dell:~/git/canonical$ sudo snap set system
experimental.refresh-app-awareness=true
dasm@dell:~/git/canonical$ sudo snap get system
Key Value
experimental {...}
refresh {...}
seed {...}
I'll report back if I'm still seeing issues with this behavior.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1914918
Title:
The snap being updated in the background causes both old and new tabs
to die to SIGTRAP
Status in chromium-browser package in Ubuntu:
Confirmed
Status in snapd package in Ubuntu:
Confirmed
Bug description:
The last few background updates of chromium have made some old tabs
suddenly crash with SIGTRAP and it also makes it impossible to open
new tabs, those die instantly with a SIGTRAP as well.
This is incredibly destructive to whatever might be the dying tabs'
unsaved state and there's no warning about it. Yet again a snap-
related change rolled out to users with absolutely amateur-tier
testing.
Ubuntu: 20.04.2
Snap: 2.48+20.04
Chromium: 88.0.4324.150
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1914918/+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 1914918] Re: The snap being updated in the background causes both old and new tabs to die to SIGTRAP
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: snapd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1914918 Title: The snap being updated in the background causes both old and new tabs to die to SIGTRAP Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: The last few background updates of chromium have made some old tabs suddenly crash with SIGTRAP and it also makes it impossible to open new tabs, those die instantly with a SIGTRAP as well. This is incredibly destructive to whatever might be the dying tabs' unsaved state and there's no warning about it. Yet again a snap- related change rolled out to users with absolutely amateur-tier testing. Ubuntu: 20.04.2 Snap: 2.48+20.04 Chromium: 88.0.4324.150 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1914918/+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 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
What happen with this bug that is not assigned and is fixed in upstream but no in distro? Michel Dänzer Michel Dänzer @daenzer · 3 weeks ago Maintainer It is, but nobody's making upstream releases, which is probably why users are still hitting this issue, even though the fix landed upstream 9 months ago. https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/issues/10#note_769719 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths Status in Linux: Unknown Status in libxcb package in Ubuntu: Confirmed Status in xfwm4 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly. With dual monitors and the external monitor placed left or right the display has a blocked staircase effect shown in the attached photograph, and seems related to https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/issues/10 More detailed investigation suggests it only happens when the X coordinate of the two monitors is different. The symptom looks like an off-by-one error because it appears as if the display is divided into, say, 10 rows and 15 columns but the first row has 16 'columns' worth of blocks on it and so wraps to the beginning of the 2nd row, and so on. On the laptop without package upgrades being applied this didn't happen. So I upgraded it (314 packages) and restarted and it too sees the same problem. I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but that didn't solve it. I now suspect libxcb but so far haven't been able to prove it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) MachineType: LENOVO 20NECTO1WW Package: xserver-xorg-video-amdgpu 19.1.0-1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET32W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NECTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E495 dmi.product.name: 20NECTO1WW dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495 dmi.product.version: ThinkPad E495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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+git20200226-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/linux/+bug/1873895/+subscriptions -- Mailing li
[Desktop-packages] [Bug 1915247] Re: Display viewbox zoomed in when using fractional scaling
** Attachment added: "Upgrade which caused this issue" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1915247/+attachment/5462240/+files/apt.history.log -- 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/1915247 Title: Display viewbox zoomed in when using fractional scaling Status in xorg package in Ubuntu: New Bug description: With fractional scaling set at 125%--175% display is zoomed in at top left of every display. Display size is 3072 x 1728 however only the top left 1920 x 1080 is visible. Taking a screenshot includes the area outside of the display. I am not sure if this is a xorg, xrandr, or mutter bug. Expected: The entire screen to be visible when using fractional scaling. Kernel: 5.8.0-43-generic Release: Ubuntu 20.04.2 LTS XOrg: 1:7.7+19ubuntu14 GPU: amd(3.20191218.1ubuntu1), nvidia(460) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 11:45:53 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.32.03, 5.8.0-40-generic, x86_64: installed nvidia, 460.32.03, 5.8.0-43-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-40-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bb1] Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Picasso [1043:1bb1] InstallationDate: Installed on 2020-07-08 (216 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X570DD_M570DD ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-43-generic root=UUID=9f488e6e-27a3-42de-945f-85568219ed82 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X570DD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X570DD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX570DD.302:bd10/24/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_M570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X570DD_M570DD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 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.9-2ubuntu1.2~20.04.1 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+git20200226-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/1915247/+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 1915270] [NEW] After upgrade to 20.10 multiple apps dropped
Public bug reported: VirtualBox does not show up anywhere in Gnome-shell as an application. Wine doesn't show up anywhere in Gnome-shell as an application. Those are two of the more egregious examples. I can run them from the command line. The .desktop entries clearly exist in /usr/share/applications. I've verified and reverified all the .desktop entries and checked them against the Gnome documentation to verify everything is correct. Yet it simply refuses to load these apps. A dump of the VirtualBox entry dumped below (even editted it to use absolute path).Similar problems with Wine which was installed via Ubuntu software so no reason for it to be rejected/disappear. Ubuntu: 20.10 VirtualBox: Installed: 6.1.16-dfsg-6~ubuntu1.20.10.1 (from ubuntu Groovy repository) Wine: Candidate: 5.0-3ubuntu1 (also from Groovy repository) ...so...all are pointing to the current repository (Groovy). I'm at a loss here even how to fix it since I can't really "upgrade" or "fix" the .desktop entry since nothing is wrong with those. They are just "ghosts" as far as Gnome-shell is concerned. [Desktop Entry] Name=VirtualBox GenericName=PC virtualization solution Type=Application Exec=/usr/bin/VirtualBox TryExec=VirtualBox Keywords=virtualization; Keywords[de]=Virtualisierung; Keywords[ru]=виртуализация; MimeType=application/x-virtualbox-vbox;application/x-virtualbox-vbox-extpack;application/x-virtualbox-ovf;application/x-virtualbox-ova; Icon=virtualbox Categories=Emulator;System;Utility; Actions=Manager; Comment=Run several virtual systems on a single host computer Comment[de]=Mehrere virtuelle Maschinen auf einem einzigen Rechner ausführen Comment[it]=Esegui più macchine virtuali su un singolo computer Comment[ko]=가상 머신 Comment[pl]=Uruchamianie wielu systemów wirtualnych na jednym komputerze gospodarza Comment[ru]=Запуск нескольких виртуальных машин на одном компьютере Comment[sv]=Kör flera virtuella system på en enda värddator [Desktop Action Manager] Exec=VirtualBox Name=Open Oracle VM Manager Name[de]=Oracle VM Manager öffnen ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 08:01:17 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-07 (552 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: linux-image-5.8.0-43-generic linux-base RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2021-02-07 (3 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1915270 Title: After upgrade to 20.10 multiple apps dropped Status in gnome-shell package in Ubuntu: New Bug description: VirtualBox does not show up anywhere in Gnome-shell as an application. Wine doesn't show up anywhere in Gnome-shell as an application. Those are two of the more egregious examples. I can run them from the command line. The .desktop entries clearly exist in /usr/share/applications. I've verified and reverified all the .desktop entries and checked them against the Gnome documentation to verify everything is correct. Yet it simply refuses to load these apps. A dump of the VirtualBox entry dumped below (even editted it to use absolute path).Similar problems with Wine which was installed via Ubuntu software so no reason for it to be rejected/disappear. Ubuntu: 20.10 VirtualBox: Installed: 6.1.16-dfsg-6~ubuntu1.20.10.1 (from ubuntu Groovy repository) Wine: Candidate: 5.0-3ubuntu1 (also from Groovy repository) ...so...all are pointing to the current repository (Groovy). I'm at a loss here even how to fix it since I can't really "upgrade" or "fix" the .desktop entry since nothing is wrong with those. They are just "ghosts" as far as Gnome-shell is concerned. [Desktop Entry] Name=VirtualBox GenericName=PC virtualization solution Type=Application Exec=/usr/bin/VirtualBox TryExec=VirtualBox Keywords=virtualization; Keywords[de]=Virtualisierung; Keywords[ru]=виртуализация; MimeType=application/x-virtualbox-vbox;application/x-virtualbox-vbox-extpack;application/x-virtualbox-ovf;application/x-virtualbox-ova; Icon=virtualbox Categories=Emulator;System;Utility; Actions=Manager; Comment=Run several virtual systems on a single host computer Comment[de]=Mehrere virtuelle Maschinen auf einem einzigen Rechner ausf
[Desktop-packages] [Bug 1915256] Re: Background and Lockscreen
Thanks for your report! You are indeed right, you can't change the background separately any longer in Ubuntu 20.10. The upstream docs has been corrected to reflect this: https://gitlab.gnome.org/GNOME/gnome-user-docs/-/commit/296ff6db and that correction will be included in Ubuntu 21.04. ** Package changed: ubuntu-docs (Ubuntu) => gnome-user-docs (Ubuntu) ** Changed in: gnome-user-docs (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-user-docs (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1915256 Title: Background and Lockscreen Status in gnome-user-docs package in Ubuntu: Fix Committed Bug description: i have read the official Documentation from Ubuntu, and in there guide find i the option to change the lock screen backgrounds https://help.ubuntu.com/stable/ubuntu-help/look-background.html.en i use Ubuntu 20.10 version, then i dont found the options in background panel for change the lock screen background. There is not include or installed. I dont found a install package thats works or found when i use the terminal install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1915256/+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 1915256] [NEW] Background and Lockscreen
You have been subscribed to a public bug: i have read the official Documentation from Ubuntu, and in there guide find i the option to change the lock screen backgrounds https://help.ubuntu.com/stable/ubuntu-help/look-background.html.en i use Ubuntu 20.10 version, then i dont found the options in background panel for change the lock screen background. There is not include or installed. I dont found a install package thats works or found when i use the terminal install. ** Affects: gnome-user-docs (Ubuntu) Importance: Medium Status: Fix Committed -- Background and Lockscreen https://bugs.launchpad.net/bugs/1915256 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. -- 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 1915247] Re: Display viewbox zoomed in when using fractional scaling
** Package changed: ubuntu => xorg (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/1915247 Title: Display viewbox zoomed in when using fractional scaling Status in xorg package in Ubuntu: New Bug description: With fractional scaling set at 125%--175% display is zoomed in at top left of every display. Display size is 3072 x 1728 however only the top left 1920 x 1080 is visible. Taking a screenshot includes the area outside of the display. I am not sure if this is a xorg, xrandr, or mutter bug. Expected: The entire screen to be visible when using fractional scaling. Kernel: 5.8.0-43-generic Release: Ubuntu 20.04.2 LTS XOrg: 1:7.7+19ubuntu14 GPU: amd(3.20191218.1ubuntu1), nvidia(460) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 11:45:53 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.32.03, 5.8.0-40-generic, x86_64: installed nvidia, 460.32.03, 5.8.0-43-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-40-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bb1] Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Picasso [1043:1bb1] InstallationDate: Installed on 2020-07-08 (216 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X570DD_M570DD ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-43-generic root=UUID=9f488e6e-27a3-42de-945f-85568219ed82 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X570DD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X570DD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX570DD.302:bd10/24/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_M570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X570DD_M570DD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 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.9-2ubuntu1.2~20.04.1 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+git20200226-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/1915247/+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 1816674] Re: Update-mime-database is getting very slow during apps installation
Same problem with 20.04. I believe this is related to this issue: https://bbs.archlinux.org/viewtopic.php?id=255817 . FTR, as `apt-daily.service` is running on startup, this was also increasing my boot-time significantly (although I found a workaround for this particular problem). Just to emphasize that this is a serious bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1816674 Title: Update-mime-database is getting very slow during apps installation Status in shared-mime-info package in Ubuntu: Confirmed Bug description: The installation of some apps has become very slow due to the update- mime-database command that takes up a lot of time. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: shared-mime-info 1.10-1 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 19 22:37:53 2019 InstallationDate: Installed on 2019-01-16 (34 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: shared-mime-info UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1816674/+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 1915247] [NEW] Display viewbox zoomed in when using fractional scaling
You have been subscribed to a public bug: With fractional scaling set at 125%--175% display is zoomed in at top left of every display. Display size is 3072 x 1728 however only the top left 1920 x 1080 is visible. Taking a screenshot includes the area outside of the display. I am not sure if this is a xorg, xrandr, or mutter bug. Expected: The entire screen to be visible when using fractional scaling. Kernel: 5.8.0-43-generic Release: Ubuntu 20.04.2 LTS XOrg: 1:7.7+19ubuntu14 GPU: amd(3.20191218.1ubuntu1), nvidia(460) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 11:45:53 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.32.03, 5.8.0-40-generic, x86_64: installed nvidia, 460.32.03, 5.8.0-43-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-40-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bb1] Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Picasso [1043:1bb1] InstallationDate: Installed on 2020-07-08 (216 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X570DD_M570DD ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-43-generic root=UUID=9f488e6e-27a3-42de-945f-85568219ed82 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X570DD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X570DD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX570DD.302:bd10/24/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_M570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X570DD_M570DD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 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.9-2ubuntu1.2~20.04.1 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+git20200226-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 ubuntu -- Display viewbox zoomed in when using fractional scaling https://bugs.launchpad.net/bugs/1915247 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- 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
Re: [Desktop-packages] [Bug 1881941] Re: Ubuntu dock behaves crazy when hidden at the bottom of the screen
It could be the auto-hide feature something to do with some pixel counting. __ Respectfully yours, Vitalie Procopan +373 69989548 Skype: spiker1988 ср, 10 февр. 2021 г. в 13:17, Vitalie Procopan : > You would have to dock the tab in the bottom and set auto-hide. Then try > to use it while using folders/windows, in some cases it buggs out, pretty > frequently to notice. > __ > Respectfully yours, > Vitalie Procopan > +373 69989548 > Skype: spiker1988 > > > вт, 9 февр. 2021 г. в 22:25, Russell Weber <1881...@bugs.launchpad.net>: > >> I'm a capable software developer. However, I am at a loss on where to >> start debugging this issue. Does anyone have any idea of where to >> start? >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1881941 >> >> Title: >> Ubuntu dock behaves crazy when hidden at the bottom of the screen >> >> Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: >> Confirmed >> >> Bug description: >> I had put the dock on the bottom of the screen and also set to hide >> automatically. >> The dock works fine as expected but there are sometimes (actually like >> 90% of the time) that it behaves weird when I try to access it with the >> mouse pointer, the dock starts to bounce quickly without stopping and then >> it's kind of hard to press the icons on it (when I'm lucky I can click the >> icon), other times I had to move away the pointer from the bottom and then >> move it back to access the dock. >> I made a video of it although it's very short but you can see for a >> brief of time how the dock starts to bounce. >> I haven't installed new packages or applications that change the >> behaviour of the dock in any way. >> >> >> tavoge@e6430s:~$ lsb_release -rd >> Description: Ubuntu 20.04 LTS >> Release: 20.04 >> >> >> tavoge@e6430s:~$ apt-cache policy xorg >> xorg: >> Instalados: 1:7.7+19ubuntu14 >> Candidato: 1:7.7+19ubuntu14 >> Tabla de versión: >>*** 1:7.7+19ubuntu14 500 >> 500 http://mx.archive.ubuntu.com/ubuntu focal/main amd64 >> Packages >> 100 /var/lib/dpkg/status >> >> ProblemType: Bug >> DistroRelease: Ubuntu 20.04 >> Package: xorg 1:7.7+19ubuntu14 >> ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 >> Uname: Linux 5.4.0-33-generic x86_64 >> ApportVersion: 2.20.11-0ubuntu27.2 >> Architecture: amd64 >> BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' >> CasperMD5CheckResult: skip >> CompositorRunning: None >> CurrentDesktop: ubuntu:GNOME >> Date: Wed Jun 3 11:40:48 2020 >> DistUpgraded: Fresh install >> DistroCodename: focal >> DistroVariant: ubuntu >> DkmsStatus: virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed >> ExtraDebuggingInterest: Yes >> GraphicsCard: >>Intel Corporation 3rd Gen Core processor Graphics Controller >> [8086:0166] (rev 09) (prog-if 00 [VGA controller]) >> Subsystem: Dell 3rd Gen Core processor Graphics Controller >> [1028:057d] >> InstallationDate: Installed on 2020-05-29 (5 days ago) >> InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 >> (20200423) >> MachineType: Dell Inc. Latitude E6430s >> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic >> root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 >> SourcePackage: xorg >> Symptom: display >> UpgradeStatus: No upgrade log present (probably fresh install) >> dmi.bios.date: 11/30/2018 >> dmi.bios.vendor: Dell Inc. >> dmi.bios.version: A21 >> dmi.board.name: 0XHTPW >> dmi.board.vendor: Dell Inc. >> dmi.board.version: A00 >> dmi.chassis.type: 9 >> dmi.chassis.vendor: Dell Inc. >> dmi.modalias: >> dmi:bvnDellInc.:bvrA21:bd11/30/2018:svnDellInc.:pnLatitudeE6430s:pvr01:rvnDellInc.:rn0XHTPW:rvrA00:cvnDellInc.:ct9:cvr: >> dmi.product.name: Latitude E6430s >> dmi.product.sku: Latitude E6430s >> dmi.product.version: 01 >> dmi.sys.vendor: Dell Inc. >> version.compiz: compiz N/A >> version.libdrm2: libdrm2 2.4.101-2 >> version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 >> version.libgl1-mesa-glx: libgl1-mesa-glx N/A >> version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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+git20200226-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/gnome-shell-extension-ubuntu-dock/+bug/1881941/+subscriptions >> > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1881941 Title: Ubuntu dock behaves crazy when h
Re: [Desktop-packages] [Bug 1881941] Re: Ubuntu dock behaves crazy when hidden at the bottom of the screen
You would have to dock the tab in the bottom and set auto-hide. Then try to use it while using folders/windows, in some cases it buggs out, pretty frequently to notice. __ Respectfully yours, Vitalie Procopan +373 69989548 Skype: spiker1988 вт, 9 февр. 2021 г. в 22:25, Russell Weber <1881...@bugs.launchpad.net>: > I'm a capable software developer. However, I am at a loss on where to > start debugging this issue. Does anyone have any idea of where to > start? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1881941 > > Title: > Ubuntu dock behaves crazy when hidden at the bottom of the screen > > Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: > Confirmed > > Bug description: > I had put the dock on the bottom of the screen and also set to hide > automatically. > The dock works fine as expected but there are sometimes (actually like > 90% of the time) that it behaves weird when I try to access it with the > mouse pointer, the dock starts to bounce quickly without stopping and then > it's kind of hard to press the icons on it (when I'm lucky I can click the > icon), other times I had to move away the pointer from the bottom and then > move it back to access the dock. > I made a video of it although it's very short but you can see for a > brief of time how the dock starts to bounce. > I haven't installed new packages or applications that change the > behaviour of the dock in any way. > > > tavoge@e6430s:~$ lsb_release -rd > Description: Ubuntu 20.04 LTS > Release: 20.04 > > > tavoge@e6430s:~$ apt-cache policy xorg > xorg: > Instalados: 1:7.7+19ubuntu14 > Candidato: 1:7.7+19ubuntu14 > Tabla de versión: >*** 1:7.7+19ubuntu14 500 > 500 http://mx.archive.ubuntu.com/ubuntu focal/main amd64 > Packages > 100 /var/lib/dpkg/status > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 > Uname: Linux 5.4.0-33-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.2 > Architecture: amd64 > BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Wed Jun 3 11:40:48 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > DkmsStatus: virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation 3rd Gen Core processor Graphics Controller > [8086:0166] (rev 09) (prog-if 00 [VGA controller]) > Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:057d] > InstallationDate: Installed on 2020-05-29 (5 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > MachineType: Dell Inc. Latitude E6430s > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic > root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/30/2018 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A21 > dmi.board.name: 0XHTPW > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 9 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvrA21:bd11/30/2018:svnDellInc.:pnLatitudeE6430s:pvr01:rvnDellInc.:rn0XHTPW:rvrA00:cvnDellInc.:ct9:cvr: > dmi.product.name: Latitude E6430s > dmi.product.sku: Latitude E6430s > dmi.product.version: 01 > dmi.sys.vendor: Dell Inc. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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+git20200226-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/gnome-shell-extension-ubuntu-dock/+bug/1881941/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1881941 Title: Ubuntu dock behaves crazy when hidden at the bottom of the screen Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I had put the dock on the bottom of the screen and also set to hide automatically. The dock works fine as expected but there are sometimes (actually like 90% of the time) that it behaves weird when I try to access
[Desktop-packages] [Bug 1887707] Re: Disabling fractional scaling after selecting another integer scaling may unselect user choice
** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1887707 Title: Disabling fractional scaling after selecting another integer scaling may unselect user choice Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Released Bug description: [ Impact ] If selecting another integer scaling after disabling fractional scaling [ Test case ] When running Ubuntu session under X11, in gnome-control-center, display panel: - Ensure 100% scaling is selected and applied - Enable fractional scaling - Select 200% scaling (or bigger integer scaling) - Green "Apply" button should be visible and clickable - Deactivate fractional scaling - Green "Apply" button stays and fractional scaling isn't disabled until applied Repeat with inverted scaling orders (applying 200% and then selecting 100%) Currently, once another integer value is selected, we just deselect the user choice and restore the previous one, deactivating the fractional scaling promtply. [ Regression potential ] - Displays are wrongly disposed and configured when fractional scaling is enabled - Configurations are not applicable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1887707/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Problem remains, my environment: - Kernel: 5.4.0-65-generic - OS: Ubuntu 20.04.2 LTS - Machine: Dell Precision 5550 - Headset: Jabra Evolve 75 Couple of users facing the same issue here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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
Re: [Desktop-packages] [Bug 1915161] Re: deja dup won't restore a folder where name contains apostrophe and space
That's great news and many thanks for your help and quick response. I've taken the easy way out and installed the snap version. All working correctly now. Many thanks On Wed, 10 Feb 2021 at 02:20, Michael Terry <1915...@bugs.launchpad.net> wrote: > Sorry you were hit by this issue! But good news is that a fix is > available. It was caused by an interaction between Deja Dup and > duplicity when a single quote was followed by a space. > > This was fixed upstream in duplicity 0.8.17 (and worked around in deja- > dup 42.5). Both those fixes are in Ubuntu 21.04 already, so I'll mark > this fixed in development Ubuntu. > > If folks want to backport a fix to Ubuntu 20.10, this patch to duplicity > should be all that's needed: > > https://gitlab.com/duplicity/duplicity/-/commit/14f18f9112ce98ad6b5ba5cf58a8f6927dab > > Meanwhile, you can workaround this in Ubuntu 20.10 by either directly > using the duplicity commandline to restore the file or switching to the > snap version of deja-dup which has the latest fixes. > > Run "man duplicity" to see how to use its commandline (it's a bit > complicated, but can be managed). > Or "snap install deja-dup --classic" to install the latest Deja Dup. > > Sorry for the trouble. > > ** Changed in: deja-dup (Ubuntu) >Status: Confirmed => Fix Released > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1915161 > > Title: > deja dup won't restore a folder where name contains apostrophe and > space > > Status in deja-dup package in Ubuntu: > Fix Released > > Bug description: > I have a folder entitled Mothers' Union. I use Deja-Dup to backup it > up (along with many other folders) on Ubuntu 20.10. When I open Deja- > Dup and click on the restore option and pick a back-up date it shows > all the folders in the backup except this one (Mothers' Union). If I > remove the apostrophe from the folder name it backs it up fine and can > be restored. Other folders where the apostrophe is in the name but not > followed by a space (e.g. John's Documents) also backup and restore > correctly. Not sure if this is a bug but it's unfortunate that with > this combination of an apostrophe and a space in the name I can't > restore the folder. > > 1. Ubuntu 20.10 > 2. deja-dup 42.2-1ubuntu1 > 3. I expected to be able to restore the folder with the apostrophe and > space in the name (Mothers' Union) > 4. The folder is not available in any of the restore points. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1915161/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1915161 Title: deja dup won't restore a folder where name contains apostrophe and space Status in deja-dup package in Ubuntu: Fix Released Bug description: I have a folder entitled Mothers' Union. I use Deja-Dup to backup it up (along with many other folders) on Ubuntu 20.10. When I open Deja- Dup and click on the restore option and pick a back-up date it shows all the folders in the backup except this one (Mothers' Union). If I remove the apostrophe from the folder name it backs it up fine and can be restored. Other folders where the apostrophe is in the name but not followed by a space (e.g. John's Documents) also backup and restore correctly. Not sure if this is a bug but it's unfortunate that with this combination of an apostrophe and a space in the name I can't restore the folder. 1. Ubuntu 20.10 2. deja-dup 42.2-1ubuntu1 3. I expected to be able to restore the folder with the apostrophe and space in the name (Mothers' Union) 4. The folder is not available in any of the restore points. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1915161/+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 1915174] Re: Fingerprint enrollment error stops user to be able to enroll again
The patches are included in the recent hirsute upload https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/1:3.38.3-1ubuntu2 ** Changed in: gnome-control-center (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1915174 Title: Fingerprint enrollment error stops user to be able to enroll again Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: In Progress Bug description: [ Impact ] An error during enrollment prevents other enrollment to happen. [ Test case ] With a real fingerprint device (harder) or with fprintd mock runner: https://gitlab.freedesktop.org/3v1n0/fprintd-mock-runner/ 1. Enroll a finger 2. Cause the enrollment to fail (unplug the device if possible or enroll a previously enrolled finger if the device supports it) 3. Go back 4. Select a finger again and be able to enroll it 5. Enrollment should start [ Regression potential ] Dialog won't allow user to show the fingers enrolled or enroll at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1915174/+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 1915091] Re: Nautilus shows LXD storage pool in sidebar
thanks, so gio lists the loop mount, it's weird though that it's not listed in the 'mount' output you added before... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1915091 Title: Nautilus shows LXD storage pool in sidebar Status in nautilus package in Ubuntu: Incomplete Bug description: I recently set up LXD 4.11 on Ubuntu 20.04 with a file-backed btrfs storage pool called "default". Now Nautilus shows a "default" device in the sidebar despite the loop device not being intended for users to directly interact with. System: Ubuntu 20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1915091/+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 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
Moved to upstream bug https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/3701 which also has a fix proposed in https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1662 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3701 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3701 ** Changed in: gnome-shell Remote watch: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3026 => gitlab.gnome.org/GNOME/gnome-shell/-/issues #3701 ** Changed in: gnome-shell (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Bug description: In disco, when policykit prompted me for a password in order for update-manager to dispatch instructions to aptdaemon to perform package updates, the password dialog remained on the screen after I clicked 'authenticate'. The window is not clickable, it appears not to even be a window - mouse presses are received by the window underneath. The exception is that the 'cancel' button is active and receives mouse events - but clicking it does nothing. This may be a gnome-shell issue rather than policykit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: policykit-1 0.105-25 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 13:14:33 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: policykit-1 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1824874/+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 1910220] Re: Characters from dead keys shown in plan view in password field on login screen
** This bug is no longer a duplicate of bug 1772791 Lock/login screen displays password in clear text occasionally -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1910220 Title: Characters from dead keys shown in plan view in password field on login screen Status in gnome-shell package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 2) apt-cache policy gdm3 gdm3: Installed: 3.38.1-2ubuntu1.1 Candidate: 3.38.1-2ubuntu1.1 Version table: *** 3.38.1-2ubuntu1.1 500 500 http://se.archive.ubuntu.com/ubuntu groovy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.38.1-2ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 3) I expect all characters, even those from dead keys, to be hidden the same ways as other characters 4) When using dead keys to add accents to letters on the password prompt on the login screen, before the letter the dead key is intended for is typed, the special characters from the dead keys are displayed in plain sight, instead of being obscured by dots as other letters and characters are. Screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gdm3 3.38.1-2ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 5 12:51:19 2021 InstallationDate: Installed on 2018-11-26 (770 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gdm3 UpgradeStatus: Upgraded to groovy on 2020-11-01 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910220/+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 1910220] Re: Characters from dead keys shown in plan view in password field on login screen
*** This bug is a duplicate of bug 1772791 *** https://bugs.launchpad.net/bugs/1772791 ** Attachment added: "Partially hidden password" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910220/+attachment/5462183/+files/Ubuntu%2064-bit-2021-02-10-09-16-02.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1910220 Title: Characters from dead keys shown in plan view in password field on login screen Status in gnome-shell package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 2) apt-cache policy gdm3 gdm3: Installed: 3.38.1-2ubuntu1.1 Candidate: 3.38.1-2ubuntu1.1 Version table: *** 3.38.1-2ubuntu1.1 500 500 http://se.archive.ubuntu.com/ubuntu groovy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.38.1-2ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 3) I expect all characters, even those from dead keys, to be hidden the same ways as other characters 4) When using dead keys to add accents to letters on the password prompt on the login screen, before the letter the dead key is intended for is typed, the special characters from the dead keys are displayed in plain sight, instead of being obscured by dots as other letters and characters are. Screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gdm3 3.38.1-2ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 5 12:51:19 2021 InstallationDate: Installed on 2018-11-26 (770 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gdm3 UpgradeStatus: Upgraded to groovy on 2020-11-01 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910220/+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 1910220] Re: Characters from dead keys shown in plan view in password field on login screen
*** This bug is a duplicate of bug 1772791 *** https://bugs.launchpad.net/bugs/1772791 If this bug was a duplicate of or related to https://bugs.launchpad.net/bugs/1772791 I would expect the whole password to be visible. Please see newly uploaded screenshot. Only the accent from the dead key is visible, while the other three letters in the password are obscured. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1910220 Title: Characters from dead keys shown in plan view in password field on login screen Status in gnome-shell package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 2) apt-cache policy gdm3 gdm3: Installed: 3.38.1-2ubuntu1.1 Candidate: 3.38.1-2ubuntu1.1 Version table: *** 3.38.1-2ubuntu1.1 500 500 http://se.archive.ubuntu.com/ubuntu groovy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.38.1-2ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 3) I expect all characters, even those from dead keys, to be hidden the same ways as other characters 4) When using dead keys to add accents to letters on the password prompt on the login screen, before the letter the dead key is intended for is typed, the special characters from the dead keys are displayed in plain sight, instead of being obscured by dots as other letters and characters are. Screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gdm3 3.38.1-2ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 5 12:51:19 2021 InstallationDate: Installed on 2018-11-26 (770 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gdm3 UpgradeStatus: Upgraded to groovy on 2020-11-01 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910220/+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 1910220] Re: Characters from dead keys shown in plan view in password field on login screen
*** This bug is a duplicate of bug 1772791 *** https://bugs.launchpad.net/bugs/1772791 I don't believe this is a duplicate of https://bugs.launchpad.net/bugs/1772791 as this is specifically about using dead keys when typing in a password. At no time does the entire password display in clear text. Only the accents of dead keys are shown, but as the intended letter is then pressed, the completed letter with accent is hidden. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1910220 Title: Characters from dead keys shown in plan view in password field on login screen Status in gnome-shell package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 2) apt-cache policy gdm3 gdm3: Installed: 3.38.1-2ubuntu1.1 Candidate: 3.38.1-2ubuntu1.1 Version table: *** 3.38.1-2ubuntu1.1 500 500 http://se.archive.ubuntu.com/ubuntu groovy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.38.1-2ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 3) I expect all characters, even those from dead keys, to be hidden the same ways as other characters 4) When using dead keys to add accents to letters on the password prompt on the login screen, before the letter the dead key is intended for is typed, the special characters from the dead keys are displayed in plain sight, instead of being obscured by dots as other letters and characters are. Screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gdm3 3.38.1-2ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 5 12:51:19 2021 InstallationDate: Installed on 2018-11-26 (770 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gdm3 UpgradeStatus: Upgraded to groovy on 2020-11-01 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910220/+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
