[Desktop-packages] [Bug 1875528] Re: Extra frozen / stuck mouse cursor after auto screen lock / sleep
Yes that's a common workaround with touchpads. Although as I understand it, this bug is about there being too many cursors. The fact that one of them is frozen is not a problem in itself. If you have an actual problem with a frozen cursor making the system unusable then please open a new bug. -- 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/1875528 Title: Extra frozen / stuck mouse cursor after auto screen lock / sleep Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: Expected: After my computer had gone to sleep and I log in I should see only a single active mouse cursor. What happened instead: After my computer had gone to sleep and I logged in I noticed a second frozen/stuck mouse cursor was on screen and was rendered in one place over any active application windows. I recently upgraded to 20.04 from 19.10 but the same issue was occurring in 19.10 as well. Logging out completely then logging back in again removed the extra frozen cursor. lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy mutter mutter: Installed: 3.36.1-3ubuntu3 Candidate: 3.36.1-3ubuntu3 Version table: *** 3.36.1-3ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 19:53:03 2020 InstallationDate: Installed on 2019-03-09 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-04-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1875528/+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 1875528] Re: Extra frozen / stuck mouse cursor after auto screen lock / sleep
The guy here has posted a solution which worked for me. https://dev.to/akarsh77/does-your-laptop-touch-pad-becomes-unresponsive-or-gets-stuck-in-ubuntu-or-ubuntu-based-systems-1npm Open the terminal and type these commands sudo modprobe -r psmouse sudo modprobe psmouse this will free the mouse from frozen state. :) -- 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/1875528 Title: Extra frozen / stuck mouse cursor after auto screen lock / sleep Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: Expected: After my computer had gone to sleep and I log in I should see only a single active mouse cursor. What happened instead: After my computer had gone to sleep and I logged in I noticed a second frozen/stuck mouse cursor was on screen and was rendered in one place over any active application windows. I recently upgraded to 20.04 from 19.10 but the same issue was occurring in 19.10 as well. Logging out completely then logging back in again removed the extra frozen cursor. lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy mutter mutter: Installed: 3.36.1-3ubuntu3 Candidate: 3.36.1-3ubuntu3 Version table: *** 3.36.1-3ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 19:53:03 2020 InstallationDate: Installed on 2019-03-09 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-04-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1875528/+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 1912530] Re: gnome-shell crashed with SIGSEGV
Hello, I deleted `sound-output-device-chooser` & `gnome-shell-screenshot` I've also launch the command you sent. -- 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/1912530 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: Incomplete Bug description: I'm sorry, I don't know why/when it happens. I attach a crash logfile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912530/+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 1912575] Re: [regression] gpm no longer starts automatically, service must be started manually
** Bug watch added: Debian Bug tracker #980726 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980726 ** Also affects: gpm (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980726 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gpm in Ubuntu. https://bugs.launchpad.net/bugs/1912575 Title: [regression] gpm no longer starts automatically, service must be started manually Status in gpm package in Ubuntu: New Status in gpm package in Debian: Unknown Bug description: gpm no longer starts automatically, service must be started manually. The problem started this past week, so maybe in version 1.20.7-7 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gpm 1.20.7-7 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 21 11:49:14 2021 InstallationDate: Installed on 2020-11-27 (54 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201125) SourcePackage: gpm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpm/+bug/1912575/+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 1912575] Re: [regression] gpm no longer starts automatically, service must be started manually
Looks like gpm.service was just introduced. It probably needs some tweaking. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gpm in Ubuntu. https://bugs.launchpad.net/bugs/1912575 Title: [regression] gpm no longer starts automatically, service must be started manually Status in gpm package in Ubuntu: New Bug description: gpm no longer starts automatically, service must be started manually. The problem started this past week, so maybe in version 1.20.7-7 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gpm 1.20.7-7 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 21 11:49:14 2021 InstallationDate: Installed on 2020-11-27 (54 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201125) SourcePackage: gpm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpm/+bug/1912575/+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 1912575] [NEW] [regression] gpm no longer starts automatically, service must be started manually
Public bug reported: gpm no longer starts automatically, service must be started manually. The problem started this past week, so maybe in version 1.20.7-7 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gpm 1.20.7-7 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 21 11:49:14 2021 InstallationDate: Installed on 2020-11-27 (54 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201125) SourcePackage: gpm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gpm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute regression regression-release ** Tags added: regression-release -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gpm in Ubuntu. https://bugs.launchpad.net/bugs/1912575 Title: [regression] gpm no longer starts automatically, service must be started manually Status in gpm package in Ubuntu: New Bug description: gpm no longer starts automatically, service must be started manually. The problem started this past week, so maybe in version 1.20.7-7 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gpm 1.20.7-7 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 21 11:49:14 2021 InstallationDate: Installed on 2020-11-27 (54 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201125) SourcePackage: gpm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpm/+bug/1912575/+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 1893060] Re: [ubuntu-dock] Application menu pages collide when scrolled before it is loaded
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1893060 Title: [ubuntu-dock] Application menu pages collide when scrolled before it is loaded Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: I noticed when the menu is scrolled before it is fully loaded, the two pages collide (Refer attachment): https://launchpadlibrarian.net/494901346/Screencast%20from%2025-08-20%2012%2020%2046%20PM%20IST.mp4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 26 19:51:23 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-08-22 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893060/+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 1893060] Re: [ubuntu-dock] Application menu pages collide when scrolled before it is loaded
Hi Daneiel, I do not have any locally installed extensions. There is no file or directory ~/.local/share/gnome-shell/extensions $ gsettings get org.gnome.shell enabled-extensions @as [] $ ls ~/.local/share/gnome-shell/extensions/ ls: cannot access '/home/sujit/.local/share/gnome-shell/extensions/': No such file or directory $ ls /usr/share/gnome-shell/extensions/ desktop-icons@csoriano ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1893060 Title: [ubuntu-dock] Application menu pages collide when scrolled before it is loaded Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: I noticed when the menu is scrolled before it is fully loaded, the two pages collide (Refer attachment): https://launchpadlibrarian.net/494901346/Screencast%20from%2025-08-20%2012%2020%2046%20PM%20IST.mp4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 26 19:51:23 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-08-22 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893060/+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 1912530] Re: gnome-shell crash
Please report this crash by running: ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash which will create a new bug that will be automatically analysed. Please also 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. ** Summary changed: - Crash + gnome-shell crash ** Summary changed: - gnome-shell crash + gnome-shell crashed with SIGSEGV ** Tags added: focal ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1912530 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: Incomplete Bug description: I'm sorry, I don't know why/when it happens. I attach a crash logfile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912530/+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 1912530] Re: gnome-shell crashed with SIGSEGV
Also, I can tell from the crash file that you have some unsupported extensions enabled. Please try disabling all of them via the 'Extensions' app. We need to try removing extensions as a first step because so many bugs are caused by extensions. -- 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/1912530 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: Incomplete Bug description: I'm sorry, I don't know why/when it happens. I attach a crash logfile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912530/+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 1912472] Re: Display freezes randomly - high CPU usage
Also, please open the 'Extensions' app and try disabling any extensions you might have installed. We need to check that as a first priority because so many bugs are caused by extensions. -- 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/1912472 Title: Display freezes randomly - high CPU usage Status in mutter package in Ubuntu: Incomplete Bug description: Randomly, system freezes with high CPU usage (cooling fan goes high when the problem happens) since update to Ubuntu 20.04.1 LTS. Same problem with X11 and Wayland. Display freezes and keyboard or mouse inputs won't change anything. Caps and num lock won't react either. Ctrl+alt+anything doesn't solve the issue. Only possibility is then to force reboot using power button. After reboot, I could find in logs : gnome-shell libinput error: client bug: timer event6 debounce short: scheduled expiry is in the past (-15ms), your system is too slow Problem happens in any situation, for example while videoconferencing with any software, or using LibreOffice Writer, sometimes with Firefox. The only common fact seems to be that Firefox is always opened. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.7+git20201123-0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 20 10:27:48 2021 InstallationDate: Installed on 2020-11-15 (65 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash 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/1912472/+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 1912472] Re: Display freezes randomly - high CPU usage
Would you say the problem occurs when entering/leaving fullscreen in Firefox? Sounds like bug 1749779. ** 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/1912472 Title: Display freezes randomly - high CPU usage Status in mutter package in Ubuntu: Incomplete Bug description: Randomly, system freezes with high CPU usage (cooling fan goes high when the problem happens) since update to Ubuntu 20.04.1 LTS. Same problem with X11 and Wayland. Display freezes and keyboard or mouse inputs won't change anything. Caps and num lock won't react either. Ctrl+alt+anything doesn't solve the issue. Only possibility is then to force reboot using power button. After reboot, I could find in logs : gnome-shell libinput error: client bug: timer event6 debounce short: scheduled expiry is in the past (-15ms), your system is too slow Problem happens in any situation, for example while videoconferencing with any software, or using LibreOffice Writer, sometimes with Firefox. The only common fact seems to be that Firefox is always opened. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.7+git20201123-0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 20 10:27:48 2021 InstallationDate: Installed on 2020-11-15 (65 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash 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/1912472/+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 1912246] Re: gnome-shell freezes randomly after upgrading to groovy
That's correct behaviour. The stock GNOME dock is hidden. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1912246 Title: gnome-shell freezes randomly after upgrading to groovy Status in gnome-shell package in Ubuntu: Incomplete Bug description: I recently upgrading from Focal to Groovy, and use proprietary NVIDIA drivers with X11 with otherwise standard GNOME, but some extensions installed. I see frequently errors relating to the dash-to-dock extension which I'm not sure are related, but I also see that gnome- shell freezes up for a minute or so, and the logs have this to say: https://pastebin.ubuntu.com/p/trWJZfZ77Z/ BTW this is the error from the dash-to-dock extension if relevant: Jan 18 07:50:24 gnome-shell[10186]: == Stack trace for context 0x565369c02220 == Jan 18 07:50:24 gnome-shell[10186]: #0 7ffc8e0a3c00 I /home/ijohnson/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:2036 (e02dce21a0 @ 208) Jan 18 07:50:24 gnome-shell[10186]: Object St.Bin (0x56537221ac80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. however that seems to be an issue reported upstream at https://github.com/micheleg/dash-to-dock/issues/1360 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 18 09:51:15 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-05 (563 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2021-01-16 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912246/+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 1912246] Re: gnome-shell freezes randomly after upgrading to groovy
If you set: gsettings set org.gnome.desktop.interface enable-hot-corners true then the dock will appear by just moving the mouse to the top-left corner of the screen. -- 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/1912246 Title: gnome-shell freezes randomly after upgrading to groovy Status in gnome-shell package in Ubuntu: Incomplete Bug description: I recently upgrading from Focal to Groovy, and use proprietary NVIDIA drivers with X11 with otherwise standard GNOME, but some extensions installed. I see frequently errors relating to the dash-to-dock extension which I'm not sure are related, but I also see that gnome- shell freezes up for a minute or so, and the logs have this to say: https://pastebin.ubuntu.com/p/trWJZfZ77Z/ BTW this is the error from the dash-to-dock extension if relevant: Jan 18 07:50:24 gnome-shell[10186]: == Stack trace for context 0x565369c02220 == Jan 18 07:50:24 gnome-shell[10186]: #0 7ffc8e0a3c00 I /home/ijohnson/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:2036 (e02dce21a0 @ 208) Jan 18 07:50:24 gnome-shell[10186]: Object St.Bin (0x56537221ac80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. however that seems to be an issue reported upstream at https://github.com/micheleg/dash-to-dock/issues/1360 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 18 09:51:15 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-05 (563 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2021-01-16 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912246/+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 1912356] Re: Password visibility toggle stays active during login of next user (gdm's gnome-shell process stays running)
** Summary changed: - Password visibility toggle stays active during login of next user + Password visibility toggle stays active during login of next user (gdm's gnome-shell process stays running) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Triaged ** Tags added: nvidia ** Summary changed: - Password visibility toggle stays active during login of next user (gdm's gnome-shell process stays running) + [nvidia] Password visibility toggle stays active during login of next user (gdm's gnome-shell process stays running) -- 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/1912356 Title: [nvidia] Password visibility toggle stays active during login of next user (gdm's gnome-shell process stays running) Status in gnome-shell package in Ubuntu: Triaged Bug description: When logging into Ubuntu's main login screen there is a toggle to show the password (the little eye on the right side of the password input box). If the previous user enabled this when logging in and left this in an enabled state, that state will persist. The next user logging in, after the previous logged out, will type his or her password and it will be plainly visible on screen. Consider that: - Typing passwords is often routine (a new user might often not notice in time his or her password appears unmasked) - The state of the eye icon might not be clear by itself - Password masking not being enabled by default is not standard, and for good reason This happens when logging into Ubuntu (Focal Fossa 20.04) on a default install. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912356/+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 1893060] Re: [ubuntu-dock] Application menu pages collide when scrolled before it is loaded
Please check the 'Extensions' app and also look in ~/.local/share/gnome- shell/extensions to ensure you don't have two different dock extensions enabled at the same time. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1893060 Title: [ubuntu-dock] Application menu pages collide when scrolled before it is loaded Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: I noticed when the menu is scrolled before it is fully loaded, the two pages collide (Refer attachment): https://launchpadlibrarian.net/494901346/Screencast%20from%2025-08-20%2012%2020%2046%20PM%20IST.mp4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 26 19:51:23 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-08-22 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893060/+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 1912211] Re: Can't scroll pages in "Show Application" when Ubuntu Dock is loaded
** Summary changed: - Scrolling of pages in "Show Application" + Can't scroll pages in "Show Application" when Ubuntu Dock is loaded ** Summary changed: - Can't scroll pages in "Show Application" when Ubuntu Dock is loaded + Can't scroll pages in "Show Applications" when Ubuntu Dock is loaded ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- ubuntu-dock (Ubuntu) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Low => High ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Triaged -- 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/1912211 Title: Can't scroll pages in "Show Applications" when Ubuntu Dock is loaded Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Go to show Application bottom left corner of the windows 2. try to scroll down to check all of the apps. whenever i try to do the same it doesnt allow me to scroll or check all the apps i have installed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 18 18:57:54 2021 InstallationDate: Installed on 2021-01-12 (6 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1912211/+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 1910537] Re: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)
The hardware data in comment #4 does explicitly say: Supported sample rates (kHz): 48 but I don't know if the Linux audio stack (PulseAudio + ALSA) is smart enough to honour that automatically. Sounds like it's not. Try making a new file ~/.config/pulse/daemon.conf with: default-sample-rate = 48000 -- 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/1910537 Title: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer) Status in pulseaudio package in Ubuntu: Incomplete Bug description: This is a complicated thing. I have a very specific problem with audio output on HDMI. I want to use an older notebook with Lubuntu 20.04 as a video source for libreoffice slides, videos etc. to feed them over HDMI into a Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input. Configured on the desktop just like a second screen or beamer. Video works well and rock-stable, no problem at all. But not audio. Although I carefully configured audio with pavucontrol to be directed to the HDMI output, the ATEM switcher does not recognize it as an audio source (like when connecting a digital camera) and does not receive or indicate any audio input. Note: But when I use the very same computer, same HDMI cable, same video with a cheap chinese portable LCD screen with speakers (i.e. pull the cable from the ATEM and plug it into the screen) it immediately starts playing both video and audio. So there is evidence that the ubuntu notebook definitely passes it's sound to HDMI and there's really an audio signal on the HDMI. I've opened a bug at Blackmagic Design, and got their reply that they can't help and have never heard of such a problem before. Their guess is that the linux notebook is not setting EDID configuration correctly and thus not recognized by the ATEM, while the cheap LCD screen propably does not care about EDID and just plays everything, therefore a wrong EDID information would not matter. Although I have decades of experience with Linux, I am not too familiar with details of HDMI and the internals of the X11 driver, so I'm not sure where to start debugging, not even, whether this is a problem of Xorg/X11 or pulseaudio. I've checked this with another notebook with much more recent (intel) hardware, which offers dozens of HDMI audio options in the pavucontrol selection menu, but same problem: Video works, but the ATEM does not recognize it as a audio source. Blackmagic Design (they're good in Windows and MacOS, but not Linux) recommended to use an edid manager, whatever this means. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: LXQt Date: Thu Jan 7 13:16:26 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0742] InstallationDate: Installed on 2020-05-16 (235 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer AO756 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnAcer:bvrV1.05:bd07/19/2012:svnAcer:pnAO756:pvrV1.05:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.05: dmi.product.family: Type1Fa
[Desktop-packages] [Bug 1910537] Re: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)
There are a few sample rate-related settings in /etc/pulse/daemon.conf (or just make your own personal ~/.config/pulse/daemon.conf). You can edit that file and remove the ';' prefix to enable any settings. -- 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/1910537 Title: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer) Status in pulseaudio package in Ubuntu: Incomplete Bug description: This is a complicated thing. I have a very specific problem with audio output on HDMI. I want to use an older notebook with Lubuntu 20.04 as a video source for libreoffice slides, videos etc. to feed them over HDMI into a Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input. Configured on the desktop just like a second screen or beamer. Video works well and rock-stable, no problem at all. But not audio. Although I carefully configured audio with pavucontrol to be directed to the HDMI output, the ATEM switcher does not recognize it as an audio source (like when connecting a digital camera) and does not receive or indicate any audio input. Note: But when I use the very same computer, same HDMI cable, same video with a cheap chinese portable LCD screen with speakers (i.e. pull the cable from the ATEM and plug it into the screen) it immediately starts playing both video and audio. So there is evidence that the ubuntu notebook definitely passes it's sound to HDMI and there's really an audio signal on the HDMI. I've opened a bug at Blackmagic Design, and got their reply that they can't help and have never heard of such a problem before. Their guess is that the linux notebook is not setting EDID configuration correctly and thus not recognized by the ATEM, while the cheap LCD screen propably does not care about EDID and just plays everything, therefore a wrong EDID information would not matter. Although I have decades of experience with Linux, I am not too familiar with details of HDMI and the internals of the X11 driver, so I'm not sure where to start debugging, not even, whether this is a problem of Xorg/X11 or pulseaudio. I've checked this with another notebook with much more recent (intel) hardware, which offers dozens of HDMI audio options in the pavucontrol selection menu, but same problem: Video works, but the ATEM does not recognize it as a audio source. Blackmagic Design (they're good in Windows and MacOS, but not Linux) recommended to use an edid manager, whatever this means. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: LXQt Date: Thu Jan 7 13:16:26 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0742] InstallationDate: Installed on 2020-05-16 (235 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer AO756 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnAcer:bvrV1.05:bd07/19/2012:svnAcer:pnAO756:pvrV1.05:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.05: dmi.product.family: Type1Family dmi.product.name: AO756 dmi.product.sku: Type1Sku0 dmi.product.version: V1.05 dmi.sys.ven
[Desktop-packages] [Bug 508522] Re: Add automatic switching to HSP/HFP from A2DP when a mic is needed
Sounds reasonable to me... https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modules /#module-bluetooth-policy -- 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/508522 Title: Add automatic switching to HSP/HFP from A2DP when a mic is needed Status in PulseAudio: New Status in chromium-browser package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+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 1901079] Re: Please update thunderbird to 68.12 in Focal
It would be great to update to 68.12 until Focal migrates to 78. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1901079 Title: Please update thunderbird to 68.12 in Focal Status in thunderbird package in Ubuntu: Triaged Bug description: Please update thunderbird to 68.12 in Focal. It fixes security vulnerabilities, and 68.11 fixes FileLink attachments included as a link and file when added from a network drive via drag & drop. https://www.thunderbird.net/thunderbird/68.11.0/releasenotes/ Security Vulnerabilities fixed in Thunderbird 68.11: https://www.mozilla.org/security/advisories/mfsa2020-35/ Security Vulnerabilities fixed in Thunderbird 68.12: https://www.mozilla.org/security/advisories/mfsa2020-40/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901079/+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 1639531] Re: GCC compiles programs to shared object instead of executable, preventing GUI file managers from executing programs
This is serious bug and is really counter-productive in 21 century when
downloading some portable archive and cannot launch software, Very
troublesome. This way is one way to scare people back to Windows.
affects 20.10 and 21.04 too, please raise voice people.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to shared-mime-info in Ubuntu.
https://bugs.launchpad.net/bugs/1639531
Title:
GCC compiles programs to shared object instead of executable,
preventing GUI file managers from executing programs
Status in gcc-defaults:
Unknown
Status in shared-mime-info:
Unknown
Status in shared-mime-info package in Ubuntu:
Triaged
Bug description:
Release of Ubuntu being used
Description:Ubuntu 16.10
Release:16.10
Version of the package being used
=
gcc:
Installed: 4:6.1.1-1ubuntu2
Candidate: 4:6.1.1-1ubuntu2
Version table:
*** 4:6.1.1-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
100 /var/lib/dpkg/status
What was expected
=
Programs compiled using `gcc -o program program.c` should be runnable
by double-clicking them from a GUI file manager.
Compiling a simple program (`void main() { }`) using Xubuntu 16.04's
current version of `gcc` (`gcc version 5.4.0 20160609 (Ubuntu
5.4.0-6ubuntu1~16.04.2)`) produces the following output from
`/usr/bin/file program`:
program: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
GNU/Linux 2.6.32, BuildID[sha1]=signature_here, not stripped
This is correct behavior, allowing the executables to run from
Nautilus and Thunar.
What happened instead
=
Programs compiled using `gcc -o program program.c` are not runnable by
double-clicking them from a GUI file manager, even though they are
runnable from the terminal.
Compiling a simple program (`void main() { }`) using the current
version of `gcc` (`6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)`) produces
the following output from `/usr/bin/file program`:
program: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
GNU/Linux 2.6.32, BuildID[sha1]=signature_here, not stripped
The program is also identified as a "shared library" instead of an
"executable" in Thunar, causing it to not be runnable from the GUI.
Others are unable to run such programs from Nautilus.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc-defaults/+bug/1639531/+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 1912536] Re: Gnome Disk Utility can't mount audio CDs
I grabbed a music CD (pink floyd, delicate sounds of thunder disc 2) and inserted it into my hirsute system. Response was identical to that described by OP, with my GNOME-DISKS looking pretty much identical to the picture provided (excluding red censorship, dvd drive model, size of disc etc or expected differences) I have NOT clicked AFFECTS ME TOO, as I can't a reason why I'd want to mount the drive with gnome-disks. A look at the Github (https://gitlab.gnome.org/GNOME/gnome-disk-utility) says "GNOME Disks, gnome-disk-image-mounter and gsd-disk-utility-notify are libraries and applications for dealing with storage devices." A look at the `man gnome-disks` also doesn't convince me this is something a user should expect. "gnome-disks is the command to launch the GNOME Disks application. Disks provides a way to inspect, format, partition and configure disks and block devices." Thus I'll confirm I get the same response in hirsute (3.38.1-1ubuntu1) but I've not checked affects-me-too as I'm unsure it's a bug. If `mounting` is an intended/expected feature it does impact me (but I didn't see reference to `mount` in the man pages, except in the 'see also' section which refers you to other utilities) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1912536 Title: Gnome Disk Utility can't mount audio CDs Status in gnome-disk-utility package in Ubuntu: New Bug description: 1) Ubuntu 20.10 2) 3.38.0-1ubuntu1 3) Gnome Disks should be able to see an audio CD when mounted. 4) Instead I get "unknown" in the contents and the Audio CD cannot be read. This occurs only in Ubuntu and not in Windows (dual boot). Tried multiple CDs. I also get the exact error on a USB Blu Ray drive. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-disk-utility 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Wed Jan 20 16:22:24 2021 InstallationDate: Installed on 2020-09-16 (126 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to groovy on 2020-11-29 (52 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1912536/+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 1873676] Re: Could not load support for `gnome': libgnome.so: cannot open shared object file: No such file or directory
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xscreensaver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgnomeui in Ubuntu. https://bugs.launchpad.net/bugs/1873676 Title: Could not load support for `gnome': libgnome.so: cannot open shared object file: No such file or directory Status in libgnomeui package in Ubuntu: Confirmed Status in xscreensaver package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install xscreensaver package 3. Launch `xscreensaver-demo` Expected results: * no warnings Actual results: * there are warnings: ``` $ xscreensaver-demo (xscreensaver-demo:6824): libglade-WARNING **: 19:47:51.804: Could not load support for `gnome': libgnome.so: cannot open shared object file: No such file or directory xscreensaver-demo: 19:47:52: XScreenSaver-debug: Name com.canonical.AppMenu.Registrar does not exist on the session bus ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xscreensaver 5.42+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Apr 19 19:49:14 2020 InstallationDate: Installed on 2020-04-12 (6 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200412) SourcePackage: xscreensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgnomeui/+bug/1873676/+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 1873676] Re: Could not load support for `gnome': libgnome.so: cannot open shared object file: No such file or directory
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libgnomeui (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgnomeui in Ubuntu. https://bugs.launchpad.net/bugs/1873676 Title: Could not load support for `gnome': libgnome.so: cannot open shared object file: No such file or directory Status in libgnomeui package in Ubuntu: Confirmed Status in xscreensaver package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install xscreensaver package 3. Launch `xscreensaver-demo` Expected results: * no warnings Actual results: * there are warnings: ``` $ xscreensaver-demo (xscreensaver-demo:6824): libglade-WARNING **: 19:47:51.804: Could not load support for `gnome': libgnome.so: cannot open shared object file: No such file or directory xscreensaver-demo: 19:47:52: XScreenSaver-debug: Name com.canonical.AppMenu.Registrar does not exist on the session bus ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xscreensaver 5.42+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Apr 19 19:49:14 2020 InstallationDate: Installed on 2020-04-12 (6 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200412) SourcePackage: xscreensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgnomeui/+bug/1873676/+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 1912541] [NEW] fprintd crashes in dev_open_cb -> g_task_return_now -> g_task_return -> fp_device_task_return_in_idle_cb
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding fprintd. This problem was most recently seen with package version 1.90.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/d573b3db58665e64e93fb65d74a9f876d54846f2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: fprintd (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1912541 Title: fprintd crashes in dev_open_cb -> g_task_return_now -> g_task_return -> fp_device_task_return_in_idle_cb Status in fprintd package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding fprintd. This problem was most recently seen with package version 1.90.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/d573b3db58665e64e93fb65d74a9f876d54846f2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1912541/+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 1912542] [NEW] /usr/libexec/fprintd:11:dev_open_cb:g_task_return_now:g_task_return:fp_device_task_return_in_idle_cb:g_main_context_dispatch
*** This bug is a duplicate of bug 1912541 *** https://bugs.launchpad.net/bugs/1912541 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding fprintd. This problem was most recently seen with package version 1.90.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/080c3fd7ece86a51cd74608f0f94d4b6fd76489f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: fprintd (Ubuntu) Importance: Undecided Status: New ** Tags: focal groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1912542 Title: /usr/libexec/fprintd:11:dev_open_cb:g_task_return_now:g_task_return:fp_device_task_return_in_idle_cb:g_main_context_dispatch Status in fprintd package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding fprintd. This problem was most recently seen with package version 1.90.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/080c3fd7ece86a51cd74608f0f94d4b6fd76489f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1912542/+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 1912536] [NEW] Gnome Disk Utility can't mount audio CDs
Public bug reported: 1) Ubuntu 20.10 2) 3.38.0-1ubuntu1 3) Gnome Disks should be able to see an audio CD when mounted. 4) Instead I get "unknown" in the contents and the Audio CD cannot be read. This occurs only in Ubuntu and not in Windows (dual boot). Tried multiple CDs. I also get the exact error on a USB Blu Ray drive. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-disk-utility 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Wed Jan 20 16:22:24 2021 InstallationDate: Installed on 2020-09-16 (126 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to groovy on 2020-11-29 (52 days ago) ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Attachment added: "Gnome Disks showing "unknown" for audio CD" https://bugs.launchpad.net/bugs/1912536/+attachment/5454965/+files/Screenshot%20from%202021-01-20%2015%3A33%3A14.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1912536 Title: Gnome Disk Utility can't mount audio CDs Status in gnome-disk-utility package in Ubuntu: New Bug description: 1) Ubuntu 20.10 2) 3.38.0-1ubuntu1 3) Gnome Disks should be able to see an audio CD when mounted. 4) Instead I get "unknown" in the contents and the Audio CD cannot be read. This occurs only in Ubuntu and not in Windows (dual boot). Tried multiple CDs. I also get the exact error on a USB Blu Ray drive. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-disk-utility 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Wed Jan 20 16:22:24 2021 InstallationDate: Installed on 2020-09-16 (126 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to groovy on 2020-11-29 (52 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1912536/+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 1912356] Re: Password visibility toggle stays active during login of next user
Hi Daniel, as you can see I used the apport tool to send system information. I also checked if the `gnome-shell` process was still running. Here's the output of `ps aux | grep gdm | grep shell`, after login: ``` gdm 1215 0.6 0.5 4075932 165140 tty1 Sl+ 20:55 0:02 /usr/bin/gnome-shell gdm 1266 0.0 0.0 2930264 26548 tty1Sl+ 20:55 0:00 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Notifications ``` Seems like it is. If I can further help investigating this issue. Let me know! -- 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/1912356 Title: Password visibility toggle stays active during login of next user Status in gnome-shell package in Ubuntu: Incomplete Bug description: When logging into Ubuntu's main login screen there is a toggle to show the password (the little eye on the right side of the password input box). If the previous user enabled this when logging in and left this in an enabled state, that state will persist. The next user logging in, after the previous logged out, will type his or her password and it will be plainly visible on screen. Consider that: - Typing passwords is often routine (a new user might often not notice in time his or her password appears unmasked) - The state of the eye icon might not be clear by itself - Password masking not being enabled by default is not standard, and for good reason This happens when logging into Ubuntu (Focal Fossa 20.04) on a default install. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912356/+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 1912530] [NEW] Crash
Public bug reported: I'm sorry, I don't know why/when it happens. I attach a crash logfile ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "log file" https://bugs.launchpad.net/bugs/1912530/+attachment/5454955/+files/_usr_bin_gnome-shell.1000.crash -- 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/1912530 Title: Crash Status in gnome-shell package in Ubuntu: New Bug description: I'm sorry, I don't know why/when it happens. I attach a crash logfile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912530/+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 1912356] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1912356/+attachment/5454953/+files/ProcEnviron.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/1912356 Title: Password visibility toggle stays active during login of next user Status in gnome-shell package in Ubuntu: Incomplete Bug description: When logging into Ubuntu's main login screen there is a toggle to show the password (the little eye on the right side of the password input box). If the previous user enabled this when logging in and left this in an enabled state, that state will persist. The next user logging in, after the previous logged out, will type his or her password and it will be plainly visible on screen. Consider that: - Typing passwords is often routine (a new user might often not notice in time his or her password appears unmasked) - The state of the eye icon might not be clear by itself - Password masking not being enabled by default is not standard, and for good reason This happens when logging into Ubuntu (Focal Fossa 20.04) on a default install. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912356/+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 1912356] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1912356/+attachment/5454951/+files/GsettingsChanges.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/1912356 Title: Password visibility toggle stays active during login of next user Status in gnome-shell package in Ubuntu: Incomplete Bug description: When logging into Ubuntu's main login screen there is a toggle to show the password (the little eye on the right side of the password input box). If the previous user enabled this when logging in and left this in an enabled state, that state will persist. The next user logging in, after the previous logged out, will type his or her password and it will be plainly visible on screen. Consider that: - Typing passwords is often routine (a new user might often not notice in time his or her password appears unmasked) - The state of the eye icon might not be clear by itself - Password masking not being enabled by default is not standard, and for good reason This happens when logging into Ubuntu (Focal Fossa 20.04) on a default install. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912356/+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 1912356] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1912356/+attachment/5454954/+files/ShellJournal.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/1912356 Title: Password visibility toggle stays active during login of next user Status in gnome-shell package in Ubuntu: Incomplete Bug description: When logging into Ubuntu's main login screen there is a toggle to show the password (the little eye on the right side of the password input box). If the previous user enabled this when logging in and left this in an enabled state, that state will persist. The next user logging in, after the previous logged out, will type his or her password and it will be plainly visible on screen. Consider that: - Typing passwords is often routine (a new user might often not notice in time his or her password appears unmasked) - The state of the eye icon might not be clear by itself - Password masking not being enabled by default is not standard, and for good reason This happens when logging into Ubuntu (Focal Fossa 20.04) on a default install. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912356/+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 1912356] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1912356/+attachment/5454952/+files/ProcCpuinfoMinimal.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/1912356 Title: Password visibility toggle stays active during login of next user Status in gnome-shell package in Ubuntu: Incomplete Bug description: When logging into Ubuntu's main login screen there is a toggle to show the password (the little eye on the right side of the password input box). If the previous user enabled this when logging in and left this in an enabled state, that state will persist. The next user logging in, after the previous logged out, will type his or her password and it will be plainly visible on screen. Consider that: - Typing passwords is often routine (a new user might often not notice in time his or her password appears unmasked) - The state of the eye icon might not be clear by itself - Password masking not being enabled by default is not standard, and for good reason This happens when logging into Ubuntu (Focal Fossa 20.04) on a default install. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912356/+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 1912356] Re: Password visibility toggle stays active during login of next user
apport information ** Tags added: apport-collected ** Description changed: When logging into Ubuntu's main login screen there is a toggle to show the password (the little eye on the right side of the password input box). If the previous user enabled this when logging in and left this in an enabled state, that state will persist. The next user logging in, after the previous logged out, will type his or her password and it will be plainly visible on screen. Consider that: - Typing passwords is often routine (a new user might often not notice in time his or her password appears unmasked) - The state of the eye icon might not be clear by itself - Password masking not being enabled by default is not standard, and for good reason - This happens when logging into Ubuntu (Focal Fossa 20.04) on a default - install. + This happens when logging into Ubuntu (Focal Fossa 20.04) on a default install. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.14 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-01-04 (16 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 + RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 + Tags: focal + Uname: Linux 5.8.0-38-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1912356/+attachment/5454950/+files/Dependencies.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/1912356 Title: Password visibility toggle stays active during login of next user Status in gnome-shell package in Ubuntu: Incomplete Bug description: When logging into Ubuntu's main login screen there is a toggle to show the password (the little eye on the right side of the password input box). If the previous user enabled this when logging in and left this in an enabled state, that state will persist. The next user logging in, after the previous logged out, will type his or her password and it will be plainly visible on screen. Consider that: - Typing passwords is often routine (a new user might often not notice in time his or her password appears unmasked) - The state of the eye icon might not be clear by itself - Password masking not being enabled by default is not standard, and for good reason This happens when logging into Ubuntu (Focal Fossa 20.04) on a default install. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912356/+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 1912211] Re: Scrolling of pages in "Show Application"
I reproduced the issue, i.e. not being able to scroll beyond the first application window in "Show Applications", by installing the 20.04.1 ISO in a VirtualBox VM. I accomplished the installation without downloading upgraded packages, so it was a true vanilla Ubuntu 20.04.1 installation. Then I updated all packages and rebooted, but the issue was still there. Then I uninstalled gnome-shell-extension-ubuntu-dock and rebooted, and now the "Show Applications" scrolling worked as expected. Finally I reinstalled gnome-shell-extension-ubuntu-dock and rebooted, and the issue was back. So it seems to be something with gnome-shell-extension-ubuntu-dock. Btw, I used an external USB connected mouse. Shouldn't the importance of this bug be raised? After all it's about a core feature of the Ubuntu desktop. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Confirmed -- 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/1912211 Title: Scrolling of pages in "Show Application" Status in gnome-shell package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Go to show Application bottom left corner of the windows 2. try to scroll down to check all of the apps. whenever i try to do the same it doesnt allow me to scroll or check all the apps i have installed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 18 18:57:54 2021 InstallationDate: Installed on 2021-01-12 (6 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912211/+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 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
Simon's deb worked for me and a GeForce 8400M GS that was broken since 2021-01-12 and linux modules 5.8.0.36. That was a misadventure, an unpleasant user experience. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Bug description: [Impact] nvidia-340 dkms fails to build against the current HWE kernel in focal, regressing the user experience. [Test case] Install the update, check that the dkms builds and works. [Where things could go wrong] The changes only add support for newer kernels so that the module can build, and it's identical to what's in groovy. In theory it could break the build against 5.4 but that's highly unlikely. -- Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M.
[Desktop-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
You may find the following information useful. It looks like Ubuntu needs to add these fixes ... https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/10#note_769719 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths Status in Linux: Unknown Status in libxcb package in Ubuntu: Confirmed Status in xfwm4 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly. With dual monitors and the external monitor placed left or right the display has a blocked staircase effect shown in the attached photograph, and seems related to https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/issues/10 More detailed investigation suggests it only happens when the X coordinate of the two monitors is different. The symptom looks like an off-by-one error because it appears as if the display is divided into, say, 10 rows and 15 columns but the first row has 16 'columns' worth of blocks on it and so wraps to the beginning of the 2nd row, and so on. On the laptop without package upgrades being applied this didn't happen. So I upgraded it (314 packages) and restarted and it too sees the same problem. I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but that didn't solve it. I now suspect libxcb but so far haven't been able to prove it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) MachineType: LENOVO 20NECTO1WW Package: xserver-xorg-video-amdgpu 19.1.0-1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET32W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NECTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E495 dmi.product.name: 20NECTO1WW dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495 dmi.product.version: ThinkPad E495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1873895/+subscriptions -- Mailing 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 1912498] Re: Preinstall some new essential raspi packages in the official raspi images
All branches ready for review, attaching debdiff for review of the ubuntu-meta package changes as well - would appreciate some feedback. It's worth mentioning the status for hirsute. So basically in hirsute and groovy we only use the seeds for the raspi desktop images. In hirsute, with as things are right now, adding it would be hard as we'd be generating a lot of component mismatches due to pulling things from restricted, universe etc. It's a problem conceptually and for migration reasons, but for a stable series like focal it's less so. Especially that since ages we've been building raspi images from universe + multiverse packages anyway, so it's already 'bad'. ** Patch added: "ubuntu-meta_1.450.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1912498/+attachment/5454877/+files/ubuntu-meta_1.450.3.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1912498 Title: Preinstall some new essential raspi packages in the official raspi images Status in livecd-rootfs package in Ubuntu: Opinion Status in ubuntu-meta package in Ubuntu: Opinion Status in livecd-rootfs source package in Focal: In Progress Status in ubuntu-meta source package in Focal: In Progress Bug description: [Impact] For 20.04.2, also as part of support for some new Pi variants (CM4, Pi400), we want to preinstall some new essential packages in our raspi images such as rpi-eeprom, raspberrypi-userland etc. This can be done in two possible ways. One is the 'old way', with a single change to livecd-rootfs adding the new packages. But what we'd like to propose this time is actually a more proper way, i.e. introducing device-specific raspi seeds and a raspi meta-package that would pull in all the needed dependencies. This way is better for the future, as if we decide we want to add new packages to existing raspi installations, we can do it easily by modifying the seeds and rebuilding meta. Currently we have no way like this. So the current approach includes changes in the following components: * The ubuntu and platform seeds (git branches) * ubuntu-meta package (adding ubuntu-server-raspi) * livecd-rootfs package (installing the raspi-server task) [Test Case] After accepting all the package into -proposed (and making sure the git seed changes are merged), run a raspi arm64 and armhf build. Check if the image boots. Confirm that the new images have the following seeded: rpi-eeprom, libraspberrypi-bin, flash-kernel, pi-bluetooth. Compare manifests between a normal, previous raspi image build and the one using seeds - check if nothing has been 'dropped'. Also, check if no other image builds have been affected and still build correctly, compare image manifests. [Where problems could occur] In its current form, as the update touches some livecd-rootfs auto/config paths, it's possible that a malformed cut-paste broke some edge case scenario, so it's good if other non-raspi builds are also checked for correctness. Seed changes are less likely to break anything, but manifests should be checked in case something got dropped by accident. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912498/+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 1902044] Re: SRU the current 42.6 stable update
There hasn't been extra demand for those fixes and we are already past mid-cycle to the next Ubuntu version so I'm not going to bother doing more paperwork there ** Changed in: deja-dup (Ubuntu Groovy) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1902044 Title: SRU the current 42.6 stable update Status in deja-dup package in Ubuntu: Fix Released Status in deja-dup source package in Groovy: Won't Fix Bug description: * Impact That's the current stable update, including some fixes and translation updates https://gitlab.gnome.org/World/deja-dup/-/releases/42.5 The update should help with bug #1901340 and backup on removable drives * Test case Check that local and remote backups and restore are working. * Regression potential The update has some fixes for backup on removable and encrypted media so that's probably something to give some testing to To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1902044/+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 1912498] Re: Preinstall some new essential raspi packages in the official raspi images
** Merge proposal linked: https://code.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/+merge/396583 ** Merge proposal linked: https://code.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/platform/+merge/396585 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1912498 Title: Preinstall some new essential raspi packages in the official raspi images Status in livecd-rootfs package in Ubuntu: Opinion Status in ubuntu-meta package in Ubuntu: Opinion Status in livecd-rootfs source package in Focal: In Progress Status in ubuntu-meta source package in Focal: In Progress Bug description: [Impact] For 20.04.2, also as part of support for some new Pi variants (CM4, Pi400), we want to preinstall some new essential packages in our raspi images such as rpi-eeprom, raspberrypi-userland etc. This can be done in two possible ways. One is the 'old way', with a single change to livecd-rootfs adding the new packages. But what we'd like to propose this time is actually a more proper way, i.e. introducing device-specific raspi seeds and a raspi meta-package that would pull in all the needed dependencies. This way is better for the future, as if we decide we want to add new packages to existing raspi installations, we can do it easily by modifying the seeds and rebuilding meta. Currently we have no way like this. So the current approach includes changes in the following components: * The ubuntu and platform seeds (git branches) * ubuntu-meta package (adding ubuntu-server-raspi) * livecd-rootfs package (installing the raspi-server task) [Test Case] After accepting all the package into -proposed (and making sure the git seed changes are merged), run a raspi arm64 and armhf build. Check if the image boots. Confirm that the new images have the following seeded: rpi-eeprom, libraspberrypi-bin, flash-kernel, pi-bluetooth. Compare manifests between a normal, previous raspi image build and the one using seeds - check if nothing has been 'dropped'. Also, check if no other image builds have been affected and still build correctly, compare image manifests. [Where problems could occur] In its current form, as the update touches some livecd-rootfs auto/config paths, it's possible that a malformed cut-paste broke some edge case scenario, so it's good if other non-raspi builds are also checked for correctness. Seed changes are less likely to break anything, but manifests should be checked in case something got dropped by accident. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912498/+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 1912498] Re: Preinstall some new essential raspi packages in the official raspi images
** Merge proposal linked: https://code.launchpad.net/~ubuntu-core-dev/livecd-rootfs/+git/livecd-rootfs/+merge/396582 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1912498 Title: Preinstall some new essential raspi packages in the official raspi images Status in livecd-rootfs package in Ubuntu: Opinion Status in ubuntu-meta package in Ubuntu: Opinion Status in livecd-rootfs source package in Focal: In Progress Status in ubuntu-meta source package in Focal: In Progress Bug description: [Impact] For 20.04.2, also as part of support for some new Pi variants (CM4, Pi400), we want to preinstall some new essential packages in our raspi images such as rpi-eeprom, raspberrypi-userland etc. This can be done in two possible ways. One is the 'old way', with a single change to livecd-rootfs adding the new packages. But what we'd like to propose this time is actually a more proper way, i.e. introducing device-specific raspi seeds and a raspi meta-package that would pull in all the needed dependencies. This way is better for the future, as if we decide we want to add new packages to existing raspi installations, we can do it easily by modifying the seeds and rebuilding meta. Currently we have no way like this. So the current approach includes changes in the following components: * The ubuntu and platform seeds (git branches) * ubuntu-meta package (adding ubuntu-server-raspi) * livecd-rootfs package (installing the raspi-server task) [Test Case] After accepting all the package into -proposed (and making sure the git seed changes are merged), run a raspi arm64 and armhf build. Check if the image boots. Confirm that the new images have the following seeded: rpi-eeprom, libraspberrypi-bin, flash-kernel, pi-bluetooth. Compare manifests between a normal, previous raspi image build and the one using seeds - check if nothing has been 'dropped'. Also, check if no other image builds have been affected and still build correctly, compare image manifests. [Where problems could occur] In its current form, as the update touches some livecd-rootfs auto/config paths, it's possible that a malformed cut-paste broke some edge case scenario, so it's good if other non-raspi builds are also checked for correctness. Seed changes are less likely to break anything, but manifests should be checked in case something got dropped by accident. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912498/+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 1908284] Re: [snap] chromium headless crashes at startup on non-desktop system
A more minimal workaround is to "apt install fonts-dejavu-core" before installing the chromium snap (verified working on a headless system). This ensures that there is at least one font when the configure hook pre-generates a font cache. -- 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/1908284 Title: [snap] chromium headless crashes at startup on non-desktop system Status in chromium-browser package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 20.04 and it looks like the current stable version of the Chromium snap has an issue running headless: ``` tjcravey@chromium:~$ chromium --headless --remote-debugging-port=9222 https://chromium.org [0100/00.240635:ERROR:zygote_linux.cc(607)] Zygote could not fork: process_type gpu-process numfds 3 child_pid -1 [0100/00.240882:ERROR:zygote_linux.cc(639)] write: Broken pipe (32) Trace/breakpoint trap (core dumped) ``` ``` tjcravey@chromium:~$ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: today at 15:33 UTC channels: latest/stable:87.0.4280.88 2020-12-10 (1424) 124MB - latest/candidate: 87.0.4280.88 2020-12-10 (1424) 124MB - latest/beta: 88.0.4324.41 2020-12-15 (1441) 144MB - latest/edge: 89.0.4350.4 2020-12-11 (1434) 257MB - installed: 87.0.4280.88(1424) 124MB - ``` I was able to revert back to snap 1421 on a different system and that command works fine there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1908284/+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 508522] Re: Add automatic switching to HSP/HFP from A2DP when a mic is needed
Daniel, do you think there would be any problem in overriding the default configuration we ship to have auto_switch=2 set by default? -- 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/508522 Title: Add automatic switching to HSP/HFP from A2DP when a mic is needed Status in PulseAudio: New Status in chromium-browser package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+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 1911456] Re: Can't receive files over bluetooth unless settings dialog is open
The issue is a gnome-control-center design decision one and has been reported upstream https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1189 ** Changed in: bluez (Ubuntu) Status: New => Invalid ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1189 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1189 ** Changed in: gnome-user-share (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-user-share (Ubuntu) Status: New => Triaged ** Package changed: gnome-user-share (Ubuntu) => gnome-control-center (Ubuntu) ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1189 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/1911456 Title: Can't receive files over bluetooth unless settings dialog is open Status in gnome-control-center: Unknown Status in bluez package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Triaged Bug description: On 18.04 I could send files from my phone to my laptop at any time. On 20.04 I can't get files to be accepted by the laptop over bluetooth. After much frustration and experimenting, I figured out that it will work, but only if the bluetooth settings dialog is open. If the settings dialog is not open, the incoming file is rejected. If the dialog is closed after the file transfer begins, the transfer continues but the file is discarded when the transfer is complete. This is very frustrating. I need to be able to send files (mostly photos and videos) from my phone to my laptop without having to open the settings dialog on the laptop, just like I could before upgrading. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1911456/+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 1912498] Re: Preinstall some new essential raspi packages in the official raspi images
** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Importance: High => Wishlist ** Changed in: livecd-rootfs (Ubuntu Focal) Importance: Undecided => High ** Changed in: ubuntu-meta (Ubuntu Focal) Importance: Undecided => High ** Changed in: ubuntu-meta (Ubuntu) Importance: Undecided => Wishlist ** Changed in: ubuntu-meta (Ubuntu) Status: New => Opinion ** Changed in: livecd-rootfs (Ubuntu) Status: New => Opinion ** Changed in: livecd-rootfs (Ubuntu Focal) Status: New => In Progress ** Changed in: ubuntu-meta (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1912498 Title: Preinstall some new essential raspi packages in the official raspi images Status in livecd-rootfs package in Ubuntu: Opinion Status in ubuntu-meta package in Ubuntu: Opinion Status in livecd-rootfs source package in Focal: In Progress Status in ubuntu-meta source package in Focal: In Progress Bug description: [Impact] For 20.04.2, also as part of support for some new Pi variants (CM4, Pi400), we want to preinstall some new essential packages in our raspi images such as rpi-eeprom, raspberrypi-userland etc. This can be done in two possible ways. One is the 'old way', with a single change to livecd-rootfs adding the new packages. But what we'd like to propose this time is actually a more proper way, i.e. introducing device-specific raspi seeds and a raspi meta-package that would pull in all the needed dependencies. This way is better for the future, as if we decide we want to add new packages to existing raspi installations, we can do it easily by modifying the seeds and rebuilding meta. Currently we have no way like this. So the current approach includes changes in the following components: * The ubuntu and platform seeds (git branches) * ubuntu-meta package (adding ubuntu-server-raspi) * livecd-rootfs package (installing the raspi-server task) [Test Case] After accepting all the package into -proposed (and making sure the git seed changes are merged), run a raspi arm64 and armhf build. Check if the image boots. Confirm that the new images have the following seeded: rpi-eeprom, libraspberrypi-bin, flash-kernel, pi-bluetooth. Compare manifests between a normal, previous raspi image build and the one using seeds - check if nothing has been 'dropped'. Also, check if no other image builds have been affected and still build correctly, compare image manifests. [Where problems could occur] In its current form, as the update touches some livecd-rootfs auto/config paths, it's possible that a malformed cut-paste broke some edge case scenario, so it's good if other non-raspi builds are also checked for correctness. Seed changes are less likely to break anything, but manifests should be checked in case something got dropped by accident. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912498/+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 1908502] Re: [MIR] libtiff5 dependency on libdeflate0
** Description changed: - tiff 4.1.0+git201212-1 enabled deflate support, adding libdeflate0 as a - dependency to libtiff5, making the package uninstallable. + * Availability - Therefor I uploaded 4.1.0+git201212-1ubuntu1 disabling the deflate - support to make libtiff5 installable again. + In sync with Debian, built on all architectures + https://launchpad.net/ubuntu/+source/libdeflate/1.7-1 - Either this package stays this way, or it needs a MIR for libdeflate. + * Rationale + + It's a new depends of libtiff + + * Security + + No known security issues, but due to the nature of this package, a + security review is probably needed. + + https://security-tracker.debian.org/tracker/source-package/libdeflate + https://people.canonical.com/~ubuntu-security/cve/pkg/libdeflate.html + https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libdeflate + + * Quality assurance + + The desktop team is going to subscribe to the package + + https://launchpad.net/ubuntu/+source/libdeflate/+bugs + https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libdeflate + + No open reports + + The package enables upstream tests during the build and ships basic + autopkgtests + + * Dependencies + + No universe binary dependencies + + * Standards compliance + + current 4.5.1 standards-version, debhelper compat 13, dh style simple + rules + + * Maintenance + + Upstream is active, the package is maintained in Debian and in sync for + Ubuntu ** Changed in: tiff (Ubuntu Hirsute) Assignee: Olivier Tilloy (osomon) => (unassigned) ** Changed in: tiff (Ubuntu Hirsute) Status: Confirmed => Invalid ** Summary changed: - [MIR] libtiff5 dependency on libdeflate0 + [MIR] libdeflate ** Changed in: libdeflate (Ubuntu Hirsute) Status: Incomplete => New ** Description changed: * Availability In sync with Debian, built on all architectures https://launchpad.net/ubuntu/+source/libdeflate/1.7-1 * Rationale It's a new depends of libtiff * Security - No known security issues, but due to the nature of this package, a - security review is probably needed. + There is no known security issues https://security-tracker.debian.org/tracker/source-package/libdeflate https://people.canonical.com/~ubuntu-security/cve/pkg/libdeflate.html https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libdeflate * Quality assurance The desktop team is going to subscribe to the package https://launchpad.net/ubuntu/+source/libdeflate/+bugs https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libdeflate No open reports The package enables upstream tests during the build and ships basic autopkgtests * Dependencies No universe binary dependencies * Standards compliance current 4.5.1 standards-version, debhelper compat 13, dh style simple rules * Maintenance Upstream is active, the package is maintained in Debian and in sync for Ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1908502 Title: [MIR] libdeflate Status in libdeflate package in Ubuntu: New Status in tiff package in Ubuntu: Invalid Status in libdeflate source package in Hirsute: New Status in tiff source package in Hirsute: Invalid Bug description: * Availability In sync with Debian, built on all architectures https://launchpad.net/ubuntu/+source/libdeflate/1.7-1 * Rationale It's a new depends of libtiff * Security There is no known security issues https://security-tracker.debian.org/tracker/source-package/libdeflate https://people.canonical.com/~ubuntu-security/cve/pkg/libdeflate.html https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libdeflate * Quality assurance The desktop team is going to subscribe to the package https://launchpad.net/ubuntu/+source/libdeflate/+bugs https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libdeflate No open reports The package enables upstream tests during the build and ships basic autopkgtests * Dependencies No universe binary dependencies * Standards compliance current 4.5.1 standards-version, debhelper compat 13, dh style simple rules * Maintenance Upstream is active, the package is maintained in Debian and in sync for Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdeflate/+bug/1908502/+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 1882878] Re: The user panel let you enroll the same finger several times
** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Released ** Also affects: fprintd (Ubuntu) Importance: Undecided Status: New ** Changed in: fprintd (Ubuntu) Status: New => Triaged ** Changed in: fprintd (Ubuntu) Importance: Undecided => Medium ** Changed in: fprintd (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1882878 Title: The user panel let you enroll the same finger several times Status in gnome-control-center: Unknown Status in fprintd package in Ubuntu: Triaged Status in gnome-control-center package in Ubuntu: Fix Released Bug description: We are able to enroll the same finger for all 10 available options. (No error like 'Fingerprint is already enrolled' is observed). In windows it doesn’t allow to enroll the same finger, it has a duplicate check API. Here we have all 10 finger options are shown in GUI itself, so whichever finger is enrolled atleast the same finger can be grayed out so that user cannot enroll the same finger again. The release of Ubuntu: Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1882878/+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 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
Robie you're right, I'll add these versioned Breaks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Triaged Status in thunderbird source package in Focal: Fix Committed Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+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 1843733] Re: fftw3 ftbfs in eoan (armhf only)
** Changed in: fftw3 (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fftw3 in Ubuntu. https://bugs.launchpad.net/bugs/1843733 Title: fftw3 ftbfs in eoan (armhf only) Status in FFTW: New Status in fftw3 package in Ubuntu: Fix Released Status in fftw3 source package in Eoan: Won't Fix Status in fftw3 package in Debian: Confirmed Bug description: fftw3 ftbfs in eoan (armhf only). https://launchpadlibrarian.net/441265031/buildlog_ubuntu-eoan- armhf.fftw3_3.3.8-2_BUILDING.txt.gz ( cd tests ; /usr/bin/make smallcheck ) make[1]: Entering directory '/<>/tests' perl -w ./check.pl -r -c=1 -v `pwd`/bench Executing "/<>/tests/bench --verbose=1 --verify 'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304'" ok7e10x12bv29 1.71318e-07 1.44516e-06 2.00887e-07 ik7e10x12bv29 1.66737e-07 1.44901e-06 1.76717e-07 Segmentation fault (core dumped) FAILED /<>/tests/bench: --verify 'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304' make[1]: *** [Makefile:723: smallcheck] Error 1 make[1]: Leaving directory '/<>/tests' To manage notifications about this bug go to: https://bugs.launchpad.net/fftw3/+bug/1843733/+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 1895855] Re: FFE: support for NVIDIA runtimepm (hybrid gfx)
Hello Alberto, or anyone else affected, Accepted nvidia-prime into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia- prime/0.8.15.3~0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-prime (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1895855 Title: FFE: support for NVIDIA runtimepm (hybrid gfx) Status in OEM Priority Project: New Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Committed Bug description: The work that went into ubuntu-drivers-common and nvidia-prime is meant to enable RTD3 support on Intel/NVIDIA or AMD/NVIDIA hybrid systems, introduced by the NVIDIA 450 driver series. This allows the supported systems to make use of the integrated GPU (Intel or AMD) and to keep the discrete NVIDIA GPU powered down until needed. While powered down, the NVIDIA GPU can still detect any events, should external displays be plugged in. This brings hybrid graphics on Linux on par with Windows. Only the supported GPUs will be able to benefit from this change. This is why NVIDIA provides a hardware database (included in the nvidia packages), which gpu-manager can now parse. The ubuntu-drivers tool relies on that detection to enable this new feature when installing the NVIDIA driver. Another improvement is the ability of ubuntu-drivers to detect LTSB (Long term support branch), NFB (New feature branch), Legacy, Beta flags, which the NVIDIA drivers can have, and make informed detection choices. This work also includes a number of bug fixes reported on errors.ubuntu.com. Requirements: The new ubuntu-drivers-common: The new nvidia-prime: Changes to the NVIDIA drivers: To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1895855/+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 1904583] Re: SRU: Backport the latest developments on drivers detection and hybrid graphics
Hello Alberto, or anyone else affected, Accepted nvidia-prime into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia- prime/0.8.15.3~0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-prime (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1904583 Title: SRU: Backport the latest developments on drivers detection and hybrid graphics Status in OEM Priority Project: New Status in nvidia-prime package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Invalid Status in nvidia-prime source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Bionic: In Progress Status in nvidia-prime source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in nvidia-prime source package in Groovy: Fix Committed Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: As we introduced the "-server" NVIDIA drivers, and the concept of "LTSB" (Long Term Support Branch) and "NFB" (New Feature Branch) releases, the detection logic behind ubuntu-drivers needs an update to make the correct choices for the user. The introduction of the NVIDIA 450 series, also added runtime power management, which greatly improves user experience on systems with hybrid graphics, and allows greater power savings. When supported, on- demand mode and runtime power management are the default. Both gpu- manager and ubuntu-drivers in ubuntu drivers common, and the tools in the nvidia-prime package need updating as a result. The nvidia-prime package also has a change to fix a problem where /lib/udev/rules.d/50-pm-nvidia.rules was left behind, after a system upgrade 20.04 LTS (focal) to 20.10 (groovy), and yet prime-select had lost the ability to remove the udev rules file, leaving the end user with no means to re-enable his/her Nvidia GPU. Only the components in Ubuntu 20.10 require a fairly small diff for the backport. The rest is a direct sync of the 1:0.8.6.3 release in 21.04. [Impact] * The ubuntu-drivers tool might install the wrong driver, or, in some cases, crash, if the new -server drivers are available. * The new runtime power management can't be used even when the hardware (Turing GPUs or newer) supports it. * We want to the default drivers to be Long Term support releases. Users may still pick different drivers manually. [Fix] * The code in Ubuntu 21.04 includes essential bug fixes, and more test cases in the test suite, to make sure that driver installation is more robust, and more accurate (LTSB vs NFB releases, and non-server vs -server releases). * ubuntu-drivers, gpu-manager, and prime-select now all support runtime power management. [Test Case] Install ubuntu-drivers-common and nvidia-prime from proposed, and check the following: 1) ubuntu-drivers debug 2) Make sure no nvidia driver is installed (sudo apt-get --purge remove '*nvidia*', and try installing an nvidia driver with "sudo ubuntu-drivers install" 3) Reboot your system 4) [optional] If you are running on a hybrid laptop, you can check if your system supports runtime power management: sudo prime-select on-demand (if you are already in "on-demand" mode, select "intel" mode first, then try "on-demand" again) 5) If you followed step 4, reboot again 6) Attach your /var/log/gpu-manager.log [Regression Risk] Medium, while this code includes many fixes, it needs careful testing. == Changes == Only the components in Ubuntu 20.10 require a fairly small diff for the backport. The rest is a direct sync of the 1:0.8.6.3 release in 21.04. == Ubuntu 20
[Desktop-packages] [Bug 1912491] [NEW] Incorrect processing of network name and time messages from operator leads to multiple issues
Public bug reported: Ubuntu version: 20.04.1 LTS modemmanager version: 1.12.8-1 modem-manager-gui version: 0.0.19.1-2 What I expected to happen: SMSes in the GUI have correct timestamps; the operator name is reported correctly in the GUI; USSD communications work correctly in the GUI and through the mmcli interface. What is actually happening: SMSes in the GUI have no timestamps; the operator name disappears from the GUI; USSD communications randomly fail both in the GUI and on the commandine. I understand that the maintainers of this package are not responsible for the GUI application, but below I explain my rationale for filing this bug against this package and why I think these issues are related. I use modemmanager and modem-manager-gui to manage a GSM modem in my Thinkpad. In 18.04 everything worked correctly, but since I upgraded to 20.04 I have noticed multiple issues which I believe may have the same underlying cause: 1. Received SMSes logged in modem-manager-gui no longer have timestamps. This may be the same issue as is reported here in the Fedora package, since the upstream version appears to be the same: https://bugzilla.redhat.com/show_bug.cgi?id=1839752 2. When I start up modem-manager-gui, I can see the operator name displayed correctly in the info tab, but after some time it disappears, and I see "Searching" as the value in the "Registration" field. 3. This is the most critical issue and the primary reason that I'm reporting this. When I interact with any USSD menu, I experience intermittent "Invalid USSD message received" errors which disrupt any sufficiently long chain of USSD interactions and make it near-impossible to complete certain tasks via USSD. It's only through extensive trial and error that I found that sometimes it's possible to retry the same reply successfully, although this is very sensitive to timeouts. After initially observing this behaviour in modem-manager-gui I tried to use the mmcli interface on the commandline to access these USSD menus, and found the same erratic behaviour. This is why I'm filing this bug against the modemmanager package. The exact error messages are always in this format: error: couldn't send response in USSD session: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Failed: Invalid USSD message received: '^NWNAME: "MTN-SA","","65510" ^NWTIME: 21/01/20,13:13:31+08,0'' My layperson's hypothesis is that these are messages from the operator containing the name of the network and the system time of the network, but modemmanager is not expecting them and therefore not processing them correctly for some reason, which is why 1) the network name and time is not being set in modem-manager-gui and 2) USSD communications are being disrupted by unexpected messages. I'd be happy to help to debug this further if there is any other information that I can provide. ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1912491 Title: Incorrect processing of network name and time messages from operator leads to multiple issues Status in modemmanager package in Ubuntu: New Bug description: Ubuntu version: 20.04.1 LTS modemmanager version: 1.12.8-1 modem-manager-gui version: 0.0.19.1-2 What I expected to happen: SMSes in the GUI have correct timestamps; the operator name is reported correctly in the GUI; USSD communications work correctly in the GUI and through the mmcli interface. What is actually happening: SMSes in the GUI have no timestamps; the operator name disappears from the GUI; USSD communications randomly fail both in the GUI and on the commandine. I understand that the maintainers of this package are not responsible for the GUI application, but below I explain my rationale for filing this bug against this package and why I think these issues are related. I use modemmanager and modem-manager-gui to manage a GSM modem in my Thinkpad. In 18.04 everything worked correctly, but since I upgraded to 20.04 I have noticed multiple issues which I believe may have the same underlying cause: 1. Received SMSes logged in modem-manager-gui no longer have timestamps. This may be the same issue as is reported here in the Fedora package, since the upstream version appears to be the same: https://bugzilla.redhat.com/show_bug.cgi?id=1839752 2. When I start up modem-manager-gui, I can see the operator name displayed correctly in the info tab, but after some time it disappears, and I see "Searching" as the value in the "Registration" field. 3. This is the most critical issue and the primary reason that I'm reporting this. When I interact with any USSD menu, I experience intermittent "Invalid USSD message received" errors which disrupt any su
[Desktop-packages] [Bug 1910537] Re: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)
BTW: what would pulseaudio / ubuntu pass out on HDMI if I do play two audio sources, one with 44.1 and one with 48 kHz, at the same time? Any tool or method to check what's going out to HDMI? -- 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/1910537 Title: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer) Status in pulseaudio package in Ubuntu: Incomplete Bug description: This is a complicated thing. I have a very specific problem with audio output on HDMI. I want to use an older notebook with Lubuntu 20.04 as a video source for libreoffice slides, videos etc. to feed them over HDMI into a Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input. Configured on the desktop just like a second screen or beamer. Video works well and rock-stable, no problem at all. But not audio. Although I carefully configured audio with pavucontrol to be directed to the HDMI output, the ATEM switcher does not recognize it as an audio source (like when connecting a digital camera) and does not receive or indicate any audio input. Note: But when I use the very same computer, same HDMI cable, same video with a cheap chinese portable LCD screen with speakers (i.e. pull the cable from the ATEM and plug it into the screen) it immediately starts playing both video and audio. So there is evidence that the ubuntu notebook definitely passes it's sound to HDMI and there's really an audio signal on the HDMI. I've opened a bug at Blackmagic Design, and got their reply that they can't help and have never heard of such a problem before. Their guess is that the linux notebook is not setting EDID configuration correctly and thus not recognized by the ATEM, while the cheap LCD screen propably does not care about EDID and just plays everything, therefore a wrong EDID information would not matter. Although I have decades of experience with Linux, I am not too familiar with details of HDMI and the internals of the X11 driver, so I'm not sure where to start debugging, not even, whether this is a problem of Xorg/X11 or pulseaudio. I've checked this with another notebook with much more recent (intel) hardware, which offers dozens of HDMI audio options in the pavucontrol selection menu, but same problem: Video works, but the ATEM does not recognize it as a audio source. Blackmagic Design (they're good in Windows and MacOS, but not Linux) recommended to use an edid manager, whatever this means. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: LXQt Date: Thu Jan 7 13:16:26 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0742] InstallationDate: Installed on 2020-05-16 (235 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer AO756 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnAcer:bvrV1.05:bd07/19/2012:svnAcer:pnAO756:pvrV1.05:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.05: dmi.product.family: Type1Family dmi.product.name: AO756 dmi.product.sku: Type1Sku0 dmi.product.version: V1.05 dmi.sys.vendor: Acer v
[Desktop-packages] [Bug 1910537] Re: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)
I think I've found the problem. @Uldis: please check and verify It doesn't work with a video with Channel(s) : 1 channel Channel layout : C Sampling rate: 44.1 kHz but it works when playing a video with Channel(s) : 2 channels Sampling rate: 48.0 kHz So maybe it's the sampling rate. Probably Linux outputs a sampling rate conforming with the current source, and the ATEM seems to expect 48kHz, while accepting everything on HDMI1, but getting it scrambled and distorted, since there's not enough data (8% missing), while the input on HDMI2-4 simply doesn't match the expectations. -- 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/1910537 Title: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer) Status in pulseaudio package in Ubuntu: Incomplete Bug description: This is a complicated thing. I have a very specific problem with audio output on HDMI. I want to use an older notebook with Lubuntu 20.04 as a video source for libreoffice slides, videos etc. to feed them over HDMI into a Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input. Configured on the desktop just like a second screen or beamer. Video works well and rock-stable, no problem at all. But not audio. Although I carefully configured audio with pavucontrol to be directed to the HDMI output, the ATEM switcher does not recognize it as an audio source (like when connecting a digital camera) and does not receive or indicate any audio input. Note: But when I use the very same computer, same HDMI cable, same video with a cheap chinese portable LCD screen with speakers (i.e. pull the cable from the ATEM and plug it into the screen) it immediately starts playing both video and audio. So there is evidence that the ubuntu notebook definitely passes it's sound to HDMI and there's really an audio signal on the HDMI. I've opened a bug at Blackmagic Design, and got their reply that they can't help and have never heard of such a problem before. Their guess is that the linux notebook is not setting EDID configuration correctly and thus not recognized by the ATEM, while the cheap LCD screen propably does not care about EDID and just plays everything, therefore a wrong EDID information would not matter. Although I have decades of experience with Linux, I am not too familiar with details of HDMI and the internals of the X11 driver, so I'm not sure where to start debugging, not even, whether this is a problem of Xorg/X11 or pulseaudio. I've checked this with another notebook with much more recent (intel) hardware, which offers dozens of HDMI audio options in the pavucontrol selection menu, but same problem: Video works, but the ATEM does not recognize it as a audio source. Blackmagic Design (they're good in Windows and MacOS, but not Linux) recommended to use an edid manager, whatever this means. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: LXQt Date: Thu Jan 7 13:16:26 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0742] InstallationDate: Installed on 2020-05-16 (235 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer AO756 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2012 dm
[Desktop-packages] [Bug 1882878] Re: The user panel let you enroll the same finger several times
FP_DEVICE_ERROR_DATA_DUPLICATE error is added in libfprint 1.90.3 version, but when driver is returned this error, UI is not showing as duplicate finger error and showing Fingerprint enroll is failed, UI should show proper error here. And also, post this failure, next finger enrollment is failed until system restart. -- 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/1882878 Title: The user panel let you enroll the same finger several times Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: We are able to enroll the same finger for all 10 available options. (No error like 'Fingerprint is already enrolled' is observed). In windows it doesn’t allow to enroll the same finger, it has a duplicate check API. Here we have all 10 finger options are shown in GUI itself, so whichever finger is enrolled atleast the same finger can be grayed out so that user cannot enroll the same finger again. The release of Ubuntu: Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1882878/+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 1910537] Re: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)
BTW, same with the older ATEM Mini (non-Pro) -- 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/1910537 Title: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer) Status in pulseaudio package in Ubuntu: Incomplete Bug description: This is a complicated thing. I have a very specific problem with audio output on HDMI. I want to use an older notebook with Lubuntu 20.04 as a video source for libreoffice slides, videos etc. to feed them over HDMI into a Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input. Configured on the desktop just like a second screen or beamer. Video works well and rock-stable, no problem at all. But not audio. Although I carefully configured audio with pavucontrol to be directed to the HDMI output, the ATEM switcher does not recognize it as an audio source (like when connecting a digital camera) and does not receive or indicate any audio input. Note: But when I use the very same computer, same HDMI cable, same video with a cheap chinese portable LCD screen with speakers (i.e. pull the cable from the ATEM and plug it into the screen) it immediately starts playing both video and audio. So there is evidence that the ubuntu notebook definitely passes it's sound to HDMI and there's really an audio signal on the HDMI. I've opened a bug at Blackmagic Design, and got their reply that they can't help and have never heard of such a problem before. Their guess is that the linux notebook is not setting EDID configuration correctly and thus not recognized by the ATEM, while the cheap LCD screen propably does not care about EDID and just plays everything, therefore a wrong EDID information would not matter. Although I have decades of experience with Linux, I am not too familiar with details of HDMI and the internals of the X11 driver, so I'm not sure where to start debugging, not even, whether this is a problem of Xorg/X11 or pulseaudio. I've checked this with another notebook with much more recent (intel) hardware, which offers dozens of HDMI audio options in the pavucontrol selection menu, but same problem: Video works, but the ATEM does not recognize it as a audio source. Blackmagic Design (they're good in Windows and MacOS, but not Linux) recommended to use an edid manager, whatever this means. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: LXQt Date: Thu Jan 7 13:16:26 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0742] InstallationDate: Installed on 2020-05-16 (235 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer AO756 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnAcer:bvrV1.05:bd07/19/2012:svnAcer:pnAO756:pvrV1.05:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.05: dmi.product.family: Type1Family dmi.product.name: AO756 dmi.product.sku: Type1Sku0 dmi.product.version: V1.05 dmi.sys.vendor: Acer 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-m
[Desktop-packages] [Bug 1910537] Re: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)
Confirmed: distorted sound on HDMI1 no sound on HDMI2-4 -- 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/1910537 Title: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer) Status in pulseaudio package in Ubuntu: Incomplete Bug description: This is a complicated thing. I have a very specific problem with audio output on HDMI. I want to use an older notebook with Lubuntu 20.04 as a video source for libreoffice slides, videos etc. to feed them over HDMI into a Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input. Configured on the desktop just like a second screen or beamer. Video works well and rock-stable, no problem at all. But not audio. Although I carefully configured audio with pavucontrol to be directed to the HDMI output, the ATEM switcher does not recognize it as an audio source (like when connecting a digital camera) and does not receive or indicate any audio input. Note: But when I use the very same computer, same HDMI cable, same video with a cheap chinese portable LCD screen with speakers (i.e. pull the cable from the ATEM and plug it into the screen) it immediately starts playing both video and audio. So there is evidence that the ubuntu notebook definitely passes it's sound to HDMI and there's really an audio signal on the HDMI. I've opened a bug at Blackmagic Design, and got their reply that they can't help and have never heard of such a problem before. Their guess is that the linux notebook is not setting EDID configuration correctly and thus not recognized by the ATEM, while the cheap LCD screen propably does not care about EDID and just plays everything, therefore a wrong EDID information would not matter. Although I have decades of experience with Linux, I am not too familiar with details of HDMI and the internals of the X11 driver, so I'm not sure where to start debugging, not even, whether this is a problem of Xorg/X11 or pulseaudio. I've checked this with another notebook with much more recent (intel) hardware, which offers dozens of HDMI audio options in the pavucontrol selection menu, but same problem: Video works, but the ATEM does not recognize it as a audio source. Blackmagic Design (they're good in Windows and MacOS, but not Linux) recommended to use an edid manager, whatever this means. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: LXQt Date: Thu Jan 7 13:16:26 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0742] InstallationDate: Installed on 2020-05-16 (235 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer AO756 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnAcer:bvrV1.05:bd07/19/2012:svnAcer:pnAO756:pvrV1.05:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.05: dmi.product.family: Type1Family dmi.product.name: AO756 dmi.product.sku: Type1Sku0 dmi.product.version: V1.05 dmi.sys.vendor: Acer 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 ver
[Desktop-packages] [Bug 1912246] Re: gnome-shell freezes randomly after upgrading to groovy
Well for the short bit that I've been using the system after disabling all the extensions through the Extensions app, I have not experienced any freeze. I will report back after the end of the day if I see any more freezes though. Interestingly, after disabling all Extensions, I have no more dock unless I press the "super" button in which case it momentarily appears on the left, is this intended? I guess I seem to remember "stock gnome" had a dock that was permanently on the screen... -- 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/1912246 Title: gnome-shell freezes randomly after upgrading to groovy Status in gnome-shell package in Ubuntu: Incomplete Bug description: I recently upgrading from Focal to Groovy, and use proprietary NVIDIA drivers with X11 with otherwise standard GNOME, but some extensions installed. I see frequently errors relating to the dash-to-dock extension which I'm not sure are related, but I also see that gnome- shell freezes up for a minute or so, and the logs have this to say: https://pastebin.ubuntu.com/p/trWJZfZ77Z/ BTW this is the error from the dash-to-dock extension if relevant: Jan 18 07:50:24 gnome-shell[10186]: == Stack trace for context 0x565369c02220 == Jan 18 07:50:24 gnome-shell[10186]: #0 7ffc8e0a3c00 I /home/ijohnson/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:2036 (e02dce21a0 @ 208) Jan 18 07:50:24 gnome-shell[10186]: Object St.Bin (0x56537221ac80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. however that seems to be an issue reported upstream at https://github.com/micheleg/dash-to-dock/issues/1360 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 18 09:51:15 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-05 (563 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2021-01-16 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912246/+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 1912472] Re: Display freezes randomly - high CPU usage
** Package changed: ubuntu => mutter (Ubuntu) -- 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/1912472 Title: Display freezes randomly - high CPU usage Status in mutter package in Ubuntu: New Bug description: Randomly, system freezes with high CPU usage (cooling fan goes high when the problem happens) since update to Ubuntu 20.04.1 LTS. Same problem with X11 and Wayland. Display freezes and keyboard or mouse inputs won't change anything. Caps and num lock won't react either. Ctrl+alt+anything doesn't solve the issue. Only possibility is then to force reboot using power button. After reboot, I could find in logs : gnome-shell libinput error: client bug: timer event6 debounce short: scheduled expiry is in the past (-15ms), your system is too slow Problem happens in any situation, for example while videoconferencing with any software, or using LibreOffice Writer, sometimes with Firefox. The only common fact seems to be that Firefox is always opened. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.7+git20201123-0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 20 10:27:48 2021 InstallationDate: Installed on 2020-11-15 (65 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash 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/1912472/+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 1912472] [NEW] Display freezes randomly - high CPU usage
You have been subscribed to a public bug: Randomly, system freezes with high CPU usage (cooling fan goes high when the problem happens) since update to Ubuntu 20.04.1 LTS. Same problem with X11 and Wayland. Display freezes and keyboard or mouse inputs won't change anything. Caps and num lock won't react either. Ctrl+alt+anything doesn't solve the issue. Only possibility is then to force reboot using power button. After reboot, I could find in logs : gnome-shell libinput error: client bug: timer event6 debounce short: scheduled expiry is in the past (-15ms), your system is too slow Problem happens in any situation, for example while videoconferencing with any software, or using LibreOffice Writer, sometimes with Firefox. The only common fact seems to be that Firefox is always opened. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.7+git20201123-0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 20 10:27:48 2021 InstallationDate: Installed on 2020-11-15 (65 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- Display freezes randomly - high CPU usage https://bugs.launchpad.net/bugs/1912472 You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter 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 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
I think thunderbird needs a versioned Breaks on tinyjsd and jsunit now, right? And also, shouldn't it have a versioned Breaks on enigmail (and vice versa) to ensure that the new enigmail is updated in lockstep with Thunderbird? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Triaged Status in thunderbird source package in Focal: Fix Committed Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+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 1912202] Re: ubuntu-drivers-common fix FTBFS in focal
# apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.8.6.3~0.20.04.2 Candidate: 1:0.8.6.3~0.20.04.2 Version table: *** 1:0.8.6.3~0.20.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main riscv64 Packages 100 /var/lib/dpkg/statu Now available and installable. ** 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 ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1912202 Title: ubuntu-drivers-common fix FTBFS in focal Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Bug description: [Impact] * ubuntu-drivers-common is not available on riscv64 in focal due to failing test cases. In later releases riscv64 is built without unittests. This is preventing creating Focal based riscv64 cloud- images & hifive images. [Test Case] * Check that ubuntu-drivers-common is now available and installable on riscv64. [Where problems could occur] * This is no change rebuild for all other arches. And certain ubuntu- drivers-common functionality may not be working correctly on riscv64 - on par with later releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1912202/+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 1903995] Re: upower report wrong battery percentage for Logitech Unify devices
Sorry for being slow in getting back to you about this.
I believe that this should be fixed by this upstream commit, which will
be in the 5.12 kernel:
https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git/commit/?h
=for-next&id=e037acf0b1aed31cb5f3b09ccb602b4768c133d5
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1903995
Title:
upower report wrong battery percentage for Logitech Unify devices
Status in upower package in Ubuntu:
Triaged
Bug description:
The battery percentage reported by upower for Logitech devices
connected using Unify receiver are wrong. Below are the results for
two devices: Mouse and Keyboard:
* Battery percentages reported by Unify receiver using Solaar:
$ solaar show | grep -iP "^(( \d: )|(.*batt.*))"
1: Wireless Keyboard K270(unifying)
4: BATTERY STATUS {1000}
Battery: 70%, discharging.
2: Wireless Mouse MX Master
7: BATTERY STATUS {1000}
Battery: 20%, discharging.
* Battery percentages reported by upower:
$ upower -i /org/freedesktop/UPower/devices/keyboard_hidpp_battery_0
native-path: hidpp_battery_0
model:Wireless Keyboard K270
serial: 4003-1a-39-5f-c1
power supply: no
updated: Thu 12 Nov 2020 13:59:18 CET (119 seconds ago)
has history: yes
has statistics: yes
keyboard
present: yes
rechargeable:yes
state: discharging
warning-level: none
battery-level: normal
percentage: 55% (should be ignored)
icon-name: 'battery-low-symbolic'
$ upower -i /org/freedesktop/UPower/devices/mouse_hidpp_battery_1
native-path: hidpp_battery_1
model:Wireless Mouse MX Master
serial: 4071-f8-eb-bf-d1
power supply: no
updated: Thu 12 Nov 2020 14:03:14 CET (27 seconds ago)
has history: yes
has statistics: yes
mouse
present: yes
rechargeable:yes
state: discharging
warning-level: low
battery-level: low
percentage: 10% (should be ignored)
icon-name: 'battery-caution-symbolic'
Basically the difference is big so I'm getting a lot of notifications
related to low battery even if the battery is OK:
* Mouse, upower: 10%real (Solaar): 20%
* Keyboard: upower: 70%real (Solaar): 55%
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: upower 0.99.11-1build2
ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
Uname: Linux 5.4.0-53-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 12 13:58:35 2020
InstallationDate: Installed on 2020-04-19 (206 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417)
SourcePackage: upower
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.apport.crashdb.conf: 2020-06-17T11:02:56.934699
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1903995/+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 1902044] Proposed package upload rejected
An upload of deja-dup to groovy-proposed has been rejected from the upload queue for the following reason: "Missing SRU information (see https://bugs.launchpad.net/ubuntu/+source/deja- dup/+bug/1902044/comments/1 and https://bugs.launchpad.net/ubuntu/+source/deja- dup/+bug/1902044/comments/5)". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1902044 Title: SRU the current 42.6 stable update Status in deja-dup package in Ubuntu: Fix Released Status in deja-dup source package in Groovy: Incomplete Bug description: * Impact That's the current stable update, including some fixes and translation updates https://gitlab.gnome.org/World/deja-dup/-/releases/42.5 The update should help with bug #1901340 and backup on removable drives * Test case Check that local and remote backups and restore are working. * Regression potential The update has some fixes for backup on removable and encrypted media so that's probably something to give some testing to To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1902044/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
Hi again Olivier, Now that the 88.x version hit stable, can we expect to have this in place in the foreseeable future? Thanks for your work on this! -- 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/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: News : - Candidate Chromium 83 Snap with vaapi enabled can be installed with : sudo snap install --channel=candidate/vaapi chromium Check that your vidéo is gpu decoded but checking "MojoVideoDecoder" in about:media-internals Widevine DRM streams will have DecryptingVideoDecoder Please report success/failure with - distro version - GPU Hardware used - Codec used --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1912354] Re: Option to show remote images gone
Thank you for your bug report, the option is still there but indeed it
doesn't seem to show on every html emails but just some, unsure what's
the trigger though
** Changed in: thunderbird (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1912354
Title:
Option to show remote images gone
Status in thunderbird package in Ubuntu:
New
Bug description:
In Thunderbird 78.5.0, the button to show remote images seems to be
gone, and there doesn't appear to be any replacement. The option to
always show remote images for this sender is also gone.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: thunderbird 1:78.5.0+build3-0ubuntu0.20.10.1
ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
Uname: Linux 5.8.0-33-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: alistair 1894 F pulseaudio
/dev/snd/pcmC0D3p: alistair 1894 F...m pulseaudio
BuildID: 20201116161136
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Jan 19 13:59:33 2021
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
IncompatibleExtensions:
Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2020-07-14 (189 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
default via 192.168.1.1 dev wlp0s20f3 proto dhcp metric 600
10.0.0.0/24 dev wg0 proto kernel scope link src 10.0.0.2
169.254.0.0/16 dev wlp0s20f3 scope link metric 1000
192.168.1.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.1.143
metric 600
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:732
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=78.5.0/20201116161136 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to groovy on 2020-10-05 (106 days ago)
dmi.bios.date: 10/15/2020
dmi.bios.release: 1.14
dmi.bios.vendor: LENOVO
dmi.bios.version: N2WET24W (1.14 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20U9CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.8
dmi.modalias:
dmi:bvnLENOVO:bvrN2WET24W(1.14):bd10/15/2020:br1.14:efr1.8:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon Gen 8
dmi.product.name: 20U9CTO1WW
dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
dmi.product.version: ThinkPad X1 Carbon Gen 8
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1912354/+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 1793472] Re: [wishlist] Add mdadm into desktop by default
Intel VROC (Intel Virtual RAID on CPU) needs mdadm to install on it per OEM test result. Intel reference document like below does mention that: https://www.intel.com/content/dam/support/us/en/documents/memory-and- storage/ssd-software/Linux_VROC_6-0_User_Guide.pdf ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High ** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1793472 Title: [wishlist] Add mdadm into desktop by default Status in OEM Priority Project: New Status in ubuntu-meta package in Ubuntu: New Bug description: Consider the situation that we have OEM systems with software raid devices and the desktop image will be installed on them as primary storage. Another work is to patch casper to support md (Please refer bug #1793444). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1793472/+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 1908284] Re: [snap] chromium headless crashes at startup on non-desktop system
I can reliably observe the problem on a system without a desktop environment, and I can confirm that installing ubuntu-desktop-minimal and then reinstalling the snap makes the problem go away. This is a regression that appeared when switching to using the gnome-3-28 extension. After removing again ubuntu-desktop-minimal and all its dependencies, and reinstalling the snap, the snap still works, so the root of the problem is not really a missing dependency, but more likely user files/folders created when installing those packages or when installing the snap (configure hook maybe). ** Summary changed: - [snap] chromium headless crashes in revision 1424 + [snap] chromium headless crashes at startup on non-desktop system ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Medium -- 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/1908284 Title: [snap] chromium headless crashes at startup on non-desktop system Status in chromium-browser package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 20.04 and it looks like the current stable version of the Chromium snap has an issue running headless: ``` tjcravey@chromium:~$ chromium --headless --remote-debugging-port=9222 https://chromium.org [0100/00.240635:ERROR:zygote_linux.cc(607)] Zygote could not fork: process_type gpu-process numfds 3 child_pid -1 [0100/00.240882:ERROR:zygote_linux.cc(639)] write: Broken pipe (32) Trace/breakpoint trap (core dumped) ``` ``` tjcravey@chromium:~$ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: today at 15:33 UTC channels: latest/stable:87.0.4280.88 2020-12-10 (1424) 124MB - latest/candidate: 87.0.4280.88 2020-12-10 (1424) 124MB - latest/beta: 88.0.4324.41 2020-12-15 (1441) 144MB - latest/edge: 89.0.4350.4 2020-12-11 (1434) 257MB - installed: 87.0.4280.88(1424) 124MB - ``` I was able to revert back to snap 1421 on a different system and that command works fine there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1908284/+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 1905494] Re: Without sudo, system-config-printer freeze when changing printer driver
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: system-config-printer (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1905494 Title: Without sudo, system-config-printer freeze when changing printer driver Status in system-config-printer package in Ubuntu: Confirmed Bug description: Distribution: Ubuntu MATE 20.04.1 LTS. System-config-printer version: 1.5.12-0ubuntu1.1 If I run system-config-printer by clicking Menu -> Administration -> Printers, the system-config-printer will be run without prompting for my user password, mean without using sudo. I can install the printers successfully without any issue. But, when changing the driver, system- config-printer will freeze. Here are the steps to reproduce the issue: 1. Run system-config-printer by clicking Menu -> Administration -> Printers. You will not be prompted to enter any password. 2. Install any printer. 3. Close system-config-printer. 4. Run system-config-printer again by repeating step 1 above, clicking Menu -> Administration -> Printers. 5. Right click on any installed printer, then click properties. Printer properties will be shown. 6. In printer properties, click the "change" button located at the right side of "Make and Model" text field. The "change Driver" dialog will occur. 7. In "Change Driver" dialog, by default, "Select printer from database" will be choosen automatically. Do not do anything, and just wait for a few seconds. Another dialog occur, showing "Searching for drivers". 8. Wait for a few minutes, you will see nothing happen. System-config-printer will continue to hang/freeze. There is a workaround. Steps for workaround: 1. Exit system-config-printer if it is still running. If the system-config-printer still hang or freeze, use system monitor to kill it. 2. Run terminal. 3. In terminal run system-config-printer by using command "sudo system-config-printer". You will be prompted to enter your user password. 4. Enter your user password, then press the Enter key. 5. In system-config-printer, right click on any installed printer, then click "properties". Printer properties will be shown. 6. In printer properties, click the "change" button located at the right side of "Make and Model" text field. The "change Driver" dialog will occur. 7. Wait for the "Searching for drivers" dialog to appear and disappear, list of printer brands will be shown. 8. You can proceed to follow on screen instructions to change the driver. Please fix this issue. If changing printer driver require sudo, system-config-printer should prompt for my password. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: system-config-printer 1.5.12-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: W [23/Nov/2020:15:45:07 +0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'DocuCentre_VI_C4471_11_a9_16_-Gray..\' already exists W [23/Nov/2020:15:45:07 +0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'DocuCentre_VI_C4471_11_a9_16_-DeviceN..\' already exists W [23/Nov/2020:18:28:39 +0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Ricoh-Aficio-MP-201-Gray..\' already exists W [25/Nov/2020:07:57:57 +0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Ricoh-Aficio-MP-201-Gray..\' already exists W [25/Nov/2020:07:59:26 +0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Ricoh-Aficio-MP-201-Gray..\' already exists CurrentDesktop: MATE Date: Wed Nov 25 08:11:23 2020 InstallationDate: Installed on 2020-11-23 (1 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for Ricoh-Aficio-MP-201: socket://192.168.0.226:9100 MachineType: ASUS All Series PackageArchitecture: all Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Ricoh-Aficio-MP-201.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Ricoh-Aficio-MP-201.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=cad772fa-c02b-4268-bc15-e366825ac807 ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be
