[Desktop-packages] [Bug 1890772] Re: Some external 4K monitor is not working properly
** Description changed: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 - MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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 -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably
[Desktop-packages] [Bug 1890772] Re: Some external 4K monitor is not working properly
reply #20 yes, Daniel. Originally, the display would like to use 10 bpc. but it is failed with some dongle. However, we found that, it uses 8bit color depth on Windows. We wonder if Windows has done some magic for enhancing compatibilty. Maybe we can also discuss if we can have some implementation like export the bpc selection to gnome-control-center for user. Otherwise, user can just found that it works on Windows but failed on Ubuntu. -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/oem-priority/+bug/1890772/+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 1890772] Re: Some external 4K monitor is not working properly
Note also that if you did have a machine that required: xrandr --output DP-3 --set "max bpc" 8 on a 4K 60Hz display then that may indicate a bandwidth problem. Maybe a limitation of the cable. Does a max bpc of 10 also work? What values don't work? -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/oem-priority/+bug/1890772/+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 1890772] Re: Some external 4K monitor is not working properly
There doesn't seem to be any external monitor connected to this machine, or any 'DP-3' connector. Please attach 'xrandr --verbose' info with a monitor connected showing the problem, or please open a new bug from the affected machine. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Changed in: oem-priority Status: New => Incomplete -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/oem-priority/+bug/1890772/+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 1890772] Re: Some external 4K monitor is not working properly
** Also affects: oem-priority Importance: Undecided Status: New -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/oem-priority/+bug/1890772/+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 1890772] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1890772/+attachment/5399488/+files/xdpyinfo.txt ** Description changed: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 + # 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028:09fc] -Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] + Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) + Subsystem: Dell Device [1028:09fc] + Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True - dmi.bios.date: 08/03/2020 - dmi.bios.vendor: Dell Inc. - dmi.bios.version: 0.6.0 - dmi.board.vendor: Dell Inc. - dmi.chassis.type: 10 - dmi.chassis.vendor: Dell Inc. - dmi.modalias: dmi:bvnDellInc.:bvr0.6.0:bd08/03/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: - dmi.product.family: Vostro - dmi.product.name: Vostro 5301 - dmi.product.sku: 09FC - 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.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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 -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia,
[Desktop-packages] [Bug 1890772] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1890772/+attachment/5399483/+files/ProcModules.txt -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/oem-priority/+bug/1890772/+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 1890772] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1890772/+attachment/5399487/+files/Xrandr.txt -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/oem-priority/+bug/1890772/+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 1890772] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1890772/+attachment/5399482/+files/ProcInterrupts.txt -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/oem-priority/+bug/1890772/+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 1890772] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1890772/+attachment/5399484/+files/UdevDb.txt -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/oem-priority/+bug/1890772/+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 1890772] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1890772/+attachment/5399486/+files/XorgLogOld.txt -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/oem-priority/+bug/1890772/+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 1890772] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1890772/+attachment/5399485/+files/XorgLog.txt -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/oem-priority/+bug/1890772/+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 1890772] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1890772/+attachment/5399481/+files/ProcEnviron.txt -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/oem-priority/+bug/1890772/+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 1890772] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1890772/+attachment/5399480/+files/ProcCpuinfoMinimal.txt -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/oem-priority/+bug/1890772/+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 1890772] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1890772/+attachment/5399479/+files/ProcCpuinfo.txt -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/oem-priority/+bug/1890772/+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 1890772] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1890772/+attachment/5399475/+files/Lspci-vt.txt -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/oem-priority/+bug/1890772/+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 1890772] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1890772/+attachment/5399478/+files/Lsusb-v.txt -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/oem-priority/+bug/1890772/+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 1890772] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1890772/+attachment/5399472/+files/Dependencies.txt -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/oem-priority/+bug/1890772/+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 1890772] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1890772/+attachment/5399476/+files/Lsusb.txt -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/oem-priority/+bug/1890772/+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 1890772] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1890772/+attachment/5399477/+files/Lsusb-t.txt -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/oem-priority/+bug/1890772/+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 1890772] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1890772/+attachment/5399474/+files/Lspci.txt -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/oem-priority/+bug/1890772/+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 1890772] Re: Some external 4K monitor is not working properly
apport information ** Tags added: apport-collected focal third-party-packages ubuntu ** Description changed: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` - Would like to open this bug to open discussion for enhancing user - experience. + Would like to open this bug to open discussion for enhancing user experience. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.4 + Architecture: amd64 + BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' + CasperMD5CheckResult: skip + CompositorRunning: None + CurrentDesktop: ubuntu:GNOME + 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+fossa-samwell-tgl+X42 + DistroCodename: focal + DistroRelease: Ubuntu 20.04 + DistroVariant: ubuntu + DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed + ExtraDebuggingInterest: Yes + GraphicsCard: + Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) +Subsystem: Dell Device [1028:09fc] +Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] + InstallationDate: Installed on 2020-08-07 (0 days ago) + InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 + MachineType: Dell Inc. Vostro 5301 + Package: xorg 1:7.7+19ubuntu14 [origin: unknown] + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 + Tags: third-party-packages focal ubuntu + Uname: Linux 5.6.0-1021-oem x86_64 + UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/03/2020 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 0.6.0 + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr0.6.0:bd08/03/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: + dmi.product.family: Vostro + dmi.product.name: Vostro 5301 + dmi.product.sku: 09FC + 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.8-0ubuntu1~20.04.1 + version.libgl1-mesa-glx: libgl1-mesa-glx N/A + version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 + 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 ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1890772/+attachment/5399471/+files/CurrentDmesg.txt -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce
[Desktop-packages] [Bug 1890772] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1890772/+attachment/5399473/+files/DpkgLog.txt -- 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/1890772 Title: Some external 4K monitor is not working properly Status in OEM Priority Project: New Status in xorg package in Ubuntu: New Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/oem-priority/+bug/1890772/+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 1890772] [NEW] Some external 4K monitor is not working properly
Public bug reported: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/03/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.6.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.6.0:bd08/03/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5301 dmi.product.sku: 09FC 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.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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: apport-collected focal third-party-packages 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/1890772 Title: Some external 4K monitor is not working properly Status in xorg package in Ubuntu: New Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME 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+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine:
[Desktop-packages] [Bug 334624] Re: Thunderbird doesn't synchronize IMAP until the program is closed
[Expired for thunderbird (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunderbird (Ubuntu) Status: Incomplete => Expired -- 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/334624 Title: Thunderbird doesn't synchronize IMAP until the program is closed Status in thunderbird package in Ubuntu: Expired Bug description: Binary package hint: thunderbird I'm using 64-bit Jaunty Kubuntu on two machines. I use an IMAP account because it's important to me that I have the same email on both machines. While I was using Intrepid, changes to my email happened immediately. For example, if I had both machines running with thunderbird open on both, if I deleted an email on one, it would be deleted on the other. Now, in order for the changes on one Thunderbird to propogate to the other I have to close Thunderbird. As soon as I do, all the changes I've made propogate to the other thunderbird and then on my webmail. The first thing I did was call my email support number, and they reset my account and that didn't fix it. They said no configuration changed, so it must be Thunderbird. Another example is if I have Thunderbird open and webmail open in Firefox, then I delete an email in Thunderbird, the email isn't deleted in webmail. Once I close Thunderbird, the changes I've made to my messages then appear in webmail. For whatever reason, Thunderbird does something when it closes to synchronize, instead of in real time. Steps to reproduce: 1. Open Thunderbird for an IMAP account 2. Send a test email to that account from a different account (such as webmail) 3. No change in Thunderbird 4. Close Thunderbird 5. Open Thunderbird again 6. The new email appears Expected behaviour: The new email should appear as soon as step #3 above Actual behaviour: The new email only appears at step #6 above, after closing and re-opening Thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/334624/+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 1560094] Re: Starting bluez service is denied
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1560094 Title: Starting bluez service is denied Status in bluez package in Ubuntu: Expired Bug description: If snappy core is updated in the background (on Raspberry Pi 2), and then bluez installed, starting the service is failing. Denials: [ 45.955490] audit: type=1400 audit(1458574955.667:11): apparmor="DENIED" operation="mknod" profile="bluez5_bluez_5.37-2-armhf" name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=834 comm="c0 [ 46.197608] audit: type=1326 audit(1458574955.907:12): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=831 comm="obexd" exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 sysc0 [ 46.275680] audit: type=1400 audit(1458574955.987:13): apparmor="DENIED" operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=829 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 [ 46.276483] audit: type=1326 audit(1458574955.987:14): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=829 comm="bluetoothd" exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000 [ 46.412021] audit: type=1326 audit(1458574956.123:15): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=839 comm="obexd" exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 sysc0 [ 46.504308] audit: type=1400 audit(1458574956.215:16): apparmor="DENIED" operation="mknod" profile="bluez5_bluez_5.37-2-armhf" name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=842 comm="c0 [ 46.520137] audit: type=1400 audit(1458574956.231:17): apparmor="DENIED" operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=841 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 [ 46.520800] audit: type=1326 audit(1458574956.231:18): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=841 comm="bluetoothd" exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000 [ 46.625293] audit: type=1326 audit(1458574956.335:19): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=844 comm="obexd" exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 sysc0 [ 46.721080] audit: type=1400 audit(1458574956.431:20): apparmor="DENIED" operation="mknod" profile="bluez5_bluez_5.37-2-armhf" name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=847 comm="c2 If trying to start bluetootctl: [ 582.205066] audit: type=1400 audit(1458575491.915:31): apparmor="DENIED" operation="connect" profile="bluez5_bluetoothctl_5.37-2-armhf" name="/run/dbus/system_bus_socket" pid=993 comm="bluetoothctl" re0 [bluetooth]# ubuntu@localhost:~$ snappy list NameDate Version Developer bluez5 2016-02-04 5.37-2-armhf canonical canonical-pi2 2016-02-02 3.0 canonical canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical ubuntu-core 2016-03-08 16.04.0-15.armhf canonical ubuntu@localhost:~$ ubuntu@localhost:~$ snappy info release: core/rolling architecture: armhf frameworks: bluez5.canonical apps: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1560094/+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 1864287] Re: pulseaudio still trying to reproduce audio to HDMI without the HDMI cable connected
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1864287 Title: pulseaudio still trying to reproduce audio to HDMI without the HDMI cable connected Status in pulseaudio package in Ubuntu: Expired Bug description: Yesterday I was using the HDMI cable to duplicate the monitor in the tv and play sound with the tv by selecting HDMI exit sound in ubuntu settings. With the pc turned off I removed the HDMI from the tv but ubuntu doesn't automatically set the exit sound to the default till in the settings there is only that option and till I selected it, ubuntu was still trying to reproduce the audio via HDMI... Also rebooting the system the problem persists. Also by reloading pulseaudio the problem persists. The only solution was installing a third-party program to switch correctly to the default audio exit... lsb_release -rd: Description: Ubuntu 18.04.3 LTS Release: 18.04 apt-cache policy pulseaudio: pulseaudio: Installato: 1:11.1-1ubuntu7.2 Candidato: 1:11.1-1ubuntu7.4 Tabella versione: 1:11.1-1ubuntu7.4 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 1:11.1-1ubuntu7.2 100 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1864287/+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 1870736] Re: [nvidia] Screen scaling 125% gives 200%
@marco-carrarini In post #77, you suggested a workaround by modifying xorg.conf. Then in post #81, @vanvugt suggested the same outcome could be achieved with `xrandr --fb` or `xrandr --scale-from`. Finally, you responded in #82 with "Yes, but expect some glitches in apps." I'm not clear if your response to "expect some glitches" was only for @vanvugt's xrandr suggestion, or if the two workarounds are equivalent and to "expect some glitches" with either method. Any clarification would be appreciated. Thanks! -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1890763] [NEW] I suspect Firefox cause journal problem, doing lags of keyboard and mouse input, or slow apps
Public bug reported: I have a new installation of Ubuntu 20.04 LTS. Two weeks ago I experienced several issues: -slow boot -disk failures (inodes corrupted, superblock invalid, read-only at start) -Firefox slower to respond at start, can't get the previous session -systemd-journald error trying to write on read-only filesystem -/tmpfs read-only -/var/log/journal with 1.6 GB -snap-store process with the highest memory use Yesterday I have to abandon the use of this Ubuntu 20.04, because the lack of trust Today, I trim the max size of journal files (100 MB), change resolution of display and avoid using Firefox (instead using Chromium); however, this report invoke Firefox; during 2 hours I been working as smooth and fine as always. Finally, I use Ubuntu in a diary basis; in this device I have versions 16.04, 18.04 and 20.04. Only 20.04 give this problems. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 79.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alejandro 2458 F pulseaudio /dev/snd/controlC0: alejandro 2458 F pulseaudio BuildID: 20200720193547 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 21:48:33 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:725 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-05-19 (79 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.254 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.64 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:725 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=79.0/20200720193547 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A4CN40WW (V 2.09) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5B3 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688SDK0J40688 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-75 dmi.modalias: dmi:bvnLENOVO:bvrA4CN40WW(V2.09):bd08/24/2015:svnLENOVO:pn80EC:pvrLenovoZ50-75:rvnLENOVO:rnLancer5B3:rvrSDK0J40688SDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoZ50-75: dmi.product.family: IDEAPAD dmi.product.name: 80EC dmi.product.sku: LENOVO_MT_80EC0_BU_idea_FM_Lenovo Z50-75 dmi.product.version: Lenovo Z50-75 dmi.sys.vendor: LENOVO ** Affects: firefox (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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/1890763 Title: I suspect Firefox cause journal problem, doing lags of keyboard and mouse input, or slow apps Status in firefox package in Ubuntu: New Bug description: I have a new installation of Ubuntu 20.04 LTS. Two weeks ago I experienced several issues: -slow boot -disk failures (inodes corrupted, superblock invalid, read-only at start) -Firefox slower to respond at start, can't get the previous session -systemd-journald error trying to write on read-only filesystem -/tmpfs read-only -/var/log/journal with 1.6 GB -snap-store process with the highest memory use Yesterday I have to abandon the use of this Ubuntu 20.04, because the lack of trust Today, I trim the max size of journal files (100 MB), change resolution of display and avoid using Firefox (instead using Chromium); however, this report invoke Firefox; during 2 hours I been working as smooth and fine as always. Finally, I use Ubuntu in a diary basis; in this device I have versions 16.04, 18.04 and 20.04. Only 20.04 give this problems. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 79.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu
[Desktop-packages] [Bug 1841774] Re: gnome-shell freezes and continuously logs "JS ERROR: TypeError: null has no properties" in _addWindowEffect from vfunc_show (both in closeDialog.js)
Since Ubuntu 19.10 (eoan) has reached end of life, this can be closed. Please see bug 1890613 for a more current discussion. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix -- 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/1841774 Title: gnome-shell freezes and continuously logs "JS ERROR: TypeError: null has no properties" in _addWindowEffect from vfunc_show (both in closeDialog.js) Status in gnome-shell package in Ubuntu: Won't Fix Bug description: I was closing the dialog of the "software and updates" tools (I was checking the repositories and ppa), but the entire desktop went into freeze, no mouse movement, at the click no action, I pressed the keys "ctrl + alt + f3 "and I went into a tty session, from there I recorded the logs via:" journalctl -f> log ", and I restarted. This is one part of the log, but it seems to repeat itself, I have attached a file with a longer log. -- Logs begin at Tue 2019-02-19 00:29:40 CET. -- ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no properties _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9 ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no properties _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 14:51:01 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (190 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841774/+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 1890613] Re: Gnome unresponsive JS ERROR: TypeError: windowActor is null
It appears this was reported upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3006 but that's been marked as a duplicate of: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2467 which is also mentioned in bug 1841774. So maybe they are related. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3006 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3006 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2467 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2467 ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3006 Importance: Unknown Status: Unknown -- 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/1890613 Title: Gnome unresponsive JS ERROR: TypeError: windowActor is null Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: gnome-shell becomes unresponsive after about 1 day. I'm able to interact with the window that had focus when the problem appears (in this case it was Chrome), but I'm unable to select or otherwise interact with other windows, the shell, dock, or indicators. The logs are spammed with gnome-shell[2916]: JS ERROR: TypeError: windowActor is null#012_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28#012vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14 This looks similar to but different enough from https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841774 I was using the i915 driver when this happened if that makes any difference ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 09:08:32 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-12 (54 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1890613/+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 1890650] Re: Activities button, Alt-F1, and super not working after upgrade to 20.04
Please run these commands: dpkg -l > packages.txt gsettings list-recursively org.gnome.shell > settings.txt and then attach the resulting text files here. Please also try selecting 'Ubuntu on Wayland' from the login screen and tell us if that has the same issue. ** 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/1890650 Title: Activities button, Alt-F1, and super not working after upgrade to 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: If I hit the Activities button, all open applications are hidden. There is no way to get the applications to display again. The application I select is started, and shows up on the vertical bar in the left with an orange dot by it. What magic is needed to bring the applications back? They are still there. I see them when I go to log out. Logging out is the only option for restoring Gnome. The same problem happens if I hit Alt-F1 or Super. Shouldn't these toggle? The only way to get a screen shot it with my phone. Sorry for the quality. You can see on the left that I started gimp.Up to 19.10, when I used "Activities", it would launch the app and then return to my running applications. Originally asked here: https://askubuntu.com/questions/1264414/activities-button-alt-f1-and- super-not-working-after-upgrade-to-20-04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.23 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 13:29:43 2020 InstallationDate: Installed on 2018-10-14 (661 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-08-03 (2 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890650/+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 1890593] Re: Xorg freeze
This sounds kind of like bug 1872159 or bug 1871641. Can you please try editing /etc/default/grub and remove 'splash' then: sudo update-grub and reboot. ** Tags added: hybrid nvidia ** Summary changed: - Xorg freeze + [nvidia] Boot freeze - can't get to login screen without unplugging HDMI first ** Package changed: xorg (Ubuntu) => plymouth (Ubuntu) ** Changed in: plymouth (Ubuntu) Status: New => Incomplete ** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- 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/1890593 Title: [nvidia] Boot freeze - can't get to login screen without unplugging HDMI first Status in gdm3 package in Ubuntu: New Status in plymouth package in Ubuntu: Incomplete Bug description: Just installed ubuntu 20.04 and I am stuck on ubuntu with a spining logo. If I go to other tty and unplug the HDMI screens I can get to the login screen, Otherwise I cant. I did checked the md5sum of the iso before installing and its was correct. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 14:29:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T570 [17aa:2248] Subsystem: Lenovo GM108GLM [Quadro M520 Mobile] [17aa:2248] InstallationDate: Installed on 2020-08-05 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20HCS0660M ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=be1cbba6-c044-4d36-a6f4-fe872353a538 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1VET49W (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HCS0660M dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1VET49W(1.39):bd05/08/2019:svnLENOVO:pn20HCS0660M:pvrThinkPadP51s:rvnLENOVO:rn20HCS0660M:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad THINKPAD P51S dmi.product.name: 20HCS0660M dmi.product.sku: LENOVO_MT_20HC_BU_Think_FM_ThinkPad THINKPAD P51S dmi.product.version: ThinkPad P51s 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/gdm3/+bug/1890593/+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 1890436] Re: VGA signal is ghosted and stretched (Intel® HD Graphics 2500)
Yes I do understand why you might call that corruption. Actually you didn't need to enable DRM debugging. It looks like there are a few errors coming from the Intel kernel graphics driver 'i915'. Those might be separate to the FIFO underrun errors, which other people also report in bug 1550779. The problems reported in your kernel log seem to relate to atomic mode setting, which is what the 'modeset' Xorg driver uses. Wayland sessions don't use that interface to Intel graphics so it's likely that logging into 'Ubuntu on Wayland' will avoid some (or all) of the problem. -- 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/1890436 Title: VGA signal is ghosted and stretched (Intel® HD Graphics 2500) Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello, last week I was digging in the BIOS of my PC at work since I tried to see if there is a way to update the dbx for secure boot. Since there was no option to perform this task, I modified some settings. In detail, I disabled CSM in BIOS and that's when hell broke loose! To get an idea about the hardware, the Lenovo machine isn't running the latest BIOS as its updater is broken and won't update it within win or its ISO image. It uses the previous version released by its manufacturer. The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled the DP monitor is lit first and then the VGA one prior OS loading. When CSM is disabled it goes the other way around. The VGA monitor is lit and the DP one opens up during OS load. With CSM disabled the VGA monitor is the primary one and it is corrupted as you can see on the pictures I have attached. Interestingly printing screens within Ubuntu does not capture the corruption problem I am getting as you can see on the pictures I have also attached. Neither X log contains anything useful. The issue is repeatable on every boot. As I have seen on other bug reports, I have enabled DRM debug, captured the dmesg using a huge buffer to get it and have uploaded it as well. I hope that it will help you track this issue down and fix it soon. Since I will be away some days for vacation, I will have physical access to it till this Friday and will get back to work at the 24th of August. In the mean time, I hope that someone will pinpoint the root cause of it and prepare a patch. Since this machine is running w10 2004, it should be noted that in win I do not get any corruption at all either in CSM mode or UEFI mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CasperVersion: 1.445 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 11:30:51 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 3209C54 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT9BAUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3209C54 dmi.product.sku: LENOVO_MT_3209 dmi.product.version: ThinkCentre M92p 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
[Desktop-packages] [Bug 1890411] Re: [bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
Not that I can think of...
I forgot to mention: i965_dri isn't used in later Ubuntu releases. It's
been replaced by a new driver called 'iris_dri'.
You will probably find that Ubuntu 20.04.1 works better:
https://releases.ubuntu.com/20.04/
--
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/1890411
Title:
[bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
Status in mesa package in Ubuntu:
New
Status in xorg-server package in Ubuntu:
New
Bug description:
When ubuntu starts up, gdm3 does not start due to a crash in the the
xserver:
[ 1271.342] (II) SELinux: Disabled on system
[ 1271.346] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 1271.346] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[ 1271.346] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 1271.346] (II) AIGLX: enabled GLX_SGI_swap_control
[ 1271.346] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 1271.346] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 1271.346] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[ 1271.346] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[ 1271.346] (II) AIGLX: Loaded and initialized i965
[ 1271.346] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 1271.348] (II) modeset(0): Damage tracking initialized
[ 1271.348] (II) modeset(0): Setting screen physical size to 508 x 317
[ 1271.352] (EE)
[ 1271.352] (EE) Backtrace:
[ 1271.352] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5649b579bacd]
[ 1271.352] (EE) 1: /usr/lib/xorg/Xorg (0x5649b55e3000+0x1bc869)
[0x5649b579f869]
[ 1271.352] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f5c7d0a5000+0x128a0) [0x7f5c7d0b78a0]
[ 1271.352] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x8e8652) [0x7f5c784e2652]
[ 1271.352] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x8e877f) [0x7f5c784e277f]
[ 1271.352] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x122916) [0x7f5c77d1c916]
[ 1271.352] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x1189bc) [0x7f5c77d129bc]
[ 1271.352] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x109c1b) [0x7f5c77d03c1b]
[ 1271.352] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x279558) [0x7f5c77e73558]
[ 1271.352] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x2796e3) [0x7f5c77e736e3]
[ 1271.352] (EE) 10: /usr/lib/xorg/modules/libglamoregl.so
(0x7f5c79937000+0x1a1ab) [0x7f5c799511ab]
[ 1271.352] (EE) 11: /usr/lib/xorg/Xorg (0x5649b55e3000+0x13ed03)
[0x5649b5721d03]
[ 1271.352] (EE) 12: /usr/lib/xorg/Xorg (miPaintWindow+0x22f)
[0x5649b577fd1f]
[ 1271.352] (EE) 13: /usr/lib/xorg/Xorg (miWindowExposures+0x112)
[0x5649b577fa62]
[ 1271.352] (EE) 14: /usr/lib/xorg/Xorg (0x5649b55e3000+0xa9c41)
[0x5649b568cc41]
[ 1271.352] (EE) 15: /usr/lib/xorg/Xorg (MapWindow+0x114) [0x5649b5665d04]
[ 1271.352] (EE) 16: /usr/lib/xorg/Xorg (0x5649b55e3000+0x56e79)
[0x5649b5639e79]
[ 1271.352] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xe7) [0x7f5c7ccd5b97]
[ 1271.352] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x5649b5623b8a]
[ 1271.352] (EE)
[ 1271.352] (EE) Segmentation fault at address 0x4
[ 1271.352] (EE)
Fatal server error:
[ 1271.352] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 1271.352] (EE)
[ 1271.352] (EE)
As i965_dri.so is part of the libgl-mesa-dri package I downgraded this
specific package from version 20.0.8-0ubuntu1~18.04.1 back to
19.2.8-0ubuntu0~18.04.3.
This solves the problem. So I suspect that the problem is in this
specific package.
My machine is (uname):
4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64
x86_64 GNU/Linux
(lspci)
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller
(rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen
Core Processor Integrated Graphics Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series
Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High
Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI
Express Root Port #1 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220
[Desktop-packages] [Bug 1791788] Re: Layout switch unwanted combination Rshift+Lshift
** Tags added: bionic -- 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/1791788 Title: Layout switch unwanted combination Rshift+Lshift Status in gnome-shell package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.1 LTS Linux version 4.15.0-33-generic WHAT I EXPECT TO HAPPEN: "R-Shift + L-Shift" hotkey combination doesn't change keyboard layout when not configured to do so. WHAT HAPPENS INSTEAD: "R-Shift + L-Shift" changes keyboard layout even when not configured to do so. -- My machine is set up to use "L-Alt + L-Shift" combination for switching keyboard layout between English and Russian. The command I use to configure this combination: gsettings set org.gnome.desktop.input-sources xkb-options "['grp:lalt_lshift_toggle']" With this setting Ubuntu also reacts to "R-Shift + L-Shift" combination and switches the layout as well. This is very irritating, since when typing the C code I often need to use macros like MY_MACRO_WITH_UNDERSCORE, where I naturally hit both shift keys when typing a capital letter after an underscore. The issue appears only when the R-Shift is hit before the L-Shift and not the other way around. The issue doesn't appear when I disable my switch combination with: gsettings set org.gnome.desktop.input-sources xkb-options "['']" I also disabled default Super+Space and Super+Shift+Space combinations, although that doesn't affect the issue. I didn't set any other keyboard combinations for switching layouts. The issue appears both in the terminal and in GUI applications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791788/+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 1844453]
Oh, indeed, looks like lots of fun... :-)
I'll chase this with the team and try to get the paperwork done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1844453
Title:
[upstream] Access to the Google remote account does not work
Status in LibreOffice:
Confirmed
Status in libreoffice package in Ubuntu:
Confirmed
Bug description:
I have a Google account with 2FA login, from LibreOffice I try to add the
remote account, but it doesn't work, it asks me for a 6-digit PIN.
Investigating to see if it was just my problem, I discovered that this is a
long-standing LibreOffice bug (1) and seems unresolved.
The last report confirms this: "2019-07-04 04:44:41 UTC
This feature doesn't work with my Google account _w/o_
2FA.
Bug hasn't be resolved for about 3 years and "very soon"
we may celebrate 5 years anniversary. %-("
1) https://bugs.documentfoundation.org/show_bug.cgi?id=101630
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 17 23:00:10 2019
InstallationDate: Installed on 2019-02-18 (210 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1844453/+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 1889477] Re: xdg-open on Kubuntu 20.04 reports 'Could not connect to localhost: Connection refused' if localhost service not already up
Hi Alex, My scripts run xdg-open http://localhost:something before starting the service as a time saver to setup my workspace. Did you already have the service running when you started it up? It works fine when the service is already up, but it throws this new error when it is not. In the past it would just open a new tab in the browser and move on. In Kubuntu 20.04 I have to click the button in the dialog for it to exit. Since it does not happen in Manjaro with either KDE 18 or 19.2 in my experience I assuming it is a Kubuntu/Ubuntu issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1889477 Title: xdg-open on Kubuntu 20.04 reports 'Could not connect to localhost: Connection refused' if localhost service not already up Status in xdg-utils package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 (Kubuntu 20.04 Fresh Install) 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center xdg-utils: Installed: 1.1.3-2ubuntu1 Candidate: 1.1.3-2ubuntu1 3) What you expected to happen xdg-open "http://localhost:1313; to open the default browser at http://localhost:1313 4) What happened instead A gui dialog titled 'Error -- KIO Client' pops up with the message 'Could not connect to host localhost: Connection refused.' 5) More Info I use xdg-open "http://localhost:someport; in my bash scripts before it actually starts the service as a time saver. On older Ubuntu and other distros it would open the default browser (Firefox) with a page not found. I press reload once the service is setup and Firefox loads the page. On Kubuntu 20.04 xdg-open gets blocked if the port is not already opened. Example command: xdg-open "http://localhost:1313; This did work on Kubuntu and Ubuntu 18.04 and Ubuntu 19.10. Currently works on Manjaro KDE with latest stable update. Worked on Fedora 31 KDE (can not remember if I tested 32). Current Manjaro package reported as: xdg-utils 1.1.3+19+g9816ebb-1 Ubuntu 20.04 not tested. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xdg-utils 1.1.3-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Jul 29 13:53:07 2020 InstallationDate: Installed on 2020-05-28 (62 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: xdg-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1889477/+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 1861453] Re: The chromium-browser snap package fails to run
*** This bug is a duplicate of bug 1776800 *** https://bugs.launchpad.net/bugs/1776800 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (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/1861453 Title: The chromium-browser snap package fails to run Status in chromium-browser package in Ubuntu: Confirmed Bug description: Xubuntu 19.10 chromium-browser 79.0.3945.79-0ubuntu0.19.10.2 Transitional package - chromium-browser -> chromium snap Chromium worked fine before the upgrade to 19.10. There has been a transition to snap packaging. My first attempt to launch the browser results in: % chromium-browser 2020/01/30 11:12:47.911841 cmd_run.go:529: WARNING: XAUTHORITY environment value is not a clean path: "/x/u/jeff/.Xauthority" cannot perform operation: mount --rbind /home /tmp/snap.rootfs_MDsNgD//home: Permission denied % dmesg | grep DENIED (just showing one typical message) [827635.380132] audit: type=1400 audit(1580411567.940:87): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="/snap/core/8268/usr/lib/snapd/snap-confine" name="/tmp/snap.rootfs_MDsNgD/home/" pid=2968 comm="snap-confine" srcname="/x/u/" flags="rw, rbind" The home directory is: /u/jeff The home directory is actually resides on an external drive mounted on /x with /u being a symlink to /x/u % cd / % ls -l home u lrwxrwxrwx 1 root root 1 Jan 2 2015 home -> u lrwxrwxrwx 1 root root 3 Nov 30 2017 u -> x/u %echo $XAUTHORITY /u/jeff/.Xauthority Applications should not care about these sorts of mounts and linkages, but they now appear to be very sensitive to them. What needs to be done to make this work? BTW, I think this move to SNAP is a disaster and completely the wrong way to go. Let's please stick with a single .deb packaging strategy which has proven itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1861453/+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 1890750] Re: Permission Denied when using SMB share as storage location
Fixed a cut & paste typo. -- 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/1890750 Title: Permission Denied when using SMB share as storage location Status in deja-dup package in Ubuntu: New Bug description: 1. Ubuntu release $ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 2. Package Version $ apt-cache policy deja-dup deja-dup: Installed: 40.7-0ubuntu1 Candidate: 40.7-0ubuntu1 Version table: *** 40.7-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 40.6-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 3. What I expected to happen Configure an SMB share as the network location to save my backups. I am using the same share that works with the Gnome File manager. 4. What happens instead: I get a permission denied error when trying to use a SMB share as the storage location. This share is mountable and read/writeable through the same path when accessing it with the Gnome File manager. Its unclear from the error what causes the failure or what I should be doing differently. I set the path to smb://mycloudex2ultra.local/bkup/, the folder to deja-dup and enter the correct username, domain, and password in the pop up dialog. Running with DEJA_DUP_DEBUG=1 shows the path as DUPLICITY: . Args: /usr/bin/duplicity --include=/home/tomg/.cache /deja-dup/metadata --exclude=/home/tomg/Downloads --exclude=/home/tomg/.local/share/Trash --exclude=/home/tomg/.cache /deja-dup --exclude=/home/tomg/.cache --include=/home/tomg --exclude=/sys --exclude=/run --exclude=/proc --exclude=/var/tmp --exclude=/tmp --exclude=/home/tomg/snap/*/*/.cache --exclude=/home/tomg/.var/app/*/cache --exclude=** --dry-run --volsize=25 / gio+smb://mycloudex2ultra.local/winston-bkup/deja-dup --verbosity=9 --archive-dir=/home/tomg/.cache/deja-dup --tempdir=/tmp --log-fd=26 and reveals this error: DUPLICITY: DEBUG 1 DUPLICITY: . Backtrace of previous error: Traceback (innermost last): DUPLICITY: . File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 376, in inner_retry DUPLICITY: . return fn(self, *args) DUPLICITY: . File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 570, in get DUPLICITY: . self.backend._get(remote_filename, local_path) DUPLICITY: . File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 150, in _get DUPLICITY: . self.__copy_file(source_file, target_file) DUPLICITY: . File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 121, in __copy_file DUPLICITY: . source.copy(target, DUPLICITY: . gi.repository.GLib.GError: g-io-error-quark: Permission denied (14) DUPLICITY: . DUPLICITY: WARNING 1 DUPLICITY: . Attempt 1 failed. Error: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1890750/+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 1890750] [NEW] Permission Denied when using SMB share as storage location
Public bug reported: 1. Ubuntu release $ lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 2. Package Version $ apt-cache policy deja-dup deja-dup: Installed: 40.7-0ubuntu1 Candidate: 40.7-0ubuntu1 Version table: *** 40.7-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 40.6-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 3. What I expected to happen Configure an SMB share as the network location to save my backups. I am using the same share that works with the Gnome File manager. 4. What happens instead: I get a permission denied error when trying to use a SMB share as the storage location. This share is mountable and read/writeable through the same path when accessing it with the Gnome File manager. Its unclear from the error what causes the failure or what I should be doing differently. I set the path to smb://mycloudex2ultra.local/bkup/, the folder to deja-dup and enter the correct username, domain, and password in the pop up dialog. Running with DEJA_DUP_DEBUG=1 shows the path as DUPLICITY: . Args: /usr/bin/duplicity --include=/home/tomg/.cache/deja- dup/metadata --exclude=/home/tomg/Downloads --exclude=/home/tomg/.local/share/Trash --exclude=/home/tomg/.cache /deja-dup --exclude=/home/tomg/.cache --include=/home/tomg --exclude=/sys --exclude=/run --exclude=/proc --exclude=/var/tmp --exclude=/tmp --exclude=/home/tomg/snap/*/*/.cache --exclude=/home/tomg/.var/app/*/cache --exclude=** --dry-run --volsize=25 / gio+smb://mycloudex2ultra.local/winston-bkup/deja-dup --verbosity=9 --archive-dir=/home/tomg/.cache/deja-dup --tempdir=/tmp --log-fd=26 and reveals this error: DUPLICITY: DEBUG 1 DUPLICITY: . Backtrace of previous error: Traceback (innermost last): DUPLICITY: . File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 376, in inner_retry DUPLICITY: . return fn(self, *args) DUPLICITY: . File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 570, in get DUPLICITY: . self.backend._get(remote_filename, local_path) DUPLICITY: . File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 150, in _get DUPLICITY: . self.__copy_file(source_file, target_file) DUPLICITY: . File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 121, in __copy_file DUPLICITY: . source.copy(target, DUPLICITY: . gi.repository.GLib.GError: g-io-error-quark: Permission denied (14) DUPLICITY: . DUPLICITY: WARNING 1 DUPLICITY: . Attempt 1 failed. Error: Permission denied ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New -- 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/1890750 Title: Permission Denied when using SMB share as storage location Status in deja-dup package in Ubuntu: New Bug description: 1. Ubuntu release $ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 2. Package Version $ apt-cache policy deja-dup deja-dup: Installed: 40.7-0ubuntu1 Candidate: 40.7-0ubuntu1 Version table: *** 40.7-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 40.6-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 3. What I expected to happen Configure an SMB share as the network location to save my backups. I am using the same share that works with the Gnome File manager. 4. What happens instead: I get a permission denied error when trying to use a SMB share as the storage location. This share is mountable and read/writeable through the same path when accessing it with the Gnome File manager. Its unclear from the error what causes the failure or what I should be doing differently. I set the path to smb://mycloudex2ultra.local/bkup/, the folder to deja-dup and enter the correct username, domain, and password in the pop up dialog. Running with DEJA_DUP_DEBUG=1 shows the path as DUPLICITY: . Args: /usr/bin/duplicity --include=/home/tomg/.cache /deja-dup/metadata --exclude=/home/tomg/Downloads --exclude=/home/tomg/.local/share/Trash --exclude=/home/tomg/.cache /deja-dup --exclude=/home/tomg/.cache --include=/home/tomg --exclude=/sys --exclude=/run --exclude=/proc --exclude=/var/tmp --exclude=/tmp --exclude=/home/tomg/snap/*/*/.cache --exclude=/home/tomg/.var/app/*/cache --exclude=** --dry-run --volsize=25 / gio+smb://mycloudex2ultra.local/winston-bkup/deja-dup --verbosity=9 --archive-dir=/home/tomg/.cache/deja-dup --tempdir=/tmp --log-fd=26 and reveals this error: DUPLICITY: DEBUG 1 DUPLICITY: . Backtrace of previous error: Traceback (innermost last): DUPLICITY: . File
[Desktop-packages] [Bug 1463190] Re: HTC One M8 mounted as gphoto not mtp
** Package changed: udev (Ubuntu) => libmtp (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1463190 Title: HTC One M8 mounted as gphoto not mtp Status in libmtp package in Ubuntu: New Bug description: On one an HTC One M8 auto-mounts in gvfs with an "mtp://" location. On the other (the computer used to report this bug) it mounts with a "gphoto2://" location. Pressing CTRL+L in Nautilus and entering the appropriate "mtp://" location manually mounts the device correctly and it works just fine, but leaves the "gphoto://" mounts in the left-hand panel. "gphoto://" is not appropriate for this device and does not support reading and writing of all file types. I have another computer with 14.04 installed which mounts the phone with an "mtp://" location automatically. I'm not sure why my other computer is working but I don't remember doing anything to make it work and they appear to have the same package versions installed for mtp and gvfs packages - although I don't know if I checked them all as I'm not familiar with which packages are used. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gvfs 1.20.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-54.91-generic 3.13.11-ckt20 Uname: Linux 3.13.0-54-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jun 8 22:56:34 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-05-07 (762 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gvfs UpgradeStatus: Upgraded to trusty on 2014-04-28 (406 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1463190/+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 1463190] [NEW] HTC One M8 mounted as gphoto not mtp
You have been subscribed to a public bug: On one an HTC One M8 auto-mounts in gvfs with an "mtp://" location. On the other (the computer used to report this bug) it mounts with a "gphoto2://" location. Pressing CTRL+L in Nautilus and entering the appropriate "mtp://" location manually mounts the device correctly and it works just fine, but leaves the "gphoto://" mounts in the left-hand panel. "gphoto://" is not appropriate for this device and does not support reading and writing of all file types. I have another computer with 14.04 installed which mounts the phone with an "mtp://" location automatically. I'm not sure why my other computer is working but I don't remember doing anything to make it work and they appear to have the same package versions installed for mtp and gvfs packages - although I don't know if I checked them all as I'm not familiar with which packages are used. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gvfs 1.20.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-54.91-generic 3.13.11-ckt20 Uname: Linux 3.13.0-54-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jun 8 22:56:34 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-05-07 (762 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gvfs UpgradeStatus: Upgraded to trusty on 2014-04-28 (406 days ago) ** Affects: libmtp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed trusty -- HTC One M8 mounted as gphoto not mtp https://bugs.launchpad.net/bugs/1463190 You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp 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 1888575] Re: Split motd-news config into a new package
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/388848 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1888575 Title: Split motd-news config into a new package Status in base-files package in Ubuntu: In Progress Status in ubuntu-meta package in Ubuntu: In Progress Status in base-files source package in Xenial: In Progress Status in ubuntu-meta source package in Xenial: In Progress Status in base-files source package in Bionic: In Progress Status in ubuntu-meta source package in Bionic: In Progress Status in base-files source package in Focal: In Progress Status in ubuntu-meta source package in Focal: In Progress Status in base-files source package in Groovy: In Progress Status in ubuntu-meta source package in Groovy: In Progress Bug description: The motd-news script is largely useless for desktop users, as they rarely login via a text console. It makes more sense for server users. We can use package dependencies to have the motd-news script enabled on servers, but disabled on desktops, and still handle upgrades. This is the plan: - move /etc/default/motd-news from base-files into a NEW package (motd-news-config) - have ubuntu-server depend on motd-news-config (or recommends) - have base-files break current ubuntu-server, so that if base-files if upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to the new version which has the depends (or recommends) on motd-news-config Care must be taken to preserve a changed /etc/default/motd-news when the upgrade installs the new motd-news-config package. For example, on a server that has set ENABLED=0 in /etc/default/motd-news and upgrades to the new base-files and ubuntu-server, and gets the new motd-config- news package, ENABLED=0 must remain set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888575/+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 1791788] Re: Layout switch unwanted combination Rshift+Lshift
** Package changed: udev (Ubuntu) => ubuntu ** Package changed: ubuntu => gnome-shell (Ubuntu) -- 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/1791788 Title: Layout switch unwanted combination Rshift+Lshift Status in gnome-shell package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.1 LTS Linux version 4.15.0-33-generic WHAT I EXPECT TO HAPPEN: "R-Shift + L-Shift" hotkey combination doesn't change keyboard layout when not configured to do so. WHAT HAPPENS INSTEAD: "R-Shift + L-Shift" changes keyboard layout even when not configured to do so. -- My machine is set up to use "L-Alt + L-Shift" combination for switching keyboard layout between English and Russian. The command I use to configure this combination: gsettings set org.gnome.desktop.input-sources xkb-options "['grp:lalt_lshift_toggle']" With this setting Ubuntu also reacts to "R-Shift + L-Shift" combination and switches the layout as well. This is very irritating, since when typing the C code I often need to use macros like MY_MACRO_WITH_UNDERSCORE, where I naturally hit both shift keys when typing a capital letter after an underscore. The issue appears only when the R-Shift is hit before the L-Shift and not the other way around. The issue doesn't appear when I disable my switch combination with: gsettings set org.gnome.desktop.input-sources xkb-options "['']" I also disabled default Super+Space and Super+Shift+Space combinations, although that doesn't affect the issue. I didn't set any other keyboard combinations for switching layouts. The issue appears both in the terminal and in GUI applications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791788/+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 1889477] Re: xdg-open on Kubuntu 20.04 reports 'Could not connect to localhost: Connection refused' if localhost service not already up
I'm using the same versions. Opening http:... links works fine for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1889477 Title: xdg-open on Kubuntu 20.04 reports 'Could not connect to localhost: Connection refused' if localhost service not already up Status in xdg-utils package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 (Kubuntu 20.04 Fresh Install) 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center xdg-utils: Installed: 1.1.3-2ubuntu1 Candidate: 1.1.3-2ubuntu1 3) What you expected to happen xdg-open "http://localhost:1313; to open the default browser at http://localhost:1313 4) What happened instead A gui dialog titled 'Error -- KIO Client' pops up with the message 'Could not connect to host localhost: Connection refused.' 5) More Info I use xdg-open "http://localhost:someport; in my bash scripts before it actually starts the service as a time saver. On older Ubuntu and other distros it would open the default browser (Firefox) with a page not found. I press reload once the service is setup and Firefox loads the page. On Kubuntu 20.04 xdg-open gets blocked if the port is not already opened. Example command: xdg-open "http://localhost:1313; This did work on Kubuntu and Ubuntu 18.04 and Ubuntu 19.10. Currently works on Manjaro KDE with latest stable update. Worked on Fedora 31 KDE (can not remember if I tested 32). Current Manjaro package reported as: xdg-utils 1.1.3+19+g9816ebb-1 Ubuntu 20.04 not tested. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xdg-utils 1.1.3-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Jul 29 13:53:07 2020 InstallationDate: Installed on 2020-05-28 (62 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: xdg-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1889477/+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 1890716] Re: xdg-mime query filetype index.html reports wrong type
** Tags added: html xdg-mime xdg-open ** Tags added: 20.04 kde kubuntu perl -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: xdg-mime query filetype index.html reports wrong type Status in xdg-utils package in Ubuntu: New Bug description: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1890716/+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 1791788] [NEW] Layout switch unwanted combination Rshift+Lshift
You have been subscribed to a public bug: Ubuntu 18.04.1 LTS Linux version 4.15.0-33-generic WHAT I EXPECT TO HAPPEN: "R-Shift + L-Shift" hotkey combination doesn't change keyboard layout when not configured to do so. WHAT HAPPENS INSTEAD: "R-Shift + L-Shift" changes keyboard layout even when not configured to do so. -- My machine is set up to use "L-Alt + L-Shift" combination for switching keyboard layout between English and Russian. The command I use to configure this combination: gsettings set org.gnome.desktop.input-sources xkb-options "['grp:lalt_lshift_toggle']" With this setting Ubuntu also reacts to "R-Shift + L-Shift" combination and switches the layout as well. This is very irritating, since when typing the C code I often need to use macros like MY_MACRO_WITH_UNDERSCORE, where I naturally hit both shift keys when typing a capital letter after an underscore. The issue appears only when the R-Shift is hit before the L-Shift and not the other way around. The issue doesn't appear when I disable my switch combination with: gsettings set org.gnome.desktop.input-sources xkb-options "['']" I also disabled default Super+Space and Super+Shift+Space combinations, although that doesn't affect the issue. I didn't set any other keyboard combinations for switching layouts. The issue appears both in the terminal and in GUI applications. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Confirmed -- Layout switch unwanted combination Rshift+Lshift https://bugs.launchpad.net/bugs/1791788 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell 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 1890716] [NEW] xdg-mime query filetype index.html reports wrong type
Public bug reported: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 ** Affects: xdg-utils (Ubuntu) Importance: Undecided Status: New ** Tags: 20.04 html kde kubuntu perl xdg-mime xdg-open ** Description changed: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html - files for anything except of text/html ! + files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html - 2. $ xdg-mime query filetype index.html # -> application/x-perl + 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! - Platform: + Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: xdg-mime query filetype index.html reports wrong type Status in xdg-utils package in Ubuntu: New Bug description: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1890716/+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 1714244] Re: [snap] apparmor denials on /etc/chromium-browser/policies/
Is there any update or workaround on this issue? This is going to be a problem to everyone in enterprise environments. -- 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/1714244 Title: [snap] apparmor denials on /etc/chromium-browser/policies/ Status in chromium-browser package in Ubuntu: Triaged Bug description: [1565519.440403] audit: type=1400 audit(1504185084.568:68574811): apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium" name="/etc/chromium-browser/policies/managed/" pid=19433 comm ="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [1565519.440527] audit: type=1400 audit(1504185084.568:68574812): apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium" name="/etc/chromium-browser/policies/recommended/" pid=19433 comm ="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Those denials don't appear to prevent the app from running. Still, they should be investigated and fixed if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1714244/+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 1886414] Re: the chromium snap takes a long time to install without visible user feedback, seems stuck
Sorry, I'm not sure what you mean with that last comment. Can you please elaborate? -- 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/1886414 Title: the chromium snap takes a long time to install without visible user feedback, seems stuck Status in chromium-browser package in Ubuntu: Confirmed Bug description: after an initial attemp to install where the progress got stuck at 20%, i rebooted as there were a bunch of other system updates that had been applied after a fresh isntall. Now chromium wont install dantheperson@danski:~$ sudo apt install chromium-browser Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: chromium-browser 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 48.4 kB of archives. After this operation, 164 kB of additional disk space will be used. Get:1 http://nz.archive.ubuntu.com/ubuntu focal-updates/universe amd64 chromium-browser amd64 81.0.4044.129-0ubuntu0.20.04.1 [48.4 kB] Fetched 48.4 kB in 0s (1,527 kB/s) Preconfiguring packages ... (Reading database ... 185728 files and directories currently installed.) Preparing to unpack .../chromium-browser_81.0.4044.129-0ubuntu0.20.04.1_amd64.deb ... => Installing the chromium snap ==> Checking connectivity with the snap store ==> Installing the chromium snap error: snap "chromium" has "install-snap" change in progress dpkg: error processing archive /var/cache/apt/archives/chromium-browser_81.0.4044.129-0ubuntu0.20.04.1_amd64.deb (--unpack): new chromium-browser package pre-installation script subprocess returned error exit status 10 Errors were encountered while processing: /var/cache/apt/archives/chromium-browser_81.0.4044.129-0ubuntu0.20.04.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 81.0.4044.129-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 6 23:39:11 2020 Dependencies: ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-07-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: chromium-browser Title: package chromium-browser 81.0.4044.129-0ubuntu0.20.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1886414/+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 1886414] Re: the chromium snap takes a long time to install without visible user feedback, seems stuck
Please put TNT on snap... This was a machine of stress on the most easy thing to do on any Linux OS, installing software. -- 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/1886414 Title: the chromium snap takes a long time to install without visible user feedback, seems stuck Status in chromium-browser package in Ubuntu: Confirmed Bug description: after an initial attemp to install where the progress got stuck at 20%, i rebooted as there were a bunch of other system updates that had been applied after a fresh isntall. Now chromium wont install dantheperson@danski:~$ sudo apt install chromium-browser Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: chromium-browser 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 48.4 kB of archives. After this operation, 164 kB of additional disk space will be used. Get:1 http://nz.archive.ubuntu.com/ubuntu focal-updates/universe amd64 chromium-browser amd64 81.0.4044.129-0ubuntu0.20.04.1 [48.4 kB] Fetched 48.4 kB in 0s (1,527 kB/s) Preconfiguring packages ... (Reading database ... 185728 files and directories currently installed.) Preparing to unpack .../chromium-browser_81.0.4044.129-0ubuntu0.20.04.1_amd64.deb ... => Installing the chromium snap ==> Checking connectivity with the snap store ==> Installing the chromium snap error: snap "chromium" has "install-snap" change in progress dpkg: error processing archive /var/cache/apt/archives/chromium-browser_81.0.4044.129-0ubuntu0.20.04.1_amd64.deb (--unpack): new chromium-browser package pre-installation script subprocess returned error exit status 10 Errors were encountered while processing: /var/cache/apt/archives/chromium-browser_81.0.4044.129-0ubuntu0.20.04.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 81.0.4044.129-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 6 23:39:11 2020 Dependencies: ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-07-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: chromium-browser Title: package chromium-browser 81.0.4044.129-0ubuntu0.20.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1886414/+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 1890650] Re: Activities button, Alt-F1, and super not working after upgrade to 20.04
** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-shell (Ubuntu) -- 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/1890650 Title: Activities button, Alt-F1, and super not working after upgrade to 20.04 Status in gnome-shell package in Ubuntu: New Bug description: If I hit the Activities button, all open applications are hidden. There is no way to get the applications to display again. The application I select is started, and shows up on the vertical bar in the left with an orange dot by it. What magic is needed to bring the applications back? They are still there. I see them when I go to log out. Logging out is the only option for restoring Gnome. The same problem happens if I hit Alt-F1 or Super. Shouldn't these toggle? The only way to get a screen shot it with my phone. Sorry for the quality. You can see on the left that I started gimp.Up to 19.10, when I used "Activities", it would launch the app and then return to my running applications. Originally asked here: https://askubuntu.com/questions/1264414/activities-button-alt-f1-and- super-not-working-after-upgrade-to-20-04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.23 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 13:29:43 2020 InstallationDate: Installed on 2018-10-14 (661 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-08-03 (2 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890650/+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 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
The post 54 workaround fixed it for me, thanks much @khitschler. (https://bugs.launchpad.net/ubuntu/+source/plasma- desktop/+bug/1849084/comments/54) Running Ubuntu 18.04.1 with latest stable kernel (5.4.0-42), but this has been a problem since the upgrade from 16.04. Since there are no issues with the workaround, it will remain in place until the upgrade to 20.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver Status in kwin package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: This is a well investigated bug by me. Problem: a black screen freeze occurs by suspend-resume process Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17 Kernel version: default 5.3.10 or the mainline 5.4.0rc3 xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works well This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is enabled in Plasma settings. Xrender is OK however I don't like screen tearing. On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the Gnome's compositor is enabled. (I don't know what is the default one there but I haven't disabled it) I think this is a Kwin / amdgpu driver related bug because of the differentiation. These can be fixed even in Kwin/opengl compositor not just in the amdgpu driver or in kernel. One possible solution: disable opengl compositor by suspend and re- enable it after login. Use fe.: Xrender before login / before the system restored from suspend. For Ubuntu's maintainers: Couldn't be this problem solved by a downstream solution? Maybe a proper script could be enough by resume and by suspend. There are a lot of bugs like this reported in freedesktop bugreport and the developers haven't got enough time for fix them fast enough. Syslog: Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 00 00 Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 00010002 Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 0202 RCX: 046a Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 0202 RDI: 0002 Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: R09: 94da76b2d170 Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: b7b54274b70c R12: 94da76b2d000 Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 94da758d25d0 R15: 94da270d1400 Oct 21 10:57:26 pc kernel: [ 9475.308861] FS: 7f2a1b9bea80() GS:94da87c4() knlGS: Oct 21 10:57:26 pc kernel: [ 9475.308863] CS: 0010 DS: ES: CR0: 80050033 Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 00012c11 CR4: 003406e0 Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace: Oct 21 10:57:26 pc kernel: [ 9475.308977] amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.308991] commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309000] ? commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309009] drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309115] amdgpu_dm_atomic_commit+0x95/0xa0 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309135] drm_atomic_commit+0x4a/0x50 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309144] drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309159] drm_mode_setcrtc+0x1cd/0x7a0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309234] ? amdgpu_cs_wait_ioctl+0xd6/0x150 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309249] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309262] drm_ioctl_kernel+0xae/0xf0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309276] drm_ioctl+0x234/0x3d0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309290] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309370] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309376] do_vfs_ioctl+0x407/0x670 Oct 21 10:57:26 pc kernel: [ 9475.309379] ? do_futex+0x10f/0x1e0 Oct 21 10:57:26 pc kernel: [ 9475.309382] ksys_ioctl+0x67/0x90 Oct 21 10:57:26 pc kernel: [ 9475.309384] __x64_sys_ioctl+0x1a/0x20 Oct 21 10:57:26 pc kernel: [ 9475.309388]
[Desktop-packages] [Bug 1890650] [NEW] Activities button, Alt-F1, and super not working after upgrade to 20.04
You have been subscribed to a public bug: If I hit the Activities button, all open applications are hidden. There is no way to get the applications to display again. The application I select is started, and shows up on the vertical bar in the left with an orange dot by it. What magic is needed to bring the applications back? They are still there. I see them when I go to log out. Logging out is the only option for restoring Gnome. The same problem happens if I hit Alt-F1 or Super. Shouldn't these toggle? The only way to get a screen shot it with my phone. Sorry for the quality. You can see on the left that I started gimp.Up to 19.10, when I used "Activities", it would launch the app and then return to my running applications. Originally asked here: https://askubuntu.com/questions/1264414/activities-button-alt-f1-and- super-not-working-after-upgrade-to-20-04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.23 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 13:29:43 2020 InstallationDate: Installed on 2018-10-14 (661 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-08-03 (2 days ago) VarLogDistupgradeTermlog: ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal -- Activities button, Alt-F1, and super not working after upgrade to 20.04 https://bugs.launchpad.net/bugs/1890650 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell 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 1888575] Re: Split motd-news config into a new package
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/388835 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1888575 Title: Split motd-news config into a new package Status in base-files package in Ubuntu: In Progress Status in ubuntu-meta package in Ubuntu: In Progress Status in base-files source package in Xenial: In Progress Status in ubuntu-meta source package in Xenial: In Progress Status in base-files source package in Bionic: In Progress Status in ubuntu-meta source package in Bionic: In Progress Status in base-files source package in Focal: In Progress Status in ubuntu-meta source package in Focal: In Progress Status in base-files source package in Groovy: In Progress Status in ubuntu-meta source package in Groovy: In Progress Bug description: The motd-news script is largely useless for desktop users, as they rarely login via a text console. It makes more sense for server users. We can use package dependencies to have the motd-news script enabled on servers, but disabled on desktops, and still handle upgrades. This is the plan: - move /etc/default/motd-news from base-files into a NEW package (motd-news-config) - have ubuntu-server depend on motd-news-config (or recommends) - have base-files break current ubuntu-server, so that if base-files if upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to the new version which has the depends (or recommends) on motd-news-config Care must be taken to preserve a changed /etc/default/motd-news when the upgrade installs the new motd-news-config package. For example, on a server that has set ENABLED=0 in /etc/default/motd-news and upgrades to the new base-files and ubuntu-server, and gets the new motd-config- news package, ENABLED=0 must remain set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888575/+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
After booting the liquorix kernel the normal kernel started working too. Although with updated firmware. The difference is that the firmware is loading while before it didn't load at all. -- 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 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/pulseaudio/+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
[Desktop-packages] [Bug 1890632] [NEW] Can't open preferences
Public bug reported: I can't seem to access the rhymbox preferences. 'Preferences' does not appear in the application menu (see attachment) since ubuntu 17.10. I was still able to edit the preferences from the menu under the song slider, but I have now accidentally removed the whole top bar (with the current song, the previous, next, pause buttons, and that menu button). So now I can't open the preferences, nor see the current song anymore, or have it display again. Note that the option in the view menu might have been from the Alternative-Toolbar plugin A temporary fix to get the view menu again would be appreciated too. $ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 $ apt-cache policy rhythmbox rhythmbox: Installed: 3.4.4-1ubuntu2 Candidate: 3.4.4-1ubuntu2 Version table: *** 3.4.4-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Mirror of the attachment (screenshot of the application menu): https://i.imgur.com/CJUVoRZ.png ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Attachment added: "rhythmbox no preferences.png" https://bugs.launchpad.net/bugs/1890632/+attachment/5399332/+files/rhythmbox%20no%20preferences.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1890632 Title: Can't open preferences Status in rhythmbox package in Ubuntu: New Bug description: I can't seem to access the rhymbox preferences. 'Preferences' does not appear in the application menu (see attachment) since ubuntu 17.10. I was still able to edit the preferences from the menu under the song slider, but I have now accidentally removed the whole top bar (with the current song, the previous, next, pause buttons, and that menu button). So now I can't open the preferences, nor see the current song anymore, or have it display again. Note that the option in the view menu might have been from the Alternative-Toolbar plugin A temporary fix to get the view menu again would be appreciated too. $ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 $ apt-cache policy rhythmbox rhythmbox: Installed: 3.4.4-1ubuntu2 Candidate: 3.4.4-1ubuntu2 Version table: *** 3.4.4-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Mirror of the attachment (screenshot of the application menu): https://i.imgur.com/CJUVoRZ.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1890632/+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 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
The pulseaudio installed on my Ubuntu 20.04.1 systems is the following: pulseaudio - 1:13.99.1-1ubuntu3.5 deleting ~/.config/pulse and reboot fixed the problem of sound being directed to builtin speakers instead of the headphones although headphones were selected as the output device. Verified this on a Dell XPS labtop and an AMD desktop. Until 1:13.99.1-1ubuntu6 is released, I recommend deleting the config file and rebooting. -- 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/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: In Progress Status in pulseaudio source package in Groovy: Fix Released Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1866194/+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 1890625] [NEW] chromium: missing syscalls whitelist from seccomp
Public bug reported:
Whenever I start chromium's snap, I get the following messages:
Aug 6 10:50:08 simon-lemur kernel: [10608.138795] audit: type=1326
audit(1596725407.998:159): auid=1000 uid=1000 gid=1000 ses=2 pid=32290
comm="chrome" exe="/snap/chromium/1244/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=203 compat=0 ip=0x7f8f31df4b9f code=0x5
...{repeats 3 times}...
Aug 6 10:50:08 simon-lemur org.gnome.Shell.desktop[3092]: WARNING: Kernel has
no file descriptor comparison support: Operation not permitted
Aug 6 10:50:08 simon-lemur kernel: [10608.433753] audit: type=1326
audit(1596725408.290:163): auid=1000 uid=1000 gid=1000 ses=2 pid=32290
comm="ThreadPoolForeg"
exe="/snap/chromium/1244/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=312 compat=0 ip=0x7f8f2b614959 code=0x5
...{repeats 4 times}...
According to
https://github.com/torvalds/linux/blob/master/arch/x86/entry/syscalls/syscall_64.tbl,
it seems that syscall 203 is sys_sched_setaffinity and 312 is sys_kcmp.
The blocking of sys_kcmp could probably explain the "WARNING: Kernel has
no file descriptor comparison support: Operation not permitted" message
from org.gnome.Shell.desktop.
Additional information
$ uname -a
Linux simon-lemur 5.4.0-42-generic #46~18.04.1-Ubuntu SMP Fri Jul 10 07:21:24
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -rd
Description:Ubuntu 18.04.4 LTS
Release:18.04
$ apt-cache policy snapd
snapd:
Installed: 2.45.1+18.04.2
Candidate: 2.45.1+18.04.2
Version table:
*** 2.45.1+18.04.2 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
100 /var/lib/dpkg/status
2.32.5+18.04 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
$ snap info chromium
name: chromium
summary: Chromium web browser, open-source version of Chrome
publisher: Canonical✓
store-url: https://snapcraft.io/chromium
contact:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
license: unset
description: |
An open-source browser project that aims to build a safer, faster, and more
stable way for all
Internet users to experience the web.
commands:
- chromium.chromedriver
- chromium
snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
tracking: latest/stable
refresh-date: 7 days ago, at 11:45 EDT
channels:
latest/stable:84.0.4147.105 2020-07-30 (1244) 166MB -
latest/candidate: 84.0.4147.105 2020-07-30 (1244) 166MB -
latest/beta: 85.0.4183.49 2020-07-31 (1248) 167MB -
latest/edge: 86.0.4221.3 2020-08-05 (1257) 167MB -
installed: 84.0.4147.105(1244) 166MB -
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
--
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/1890625
Title:
chromium: missing syscalls whitelist from seccomp
Status in chromium-browser package in Ubuntu:
New
Bug description:
Whenever I start chromium's snap, I get the following messages:
Aug 6 10:50:08 simon-lemur kernel: [10608.138795] audit: type=1326
audit(1596725407.998:159): auid=1000 uid=1000 gid=1000 ses=2 pid=32290
comm="chrome" exe="/snap/chromium/1244/usr/lib/chromium-browser/chrome" sig=0
arch=c03e syscall=203 compat=0 ip=0x7f8f31df4b9f code=0x5
...{repeats 3 times}...
Aug 6 10:50:08 simon-lemur org.gnome.Shell.desktop[3092]: WARNING: Kernel
has no file descriptor comparison support: Operation not permitted
Aug 6 10:50:08 simon-lemur kernel: [10608.433753] audit: type=1326
audit(1596725408.290:163): auid=1000 uid=1000 gid=1000 ses=2 pid=32290
comm="ThreadPoolForeg"
exe="/snap/chromium/1244/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=312 compat=0 ip=0x7f8f2b614959 code=0x5
...{repeats 4 times}...
According to
https://github.com/torvalds/linux/blob/master/arch/x86/entry/syscalls/syscall_64.tbl,
it seems that syscall 203 is sys_sched_setaffinity and 312 is
sys_kcmp. The blocking of sys_kcmp could probably explain the
"WARNING: Kernel has no file descriptor comparison support: Operation
not permitted" message from org.gnome.Shell.desktop.
Additional information
$ uname -a
Linux simon-lemur 5.4.0-42-generic #46~18.04.1-Ubuntu SMP Fri Jul 10 07:21:24
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -rd
Description: Ubuntu 18.04.4 LTS
Release: 18.04
$ apt-cache policy snapd
snapd:
Installed: 2.45.1+18.04.2
Candidate: 2.45.1+18.04.2
Version table:
*** 2.45.1+18.04.2 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
100 /var/lib/dpkg/status
2.32.5+18.04 500
500
[Desktop-packages] [Bug 1890619] Re: poppler fails to build on s390x with gcc10 due to symbols changes
tah. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1890619 Title: poppler fails to build on s390x with gcc10 due to symbols changes Status in poppler package in Ubuntu: New Bug description: The build log is there https://launchpadlibrarian.net/491645678/buildlog_ubuntu-groovy-s390x.poppler_0.86.1-0ubuntu1_BUILDING.txt.gz the errors are * Build-Depends-Package: libpoppler-glib-dev - (regex)"^_Z.*@Base$" 0.86.1 +#MISSING: 0.86.1-0ubuntu1# (regex)"^_Z.*@Base$" 0.86.1 + _ZN7Poppler19UnicodeParsedStringERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 0.86.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1890619/+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 1890619] [NEW] poppler fails to build on s390x with gcc10 due to symbols changes
Public bug reported: The build log is there https://launchpadlibrarian.net/491645678/buildlog_ubuntu-groovy-s390x.poppler_0.86.1-0ubuntu1_BUILDING.txt.gz the errors are * Build-Depends-Package: libpoppler-glib-dev - (regex)"^_Z.*@Base$" 0.86.1 +#MISSING: 0.86.1-0ubuntu1# (regex)"^_Z.*@Base$" 0.86.1 + _ZN7Poppler19UnicodeParsedStringERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 0.86.1-0ubuntu1 ** Affects: poppler (Ubuntu) Importance: High Assignee: Dimitri John Ledkov (xnox) Status: New ** Tags: ftbfs ** Changed in: poppler (Ubuntu) Importance: Undecided => High ** Changed in: poppler (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1890619 Title: poppler fails to build on s390x with gcc10 due to symbols changes Status in poppler package in Ubuntu: New Bug description: The build log is there https://launchpadlibrarian.net/491645678/buildlog_ubuntu-groovy-s390x.poppler_0.86.1-0ubuntu1_BUILDING.txt.gz the errors are * Build-Depends-Package: libpoppler-glib-dev - (regex)"^_Z.*@Base$" 0.86.1 +#MISSING: 0.86.1-0ubuntu1# (regex)"^_Z.*@Base$" 0.86.1 + _ZN7Poppler19UnicodeParsedStringERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 0.86.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1890619/+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 1327801] Re: Bightness and contrast settings have no effect
After updating to Mint 20, I have the same issue with my Lide 60. It worked before, and now brightness and contrast settings are ignored. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1327801 Title: Bightness and contrast settings have no effect Status in simple-scan package in Ubuntu: Triaged Bug description: Scanner: Canon, Inc. CanoScan N1240U/LiDE 30 Ubuntu 14.04, Simple Scan version 3.12.1. Adjusting the settings of brightness and contrast has no effect. With the default for scanning in "text" mode being too bright, this makes "Simple Scan" in text mode unusable for me. Brightness and contrast settings don't work in "foto" mode, too. But the default of the foto mode is usable. Brightness setting does work in program "Skanlite". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1327801/+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 1890613] [NEW] Gnome unresponsive JS ERROR: TypeError: windowActor is null
Public bug reported: gnome-shell becomes unresponsive after about 1 day. I'm able to interact with the window that had focus when the problem appears (in this case it was Chrome), but I'm unable to select or otherwise interact with other windows, the shell, dock, or indicators. The logs are spammed with gnome-shell[2916]: JS ERROR: TypeError: windowActor is null#012_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28#012vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14 This looks similar to but different enough from https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841774 I was using the i915 driver when this happened if that makes any difference ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 09:08:32 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-12 (54 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal package-from-proposed -- 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/1890613 Title: Gnome unresponsive JS ERROR: TypeError: windowActor is null Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell becomes unresponsive after about 1 day. I'm able to interact with the window that had focus when the problem appears (in this case it was Chrome), but I'm unable to select or otherwise interact with other windows, the shell, dock, or indicators. The logs are spammed with gnome-shell[2916]: JS ERROR: TypeError: windowActor is null#012_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28#012vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14 This looks similar to but different enough from https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841774 I was using the i915 driver when this happened if that makes any difference ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 09:08:32 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-12 (54 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890613/+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 1838152] Re: gnome-shell freezes on notification arrival (fixed upstream)
** Also affects: gnome-shell (Ubuntu Bionic) Importance: Undecided Status: New -- 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/1838152 Title: gnome-shell freezes on notification arrival (fixed upstream) Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: New Status in gnome-shell source package in Disco: Fix Released Status in gnome-shell source package in Eoan: Fix Released Bug description: Sometimes certain notifications make the desktop unresponsive for a few seconds and then gnome-shell crashes and all extensions are reloaded. I have found an upstream bug with a patch, but it's probably not in the Ubuntu's package. I thought of creating an issue in case it is something not known. https://gitlab.gnome.org/GNOME/gnome-shell/issues/470 https://gitlab.gnome.org/GNOME/gnome- shell/commit/86a00b6872375a266449beee1ea6d5e94f1ebbcb In my case it happens only with the notifications of gsconnect and maybe android studio. I have reproduced the problem in gsconnect in case it helps. https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/549 the error is: lug 27 19:55:56 ghv gnome-shell[4071]: Object Meta.Background (0x55ce6b4cf300), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Ubuntu 18.04 gnome-shell Version: 3.28.4-0ubuntu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1838152/+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 1890411] Re: [bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
Is there any other information I could provide?
--
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/1890411
Title:
[bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
Status in mesa package in Ubuntu:
New
Status in xorg-server package in Ubuntu:
New
Bug description:
When ubuntu starts up, gdm3 does not start due to a crash in the the
xserver:
[ 1271.342] (II) SELinux: Disabled on system
[ 1271.346] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 1271.346] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[ 1271.346] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 1271.346] (II) AIGLX: enabled GLX_SGI_swap_control
[ 1271.346] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 1271.346] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 1271.346] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[ 1271.346] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[ 1271.346] (II) AIGLX: Loaded and initialized i965
[ 1271.346] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 1271.348] (II) modeset(0): Damage tracking initialized
[ 1271.348] (II) modeset(0): Setting screen physical size to 508 x 317
[ 1271.352] (EE)
[ 1271.352] (EE) Backtrace:
[ 1271.352] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5649b579bacd]
[ 1271.352] (EE) 1: /usr/lib/xorg/Xorg (0x5649b55e3000+0x1bc869)
[0x5649b579f869]
[ 1271.352] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f5c7d0a5000+0x128a0) [0x7f5c7d0b78a0]
[ 1271.352] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x8e8652) [0x7f5c784e2652]
[ 1271.352] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x8e877f) [0x7f5c784e277f]
[ 1271.352] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x122916) [0x7f5c77d1c916]
[ 1271.352] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x1189bc) [0x7f5c77d129bc]
[ 1271.352] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x109c1b) [0x7f5c77d03c1b]
[ 1271.352] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x279558) [0x7f5c77e73558]
[ 1271.352] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x2796e3) [0x7f5c77e736e3]
[ 1271.352] (EE) 10: /usr/lib/xorg/modules/libglamoregl.so
(0x7f5c79937000+0x1a1ab) [0x7f5c799511ab]
[ 1271.352] (EE) 11: /usr/lib/xorg/Xorg (0x5649b55e3000+0x13ed03)
[0x5649b5721d03]
[ 1271.352] (EE) 12: /usr/lib/xorg/Xorg (miPaintWindow+0x22f)
[0x5649b577fd1f]
[ 1271.352] (EE) 13: /usr/lib/xorg/Xorg (miWindowExposures+0x112)
[0x5649b577fa62]
[ 1271.352] (EE) 14: /usr/lib/xorg/Xorg (0x5649b55e3000+0xa9c41)
[0x5649b568cc41]
[ 1271.352] (EE) 15: /usr/lib/xorg/Xorg (MapWindow+0x114) [0x5649b5665d04]
[ 1271.352] (EE) 16: /usr/lib/xorg/Xorg (0x5649b55e3000+0x56e79)
[0x5649b5639e79]
[ 1271.352] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xe7) [0x7f5c7ccd5b97]
[ 1271.352] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x5649b5623b8a]
[ 1271.352] (EE)
[ 1271.352] (EE) Segmentation fault at address 0x4
[ 1271.352] (EE)
Fatal server error:
[ 1271.352] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 1271.352] (EE)
[ 1271.352] (EE)
As i965_dri.so is part of the libgl-mesa-dri package I downgraded this
specific package from version 20.0.8-0ubuntu1~18.04.1 back to
19.2.8-0ubuntu0~18.04.3.
This solves the problem. So I suspect that the problem is in this
specific package.
My machine is (uname):
4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64
x86_64 GNU/Linux
(lspci)
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller
(rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen
Core Processor Integrated Graphics Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series
Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High
Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI
Express Root Port #1 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI
Express Root Port #3 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB EHCI #1 (rev 05)
00:1f.0 ISA bridge: Intel
[Desktop-packages] [Bug 1890593] [NEW] Xorg freeze
Public bug reported: Just installed ubuntu 20.04 and I am stuck on ubuntu with a spining logo. If I go to other tty and unplug the HDMI screens I can get to the login screen, Otherwise I cant. I did checked the md5sum of the iso before installing and its was correct. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 14:29:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T570 [17aa:2248] Subsystem: Lenovo GM108GLM [Quadro M520 Mobile] [17aa:2248] InstallationDate: Installed on 2020-08-05 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20HCS0660M ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=be1cbba6-c044-4d36-a6f4-fe872353a538 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1VET49W (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HCS0660M dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1VET49W(1.39):bd05/08/2019:svnLENOVO:pn20HCS0660M:pvrThinkPadP51s:rvnLENOVO:rn20HCS0660M:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad THINKPAD P51S dmi.product.name: 20HCS0660M dmi.product.sku: LENOVO_MT_20HC_BU_Think_FM_ThinkPad THINKPAD P51S dmi.product.version: ThinkPad P51s 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/1890593 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Just installed ubuntu 20.04 and I am stuck on ubuntu with a spining logo. If I go to other tty and unplug the HDMI screens I can get to the login screen, Otherwise I cant. I did checked the md5sum of the iso before installing and its was correct. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 14:29:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches
[Desktop-packages] [Bug 1890584] [NEW] Chromium (snap) UI elements are too small even on non Hi-DPI display.
Public bug reported:
On this system, for some reason I have to always modify the launchers for
Chromium in order to get the UI elements (bookmarks in the bookmark bar, tabs,
etc) with this flag '--force-device-scale-factor=1' but even then if I click on
a link in an email it opens Chromium with the tiny UI elements, despite my
efforts to try and make it open as it should.
This is REEELLY ANNOYING and didn't use to happen in the normal .deb/APT
version of Chromium but as we all know now Canonical prefers to shove this
nonsense down users' throats whether they like it or not just like Apple does.
But besides that I'm not going to go down this argument here as there is no
point, but there is not other way for me to fix this but report this bug.
Expected behaviour: Chromium should open with scale factor 1 by default.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 83.0.4103.97-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Thu Aug 6 13:05:12 2020
InstallationDate: Installed on 2020-08-05 (0 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64
(20200423)
Snap.ChromeDriverVersion: ChromeDriver 84.0.4147.105
(a6b12dfad6663f13a7e16e9a42a6a4975374096b-refs/branch-heads/4147@{#943})
Snap.ChromiumVersion: Chromium 84.0.4147.105 snap
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: chromium-browser (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 chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1890584
Title:
Chromium (snap) UI elements are too small even on non Hi-DPI display.
Status in chromium-browser package in Ubuntu:
New
Bug description:
On this system, for some reason I have to always modify the launchers for
Chromium in order to get the UI elements (bookmarks in the bookmark bar, tabs,
etc) with this flag '--force-device-scale-factor=1' but even then if I click on
a link in an email it opens Chromium with the tiny UI elements, despite my
efforts to try and make it open as it should.
This is REEELLY ANNOYING and didn't use to happen in the normal .deb/APT
version of Chromium but as we all know now Canonical prefers to shove this
nonsense down users' throats whether they like it or not just like Apple does.
But besides that I'm not going to go down this argument here as there is no
point, but there is not other way for me to fix this but report this bug.
Expected behaviour: Chromium should open with scale factor 1 by
default.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 83.0.4103.97-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Thu Aug 6 13:05:12 2020
InstallationDate: Installed on 2020-08-05 (0 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64
(20200423)
Snap.ChromeDriverVersion: ChromeDriver 84.0.4147.105
(a6b12dfad6663f13a7e16e9a42a6a4975374096b-refs/branch-heads/4147@{#943})
Snap.ChromiumVersion: Chromium 84.0.4147.105 snap
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890584/+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 1888558] Re: VLC is using up to 2 GB of RAM just to play a regular 720px HD video
As suspected, this seems to be an issue with a driver. ** Package changed: vlc (Ubuntu) => mesa (Ubuntu) -- 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/1888558 Title: VLC is using up to 2 GB of RAM just to play a regular 720px HD video Status in mesa package in Ubuntu: Incomplete Bug description: On my computer running Ubuntu 20.04 and XFCE desktop, The VLC GUI player is using an increasing amount of memory as time progressed. The video is a typical H.264 movie (MP4 file format). I have let the application sit for a few days, and here is the usage of RAM as the days went by: Date Time(EDT) VSIZE RSS 2020-07-19 20:19:162848984455148 2020-07-20 13:09:063307736926156 2020-07-22 13:18:054487464 2059848 The process itself was started on: Sat Jul 18 21:41:24 2020 I was playing the video only for about ~5 minutes when the program started, then let the program sit idle for a few days. Today I found that it consumed 2GB RSS as shown above! I am reporting this issue to see if something in my system is messing up VLC memory usage. In an older laptop, trying to play the same file (with VLC version 2.0.3) has its memory consumption starting at just under 190M. Wirawan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: vlc 3.0.9.2-1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Jul 22 13:19:21 2020 SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1888558/+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 1888558] [NEW] VLC is using up to 2 GB of RAM just to play a regular 720px HD video
You have been subscribed to a public bug: On my computer running Ubuntu 20.04 and XFCE desktop, The VLC GUI player is using an increasing amount of memory as time progressed. The video is a typical H.264 movie (MP4 file format). I have let the application sit for a few days, and here is the usage of RAM as the days went by: Date Time(EDT) VSIZE RSS 2020-07-19 20:19:162848984455148 2020-07-20 13:09:063307736926156 2020-07-22 13:18:054487464 2059848 The process itself was started on: Sat Jul 18 21:41:24 2020 I was playing the video only for about ~5 minutes when the program started, then let the program sit idle for a few days. Today I found that it consumed 2GB RSS as shown above! I am reporting this issue to see if something in my system is messing up VLC memory usage. In an older laptop, trying to play the same file (with VLC version 2.0.3) has its memory consumption starting at just under 190M. Wirawan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: vlc 3.0.9.2-1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Jul 22 13:19:21 2020 SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mesa (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal -- VLC is using up to 2 GB of RAM just to play a regular 720px HD video https://bugs.launchpad.net/bugs/1888558 You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa 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 1890436] Re: VGA signal is ghosted and stretched (Intel® HD Graphics 2500)
Well this is a PC with onboard intel graphics. A memory issue would mean RAM problem which is not the case here. I can see a visual corruption. If you can't see it then there is nothing more to say here. You are welcomed to see the dmesg and figure out what happens. There is no hardware damage on my PC. This occurs with a specific BIOS setting as I described above and it affects only ubuntu. Windows 10 2004 work fine on my "damaged" PC. If you wish to get a screenshot from windows working fine, I can upload it here. I might test wayland at the evening but linux kernel detects the problem and shouts about underrun error in FIFO A as the first attached image with dmesg shows. So if you have anything usefull to write that is related to this bug report, please do so. If you just continue to say that my hardware is damaged you are free to close this bug right away. I will try another distro and open another bug there... -- 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/1890436 Title: VGA signal is ghosted and stretched (Intel® HD Graphics 2500) Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello, last week I was digging in the BIOS of my PC at work since I tried to see if there is a way to update the dbx for secure boot. Since there was no option to perform this task, I modified some settings. In detail, I disabled CSM in BIOS and that's when hell broke loose! To get an idea about the hardware, the Lenovo machine isn't running the latest BIOS as its updater is broken and won't update it within win or its ISO image. It uses the previous version released by its manufacturer. The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled the DP monitor is lit first and then the VGA one prior OS loading. When CSM is disabled it goes the other way around. The VGA monitor is lit and the DP one opens up during OS load. With CSM disabled the VGA monitor is the primary one and it is corrupted as you can see on the pictures I have attached. Interestingly printing screens within Ubuntu does not capture the corruption problem I am getting as you can see on the pictures I have also attached. Neither X log contains anything useful. The issue is repeatable on every boot. As I have seen on other bug reports, I have enabled DRM debug, captured the dmesg using a huge buffer to get it and have uploaded it as well. I hope that it will help you track this issue down and fix it soon. Since I will be away some days for vacation, I will have physical access to it till this Friday and will get back to work at the 24th of August. In the mean time, I hope that someone will pinpoint the root cause of it and prepare a patch. Since this machine is running w10 2004, it should be noted that in win I do not get any corruption at all either in CSM mode or UEFI mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CasperVersion: 1.445 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 11:30:51 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 3209C54 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT9BAUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3209C54 dmi.product.sku: LENOVO_MT_3209 dmi.product.version: ThinkCentre M92p dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri:
[Desktop-packages] [Bug 1890572] Re: USB backend never ends if the printer is not connected
** Description changed:
- USB backend never ends if the printer is not connected. we have been
+ USB backend never ends if the printer is not connected. We have been
able to identify a infinity loop in print_device function in usb-
libusb.c file:
```
- fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
- while ((g.printer = find_device(print_cb, uri)) == NULL)
- {
- _cupsLangPrintFilter(stderr, "INFO",
-_("Waiting for printer to become available."));
- sleep(5);
- }
+ fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
+ while ((g.printer = find_device(print_cb, uri)) == NULL)
+ {
+ _cupsLangPrintFilter(stderr, "INFO",
+ _("Waiting for printer to become available."));
+ sleep(5);
+ }
```
It's also easy to test by invoking the backend by hand:
-
```
# export DEVICE_URI='usb://Printer/Model?serial=?'
# /usr/lib/cups/backend/usb 0 root title 1 '' data.file
DEBUG: Loading USB quirks from "/usr/share/cups/usb".
DEBUG: Loaded 159 quirks.
DEBUG: Printing on printer with URI: usb://Brother/PJ-773?serial=?
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
...
```
- Setting a job timeout policy or stopping the job by hand are not options
- for us. We can have job that take up to an hour to complete.
+ Setting a work timeout policy or manually stopping work are not options
+ for us. We may have jobs that take up to an hour to complete.
** Description changed:
USB backend never ends if the printer is not connected. We have been
able to identify a infinity loop in print_device function in usb-
libusb.c file:
```
fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
while ((g.printer = find_device(print_cb, uri)) == NULL)
{
_cupsLangPrintFilter(stderr, "INFO",
_("Waiting for printer to become available."));
sleep(5);
}
```
It's also easy to test by invoking the backend by hand:
```
# export DEVICE_URI='usb://Printer/Model?serial=?'
# /usr/lib/cups/backend/usb 0 root title 1 '' data.file
DEBUG: Loading USB quirks from "/usr/share/cups/usb".
DEBUG: Loaded 159 quirks.
- DEBUG: Printing on printer with URI: usb://Brother/PJ-773?serial=?
+ DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
...
```
Setting a work timeout policy or manually stopping work are not options
for us. We may have jobs that take up to an hour to complete.
** Description changed:
USB backend never ends if the printer is not connected. We have been
able to identify a infinity loop in print_device function in usb-
libusb.c file:
```
fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
while ((g.printer = find_device(print_cb, uri)) == NULL)
{
_cupsLangPrintFilter(stderr, "INFO",
_("Waiting for printer to become available."));
sleep(5);
}
```
It's also easy to test by invoking the backend by hand:
```
# export DEVICE_URI='usb://Printer/Model?serial=?'
# /usr/lib/cups/backend/usb 0 root title 1 '' data.file
DEBUG: Loading USB quirks from "/usr/share/cups/usb".
DEBUG: Loaded 159 quirks.
DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
-
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
...
```
- Setting a work timeout policy or manually stopping work are not options
+ Setting a job timeout policy or manually stopping work are not options
for us. We may have jobs that take up to an hour to complete.
** Description changed:
USB backend never ends if the printer is not connected. We have been
able to identify a infinity loop in print_device function in usb-
libusb.c file:
```
fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
while
[Desktop-packages] [Bug 1890569] Re: javaldx: Could not find a Java Runtime Environment! Please ensure that a JVM and the package libreoffice-java-common is installed.
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1890569 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1890569 Title: javaldx: Could not find a Java Runtime Environment! Please ensure that a JVM and the package libreoffice-java-common is installed. Status in libreoffice package in Ubuntu: New Bug description: Steps to reproduce: 1. Boot Ubuntu 20.10 daily ISO 2. Launch libreoffice-calc from its desktop file 3. Monitor the output of error-log by `tail -f ~/.xsession-errors` Expected results: * error log is empty Actual results: * error log contains lines: ``` javaldx: Could not find a Java Runtime Environment! Please ensure that a JVM and the package libreoffice-java-common is installed. If it is already installed then try removing ~/.config/libreoffice/4/user/config/javasettings_Linux_*.xml Warning: failed to read path from javaldx ``` Note: also happens for Draw, Impress, Math, StartCenter, Writer, xsltfilter. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libreoffice-calc 1:6.4.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu43 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.452 CurrentDesktop: MATE Date: Thu Aug 6 10:10:47 2020 LiveMediaBuild: Ubuntu-MATE 20.10 "Groovy Gorilla" - Alpha amd64 (20200806) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1890569/+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 1890569] Re: javaldx: Could not find a Java Runtime Environment! Please ensure that a JVM and the package libreoffice-java-common is installed.
** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1890569 Title: javaldx: Could not find a Java Runtime Environment! Please ensure that a JVM and the package libreoffice-java-common is installed. Status in libreoffice package in Ubuntu: New Bug description: Steps to reproduce: 1. Boot Ubuntu 20.10 daily ISO 2. Launch libreoffice-calc from its desktop file 3. Monitor the output of error-log by `tail -f ~/.xsession-errors` Expected results: * error log is empty Actual results: * error log contains lines: ``` javaldx: Could not find a Java Runtime Environment! Please ensure that a JVM and the package libreoffice-java-common is installed. If it is already installed then try removing ~/.config/libreoffice/4/user/config/javasettings_Linux_*.xml Warning: failed to read path from javaldx ``` Note: also happens for Draw, Impress, Math, StartCenter, Writer, xsltfilter. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libreoffice-calc 1:6.4.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu43 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.452 CurrentDesktop: MATE Date: Thu Aug 6 10:10:47 2020 LiveMediaBuild: Ubuntu-MATE 20.10 "Groovy Gorilla" - Alpha amd64 (20200806) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1890569/+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 1890572] [NEW] USB backend never ends if the printer is not connected
Public bug reported:
USB backend never ends if the printer is not connected. we have been
able to identify a infinity loop in print_device function in usb-
libusb.c file:
```
fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
while ((g.printer = find_device(print_cb, uri)) == NULL)
{
_cupsLangPrintFilter(stderr, "INFO",
_("Waiting for printer to become available."));
sleep(5);
}
```
It's also easy to test by invoking the backend by hand:
```
# export DEVICE_URI='usb://Printer/Model?serial=?'
# /usr/lib/cups/backend/usb 0 root title 1 '' data.file
DEBUG: Loading USB quirks from "/usr/share/cups/usb".
DEBUG: Loaded 159 quirks.
DEBUG: Printing on printer with URI: usb://Brother/PJ-773?serial=?
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
...
```
Setting a job timeout policy or stopping the job by hand are not options
for us. We can have job that take up to an hour to complete.
** Affects: cups (Ubuntu)
Importance: Undecided
Status: New
--
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/1890572
Title:
USB backend never ends if the printer is not connected
Status in cups package in Ubuntu:
New
Bug description:
USB backend never ends if the printer is not connected. we have been
able to identify a infinity loop in print_device function in usb-
libusb.c file:
```
fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
while ((g.printer = find_device(print_cb, uri)) == NULL)
{
_cupsLangPrintFilter(stderr, "INFO",
_("Waiting for printer to become available."));
sleep(5);
}
```
It's also easy to test by invoking the backend by hand:
```
# export DEVICE_URI='usb://Printer/Model?serial=?'
# /usr/lib/cups/backend/usb 0 root title 1 '' data.file
DEBUG: Loading USB quirks from "/usr/share/cups/usb".
DEBUG: Loaded 159 quirks.
DEBUG: Printing on printer with URI: usb://Brother/PJ-773?serial=?
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
...
```
Setting a job timeout policy or stopping the job by hand are not
options for us. We can have job that take up to an hour to complete.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1890572/+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 1847712] Re: Desktop icons vanishing when in Activities Overview is jarring and looks ugly
New fix proposed in: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1395 -- 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/1847712 Title: Desktop icons vanishing when in Activities Overview is jarring and looks ugly Status in gnome-shell package in Ubuntu: In Progress Bug description: Desktop icons vanishing and reappearing when in Activities Overview is jarring and looks ugly. Suggestions: * Don't hide them in AO, because they will be well shaded anyway; or * Fade them out and in smoothly. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-desktop-icons 19.01.4-1 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Fri Oct 11 14:24:42 2019 InstallationDate: Installed on 2019-05-02 (162 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847712/+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 1890569] [NEW] javaldx: Could not find a Java Runtime Environment! Please ensure that a JVM and the package libreoffice-java-common is installed.
Public bug reported: Steps to reproduce: 1. Boot Ubuntu 20.10 daily ISO 2. Launch libreoffice-calc from its desktop file 3. Monitor the output of error-log by `tail -f ~/.xsession-errors` Expected results: * error log is empty Actual results: * error log contains lines: ``` javaldx: Could not find a Java Runtime Environment! Please ensure that a JVM and the package libreoffice-java-common is installed. If it is already installed then try removing ~/.config/libreoffice/4/user/config/javasettings_Linux_*.xml Warning: failed to read path from javaldx ``` Note: also happens for Draw, Impress, Math, StartCenter, Writer, xsltfilter. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libreoffice-calc 1:6.4.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu43 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.452 CurrentDesktop: MATE Date: Thu Aug 6 10:10:47 2020 LiveMediaBuild: Ubuntu-MATE 20.10 "Groovy Gorilla" - Alpha amd64 (20200806) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (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 libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1890569 Title: javaldx: Could not find a Java Runtime Environment! Please ensure that a JVM and the package libreoffice-java-common is installed. Status in libreoffice package in Ubuntu: New Bug description: Steps to reproduce: 1. Boot Ubuntu 20.10 daily ISO 2. Launch libreoffice-calc from its desktop file 3. Monitor the output of error-log by `tail -f ~/.xsession-errors` Expected results: * error log is empty Actual results: * error log contains lines: ``` javaldx: Could not find a Java Runtime Environment! Please ensure that a JVM and the package libreoffice-java-common is installed. If it is already installed then try removing ~/.config/libreoffice/4/user/config/javasettings_Linux_*.xml Warning: failed to read path from javaldx ``` Note: also happens for Draw, Impress, Math, StartCenter, Writer, xsltfilter. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libreoffice-calc 1:6.4.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu43 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.452 CurrentDesktop: MATE Date: Thu Aug 6 10:10:47 2020 LiveMediaBuild: Ubuntu-MATE 20.10 "Groovy Gorilla" - Alpha amd64 (20200806) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1890569/+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 1890411] Re: [bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
^^^
That is bug 1890563 but that's a different issue to this one.
Although it's likely both issues are fixed in Ubuntu 20.04 already.
Certainly bug 1890563 is.
--
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/1890411
Title:
[bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
Status in mesa package in Ubuntu:
New
Status in xorg-server package in Ubuntu:
New
Bug description:
When ubuntu starts up, gdm3 does not start due to a crash in the the
xserver:
[ 1271.342] (II) SELinux: Disabled on system
[ 1271.346] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 1271.346] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[ 1271.346] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 1271.346] (II) AIGLX: enabled GLX_SGI_swap_control
[ 1271.346] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 1271.346] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 1271.346] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[ 1271.346] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[ 1271.346] (II) AIGLX: Loaded and initialized i965
[ 1271.346] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 1271.348] (II) modeset(0): Damage tracking initialized
[ 1271.348] (II) modeset(0): Setting screen physical size to 508 x 317
[ 1271.352] (EE)
[ 1271.352] (EE) Backtrace:
[ 1271.352] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5649b579bacd]
[ 1271.352] (EE) 1: /usr/lib/xorg/Xorg (0x5649b55e3000+0x1bc869)
[0x5649b579f869]
[ 1271.352] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f5c7d0a5000+0x128a0) [0x7f5c7d0b78a0]
[ 1271.352] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x8e8652) [0x7f5c784e2652]
[ 1271.352] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x8e877f) [0x7f5c784e277f]
[ 1271.352] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x122916) [0x7f5c77d1c916]
[ 1271.352] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x1189bc) [0x7f5c77d129bc]
[ 1271.352] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x109c1b) [0x7f5c77d03c1b]
[ 1271.352] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x279558) [0x7f5c77e73558]
[ 1271.352] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x2796e3) [0x7f5c77e736e3]
[ 1271.352] (EE) 10: /usr/lib/xorg/modules/libglamoregl.so
(0x7f5c79937000+0x1a1ab) [0x7f5c799511ab]
[ 1271.352] (EE) 11: /usr/lib/xorg/Xorg (0x5649b55e3000+0x13ed03)
[0x5649b5721d03]
[ 1271.352] (EE) 12: /usr/lib/xorg/Xorg (miPaintWindow+0x22f)
[0x5649b577fd1f]
[ 1271.352] (EE) 13: /usr/lib/xorg/Xorg (miWindowExposures+0x112)
[0x5649b577fa62]
[ 1271.352] (EE) 14: /usr/lib/xorg/Xorg (0x5649b55e3000+0xa9c41)
[0x5649b568cc41]
[ 1271.352] (EE) 15: /usr/lib/xorg/Xorg (MapWindow+0x114) [0x5649b5665d04]
[ 1271.352] (EE) 16: /usr/lib/xorg/Xorg (0x5649b55e3000+0x56e79)
[0x5649b5639e79]
[ 1271.352] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xe7) [0x7f5c7ccd5b97]
[ 1271.352] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x5649b5623b8a]
[ 1271.352] (EE)
[ 1271.352] (EE) Segmentation fault at address 0x4
[ 1271.352] (EE)
Fatal server error:
[ 1271.352] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 1271.352] (EE)
[ 1271.352] (EE)
As i965_dri.so is part of the libgl-mesa-dri package I downgraded this
specific package from version 20.0.8-0ubuntu1~18.04.1 back to
19.2.8-0ubuntu0~18.04.3.
This solves the problem. So I suspect that the problem is in this
specific package.
My machine is (uname):
4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64
x86_64 GNU/Linux
(lspci)
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller
(rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen
Core Processor Integrated Graphics Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series
Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High
Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI
Express Root Port #1 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI
Express Root Port #3 (rev d5)
00:1d.0 USB
[Desktop-packages] [Bug 1890563] Re: gdm3 crashed with SIGTRAP in g_wakeup_new() from g_main_context_new() from g_dbus_connection_call_sync_internal() from g_dbus_connection_call_sync_internal() from
Since there are no reports of this in 20.04 and later we can consider it fixed. ** Summary changed: - /usr/sbin/gdm3:5:g_wakeup_new:g_main_context_new:g_dbus_connection_call_sync_internal:g_dbus_connection_call_sync_internal:initable_init + gdm3 crashed with SIGTRAP in g_wakeup_new() from g_main_context_new() from g_dbus_connection_call_sync_internal() from g_dbus_connection_call_sync_internal() from initable_init() ** Changed in: gdm3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1890563 Title: gdm3 crashed with SIGTRAP in g_wakeup_new() from g_main_context_new() from g_dbus_connection_call_sync_internal() from g_dbus_connection_call_sync_internal() from initable_init() Status in gdm3 package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdm3. This problem was most recently seen with package version 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7, the problem page at https://errors.ubuntu.com/problem/c3d0de92d9e79e008d0c1b41577c3d938c7f42cd contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1890563/+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 1890436] Re: VGA signal is ghosted and stretched (Intel® HD Graphics 2500)
It might be that there's some minor damage to the VGA port on the machine. It might be so minor you can't even see 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/1890436 Title: VGA signal is ghosted and stretched (Intel® HD Graphics 2500) Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello, last week I was digging in the BIOS of my PC at work since I tried to see if there is a way to update the dbx for secure boot. Since there was no option to perform this task, I modified some settings. In detail, I disabled CSM in BIOS and that's when hell broke loose! To get an idea about the hardware, the Lenovo machine isn't running the latest BIOS as its updater is broken and won't update it within win or its ISO image. It uses the previous version released by its manufacturer. The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled the DP monitor is lit first and then the VGA one prior OS loading. When CSM is disabled it goes the other way around. The VGA monitor is lit and the DP one opens up during OS load. With CSM disabled the VGA monitor is the primary one and it is corrupted as you can see on the pictures I have attached. Interestingly printing screens within Ubuntu does not capture the corruption problem I am getting as you can see on the pictures I have also attached. Neither X log contains anything useful. The issue is repeatable on every boot. As I have seen on other bug reports, I have enabled DRM debug, captured the dmesg using a huge buffer to get it and have uploaded it as well. I hope that it will help you track this issue down and fix it soon. Since I will be away some days for vacation, I will have physical access to it till this Friday and will get back to work at the 24th of August. In the mean time, I hope that someone will pinpoint the root cause of it and prepare a patch. Since this machine is running w10 2004, it should be noted that in win I do not get any corruption at all either in CSM mode or UEFI mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CasperVersion: 1.445 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 11:30:51 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 3209C54 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT9BAUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3209C54 dmi.product.sku: LENOVO_MT_3209 dmi.product.version: ThinkCentre M92p 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/ubuntu/+source/linux/+bug/1890436/+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 1890563] [NEW] gdm3 crashed with SIGTRAP in g_wakeup_new() from g_main_context_new() from g_dbus_connection_call_sync_internal() from g_dbus_connection_call_sync_internal() fro
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdm3. This problem was most recently seen with package version 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7, the problem page at https://errors.ubuntu.com/problem/c3d0de92d9e79e008d0c1b41577c3d938c7f42cd contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: Fix Released ** Tags: bionic eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1890563 Title: gdm3 crashed with SIGTRAP in g_wakeup_new() from g_main_context_new() from g_dbus_connection_call_sync_internal() from g_dbus_connection_call_sync_internal() from initable_init() Status in gdm3 package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdm3. This problem was most recently seen with package version 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7, the problem page at https://errors.ubuntu.com/problem/c3d0de92d9e79e008d0c1b41577c3d938c7f42cd contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1890563/+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 1890436] Re: VGA image is ghosted and stretched
"corruption" to me would mean a problem in graphics memory. That's not what I am seeing in your photos. Your photos seem to show the graphics memory fully intact and some kind of analog VGA signalling problem. Which unfortunately means the Linux kernel might not be aware of the problem. Still, as a workaround please try selecting 'Ubuntu on Wayland' from the login screen. ** Summary changed: - VGA image is ghosted and stretched (LG L1953S) + VGA image is ghosted and stretched ** Summary changed: - VGA image is ghosted and stretched + VGA signal is ghosted and stretched (Intel® HD Graphics 2500) -- 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/1890436 Title: VGA signal is ghosted and stretched (Intel® HD Graphics 2500) Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello, last week I was digging in the BIOS of my PC at work since I tried to see if there is a way to update the dbx for secure boot. Since there was no option to perform this task, I modified some settings. In detail, I disabled CSM in BIOS and that's when hell broke loose! To get an idea about the hardware, the Lenovo machine isn't running the latest BIOS as its updater is broken and won't update it within win or its ISO image. It uses the previous version released by its manufacturer. The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled the DP monitor is lit first and then the VGA one prior OS loading. When CSM is disabled it goes the other way around. The VGA monitor is lit and the DP one opens up during OS load. With CSM disabled the VGA monitor is the primary one and it is corrupted as you can see on the pictures I have attached. Interestingly printing screens within Ubuntu does not capture the corruption problem I am getting as you can see on the pictures I have also attached. Neither X log contains anything useful. The issue is repeatable on every boot. As I have seen on other bug reports, I have enabled DRM debug, captured the dmesg using a huge buffer to get it and have uploaded it as well. I hope that it will help you track this issue down and fix it soon. Since I will be away some days for vacation, I will have physical access to it till this Friday and will get back to work at the 24th of August. In the mean time, I hope that someone will pinpoint the root cause of it and prepare a patch. Since this machine is running w10 2004, it should be noted that in win I do not get any corruption at all either in CSM mode or UEFI mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CasperVersion: 1.445 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 11:30:51 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 3209C54 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT9BAUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3209C54 dmi.product.sku: LENOVO_MT_3209 dmi.product.version: ThinkCentre M92p 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:
[Desktop-packages] [Bug 1890411] Re: [bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
I just added the crash report of gdm3: https://errors.ubuntu.com/oops
/1e6d888a-d7c5-11ea-ae81-fa163ee63de6
--
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/1890411
Title:
[bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
Status in mesa package in Ubuntu:
New
Status in xorg-server package in Ubuntu:
New
Bug description:
When ubuntu starts up, gdm3 does not start due to a crash in the the
xserver:
[ 1271.342] (II) SELinux: Disabled on system
[ 1271.346] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 1271.346] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[ 1271.346] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 1271.346] (II) AIGLX: enabled GLX_SGI_swap_control
[ 1271.346] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 1271.346] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 1271.346] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[ 1271.346] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[ 1271.346] (II) AIGLX: Loaded and initialized i965
[ 1271.346] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 1271.348] (II) modeset(0): Damage tracking initialized
[ 1271.348] (II) modeset(0): Setting screen physical size to 508 x 317
[ 1271.352] (EE)
[ 1271.352] (EE) Backtrace:
[ 1271.352] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5649b579bacd]
[ 1271.352] (EE) 1: /usr/lib/xorg/Xorg (0x5649b55e3000+0x1bc869)
[0x5649b579f869]
[ 1271.352] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f5c7d0a5000+0x128a0) [0x7f5c7d0b78a0]
[ 1271.352] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x8e8652) [0x7f5c784e2652]
[ 1271.352] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x8e877f) [0x7f5c784e277f]
[ 1271.352] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x122916) [0x7f5c77d1c916]
[ 1271.352] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x1189bc) [0x7f5c77d129bc]
[ 1271.352] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x109c1b) [0x7f5c77d03c1b]
[ 1271.352] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x279558) [0x7f5c77e73558]
[ 1271.352] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x2796e3) [0x7f5c77e736e3]
[ 1271.352] (EE) 10: /usr/lib/xorg/modules/libglamoregl.so
(0x7f5c79937000+0x1a1ab) [0x7f5c799511ab]
[ 1271.352] (EE) 11: /usr/lib/xorg/Xorg (0x5649b55e3000+0x13ed03)
[0x5649b5721d03]
[ 1271.352] (EE) 12: /usr/lib/xorg/Xorg (miPaintWindow+0x22f)
[0x5649b577fd1f]
[ 1271.352] (EE) 13: /usr/lib/xorg/Xorg (miWindowExposures+0x112)
[0x5649b577fa62]
[ 1271.352] (EE) 14: /usr/lib/xorg/Xorg (0x5649b55e3000+0xa9c41)
[0x5649b568cc41]
[ 1271.352] (EE) 15: /usr/lib/xorg/Xorg (MapWindow+0x114) [0x5649b5665d04]
[ 1271.352] (EE) 16: /usr/lib/xorg/Xorg (0x5649b55e3000+0x56e79)
[0x5649b5639e79]
[ 1271.352] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xe7) [0x7f5c7ccd5b97]
[ 1271.352] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x5649b5623b8a]
[ 1271.352] (EE)
[ 1271.352] (EE) Segmentation fault at address 0x4
[ 1271.352] (EE)
Fatal server error:
[ 1271.352] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 1271.352] (EE)
[ 1271.352] (EE)
As i965_dri.so is part of the libgl-mesa-dri package I downgraded this
specific package from version 20.0.8-0ubuntu1~18.04.1 back to
19.2.8-0ubuntu0~18.04.3.
This solves the problem. So I suspect that the problem is in this
specific package.
My machine is (uname):
4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64
x86_64 GNU/Linux
(lspci)
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller
(rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen
Core Processor Integrated Graphics Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series
Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High
Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI
Express Root Port #1 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI
Express Root Port #3 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
[Desktop-packages] [Bug 1890411] Re: Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
Thanks. That's the right crash report but unfortunately it doesn't offer
any new information :(
** Changed in: mesa (Ubuntu)
Status: Incomplete => New
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => New
** Summary changed:
- Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
+ [bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
--
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/1890411
Title:
[bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
Status in mesa package in Ubuntu:
New
Status in xorg-server package in Ubuntu:
New
Bug description:
When ubuntu starts up, gdm3 does not start due to a crash in the the
xserver:
[ 1271.342] (II) SELinux: Disabled on system
[ 1271.346] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 1271.346] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[ 1271.346] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 1271.346] (II) AIGLX: enabled GLX_SGI_swap_control
[ 1271.346] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 1271.346] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 1271.346] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[ 1271.346] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[ 1271.346] (II) AIGLX: Loaded and initialized i965
[ 1271.346] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 1271.348] (II) modeset(0): Damage tracking initialized
[ 1271.348] (II) modeset(0): Setting screen physical size to 508 x 317
[ 1271.352] (EE)
[ 1271.352] (EE) Backtrace:
[ 1271.352] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5649b579bacd]
[ 1271.352] (EE) 1: /usr/lib/xorg/Xorg (0x5649b55e3000+0x1bc869)
[0x5649b579f869]
[ 1271.352] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f5c7d0a5000+0x128a0) [0x7f5c7d0b78a0]
[ 1271.352] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x8e8652) [0x7f5c784e2652]
[ 1271.352] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x8e877f) [0x7f5c784e277f]
[ 1271.352] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x122916) [0x7f5c77d1c916]
[ 1271.352] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x1189bc) [0x7f5c77d129bc]
[ 1271.352] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x109c1b) [0x7f5c77d03c1b]
[ 1271.352] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x279558) [0x7f5c77e73558]
[ 1271.352] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x2796e3) [0x7f5c77e736e3]
[ 1271.352] (EE) 10: /usr/lib/xorg/modules/libglamoregl.so
(0x7f5c79937000+0x1a1ab) [0x7f5c799511ab]
[ 1271.352] (EE) 11: /usr/lib/xorg/Xorg (0x5649b55e3000+0x13ed03)
[0x5649b5721d03]
[ 1271.352] (EE) 12: /usr/lib/xorg/Xorg (miPaintWindow+0x22f)
[0x5649b577fd1f]
[ 1271.352] (EE) 13: /usr/lib/xorg/Xorg (miWindowExposures+0x112)
[0x5649b577fa62]
[ 1271.352] (EE) 14: /usr/lib/xorg/Xorg (0x5649b55e3000+0xa9c41)
[0x5649b568cc41]
[ 1271.352] (EE) 15: /usr/lib/xorg/Xorg (MapWindow+0x114) [0x5649b5665d04]
[ 1271.352] (EE) 16: /usr/lib/xorg/Xorg (0x5649b55e3000+0x56e79)
[0x5649b5639e79]
[ 1271.352] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xe7) [0x7f5c7ccd5b97]
[ 1271.352] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x5649b5623b8a]
[ 1271.352] (EE)
[ 1271.352] (EE) Segmentation fault at address 0x4
[ 1271.352] (EE)
Fatal server error:
[ 1271.352] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 1271.352] (EE)
[ 1271.352] (EE)
As i965_dri.so is part of the libgl-mesa-dri package I downgraded this
specific package from version 20.0.8-0ubuntu1~18.04.1 back to
19.2.8-0ubuntu0~18.04.3.
This solves the problem. So I suspect that the problem is in this
specific package.
My machine is (uname):
4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64
x86_64 GNU/Linux
(lspci)
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller
(rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen
Core Processor Integrated Graphics Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series
Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High
Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel
[Desktop-packages] [Bug 1890436] Re: VGA image is ghosted and stretched (LG L1953S)
** Attachment added: "Cursor corruption at VGA#2(same seen at VGA#1)" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890436/+attachment/5399180/+files/new-VGA-cursor-29.jpg -- 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/1890436 Title: VGA image is ghosted and stretched (LG L1953S) Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello, last week I was digging in the BIOS of my PC at work since I tried to see if there is a way to update the dbx for secure boot. Since there was no option to perform this task, I modified some settings. In detail, I disabled CSM in BIOS and that's when hell broke loose! To get an idea about the hardware, the Lenovo machine isn't running the latest BIOS as its updater is broken and won't update it within win or its ISO image. It uses the previous version released by its manufacturer. The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled the DP monitor is lit first and then the VGA one prior OS loading. When CSM is disabled it goes the other way around. The VGA monitor is lit and the DP one opens up during OS load. With CSM disabled the VGA monitor is the primary one and it is corrupted as you can see on the pictures I have attached. Interestingly printing screens within Ubuntu does not capture the corruption problem I am getting as you can see on the pictures I have also attached. Neither X log contains anything useful. The issue is repeatable on every boot. As I have seen on other bug reports, I have enabled DRM debug, captured the dmesg using a huge buffer to get it and have uploaded it as well. I hope that it will help you track this issue down and fix it soon. Since I will be away some days for vacation, I will have physical access to it till this Friday and will get back to work at the 24th of August. In the mean time, I hope that someone will pinpoint the root cause of it and prepare a patch. Since this machine is running w10 2004, it should be noted that in win I do not get any corruption at all either in CSM mode or UEFI mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CasperVersion: 1.445 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 11:30:51 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 3209C54 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT9BAUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3209C54 dmi.product.sku: LENOVO_MT_3209 dmi.product.version: ThinkCentre M92p 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/ubuntu/+source/linux/+bug/1890436/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1890436] Re: VGA image is ghosted and stretched (LG L1953S)
** Attachment added: "Normal font display at DP" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890436/+attachment/5399173/+files/good-DP-01b.jpg -- 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/1890436 Title: VGA image is ghosted and stretched (LG L1953S) Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello, last week I was digging in the BIOS of my PC at work since I tried to see if there is a way to update the dbx for secure boot. Since there was no option to perform this task, I modified some settings. In detail, I disabled CSM in BIOS and that's when hell broke loose! To get an idea about the hardware, the Lenovo machine isn't running the latest BIOS as its updater is broken and won't update it within win or its ISO image. It uses the previous version released by its manufacturer. The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled the DP monitor is lit first and then the VGA one prior OS loading. When CSM is disabled it goes the other way around. The VGA monitor is lit and the DP one opens up during OS load. With CSM disabled the VGA monitor is the primary one and it is corrupted as you can see on the pictures I have attached. Interestingly printing screens within Ubuntu does not capture the corruption problem I am getting as you can see on the pictures I have also attached. Neither X log contains anything useful. The issue is repeatable on every boot. As I have seen on other bug reports, I have enabled DRM debug, captured the dmesg using a huge buffer to get it and have uploaded it as well. I hope that it will help you track this issue down and fix it soon. Since I will be away some days for vacation, I will have physical access to it till this Friday and will get back to work at the 24th of August. In the mean time, I hope that someone will pinpoint the root cause of it and prepare a patch. Since this machine is running w10 2004, it should be noted that in win I do not get any corruption at all either in CSM mode or UEFI mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CasperVersion: 1.445 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 11:30:51 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 3209C54 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT9BAUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3209C54 dmi.product.sku: LENOVO_MT_3209 dmi.product.version: ThinkCentre M92p 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/ubuntu/+source/linux/+bug/1890436/+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 1890436] Re: VGA image is ghosted and stretched (LG L1953S)
** Attachment added: "Corruption of welcoming screen at VGA#2" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890436/+attachment/5399179/+files/new-VGA-50.jpg -- 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/1890436 Title: VGA image is ghosted and stretched (LG L1953S) Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello, last week I was digging in the BIOS of my PC at work since I tried to see if there is a way to update the dbx for secure boot. Since there was no option to perform this task, I modified some settings. In detail, I disabled CSM in BIOS and that's when hell broke loose! To get an idea about the hardware, the Lenovo machine isn't running the latest BIOS as its updater is broken and won't update it within win or its ISO image. It uses the previous version released by its manufacturer. The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled the DP monitor is lit first and then the VGA one prior OS loading. When CSM is disabled it goes the other way around. The VGA monitor is lit and the DP one opens up during OS load. With CSM disabled the VGA monitor is the primary one and it is corrupted as you can see on the pictures I have attached. Interestingly printing screens within Ubuntu does not capture the corruption problem I am getting as you can see on the pictures I have also attached. Neither X log contains anything useful. The issue is repeatable on every boot. As I have seen on other bug reports, I have enabled DRM debug, captured the dmesg using a huge buffer to get it and have uploaded it as well. I hope that it will help you track this issue down and fix it soon. Since I will be away some days for vacation, I will have physical access to it till this Friday and will get back to work at the 24th of August. In the mean time, I hope that someone will pinpoint the root cause of it and prepare a patch. Since this machine is running w10 2004, it should be noted that in win I do not get any corruption at all either in CSM mode or UEFI mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CasperVersion: 1.445 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 11:30:51 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 3209C54 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT9BAUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3209C54 dmi.product.sku: LENOVO_MT_3209 dmi.product.version: ThinkCentre M92p 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/ubuntu/+source/linux/+bug/1890436/+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 1890436] Re: VGA image is ghosted and stretched (LG L1953S)
** Attachment added: "Corruption of home folder at VGA#2" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890436/+attachment/5399178/+files/new-VGA-16.jpg -- 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/1890436 Title: VGA image is ghosted and stretched (LG L1953S) Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello, last week I was digging in the BIOS of my PC at work since I tried to see if there is a way to update the dbx for secure boot. Since there was no option to perform this task, I modified some settings. In detail, I disabled CSM in BIOS and that's when hell broke loose! To get an idea about the hardware, the Lenovo machine isn't running the latest BIOS as its updater is broken and won't update it within win or its ISO image. It uses the previous version released by its manufacturer. The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled the DP monitor is lit first and then the VGA one prior OS loading. When CSM is disabled it goes the other way around. The VGA monitor is lit and the DP one opens up during OS load. With CSM disabled the VGA monitor is the primary one and it is corrupted as you can see on the pictures I have attached. Interestingly printing screens within Ubuntu does not capture the corruption problem I am getting as you can see on the pictures I have also attached. Neither X log contains anything useful. The issue is repeatable on every boot. As I have seen on other bug reports, I have enabled DRM debug, captured the dmesg using a huge buffer to get it and have uploaded it as well. I hope that it will help you track this issue down and fix it soon. Since I will be away some days for vacation, I will have physical access to it till this Friday and will get back to work at the 24th of August. In the mean time, I hope that someone will pinpoint the root cause of it and prepare a patch. Since this machine is running w10 2004, it should be noted that in win I do not get any corruption at all either in CSM mode or UEFI mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CasperVersion: 1.445 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 11:30:51 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 3209C54 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT9BAUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3209C54 dmi.product.sku: LENOVO_MT_3209 dmi.product.version: ThinkCentre M92p 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/ubuntu/+source/linux/+bug/1890436/+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 1890436] Re: VGA image is ghosted and stretched (LG L1953S)
** Attachment added: "X log with DP and VGA#2 monitors" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890436/+attachment/5399181/+files/Xorg.log -- 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/1890436 Title: VGA image is ghosted and stretched (LG L1953S) Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello, last week I was digging in the BIOS of my PC at work since I tried to see if there is a way to update the dbx for secure boot. Since there was no option to perform this task, I modified some settings. In detail, I disabled CSM in BIOS and that's when hell broke loose! To get an idea about the hardware, the Lenovo machine isn't running the latest BIOS as its updater is broken and won't update it within win or its ISO image. It uses the previous version released by its manufacturer. The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled the DP monitor is lit first and then the VGA one prior OS loading. When CSM is disabled it goes the other way around. The VGA monitor is lit and the DP one opens up during OS load. With CSM disabled the VGA monitor is the primary one and it is corrupted as you can see on the pictures I have attached. Interestingly printing screens within Ubuntu does not capture the corruption problem I am getting as you can see on the pictures I have also attached. Neither X log contains anything useful. The issue is repeatable on every boot. As I have seen on other bug reports, I have enabled DRM debug, captured the dmesg using a huge buffer to get it and have uploaded it as well. I hope that it will help you track this issue down and fix it soon. Since I will be away some days for vacation, I will have physical access to it till this Friday and will get back to work at the 24th of August. In the mean time, I hope that someone will pinpoint the root cause of it and prepare a patch. Since this machine is running w10 2004, it should be noted that in win I do not get any corruption at all either in CSM mode or UEFI mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CasperVersion: 1.445 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 11:30:51 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 3209C54 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT9BAUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3209C54 dmi.product.sku: LENOVO_MT_3209 dmi.product.version: ThinkCentre M92p 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/ubuntu/+source/linux/+bug/1890436/+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 1890436] Re: VGA image is ghosted and stretched (LG L1953S)
** Attachment added: "Corrupted font display at VGA#1" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890436/+attachment/5399175/+files/bad-VGA-22b.jpg -- 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/1890436 Title: VGA image is ghosted and stretched (LG L1953S) Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello, last week I was digging in the BIOS of my PC at work since I tried to see if there is a way to update the dbx for secure boot. Since there was no option to perform this task, I modified some settings. In detail, I disabled CSM in BIOS and that's when hell broke loose! To get an idea about the hardware, the Lenovo machine isn't running the latest BIOS as its updater is broken and won't update it within win or its ISO image. It uses the previous version released by its manufacturer. The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled the DP monitor is lit first and then the VGA one prior OS loading. When CSM is disabled it goes the other way around. The VGA monitor is lit and the DP one opens up during OS load. With CSM disabled the VGA monitor is the primary one and it is corrupted as you can see on the pictures I have attached. Interestingly printing screens within Ubuntu does not capture the corruption problem I am getting as you can see on the pictures I have also attached. Neither X log contains anything useful. The issue is repeatable on every boot. As I have seen on other bug reports, I have enabled DRM debug, captured the dmesg using a huge buffer to get it and have uploaded it as well. I hope that it will help you track this issue down and fix it soon. Since I will be away some days for vacation, I will have physical access to it till this Friday and will get back to work at the 24th of August. In the mean time, I hope that someone will pinpoint the root cause of it and prepare a patch. Since this machine is running w10 2004, it should be noted that in win I do not get any corruption at all either in CSM mode or UEFI mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CasperVersion: 1.445 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 11:30:51 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 3209C54 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT9BAUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3209C54 dmi.product.sku: LENOVO_MT_3209 dmi.product.version: ThinkCentre M92p 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/ubuntu/+source/linux/+bug/1890436/+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 1890436] Re: VGA image is ghosted and stretched (LG L1953S)
** Attachment added: "Corrupted font display at VGA#2" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890436/+attachment/5399176/+files/bad-VGA-48b.jpg -- 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/1890436 Title: VGA image is ghosted and stretched (LG L1953S) Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello, last week I was digging in the BIOS of my PC at work since I tried to see if there is a way to update the dbx for secure boot. Since there was no option to perform this task, I modified some settings. In detail, I disabled CSM in BIOS and that's when hell broke loose! To get an idea about the hardware, the Lenovo machine isn't running the latest BIOS as its updater is broken and won't update it within win or its ISO image. It uses the previous version released by its manufacturer. The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled the DP monitor is lit first and then the VGA one prior OS loading. When CSM is disabled it goes the other way around. The VGA monitor is lit and the DP one opens up during OS load. With CSM disabled the VGA monitor is the primary one and it is corrupted as you can see on the pictures I have attached. Interestingly printing screens within Ubuntu does not capture the corruption problem I am getting as you can see on the pictures I have also attached. Neither X log contains anything useful. The issue is repeatable on every boot. As I have seen on other bug reports, I have enabled DRM debug, captured the dmesg using a huge buffer to get it and have uploaded it as well. I hope that it will help you track this issue down and fix it soon. Since I will be away some days for vacation, I will have physical access to it till this Friday and will get back to work at the 24th of August. In the mean time, I hope that someone will pinpoint the root cause of it and prepare a patch. Since this machine is running w10 2004, it should be noted that in win I do not get any corruption at all either in CSM mode or UEFI mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CasperVersion: 1.445 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 11:30:51 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 3209C54 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT9BAUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3209C54 dmi.product.sku: LENOVO_MT_3209 dmi.product.version: ThinkCentre M92p 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/ubuntu/+source/linux/+bug/1890436/+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 1890436] Re: VGA image is ghosted and stretched (LG L1953S)
-- 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/1890436 Title: VGA image is ghosted and stretched (LG L1953S) Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello, last week I was digging in the BIOS of my PC at work since I tried to see if there is a way to update the dbx for secure boot. Since there was no option to perform this task, I modified some settings. In detail, I disabled CSM in BIOS and that's when hell broke loose! To get an idea about the hardware, the Lenovo machine isn't running the latest BIOS as its updater is broken and won't update it within win or its ISO image. It uses the previous version released by its manufacturer. The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled the DP monitor is lit first and then the VGA one prior OS loading. When CSM is disabled it goes the other way around. The VGA monitor is lit and the DP one opens up during OS load. With CSM disabled the VGA monitor is the primary one and it is corrupted as you can see on the pictures I have attached. Interestingly printing screens within Ubuntu does not capture the corruption problem I am getting as you can see on the pictures I have also attached. Neither X log contains anything useful. The issue is repeatable on every boot. As I have seen on other bug reports, I have enabled DRM debug, captured the dmesg using a huge buffer to get it and have uploaded it as well. I hope that it will help you track this issue down and fix it soon. Since I will be away some days for vacation, I will have physical access to it till this Friday and will get back to work at the 24th of August. In the mean time, I hope that someone will pinpoint the root cause of it and prepare a patch. Since this machine is running w10 2004, it should be noted that in win I do not get any corruption at all either in CSM mode or UEFI mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CasperVersion: 1.445 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 11:30:51 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 3209C54 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT9BAUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3209C54 dmi.product.sku: LENOVO_MT_3209 dmi.product.version: ThinkCentre M92p 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/ubuntu/+source/linux/+bug/1890436/+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 1890436] Re: VGA image is ghosted and stretched (LG L1953S)
Hello, thank you for your early reply! I am afraid that you haven't got the big picture here. On my side, there is no doubt that I am getting a visual corruption. Just take a look at the attached images. The video signal is good since the monitor works normal when I enable CSM setting in BIOS. As you have suggested, I used a different VGA cable having double thickness than the initial one and I am still getting the same behaviour. If it was a signalling issue the kernel would probably not print any warning messages. Since I have another VGA monitor on my desk, I went a step ahead and connected this VGA monitor instead since I hadn't tested this case with that monitor. As expected, I got exactly the same behaviour. That is smooth display on VGA monitor when CSM is enabled and corruption when CSM is disabled. As a proof of it, I am uploading images from the third monitor. Take a closer look at the cursor as it has blank lines after each horizontal line. As you can see, the same applies to fonts when switching to console view. I am also uploading the X log with that monitor. -- 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/1890436 Title: VGA image is ghosted and stretched (LG L1953S) Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello, last week I was digging in the BIOS of my PC at work since I tried to see if there is a way to update the dbx for secure boot. Since there was no option to perform this task, I modified some settings. In detail, I disabled CSM in BIOS and that's when hell broke loose! To get an idea about the hardware, the Lenovo machine isn't running the latest BIOS as its updater is broken and won't update it within win or its ISO image. It uses the previous version released by its manufacturer. The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled the DP monitor is lit first and then the VGA one prior OS loading. When CSM is disabled it goes the other way around. The VGA monitor is lit and the DP one opens up during OS load. With CSM disabled the VGA monitor is the primary one and it is corrupted as you can see on the pictures I have attached. Interestingly printing screens within Ubuntu does not capture the corruption problem I am getting as you can see on the pictures I have also attached. Neither X log contains anything useful. The issue is repeatable on every boot. As I have seen on other bug reports, I have enabled DRM debug, captured the dmesg using a huge buffer to get it and have uploaded it as well. I hope that it will help you track this issue down and fix it soon. Since I will be away some days for vacation, I will have physical access to it till this Friday and will get back to work at the 24th of August. In the mean time, I hope that someone will pinpoint the root cause of it and prepare a patch. Since this machine is running w10 2004, it should be noted that in win I do not get any corruption at all either in CSM mode or UEFI mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CasperVersion: 1.445 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 11:30:51 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 3209C54 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT9BAUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3209C54 dmi.product.sku: LENOVO_MT_3209 dmi.product.version:
[Desktop-packages] [Bug 1817480] Re: Emacs color-theme package is gone from version 40.1
** Changed in: emacs-goodies-el (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs-goodies-el in Ubuntu. https://bugs.launchpad.net/bugs/1817480 Title: Emacs color-theme package is gone from version 40.1 Status in emacs-goodies-el package in Ubuntu: Confirmed Bug description: It seems that color-theme and other packages are missing from between versions 40.1 and 36.3ubuntu1 which is breaking existing emacs customizations. Any chance these could be reverted back? or a different package could be provided? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs-goodies-el/+bug/1817480/+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 1890411] Re: Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
I followed step 1 and 2. I don't know how to get the ID. According to
step 2 the link to the crash report is https://errors.ubuntu.com/oops
/3d15afdc-d7b7-11ea-b244-fa163e983629
--
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/1890411
Title:
Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
Status in mesa package in Ubuntu:
Incomplete
Status in xorg-server package in Ubuntu:
Incomplete
Bug description:
When ubuntu starts up, gdm3 does not start due to a crash in the the
xserver:
[ 1271.342] (II) SELinux: Disabled on system
[ 1271.346] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 1271.346] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[ 1271.346] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 1271.346] (II) AIGLX: enabled GLX_SGI_swap_control
[ 1271.346] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 1271.346] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 1271.346] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[ 1271.346] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[ 1271.346] (II) AIGLX: Loaded and initialized i965
[ 1271.346] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 1271.348] (II) modeset(0): Damage tracking initialized
[ 1271.348] (II) modeset(0): Setting screen physical size to 508 x 317
[ 1271.352] (EE)
[ 1271.352] (EE) Backtrace:
[ 1271.352] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5649b579bacd]
[ 1271.352] (EE) 1: /usr/lib/xorg/Xorg (0x5649b55e3000+0x1bc869)
[0x5649b579f869]
[ 1271.352] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f5c7d0a5000+0x128a0) [0x7f5c7d0b78a0]
[ 1271.352] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x8e8652) [0x7f5c784e2652]
[ 1271.352] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x8e877f) [0x7f5c784e277f]
[ 1271.352] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x122916) [0x7f5c77d1c916]
[ 1271.352] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x1189bc) [0x7f5c77d129bc]
[ 1271.352] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x109c1b) [0x7f5c77d03c1b]
[ 1271.352] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x279558) [0x7f5c77e73558]
[ 1271.352] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x2796e3) [0x7f5c77e736e3]
[ 1271.352] (EE) 10: /usr/lib/xorg/modules/libglamoregl.so
(0x7f5c79937000+0x1a1ab) [0x7f5c799511ab]
[ 1271.352] (EE) 11: /usr/lib/xorg/Xorg (0x5649b55e3000+0x13ed03)
[0x5649b5721d03]
[ 1271.352] (EE) 12: /usr/lib/xorg/Xorg (miPaintWindow+0x22f)
[0x5649b577fd1f]
[ 1271.352] (EE) 13: /usr/lib/xorg/Xorg (miWindowExposures+0x112)
[0x5649b577fa62]
[ 1271.352] (EE) 14: /usr/lib/xorg/Xorg (0x5649b55e3000+0xa9c41)
[0x5649b568cc41]
[ 1271.352] (EE) 15: /usr/lib/xorg/Xorg (MapWindow+0x114) [0x5649b5665d04]
[ 1271.352] (EE) 16: /usr/lib/xorg/Xorg (0x5649b55e3000+0x56e79)
[0x5649b5639e79]
[ 1271.352] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xe7) [0x7f5c7ccd5b97]
[ 1271.352] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x5649b5623b8a]
[ 1271.352] (EE)
[ 1271.352] (EE) Segmentation fault at address 0x4
[ 1271.352] (EE)
Fatal server error:
[ 1271.352] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 1271.352] (EE)
[ 1271.352] (EE)
As i965_dri.so is part of the libgl-mesa-dri package I downgraded this
specific package from version 20.0.8-0ubuntu1~18.04.1 back to
19.2.8-0ubuntu0~18.04.3.
This solves the problem. So I suspect that the problem is in this
specific package.
My machine is (uname):
4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64
x86_64 GNU/Linux
(lspci)
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller
(rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen
Core Processor Integrated Graphics Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series
Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High
Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI
Express Root Port #1 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI
Express Root Port #3 (rev d5)
[Desktop-packages] [Bug 1860830] Re: Geolocation not working − the Google maps API always returns error codes
As pointed out by Evangelos in https://groups.google.com/a/chromium.org/g/chromium-packagers/c/ZytNtRam5II/m/4o9ql5IaAwAJ?pli=1, geolocation started working again on July 29th. Marking the bug fixed accordingly, let's hope this doesn't break unexpectedly again. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Released ** Changed in: firefox (Ubuntu) Status: Confirmed => Fix Released -- 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/1860830 Title: Geolocation not working − the Google maps API always returns error codes Status in chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Happened as soon as Firefox was updated to 72.0.1. I noticed sites could not determine my location. Troubleshooting page shows "missing" under Location service key. I have another computer running Lubuntu 18.04LTS, which I rarely use. Just for fun, I booted it up and as soon as the software updater updated Firefox to 72.0.1, location stopped working. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 72.0.1+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frank 2125 F pulseaudio /dev/snd/controlC1: frank 2125 F pulseaudio BuildID: 20200107212822 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 19:58:30 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 192.168.0.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.8 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-82fc5472-37b3-46d6-a6fa-f47e11180406 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:727 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=72.0.1/20200107212822 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to bionic on 2019-07-05 (203 days ago) dmi.bios.date: 03/24/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.27 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1442 dmi.board.vendor: Hewlett-Packard dmi.board.version: 67.33 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.27:bd03/24/2011:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr048D10242B202:rvnHewlett-Packard:rn1442:rvr67.33:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 048D10242B202 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1860830/+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 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop
OK, got it, will upload for G. thx. -- 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/1889217 Title: Make digital mic on the AMD Renoir machines work under gnome desktop Status in alsa-lib package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-lib source package in Groovy: New Status in alsa-ucm-conf source package in Groovy: New Status in pulseaudio source package in Groovy: New Bug description: [Impact] On the LENOVO AMD Renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input and multichannel input, and users can only record sound from analog input, the multichannel input can't function at all. Besides this issue, there is another issue, after users plug an external mic, the external mic can't replace the dmic automatically, this gives users a bad experience since this behaviour is different from the other audio designs. [Fix for pulseaudio] backport 3 patches: 2 of them from upstream device-port: queue CARD CHANGE event before update default sink alsa: adjust ucm sink/source priority according to ports priority 1 of them from a merge request: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Fix for alsa-ucm-conf] backport 14 patches: 11 of them from upstream: ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch ucm.conf-add-support-for-the-kernel-module-name-tree.patch sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch sof-soundwire-initial-UCM2-version.patch sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch sof-soundwire-rewrite-for-syntax-3.patch HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch Fix-invalid-Regex-Type-in-various-Condition-blocks.patch hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 3 of them from a merge request: https://github.com/alsa-project/alsa-ucm-conf/pull/41 [Fix for alsa-lib] backport 47 patches from upstream: Enabled-extended-namehints-in-alsa.conf.patch conf-add-snd_config_is_array-function.patch topology-use-snd_config_is_array-function.patch ucm-merge-the-array-items-from-the-condition-blocks.patch ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch ucm-execute-SectionDefaults-lately-when-the-first-ve.patch ucm-handle-set-_once-command.patch ucm-handle-set-_defaults-command.patch ucm-initialize-mgr-once_list.patch ucm-fix-SectionOnce-comment.patch ucm-fix-compilation-error-in-set_defaults_user.patch ucm-rename-SectionOnce-to-BootSequence.patch ucm-rename-_once-command-to-_boot-command.patch ucm-configuration-implement-in-place-Include.patch ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch ucm-config-substitute-File-string-to-allow-variables.patch ucm-configuration-allow-to-define-the-configuration-.patch ucm-configuration-add-DefineRegex.patch ucm-substitute-arguments-in-sequences.patch ucm-allow-syntax-version-3.patch ucm-config-change-the-in-place-include-evaluation-or.patch ucm-allow-to-specify-the-toplevel-directory-using-as.patch ucm-substitute-also-value-strings.patch ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch ucm-String-condition-implement-Empty.patch ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch ucm-substitute-OpenName.patch ucm-substitute-CardNumber.patch ucm-implement-the-toplevel-ucm-configuration-file-pa.patch ucm-substitute-device-modifier-names-too.patch ucm-substitute-device-strings-in-the-device-lists.patch ucm-substitute-component-sequence-string.patch ucm-substitute-verb-name-and-file-field.patch ucm-substitute-Comment-in-Transition-and-Device.patch ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch ucm-substitute-arguments-in-sequences-only-for-synta.patch ucm-shuffle-code-in-compound_merge.patch ucm-implement-CardIdByName-substitution.patch ucm-allow-to-ignore-errors-for-the-value-substitutio.patch ucm-allow-to-use-the-defined-variables-in-the-substi.patch ucm-implement-CardNumberByName-substitution.patch ucm-fix-the-possible-buffer-overflow-substitution.patch
[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Thanks for the tip, also got this working with the liquorix kernel but didn't have to update the firmware - used the current version in ubuntu 20.04 -- 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 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/pulseaudio/+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
[Desktop-packages] [Bug 1890533] Re: Overview stuttering with 3K & Intel
Not yet, but the good news is it's coming soon: https://wiki.gnome.org/ThreePointThirtyseven And should be in Ubuntu 20.10 soon after that. Also note your log is still mentioning errors from: /home/carlos/.local/share/gnome-shell/extensions/clipboard- indica...@tudmotu.com/... The simplest way to clear local extensions is to remove the whole 'extensions' directory. -- 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/1890533 Title: Overview stuttering with 3K & Intel Status in gnome-shell package in Ubuntu: Incomplete Bug description: This was first described upstream in https://gitlab.gnome.org/GNOME /gnome-shell/-/issues/2697 I'm reporting it here as requested in https://discourse.ubuntu.com/t /gnome-shell-performance-improvements-in- ubuntu-20-04/15972/38?u=memeplex Please don't be mislead by the enabled-extensions value in the attached log (['cpuf...@zdyb.tk', 'impatie...@gfxmonk.net', 'clipboard-indica...@tudmotu.com', 'ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com']). This is just a residual value, the only extensions installed in my system are the ones provided by Ubuntu and clipboard-indicator. And desktop-icons is indeed disabled. Besides I'm perfectly able to reproduce the same problem in a vanilla Gnome installation both in Arch and in Fedora using a wide range of kernels (from 5.4 to 5.8). Despite some variations, performance is consistently poor. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 02:23:54 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-24 (103 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890533/+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 1890533] Re: Overview stuttering with 3K & Intel
> For me, only GNOME 3.38 (prerelease) is close to smooth at 4K. Is there a reasonably simple way to test this in Ubuntu? Or maybe I could look for a package in the AUR. -- 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/1890533 Title: Overview stuttering with 3K & Intel Status in gnome-shell package in Ubuntu: Incomplete Bug description: This was first described upstream in https://gitlab.gnome.org/GNOME /gnome-shell/-/issues/2697 I'm reporting it here as requested in https://discourse.ubuntu.com/t /gnome-shell-performance-improvements-in- ubuntu-20-04/15972/38?u=memeplex Please don't be mislead by the enabled-extensions value in the attached log (['cpuf...@zdyb.tk', 'impatie...@gfxmonk.net', 'clipboard-indica...@tudmotu.com', 'ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com']). This is just a residual value, the only extensions installed in my system are the ones provided by Ubuntu and clipboard-indicator. And desktop-icons is indeed disabled. Besides I'm perfectly able to reproduce the same problem in a vanilla Gnome installation both in Arch and in Fedora using a wide range of kernels (from 5.4 to 5.8). Despite some variations, performance is consistently poor. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 02:23:54 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-24 (103 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890533/+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
