[Desktop-packages] [Bug 1942663] [NEW] nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
Public bug reported: из-за ошибки не грузиться система ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-27-generic Date: Fri Sep 3 12:40:31 2021 InstallationDate: Installed on 2021-05-10 (116 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (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 nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1942663 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: из-за ошибки не грузиться система ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-27-generic Date: Fri Sep 3 12:40:31 2021 InstallationDate: Installed on 2021-05-10 (116 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1942663/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934520] Re: Nautilus very slow to start after 20.04 upgrade
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1934520 Title: Nautilus very slow to start after 20.04 upgrade Status in nautilus package in Ubuntu: Expired Bug description: Nautilus takes up to 50 seconds to start, even in save or open dialogs. Attached is the output for time strace -y -f -t -T -o /tmp/nautilus.strace2 nautilus --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-08-11 (1421 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: nautilus 1:3.36.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Tags: focal Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (431 days ago) UserGroups: root wireshark _MarkForUpload: True usr_lib_nautilus: dropbox 2020.03.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934520/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926104] Re: Ubuntu software center lists Wesnoth as proprietary
This bug was fixed in the package wesnoth-1.14 - 1:1.14.17-2 --- wesnoth-1.14 (1:1.14.17-2) unstable; urgency=low * Install appstream metainfo file (LP: #1926104) -- Rhonda D'Vine Thu, 26 Aug 2021 14:19:46 +0200 ** Changed in: wesnoth-1.14 (Ubuntu) Status: Triaged => Fix Released -- 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/1926104 Title: Ubuntu software center lists Wesnoth as proprietary Status in gnome-software package in Ubuntu: Confirmed Status in wesnoth-1.14 package in Ubuntu: Fix Released Bug description: Wesnoth is not under a proprietary license and should not be listed as such in the Ubuntu software center. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1926104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1936643] Re: Logging in to GNOME 40.2.0 causes desktop icon extension to show as application in Activities overview
This bug was fixed in the package gnome-shell - 40.2-1ubuntu6 --- gnome-shell (40.2-1ubuntu6) impish; urgency=medium * d/rules: - Drop dh_translations workaround. gettext used by LP has been updated (LP: #1756547). - Fix Lintian warning about DEB_HOST_ARCH assignment gnome-shell (40.2-1ubuntu5) impish; urgency=medium * Fix translation issues (LP: #1941954): - Really fix translation import problem as reported in LP: #1756547 - Add libgtk-3-bin to Build-Depends for dh_translations gnome-shell (40.2-1ubuntu4) impish; urgency=medium * debian/rules: - Skip tests when building for ppc64el to fix FTBFS (LP: #1941792) gnome-shell (40.2-1ubuntu3) impish; urgency=medium [ Daniel van Vugt ] * Add layout-Make-starting-in-the-overview-optional.patch: - So that extensions like Ubuntu Dock have the option of preventing the shell starting in the overview. (LP: #1940925) gnome-shell (40.2-1ubuntu2) impish; urgency=medium [ Daniel van Vugt ] * Add workspace-Remove-skip-taskbar-windows-while-the-over.patch to stop the desktop icons window appearing like an app window in the overview on startup (LP: #1936643) -- Gunnar Hjalmarsson Wed, 01 Sep 2021 15:44:38 +0200 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- 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/1936643 Title: Logging in to GNOME 40.2.0 causes desktop icon extension to show as application in Activities overview Status in Gnome Shell Extension Desktop Icons Ng: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Won't Fix Bug description: In Ubuntu 21.10 Impish Indri, I have done today's updates, including GNOME 40, and when I rebooted, I saw the desktop icons in the Activities overview that has the grey gears icon and the gibberish name. However, when I clicked on it, I'm taken to the desktop. When I open the Activities overview again, that "application" didn't show up. I suspect that this "application" came from a GNOME extension that handles desktop icons, called gnome-shell-extension-desktop-icons-ng. Because I thought that it loaded AFTER the Activities overview opened at log in. This repeats every time I reboot or just log off and log back in. Steps to reproduce: 1. Update the Impish system to the latest version 2. Reboot 3. Log in Expected results: The "application" that came from the desktop icon shell extension doesn't appear in the Activities overview Actual results: This "application" shows up in the overview with the grey gears icon and the gibberish name every time a user signs in to the new GNOME 40 desktop lsb_release -rd: Description: Ubuntu Impish Indri (development branch) Release: 21.10 apt-cache policy gnome-shell: gnome-shell: Installed: 40.2-1ubuntu1 Candidate: 40.2-1ubuntu1 Version table: *** 40.2-1ubuntu1 500 500 http://sy.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status If there is any more information needed, let me know. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 16 15:07:53 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-02-02 (163 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1936643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934761] Re: gnome keyboard settings panel enforces single iso-level3-shift key
This bug was fixed in the package gnome-control-center - 1:40.0-1ubuntu5 --- gnome-control-center (1:40.0-1ubuntu5) impish; urgency=medium * d/p/keyboard-Create-CcXkbModifierDialog-only-when-used.patch, d/p/keyboard-Rename-XkbOption-and-XkbModifier-with-Cc-prefix.patch: - Avoid Alternate Characters Key unexpected behavior (LP: #1934761) * d/p/keyboard-Avoid-modifying-xkb-options-when-user-changes-n.patch: - Extra 'safety' (LP: #1934761) -- Gunnar Hjalmarsson Thu, 19 Aug 2021 12:58:46 +0200 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1934761 Title: gnome keyboard settings panel enforces single iso-level3-shift key Status in gnome-control-center package in Ubuntu: Fix Released Bug description: My Unicomp has a right windows key and alt key in swapped positions, so I configured right windows key to act as a second Alt_R (well ISO_Level3_Shift), using gnome-tweaks, leading to: /org/gnome/desktop/input-sources/xkb-options ['caps:none', 'lv3:rwin_switch'] Opening the keyboard page in gnome settings resets this to /org/gnome/desktop/input-sources/xkb-options ['caps:none', 'lv3:ralt_alt', 'lv3:rwin_switch'] Effectively disabling the Alt Gr (right alt key) from acting as level 3 shift. Enabling right alt explicitly is not better. That sets /org/gnome/desktop/input-sources/xkb-options ['caps:none', 'lv3:ralt_switch', 'lv3:rwin_switch'] and opening the keyboard panel then just deletes the windows key switch: /org/gnome/desktop/input-sources/xkb-options ['caps:none', 'lv3:ralt_switch'] Not sure if it's a regression, but it's problematic anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1934761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d
This bug was fixed in the package gnome-shell - 40.2-1ubuntu6 --- gnome-shell (40.2-1ubuntu6) impish; urgency=medium * d/rules: - Drop dh_translations workaround. gettext used by LP has been updated (LP: #1756547). - Fix Lintian warning about DEB_HOST_ARCH assignment gnome-shell (40.2-1ubuntu5) impish; urgency=medium * Fix translation issues (LP: #1941954): - Really fix translation import problem as reported in LP: #1756547 - Add libgtk-3-bin to Build-Depends for dh_translations gnome-shell (40.2-1ubuntu4) impish; urgency=medium * debian/rules: - Skip tests when building for ppc64el to fix FTBFS (LP: #1941792) gnome-shell (40.2-1ubuntu3) impish; urgency=medium [ Daniel van Vugt ] * Add layout-Make-starting-in-the-overview-optional.patch: - So that extensions like Ubuntu Dock have the option of preventing the shell starting in the overview. (LP: #1940925) gnome-shell (40.2-1ubuntu2) impish; urgency=medium [ Daniel van Vugt ] * Add workspace-Remove-skip-taskbar-windows-while-the-over.patch to stop the desktop icons window appearing like an app window in the overview on startup (LP: #1936643) -- Gunnar Hjalmarsson Wed, 01 Sep 2021 15:44:38 +0200 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- 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/1756547 Title: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d Status in Launchpad itself: Fix Released Status in Ubuntu Translations: Fix Released Status in gettext package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: Some strings of GNOME Shell are untranslated in the Czech translation on Ubuntu 18.04 although they are translated upstream and when I try to manually translate them on launchpad, I get this error: "number of format specifications in 'msgid_plural' and 'msgstr[0]' does not match". The bad strings are: %d minute ago %d minutes ago %d hour ago %d hours ago %d week ago %d weeks ago %d month ago %d months ago %d year ago %d years ago They seem to be correct, but they are not accepted for some reason. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1756547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1912168] Re: Merge ppp 2.4.9
This bug was fixed in the package ppp - 2.4.9-1+1ubuntu1 --- ppp (2.4.9-1+1ubuntu1) impish; urgency=low [ Simon Chopin ] * Merge from Debian unstable (LP: #1912168). Remaining changes: - debian/extra/ip-up.d/usepeerdns: Added NetworkManager check, which lets the script exit when NetworkManager is in use * Dropped changes as obsolete - debian/patches/CVE-2020-8597.patch: fix bounds check in EAP code in pppd/eap.c. [ Iain Lane ] * Also drop this change: - Stop producing udebs on i386 where we no longer have d-i or a kernel. + Since hirsute these aren't built anyway, so we no longer need to exclude them on specific arches. ppp (2.4.9-1+1) unstable; urgency=medium [ Samuel Thibault ] * Use merge request URLs. * Add comments from upstream for Nacked patches. [ Chris Boot ] * New upstream release. - Adds defaultroute6 option. (Closes: #477245) - Adds defaultroute-metric option. (Closes: #578726) - Accepts Windows Server 2019 malformed messages. (Closes: #968040) - Fixes pppoe-discovery -U. (Closes: #961462) * Remove patches merged upstream (lots!) and refresh the rest. * d/ppp.symbols: update for the new version. * d/rules: adjust for renamed pppoe plugin. * d/ppp.lintian-overrides: update paths to plugins. * d/ppp.postinst: remove left-in debugging aid (set -x). (Closes: #978732) * Update d/watch to point at ftp.samba.org and add the signing key. * Freshen up the ip{,v6}-{up,down} scripts. (Closes: #710946) [ Michael Biebl ] * Stop using deprecated systemd-resolve tool. (Closes: #979255) [ наб ] * Add /etc/ppp/ip-pre-up and corresponding /etc/ppp/ip-pre-up.d. (Closes: #978396) ppp (2.4.8-1+2) unstable; urgency=medium * Clean up correctly after pppd-dns init script and systemd unit removal. (Closes: #978427) * Don't touch resolv.conf when systemd-resolved is running. (Closes: #968589) [ Samuel Thibault ] * Mark forwarded patches. ppp (2.4.8-1+1) unstable; urgency=medium [ Debian Janitor ] * Use secure URI in Homepage field. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Update renamed lintian tag names in lintian overrides. [ Chris Boot ] * d/control: - Switch to debhelper compat level 13. - Update Standards-Version to 4.5.1 (no changes requird). * Clean up or ignore a handful of lintian complaints: - Ignore possible-bashism-in-maintainer-script in ppp-udeb ($HOSTNAME is set in the script). - Do not use full path to pppoe-discovery. - Remove 'echo' bashism (backslash substitution). - Remove superfluous #DEBHELPER# tag. - Install lintian overrides for ppp-udeb. * d/rules: move generated changelog-from-README under debian/. * Add debian/.gitignore file covering most files generated during build. * Upload to unstable. ppp (2.4.8-1+1~exp1) experimental; urgency=medium * New upstream release. * d/patches: - Remove patches applied upstream. - Refresh other patches to remove fuzz. - Some patches required significant reworking: - cifdefroute.dif (for replacedefaultroute) - makefiles_cleanup * d/ppp.symbols: - adjust symbols for new release. - add Build-Depends-Package metadata field. * Switch to debhelper compat level 12. - Remove d/compat. - Replace Build-Depends on debhelper with debhelper-compat (= 12). * Remove d/upstream/signing-key.asc. Upstream no loner supplied signed tarballs. * Fix various lintian complaints: - d/rules: don't trigger ldconfig unnecessarily. - d/rules: remove obsolete get-orig-source target. - d/ppp.lintian-overrides: update version in plugins path. - d/ppp.lintian-overrides: add new override for minconn.so. * Remove pppd-dns init script and systemd unit, which have been broken since ppp 2.4.5-1. * Update pppoe-discovery(8) man page. * Enable systemd notify integration. * d/rules: don't set LDOPTS now that the makefiles use LDFLAGS correctly. * Add patch to handle IPv6 RADIUS attributes. (Closes: #874620) * d/ppp-udeb.postinst: - Source /etc/network/interfaces.d snippets in /etc/network/interfaces file generated by debian-installer udeb. (Closes: #889314) - Prevent NetworkManager from managing the interface being used for PPPoE. (Closes: #889323) - Thanks to Алексей Шилин for the patches. * Update Standards-Version to 4.5.0 (no changes requird). * Add debian/salsa-ci.yml for GitLab CI, but disable reprotest which currently fails when files need chowning (salsa-ci-team/pipeline#26). * Import patches since upstream 2.4.8 release: - radius: Prevent buffer overflow in rc_mksid (replaces rc_mksid-no-buffer-overflow fixing #782450) - pppd: Fix bounds check in EAP code (Closes: #950618; CVE-2020-8597) - pppd: Ignore received EAP messages when not doing EAP - Refresh eaptls-mppe.patch to remove fuzz. * Add
[Desktop-packages] [Bug 1941954] Re: Translation issues
This bug was fixed in the package gnome-shell - 40.2-1ubuntu6 --- gnome-shell (40.2-1ubuntu6) impish; urgency=medium * d/rules: - Drop dh_translations workaround. gettext used by LP has been updated (LP: #1756547). - Fix Lintian warning about DEB_HOST_ARCH assignment gnome-shell (40.2-1ubuntu5) impish; urgency=medium * Fix translation issues (LP: #1941954): - Really fix translation import problem as reported in LP: #1756547 - Add libgtk-3-bin to Build-Depends for dh_translations gnome-shell (40.2-1ubuntu4) impish; urgency=medium * debian/rules: - Skip tests when building for ppc64el to fix FTBFS (LP: #1941792) gnome-shell (40.2-1ubuntu3) impish; urgency=medium [ Daniel van Vugt ] * Add layout-Make-starting-in-the-overview-optional.patch: - So that extensions like Ubuntu Dock have the option of preventing the shell starting in the overview. (LP: #1940925) gnome-shell (40.2-1ubuntu2) impish; urgency=medium [ Daniel van Vugt ] * Add workspace-Remove-skip-taskbar-windows-while-the-over.patch to stop the desktop icons window appearing like an app window in the overview on startup (LP: #1936643) -- Gunnar Hjalmarsson Wed, 01 Sep 2021 15:44:38 +0200 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- 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/1941954 Title: Translation issues Status in gnome-shell package in Ubuntu: Fix Released Bug description: This commit: https://salsa.debian.org/gnome-team/gnome-shell/-/commit/86ace441 may have served its purpose for a couple of days. But then this happened: https://launchpad.net/ubuntu/+source/pkgbinarymangler/136 giving dh_translations the ability to create POT files when meson is in use. So what currently happens is: 1. The POT is created 2. The POT is modified with sed() 3. The POT is created again, overwriting the sed() modifications And we still have import problems as reported in bug #1756547. So the override in debian/rules needs to be changed to do things in the right order. Another thing: libgtk-3-bin should be added to Build-Depends to avoid warnings when running dh_translations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1941954/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1940556] Re: FFe: libreoffice 7.2.0 for impish
This bug was fixed in the package libreoffice - 1:7.2.0-0ubuntu1 --- libreoffice (1:7.2.0-0ubuntu1) impish; urgency=medium * New upstream release (LP: #1940556) * Revert GDrive API v3 support to allow build with libcmis 0.5.2 * Revert "Fix some warnings for Raspberry pi 4" changes to unbreak armhf -- Rico Tzschichholz Thu, 19 Aug 2021 17:16:19 +0200 ** Changed in: libreoffice (Ubuntu Impish) Status: Fix Committed => Fix Released -- 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/1940556 Title: FFe: libreoffice 7.2.0 for impish Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Impish: Fix Released Bug description: LibreOffice 7.2.0 is meant to be targeted for Impish/21.10. Unfortunately is was not ready in time due to a regression of the ARM builds. [Impact] * LibreOffice 7.2.0 is the initial release of the 7.2 line: https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.0_release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/amd64/libr/libreoffice/20210821_112901_fff50@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/arm64/libr/libreoffice/20210821_112241_aae0a@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/armhf/libr/libreoffice/20210821_123442_b37dd@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/ppc64el/libr/libreoffice/20210821_105712_5f0a0@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/s390x/libr/libreoffice/20210821_100240_a0e59@/log.gz * based on 7.2.0-0ubuntu0.21.10.1~lo2 - https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice- prereleases/+sourcepub/12658139/+listing-archive-extra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1940556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1940925] Re: [FFe] Do not activate spread view on first boot
This bug was fixed in the package gnome-shell - 40.2-1ubuntu6 --- gnome-shell (40.2-1ubuntu6) impish; urgency=medium * d/rules: - Drop dh_translations workaround. gettext used by LP has been updated (LP: #1756547). - Fix Lintian warning about DEB_HOST_ARCH assignment gnome-shell (40.2-1ubuntu5) impish; urgency=medium * Fix translation issues (LP: #1941954): - Really fix translation import problem as reported in LP: #1756547 - Add libgtk-3-bin to Build-Depends for dh_translations gnome-shell (40.2-1ubuntu4) impish; urgency=medium * debian/rules: - Skip tests when building for ppc64el to fix FTBFS (LP: #1941792) gnome-shell (40.2-1ubuntu3) impish; urgency=medium [ Daniel van Vugt ] * Add layout-Make-starting-in-the-overview-optional.patch: - So that extensions like Ubuntu Dock have the option of preventing the shell starting in the overview. (LP: #1940925) gnome-shell (40.2-1ubuntu2) impish; urgency=medium [ Daniel van Vugt ] * Add workspace-Remove-skip-taskbar-windows-while-the-over.patch to stop the desktop icons window appearing like an app window in the overview on startup (LP: #1936643) -- Gunnar Hjalmarsson Wed, 01 Sep 2021 15:44:38 +0200 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1940925 Title: [FFe] Do not activate spread view on first boot Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: On first boot the spread view shows the first boot wizard and it looks really weird. Moreover if you click on the right workspace the wizard is not displayed. The spread view should be disabled and the wizard should be displayed full screen immediately. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 24 12:41:16 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-31 (450 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1940925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1941792] Re: Fails to build for ppc64el
This bug was fixed in the package gnome-shell - 40.2-1ubuntu6 --- gnome-shell (40.2-1ubuntu6) impish; urgency=medium * d/rules: - Drop dh_translations workaround. gettext used by LP has been updated (LP: #1756547). - Fix Lintian warning about DEB_HOST_ARCH assignment gnome-shell (40.2-1ubuntu5) impish; urgency=medium * Fix translation issues (LP: #1941954): - Really fix translation import problem as reported in LP: #1756547 - Add libgtk-3-bin to Build-Depends for dh_translations gnome-shell (40.2-1ubuntu4) impish; urgency=medium * debian/rules: - Skip tests when building for ppc64el to fix FTBFS (LP: #1941792) gnome-shell (40.2-1ubuntu3) impish; urgency=medium [ Daniel van Vugt ] * Add layout-Make-starting-in-the-overview-optional.patch: - So that extensions like Ubuntu Dock have the option of preventing the shell starting in the overview. (LP: #1940925) gnome-shell (40.2-1ubuntu2) impish; urgency=medium [ Daniel van Vugt ] * Add workspace-Remove-skip-taskbar-windows-while-the-over.patch to stop the desktop icons window appearing like an app window in the overview on startup (LP: #1936643) -- Gunnar Hjalmarsson Wed, 01 Sep 2021 15:44:38 +0200 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- 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/1941792 Title: Fails to build for ppc64el Status in gnome-shell package in Ubuntu: Fix Released Bug description: This happens with both 40.2-1ubuntu2 and 40.2-1ubuntu3. Before uploading the latter I could successfully build for ppc64el in PPA, though. From the build log: 1/7 CSS styling support FAIL 0.23s (exit status 1) --- command --- 18:49:35 /<>/obj-powerpc64le-linux-gnu/src/st/test-theme --- stderr --- (test-theme:13115): dbind-WARNING **: 18:49:35.810: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files libEGL warning: DRI2: failed to create any config libEGL warning: DRI2: failed to create any config libEGL warning: DRI2: failed to create any config libEGL warning: DRI2: failed to create any config (test-theme:13115): Clutter-CRITICAL **: 18:49:35.868: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found. (test-theme:13115): mutter-WARNING **: 18:49:35.868: Failed to create backend: Unable to initialize Clutter https://launchpadlibrarian.net/555456872/buildlog_ubuntu-impish- ppc64el.gnome-shell_40.2-1ubuntu3_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1941792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1939640] Re: libvpx FTBFS with LTO enabled
This bug was fixed in the package libvpx - 1.9.0-1ubuntu1 --- libvpx (1.9.0-1ubuntu1) impish; urgency=medium * d/rules: Disable LTO and fix FTBFS when building with GCC 11. (LP: #1939640) -- Sergio Durigan Junior Wed, 11 Aug 2021 22:25:45 -0400 ** Changed in: libvpx (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvpx in Ubuntu. https://bugs.launchpad.net/bugs/1939640 Title: libvpx FTBFS with LTO enabled Status in libvpx package in Ubuntu: Fix Released Status in lto-disabled-list package in Ubuntu: Fix Released Bug description: libvpx FTBFS with LTO enabled on GCC 11, as can be seen here: https://people.canonical.com/~doko/ftbfs-report/test- rebuild-20210805-impish-impish.html#ubuntu-server https://launchpadlibrarian.net/552670245/buildlog_ubuntu-impish- amd64.libvpx_1.9.0-1_BUILDING.txt.gz g++ -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -m64 -o test_libvpx ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o test/decode_corrupted.cc.o test/decode_svc_test.cc.o test/decode_test_driver.cc.o test/encode_api_test.cc.o test/encode_test_driver.cc.o test/error_resilience_test.cc.o test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o test/invalid_file_test.cc.o test/keyframe_test.cc.o test/level_test.cc.o test/realtime_test.cc.o test/resize_test.cc.o test/svc_datarate_test.cc.o test/svc_end_to_end_test.cc.o test/svc_test.cc.o test/test_libvpx.cc.o test/test_vector_test.cc.o test/test_vectors.cc.o test/timestamp_test.cc.o test/user_priv_test.cc.o test/vp8_datarate_test.cc.o test/vp9_datarate_test.cc.o test/vp9_end_to_end_test.cc.o test/vp9_ethread_test.cc.o test/vp9_lossless_test.cc.o test/vp9_motion_vector_test.cc.o test/vp9_skip_loopfilter_test.cc.o test/y4m_test.cc.o third_party/libwebm/mkvparser/mkvparser.cc.o third_party/libwebm/mkvparser/mkvreader.cc.o webmdec.cc.o y4menc.c.o y4minput.c.o -L. -lvpx -lgtest -lpthread -lm -lpthread ln -sf libvpx.so.6.3.0 vpx-vp8-vp9-x86_64-linux-v1.9.0/lib/libvpx.so.6 /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x1586f): undefined reference to `gtest_all.cc.5c9bdf8f' /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158a5): undefined reference to `gtest_all.cc.5c9bdf8f' /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b2): undefined reference to `gtest_all.cc.5c9bdf8f' /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b7): undefined reference to `gtest_all.cc.5c9bdf8f' /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158dd): undefined reference to `gtest_all.cc.5c9bdf8f' /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x15903): more undefined references to `gtest_all.cc.5c9bdf8f' follow collect2: error: ld returned 1 exit status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1939640/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1936008] Re: Trackpad interfering with trackpoint even when disabled
The trackpoint issue is still unresolved as of today's Ubuntu 21.10 daily build. ** Tags added: impish -- 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/1936008 Title: Trackpad interfering with trackpoint even when disabled Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: I am running Ubuntu 20.04 on a new ThinkPad P14s AMD. I noticed that my trackpoint was very laggy and choppy. After a while I realized that the trackpoint is smooth as long as I am not touching the trackpad (very difficult). Even with the trackpad disabled in GNOME and the BIOS (which seems to only affect Windows) the interference continues. Using the command "libinput debug-events" I can see "POINTER_MOTION" events being registered despite the trackpad being off. This seems to be what is causing the trackpoint lag. Disabling the trackpad in the BIOS does not help. I have the same behaviour on a 21.04 live USB session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-libinput 0.29.0-1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 13 19:09:36 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu InstallationDate: Installed on 2021-07-08 (5 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1S00C00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET63W(1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1S00C00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR1BET63W(1.32):bd04/12/2021:br1.32:efr1.32:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1S00C00 dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107+git2107030500.9cef5d~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.2~git2107130600.9d225c~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx 21.2~git2107130600.9d225c~oibaf~f version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1936008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942653] Re: RandR fractional scaling patch interferes with manual RandR output scaling
The attachment "x11-Add-support-for-fractional-scaling-using- Randr.patch" 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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1942653 Title: RandR fractional scaling patch interferes with manual RandR output scaling Status in mutter package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 $ apt-cache policy mutter mutter: Installed: 3.36.9-0ubuntu0.20.04.1 Candidate: 3.36.9-0ubuntu0.20.04.1 Version table: *** 3.36.9-0ubuntu0.20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-3ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages --- As an example with one output, scaling it with e.g. 'xrandr --output --mode 3840x2160 --scale-from 1920x1080', would usually result in a screen size of 1920x1080, as xrandr sets the screen size to the bounding box of the configured crtcs. Ubuntu carries an out-of-tree patch for Mutter: x11-Add-support-for-fractional-scaling-using-Randr.patch, attached. It adds a new function, meta_monitor_manager_xrandr_update_screen_size_derived(), that in response to RandR configuration changes will attempt to set its own screen size. When calculating the new screen size, it applies a scaling factor to each crtc that effectively reverses the requested one. As a result, in the above example the resulting screen size is 3840x2160, despite the fact that there is only a 1920x1080 viewport into it. With the modesetting driver, this isn't a huge issue. The resulting screen size is larger than you can actually interact with, wasting memory, but it doesn't cause any visible functional issues. The NVIDIA driver automatically configures panning when the requested outputs' viewports are smaller than the screen size. This increases crtc size, which impacts Mutter's screen size calculation. When Mutter sets the larger-than-outputs screen size, it triggers the NVIDIA driver to automatically configure panning. Mutter reacts to the RandR configuration change by again recalculating the screen size, this time growing it even larger due to the larger crtcs. In response, the NVIDIA driver sets up the new, larger panning configuration, causing the crtcs to be even larger, and causing Mutter to once again recalculate the screen size. This goes on until all memory is consumed and gnome-shell is killed by the OOM killer, or the screen reaches maximum size. In the meantime, the screen is black with only a cursor while gnome-shell spins. It appears that meta_monitor_manager_xrandr_update_screen_size_derived() is intended for GNOME fractional scaling, adjusting the screen size to accommodate. In this case we are manually configuring output scaling with RandR, but this code still runs, causing unintended consequences. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1942653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942655] [NEW] problem after minimizing windows
Public bug reported: Hello, the problem that I am presented with is basic, but quite annoying. At any time without any type of pattern, when minimizing a window (of any program), these remain as "background", and become part of the wallpaper. You do not interact with it but it remains static on the site. I attach an example. The only temporary solution that has worked for me is to log out, but it almost certainly happens again. I appreciate the help :) (The theme has nothing to do with it, it happens to me even though it is stock) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 17:12:04 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-28 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-08-31 (3 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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/1942655 Title: problem after minimizing windows Status in gnome-shell package in Ubuntu: New Bug description: Hello, the problem that I am presented with is basic, but quite annoying. At any time without any type of pattern, when minimizing a window (of any program), these remain as "background", and become part of the wallpaper. You do not interact with it but it remains static on the site. I attach an example. The only temporary solution that has worked for me is to log out, but it almost certainly happens again. I appreciate the help :) (The theme has nothing to do with it, it happens to me even though it is stock) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 17:12:04 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-28 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-08-31 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1942655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942653] [NEW] RandR fractional scaling patch interferes with manual RandR output scaling
Public bug reported: $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 $ apt-cache policy mutter mutter: Installed: 3.36.9-0ubuntu0.20.04.1 Candidate: 3.36.9-0ubuntu0.20.04.1 Version table: *** 3.36.9-0ubuntu0.20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-3ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages --- As an example with one output, scaling it with e.g. 'xrandr --output --mode 3840x2160 --scale-from 1920x1080', would usually result in a screen size of 1920x1080, as xrandr sets the screen size to the bounding box of the configured crtcs. Ubuntu carries an out-of-tree patch for Mutter: x11-Add-support-for-fractional-scaling-using-Randr.patch, attached. It adds a new function, meta_monitor_manager_xrandr_update_screen_size_derived(), that in response to RandR configuration changes will attempt to set its own screen size. When calculating the new screen size, it applies a scaling factor to each crtc that effectively reverses the requested one. As a result, in the above example the resulting screen size is 3840x2160, despite the fact that there is only a 1920x1080 viewport into it. With the modesetting driver, this isn't a huge issue. The resulting screen size is larger than you can actually interact with, wasting memory, but it doesn't cause any visible functional issues. The NVIDIA driver automatically configures panning when the requested outputs' viewports are smaller than the screen size. This increases crtc size, which impacts Mutter's screen size calculation. When Mutter sets the larger-than-outputs screen size, it triggers the NVIDIA driver to automatically configure panning. Mutter reacts to the RandR configuration change by again recalculating the screen size, this time growing it even larger due to the larger crtcs. In response, the NVIDIA driver sets up the new, larger panning configuration, causing the crtcs to be even larger, and causing Mutter to once again recalculate the screen size. This goes on until all memory is consumed and gnome-shell is killed by the OOM killer, or the screen reaches maximum size. In the meantime, the screen is black with only a cursor while gnome-shell spins. It appears that meta_monitor_manager_xrandr_update_screen_size_derived() is intended for GNOME fractional scaling, adjusting the screen size to accommodate. In this case we are manually configuring output scaling with RandR, but this code still runs, causing unintended consequences. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Patch added: "x11-Add-support-for-fractional-scaling-using-Randr.patch" https://bugs.launchpad.net/bugs/1942653/+attachment/5522890/+files/x11-Add-support-for-fractional-scaling-using-Randr.patch -- 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/1942653 Title: RandR fractional scaling patch interferes with manual RandR output scaling Status in mutter package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 $ apt-cache policy mutter mutter: Installed: 3.36.9-0ubuntu0.20.04.1 Candidate: 3.36.9-0ubuntu0.20.04.1 Version table: *** 3.36.9-0ubuntu0.20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-3ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages --- As an example with one output, scaling it with e.g. 'xrandr --output --mode 3840x2160 --scale-from 1920x1080', would usually result in a screen size of 1920x1080, as xrandr sets the screen size to the bounding box of the configured crtcs. Ubuntu carries an out-of-tree patch for Mutter: x11-Add-support-for-fractional-scaling-using-Randr.patch, attached. It adds a new function, meta_monitor_manager_xrandr_update_screen_size_derived(), that in response to RandR configuration changes will attempt to set its own screen size. When calculating the new screen size, it applies a scaling factor to each crtc that effectively reverses the requested one. As a result, in the above example the resulting screen size is 3840x2160, despite the fact that there is only a 1920x1080 viewport into it. With the modesetting driver, this isn't a huge issue. The resulting screen size is larger than you can actually interact with, wasting memory, but it doesn't cause any visible functional issues. The NVIDIA driver automatically configures panning when the requested outputs' viewports are smaller than the screen size. This increases crtc size, which impacts Mutter's screen size calculation. When Mutter sets the larger-than-outputs screen size, it triggers the NVIDIA driver to automatically
[Desktop-packages] [Bug 1942542] Re: gedit causes loss of extended attributes (xattrs)
Nice find Alex; can you please report this to upstream gedit, and report back the bug url here so we can link them together? Thanks ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1942542 Title: gedit causes loss of extended attributes (xattrs) Status in gedit package in Ubuntu: New Bug description: Ubuntu 21.04 hirsute gedit 3.38.1-1 If a file with extended attributes (xattrs) is edited and saved with gedit, the xattrs are lost. This problem - as well as the loss of birth time, reported in https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1940758 - seems to be caused by gedit creating a new file when saving. Compare this with nano, which does not destroy xattrs. Steps to reproduce: 1 echo testing > testfile.txt 2 setfattr -n user.test -v "this is my test xattr" testfile.txt 3 getfattr -d testfile.txt # file: testfile.txt user.test="this is my test xattr" 4 gedit testfile.txt make edit and save 5 getfattr -d testfile.txt no output This bug also causes a loss of ACLs for the edited file, as they are stored as extended attributes. Because of this I am marking this bug as a security vulnerability. This bug is not limited to gedit; it applies to a number of other text editors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1942542/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
>From the investigation I performed earlier this week, this issue appears to go back at least 10 years. The original report against Ubuntu 16 has a video that demonstrates the problem clearly. It should suffice as steps to reproduce. On Thu, Sep 2, 2021 at 8:11 PM Daniel van Vugt <1532...@bugs.launchpad.net> wrote: > I don't think we need new bug reports about this. I've just fixed the > concern about "unrelated packages" by removing the irrelevant tasks at > the top of the page. Only the gnome-shell task remains open. > > What we really need here is clear instructions for how to reproduce the > bug in GNOME using a recent Ubuntu release. > > ** No longer affects: gdm3 (Ubuntu) > > ** Project changed: ubuntu-gnome => mir > > ** No longer affects: mir > > ** Tags added: hirsute > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1935690). > https://bugs.launchpad.net/bugs/1532508 > > Title: > Screen contents revealed briefly on resume, before even unlocking > > Status in GNOME Shell: > Unknown > Status in gnome-shell package in Ubuntu: > Confirmed > Status in unity package in Ubuntu: > Fix Released > Status in unity source package in Xenial: > Fix Released > Status in gnome-shell package in Debian: > Confirmed > > Bug description: > [Impact] > > When lock is enabled, the screen doesn't get blank/covered by > lockscreen before suspending, thus on early resume the content might > be shown. > > Video showing the bug: https://youtu.be/dDOgtK1MldI > > Reproduced on Ubuntu 2015.10, Ubuntu 2014.04 > > [Test case] > > 1. Work on highly secret files > 2. Close the lid of your laptop and go have a break > 3. Anyone who opens the lid of the laptop can see the secret files for a > half second before the lock screen appears > > [Possible Regression] > > Content on screen isn't painted anymore and screen stays black. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions > > -- This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic mail or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify me immediately by reply e-mail so that I may correct my records, then please delete the original message (including any attachments) in its entirety. Thank you. -- 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/1532508 Title: Screen contents revealed briefly on resume, before even unlocking Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity source package in Xenial: Fix Released Status in gnome-shell package in Debian: Confirmed Bug description: [Impact] When lock is enabled, the screen doesn't get blank/covered by lockscreen before suspending, thus on early resume the content might be shown. Video showing the bug: https://youtu.be/dDOgtK1MldI Reproduced on Ubuntu 2015.10, Ubuntu 2014.04 [Test case] 1. Work on highly secret files 2. Close the lid of your laptop and go have a break 3. Anyone who opens the lid of the laptop can see the secret files for a half second before the lock screen appears [Possible Regression] Content on screen isn't painted anymore and screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942622] Re: Gnome control center displays tab crashes if you unplug all monitors
** Description changed: 1. Open gnome control center. 2. Open the "Displays" tab 3. Unplug ALL monitors 4. Plug a monitor back in. 5. Gnome Control center has crashed + + ps. + Also tested this on Ubuntu 21.04 using a live USB stick and interestingly Gnome control center does not crash but freezes instead and has to be force quit. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 19:25:36 2021 InstallationDate: Installed on 2021-08-26 (7 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1942622 Title: Gnome control center displays tab crashes if you unplug all monitors Status in gnome-control-center package in Ubuntu: New Bug description: 1. Open gnome control center. 2. Open the "Displays" tab 3. Unplug ALL monitors 4. Plug a monitor back in. 5. Gnome Control center has crashed ps. Also tested this on Ubuntu 21.04 using a live USB stick and interestingly Gnome control center does not crash but freezes instead and has to be force quit. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 19:25:36 2021 InstallationDate: Installed on 2021-08-26 (7 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1942622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942622] [NEW] Gnome control center displays tab crashes if you unplug all monitors
Public bug reported: 1. Open gnome control center. 2. Open the "Displays" tab 3. Unplug ALL monitors 4. Plug a monitor back in. 5. Gnome Control center has crashed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 19:25:36 2021 InstallationDate: Installed on 2021-08-26 (7 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1942622 Title: Gnome control center displays tab crashes if you unplug all monitors Status in gnome-control-center package in Ubuntu: New Bug description: 1. Open gnome control center. 2. Open the "Displays" tab 3. Unplug ALL monitors 4. Plug a monitor back in. 5. Gnome Control center has crashed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 19:25:36 2021 InstallationDate: Installed on 2021-08-26 (7 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1942622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1940543] Re: Show Hidden Files does not persist and even resets during the same session
Thanks for clearing that up Paul. I will provide whatever data I can once someone can check on this ticket. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1940543 Title: Show Hidden Files does not persist and even resets during the same session Status in nautilus package in Ubuntu: New Bug description: Since 20.04 has been released, the option "Show Hidden Files" has never lasted long. It never persists over a reboot and even during the same session, it will just hide the files after some random (it seems random) interval. This happens for me on 3 different computers, all different builds. This happens on a vanilla install too. I have never been able to make "Show Hidden Files" last longer than an hourish, and never over a reboot. I work a lot in hidden files, this is mostly just frustrating to me since it happens randomly and when I am moving around a project, I have to keep toggling "Show Hidden Files" to get work done. I did have to reinstall `gnome-control-center` after a fresh install and updating Ubuntu 20.04 the latest version, I am not sure if that could help identify the issue but I have always had this issue on 20.04 so I am doubtful. I did this running: ``` sudo apt install --reinstall gnome-control-center ``` I had to reinstall this since Settings was no longer available after the system was updated (fresh install with `sudo apt update && sudo apt upgrade` is what broken it for me to have to reinstall it. I even tried using: ``` gsettings set org.gtk.Settings.FileChooser show-hidden true ``` but the issue still happens. Also, not sure why nautilus is installed, I thought 20.04 was gnome? Again, this is a fresh install (15 days old) ``` $ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 ``` ``` $ apt-cache policy nautilus nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ``` ``` apt-cache policy gnome gnome: Installed: (none) Candidate: 1:3.30+2 Version table: 1:3.30+2 500 500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 19 09:46:31 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1280, 1393)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-08-03 (15 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1940543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942616] Re: Settings Power says high hardware temperature
** Package changed: gnome-control-center (Ubuntu) => power-profiles- daemon (Ubuntu) ** Changed in: power-profiles-daemon (Ubuntu) Importance: Undecided => Low -- 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/1942616 Title: Settings Power says high hardware temperature Status in power-profiles-daemon package in Ubuntu: New Bug description: Settings Power says 'high hardware temperature: performance mode unavailable' while temperature is normal. corrado@corrado-x5-ii-0901:~$ sensors coretemp-isa- Adapter: ISA adapter Package id 0: +35.0°C (high = +80.0°C, crit = +100.0°C) Core 0:+35.0°C (high = +80.0°C, crit = +100.0°C) Core 1:+34.0°C (high = +80.0°C, crit = +100.0°C) nvme-pci-0200 Adapter: PCI adapter Composite:+31.9°C (low = -0.1°C, high = +74.8°C) (crit = +79.8°C) pch_skylake-virtual-0 Adapter: Virtual device temp1:+49.5°C See also attached screenshot ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 16:36:11 2021 InstallationDate: Installed on 2021-09-01 (2 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210901) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/1942616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942616] [NEW] Settings Power says high hardware temperature
Public bug reported: Settings Power says 'high hardware temperature: performance mode unavailable' while temperature is normal. corrado@corrado-x5-ii-0901:~$ sensors coretemp-isa- Adapter: ISA adapter Package id 0: +35.0°C (high = +80.0°C, crit = +100.0°C) Core 0:+35.0°C (high = +80.0°C, crit = +100.0°C) Core 1:+34.0°C (high = +80.0°C, crit = +100.0°C) nvme-pci-0200 Adapter: PCI adapter Composite:+31.9°C (low = -0.1°C, high = +74.8°C) (crit = +79.8°C) pch_skylake-virtual-0 Adapter: Virtual device temp1:+49.5°C See also attached screenshot ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 16:36:11 2021 InstallationDate: Installed on 2021-09-01 (2 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210901) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session ** Attachment added: "Screenshot from 2021-09-03 16-32-22.png" https://bugs.launchpad.net/bugs/1942616/+attachment/5522802/+files/Screenshot%20from%202021-09-03%2016-32-22.png -- 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/1942616 Title: Settings Power says high hardware temperature Status in gnome-control-center package in Ubuntu: New Bug description: Settings Power says 'high hardware temperature: performance mode unavailable' while temperature is normal. corrado@corrado-x5-ii-0901:~$ sensors coretemp-isa- Adapter: ISA adapter Package id 0: +35.0°C (high = +80.0°C, crit = +100.0°C) Core 0:+35.0°C (high = +80.0°C, crit = +100.0°C) Core 1:+34.0°C (high = +80.0°C, crit = +100.0°C) nvme-pci-0200 Adapter: PCI adapter Composite:+31.9°C (low = -0.1°C, high = +74.8°C) (crit = +79.8°C) pch_skylake-virtual-0 Adapter: Virtual device temp1:+49.5°C See also attached screenshot ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 16:36:11 2021 InstallationDate: Installed on 2021-09-01 (2 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210901) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1942616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d
Launchpad intentionally imports even obsolete messages, although they're tagged internally as obsolete and filtered out for various purposes. I think this is so that they can be used as suggestions in some cases (for example, a similar message might still be used in another context). For that sort of purpose it can still be useful to know that the messages don't parse correctly, because they couldn't be used directly as suggestions without fixing the mistakes. This is likely part of some work that was never completed, e.g. https://bugs.launchpad.net/launchpad/+bug/281165 and https://blueprints.launchpad.net/launchpad/+spec/rosetta-fuzzy-merge. (Note that I'm reverse-engineering this from the code and from my general understanding of translations, rather than with direct information from the people who wrote the code.) I can see that it might be useful to at least exclude errors about obsolete messages like this from translation import failure emails. If you agree, could you file a separate bug about that? ** Changed in: ubuntu-translations Status: Triaged => Fix Released ** Changed in: gettext (Ubuntu) Status: Confirmed => Fix Released -- 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/1756547 Title: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d Status in Launchpad itself: Fix Released Status in Ubuntu Translations: Fix Released Status in gettext package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Bug description: Some strings of GNOME Shell are untranslated in the Czech translation on Ubuntu 18.04 although they are translated upstream and when I try to manually translate them on launchpad, I get this error: "number of format specifications in 'msgid_plural' and 'msgstr[0]' does not match". The bad strings are: %d minute ago %d minutes ago %d hour ago %d hours ago %d week ago %d weeks ago %d month ago %d months ago %d year ago %d years ago They seem to be correct, but they are not accepted for some reason. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1756547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942432] Re: third-party applications freeze gnome-shell reproducibly
Thank you for the quick response. I'm sorry for the work I generated. After reporting the bug, I tried another display / window manager, respectively, and managed my system into a non-working GUI. I then did a backup and reinstalled Linux, now cinnamon is working well. So you can close the bug in my view. -- 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/1942432 Title: third-party applications freeze gnome-shell reproducibly Status in gnome-shell package in Ubuntu: Incomplete Bug description: On my Ubuntu 20.04.3 LTS, I have reproducible freezes of gdm3 (3.36.3-0ubuntu0.20.04.4) caused by third-party applications. The only thing I found describing my problem was https://unix.stackexchange.com/a/39855 (passage *GUI Glitches Causing Unresponsive WM or X11/Wayland*). This is exactly my experience ("**an application stops responding and prevents you from entering input with the keyboard or mouse to other application windows**"). Specifically: - clicking on a hyperlink in (an open mail in) thunderbird freezes gdm3 at 90%. - opening files via nemo (file manager) freezes gdm3 sometimes, regardless which file type. - libreoffice freezes gdm3 a lot when switching windows via alt-tab, but not when I switch windows via super key. Whenever a freeze occurs, the clock in my taskbar stops, the mouse and keyboard still work, but no window responds. Switching to tty works. Killing the last used application (e.g. thunderbird, nemo, soffice.bin) via tty brings gdm3 to life again. The funny thing is that when e.g. I open a link via thunderbird and gdm3 freezes, then I kill thunderbird via tty and switch back to X, then thunderbird is gone but firefox has opened the link. I activated gdm3 debug output but could not find anything (I'm not an ubuntu/X/gdm expert). One freeze occurs somewhere between two **systemd-logind: got pause for 13:73** in syslog_gdm3.log ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.36.3-0ubuntu0.20.04.4 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 2 12:23:57 2021 InstallationDate: Installed on 2018-07-26 (1134 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANGUAGE=de_CH:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_CH.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-10-07 (329 days ago) mtime.conffile..etc.gdm3.custom.conf: 2021-09-02T11:47:52.516792 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1942432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942599] [NEW] KDE Volume not matching alsa volume in ALC294 (Asus Zenbook UM431D)
Public bug reported: Hello. I posted some weeks ago in pulseaudio bugtracker https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1249 about an issue, but i was thinking it should be better have here the issue too because maybe is related with other components in (K)Ubuntu system. I will go to a copy paste, because it self explanatory: --- * Context: OS: KUbuntu 21.04 with kernel 5.14.0rc4 mainline. Laptop: Asus Zenbook UMD431D with ALC294 pa-info: pa-info.txt (attached) Also recently was fixed an issue with alsa about the 4 speakers volume (two of them weren't affected by it https://bugzilla.kernel.org/show_bug.cgi?id=212547) however, this doesn't seems related to that. (That's why i use 5.14.0rc4, because 5.14 are the first with the patch). * Issue behaviour and description The main issue can be seen in the next video: https://www.youtube.com/watch?v=eBrHi1f9bck Summarizing, when you go up and down the KDE volume, if you compared the desired volume in the slider with alsamixer doesn't match. But the issue is when you reach below 9%, with that the Master volume in alsamixer is 0%, so there isn't any sound, and between 1%~8% it's changing the "Speaker" slider, doing nothing. It's like the "Speaker" slider is stacked below the "Master", but that doesn't make any sense in practice. Changing the volume in the KDE volume slider is not "linear", between 50%~100% it's more or less and the volume "feels" right, but below that, the volume goes down way faster. For example, having the volume at 25%, the sound is almost noticiable unless you put you ears near the speakers, something like this should be at 10%, but at the real 10% you have a barely noticiable sound in the speakers when you have your ears directly in them. * Expected Results The general volume slider should match the Master Volume in alsa, and only change that slider. Thanks! --- Offtopic: Also i found doing testing for the kernel bug noted above, that changing to some alsa model in this laptop, then appears in the volume/audio configurator a selection of output and input what can overrides the headphone plug status, and i see it very useful, especially because if i plug a headphone without microphone i can't use the laptop built-in microphone and the only thing i can do is not use headphone. But using some models (dell-headset-multi, for example) i can do that, however, it brings the issue with the volume in the back speakers. How pulseaudio can be do this? it can be done for my laptop? ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Attachment added: "pa-info" https://bugs.launchpad.net/bugs/1942599/+attachment/5522765/+files/pa-info.txt ** Description changed: Hello. I posted some weeks ago in pulseaudio bugtracker https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1249 about an issue, but i was thinking it should be better have here the issue too because maybe is related with other components in (K)Ubuntu system. I will go to a copy paste, because it self explanatory: --- * Context: OS: KUbuntu 21.04 with kernel 5.14.0rc4 mainline. Laptop: Asus Zenbook UMD431D with ALC294 pa-info: pa-info.txt (attached) - Also recently was fixed an issue with alsa about the 4 speakers volume (two of them weren't affected by it https://bugzilla.kernel.org/show_bug.cgi?id=212547) however, this doesn't seems related to that. (That's why i use 5.14.0rc4, because 5.14 are the first with the patch). + + Also recently was fixed an issue with alsa about the 4 speakers volume + (two of them weren't affected by it + https://bugzilla.kernel.org/show_bug.cgi?id=212547) however, this + doesn't seems related to that. (That's why i use 5.14.0rc4, because 5.14 + are the first with the patch). * Issue behaviour and description - The main issue can be seen in the next video: https://www.youtube.com/watch?v=eBrHi1f9bck - Summarizing, when you go up and down the KDE volume, if you compared the desired volume in the slider with alsamixer doesn't match. But the issue is when you reach below 9%, with that the Master volume in alsamixer is 0%, so there isn't any sound, and between 1%~8% it's changing the "Speaker" slider, doing nothing. It's like the "Speaker" slider is stacked below the "Master", but that doesn't make any sense in practice. - Changing the volume in the KDE volume slider is not "linear", between 50%~100% it's more or less and the volume "feels" right, but below that, the volume goes down way faster. For example, having the volume at 25%, the sound is almost noticiable unless you put you ears near the speakers, something like this should be at 10%, but at the real 10% you have a barely noticiable sound in the speakers when you have your ears directly in them. + The main issue can be seen in the next video: + https://www.youtube.com/watch?v=eBrHi1f9bck + + Summarizing, when you go up and down the KDE volume, if you compared
[Desktop-packages] [Bug 1942597] [NEW] I only have 640x480 resolution and cant use gdm3
Public bug reported: I believe there is something wrong with my graphic driver ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-7633.35~1630100930~20.04~ae2753e~dev-generic 5.11.22 Uname: Linux 5.11.0-7633-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Sep 3 14:47:31 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G96C [GeForce 9500 GT] [10de:0640] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd G96C [GeForce 9500 GT] [1458:34a9] InstallationDate: Installed on 2021-09-01 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-7633-generic root=UUID=428abc01-2e2d-4a8f-bfae-e5c776022a84 ro nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2009 dmi.bios.release: 8.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0403 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5KPL/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0403:bd06/17/2009:br8.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuToBeFilledByO.E.M.:rvnASUSTeKComputerINC.:rnP5KPL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.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 xserver.bootTime: Fri Sep 3 14:25:47 2021 xserver.configfile: default xserver.errors: [drm] Failed to open DRM device for pci::01:00.0: -19 open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.11-1ubuntu1~20.04.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1942597 Title: I only have 640x480 resolution and cant use gdm3 Status in xorg package in Ubuntu: New Bug description: I believe there is something wrong with my graphic driver ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-7633.35~1630100930~20.04~ae2753e~dev-generic 5.11.22 Uname: Linux 5.11.0-7633-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Sep 3 14:47:31 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G96C [GeForce 9500 GT] [10de:0640] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd G96C [GeForce 9500 GT] [1458:34a9] InstallationDate: Installed on 2021-09-01 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-7633-generic root=UUID=428abc01-2e2d-4a8f-bfae-e5c776022a84 ro nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2009 dmi.bios.release: 8.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0403 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5KPL/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias:
[Desktop-packages] [Bug 1942592] Re: Settings crashes on Displays setting
Probably bug 1874931 or bug 1874197 -- 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/1942592 Title: Settings crashes on Displays setting Status in gnome-control-center package in Ubuntu: Invalid Bug description: Do the following steps and the app will crash: 1. On "Displays" tab, enable "Fractional Scaling". 2. Select any "fractional scale" (125%, 150%, 175%). No need for "Apply". 3. Turn off "Fractional Scaling". The app will crash (exit). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 15:51:07 2021 InstallationDate: Installed on 2021-06-18 (76 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1942592/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942592] Re: Settings crashes on Displays setting
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- 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/1942592 Title: Settings crashes on Displays setting Status in gnome-control-center package in Ubuntu: Invalid Bug description: Do the following steps and the app will crash: 1. On "Displays" tab, enable "Fractional Scaling". 2. Select any "fractional scale" (125%, 150%, 175%). No need for "Apply". 3. Turn off "Fractional Scaling". The app will crash (exit). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 15:51:07 2021 InstallationDate: Installed on 2021-06-18 (76 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1942592/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930937] Re: SRU: Default dependency resolution in Focal pulls in full GNOME Desktop
** Tags removed: verification-needed verification-needed-focal verification-needed-groovy verification-needed-hirsute ** Tags added: verification-failed verification-failed-focal verification-failed-groovy verification-failed-hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/1930937 Title: SRU: Default dependency resolution in Focal pulls in full GNOME Desktop Status in screen-resolution-extra package in Ubuntu: Triaged Status in screen-resolution-extra source package in Focal: Fix Committed Status in screen-resolution-extra source package in Groovy: Fix Committed Status in screen-resolution-extra source package in Hirsute: Fix Committed Bug description: In Bionic, screen-resolution-extra has a dependency on policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a dependency on gnome-shell | policykit-1-gnome | polkit-1-auth-agent. As a result, when install screen-resolution-extra (e.g. as a dependency of nvidia-settings) on a system that doesn't already have GNOME or another polkit auth agent installed, the default dependency resolution pulls in a full GNOME desktop in Focal, while it does not do so under the same circumstances in Bionic. This can be worked around by explicitly installing policykit-1-gnome (or another package which provides the polkit-1-auth-agent virtual package), but it would be nice to not pull in GNOME by default on a system that doesn't already have it. [Impact] * Installing the nvidia-settings package causes gnome-shell to be installed. This is less than ideal on servers. [Fix] * Moving policykit-1-gnome ahead as the first of the polkit dependencies will solve the problem. [Test Case] * Install screen-resolution-extra from proposed on a system where no polkit-1-auth-agent provider is installed, and check that gnome-shell is not installed as a dependency. [Regression Risk] Low, as the change will still allow the dependency to be satisfied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942561] Re: ubuntu-mate impish install; graphics on one display warped on display.position adjustment
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1942561 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1942561 Title: ubuntu-mate impish install; graphics on one display warped on display.position adjustment Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Ubuntu MATE impish QA-test install to - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) NOTE: this or like issue is experienced with Ubuntu (GNOME) & Kubuntu (KDE) so it's not surprising. It does not occur on Xubuntu & Lubuntu though. Daniel (vanvugt) has suggested this box should only be used for 20.04; bugs in nouveau are difficult for Ubuntu to track down.. but this box is what I have for QA-installs. Related (possibly duplicates) - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930945 (Ubuntu GNOME desktop) - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919266 (Kubuntu KDE desktop) Install worked flawlessly except the adjust.screens.to.match.my.setup which I consider part of system shakedown.. ** Expected results I expect on adjust screens, I can read both screens ** Actual results My top.display remained readable; lower display had become a somewhat garbled mess (refer pics) Of NOTE: I can click the 'hide all windows & show desktop' and screen muck up was gone in an instant; hit it again & windows were returned & usable. MINOR ISSUE as relates to specific OLD nvidia graphics card(s?) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xserver-xorg-video-nouveau 1:1.0.17-1 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Fri Sep 3 17:57:23 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492] InstallationDate: Installed on 2021-09-03 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Alpha amd64 (20210903) MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-14-generic root=UUID=27bd4e3d-7a58-434f-b833-a1d616e66b9e ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.release: 1.5 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:br1.5:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:skuET090AV:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.product.sku: ET090AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.4-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1942561/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942592] [NEW] Settings crashes on Displays setting
Public bug reported: Do the following steps and the app will crash: 1. On "Displays" tab, enable "Fractional Scaling". 2. Select any "fractional scale" (125%, 150%, 175%). No need for "Apply". 3. Turn off "Fractional Scaling". The app will crash (exit). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 15:51:07 2021 InstallationDate: Installed on 2021-06-18 (76 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1942592 Title: Settings crashes on Displays setting Status in gnome-control-center package in Ubuntu: New Bug description: Do the following steps and the app will crash: 1. On "Displays" tab, enable "Fractional Scaling". 2. Select any "fractional scale" (125%, 150%, 175%). No need for "Apply". 3. Turn off "Fractional Scaling". The app will crash (exit). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 15:51:07 2021 InstallationDate: Installed on 2021-06-18 (76 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1942592/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942561] Re: ubuntu-mate impish install; graphics on one display warped on display.position adjustment
** Description changed: - ** quick notes - - I'll add more soon; link other report(s; 1 kubuntu, 1 ubuntu) & maybe - mark duplicate + Ubuntu MATE impish QA-test install to + - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) NOTE: this or like issue is experienced with Ubuntu (GNOME) & Kubuntu (KDE) so it's not surprising. It does not occur on Xubuntu & Lubuntu though. Daniel (vanvugt) has suggested this box should only be used for 20.04; bugs in nouveau are difficult for Ubuntu to track down.. but this box is what I have for QA-installs. - Install worked flawlessly except the adjust.screens.to.match.my.setup - which I consider part of system shakedown.. + Related (possibly duplicates) + - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930945 (Ubuntu GNOME desktop) + - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919266 (Kubuntu KDE desktop) - Of NOTE: I can click the 'hide all windows & show desktop' and screen - muck up was gone in an instant; hit it again & windows were returned & - usable. + + Install worked flawlessly except the adjust.screens.to.match.my.setup which I consider part of system shakedown.. + + ** Expected results + + I expect on adjust screens, I can read both screens + + ** Actual results + + My top.display remained readable; lower display had become a somewhat + garbled mess (refer pics) + + + Of NOTE: I can click the 'hide all windows & show desktop' and screen muck up was gone in an instant; hit it again & windows were returned & usable. + + + MINOR ISSUE as relates to specific OLD nvidia graphics card(s?) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xserver-xorg-video-nouveau 1:1.0.17-1 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Fri Sep 3 17:57:23 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492] + NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492] InstallationDate: Installed on 2021-09-03 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Alpha amd64 (20210903) MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-14-generic root=UUID=27bd4e3d-7a58-434f-b833-a1d616e66b9e ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.release: 1.5 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:br1.5:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:skuET090AV:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.product.sku: ET090AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.4-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1942561 Title: ubuntu-mate impish install; graphics on one display warped on display.position adjustment Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Ubuntu MATE impish QA-test install to - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) NOTE: this or like issue is experienced with Ubuntu (GNOME) & Kubuntu (KDE) so it's not surprising. It does not occur on Xubuntu & Lubuntu though. Daniel (vanvugt) has suggested this box should only be used for 20.04; bugs in nouveau are difficult for Ubuntu to track down.. but this box is what I have for QA-installs. Related (possibly duplicates)
[Desktop-packages] [Bug 1942561] Re: ubuntu-mate impish install; graphics on one display warped on display.position adjustment
** Attachment added: "another pic; slightly different window positions" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1942561/+attachment/5522709/+files/Screenshot%20at%202021-09-03%2017-55-19.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1942561 Title: ubuntu-mate impish install; graphics on one display warped on display.position adjustment Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: ** quick notes I'll add more soon; link other report(s; 1 kubuntu, 1 ubuntu) & maybe mark duplicate NOTE: this or like issue is experienced with Ubuntu (GNOME) & Kubuntu (KDE) so it's not surprising. It does not occur on Xubuntu & Lubuntu though. Daniel (vanvugt) has suggested this box should only be used for 20.04; bugs in nouveau are difficult for Ubuntu to track down.. but this box is what I have for QA-installs. Install worked flawlessly except the adjust.screens.to.match.my.setup which I consider part of system shakedown.. Of NOTE: I can click the 'hide all windows & show desktop' and screen muck up was gone in an instant; hit it again & windows were returned & usable. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xserver-xorg-video-nouveau 1:1.0.17-1 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Fri Sep 3 17:57:23 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492] InstallationDate: Installed on 2021-09-03 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Alpha amd64 (20210903) MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-14-generic root=UUID=27bd4e3d-7a58-434f-b833-a1d616e66b9e ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.release: 1.5 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:br1.5:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:skuET090AV:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.product.sku: ET090AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.4-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1942561/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942561] [NEW] ubuntu-mate impish install; graphics on one display warped on display.position adjustment
Public bug reported: ** quick notes I'll add more soon; link other report(s; 1 kubuntu, 1 ubuntu) & maybe mark duplicate NOTE: this or like issue is experienced with Ubuntu (GNOME) & Kubuntu (KDE) so it's not surprising. It does not occur on Xubuntu & Lubuntu though. Daniel (vanvugt) has suggested this box should only be used for 20.04; bugs in nouveau are difficult for Ubuntu to track down.. but this box is what I have for QA-installs. Install worked flawlessly except the adjust.screens.to.match.my.setup which I consider part of system shakedown.. Of NOTE: I can click the 'hide all windows & show desktop' and screen muck up was gone in an instant; hit it again & windows were returned & usable. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xserver-xorg-video-nouveau 1:1.0.17-1 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Fri Sep 3 17:57:23 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492] InstallationDate: Installed on 2021-09-03 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Alpha amd64 (20210903) MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-14-generic root=UUID=27bd4e3d-7a58-434f-b833-a1d616e66b9e ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.release: 1.5 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:br1.5:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:skuET090AV:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.product.sku: ET090AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.4-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish regression reproducible ubuntu ** Attachment added: "Screen Capture - top screen is usable; bottom not so much" https://bugs.launchpad.net/bugs/1942561/+attachment/5522687/+files/Screenshot%20at%202021-09-03%2017-54-33.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1942561 Title: ubuntu-mate impish install; graphics on one display warped on display.position adjustment Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: ** quick notes I'll add more soon; link other report(s; 1 kubuntu, 1 ubuntu) & maybe mark duplicate NOTE: this or like issue is experienced with Ubuntu (GNOME) & Kubuntu (KDE) so it's not surprising. It does not occur on Xubuntu & Lubuntu though. Daniel (vanvugt) has suggested this box should only be used for 20.04; bugs in nouveau are difficult for Ubuntu to track down.. but this box is what I have for QA-installs. Install worked flawlessly except the adjust.screens.to.match.my.setup which I consider part of system shakedown.. Of NOTE: I can click the 'hide all windows & show desktop' and screen muck up was gone in an instant; hit it again & windows were returned & usable. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xserver-xorg-video-nouveau 1:1.0.17-1 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Fri Sep 3 17:57:23 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: