[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
[Desktop-packages] [Bug 1889784] Re: Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland)
** Changed in: firefox Status: In Progress => Fix Released -- 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/1889784 Title: Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland) Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: After updating Firefox from 78 to 79, hardware-accelerated video decoding no longer works properly in Wayland: streaming video gets cut off with an error message from the service. == Steps to reproduce == 1. Follow the steps in [1] to enable VA-API. 2. Open a Youtube/Twitch video (for instance https://www.twitch.tv/rifftrax), press play == What I expect to happen == For the video be played without issues (as it did with Firefox 78). == What happens == After playing for a while (anything from just a few seconds to a couple of minutes), the video stops and is replaced by a service-specific error message, such as error #3000 (in case of Twitch). Even when playing, the video also flickers green. After reloading the tab, the video again plays for a few seconds before the error message reappears. == Other info == A fix is apparently already in the works upstream [2]. * [1] https://mastransky.wordpress.com/2020/06/03/firefox-on-fedora-finally-gets-va-api-on-wayland/ * [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1645671 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BuildID: 20200720193547 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 31 17:07:50 2020 InstallationDate: Installed on 2016-10-13 (1387 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-11T14:52:22.308877 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1889784/+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
> 1. Reboot, make sure you still see stuttering and then run these commands: Done > 2. Completely uninstall these extensions: They weren't installed in fact, just remaining configurations of old installations. I've removed every reference to them from my settings now. > 3. Disable 'Ubuntu AppIndicators' in the 'Extensions' app, then log out and > in again. Done. No difference. > 4. Edit /etc/environment and add a new line: Done. No difference. -- 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
** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890533/+attachment/5399149/+files/lspcik.txt -- 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
> Also remember to update your system because it appears to be out of date... Strange cause I manually run the GUI updater on a daily basis. But it's showing no update while I get 7 upgradeable packages from the CLI. Done, just small things, no difference. -- 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
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890533/+attachment/5399150/+files/journal.txt -- 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 1889784]
https://hg.mozilla.org/mozilla-central/rev/bacacb384008 -- 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/1889784 Title: Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland) Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: After updating Firefox from 78 to 79, hardware-accelerated video decoding no longer works properly in Wayland: streaming video gets cut off with an error message from the service. == Steps to reproduce == 1. Follow the steps in [1] to enable VA-API. 2. Open a Youtube/Twitch video (for instance https://www.twitch.tv/rifftrax), press play == What I expect to happen == For the video be played without issues (as it did with Firefox 78). == What happens == After playing for a while (anything from just a few seconds to a couple of minutes), the video stops and is replaced by a service-specific error message, such as error #3000 (in case of Twitch). Even when playing, the video also flickers green. After reloading the tab, the video again plays for a few seconds before the error message reappears. == Other info == A fix is apparently already in the works upstream [2]. * [1] https://mastransky.wordpress.com/2020/06/03/firefox-on-fedora-finally-gets-va-api-on-wayland/ * [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1645671 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BuildID: 20200720193547 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 31 17:07:50 2020 InstallationDate: Installed on 2016-10-13 (1387 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-11T14:52:22.308877 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1889784/+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 1889784]
Not tracking as this is still disabled. -- 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/1889784 Title: Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland) Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: After updating Firefox from 78 to 79, hardware-accelerated video decoding no longer works properly in Wayland: streaming video gets cut off with an error message from the service. == Steps to reproduce == 1. Follow the steps in [1] to enable VA-API. 2. Open a Youtube/Twitch video (for instance https://www.twitch.tv/rifftrax), press play == What I expect to happen == For the video be played without issues (as it did with Firefox 78). == What happens == After playing for a while (anything from just a few seconds to a couple of minutes), the video stops and is replaced by a service-specific error message, such as error #3000 (in case of Twitch). Even when playing, the video also flickers green. After reloading the tab, the video again plays for a few seconds before the error message reappears. == Other info == A fix is apparently already in the works upstream [2]. * [1] https://mastransky.wordpress.com/2020/06/03/firefox-on-fedora-finally-gets-va-api-on-wayland/ * [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1645671 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BuildID: 20200720193547 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 31 17:07:50 2020 InstallationDate: Installed on 2016-10-13 (1387 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-11T14:52:22.308877 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1889784/+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 1889784]
Pushed by abutkov...@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/bacacb384008 [Linux/VA-API] Create DMABufSurfaceWrapper directly at nsTAttay and disable DMABufSurfaceWrapper class copy and assignment constructors, r=jya -- 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/1889784 Title: Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland) Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: After updating Firefox from 78 to 79, hardware-accelerated video decoding no longer works properly in Wayland: streaming video gets cut off with an error message from the service. == Steps to reproduce == 1. Follow the steps in [1] to enable VA-API. 2. Open a Youtube/Twitch video (for instance https://www.twitch.tv/rifftrax), press play == What I expect to happen == For the video be played without issues (as it did with Firefox 78). == What happens == After playing for a while (anything from just a few seconds to a couple of minutes), the video stops and is replaced by a service-specific error message, such as error #3000 (in case of Twitch). Even when playing, the video also flickers green. After reloading the tab, the video again plays for a few seconds before the error message reappears. == Other info == A fix is apparently already in the works upstream [2]. * [1] https://mastransky.wordpress.com/2020/06/03/firefox-on-fedora-finally-gets-va-api-on-wayland/ * [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1645671 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BuildID: 20200720193547 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 31 17:07:50 2020 InstallationDate: Installed on 2016-10-13 (1387 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-11T14:52:22.308877 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1889784/+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 1890382] Re: Gnome-terminal maximize loses one line of terminal output
Attaching original screenshots: gnomeTerminalMaximiseBugScreenshot1-afterLScommand.png gnomeTerminalMaximiseBugScreenshot2-afterMaximize.png ** Attachment added: "gnomeTerminalMaximiseBugScreenshots.png" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1890382/+attachment/5399148/+files/gnomeTerminalMaximiseBugScreenshots.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1890382 Title: Gnome-terminal maximize loses one line of terminal output Status in gnome-terminal package in Ubuntu: New Bug description: Gnome-terminal maximize loses one line of terminal output. Summary: 1. Assume the gnome-terminal currently contains output that exceeds the maximum number of characters of its current display area (ie the text is wrapped) 2. Maximise the gnome-terminal 3. Note that one line of the original content is lost Replication: cd ~/gnomeTerminalBug/replicationTest touch 01.txt touch 02.txt touch 03.txt touch 04.txt touch 05.txt touch 06.txt touch 07.txt touch 08.txt touch 09.txt touch 10.txt touch 11.txt touch 12.txt touch 13.txt touch 14.txt touch 15.txt touch 16.txt touch 17.txt touch 18.txt touch 19.txt touch 20.txt touch 21.txt touch 22.txt touch 23.txt touch 24.txt touch 25.txt touch 26.txt touch 27.txt touch 28.txt touch 29.txt touch 30.txt touch 31.txt touch 32.txt touch 33.txt touch 34.txt touch 35.txt touch 36.txt touch 37.txt touch 38.txt touch 39.txt touch 40.txt touch 41.txt touch 42.txt touch 43.txt touch
[Desktop-packages] [Bug 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes
Yes, find the new packages' names: dpkg -l | grep 5.8.0-050800 and then purge them: sudo dpkg -P ... -- 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/1890418 Title: i915 does not expose vendor-specific extended HDMI timings/modes Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: I have a Toshiba radius 11 laptop which has a 4 k native screen. I have connected an Asus PB287Q 28" external monitor (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/) over HDMI which displays the full 4K resolution when running under windows10 but will only reach a maximum resolution of 1920x1080 under ubuntu 20.04, same hardware just dual booting. Under Monitor Preferences this monitor is detected as an "Ancor Communications inc 28" and the monitor preferences provides a number of resolution steps up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this resolution is added to the monitor preferences pick list but attempting to apply it results in "the selected configuration for displays could not ..." message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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 1889784]
[Tracking Requested - why for this release]: This regression affects: * MOZ_ENABLE_WAYLAND=1 users with Firefox 79, * MOZ_X11_EGL=1 and MOZ_ENABLE_WAYLAND=1 users with Firefox 80. Everyone is excited that Firefox 80 finally supports VAAPI hardware decoding on X11, it got news coverage, etc., but those who tested it know that it suffers from at least two fatal bugs. (bug 1645672 is the other one.) Wayland/MOZ_X11_EGL and VAAPI are still experimental and disabled-by-default, but it's a killer feature that brings users back. Therefore please consider uplifing this into beta, and even into a dot release, if there is any. Downstream Fedora applies this patch on Firefox 79: https://src.fedoraproject.org/rpms/firefox/c/cd18e999f576523b6b3f2076bca625d5e04d1178?branch=master https://www.reddit.com/r/archlinux/comments/i0ireu/firefox_developer_edition_hardware_video/fzpojad/ https://www.reddit.com/r/flatpak/comments/i157dm/green_flashes_in_video_in_firefox/ https://www.reddit.com/r/linux/comments/i04cvr/psa_firefox_79_appears_to_break_vaapi_decoding_on/ https://www.reddit.com/r/firefox/comments/i1p2ct/linux_vaapi_video_decode_acceleration_unreliable/ -- 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/1889784 Title: Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland) Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: After updating Firefox from 78 to 79, hardware-accelerated video decoding no longer works properly in Wayland: streaming video gets cut off with an error message from the service. == Steps to reproduce == 1. Follow the steps in [1] to enable VA-API. 2. Open a Youtube/Twitch video (for instance https://www.twitch.tv/rifftrax), press play == What I expect to happen == For the video be played without issues (as it did with Firefox 78). == What happens == After playing for a while (anything from just a few seconds to a couple of minutes), the video stops and is replaced by a service-specific error message, such as error #3000 (in case of Twitch). Even when playing, the video also flickers green. After reloading the tab, the video again plays for a few seconds before the error message reappears. == Other info == A fix is apparently already in the works upstream [2]. * [1] https://mastransky.wordpress.com/2020/06/03/firefox-on-fedora-finally-gets-va-api-on-wayland/ * [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1645671 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BuildID: 20200720193547 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 31 17:07:50 2020 InstallationDate: Installed on 2016-10-13 (1387 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-11T14:52:22.308877 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1889784/+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 1889784]
Since the status are different for nightly and release, what's the status for beta? For more information, please visit [auto_nag documentation](https://wiki.mozilla.org/Release_Management/autonag#missing_beta_status.py). -- 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/1889784 Title: Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland) Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: After updating Firefox from 78 to 79, hardware-accelerated video decoding no longer works properly in Wayland: streaming video gets cut off with an error message from the service. == Steps to reproduce == 1. Follow the steps in [1] to enable VA-API. 2. Open a Youtube/Twitch video (for instance https://www.twitch.tv/rifftrax), press play == What I expect to happen == For the video be played without issues (as it did with Firefox 78). == What happens == After playing for a while (anything from just a few seconds to a couple of minutes), the video stops and is replaced by a service-specific error message, such as error #3000 (in case of Twitch). Even when playing, the video also flickers green. After reloading the tab, the video again plays for a few seconds before the error message reappears. == Other info == A fix is apparently already in the works upstream [2]. * [1] https://mastransky.wordpress.com/2020/06/03/firefox-on-fedora-finally-gets-va-api-on-wayland/ * [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1645671 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BuildID: 20200720193547 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 31 17:07:50 2020 InstallationDate: Installed on 2016-10-13 (1387 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-11T14:52:22.308877 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1889784/+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
Also remember to update your system because it appears to be out of date... sudo apt update sudo apt full-upgrade Reboot -- 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 1890382] Re: Gnome-terminal maximize loses one line of terminal output
I have encountered a seemingly related issue where ls is sometimes displaying different output depending on the terminal display size (and when the function is called), independent of maximisation. ** Attachment added: "gnomeTerminalDisplayBugScreenshot.png" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1890382/+attachment/5399141/+files/gnomeTerminalDisplayBugScreenshot.png ** Attachment removed: "gnomeTerminalMaximiseBugScreenshots.png" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1890382/+attachment/5398803/+files/gnomeTerminalMaximiseBugScreenshots.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1890382 Title: Gnome-terminal maximize loses one line of terminal output Status in gnome-terminal package in Ubuntu: New Bug description: Gnome-terminal maximize loses one line of terminal output. Summary: 1. Assume the gnome-terminal currently contains output that exceeds the maximum number of characters of its current display area (ie the text is wrapped) 2. Maximise the gnome-terminal 3. Note that one line of the original content is lost Replication: cd ~/gnomeTerminalBug/replicationTest touch 01.txt touch 02.txt touch 03.txt touch 04.txt touch 05.txt touch 06.txt touch 07.txt touch 08.txt touch 09.txt touch 10.txt touch 11.txt touch 12.txt touch 13.txt touch 14.txt touch 15.txt touch 16.txt touch 17.txt touch 18.txt touch 19.txt touch 20.txt touch 21.txt touch 22.txt touch 23.txt touch 24.txt touch 25.txt touch 26.txt touch 27.txt touch 28.txt touch 29.txt touch 30.txt touch 31.txt touch 32.txt touch 33.txt touch 34.txt touch 35.txt touch 36.txt touch 37.txt touch 38.txt touch 39.txt touch 40.txt touch
[Desktop-packages] [Bug 1890533] Re: Overview stuttering with 3K & Intel
Although I would not be surprised if those don't work adequately. For me, only GNOME 3.38 (prerelease) is close to smooth at 4K. Although 3.36 is at least usable with the MESA_LOADER_DRIVER_OVERRIDE=i965 workaround. -- 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 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes
Daniel I successfully ran the dpkg process as you illustrated but it then failed to boot, so now I must manually selected the 5.4 version in order to get to this boot. Is there a way to reverse that? -- 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/1890418 Title: i915 does not expose vendor-specific extended HDMI timings/modes Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: I have a Toshiba radius 11 laptop which has a 4 k native screen. I have connected an Asus PB287Q 28" external monitor (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/) over HDMI which displays the full 4K resolution when running under windows10 but will only reach a maximum resolution of 1920x1080 under ubuntu 20.04, same hardware just dual booting. Under Monitor Preferences this monitor is detected as an "Ancor Communications inc 28" and the monitor preferences provides a number of resolution steps up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this resolution is added to the monitor preferences pick list but attempting to apply it results in "the selected configuration for displays could not ..." message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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
Please try these. You can stop at any step if the problem goes away... 1. Reboot, make sure you still see stuttering and then run these commands: lspci -k > lspcik.txt journalctl -b0 > journal.txt and attach the resulting text files here. 2. Completely uninstall these extensions: cpuf...@zdyb.tk', 'impatie...@gfxmonk.net', 'clipboard- indica...@tudmotu.com' then reboot. 3. Disable 'Ubuntu AppIndicators' in the 'Extensions' app, then log out and in again. 4. Edit /etc/environment and add a new line: MESA_LOADER_DRIVER_OVERRIDE=i965 then reboot. ** Summary changed: - Overview stuttering with 4K & Intel + Overview stuttering with 3K & Intel ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags added: performance -- 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 1888504] Re: Two-finger touchpad scroll broken
** Changed in: libreoffice (Ubuntu) Importance: Undecided => Low -- 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/1888504 Title: Two-finger touchpad scroll broken Status in libreoffice package in Ubuntu: New Bug description: Run Calc -> drag two fingers up, down, left or right slowly. Expected behaviour: content pans in the direction of movement Observed behaviour: no effect on viewport, sometimes at all, sometimes after a sufficiently long drag, the viewport jumps/snaps to a different part of the document, as if the entire "accumulated" movement happened at once The behaviour is easily reproducible in Calc and Draw, but does not happen in Writer. Other applications (e.g. Firefox, Nautilus, GVim...) work as expected, scrolling smoothly as fingers slide along the touchpad. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-core 1:6.0.7-0ubuntu0.18.04.10 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 14:31:59 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (804 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2020-03-04 (140 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1888504/+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 4K & Intel
** Description changed: 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. 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) ** Description changed: 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) -- 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 4K & Intel Status in gnome-shell package in Ubuntu: New 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 Unsubscri
[Desktop-packages] [Bug 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes
To test kernel 5.8 you need to download all these packages EXCEPT the "lowlatency" ones: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8/amd64/ and then install them all at once: sudo dpkg -i *.deb -- 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/1890418 Title: i915 does not expose vendor-specific extended HDMI timings/modes Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: I have a Toshiba radius 11 laptop which has a 4 k native screen. I have connected an Asus PB287Q 28" external monitor (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/) over HDMI which displays the full 4K resolution when running under windows10 but will only reach a maximum resolution of 1920x1080 under ubuntu 20.04, same hardware just dual booting. Under Monitor Preferences this monitor is detected as an "Ancor Communications inc 28" and the monitor preferences provides a number of resolution steps up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this resolution is added to the monitor preferences pick list but attempting to apply it results in "the selected configuration for displays could not ..." message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes
The attachment in comment #10 confirms the problem is happening at a low level in the kernel. Although Xorg could override that if it was smart enough. In theory you can do it manually but would need to become an expert at crafting modeline entries to get it working. I don't know how myself. If that's possible then the data you need is in comment #7. Obviously Windows 10 demonstrates that it is possible to support this monitor with this HDMI port. Only Linux does not yet... As a workaround, if you have a USB-C port and an appropriate cable/adapter then you might be able to use the DisplayPort on the monitor. If that works then it should give different timings and might provide the 4K option... also at 60Hz instead of just 30Hz. ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1890418 Title: i915 does not expose vendor-specific extended HDMI timings/modes Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: I have a Toshiba radius 11 laptop which has a 4 k native screen. I have connected an Asus PB287Q 28" external monitor (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/) over HDMI which displays the full 4K resolution when running under windows10 but will only reach a maximum resolution of 1920x1080 under ubuntu 20.04, same hardware just dual booting. Under Monitor Preferences this monitor is detected as an "Ancor Communications inc 28" and the monitor preferences provides a number of resolution steps up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this resolution is added to the monitor preferences pick list but attempting to apply it results in "the selected configuration for displays could not ..." message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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 1890418] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1890418 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1890418 Title: i915 does not expose vendor-specific extended HDMI timings/modes Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: I have a Toshiba radius 11 laptop which has a 4 k native screen. I have connected an Asus PB287Q 28" external monitor (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/) over HDMI which displays the full 4K resolution when running under windows10 but will only reach a maximum resolution of 1920x1080 under ubuntu 20.04, same hardware just dual booting. Under Monitor Preferences this monitor is detected as an "Ancor Communications inc 28" and the monitor preferences provides a number of resolution steps up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this resolution is added to the monitor preferences pick list but attempting to apply it results in "the selected configuration for displays could not ..." message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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] [NEW] Overview stuttering with 4K & Intel
Public bug reported: 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 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) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1890533 Title: Overview stuttering with 4K & Intel Status in gnome-shell package in Ubuntu: New 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 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 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes
I found the information, at section 3.4 of the manual https://dlcdnets.asus.com/pub/ASUS/LCD%20Monitors/PB287/PB287Q_English.pdf where VESA / IBM Modes Support Timing (DP/HDMI) reaches 4k but CEA-861 Formats Supported Timing (HDMI/MHL) only reach 1920 -- 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/1890418 Title: i915 does not expose vendor-specific extended HDMI timings/modes Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Toshiba radius 11 laptop which has a 4 k native screen. I have connected an Asus PB287Q 28" external monitor (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/) over HDMI which displays the full 4K resolution when running under windows10 but will only reach a maximum resolution of 1920x1080 under ubuntu 20.04, same hardware just dual booting. Under Monitor Preferences this monitor is detected as an "Ancor Communications inc 28" and the monitor preferences provides a number of resolution steps up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this resolution is added to the monitor preferences pick list but attempting to apply it results in "the selected configuration for displays could not ..." message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes
Regarding HDMI version the spec which I gave a link to claims; True Resolution : 3840x2160 at 60Hz (DisplayPort) ,3840x2160 at 30Hz (HDMI) Some while ago I was researching this issue and found a specification page on the ASUS website which showed two formats for declaring the frame rate, one extended only to the 1920 value while the other went to the full 4K. From this I deduced that perhaps windows uses one report format while linux uses the other. I cannot locate that page now, it may have been taken down. -- 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/1890418 Title: i915 does not expose vendor-specific extended HDMI timings/modes Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Toshiba radius 11 laptop which has a 4 k native screen. I have connected an Asus PB287Q 28" external monitor (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/) over HDMI which displays the full 4K resolution when running under windows10 but will only reach a maximum resolution of 1920x1080 under ubuntu 20.04, same hardware just dual booting. Under Monitor Preferences this monitor is detected as an "Ancor Communications inc 28" and the monitor preferences provides a number of resolution steps up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this resolution is added to the monitor preferences pick list but attempting to apply it results in "the selected configuration for displays could not ..." message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes
Thanks for your work I just bought and tried a new 4K hdmi cable, with no change. I noticed that the monitor has TWO inputs, HDMI and HDMI/MHL (it had been plugged into HDMI) but switching this to HDMI/MHL gave no result. I am using MATE but the same issue occurs in several flavours of Ubuntu that I have tried. I dont know how to try the new kernel at https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8/ as you requested. If I attempt to ask Gdebi to load the linux-image-unsigned-5.8.0-050800-generic_5.8.0-050800.202008022230_amd64.deb package from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8/amd64/ it fails with unmet dependencies. kernel-modes.txt is attached ** Attachment added: "kernel-modes.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890418/+attachment/5399129/+files/kernel-modes.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1890418 Title: i915 does not expose vendor-specific extended HDMI timings/modes Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Toshiba radius 11 laptop which has a 4 k native screen. I have connected an Asus PB287Q 28" external monitor (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/) over HDMI which displays the full 4K resolution when running under windows10 but will only reach a maximum resolution of 1920x1080 under ubuntu 20.04, same hardware just dual booting. Under Monitor Preferences this monitor is detected as an "Ancor Communications inc 28" and the monitor preferences provides a number of resolution steps up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this resolution is added to the monitor preferences pick list but attempting to apply it results in "the selected configuration for displays could not ..." message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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 1875113] Re: OpenGL not detected (Intel Ivy Bridge + Nvidia GeForce GT 635M)
Please open your own new bug by running: ubuntu-bug gnome-shell This bug should stay closed. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Opinion => Invalid ** Changed in: xorg-server (Ubuntu) Status: Opinion => Invalid ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Invalid => Won't Fix ** Changed in: xorg-server (Ubuntu) Status: Invalid => Won't Fix -- 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/1875113 Title: OpenGL not detected (Intel Ivy Bridge + Nvidia GeForce GT 635M) Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in xorg-server package in Ubuntu: Won't Fix Bug description: The screen presents screen tearing in the browser, on the desktop as well and when installing Steam it says that it does not detect Opengl or any video card 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: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 20:01:32 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:100d] NVIDIA Corporation GF108M [GeForce GT 635M] [10de:0de3] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108M [GeForce GT 635M] [1043:100d] InstallationDate: Installed on 2020-04-24 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. K46CM ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CO.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=2d00d17e-c566-412e-bdfd-529af92571e2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K46CM.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K46CM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK46CM.317:bd05/17/2013:svnASUSTeKCOMPUTERINC.:pnK46CM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK46CM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K46CM dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/nvidia-graphics-drivers-390/+bug/1875113/+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 1875113] Re: OpenGL not detected (Intel Ivy Bridge + Nvidia GeForce GT 635M)
I'm too affected, please review. Thanks ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Expired => Opinion ** Changed in: xorg-server (Ubuntu) Status: Expired => Opinion -- 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/1875113 Title: OpenGL not detected (Intel Ivy Bridge + Nvidia GeForce GT 635M) Status in nvidia-graphics-drivers-390 package in Ubuntu: Opinion Status in xorg-server package in Ubuntu: Opinion Bug description: The screen presents screen tearing in the browser, on the desktop as well and when installing Steam it says that it does not detect Opengl or any video card 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: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 20:01:32 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:100d] NVIDIA Corporation GF108M [GeForce GT 635M] [10de:0de3] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108M [GeForce GT 635M] [1043:100d] InstallationDate: Installed on 2020-04-24 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. K46CM ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CO.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=2d00d17e-c566-412e-bdfd-529af92571e2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K46CM.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K46CM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK46CM.317:bd05/17/2013:svnASUSTeKCOMPUTERINC.:pnK46CM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK46CM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K46CM dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/nvidia-graphics-drivers-390/+bug/1875113/+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 1826786] Re: High CPU usage of the Xorg process
> I mean that xorg is working and using 50%of the cou without purpose.When I have just close fire fox. When this happens please: 1. Run 'top' and check if any other processes are using more than 10% CPU. 2. Look carefully at your screen and tell us if any part is constantly changing, like any performance graphs etc. 3. Run: sudo apt-get install mesa-utils glxinfo > glxinfo.txt and attach the file 'glxinfo.txt' here. ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1826786 Title: High CPU usage of the Xorg process Status in xorg-server package in Ubuntu: Incomplete Bug description: when I see for a long time on firefox a video on youtube. Xorg is begining to use the processor by incraese a two core processor for an average use on 40%. When I close firefox xorg ix in excution in the same way. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 Uname: Linux 4.4.0-145-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Apr 28 23:05:17 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) (prog-if 00 [VGA controller]) Subsystem: Lenovo 82G33/G31 Express Integrated Graphics Controller [17aa:303c] InstallationDate: Installed on 2015-07-16 (1382 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 222 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-145-generic root=UUID=b8485282-6c4c-4911-8054-b3658a58f78b ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 52KT38AUS dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvr52KT38AUS:bd05/07/2008:svnLENOVO:pn222:pvrLENOVO:rvnLENOVO:rnLENOVO:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 222 dmi.product.version: LENOVO dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Apr 28 19:27:56 2019 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputImPS/2 Logitech Wheel Mouse MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 19232 vendor GSM xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1826786/+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 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes
Please also run this command: grep . /sys/class/drm/*/modes > kernel-modes.txt and attach the resulting text file here. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1890418 Title: i915 does not expose vendor-specific extended HDMI timings/modes Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Toshiba radius 11 laptop which has a 4 k native screen. I have connected an Asus PB287Q 28" external monitor (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/) over HDMI which displays the full 4K resolution when running under windows10 but will only reach a maximum resolution of 1920x1080 under ubuntu 20.04, same hardware just dual booting. Under Monitor Preferences this monitor is detected as an "Ancor Communications inc 28" and the monitor preferences provides a number of resolution steps up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this resolution is added to the monitor preferences pick list but attempting to apply it results in "the selected configuration for displays could not ..." message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes
This might have been fixed in the Intel graphics driver in a newer kernel. Can you please test this one? https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8/ -- 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/1890418 Title: i915 does not expose vendor-specific extended HDMI timings/modes Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Toshiba radius 11 laptop which has a 4 k native screen. I have connected an Asus PB287Q 28" external monitor (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/) over HDMI which displays the full 4K resolution when running under windows10 but will only reach a maximum resolution of 1920x1080 under ubuntu 20.04, same hardware just dual booting. Under Monitor Preferences this monitor is detected as an "Ancor Communications inc 28" and the monitor preferences provides a number of resolution steps up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this resolution is added to the monitor preferences pick list but attempting to apply it results in "the selected configuration for displays could not ..." message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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 1890418] Re: External monitor will not display to 4k
Actually the problem might just be that the Linux kernel doesn't understand extended vendor-specific display timings. I've decoded your monitor's EDID and it reveals that 3840x2160 30Hz is mentioned: edid-decode (hex): 00 ff ff ff ff ff ff 00 04 69 a3 28 24 51 00 00 0e 1b 01 03 80 3e 22 78 3a 1c b5 a3 57 4f a0 27 0d 50 54 bf ef 00 d1 c0 81 40 81 80 95 00 b3 00 71 4f 81 c0 01 01 04 74 00 30 f2 70 5a 80 b0 58 8a 00 6d 55 21 00 00 1a 02 3a 80 18 71 38 2d 40 58 2c 45 00 6d 55 21 00 00 1e 00 00 00 fd 00 1e 50 18 a0 1e 00 0a 20 20 20 20 20 20 00 00 00 fc 00 41 53 55 53 20 50 42 32 38 37 51 0a 20 01 83 02 03 2c f1 51 01 02 03 11 12 13 04 14 05 0e 0f 1d 1e 1f 90 20 22 23 09 17 07 83 01 00 00 6d 03 0c 00 20 00 00 3c 20 00 60 01 02 03 56 5e 00 a0 a0 a0 29 50 30 20 35 00 6d 55 21 00 00 1e e2 68 00 a0 a0 40 2e 60 30 20 36 00 6d 55 21 00 00 1a 01 1d 00 bc 52 d0 1e 20 b8 28 55 40 6d 55 21 00 00 1e 8c 0a d0 90 20 40 31 20 0c 40 55 00 6d 55 21 00 00 18 00 00 00 00 00 00 00 00 00 00 00 5e EDID version: 1.3 Manufacturer: ACI Model 10403 Serial Number 20772 Made in week 14 of 2017 Digital display Maximum image size: 62 cm x 34 cm Gamma: 2.20 DPMS levels: Off Undefined display color type First detailed timing is preferred timing Color Characteristics Red: 0.6367, 0.3408 Green: 0.3115, 0.6250 Blue: 0.1542, 0.0537 White: 0.3134, 0.3291 Established Timings I & II 720x40070.082 Hz 9:531.467 kHz 28.320 MHz (IBM) 640x48059.940 Hz 4:331.469 kHz 25.175 MHz (DMT) 640x48066.667 Hz 4:335.000 kHz 30.240 MHz (Apple) 640x48072.809 Hz 4:337.861 kHz 31.500 MHz (DMT) 640x48075.000 Hz 4:337.500 kHz 31.500 MHz (DMT) 800x60056.250 Hz 4:335.156 kHz 36.000 MHz (DMT) 800x60060.317 Hz 4:337.879 kHz 40.000 MHz (DMT) 800x60072.188 Hz 4:348.077 kHz 50.000 MHz (DMT) 800x60075.000 Hz 4:346.875 kHz 49.500 MHz (DMT) 832x62474.551 Hz 4:349.726 kHz 57.284 MHz (Apple) 1024x76860.004 Hz 4:348.363 kHz 65.000 MHz (DMT) 1024x76870.069 Hz 4:356.476 kHz 75.000 MHz (DMT) 1024x76875.029 Hz 4:360.023 kHz 78.750 MHz (DMT) 1280x1024 75.025 Hz 5:479.976 kHz 135.000 MHz (DMT) Standard Timings 1920x1080 60.000 Hz 16:967.500 kHz 148.500 MHz (DMT) 1280x96060.000 Hz 4:360.000 kHz 108.000 MHz (DMT) 1280x1024 60.020 Hz 5:463.981 kHz 108.000 MHz (DMT) 1440x90059.887 Hz 16:10 55.935 kHz 106.500 MHz (DMT) 1680x1050 59.954 Hz 16:10 65.290 kHz 146.250 MHz (DMT) 1152x86475.000 Hz 4:367.500 kHz 108.000 MHz (DMT) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (DMT) Detailed mode: Clock 297.000 MHz, 621 mm x 341 mm 3840 4016 4104 4400 (176 88 296) 2160 2168 2178 2250 ( 8 10 72) +hsync -vsync VertFreq: 30.000 Hz, HorFreq: 67.500 kHz Detailed mode: Clock 148.500 MHz, 621 mm x 341 mm 1920 2008 2052 2200 ( 88 44 148) 1080 1084 1089 1125 ( 4 5 36) +hsync +vsync VertFreq: 60.000 Hz, HorFreq: 67.500 kHz Display Range Limits Monitor ranges (GTF): 30-80 Hz V, 24-160 kHz H, max dotclock 300 MHz Display Product Name: ASUS PB287Q Has 1 extension block Checksum: 0x83 CTA-861 Extension Block Revision 3 Underscans PC formats by default Basic audio support Supports YCbCr 4:4:4 Supports YCbCr 4:2:2 1 native detailed modes 40 bytes of CTA data blocks Video Data Block 640x48059.940 Hz 4:331.469 kHz 25.175 MHz (VIC 1) 720x48059.940 Hz 4:331.469 kHz 27.000 MHz (VIC 2) 720x48059.940 Hz 16:931.469 kHz 27.000 MHz (VIC 3) 720x57650.000 Hz 4:331.250 kHz 27.000 MHz (VIC 17) 720x57650.000 Hz 16:931.250 kHz 27.000 MHz (VIC 18) 1280x72050.000 Hz 16:937.500 kHz 74.250 MHz (VIC 19) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (VIC 4) 1920x1080i 50.000 Hz 16:928.125 kHz 74.250 MHz (VIC 20) 1920x1080i 60.000 Hz 16:933.750 kHz 74.250 MHz (VIC 5) 1440x48059.940 Hz 4:331.469 kHz 54.000 MHz (VIC 14) 1440x48059.940 Hz 16:931.469 kHz 54.000 MHz (VIC 15) 1440x57650.000 Hz 4:331.250 kHz 54.000 MHz (VIC 29) 1440x57650.000 Hz 16:931.250 kHz 54.000 MHz (VIC 30) 1920x1080 50.000 Hz 16:956.250 kHz 148.500 MHz (VIC 31) 1920x1080 60.000 Hz 16:967.500 kHz 148.500 MHz (VIC 16, native) 1920x1080 24.000 Hz 16:927.000 kHz 74.250 MHz (VIC 32) 1920x1080 30.000 Hz 16:933.750 kHz 74.250 MHz (VIC 34) Audio Data Block Linear PCM, max channels 2 Supported sample rates (kHz): 96 48 44.1 32 Supported sample sizes (bits): 24 20 16 Speaker Allocation Data Block Speaker map: FL/FR - Fron
[Desktop-packages] [Bug 1890418] Re: External monitor will not display to 4k
Thanks. The file xrandr.txt indeed shows the HDMI connection is limited to 1920x1080. It also shows that's the "current" mode but it lists no "preferred" mode, which does support the idea that the monitor can do higher resolution... The manufacturer's specs mention that 4K is limited to 30Hz over HDMI. But that should be fine. It just means the monitor can't do HDMI 2.0. Most likely the monitor only supports HDMI 1.3 or 1.4. I think the main problem here is probably the HDMI cable. If it can only handle HDMI 1.2 or lower then you will not see the 3840×2160 30Hz option. So I suggest getting a newer cable that supports at least HDMI 1.3. Why Windows 10 doesn't have the same issue, I don't know. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890418 Title: External monitor will not display to 4k Status in mutter package in Ubuntu: Incomplete Bug description: I have a Toshiba radius 11 laptop which has a 4 k native screen. I have connected an Asus PB287Q 28" external monitor (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/) over HDMI which displays the full 4K resolution when running under windows10 but will only reach a maximum resolution of 1920x1080 under ubuntu 20.04, same hardware just dual booting. Under Monitor Preferences this monitor is detected as an "Ancor Communications inc 28" and the monitor preferences provides a number of resolution steps up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this resolution is added to the monitor preferences pick list but attempting to apply it results in "the selected configuration for displays could not ..." message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+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 1817480] Re: Emacs color-theme package is gone from version 40.1
Still a problem in 42.2. No color-theme-* (thus no color-theme-modern that was proposed as a replacement). -- 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 1817480] Re: Emacs color-theme package is gone from version 40.1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: emacs-goodies-el (Ubuntu) Status: New => Confirmed -- 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 1890436] Re: VGA image is ghosted and stretched (LG L1953S)
** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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 1890418] Re: External monitor will not display to 4k
** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+attachment/5399093/+files/lspcik.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890418 Title: External monitor will not display to 4k Status in mutter package in Ubuntu: Incomplete Bug description: I have a Toshiba radius 11 laptop which has a 4 k native screen. I have connected an Asus PB287Q 28" external monitor (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/) over HDMI which displays the full 4K resolution when running under windows10 but will only reach a maximum resolution of 1920x1080 under ubuntu 20.04, same hardware just dual booting. Under Monitor Preferences this monitor is detected as an "Ancor Communications inc 28" and the monitor preferences provides a number of resolution steps up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this resolution is added to the monitor preferences pick list but attempting to apply it results in "the selected configuration for displays could not ..." message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+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 1890418] Re: External monitor will not display to 4k
** Attachment added: "xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+attachment/5399094/+files/xrandr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890418 Title: External monitor will not display to 4k Status in mutter package in Ubuntu: Incomplete Bug description: I have a Toshiba radius 11 laptop which has a 4 k native screen. I have connected an Asus PB287Q 28" external monitor (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/) over HDMI which displays the full 4K resolution when running under windows10 but will only reach a maximum resolution of 1920x1080 under ubuntu 20.04, same hardware just dual booting. Under Monitor Preferences this monitor is detected as an "Ancor Communications inc 28" and the monitor preferences provides a number of resolution steps up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this resolution is added to the monitor preferences pick list but attempting to apply it results in "the selected configuration for displays could not ..." message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+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 1890418] Re: External monitor will not display to 4k
Done. Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890418 Title: External monitor will not display to 4k Status in mutter package in Ubuntu: Incomplete Bug description: I have a Toshiba radius 11 laptop which has a 4 k native screen. I have connected an Asus PB287Q 28" external monitor (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/) over HDMI which displays the full 4K resolution when running under windows10 but will only reach a maximum resolution of 1920x1080 under ubuntu 20.04, same hardware just dual booting. Under Monitor Preferences this monitor is detected as an "Ancor Communications inc 28" and the monitor preferences provides a number of resolution steps up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this resolution is added to the monitor preferences pick list but attempting to apply it results in "the selected configuration for displays could not ..." message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+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 1890418] Re: External monitor will not display to 4k
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+attachment/5399092/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890418 Title: External monitor will not display to 4k Status in mutter package in Ubuntu: Incomplete Bug description: I have a Toshiba radius 11 laptop which has a 4 k native screen. I have connected an Asus PB287Q 28" external monitor (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/) over HDMI which displays the full 4K resolution when running under windows10 but will only reach a maximum resolution of 1920x1080 under ubuntu 20.04, same hardware just dual booting. Under Monitor Preferences this monitor is detected as an "Ancor Communications inc 28" and the monitor preferences provides a number of resolution steps up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this resolution is added to the monitor preferences pick list but attempting to apply it results in "the selected configuration for displays could not ..." message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+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] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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: Confirmed Status in xorg-server package in Ubuntu: New 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 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages: xserver-xorg-input-void 1:1.4.1-1build3 in groovy xserver-xorg-input-void 1:1.4.1-1build3 in groovy amd64 xserver-xorg-input-void 1:1.4.1-1build3 in groovy arm64 xserver-xorg-input-void 1:1.4.1-1build3 in groovy armhf xserver-xorg-input-void 1:1.4.1-1build3 in groovy ppc64el xserver-xorg-input-void 1:1.4.1-1build3 in groovy riscv64 xserver-xorg-input-void 1:1.4.1-1build3 in groovy s390x xserver-xorg-input-void-dbgsym 1:1.4.1-1build3 in groovy amd64 xserver-xorg-input-void-dbgsym 1:1.4.1-1build3 in groovy arm64 xserver-xorg-input-void-dbgsym 1:1.4.1-1build3 in groovy armhf xserver-xorg-input-void-dbgsym 1:1.4.1-1build3 in groovy ppc64el xserver-xorg-input-void-dbgsym 1:1.4.1-1build3 in groovy riscv64 xserver-xorg-input-void-dbgsym 1:1.4.1-1build3 in groovy s390x Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603 Remove [y|N]? y ** Changed in: xserver-xorg-input-void (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: Fix Released Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+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 1890418] Re: External monitor will not display to 4k
Please run this command to attach more information about the system: apport-collect 1890418 Please also run these commands: lspci -k > lspcik.txt journalctl -b0 > journal.txt xrandr --verbose > xrandr.txt and attach the resulting text files here. ** Tags added: focal ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890418 Title: External monitor will not display to 4k Status in mutter package in Ubuntu: Incomplete Bug description: I have a Toshiba radius 11 laptop which has a 4 k native screen. I have connected an Asus PB287Q 28" external monitor (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/) over HDMI which displays the full 4K resolution when running under windows10 but will only reach a maximum resolution of 1920x1080 under ubuntu 20.04, same hardware just dual booting. Under Monitor Preferences this monitor is detected as an "Ancor Communications inc 28" and the monitor preferences provides a number of resolution steps up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this resolution is added to the monitor preferences pick list but attempting to apply it results in "the selected configuration for displays could not ..." message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+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 1866444] Re: [MacBook2, 1, SigmaTel STAC9221 A1, Mic, Internal] Recording problem
Hi! I just want to chime in and document my workaround to use a generic UVC webcam with a built-in mic. I attach a screenshot showing both a "multichannel input" and "microphone" once the UVC webcam is attached. Notice the picklist still does not contain an item for the system built- in [analog] microphone. ** Attachment added: "Sound setting missing picklist item for internal analog mic" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1866444/+attachment/5399088/+files/Settings%20-%20Sounds%20-%20Microphone%20-%20Camera.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1866444 Title: [MacBook2,1, SigmaTel STAC9221 A1, Mic, Internal] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: What you expected to happen Settings -> Sound -> Input to list internal mic (to test orange bars for recording from internal mic) What actually happened Settings -> Sound -> Input only lists "Digital Input (S/PDIF)" (no bars move because no digital input connected) If possible, a minimal series of steps necessary to make it happen, where step 1 is "start the program" 1. Open Settings 2. Select Sound setting 3. Select Input tab -- NOTE: ultimately, I want recording to work in apps such as Chrome, Firefox, Zoom, etc. NOTE 2: mic recording was last working in Ubuntu 18.04.x (32-bit) instance on *same* MacBook hardware (this installation went corrupt so I can't reverify it still works unfortunately - I will add to this issue if I get the cycles to reinstall or at your request) NOTE 3: interestingly enough, while using "ubuntu-bug" it was able to record from the mic on the 1st (of 2 tests the bug collector initiated). -- $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 from "apt list --installed" alsa-base/bionic,bionic,bionic,bionic,now 1.0.25+dfsg-0ubuntu5 all [installed] alsa-utils/bionic,bionic,now 1.1.3-1ubuntu1 amd64 [installed] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_76_86_generic_63 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D1c: chinarut 1724 F...m pulseaudio /dev/snd/controlC0: chinarut 1724 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 22:41:25 2020 InstallationDate: Installed on 2020-01-24 (42 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Intel failed Symptom_Type: Only some of inputs are working Title: [MacBook2,1, SigmaTel STAC9221 A1, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/07 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB21.88Z.00A5.B07.0706270922 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4208CAA dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4208CAA dmi.modalias: dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA: dmi.product.family: MacBook dmi.product.name: MacBook2,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1866444/+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)
This looks like a signalling problem. There doesn't seem to be any corruption in the image. Only the signal to the monitor doesn't correctly match the frequencies that the monitor requires. As a workaround please try selecting 'Ubuntu on Wayland' from the login screen. Please also try a different VGA cable if you can. ** Summary changed: - Screen corruption with multi monitor setup + VGA image is ghosted and stretched (LG L1953S) ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1890436 Title: VGA image is ghosted and stretched (LG L1953S) Status in linux package in Ubuntu: New Status in xorg-server package in Ubuntu: New 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:
[Desktop-packages] [Bug 1890512] Re: bluetooth stopped working after recent apt updates
There have been no updates to the 'bluez' package since 20.04 was released. So that can't be the problem. Most likely it's a kernel update that caused the problem. The most recent one was only a week or two ago. Please try downgrading (or upgrading) your kernel version using these: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1890512 Title: bluetooth stopped working after recent apt updates Status in linux package in Ubuntu: Incomplete Bug description: bluetooth stopped working after recent apt updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 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 06:20:29 2020 InstallationDate: Installed on 2020-03-02 (156 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterestingModules: bluetooth Lsusb: Bus 002 Device 002: ID 1058:25e1 Western Digital Technologies, Inc. My Passport 25E1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 002: ID 24ae:1813 RAPOO Rapoo 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook UX461FN_UX461FN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=68586d80-0dfa-454e-918b-83ddbf1d4c3c ro quiet splash dis_ucode_ldr resume=UUID=014fadee-e595-4994-a198-c7eb8db1fa57 vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-05-21 (76 days ago) dmi.bios.date: 01/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX461FN.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX461FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX461FN.302:bd01/28/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX461FN_UX461FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX461FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: ZenBook UX461FN_UX461FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: mtime.conffile..etc.bluetooth.input.conf: 2020-06-30T20:08:54.584021 mtime.conffile..etc.bluetooth.main.conf: 2020-03-04T03:26:07.238405 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890512/+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.
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: bionic ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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_6
[Desktop-packages] [Bug 1715602] Re: ubiquity-dm / Install Ubuntu - Power button/menu does nothing
** Tags added: focal -- 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/1715602 Title: ubiquity-dm / Install Ubuntu - Power button/menu does nothing Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Bug description: Artful Desktop 20170907 In ubiquity-dm and 'Install Ubuntu' the power button does nothing. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubiquity 17.10.6 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CasperVersion: 1.384 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 09:55:57 2017 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170907) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1715602/+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 1890271] Re: [20.04.01] The system cannot be shut down after clicking the "Power off" option on the OEM installation mode
*** This bug is a duplicate of bug 1715602 *** https://bugs.launchpad.net/bugs/1715602 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1715602, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1715602 ubiquity-dm / Install Ubuntu - Power button/menu does nothing -- 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/1890271 Title: [20.04.01] The system cannot be shut down after clicking the "Power off" option on the OEM installation mode Status in gnome-shell package in Ubuntu: Confirmed Bug description: [Summary] After entering the OEM installation mode and then clicking the "Power off" option, the system cannot be powered off. [Steps to reproduce] 1. Plug the USB key which has the 20.04.01 build 2. Power on the system 3. Select USB drive to launch the grub menu 4. Select "OEM installation" to run the installation 5. After entering the OEM installation page, click the "Power off" option. 6. Check if the system can be powered off [Expected result] The system can be powered off after clicking the "Power off" option [Actual result] There is no response after clicking the "Power off" option [Failure rate] 3/3 [Additional information] system-manufacturer: LENOVO system-product-name: P920 CPU: Intel(R) Xeon(R) Gold 6230N CPU @ 2.30GHz GPU: nVidia - 10de:1e30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890271/+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 1890001] Re: Random stuttering while in game
*** This bug is a duplicate of bug 1849142 *** https://bugs.launchpad.net/bugs/1849142 You may also need to log out and in again. If the problem persists then please provide a new log by running: journalctl -b0 > journal-again.txt -- 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/1890001 Title: Random stuttering while in game Status in gnome-shell package in Ubuntu: Incomplete Bug description: Updated kernel to 5.7.12 and updated nvidia driver to 450 yesterday but only experiencing this today. Random stuttering while playing minecraft, no clue what's causing it but I checked system monitor and it shows random spikes of a cpu thread to 100% and some spikes staying at 100% for a prolonged period. It may be related to me updating my video driver that is not recommended so I will see if switching down will resolve the issue. I never had this issue on driver 440. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.7.12-050712-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.57 Sun Jul 5 14:42:25 UTC 2020 GCC version: gcc version 10.2.0 (GCC) 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 Date: Sat Aug 1 13:57:56 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] [10de:1e87] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU104 [GeForce RTX 2080 Rev. A] [1462:3726] InstallationDate: Installed on 2020-07-31 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. Z390 AORUS MASTER ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.7.12-050712-lowlatency root=UUID=76f51654-be39-4436-80da-a240e8149ca5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: Default string dmi.board.name: Z390 AORUS MASTER-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/04/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ390AORUSMASTER:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ390AORUSMASTER-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z390 AORUS MASTER dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.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/gnome-shell/+bug/1890001/+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 1890512] [NEW] bluetooth stopped working after recent apt updates
Public bug reported: bluetooth stopped working after recent apt updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 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 06:20:29 2020 InstallationDate: Installed on 2020-03-02 (156 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterestingModules: bluetooth Lsusb: Bus 002 Device 002: ID 1058:25e1 Western Digital Technologies, Inc. My Passport 25E1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 002: ID 24ae:1813 RAPOO Rapoo 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook UX461FN_UX461FN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=68586d80-0dfa-454e-918b-83ddbf1d4c3c ro quiet splash dis_ucode_ldr resume=UUID=014fadee-e595-4994-a198-c7eb8db1fa57 vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-05-21 (76 days ago) dmi.bios.date: 01/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX461FN.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX461FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX461FN.302:bd01/28/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX461FN_UX461FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX461FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: ZenBook UX461FN_UX461FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: mtime.conffile..etc.bluetooth.input.conf: 2020-06-30T20:08:54.584021 mtime.conffile..etc.bluetooth.main.conf: 2020-03-04T03:26:07.238405 ** Affects: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1890512 Title: bluetooth stopped working after recent apt updates Status in bluez package in Ubuntu: New Bug description: bluetooth stopped working after recent apt updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 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 06:20:29 2020 InstallationDate: Installed on 2020-03-02 (156 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterestingModules: bluetooth Lsusb: Bus 002 Device 002: ID 1058:25e1 Western Digital Technologies, Inc. My Passport 25E1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 002: ID 24ae:1813 RAPOO Rapoo 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook UX461FN_UX461FN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=68586d80-0dfa-454e-918b-83ddbf1d4c3c ro quiet splash dis_ucode_ldr resume=UUID=014fadee-e595-4994-a198-c7eb8db1fa57 vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-05-21 (76 days ago) dmi.bios.date: 01/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX461FN.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX461FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX461FN.302:bd01/28/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX461FN_UX461FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX461FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: ZenBook UX461FN_UX461FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: mtime.conffile..etc.bluetooth.input.conf: 2020-06-30T20:08:54.584021 mtime.conffile..etc.bluetooth.main.conf: 2020-03-04T03:26:07.238405 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1890512/+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 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
Given that we've implemented the only known solution for this in bug 1877075, the remaining explanation for it might not be thread-related. Some kind of memory corruption (even single threaded) could have the same effect. -- 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/1886059 Title: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.3-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/5d9a112e0c6aeddb3cf972203bede962f60d767d 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/. Similar error: https://errors.ubuntu.com/problem/14911e4a22eec995bc364278c0490d8bfea557dd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+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 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
Yes that stack looks the same as before. -- 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/1886059 Title: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.3-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/5d9a112e0c6aeddb3cf972203bede962f60d767d 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/. Similar error: https://errors.ubuntu.com/problem/14911e4a22eec995bc364278c0490d8bfea557dd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+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 1873026] Re: File manager grabs favorites folders on left
Hi All, As described on June 20, the bug went away, but it is back now, so there must be some way to make it come and go, but I haven't figured out what I did. Rob -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1873026 Title: File manager grabs favorites folders on left Status in nautilus package in Ubuntu: Fix Released Bug description: Upgraded to beta release of 20.4 and Nautilus file manager now is exhibiting a problem reported in older versions. When clicking on folders in the left side window the folder will be dragged to where ever the mouse is moved. The work around is to click once move slightly then click again to release in the same spot. The other work around is to reboot and sometimes the problem goes away. I believe all this information has be sent when I did the ubuntu-bug command, but here is is again: Release: Ubuntu Focal Fossa (development branch) nautilus:Installed: 1:3.36.1.1-1ubuntu2 Expected behavior: Expected to click on "favorite" folder and be taken to the folder in the right side of screen. Actual behavior: Clicking on "favorite" folder grabbed the folder to drag where ever the cursor went. Need to click again in same place on left screen to release the folder. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 10:28:53 2020 InstallationDate: Installed on 2017-03-19 (1123 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1873026/+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]
Florian - this looks like something that TDF would need to chase to fix ? a nice list of things to do from Pedro; is this something you can handle ? -- 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 1888186] Re: LibreOffice Writer unusably slow
* As originally described, it usually starts to lag within one minute of usage, although not usually from the first character typed. * When I changed to 19.10. This involved a clean install on a new machine and moving my home folder over, rather than an upgrade. * As originally described, it does not appear to affect spreadsheets, and appears to affect any document with more than a page or so of content. It seems to be particularly bad with italic text. (I've tried changing the font, but that doesn't seem to help.) -- 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/1888186 Title: LibreOffice Writer unusably slow Status in libreoffice package in Ubuntu: New Bug description: LibreOffice Writer lags by several seconds per keypress when typing in a document of more than a page or so. This does not always start immediately, but normally begins within a couple of lines of text, and also affects text deletion. The bug does not seem to affect Calc. Also, when I installed Writer alone through Synaptic, without any gnome integration at all, the problem didn't seem to arise, although it looks hideous, so that is not an ideal solution. Removing user preferences did not fix the problem, however. Obviously, this bug does not affect everyone, because it would have been reported already. I hope the apport data provides enough information to pin the problem down. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice 1:6.4.4-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jul 20 14:54:52 2020 InstallationDate: Installed on 2020-01-05 (197 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2020-05-08 (73 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1888186/+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 1890365] Re: [snap] Web Serial fails to access local device
Disabling apparmor for chromium $ sudo ln -s /etc/apparmor.d/usr.bin.chromium-browser /etc/apparmor.d/disable/ $ sudo apparmor_parser -R /etc/apparmor.d/disable/usr.bin.chromium-browser had no effect. Adding "/dev/tty* rw" right below the line for "/dev/null rw" in /etc/apparmor.d/disable/usr.bin.chromium-browser and removing/re-adding the profile had no effect. -- 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/1890365 Title: [snap] Web Serial fails to access local device Status in chromium-browser package in Ubuntu: Incomplete Bug description: A javascript-based web page works fine when accessed through Chrome, fails to recognize that any devices exist when accessed from Chromium on the same Unubtu 20.04 platform. The code includes the following snippet: const requestOptions = { filters: [{ usbVendorId: 0x1881 }] }; port = await navigator.serial.requestPort(requestOptions); await port.open({ baudrate: 9600 }); writer = port.writable.getWriter(); reader = port.readable.getReader(); Under Chrome 84.0.4147.105 (Official Build) (64-bit), ttyACM0 device is listed in the pop-up, is selectable, and can communicate. Under Chromium 84.0.4147.105 (Official Build) snap (64-bit), the pop-up contains only "No compatible devices found" message. Experimental Web Features flag is enabled in both browsers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890365/+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 1843760] Re: Please add a PPA to track only the Still Branch across major versions of LibreOffice
** Changed in: libreoffice (Ubuntu) Importance: Undecided => Wishlist -- 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/1843760 Title: Please add a PPA to track only the Still Branch across major versions of LibreOffice Status in libreoffice package in Ubuntu: New Bug description: Upstream LibreOffice provides two branches of LibreOffice, the Fresh Branch (6.3.0) and the Still Branch (6.2.7). In Ubuntu there is a PPA that tracks the Fresh Branch (LibreOffice Fresh) and separate PPAs that track one major version of LO without crossing to a higher version in the same PPA. I suggest creating a new PPA that tracks only the Still Branch of LibreOffice. Meaning, today the latest version in the still branch is 6.2.6, the last release from the 6.2.x branch is 6.2.7 and its end of life is on November 30, 2019. Afterwards the still branch will track the 6.3.x branch from the 6.3.4 release and so on. So the PPA would have: 6.2.6 ⇒ 6.2.7 (EOL) ⇒ 6.3.4 ⇒ 6.3.5 ⇒ 6.3.6 (EOL) ⇒ 6.4.4 ⇒ 6.4.5 ⇒ 6.4.6 ⇒ ... and so on. The reason why I ask this is that almost always the first three releases of a new major version of LO are buggy and have regressions. The 6.3.0 version that I'm on now is buggy, but at the same time, newer versions of LO fix bugs and UI enhancements that probably will never be backported to older branches like the one in Bionic. So tracking only the Still Branch solves this issue especially for enterprise and school users. The Still Branch PPA would target only the Ubuntu LTS releases, Xenial and Bionic, because it doesn't make sense to target the short-lived releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1843760/+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 1890494] Re: Closing Rhythmbox does not free the media keys
After restarting the machine, launching rhythmbox from the command line does not print messages. Subsequent launches do however -- 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/1890494 Title: Closing Rhythmbox does not free the media keys Status in rhythmbox package in Ubuntu: Incomplete Bug description: Closing Rhythmbox, does not free the media keys, and no program can use them after that, not even Rhythmbox if you restart it. This seems to be very close to bug #1036489, but that one was active 8 years ago, and was marked as expired 6 years ago. Restarting the machine frees the media keys again. Steps to reproduce: 1. Verify that the media keys work (restart the machine if not) 2. close rhythmbox with right click on the taskbar icon, use "stop & quit" 3. reopen rhythmbox, the media keys do not work. 1. Verify that the media keys work (restart the machine if not) 2. End the 'rhythmbox' process 3. reopen rhythmbox, the media keys do not work. 1. Verify that the media keys work (restart the machine if not) 2. in rhythmbox go to preferences -> plugins -> click preferences for any plugin 3. click the 'restart' next to "Restart the player for the changes to take effect" 4. once rhythmbox restarts, the media keys do not work anymore. $ 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1890494/+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 1890494] Re: Closing Rhythmbox does not free the media keys
I am talking about the pause/play, previous song and next song keys. On my Dell xps 13 laptop, those are f4, f5 and f6 (or fn + f4, fn + f5, fn + f6) When opening Rhythmbox from the command line: (this is after having opened and closed it once, so the media keys were already not working) Opening and using rhythmbox does not print error messages, but closing does: /usr/lib/python3/dist-packages/gi/overrides/GObject.py:502: Warning: ../../../gobject/gsignal.c:2735: instance '0x5635f68af300' has no handler with id '12157' return func(*args, **kwargs) /usr/lib/python3/dist-packages/gi/overrides/GObject.py:502: Warning: ../../../gobject/gsignal.c:2735: instance '0x5635f68af300' has no handler with id '12156' return func(*args, **kwargs) /usr/lib/python3/dist-packages/gi/overrides/GObject.py:502: Warning: ../../../gobject/gsignal.c:2735: instance '0x5635f68af300' has no handler with id '40060' return func(*args, **kwargs) I will now restart my machine to launch rhythmbox the first time from the command line (with working media keys) -- 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/1890494 Title: Closing Rhythmbox does not free the media keys Status in rhythmbox package in Ubuntu: Incomplete Bug description: Closing Rhythmbox, does not free the media keys, and no program can use them after that, not even Rhythmbox if you restart it. This seems to be very close to bug #1036489, but that one was active 8 years ago, and was marked as expired 6 years ago. Restarting the machine frees the media keys again. Steps to reproduce: 1. Verify that the media keys work (restart the machine if not) 2. close rhythmbox with right click on the taskbar icon, use "stop & quit" 3. reopen rhythmbox, the media keys do not work. 1. Verify that the media keys work (restart the machine if not) 2. End the 'rhythmbox' process 3. reopen rhythmbox, the media keys do not work. 1. Verify that the media keys work (restart the machine if not) 2. in rhythmbox go to preferences -> plugins -> click preferences for any plugin 3. click the 'restart' next to "Restart the player for the changes to take effect" 4. once rhythmbox restarts, the media keys do not work anymore. $ 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1890494/+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
@Hui, we will get the new version but unsure when so if it's not too much extra work it would be b etter to generate debdiffs for G -- 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-s
[Desktop-packages] [Bug 1890494] Re: Closing Rhythmbox does not free the media keys
Thank you for your bug report. Could you start rhythmbox from a command line and see if any error is printed? What media keys are you talking about exactly? ** Changed in: rhythmbox (Ubuntu) Importance: Undecided => Low ** Changed in: rhythmbox (Ubuntu) Status: New => Incomplete -- 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/1890494 Title: Closing Rhythmbox does not free the media keys Status in rhythmbox package in Ubuntu: Incomplete Bug description: Closing Rhythmbox, does not free the media keys, and no program can use them after that, not even Rhythmbox if you restart it. This seems to be very close to bug #1036489, but that one was active 8 years ago, and was marked as expired 6 years ago. Restarting the machine frees the media keys again. Steps to reproduce: 1. Verify that the media keys work (restart the machine if not) 2. close rhythmbox with right click on the taskbar icon, use "stop & quit" 3. reopen rhythmbox, the media keys do not work. 1. Verify that the media keys work (restart the machine if not) 2. End the 'rhythmbox' process 3. reopen rhythmbox, the media keys do not work. 1. Verify that the media keys work (restart the machine if not) 2. in rhythmbox go to preferences -> plugins -> click preferences for any plugin 3. click the 'restart' next to "Restart the player for the changes to take effect" 4. once rhythmbox restarts, the media keys do not work anymore. $ 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1890494/+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 1890494] [NEW] Closing Rhythmbox does not free the media keys
Public bug reported: Closing Rhythmbox, does not free the media keys, and no program can use them after that, not even Rhythmbox if you restart it. This seems to be very close to bug #1036489, but that one was active 8 years ago, and was marked as expired 6 years ago. Restarting the machine frees the media keys again. Steps to reproduce: 1. Verify that the media keys work (restart the machine if not) 2. close rhythmbox with right click on the taskbar icon, use "stop & quit" 3. reopen rhythmbox, the media keys do not work. 1. Verify that the media keys work (restart the machine if not) 2. End the 'rhythmbox' process 3. reopen rhythmbox, the media keys do not work. 1. Verify that the media keys work (restart the machine if not) 2. in rhythmbox go to preferences -> plugins -> click preferences for any plugin 3. click the 'restart' next to "Restart the player for the changes to take effect" 4. once rhythmbox restarts, the media keys do not work anymore. $ 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 ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- 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/1890494 Title: Closing Rhythmbox does not free the media keys Status in rhythmbox package in Ubuntu: New Bug description: Closing Rhythmbox, does not free the media keys, and no program can use them after that, not even Rhythmbox if you restart it. This seems to be very close to bug #1036489, but that one was active 8 years ago, and was marked as expired 6 years ago. Restarting the machine frees the media keys again. Steps to reproduce: 1. Verify that the media keys work (restart the machine if not) 2. close rhythmbox with right click on the taskbar icon, use "stop & quit" 3. reopen rhythmbox, the media keys do not work. 1. Verify that the media keys work (restart the machine if not) 2. End the 'rhythmbox' process 3. reopen rhythmbox, the media keys do not work. 1. Verify that the media keys work (restart the machine if not) 2. in rhythmbox go to preferences -> plugins -> click preferences for any plugin 3. click the 'restart' next to "Restart the player for the changes to take effect" 4. once rhythmbox restarts, the media keys do not work anymore. $ 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1890494/+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 1036489] Re: Closing Rhythmbox doesn't close Rhythmbox and causes confusing key-binding behavior
This still affects me in Ubuntu 20.04. Fully closing Rhythmbox does not free up the media keys, and if you reopen it later the media keys will not work (and won't work for other programs either) Different ways to reproduce (note that the only way to have the media keys working again is to restart the machine) 1. Verify that the media keys work (restart the machine if not) 2. close rhythmbox with right click on the taskbar icon, use "stop & quit" 3. reopen rhythmbox, the media keys do not work. 1. Verify that the media keys work (restart the machine if not) 2. End the 'rhythmbox' process 3. reopen rhythmbox, the media keys do not work. 1. Verify that the media keys work (restart the machine if not) 2. in rhythmbox go to preferences -> plugins -> click preferences for any plugin 3. click the 'restart' next to "Restart the player for the changes to take effect" 4. once rhythmbox restarts, the media keys do not work anymore. -- 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/1036489 Title: Closing Rhythmbox doesn't close Rhythmbox and causes confusing key- binding behavior Status in rhythmbox package in Ubuntu: Expired Bug description: This is a problem I am experiencing in Quantal right now. Here is how to trigger it: 1. I load Pithos and start listening to music. My track change and start/pause key-bindings work great. 2. I load Rhythmbox to listen to a song on my computer. I stop Pithos playing and start playing Rhythmbox. 3. With two media players open my key-bindings only seem to apply to one player, so I close Rhythmbox (clicking the X in the window). 4. The window is not actually closed and my key-bindings still affect Rhythmbox - this is confusing as I see no icon on my Launcher. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic i686 ApportVersion: 2.4-0ubuntu6 Architecture: i386 Date: Mon Aug 13 21:20:01 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1036489/+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 1890464] Re: Can not scan as user
Great! I suspected that was it because I need to do the same for my own scanner. Not sure whether this obstacle is a bug which can be fixed. Keeping the bug open for now. ** Changed in: sane-backends (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1890464 Title: Can not scan as user Status in sane-backends package in Ubuntu: Confirmed Bug description: # Description I can not scan as user using software like simple-scan or xsane. If I run xsane and simple-scan with sudo, I can use my scanner. It seems to be a permission issue # Step to reproduce 1. Start xsane or simple-scan as user 2. xsane and simple-scan fail to scan, "device is not connected" 3. Start xsane or simple-scan with sudo 4. It works, you can scan # Infos xubuntu 20.04 HP Deskjet 2540 All-in-One Printer antoine@Talos:~$ apt show sane-utils Package: sane-utils Version: 1.0.29-0ubuntu5 antoine@Talos:~$ apt show libsane Package: libsane Version: 1.0.29-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1890464/+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 1890001] Re: Random stuttering while in game
*** This bug is a duplicate of bug 1849142 *** https://bugs.launchpad.net/bugs/1849142 I looked and I already had Ubuntu AppIndicators turned off. -- 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/1890001 Title: Random stuttering while in game Status in gnome-shell package in Ubuntu: Incomplete Bug description: Updated kernel to 5.7.12 and updated nvidia driver to 450 yesterday but only experiencing this today. Random stuttering while playing minecraft, no clue what's causing it but I checked system monitor and it shows random spikes of a cpu thread to 100% and some spikes staying at 100% for a prolonged period. It may be related to me updating my video driver that is not recommended so I will see if switching down will resolve the issue. I never had this issue on driver 440. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.7.12-050712-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.57 Sun Jul 5 14:42:25 UTC 2020 GCC version: gcc version 10.2.0 (GCC) 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 Date: Sat Aug 1 13:57:56 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] [10de:1e87] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU104 [GeForce RTX 2080 Rev. A] [1462:3726] InstallationDate: Installed on 2020-07-31 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. Z390 AORUS MASTER ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.7.12-050712-lowlatency root=UUID=76f51654-be39-4436-80da-a240e8149ca5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: Default string dmi.board.name: Z390 AORUS MASTER-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/04/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ390AORUSMASTER:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ390AORUSMASTER-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z390 AORUS MASTER dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.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/gnome-shell/+bug/1890001/+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 1890365] Re: [snap] Web Serial fails to access local device
Also: it is chroME that is installed as a snap package, chroMIUM is installed through apt-get, and it works just fine: $ journalctl -f | grep chrome Aug 05 15:26:57 slon dbus-daemon[782]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.80' (uid=1000 pid=3623 comm="/home/opt/google/chrome/chrome " label="unconfined") and no additional messages as the "connect" button is clicked and the serial device accessed. -- 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/1890365 Title: [snap] Web Serial fails to access local device Status in chromium-browser package in Ubuntu: Incomplete Bug description: A javascript-based web page works fine when accessed through Chrome, fails to recognize that any devices exist when accessed from Chromium on the same Unubtu 20.04 platform. The code includes the following snippet: const requestOptions = { filters: [{ usbVendorId: 0x1881 }] }; port = await navigator.serial.requestPort(requestOptions); await port.open({ baudrate: 9600 }); writer = port.writable.getWriter(); reader = port.readable.getReader(); Under Chrome 84.0.4147.105 (Official Build) (64-bit), ttyACM0 device is listed in the pop-up, is selectable, and can communicate. Under Chromium 84.0.4147.105 (Official Build) snap (64-bit), the pop-up contains only "No compatible devices found" message. Experimental Web Features flag is enabled in both browsers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890365/+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 1890365] Re: [snap] Web Serial fails to access local device
The output is shown. Please note that no additional lines show up when I load the page that has that javascript code, or on clicking the button that causes the connect attempt. All of that output is already there. $ journalctl -f | grep chromium Aug 05 15:21:33 slon dbus-daemon[1410]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/PowerManagement/Inhibit" interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" mask="send" name="org.freedesktop.PowerManagement" pid=2802 label="snap.chromium.chromium" peer_pid=2397 peer_label="unconfined" Aug 05 15:21:34 slon dbus-daemon[1410]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/PowerManagement/Inhibit" interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" mask="send" name="org.freedesktop.PowerManagement" pid=2802 label="snap.chromium.chromium" peer_pid=2397 peer_label="unconfined" Aug 05 15:21:38 slon dbus-daemon[1410]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/PowerManagement/Inhibit" interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" mask="send" name="org.freedesktop.PowerManagement" pid=2802 label="snap.chromium.chromium" peer_pid=2397 peer_label="unconfined" Aug 05 15:21:43 slon dbus-daemon[1410]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/PowerManagement/Inhibit" interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" mask="send" name="org.freedesktop.PowerManagement" pid=2802 label="snap.chromium.chromium" peer_pid=2397 peer_label="unconfined" Aug 05 15:21:44 slon dbus-daemon[1410]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/PowerManagement/Inhibit" interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" mask="send" name="org.freedesktop.PowerManagement" pid=2802 label="snap.chromium.chromium" peer_pid=2397 peer_label="unconfined" Aug 05 15:21:44 slon dbus-daemon[1410]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/PowerManagement/Inhibit" interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" mask="send" name="org.freedesktop.PowerManagement" pid=2802 label="snap.chromium.chromium" peer_pid=2397 peer_label="unconfined" Aug 05 15:21:44 slon dbus-daemon[1410]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/PowerManagement/Inhibit" interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" mask="send" name="org.freedesktop.PowerManagement" pid=2802 label="snap.chromium.chromium" peer_pid=2397 peer_label="unconfined" Aug 05 15:21:46 slon dbus-daemon[1410]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/PowerManagement/Inhibit" interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" mask="send" name="org.freedesktop.PowerManagement" pid=2802 label="snap.chromium.chromium" peer_pid=2397 peer_label="unconfined" Aug 05 15:21:46 slon dbus-daemon[1410]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/PowerManagement/Inhibit" interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" mask="send" name="org.freedesktop.PowerManagement" pid=2802 label="snap.chromium.chromium" peer_pid=2397 peer_label="unconfined" Aug 05 15:21:46 slon dbus-daemon[1410]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/PowerManagement/Inhibit" interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" mask="send" name="org.freedesktop.PowerManagement" pid=2802 label="snap.chromium.chromium" peer_pid=2397 peer_label="unconfined" Aug 05 15:22:22 slon audit[2802]: AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c166:0" pid=2802 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Aug 05 15:22:22 slon kernel: audit: type=1400 audit(1596655342.601:44): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c166:0" pid=2802 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Aug 05 15:22:45 slon audit[782]: USER_AVC pid=782 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=3305 label="snap.chromium.chromium" Aug 05 15:22:45 slon kernel: audit: type=1107 audit(1596655365.450:45): pid=782 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=3305 label="snap.chromium.chromium" -- You received this bug notification because you are a member of Desktop Packages, whi
[Desktop-packages] [Bug 1890464] Re: Can not scan as user
Thank you I added myself in the lp group antoine@Talos:~$ groups antoine antoine : antoine adm cdrom sudo dip plugdev lpadmin lxd sambashare antoine@Talos:~$ sudo adduser $USER lp [sudo] Mot de passe de antoine : Ajout de l'utilisateur « antoine » au groupe « lp »... Ajout de l'utilisateur antoine au groupe lp Fait. antoine@Talos:~$ groups antoine antoine : antoine adm lp cdrom sudo dip plugdev lpadmin lxd sambashare antoine@Talos:~$ then I tried simple-scan and it is working This issue is fixed for me, I do not know why I was not in the lp group -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1890464 Title: Can not scan as user Status in sane-backends package in Ubuntu: Incomplete Bug description: # Description I can not scan as user using software like simple-scan or xsane. If I run xsane and simple-scan with sudo, I can use my scanner. It seems to be a permission issue # Step to reproduce 1. Start xsane or simple-scan as user 2. xsane and simple-scan fail to scan, "device is not connected" 3. Start xsane or simple-scan with sudo 4. It works, you can scan # Infos xubuntu 20.04 HP Deskjet 2540 All-in-One Printer antoine@Talos:~$ apt show sane-utils Package: sane-utils Version: 1.0.29-0ubuntu5 antoine@Talos:~$ apt show libsane Package: libsane Version: 1.0.29-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1890464/+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 1888186] Re: LibreOffice Writer unusably slow
Can you tell me a little more.. * Does Libreoffice display this lag immediately or does it take some time of the app running before it becomes unusably slow? * When did this problem start? * Does this happen on an empty document/spreadsheet or does can you point to an example problematic document? -- 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/1888186 Title: LibreOffice Writer unusably slow Status in libreoffice package in Ubuntu: New Bug description: LibreOffice Writer lags by several seconds per keypress when typing in a document of more than a page or so. This does not always start immediately, but normally begins within a couple of lines of text, and also affects text deletion. The bug does not seem to affect Calc. Also, when I installed Writer alone through Synaptic, without any gnome integration at all, the problem didn't seem to arise, although it looks hideous, so that is not an ideal solution. Removing user preferences did not fix the problem, however. Obviously, this bug does not affect everyone, because it would have been reported already. I hope the apport data provides enough information to pin the problem down. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice 1:6.4.4-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jul 20 14:54:52 2020 InstallationDate: Installed on 2020-01-05 (197 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2020-05-08 (73 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1888186/+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 1890464] Re: Can not scan as user
Try to add yourself to the lp group: sudo adduser $USER lp and let us know if it helps. ** Changed in: sane-backends (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1890464 Title: Can not scan as user Status in sane-backends package in Ubuntu: Incomplete Bug description: # Description I can not scan as user using software like simple-scan or xsane. If I run xsane and simple-scan with sudo, I can use my scanner. It seems to be a permission issue # Step to reproduce 1. Start xsane or simple-scan as user 2. xsane and simple-scan fail to scan, "device is not connected" 3. Start xsane or simple-scan with sudo 4. It works, you can scan # Infos xubuntu 20.04 HP Deskjet 2540 All-in-One Printer antoine@Talos:~$ apt show sane-utils Package: sane-utils Version: 1.0.29-0ubuntu5 antoine@Talos:~$ apt show libsane Package: libsane Version: 1.0.29-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1890464/+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 474612] Re: [Transmission] "Peer not found. Restart the torrent." message extremely often
This is still an issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/474612 Title: [Transmission] "Peer not found. Restart the torrent." message extremely often Status in transmission package in Ubuntu: Invalid Bug description: Binary package hint: transmission I get extremely often the message (for some of the torrents in a disorderly manner): Tracker gave an error: Peer not found. Restart the torrent. - Idle And, of course, Transmission DOES NOT restart these torrents automatically. In the end of the day I realize that I do not seed the most part of my downloaded torrents. ProblemType: Bug Architecture: amd64 Date: Wed Nov 4 21:28:05 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/transmission InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) Package: transmission-gtk 1.75-0ubuntu2 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: transmission Uname: Linux 2.6.31-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/474612/+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 1890321] Re: package chromium-browser 83.0.4103.97-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before atte
Can you try re-installing the package, and let us know how this goes? sudo apt reinstall chromium-browser ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/1890321 Title: package chromium-browser 83.0.4103.97-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in chromium-browser package in Ubuntu: Incomplete Bug description: Unable to install ProblemType: Package 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 ApportVersion: 2.20.11-0ubuntu27.4 AptOrdering: chromium-browser:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Aug 4 21:23:44 2020 Dependencies: DpkgTerminalLog: dpkg: error processing package chromium-browser (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2020-07-30 (4 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 83.0.4103.97-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal 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/1890321/+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 1890446] Re: package firefox 78.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 127
Can you try running the following command in a terminal, and let us know how it goes? sudo apt reinstall firefox ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/1890446 Title: package firefox 78.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 127 Status in firefox package in Ubuntu: Incomplete Bug description: system generated bug info ProblemType: Package DistroRelease: Ubuntu 20.04 Package: firefox 78.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edward 1616 F pulseaudio BuildID: 20200630195452 CasperMD5CheckResult: skip Channel: Unavailable Date: Wed Aug 5 18:47:48 2020 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 127 ForcedLayersAccel: False InstallationDate: Installed on 2020-06-10 (55 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto static metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.54 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 78.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 0FGN4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd02/14/2020:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.product.sku: 078C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1890446/+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 1890365] Re: Web Serial fails to access local device
This is most likely the snap strict confinement that prevents communication with the serial device. Can you please run the following command in a terminal, then run chromium and reproduce the problem, and share the output of the terminal here? journalctl -f | grep chromium ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete ** Summary changed: - Web Serial fails to access local device + [snap] Web Serial fails to access local device ** Tags added: snap -- 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/1890365 Title: [snap] Web Serial fails to access local device Status in chromium-browser package in Ubuntu: Incomplete Bug description: A javascript-based web page works fine when accessed through Chrome, fails to recognize that any devices exist when accessed from Chromium on the same Unubtu 20.04 platform. The code includes the following snippet: const requestOptions = { filters: [{ usbVendorId: 0x1881 }] }; port = await navigator.serial.requestPort(requestOptions); await port.open({ baudrate: 9600 }); writer = port.writable.getWriter(); reader = port.readable.getReader(); Under Chrome 84.0.4147.105 (Official Build) (64-bit), ttyACM0 device is listed in the pop-up, is selectable, and can communicate. Under Chromium 84.0.4147.105 (Official Build) snap (64-bit), the pop-up contains only "No compatible devices found" message. Experimental Web Features flag is enabled in both browsers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890365/+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 1890446] Re: package firefox 78.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 127
Relevant excerpt from DpkgTerminalLog.txt: Preparing to unpack .../19-firefox_79.0+build1-0ubuntu0.20.04.1_amd64.deb ... /var/lib/dpkg/tmp.ci/preinst: 1: awk: Too many levels of symbolic links Exception ignored in: <_io.TextIOWrapper name='' mode='w' encoding='utf-8'> BrokenPipeError: [Errno 32] Broken pipe /var/lib/dpkg/tmp.ci/preinst: 1: awk: Too many levels of symbolic links Exception ignored in: <_io.TextIOWrapper name='' mode='w' encoding='utf-8'> BrokenPipeError: [Errno 32] Broken pipe -- 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/1890446 Title: package firefox 78.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 127 Status in firefox package in Ubuntu: Incomplete Bug description: system generated bug info ProblemType: Package DistroRelease: Ubuntu 20.04 Package: firefox 78.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edward 1616 F pulseaudio BuildID: 20200630195452 CasperMD5CheckResult: skip Channel: Unavailable Date: Wed Aug 5 18:47:48 2020 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 127 ForcedLayersAccel: False InstallationDate: Installed on 2020-06-10 (55 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto static metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.54 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 78.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 0FGN4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd02/14/2020:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.product.sku: 078C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1890446/+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 1890049] Re: global menu bar no longer supported after 20.04 upgrade
Although the absence of a global menubar in GNOME by default did influence this particular decision, the main factor was the increasing difficulty to maintain the firefox patch that enabled the feature. The patch was quite large (several thousands LOC) and heavily relied on internal APIs that have been changing significantly in the past few releases. I appreciate this is a functional regression for users of Unity and other desktop environments with a global menu bar, but this is a trade- off that had to be made to ensure timely updates for future firefox releases. -- 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/1890049 Title: global menu bar no longer supported after 20.04 upgrade Status in firefox package in Ubuntu: Won't Fix Bug description: 1) version: 79.0+build1-0ubuntu0.20.04.1 500 2) Ubuntu Release : Ubuntu 20.04.1 LTS 3) What I expected to happen: In Unity DE. menu bars are integrated with title bar or top panel when maximized 4) What happened instead: Menu bar doesn't integrate. Takes too much vertical space. Problematic because I have made a jump to wide screens around 2012. I guess decision makers at ubuntu still enjoy 4:3 screens and thus don't see the value in DEs that optimize vertical space. But it would be really nice to have a hand here. The current workaround is to disable the menu bar, which leaves me at the mercy of the hamburger menu. The hamburger menu is an implant from old Mobile App Design. But nowadays even Mobile App UX designers decry the Hamburger menu and in a desktop it makes little sense. Firefox is a good example because the menu bar has sections like History which are a lot richer than what's available to be accessed from the hamburger menu. It's really just not possible to have as many menu options and categories as a menu bar in a hamburger menu. And access is less efficient -> more mouse movement -> more mouse clicks. So I have to choose between wasting space unnecessarily with a menu bar that does not integrate with the top panel OR losing a lot of access to options and settings by removing the menu bar and using the hamburger menu instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1890049/+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 1890464] Re: Can not scan as user
** Package changed: ubuntu => sane-backends (Ubuntu) ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1890464 Title: Can not scan as user Status in sane-backends package in Ubuntu: New Bug description: # Description I can not scan as user using software like simple-scan or xsane. If I run xsane and simple-scan with sudo, I can use my scanner. It seems to be a permission issue # Step to reproduce 1. Start xsane or simple-scan as user 2. xsane and simple-scan fail to scan, "device is not connected" 3. Start xsane or simple-scan with sudo 4. It works, you can scan # Infos xubuntu 20.04 HP Deskjet 2540 All-in-One Printer antoine@Talos:~$ apt show sane-utils Package: sane-utils Version: 1.0.29-0ubuntu5 antoine@Talos:~$ apt show libsane Package: libsane Version: 1.0.29-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1890464/+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 1890464] [NEW] Can not scan as user
You have been subscribed to a public bug: # Description I can not scan as user using software like simple-scan or xsane. If I run xsane and simple-scan with sudo, I can use my scanner. It seems to be a permission issue # Step to reproduce 1. Start xsane or simple-scan as user 2. xsane and simple-scan fail to scan, "device is not connected" 3. Start xsane or simple-scan with sudo 4. It works, you can scan # Infos xubuntu 20.04 HP Deskjet 2540 All-in-One Printer antoine@Talos:~$ apt show sane-utils Package: sane-utils Version: 1.0.29-0ubuntu5 antoine@Talos:~$ apt show libsane Package: libsane Version: 1.0.29-0ubuntu5 ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment permission scanner -- Can not scan as user https://bugs.launchpad.net/bugs/1890464 You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends 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 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop
** Tags added: originate-from-1874593 sutton -- 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 ucm-simpl
[Desktop-packages] [Bug 1890436] Re: Screen corruption with multi monitor setup
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1890436 Title: Screen corruption with multi monitor setup Status in xorg package in Ubuntu: New 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/xorg/+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] [NEW] Screen corruption with multi monitor setup
You have been subscribed to a public bug: 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal third-party-packages ubuntu -- Screen corruption with multi monitor setup https://bugs.launchpad.net/bugs/1890436 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838152] Re: gnome-shell freezes on notification arrival (fixed upstream)
** Tags added: rls-bb-incoming -- 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 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 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
I've just got a similar crash when just clicking on a menu item, I've got some more complete stacktrace, but don't think is really helpful #0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 set = {__val = {0, 548, 549, 550, 551, 552, 553, 554, 555, 556, 557, 558, 559, 15822592872050180864, 94249823962208, 94249845226528}} pid = tid = #1 0x55b83f47052a in () #2 0x7f45908a3210 in () at /lib/x86_64-linux-gnu/libc.so.6 #3 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 set = {__val = {0, 139936754804816, 94252984795136, 94250118475456, 94250118475557, 94250118475456, 94250118475456, 94250118475568, 94250118475756, 94250118475456, 94250118475756, 0, 0, 0, 0, 0}} pid = tid = #4 0x7f4590882859 in __GI_abort () at abort.c:79 save_stage = 1 act = {__sigaction_handler = {sa_handler = 0x5, sa_sigaction = 0x5}, sa_mask = {__val = {112, 4, 48320015904, 0, 0, 139936755958789, 0, 21474836480, 140735042337344, 139936638613175, 139936638613175, 0, 15822592872050180864, 139936755958789, 139935137267712, 139936638613175}}, sa_flags = -1874503997, sa_restorer = 0x104} sigs = {__val = {32, 0 }} #5 0x7f4590882729 in __assert_fail_base (fmt=0x7f4589a2b6b7 , assertion=0x7f4590455858 "!xcb_xlib_threads_sequence_lost", file=0x7f45904556c3 "../../src/xcb_io.c", line=260, function=) at assert.c:92 str = 0x55b850d16780 "\220ŻE\270U" total = 4096 #6 0x7f4590893f36 in __GI___assert_fail (assertion=assertion@entry=0x7f4590455858 "!xcb_xlib_threads_sequence_lost", file=file@entry=0x7f45904556c3 "../../src/xcb_io.c", line=line@entry=260, function=function@entry=0x7f4590455b10 <__PRETTY_FUNCTION__.14999> "poll_for_event") at assert.c:101 #7 0x7f45903e1493 in poll_for_event (dpy=dpy@entry=0x55b83fee4000, queued_only=queued_only@entry=0) at ../../src/xcb_io.c:260 request = req = event = event_sequence = __PRETTY_FUNCTION__ = "poll_for_event" #8 0x7f45903e153d in poll_for_response (dpy=dpy@entry=0x55b83fee4000) at ../../src/xcb_io.c:278 response = error = 0x55b83fee4000 req = __PRETTY_FUNCTION__ = "poll_for_response" #9 0x7f45903e183a in _XEventsQueued (mode=, dpy=0x55b83fee4000) at ../../src/xcb_io.c:362 response = #10 _XEventsQueued (dpy=0x55b83fee4000, mode=) at ../../src/xcb_io.c:344 #11 0x7f45903e482d in _XGetRequest (dpy=dpy@entry=0x55b83fee4000, type=type@entry=43 '+', len=len@entry=4) at ../../src/XlibInt.c:1764 req = --Type for more, q to quit, c to continue without paging-- #12 0x7f45903dd62f in XSync (dpy=0x55b83fee4000, discard=discard@entry=0) at ../../src/Sync.c:43 rep = {type = 48 '0', revertTo = 236 '\354', sequenceNumber = 16408, length = 21944, focus = 1073049456, pad1 = 21944, pad2 = 1, pad3 = 0, pad4 = 2288196592, pad5 = 32581} #13 0x7f459054ba53 in _cogl_winsys_onscreen_bind (onscreen=) at ../cogl/cogl/winsys/cogl-winsys-glx.c:1553 context = 0x55b83ff3aaa0 glx_context = 0x55b83ff3b450 glx_display = xlib_renderer = 0x7f457c001d60 glx_renderer = xlib_onscreen = glx_onscreen = old_state = {old_error_handler = 0x7f459073bc70, trapped_error_code = 0, old_state = 0x0} drawable = 2097170 #14 0x7f459050a8eb in _cogl_framebuffer_gl_bind (framebuffer=0x55b84018e7d0, target=36160) at ../cogl/cogl/driver/gl/cogl-framebuffer-gl.c:284 winsys = ctx = 0x55b83ff3aaa0 #15 0x7f459050aec5 in _cogl_framebuffer_gl_flush_state (draw_buffer=0x55b84018e7d0, read_buffer=0x55b84018e7d0, state=(COGL_FRAMEBUFFER_STATE_BIND | COGL_FRAMEBUFFER_STATE_VIEWPORT | COGL_FRAMEBUFFER_STATE_CLIP | COGL_FRAMEBUFFER_STATE_DITHER | COGL_FRAMEBUFFER_STATE_MODELVIEW | COGL_FRAMEBUFFER_STATE_PROJECTION | COGL_FRAMEBUFFER_STATE_FRONT_FACE_WINDING | COGL_FRAMEBUFFER_STATE_DEPTH_WRITE | COGL_FRAMEBUFFER_STATE_STEREO_MODE)) at ../cogl/cogl/driver/gl/cogl-framebuffer-gl.c:386 ctx = 0x55b83ff3aaa0 differences = 511 bit = __func__ = "_cogl_framebuffer_gl_flush_state" #16 0x7f4590541c5a in _cogl_framebuffer_flush_state (state=(COGL_FRAMEBUFFER_STATE_BIND | COGL_FRAMEBUFFER_STATE_VIEWPORT | COGL_FRAMEBUFFER_STATE_CLIP | COGL_FRAMEBUFFER_STATE_DITHER | COGL_FRAMEBUFFER_STATE_MODELVIEW | COGL_FRAMEBUFFER_STATE_PROJECTION | COGL_FRAMEBUFFER_STATE_FRONT_FACE_WINDING | COGL_FRAMEBUFFER_STATE_DEPTH_WRITE | COGL_FRAMEBUFFER_STATE_STEREO_MODE), read_buffer=0x55b84018e7d0, draw_buffer=0x55b84018e7d0) at ../cogl/cogl/cogl-framebuffer.c:887 ctx = clip_stack = had_depth_and_color_buffer_bits = scissor_x0 = 0 scissor_y0 = 0 scissor_x1 = 2147483647 scissor_y1 = 2147483647 #17 cogl_framebuffer_cl
[Desktop-packages] [Bug 1890446] [NEW] package firefox 78.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 127
Public bug reported: system generated bug info ProblemType: Package DistroRelease: Ubuntu 20.04 Package: firefox 78.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edward 1616 F pulseaudio BuildID: 20200630195452 CasperMD5CheckResult: skip Channel: Unavailable Date: Wed Aug 5 18:47:48 2020 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 127 ForcedLayersAccel: False InstallationDate: Installed on 2020-06-10 (55 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto static metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.54 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 78.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 0FGN4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd02/14/2020:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.product.sku: 078C dmi.sys.vendor: Dell Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package 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/1890446 Title: package firefox 78.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 127 Status in firefox package in Ubuntu: New Bug description: system generated bug info ProblemType: Package DistroRelease: Ubuntu 20.04 Package: firefox 78.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edward 1616 F pulseaudio BuildID: 20200630195452 CasperMD5CheckResult: skip Channel: Unavailable Date: Wed Aug 5 18:47:48 2020 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 127 ForcedLayersAccel: False InstallationDate: Installed on 2020-06-10 (55 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto static metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.54 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 78.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 0FGN4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd02/14/2020:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.product.sku: 078C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.laun
[Desktop-packages] [Bug 1890446] Re: package firefox 78.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 127
** Tags removed: need-duplicate-check -- 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/1890446 Title: package firefox 78.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 127 Status in firefox package in Ubuntu: New Bug description: system generated bug info ProblemType: Package DistroRelease: Ubuntu 20.04 Package: firefox 78.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edward 1616 F pulseaudio BuildID: 20200630195452 CasperMD5CheckResult: skip Channel: Unavailable Date: Wed Aug 5 18:47:48 2020 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 127 ForcedLayersAccel: False InstallationDate: Installed on 2020-06-10 (55 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto static metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.54 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 78.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 0FGN4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd02/14/2020:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.product.sku: 078C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1890446/+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 1889460] Re: Missing font after $LANG change
Yes, its related to https://bugs.launchpad.net/bugs/1839022 I installed fixed font from 1839022 and Libreoffice display Ubuntu Light. -- 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/1889460 Title: Missing font after $LANG change Status in libreoffice package in Ubuntu: New Bug description: When $LANG is set for example to: "pl_PL.UTF-8" or "en_GB.utf8" certain fonts are not displayed on font list - for example Ubuntu Light, Ubuntu Thin. When $LANG is unset - all fonts are displayed on font list - for example Ubuntu Light, Ubuntu Thin. Tested on OS: Ubuntu 18.04.04 LTS, LiveCD Kubuntu 20.04.01 LTS, in calc and writer. Version: 6.4.4-0ubuntu0.20.04.1, 6.0.7-0ubuntu0.18.04.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1889460/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
Same here Ununtu 20.04 with Anker Soundcore life Q10, what is worse it that ofono/phonesim can't be used properly, no stable version for Ubuntu 20.04 and no proper instructions to set it up... Please help!!! -- 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/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+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 1857947] Re: gnome-shell crashed with SIGSEGV in get_top_visible_window_actor() from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack() from stack_tracker_sync_s
This crash doesn't seem to reproduce anymore, and there's no trace of it in e.u.c since version 3.36.4 went in proposed. ❯ apt-cache policy libmutter-6-0 libmutter-6-0: Installed: 3.36.4-0ubuntu0.20.04.2 Candidate: 3.36.4-0ubuntu0.20.04.2 Version table: *** 3.36.4-0ubuntu0.20.04.2 500 500 http://it.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.36.3-0ubuntu0.20.04.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 3.36.1-3ubuntu3 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1857947 Title: gnome-shell crashed with SIGSEGV in get_top_visible_window_actor() from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack() from stack_tracker_sync_stack_later() from call_later_func() Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] GNOME Shell crashes [ Test case ] Four-finger gesture seems to trigger it, in any case it can be monitored via - https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 [ Regression potential ] Windows might not be closed correctly when requested via delete-events (clicking on clientside decoration close button). The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.1+git20191024-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 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/mutter/+bug/1857947/+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.
Was wrong package ** Package changed: apport (Ubuntu) => xorg-server (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/1890411 Title: Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri. 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 Corporation H81 Express LP
[Desktop-packages] [Bug 1876894] Re: Scaling is not reverted properly (appears shrunk) when disabling fractional scaling
Reverting to both 100% and 200% works fine, without issues. g-c-c now requires a further "apply" to turn it off, and mutter reacts properly when setting it back to both 200% and 100%. marco-ThinkPad-X1-Carbon-7th ~ 13:22:00 ❯ apt-cache policy libmutter-6-0 libmutter-6-0: Installed: 3.36.4-0ubuntu0.20.04.2 Candidate: 3.36.4-0ubuntu0.20.04.2 Version table: *** 3.36.4-0ubuntu0.20.04.2 500 500 http://it.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.36.3-0ubuntu0.20.04.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 3.36.1-3ubuntu3 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages marco-ThinkPad-X1-Carbon-7th ~ 13:22:02 ❯ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.36.4-0ubuntu1 Candidate: 1:3.36.4-0ubuntu1 Version table: *** 1:3.36.4-0ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1876894 Title: Scaling is not reverted properly (appears shrunk) when disabling fractional scaling Status in gnome-control-center package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: * Impact Scaling is not reverted properly (appears shrunk) when disabling fractional scaling * Test Case Do this in an Ubuntu/Xorg session: 0. Be on a "clean" system wrt. fractional scaling, i.e. disabled & scaling at 100% 1. Open gnome-control-center → displays 2. Turn on fractional scaling 3. Select 125% 4. Press apply (the scaling should correctly change now) 5. Turn off fractional scaling by changing the toggle Now everything is shrunk - it's not been returned to 100% properly. See the attached screenshot where the text is tiny instead of regular 100% size. If you do this instead of step 5: 5. Select 100% scaling 7. Press apply 8. Turn off fractional scaling by changing the toggle Then everything returns to the normal size. Repeat the same selecting 200% at 5., (or 100% if 200% was your default) and ensure it's applied. I'm on nvidia(-440), but Séb said that he saw this on his Intel machine too. * Regression potential Verify that scaling changes are correctly applied on different setup ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue May 5 10:57:40 2020 InstallationDate: Installed on 2012-10-07 (2766 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-01-16 (109 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876894/+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 1884754] Re: Fractional scaling does not persist while resizing or rebooting in VM windows
Marking this verified again, as it was verified as fixed in version 3.36.4-0ubuntu0.20.04.1 (see [1] and [2]), so given that the changes in .2 [3] do not affect this behavior, we can safely consider it already verified. [1] https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/comments/16 [2] https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/comments/18 [3] https://launchpadlibrarian.net/490341554/mutter_3.36.4-0ubuntu0.20.04.1_3.36.4-0ubuntu0.20.04.2.diff.gz ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1884754 Title: Fractional scaling does not persist while resizing or rebooting in VM windows Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] Related to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593, https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860, but those report the issues are fixed. They also do not mention the VMware specific issues. [ Test case ] Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done automatically with Easy Install), go to settings, enable Fractional Scaling and select any non-integer value. Results: - The scaling is applied - After next reboot the setting is reverted to 100%, but should use previous value [ Regression potential ] Resolution doesn't adapt properly to the vmware player window size. --- ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 04:30:21 2020 InstallationDate: Installed on 2020-06-22 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/+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 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
Marking this verified again, as it was verified as fixed in version 3.36.4-0ubuntu0.20.04.1 (see [1] and [2]), so given that the changes in .2 [3] do not affect this behavior, we can safely consider it already verified. [1] https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873403/comments/30 [2] https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/comments/31 [3] https://launchpadlibrarian.net/490341554/mutter_3.36.4-0ubuntu0.20.04.1_3.36.4-0ubuntu0.20.04.2.diff.gz ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers package in Ubuntu: Won't Fix Status in mutter source package in Focal: Fix Committed Status in nvidia-graphics-drivers source package in Focal: Won't Fix Bug description: [ Impact ] When the nvidia driver is installed, the screen turns off when trying to set some fractional scaling values like 150%. And it stays off even after rebooting and logging in again. And from ssh I can see there's no current mode set anymore (just like in bug 1869750): $ xrandr Screen 0: minimum 8 x 8, current 960 x 600, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 connected primary (normal left inverted right x axis y axis) 1920x1200 59.95 + 59.88 [ Test case ] In a Nvidia system: - From g-c-c enable fractional scaling - Set all the available fractional scaling values and ensure they work + In any case the screen should be turned off [ Regression potential ] Wrong screen size is set and panning might be enabled. --- ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 17 15:51:15 2020 InstallationDate: Installed on 2020-02-03 (73 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873403/+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] [NEW] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
You have been subscribed to a public bug: 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 Corporation H81 Express LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c) ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- Xorg crash
[Desktop-packages] [Bug 1886996] Re: Restore previous configuration after turning off fractional scaling does not work
Confirm the test case works correctly here: ❯ apt-cache policy libmutter-6-0 libmutter-6-0: Installed: 3.36.4-0ubuntu0.20.04.2 Candidate: 3.36.4-0ubuntu0.20.04.2 Version table: *** 3.36.4-0ubuntu0.20.04.2 500 500 http://it.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.36.3-0ubuntu0.20.04.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 3.36.1-3ubuntu3 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages ❯ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.36.4-0ubuntu1 Candidate: 1:3.36.4-0ubuntu1 Version table: *** 1:3.36.4-0ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1886996 Title: Restore previous configuration after turning off fractional scaling does not work Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] It's not possible to restore the application a non-fractional scaling configuration when fractional scaling was previously enabled and applied. [ Test case ] 1. From control center, display panel, enable fractional scaling 2. Set scaling to some fractional value and apply and confirm it. 3. Turn off the fractional scaling switch and apply it 4. Fractional scaling should be reverted to the selected integer scaling. 5. When gnome-shell shows the confirmation dialog, click "Revert Settings" 6. Expect the fractional scaling to be re-enabled and applied as it used to be [ Regression potential ] - Configuration can't be applied - Scaling (fractional or not) is not properly applied in single and multi-monitor - Fractional scaling can't be toggled anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1886996/+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 1890427] Re: package libp11-kit-gnome-keyring (not installed) failed to install/upgrade: trying to overwrite '/usr/share/p11-kit/modules/gnome-keyring.module', which is also in
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1890427 Title: package libp11-kit-gnome-keyring (not installed) failed to install/upgrade: trying to overwrite '/usr/share/p11-kit/modules /gnome-keyring.module', which is also in package gnome-keyring- pkcs11:amd64 3.36.0-1ubuntu1 Status in gnome-keyring package in Ubuntu: New Bug description: bug while installing wine ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libp11-kit-gnome-keyring (not installed) 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 Date: Wed Aug 5 12:37:37 2020 DuplicateSignature: package:libp11-kit-gnome-keyring:(not installed) Unpacking libpng12-0:i386 (1.2.50-1ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-FSmyoz/000-libpng12-0_1.2.50-1ubuntu2_i386.deb (--unpack): unable to install new version of '/usr/lib/i386-linux-gnu/libpng12.so.0': No such file or directory ErrorMessage: trying to overwrite '/usr/share/p11-kit/modules/gnome-keyring.module', which is also in package gnome-keyring-pkcs11:amd64 3.36.0-1ubuntu1 InstallationDate: Installed on 2020-07-20 (15 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: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 2.7.5-5ubuntu3 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: gnome-keyring Title: package libp11-kit-gnome-keyring (not installed) failed to install/upgrade: trying to overwrite '/usr/share/p11-kit/modules/gnome-keyring.module', which is also in package gnome-keyring-pkcs11:amd64 3.36.0-1ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1890427/+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 1890427] [NEW] package libp11-kit-gnome-keyring (not installed) failed to install/upgrade: trying to overwrite '/usr/share/p11-kit/modules/gnome-keyring.module', which is also
Public bug reported: bug while installing wine ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libp11-kit-gnome-keyring (not installed) 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 Date: Wed Aug 5 12:37:37 2020 DuplicateSignature: package:libp11-kit-gnome-keyring:(not installed) Unpacking libpng12-0:i386 (1.2.50-1ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-FSmyoz/000-libpng12-0_1.2.50-1ubuntu2_i386.deb (--unpack): unable to install new version of '/usr/lib/i386-linux-gnu/libpng12.so.0': No such file or directory ErrorMessage: trying to overwrite '/usr/share/p11-kit/modules/gnome-keyring.module', which is also in package gnome-keyring-pkcs11:amd64 3.36.0-1ubuntu1 InstallationDate: Installed on 2020-07-20 (15 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: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 2.7.5-5ubuntu3 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: gnome-keyring Title: package libp11-kit-gnome-keyring (not installed) failed to install/upgrade: trying to overwrite '/usr/share/p11-kit/modules/gnome-keyring.module', which is also in package gnome-keyring-pkcs11:amd64 3.36.0-1ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1890427 Title: package libp11-kit-gnome-keyring (not installed) failed to install/upgrade: trying to overwrite '/usr/share/p11-kit/modules /gnome-keyring.module', which is also in package gnome-keyring- pkcs11:amd64 3.36.0-1ubuntu1 Status in gnome-keyring package in Ubuntu: New Bug description: bug while installing wine ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libp11-kit-gnome-keyring (not installed) 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 Date: Wed Aug 5 12:37:37 2020 DuplicateSignature: package:libp11-kit-gnome-keyring:(not installed) Unpacking libpng12-0:i386 (1.2.50-1ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-FSmyoz/000-libpng12-0_1.2.50-1ubuntu2_i386.deb (--unpack): unable to install new version of '/usr/lib/i386-linux-gnu/libpng12.so.0': No such file or directory ErrorMessage: trying to overwrite '/usr/share/p11-kit/modules/gnome-keyring.module', which is also in package gnome-keyring-pkcs11:amd64 3.36.0-1ubuntu1 InstallationDate: Installed on 2020-07-20 (15 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: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 2.7.5-5ubuntu3 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: gnome-keyring Title: package libp11-kit-gnome-keyring (not installed) failed to install/upgrade: trying to overwrite '/usr/share/p11-kit/modules/gnome-keyring.module', which is also in package gnome-keyring-pkcs11:amd64 3.36.0-1ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1890427/+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 1890271] Re: [20.04.01] The system cannot be shut down after clicking the "Power off" option on the OEM installation mode
It's reproducible in a VM. There is no related message in the journal. ** Package changed: ubuntu => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- 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/1890271 Title: [20.04.01] The system cannot be shut down after clicking the "Power off" option on the OEM installation mode Status in gnome-shell package in Ubuntu: Confirmed Bug description: [Summary] After entering the OEM installation mode and then clicking the "Power off" option, the system cannot be powered off. [Steps to reproduce] 1. Plug the USB key which has the 20.04.01 build 2. Power on the system 3. Select USB drive to launch the grub menu 4. Select "OEM installation" to run the installation 5. After entering the OEM installation page, click the "Power off" option. 6. Check if the system can be powered off [Expected result] The system can be powered off after clicking the "Power off" option [Actual result] There is no response after clicking the "Power off" option [Failure rate] 3/3 [Additional information] system-manufacturer: LENOVO system-product-name: P920 CPU: Intel(R) Xeon(R) Gold 6230N CPU @ 2.30GHz GPU: nVidia - 10de:1e30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890271/+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