[Desktop-packages] [Bug 1312376]
Bug 1207700 landed and xinput2 should be enabled by default now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1312376 Title: touch screen in browser not scrolling Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Hi team, I wanted to highlight a problem with my touch screen laptop not scrolling on touch. It doesn't grab and scroll but highlights the text in the browser. Please feel free to ask for more information as I am more than happy to help! thanks Morlando To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1312376/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1312376]
As this issue is about Ubuntu 16.04 and #1207700 addresses gtk-3.24 only. xinput2 won't be enabled by default until Ubuntu 19.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1312376 Title: touch screen in browser not scrolling Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Hi team, I wanted to highlight a problem with my touch screen laptop not scrolling on touch. It doesn't grab and scroll but highlights the text in the browser. Please feel free to ask for more information as I am more than happy to help! thanks Morlando To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1312376/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1683383] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen)
To whom it may concern, I have uploaded xorg-server 1.20.8 packages for Ubuntu 18.04.5 amd64 (with the patch from https://bugs.freedesktop.org/show_bug.cgi?id=865 applied) to https://drive.google.com/drive/folders/1s4NavrQ4LBrafbTBd3ASRZ22vK7Nblvc?usp=sharing Generally, to get the topic issue fixed, you need to install only one of the packages: xserver-xorg-core- hwe-18.04_1.20.8-2ubuntu2.2~18.04.1_amd64.deb To apply the patch and build the binaries and packages, I used my script mentioned in comment #25. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1683383 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen) Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Status in xorg package in Debian: New Bug description: From duplicate bug 1720364 report. Steps to reproduce: 1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 17.10 or 18.04 LTS. 2. Set-up two keyboard layouts - English and Russian 3. Set as keyboard layout switcher in mate-control-center 4. Try to use shortcuts starting from : 4.1. Open Firefox, open new tab, go to some site in it, close tab, try to click to restore closed tab. 4.2. Open mate-terminal, try to open new tab with , or copy (), or paste (). 4.3. Open pluma, write some text, try to navigate in it with . Expected results: switches keyboard layout, shortcuts starting from work normally. Actual results: switches keyboard layout, shortcuts starting from do not work. Notes: 1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with keyboard layout switcher. 2. This problem was discovered before on 13.10, 14.04 and other modern versions with GNOME desktop (Metacity and Compiz) - see bug 1245473. --- Original description below: This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04 Zesty Zapus. This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. Apparently, the bug has reappeared after the patch that used to fix the problem (208_switch_on_release.diff) has been removed from X.Org 1.19 packages. There is an updated patch in the upstream ticket https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xserver-xorg-core 2:1.19.3-1ubuntu1 Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 17 17:46:35 2017 InstallationDate: Installed on 2015-05-01 (716 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: xorg-server UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1683383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892521] [NEW] UI bug - system fonts enlarge after every reboot
You have been subscribed to a public bug: I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after a RECENT UPDATE (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - the fonts automatically scale up after every reboot and ruin the look of my desktop.I had never encountered this problem before.It can be fixed by manually scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I really would love to have this fixed. ** Affects: mutter (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bot-comment -- UI bug - system fonts enlarge after every reboot https://bugs.launchpad.net/bugs/1892521 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 1892521] Re: UI bug - system fonts enlarge after every reboot
** Description changed: I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after a RECENT UPDATE - (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - + (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - the fonts automatically scale up after every reboot and ruin the look of my desktop.I had never encountered this problem before.It can be fixed by manually scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I really would love to have this fixed. ** 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/1892521 Title: UI bug - system fonts enlarge after every reboot Status in mutter package in Ubuntu: Confirmed Bug description: I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after a RECENT UPDATE (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - the fonts automatically scale up after every reboot and ruin the look of my desktop.I had never encountered this problem before.It can be fixed by manually scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I really would love to have this fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
It is finally fixed! <3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892569] [NEW] Font scaling not working correctly 20.04
Public bug reported: During log in screen and after all text on desktop is enlarged. (no accessibility settings are turned on) During log in, text scaling can be reset by turning on and off the text scaling accessibility option, however scaling after login is still messed up. After log in, manual reset of font scaling factor in gnome-tweak software is needed. Settings are not saved after reboot. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1892569 Title: Font scaling not working correctly 20.04 Status in gnome-shell package in Ubuntu: New Bug description: During log in screen and after all text on desktop is enlarged. (no accessibility settings are turned on) During log in, text scaling can be reset by turning on and off the text scaling accessibility option, however scaling after login is still messed up. After log in, manual reset of font scaling factor in gnome-tweak software is needed. Settings are not saved after reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892521] Re: UI bug - system fonts enlarge after every reboot
Some more information on my experience with this issue. I have upgraded mutter on two other machines and neither exhibit the same behaviour. 1 - Desktop - 1920x1080 - AMD Pitcairn - No Issue 2 - Laptop - 1920x1080 - Mesa Intel UHD Graphics (CML GT2) - No Issue 3 - Desktop - 3440x1440 GeForce GTX 950 - Nvidia Driver (440) - Issue Exists -- 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/1892521 Title: UI bug - system fonts enlarge after every reboot Status in mutter package in Ubuntu: Confirmed Bug description: I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after a RECENT UPDATE (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - the fonts automatically scale up after every reboot and ruin the look of my desktop.I had never encountered this problem before.It can be fixed by manually scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I really would love to have this fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854912] Re: Installation stuck at 0%
Thank you for reporting this bug to Ubuntu. Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-software (Ubuntu) Status: New => Incomplete ** Changed in: pinta (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1854912 Title: Installation stuck at 0% Status in gnome-software package in Ubuntu: Incomplete Status in pinta package in Ubuntu: Incomplete Bug description: 1) Ubuntu 19.10 2) 3.30.6-2ubuntu10.19.10.0 3) I searched for "Pinta" in Unbuntu Software. I clicked the installation button, I expected it to install. 4) The install got stuck at 0% for several minutes. I was able to load a webpage, so my internet connection was good. I cancelled the installation of Pinta. Launch and Remove buttons appeared. If I click the launch button, nothing happens. Pinta is listed on the install screen. If I click the Remove button, I get a removal confirmation message. If I click the Remove button, there is a "Unable to remove Pinta" notification. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-28 (36 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu10.19.10.0 Package: gnome-software 3.30.6-2ubuntu10.19.10.0 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Tags: wayland-session eoan Uname: Linux 5.3.0-23-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-software/+bug/1854912/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
No it is not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Somehow after I updated through update-manager about an hour ago and restart, now it is working fine. I also notice a scroll bar on loginscreen (although I have only one user). After logged in, I notice the text (previous was 1.25) to seem a bit larger.. And I goto settings/monitor. Now (at least for me) fractional scaling is working. What I tested: 100%->125% 125%->100% 125%->150% 150%->100% and everything was as expected. What can I do to check it further? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
checked again every possible change.. (ecxept from 200%) and everything is working fine! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1842191] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()
*** This bug is a duplicate of bug 1842022 *** https://bugs.launchpad.net/bugs/1842022 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1842191 Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names() Status in ibus package in Ubuntu: Confirmed Bug description: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 ibus: Installed: 1.5.19-4ubuntu2 Candidate: 1.5.19-4ubuntu2 Version table: *** 1.5.19-4ubuntu2 500 500 http://ubuntu.ethz.ch/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Just logged in, and saw an app crash. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: ibus 1.5.19-4ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 31 21:22:14 2019 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2015-10-06 (1424 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151006) ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 SegvAnalysis: Segfault happened at: 0x7fa961aceabb : orq $0x0,(%rsp) PC (0x7fa961aceabb) ok source "$0x0" ok destination "(%rsp)" (0x7ffe74b35f00) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libibus-1.0.so.5 ibus_bus_get_engines_by_names () from /usr/lib/x86_64-linux-gnu/libibus-1.0.so.5 ?? () ?? () g_cclosure_marshal_VOID__STRINGv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names() UpgradeStatus: Upgraded to eoan on 2019-07-13 (48 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1842191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Fractional Scaling works for me after update. NVIDIA Corporation GM204 [GeForce GTX 970] Scrolling and 4K videos are very laggy in 125%, 150% and 175% mode. Tested with: - NVIDIA driver metapackage from nvidia-driver-440 (proprietary) - NVIDIA driver metapackage from nvidia-driver-450 (open-source) 1 x 4K-Monitor (125%) 1 x FHD-Monitor (100%) Used this command to see GPU usage: $ watch -n 0.5 nvidia-smi Watching 4k Video (120fps): - no scaling: 25% capacity - with scaling: 65% capacity (sometimes flickering and black screen) No interaction: - no scaling: 3% capacity - with scaling: 6% capacity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892573] [NEW] syslog gdm-x-session "your system is too slow" as desktop GUI slows down and eventually stops
Public bug reported: After ~72 hours, my Gnome desktop will be very slow. In syslog I noticed that I get a bunch of these messages as the system slows down: /usr/lib/gdm3/gdm-x-session[13460]: (EE) client bug: timer event6 debounce short: scheduled expiry is in the past (-30ms), your system is too slow ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.4-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 22 18:02:23 2020 InstallationDate: Installed on 2020-02-23 (181 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1892573 Title: syslog gdm-x-session "your system is too slow" as desktop GUI slows down and eventually stops Status in mutter package in Ubuntu: New Bug description: After ~72 hours, my Gnome desktop will be very slow. In syslog I noticed that I get a bunch of these messages as the system slows down: /usr/lib/gdm3/gdm-x-session[13460]: (EE) client bug: timer event6 debounce short: scheduled expiry is in the past (-30ms), your system is too slow ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.4-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 22 18:02:23 2020 InstallationDate: Installed on 2020-02-23 (181 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) 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/1892573/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892521] Re: UI bug - system fonts enlarge after every reboot
My laptop has a resolution of 1366x768 and I too use the Nvidia Driver 440. Could it be an Nvidia thing? -- 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/1892521 Title: UI bug - system fonts enlarge after every reboot Status in mutter package in Ubuntu: Confirmed Bug description: I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after a RECENT UPDATE (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - the fonts automatically scale up after every reboot and ruin the look of my desktop.I had never encountered this problem before.It can be fixed by manually scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I really would love to have this fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
Same problem here, just happened this morning. --- vartan@system76:~$ ps axu | grep gvfsd gdm 4984 0.0 0.0 248336 7500 ?Ssl Aug20 0:00 /usr/libexec/gvfsd gdm 5002 0.0 0.0 312800 6360 ?Sl Aug20 0:00 /usr/libexec/gvfsd-fuse /run/user/125/gvfs -f -o big_writes vartan 6798 0.0 0.0 248440 7748 ?Ssl Aug20 0:00 /usr/libexec/gvfsd vartan 6803 0.0 0.0 378336 6504 ?Sl Aug20 0:00 /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes vartan 7182 0.0 0.0 322844 8520 ?Sl Aug20 0:00 /usr/libexec/gvfsd-trash --spawner :1.3 /org/gtk/gvfs/exec_spaw/0 vartan 7337 0.0 0.0 171368 6764 ?Ssl Aug20 0:00 /usr/libexec/gvfsd-metadata vartan242879 0.0 0.0 396620 8880 ?Sl Aug21 0:00 /usr/libexec/gvfsd-network --spawner :1.3 /org/gtk/gvfs/exec_spaw/2 vartan242922 0.0 0.0 323604 8360 ?Sl Aug21 0:00 /usr/libexec/gvfsd-dnssd --spawner :1.3 /org/gtk/gvfs/exec_spaw/4 vartan330214 0.0 0.0 17664 2500 pts/1S+ 09:46 0:00 grep --color=auto gvfsd --- Distributor ID: Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal --- Linux system76 5.4.0-7642-generic #46~1597422484~20.04~e78f762~dev-Ubuntu SMP Wed Aug 19 14:32:27 x86_64 x86_64 x86_64 GNU/Linux --- GNOME Shell 3.36.4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: In disco, when policykit prompted me for a password in order for update-manager to dispatch instructions to aptdaemon to perform package updates, the password dialog remained on the screen after I clicked 'authenticate'. The window is not clickable, it appears not to even be a window - mouse presses are received by the window underneath. The exception is that the 'cancel' button is active and receives mouse events - but clicking it does nothing. This may be a gnome-shell issue rather than policykit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: policykit-1 0.105-25 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 13:14:33 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: policykit-1 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1824874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892580] [NEW] [HDA-Intel - HDA Intel, playback] No sound at all
You have been subscribed to a public bug: Running Linux Ubuntu 20.04 via VirtualBox but am encountering no sound. My primary laptop does have sound but when I run Ubuntu via VirtualBox, there is no sound. Did have sound initially when I first installed Ubuntu but audio went out after I installed updates. Tried installing Alsamixer and PulseAudio Volume Control but both could not fix issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jtm1625 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Aug 22 03:12:44 2020 InstallationDate: Installed on 2020-08-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jtm1625 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- [HDA-Intel - HDA Intel, playback] No sound at all https://bugs.launchpad.net/bugs/1892580 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver 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 1892584] [NEW] wine game 'rune classic' hungs the OS on exit
Public bug reported: Hello! Rune Classic hungs OS on exit (music plays, but X or keyboard caps lock not responding), Debian 10 works fine. https://www.gog.com/game/rune_classic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-video-amdgpu 19.1.0-1 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.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 22 19:03:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10: added wireguard, 1.0.20200611: added GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Picasso [1043:1b11] MachineType: ASUSTeK COMPUTER INC. ZenBook UX431DA_UM431DA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=/dev/mapper/vg0-root ro SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX431DA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX431DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX431DA.301:bd09/11/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431DA_UM431DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX431DA_UM431DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1892584 Title: wine game 'rune classic' hungs the OS on exit Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Hello! Rune Classic hungs OS on exit (music plays, but X or keyboard caps lock not responding), Debian 10 works fine. https://www.gog.com/game/rune_classic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-video-amdgpu 19.1.0-1 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.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 22 19:03:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10: added wireguard, 1.0.20200611: added GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Picasso [1043:1b11] MachineType: ASUSTeK COMPUTER INC. ZenBook UX431DA_UM431DA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=/dev/mapper/vg0-root ro SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX431DA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX431DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX431DA.301:bd09/11/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX431DA_UM431DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX431DA_UM431DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu
[Desktop-packages] [Bug 1892580] Re: [HDA-Intel - HDA Intel, playback] No sound at all
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1892580 Title: [HDA-Intel - HDA Intel, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Running Linux Ubuntu 20.04 via VirtualBox but am encountering no sound. My primary laptop does have sound but when I run Ubuntu via VirtualBox, there is no sound. Did have sound initially when I first installed Ubuntu but audio went out after I installed updates. Tried installing Alsamixer and PulseAudio Volume Control but both could not fix issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jtm1625 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Aug 22 03:12:44 2020 InstallationDate: Installed on 2020-08-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jtm1625 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1892580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892588] [NEW] package libreoffice-help-common 1:6.4.4-0ubuntu0.20.04.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Public bug reported: The error was occured ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-help-common 1:6.4.4-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Aug 22 12:15:19 2020 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2020-04-26 (118 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libreoffice Title: package libreoffice-help-common 1:6.4.4-0ubuntu0.20.04.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1892588 Title: package libreoffice-help-common 1:6.4.4-0ubuntu0.20.04.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in libreoffice package in Ubuntu: New Bug description: The error was occured ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-help-common 1:6.4.4-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Aug 22 12:15:19 2020 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2020-04-26 (118 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libreoffice Title: package libreoffice-help-common 1:6.4.4-0ubuntu0.20.04.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1892588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892588] Re: package libreoffice-help-common 1:6.4.4-0ubuntu0.20.04.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1892588 Title: package libreoffice-help-common 1:6.4.4-0ubuntu0.20.04.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in libreoffice package in Ubuntu: New Bug description: The error was occured ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-help-common 1:6.4.4-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Aug 22 12:15:19 2020 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2020-04-26 (118 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libreoffice Title: package libreoffice-help-common 1:6.4.4-0ubuntu0.20.04.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1892588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Fractional scaling also works again for me after the update. Only problem I now have is some freezing / lag when I watch 4k videos (e.g. via YouTube) I tried different browsers, 4K videos play a bit better on chrome (less lag) then on Firefox. Scrolling is also slow / laggy. Did not have these issues with the workaround. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892588] Re: package libreoffice-help-common 1:6.4.4-0ubuntu0.20.04.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: fsys-tarfile-error ** Changed in: libreoffice (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1892588 Title: package libreoffice-help-common 1:6.4.4-0ubuntu0.20.04.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in libreoffice package in Ubuntu: Invalid Bug description: The error was occured ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-help-common 1:6.4.4-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Aug 22 12:15:19 2020 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2020-04-26 (118 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libreoffice Title: package libreoffice-help-common 1:6.4.4-0ubuntu0.20.04.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1892588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891183] Re: the new -server drivers break nvidia-detector
Here is the output without the fix: Traceback (most recent call last): File "/usr/bin/nvidia-detector", line 8, in a = NvidiaDetection(printonly=True, verbose=False) File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line 73, in __init__ self.getData() File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line 163, in getData driver_version = self.__get_value_from_name(stripped_package_name) File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line 92, in __get_value_from_name v = int(name) ValueError: invalid literal for int() with base 10: 'server' Here are is my solution: In function # line 88 def __get_value_from_name(self, name): '''Get the integer associated to the name of a driver''' v = self.__driver_aliases.get(name) if v is None: if name.isdigit(): # I made sure is an int. v = int(name) return v # in line 164 I replaced with : if not (driver_version := self.__get_value_from_name(stripped_package_name)): continue ** Attachment added: "nvidiadetector.py" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1891183/+attachment/5403712/+files/nvidiadetector.py -- 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/1891183 Title: the new -server drivers break nvidia-detector Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Focal: In Progress Bug description: Calling nvidia-detector, fails when the new -server series are available in the archive: nvidia-detector Traceback (most recent call last): File "/usr/bin/nvidia-detector", line 8, in a = NvidiaDetection(printonly=True, verbose=False) File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line 73, in __init__ self.getData() File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line 163, in getData driver_version = self.__get_value_from_name(stripped_package_name) File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line 92, in __get_value_from_name v = int(name) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1891183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891183] Re: the new -server drivers break nvidia-detector
The attachment "nvidiadetector.py" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1891183 Title: the new -server drivers break nvidia-detector Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Focal: In Progress Bug description: Calling nvidia-detector, fails when the new -server series are available in the archive: nvidia-detector Traceback (most recent call last): File "/usr/bin/nvidia-detector", line 8, in a = NvidiaDetection(printonly=True, verbose=False) File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line 73, in __init__ self.getData() File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line 163, in getData driver_version = self.__get_value_from_name(stripped_package_name) File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line 92, in __get_value_from_name v = int(name) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1891183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892600] [NEW] pdfannotextractor launch script is missing "-jar" flag
Public bug reported:
pdfannotextractor is a script that is part of the pax package that is
part of texlive-latex-extra : https://packages.ubuntu.com/focal/texlive-
latex-extra
The default installation throws this error:
$ pdfannotextractor --debug submission.pdf
PDFAnnotExtractor 0.1l, 2012/04/18 - Copyright (c) 2008, 2011, 2012 by Heiko
Oberdiek.
* CLASSPATH: []
* is_win: [0]
* Which kpsewhich: [/usr/bin/kpsewhich]
* Backticks: [kpsewhich --progname pdfannotextractor --format texmfscripts
pax.jar]
* Exit code: [0/success]
* pax.jar: [/usr/share/texlive/texmf-dist/scripts/pax/pax.jar]
* pdfbox.jar: [/usr/share/java/pdfbox.jar]
* Which java: [/usr/bin/java]
* System: [java /usr/share/texlive/texmf-dist/scripts/pax/pax.jar
submission.pdf]
Error: Could not find or load main class
.usr.share.texlive.texmf-dist.scripts.pax.pax.jar
Caused by: java.lang.ClassNotFoundException:
/usr/share/texlive/texmf-dist/scripts/pax/pax/jar
* Exit code: [1]
The problem is that the classpath is not properly configured to use the
jar. Simply adding the "-jar" flag solves the problem:
$ java -jar /usr/share/texlive/texmf-dist/scripts/pax/pax.jar submission.pdf
* Processing file `submission.pdf' ...
In the code, pdfannotextractor.pl, the change would be located here:
sub launch_pax () {
check_prg $prg_java, 1;
my @cmd = ($prg_java);
push @cmd, $path_jar_pax;
push @cmd, @ARGV;
debug 'System', "@cmd";
Description:Ubuntu 20.04.1 LTS
Release:20.04
Codename: focal
** Affects: texlive-extra (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-extra in Ubuntu.
https://bugs.launchpad.net/bugs/1892600
Title:
pdfannotextractor launch script is missing "-jar" flag
Status in texlive-extra package in Ubuntu:
New
Bug description:
pdfannotextractor is a script that is part of the pax package that is
part of texlive-latex-extra : https://packages.ubuntu.com/focal
/texlive-latex-extra
The default installation throws this error:
$ pdfannotextractor --debug submission.pdf
PDFAnnotExtractor 0.1l, 2012/04/18 - Copyright (c) 2008, 2011, 2012 by Heiko
Oberdiek.
* CLASSPATH: []
* is_win: [0]
* Which kpsewhich: [/usr/bin/kpsewhich]
* Backticks: [kpsewhich --progname pdfannotextractor --format texmfscripts
pax.jar]
* Exit code: [0/success]
* pax.jar: [/usr/share/texlive/texmf-dist/scripts/pax/pax.jar]
* pdfbox.jar: [/usr/share/java/pdfbox.jar]
* Which java: [/usr/bin/java]
* System: [java /usr/share/texlive/texmf-dist/scripts/pax/pax.jar
submission.pdf]
Error: Could not find or load main class
.usr.share.texlive.texmf-dist.scripts.pax.pax.jar
Caused by: java.lang.ClassNotFoundException:
/usr/share/texlive/texmf-dist/scripts/pax/pax/jar
* Exit code: [1]
The problem is that the classpath is not properly configured to use
the jar. Simply adding the "-jar" flag solves the problem:
$ java -jar /usr/share/texlive/texmf-dist/scripts/pax/pax.jar submission.pdf
* Processing file `submission.pdf' ...
In the code, pdfannotextractor.pl, the change would be located here:
sub launch_pax () {
check_prg $prg_java, 1;
my @cmd = ($prg_java);
push @cmd, $path_jar_pax;
push @cmd, @ARGV;
debug 'System', "@cmd";
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Codename: focal
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1892600/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Fractional scalling still not working for me at all. Same exactly behavior as before. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890141] Re: Can't fullscreen, or windows get automatically un-fullscreened, when using fractional scaling
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1890141 Title: Can't fullscreen, or windows get automatically un-fullscreened, when using fractional scaling Status in mutter package in Ubuntu: Confirmed Bug description: Same issue as this one: https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1863391 Some websites like YouTube will attempt to fullscreen, just not successfully. Other websites, like Netflix, will fullscreen for a second and de-fullscreen after that. Some games act weirdly in fullscreen mode (this might be related, as I've never had this issue before now: https://github.com/ValveSoftware/csgo-osx- linux/issues/2429). EDIT: This only happens when fractional scaling is enabled. My config; main 4K screen at 150% and secondary 1080p screen to the right at 100%. YouTube fullscreens fine on the sec. screen (1080 100%). This is a gif I posted in the related bug report showing exactly what happens: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1863391/+attachment/5397743/+files/20200731_160007.gif ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 3 14:03:00 2020 InstallationDate: Installed on 2020-07-30 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1890141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890141] Re: Can't fullscreen, or windows get automatically un-fullscreened, when using fractional scaling
https://www.reddit.com/r/Ubuntu/comments/iesevz/fractional_scaling_full_screen_video_causes_this/?utm_source=share&utm_medium=ios_app&utm_name=iossmf This is my video link which I posted on Reddit, same bug has affected me with i915 driver. One little note: This isn’t a case when I added upscaled monitor resolution (for me, it is 2160x1440 150% to 2880x1920 200%) config and setting intel to modesetting driver on /etc/X11/xorg.conf.d There are two options for setting the correct scaling: 1. Using xrandr scaling options, causes tearing and fullscreen inconsistencies 2. Adding new upscaled monitor resolution with xrandr and choosing that Second options has always worked flawlessly for me, but want to make a warning: second option doesn’t work on between kernel 5.0 and 5.4 (that means it doesn’t work on LTS kernel). They reverted a patch after 5.5, and it works flawlessly. Here’s the trick files that I’ve created: https://github.com/nekr0z/linux-on-huawei-matebook-13-2019#display I think Ubuntu’s X11 fractional scaling method uses the first one, and that’s indeed buggy. -- 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/1890141 Title: Can't fullscreen, or windows get automatically un-fullscreened, when using fractional scaling Status in mutter package in Ubuntu: Confirmed Bug description: Same issue as this one: https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1863391 Some websites like YouTube will attempt to fullscreen, just not successfully. Other websites, like Netflix, will fullscreen for a second and de-fullscreen after that. Some games act weirdly in fullscreen mode (this might be related, as I've never had this issue before now: https://github.com/ValveSoftware/csgo-osx- linux/issues/2429). EDIT: This only happens when fractional scaling is enabled. My config; main 4K screen at 150% and secondary 1080p screen to the right at 100%. YouTube fullscreens fine on the sec. screen (1080 100%). This is a gif I posted in the related bug report showing exactly what happens: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1863391/+attachment/5397743/+files/20200731_160007.gif ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 3 14:03:00 2020 InstallationDate: Installed on 2020-07-30 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1890141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Hi Stefano, > sudo evtest > > > /dev/input/event17: Elan Touchpad > /dev/input/event18: MSFT0001:00 04F3:3140 > Select the device event number [0-27]: 17 > Input driver version is 1.0.1 > Input device ID: bus 0x18 vendor 0x4f3 product 0x3140 version 0x100 > Input device name: "Elan Touchpad" > Supported events: > Event type 0 (EV_SYN) > Event type 1 (EV_KEY) > Event code 272 (BTN_LEFT) > Event code 325 (BTN_TOOL_FINGER) > Event code 328 (BTN_TOOL_QUINTTAP) > Event code 330 (BTN_TOUCH) > Event code 333 (BTN_TOOL_DOUBLETAP) > Event code 334 (BTN_TOOL_TRIPLETAP) > Event code 335 (BTN_TOOL_QUADTAP) > Event type 3 (EV_ABS) > Event code 0 (ABS_X) > Value 0 > Min 0 > Max 3209 > Resolution 31 > Event code 1 (ABS_Y) > Value 0 > Min 0 > Max 2097 > Resolution 31 > Event code 24 (ABS_PRESSURE) > Value 0 > Min 0 > Max 255 > Event code 47 (ABS_MT_SLOT) > Value 0 > Min 0 > Max 4 > Event code 53 (ABS_MT_POSITION_X) > Value 0 > Min 0 > Max 3209 > Event code 54 (ABS_MT_POSITION_Y) > Value 0 > Min 0 > Max 2097 > Event code 57 (ABS_MT_TRACKING_ID) > Value 0 > Min 0 > Max 65535 > Event code 58 (ABS_MT_PRESSURE) > Value 0 > Min 0 > Max 255 > Properties: > Property type 0 (INPUT_PROP_POINTER) > Property type 2 (INPUT_PROP_BUTTONPAD) > Testing ... (interrupt to exit) > > Thank you for providing this! So "*_PRESSURE" events are also supported. When you move your fingers or touch the touchpad, are there any event as follows reported? > Event: time 1597225994.180980, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), > value 0 > Event: time 1597225994.180980, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), > value 765 > Event: time 1597225994.180980, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), > value 220 > Event: time 1597225994.180980, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generi
[Desktop-packages] [Bug 1892605] [NEW] Since mutter updated to 3.36.4-0ubuntu0.20.04.2, the nvidia-390 driver package from apt does not work properly. On every start the top panel and font size in gno
Public bug reported: Already tried to install the nvidia 390 driver from nvidias .run installer, but this is also not running without the use of nouveau and log in to 'Ubuntu on Wayland'. The problem is that the scaling has become abnormal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.4-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 02:10:51 2020 InstallationDate: Installed on 2020-04-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Attachment added: "nvidia-installer.log and gpu-manager.log after the switch to nvidia-390 outside the apt sources." https://bugs.launchpad.net/bugs/1892605/+attachment/5403751/+files/logs.tar.xz -- 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/1892605 Title: Since mutter updated to 3.36.4-0ubuntu0.20.04.2, the nvidia-390 driver package from apt does not work properly. On every start the top panel and font size in gnome is shrinked. Status in mutter package in Ubuntu: New Bug description: Already tried to install the nvidia 390 driver from nvidias .run installer, but this is also not running without the use of nouveau and log in to 'Ubuntu on Wayland'. The problem is that the scaling has become abnormal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.4-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 02:10:51 2020 InstallationDate: Installed on 2020-04-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1892605/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
hey Coybi, unfortunately using the 'elan touchpad patch' didn't work because probably MSFT0001:00 04F3:3140 is not an elan device. with and without patch, no events are ever recorded by pressing or swiping the surface of the TouchPad -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LEN
[Desktop-packages] [Bug 1824855]
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. -- 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/1824855 Title: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..." Status in fprintd package in Ubuntu: Won't Fix Status in gnome-shell package in Ubuntu: Won't Fix Status in fprintd package in Fedora: Won't Fix Bug description: When waking my laptop screen up at the lock screen, it takes a very long time to display the password prompt (definitely longer than 30s, possibly longer than 1m - I didn't time it). I notice that while waiting for the password prompt, the screen is showing a full list of (obfuscated) desktop notifications. After logging in, I used the gnome-shell interface to clear the notifications; then I locked my screen again, at which point hitting the space bar caused the password prompt to show up immediately. So it looks like the time to display the password prompt might scale linearly with the number of notifications; which is not useful, because there is a finite number of (obfuscated!) notifications that will be displayed on the lock screen, and AFAIK you can't interact with them through the lock screen at all. So we shouldn't be wasting time processing (and presumably rendering) notifications that will never be visible. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 09:58:23 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1824855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824855]
Created attachment 1712228 strace output of "fprintd-list $USER" -- 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/1824855 Title: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..." Status in fprintd package in Ubuntu: Won't Fix Status in gnome-shell package in Ubuntu: Won't Fix Status in fprintd package in Fedora: Won't Fix Bug description: When waking my laptop screen up at the lock screen, it takes a very long time to display the password prompt (definitely longer than 30s, possibly longer than 1m - I didn't time it). I notice that while waiting for the password prompt, the screen is showing a full list of (obfuscated) desktop notifications. After logging in, I used the gnome-shell interface to clear the notifications; then I locked my screen again, at which point hitting the space bar caused the password prompt to show up immediately. So it looks like the time to display the password prompt might scale linearly with the number of notifications; which is not useful, because there is a finite number of (obfuscated!) notifications that will be displayed on the lock screen, and AFAIK you can't interact with them through the lock screen at all. So we shouldn't be wasting time processing (and presumably rendering) notifications that will never be visible. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 09:58:23 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1824855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824855]
# strace -o /tmp/strace_fprintd-list.out -tt -f fprintd-list $USER list_devices failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. strace_fprintd-list.out in attachment ; command hangs at '2570072 10:44:27.207763 restart_syscall(<... resuming interrupted restart_syscall ...>' -- 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/1824855 Title: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..." Status in fprintd package in Ubuntu: Won't Fix Status in gnome-shell package in Ubuntu: Won't Fix Status in fprintd package in Fedora: Won't Fix Bug description: When waking my laptop screen up at the lock screen, it takes a very long time to display the password prompt (definitely longer than 30s, possibly longer than 1m - I didn't time it). I notice that while waiting for the password prompt, the screen is showing a full list of (obfuscated) desktop notifications. After logging in, I used the gnome-shell interface to clear the notifications; then I locked my screen again, at which point hitting the space bar caused the password prompt to show up immediately. So it looks like the time to display the password prompt might scale linearly with the number of notifications; which is not useful, because there is a finite number of (obfuscated!) notifications that will be displayed on the lock screen, and AFAIK you can't interact with them through the lock screen at all. So we shouldn't be wasting time processing (and presumably rendering) notifications that will never be visible. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 09:58:23 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1824855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824855]
Can this bz be reopened, or do I need to file a new bug report against F32 ? -- 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/1824855 Title: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..." Status in fprintd package in Ubuntu: Won't Fix Status in gnome-shell package in Ubuntu: Won't Fix Status in fprintd package in Fedora: Won't Fix Bug description: When waking my laptop screen up at the lock screen, it takes a very long time to display the password prompt (definitely longer than 30s, possibly longer than 1m - I didn't time it). I notice that while waiting for the password prompt, the screen is showing a full list of (obfuscated) desktop notifications. After logging in, I used the gnome-shell interface to clear the notifications; then I locked my screen again, at which point hitting the space bar caused the password prompt to show up immediately. So it looks like the time to display the password prompt might scale linearly with the number of notifications; which is not useful, because there is a finite number of (obfuscated!) notifications that will be displayed on the lock screen, and AFAIK you can't interact with them through the lock screen at all. So we shouldn't be wasting time processing (and presumably rendering) notifications that will never be visible. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 09:58:23 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1824855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824855]
Encountering this issue on an up-to-date F32 : systemd-245.7-1.fc32.x86_64 fprintd-1.90.1-1.fc32.x86_64 -- 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/1824855 Title: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..." Status in fprintd package in Ubuntu: Won't Fix Status in gnome-shell package in Ubuntu: Won't Fix Status in fprintd package in Fedora: Won't Fix Bug description: When waking my laptop screen up at the lock screen, it takes a very long time to display the password prompt (definitely longer than 30s, possibly longer than 1m - I didn't time it). I notice that while waiting for the password prompt, the screen is showing a full list of (obfuscated) desktop notifications. After logging in, I used the gnome-shell interface to clear the notifications; then I locked my screen again, at which point hitting the space bar caused the password prompt to show up immediately. So it looks like the time to display the password prompt might scale linearly with the number of notifications; which is not useful, because there is a finite number of (obfuscated!) notifications that will be displayed on the lock screen, and AFAIK you can't interact with them through the lock screen at all. So we shouldn't be wasting time processing (and presumably rendering) notifications that will never be visible. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 09:58:23 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1824855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824855]
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- 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/1824855 Title: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..." Status in fprintd package in Ubuntu: Won't Fix Status in gnome-shell package in Ubuntu: Won't Fix Status in fprintd package in Fedora: Won't Fix Bug description: When waking my laptop screen up at the lock screen, it takes a very long time to display the password prompt (definitely longer than 30s, possibly longer than 1m - I didn't time it). I notice that while waiting for the password prompt, the screen is showing a full list of (obfuscated) desktop notifications. After logging in, I used the gnome-shell interface to clear the notifications; then I locked my screen again, at which point hitting the space bar caused the password prompt to show up immediately. So it looks like the time to display the password prompt might scale linearly with the number of notifications; which is not useful, because there is a finite number of (obfuscated!) notifications that will be displayed on the lock screen, and AFAIK you can't interact with them through the lock screen at all. So we shouldn't be wasting time processing (and presumably rendering) notifications that will never be visible. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 09:58:23 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1824855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824855]
$ strace -o /tmp/strace_su.out -tt -f su
strace_su.out in attachment ; command hangs at
'2571952 10:49:47.809422 ppoll([{fd=5, events=POLLIN}], 1, {tv_sec=24,
tv_nsec=3}, NULL, 8'
--
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/1824855
Title:
Unlocking the screen takes a long time after "Starting Fingerprint
Authentication Daemon..."
Status in fprintd package in Ubuntu:
Won't Fix
Status in gnome-shell package in Ubuntu:
Won't Fix
Status in fprintd package in Fedora:
Won't Fix
Bug description:
When waking my laptop screen up at the lock screen, it takes a very
long time to display the password prompt (definitely longer than 30s,
possibly longer than 1m - I didn't time it). I notice that while
waiting for the password prompt, the screen is showing a full list of
(obfuscated) desktop notifications. After logging in, I used the
gnome-shell interface to clear the notifications; then I locked my
screen again, at which point hitting the space bar caused the password
prompt to show up immediately.
So it looks like the time to display the password prompt might scale
linearly with the number of notifications; which is not useful,
because there is a finite number of (obfuscated!) notifications that
will be displayed on the lock screen, and AFAIK you can't interact
with them through the lock screen at all. So we shouldn't be wasting
time processing (and presumably rendering) notifications that will
never be visible.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gdm3 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 15 09:58:23 2019
InstallationDate: Installed on 2010-09-24 (3125 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64
(20100816.1)
SourcePackage: gdm3
UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1824855/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824855]
Note : this behaviour usually starts to occur after a couple of days uptime (this is on a Dell XPS7390 2-in-1 with unrecognized fingerprint reader), for every action which requires authentication (su, sudo, virt- manager, screensaver unlocking). journalctl error message (for the "su" example from comment#20) : Aug 22 10:50:12 mymachine su[2571952]: pam_fprintd(su:auth): GetDevices failed: Connection timed out -- 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/1824855 Title: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..." Status in fprintd package in Ubuntu: Won't Fix Status in gnome-shell package in Ubuntu: Won't Fix Status in fprintd package in Fedora: Won't Fix Bug description: When waking my laptop screen up at the lock screen, it takes a very long time to display the password prompt (definitely longer than 30s, possibly longer than 1m - I didn't time it). I notice that while waiting for the password prompt, the screen is showing a full list of (obfuscated) desktop notifications. After logging in, I used the gnome-shell interface to clear the notifications; then I locked my screen again, at which point hitting the space bar caused the password prompt to show up immediately. So it looks like the time to display the password prompt might scale linearly with the number of notifications; which is not useful, because there is a finite number of (obfuscated!) notifications that will be displayed on the lock screen, and AFAIK you can't interact with them through the lock screen at all. So we shouldn't be wasting time processing (and presumably rendering) notifications that will never be visible. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 09:58:23 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1824855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824855]
Created attachment 1712229 strace output of "su" -- 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/1824855 Title: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..." Status in fprintd package in Ubuntu: Won't Fix Status in gnome-shell package in Ubuntu: Won't Fix Status in fprintd package in Fedora: Won't Fix Bug description: When waking my laptop screen up at the lock screen, it takes a very long time to display the password prompt (definitely longer than 30s, possibly longer than 1m - I didn't time it). I notice that while waiting for the password prompt, the screen is showing a full list of (obfuscated) desktop notifications. After logging in, I used the gnome-shell interface to clear the notifications; then I locked my screen again, at which point hitting the space bar caused the password prompt to show up immediately. So it looks like the time to display the password prompt might scale linearly with the number of notifications; which is not useful, because there is a finite number of (obfuscated!) notifications that will be displayed on the lock screen, and AFAIK you can't interact with them through the lock screen at all. So we shouldn't be wasting time processing (and presumably rendering) notifications that will never be visible. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 09:58:23 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1824855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824855] Re: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..."
** Changed in: fprintd (Fedora) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1824855 Title: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..." Status in fprintd package in Ubuntu: Won't Fix Status in gnome-shell package in Ubuntu: Won't Fix Status in fprintd package in Fedora: Won't Fix Bug description: When waking my laptop screen up at the lock screen, it takes a very long time to display the password prompt (definitely longer than 30s, possibly longer than 1m - I didn't time it). I notice that while waiting for the password prompt, the screen is showing a full list of (obfuscated) desktop notifications. After logging in, I used the gnome-shell interface to clear the notifications; then I locked my screen again, at which point hitting the space bar caused the password prompt to show up immediately. So it looks like the time to display the password prompt might scale linearly with the number of notifications; which is not useful, because there is a finite number of (obfuscated!) notifications that will be displayed on the lock screen, and AFAIK you can't interact with them through the lock screen at all. So we shouldn't be wasting time processing (and presumably rendering) notifications that will never be visible. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 09:58:23 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1824855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Happy to say that for that for me at least it works. No more choppy mouse movement and I am able to use both my monitors with the first in 150% and the second in 175%. I also tested playing some 4k movies in firefox, which worked fine. DP-0 connected primary 5120x2880+0+0 (normal left inverted right x axis y axis) 698mm x 393mm 3840x2160 60.00*+ 59.9450.0029.9829.9725.0023.98 23.98 ... DP-2 connected 4384x2466+5120+0 (normal left inverted right x axis y axis) 521mm x 293mm 3840x2160 60.00*+ 29.98 ... Thanks to all involved for fixing this issue! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884732] Re: The screen freezes every now and then
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1884732 Title: The screen freezes every now and then Status in gnome-shell package in Ubuntu: Expired Bug description: The screen freezes every now and then. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-38.42-generic 5.4.44 Uname: Linux 5.4.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 15:36:58 2020 DistUpgraded: 2020-06-23 14:24:21,927 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:802d] InstallationDate: Installed on 2020-04-25 (58 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Hewlett-Packard HP Spectre Pro x360 G1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-38-generic root=UUID=079528a8-d4db-4fc9-b519-73521b170d15 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-06-23 (0 days ago) dmi.bios.date: 12/17/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 802D dmi.board.vendor: Hewlett-Packard dmi.board.version: 58.51 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.30:bd12/17/2015:svnHewlett-Packard:pnHPSpectreProx360G1:pvr:rvnHewlett-Packard:rn802D:rvr58.51:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre Pro x360 G1 dmi.product.sku: P7Q68PA#ABG dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102+git2006181830.f44908~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2006230730.3fec2f~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx 20.2~git2006230730.3fec2f~oibaf~f version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1884732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862331]
This is the update for all players exited for this just look site here https://fundecade.com/pyramid-solitaire great fun forever here to you seen the hurry to more enjoyments -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1862331 Title: [upstream] mozilla cert8.db and key3.db are denied by apparmor Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: New Bug description: libreoffice accesses firefox's cert8.db and key3.db, i have found this from apparmor log messages. i googled "libreoffice cert8.db key3.db" and have found out that seems libreoffice does this by design. see https://bugs.documentfoundation.org/show_bug.cgi?id=119811 , https://weekly-geekly.github.io/articles/357692/index.html . do you agree with this? then there should be allow rule, i think. if you do not, then should be a comment and / or deny rule. does libreoffice really need write access to these files? i think it can potentially add some bad certificates, and some sites would have verified sign then, while user has not added it to exceptions. i think if user have not secured his master password, it can be considered it is ok if some app can access his passwords. i think this pages also can be helpful: https://stackoverflow.com/questions/45126738/what-is-cert8-db-and-key3 -db-file , https://developer.mozilla.org/en- US/docs/Mozilla/Projects/NSS/tools/NSS_Tools_certutil , these are found by googling "cert8.db key3.db". this also can be helpful: https://en.wikipedia.org/wiki/Public_key_certificate . To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1862331/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892615] [NEW] screen goes down sometimes
Public bug reported: screen automatic goes down while working ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-114.115-generic 4.15.18 Uname: Linux 4.15.0-114-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CompositorRunning: None Date: Sun Aug 23 11:46:09 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-114-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1] InstallationDate: Installed on 2015-10-17 (1771 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-114-generic root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.0B dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C1 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.11 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu May 28 11:49:11 2020 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1892615 Title: screen goes down sometimes Status in xorg package in Ubuntu: New Bug description: screen automatic goes down while working ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-114.115-generic 4.15.18 Uname: Linux 4.15.0-114-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CompositorRunning: None Date: Sun Aug 23 11:46:09 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-114-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1] InstallationDate: Installed on 2015-10-17 (1771 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-114-generic root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.0B dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C1 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.11 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ub
[Desktop-packages] [Bug 1736222] Re: speech-dispatcher distorts all sound
This bug started affecting me in the past week although I've been on 20.04 since launch. I have removed the packages including orca. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1736222 Title: speech-dispatcher distorts all sound Status in speech-dispatcher package in Ubuntu: Confirmed Bug description: So, a brand new computer running Ubuntu 16.04.3 LTS. In hardinfo summary, my audio adapters are • HDA-Intel - HDA Intel HDMI • HDA-Intel - HDA Intel PCH • HDA-Intel - HDA NVidia In detail: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) Memory 16kb (non-prefetchable), snd_hda_intel As soon as I load a website in Firefox that utilizes speech-dispatcher (fimfiction.net) all sounds get distorted, whether I click a paragraph for TTS reading or not. The problem seems to go away if I don't use the site after a while. When I close down Firefox the problem still lingers a bit, but maybe not as long. One thing I did which seemed faster was close down everything, then load what I wanted to listen to (Skype, Discord), and if it still persisted I would go into "Sound Settings" and after a few blinks in that window the sound is normal again. While the site is open, according to "Sound Settings" (from the speaker icon menu) and Pulse Audio Volume Controller (pavu) there are 4 copies of this package. Muting them did not help the problem, but moving one of them, and a very specific one, from the "Built-in Audio Analog Stereo" to something else like HDA NVidia (HDMI 3) seems to be a workaround. Just so you know, I do not use the HDMI cable for sound, but instead use the "headphones" jack. If you need any more details, I'll try to provide them. /Edward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736222] Re: speech-dispatcher distorts all sound
I will try this workaround/config change: https://github.com/brailcom/speechd/issues/198#issuecomment-619605269 ** Bug watch added: github.com/brailcom/speechd/issues #198 https://github.com/brailcom/speechd/issues/198 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1736222 Title: speech-dispatcher distorts all sound Status in speech-dispatcher package in Ubuntu: Confirmed Bug description: So, a brand new computer running Ubuntu 16.04.3 LTS. In hardinfo summary, my audio adapters are • HDA-Intel - HDA Intel HDMI • HDA-Intel - HDA Intel PCH • HDA-Intel - HDA NVidia In detail: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) Memory 16kb (non-prefetchable), snd_hda_intel As soon as I load a website in Firefox that utilizes speech-dispatcher (fimfiction.net) all sounds get distorted, whether I click a paragraph for TTS reading or not. The problem seems to go away if I don't use the site after a while. When I close down Firefox the problem still lingers a bit, but maybe not as long. One thing I did which seemed faster was close down everything, then load what I wanted to listen to (Skype, Discord), and if it still persisted I would go into "Sound Settings" and after a few blinks in that window the sound is normal again. While the site is open, according to "Sound Settings" (from the speaker icon menu) and Pulse Audio Volume Controller (pavu) there are 4 copies of this package. Muting them did not help the problem, but moving one of them, and a very specific one, from the "Built-in Audio Analog Stereo" to something else like HDA NVidia (HDMI 3) seems to be a workaround. Just so you know, I do not use the HDMI cable for sound, but instead use the "headphones" jack. If you need any more details, I'll try to provide them. /Edward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
