[Desktop-packages] [Bug 1922340] Re: GNOME lock screen wallpaper turns black on main display
Hi, this bug does still affect Ubuntu 21.10: ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 26 08:46:23 2022 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2021-09-26 (121 days ago) -- 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/1922340 Title: GNOME lock screen wallpaper turns black on main display Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Won't Fix Bug description: 1) Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 2) gnome-shell: Installed: 3.38.4-1ubuntu1 Candidate: 3.38.4-1ubuntu1 Version table: *** 3.38.4-1ubuntu1 500 500 http://pl.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status 3) This bug only appears on Gnome with Wayland. It does not affect Gnome on xorg. After the screen stays off and locked for some time the wallpaper on the main display turns black. It never happens on the secondary display. The issue is also reported, here on gitlab: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3206 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 11:50:15 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1922340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]
As a workaround I updated to Thunderbird Beta (v. 97.0b3) and it does not cause the alt-tab problem. -- 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/1933996 Title: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27] Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: When a new Wayland session is created from a login, Alt-tab works as expected to change windows. After sometime Alt-tab fails to do anything (super-tab still works to change applications) and the following error is created in syslog: gnome-shell[18]: JS ERROR: TypeError: window is null#012_createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27#012_init@resource:///org/gnome/shell/ui/altTab.js:1004:34#012_init@resource:///org/gnome/shell/ui/altTab.js:1045:24#012_init@resource:///org/gnome/shell/ui/altTab.js:568:30#012_startSwitcher@resource:///org/gnome/shell/ui/windowManager.js:2069:24 The only workaround I have found is to logout and log back in, however after some time the error repeats itself. Ubuntu 21.04 gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 10:53:32 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-11 (230 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-27 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1933996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]
Not fixed. Jammy w/ mutter 41.3. Alt-tab works on boot. Send e-mail with Thunderbird, alt-tab fails to work. ** Changed in: mutter (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1933996 Title: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27] Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: When a new Wayland session is created from a login, Alt-tab works as expected to change windows. After sometime Alt-tab fails to do anything (super-tab still works to change applications) and the following error is created in syslog: gnome-shell[18]: JS ERROR: TypeError: window is null#012_createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27#012_init@resource:///org/gnome/shell/ui/altTab.js:1004:34#012_init@resource:///org/gnome/shell/ui/altTab.js:1045:24#012_init@resource:///org/gnome/shell/ui/altTab.js:568:30#012_startSwitcher@resource:///org/gnome/shell/ui/windowManager.js:2069:24 The only workaround I have found is to logout and log back in, however after some time the error repeats itself. Ubuntu 21.04 gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 10:53:32 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-11 (230 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-27 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1933996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944113]
*** Bug 146942 has been marked as a duplicate of this bug. *** -- 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/1944113 Title: Many UI elements (list box, drop down) don't work at all in kf5 environment Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: Many UI elements (list box, drop down) don't work at all in kf5 environment. This makes LO unusable. For example, try to insert a table from standard toolbar in LO Writer – nothing inserted. Same happens with other drop down elements (styles, font family, font size, font color, font highlight, etc). Bug reports at LO's bug tracker: https://bugs.documentfoundation.org/show_bug.cgi?id=144037 https://bugs.documentfoundation.org/show_bug.cgi?id=144562 https://gerrit.libreoffice.org/c/core/+/122116 Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.11.0-34-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz Memory: 7,7 GiB Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3 Calc: threaded To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1944113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
FWIW I could reproduce the issue, as described in comment #16, on Debian testing. -- 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/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session Status in gnome-control-center package in Ubuntu: New Bug description: Currently, there is no way to define Left Alt + Left Shift key combination to change keyboard layouts in Ubuntu 22.04. In previous versions there was a convenient "Keyboard Layout Options" window in which there was able to set required key combination. Since 22.04 release I can't find a way to do that because useless "Keyboard Shortcuts" window opens instead in which unable to set Left Alt + Left Shift as "Switch to the next source" shortcut. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-01-07 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) NonfreeKernelModules: nvidia_modeset nvidia Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: jammy wayland-session ubiquity-22.04.3 Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1947445] Re: Click actions "previews" and "minimize-or-previews" are broken
Hello Sebastian, or anyone else affected, Accepted gnome-shell-extension-ubuntu-dock into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/70~ubuntu3.21.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-impish -- 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/1947445 Title: Click actions "previews" and "minimize-or-previews" are broken Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Impish: Fix Committed Bug description: [ Impact ] Since upgrading to Ubuntu 21.10 the "previews" and "minimize-or- previews" options no longer work as expected. [ Test case ] 1. gsettings set org.gnome.shell.extensions.dash-to-dock click-action "previews" - Open multiple windows for an application - Click on the icon, previews should be shown 2. gsettings set org.gnome.shell.extensions.dash-to-dock click-action "minimize-or-previews" - Open multiple windows for an application - Click on the icon, previews should be shown [ Regression potential ] Wrong action is taken if an application has urgent windows For "previews": No previews are shown when clicking on the app icon. For "minimize-or-previews": When multiple windows of the same application are open and I click on the app icon, no previews are shown anymore. Schema: org.gnome.shell.extensions.dash-to-dock Name: click-action Value: "minimize-or-previews" Value: "previews" Description: Ubuntu 21.10 Release: 21.10 gnome-shell-extension-ubuntu-dock: Installed: 70~ubuntu3 ProblemType: BugDistroRelease: Ubuntu 21.10 Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 11:32:51 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-21 (1090 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: allSourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to impish on 2021-10-14 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1947445/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949352] Re: Removable drives are not auto-mounted after screen lock/unlock
Hello István, or anyone else affected, Accepted gnome-shell-extension-ubuntu-dock into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/70~ubuntu3.21.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-impish -- 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/1949352 Title: Removable drives are not auto-mounted after screen lock/unlock Status in gnome-shell-extension-dashtodock package in Ubuntu: Won't Fix Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Impish: Fix Committed Bug description: [ Impact ] If I lock and then unlock the screen, and then connect a removable drive, it is not recognized by the GNOME shell. The kernel logs show the drive, I can mount it manually, but it is not mounted automatically. The logged errors are attached. [ Test case ] - Mount a device - Lock the screen - Unlock the screen - The device should be re-mounted (and no errors in journal) [ Regression Potential ] Devices could be leaked if gc doesn't work as expected --- I could fix the issue by modifying the source code as given in the attached patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-01 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell 40.5-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Tags: wayland-session impish Uname: Linux 5.13.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1949352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874578] Re: Dock has very long load time when show-mounts is enabled
Hello Xanthopoulos, or anyone else affected, Accepted gnome-shell-extension-ubuntu-dock into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/70~ubuntu3.21.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-impish -- 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/1874578 Title: Dock has very long load time when show-mounts is enabled Status in Dash to dock: New Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Impish: Fix Committed Bug description: [ Impact ] Icons are not showing on loading when mount-points are showing [ Test case ] - Start a new session (ensure that the system has mounted devices) - The launcher icons should show promptly without any delay [ Regression potential ] Mounted devices will have wrong or no icon. I just upgraded from Ubuntu 18.04 to 20.04. When I boot my system I have to wait at least 10 to 15 seconds for the application icons to load on dock. Meanwhile everything else seems to be working properly. I didn't experience this behavior in Ubuntu 18.04. Also the dock doesn't trigger when I move my cursor to the left of the screen. (I have set the docker to Auto-Hide mode and it's position is on the left of my screen). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2016-08-03 (1359 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Tags: focal third-party-packages wayland-session Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1874578/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949572] Re: Shell freeze after right click on the app in the dock
Hello giorgi, or anyone else affected, Accepted gnome-shell-extension-ubuntu-dock into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/70~ubuntu3.21.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-impish -- 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/1949572 Title: Shell freeze after right click on the app in the dock Status in gnome-shell-extension-appindicator package in Ubuntu: Invalid Status in gnome-shell-extension-dashtodock package in Ubuntu: Won't Fix Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Impish: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Impish: Fix Committed Bug description: [ Impact ] When you click the icon of the app in the dock to open it for the first time and then immediately right click to see options, everything freezes and you are forced to reboot. [ Test case ] - Under wayland, open an application and immediately right-click its icon - The shell should show the application window that has just been opened in the windows submenu, and continue working [ Regression potential] No windows previews are showing in the application menu --- I'm using Ubuntu 21.10. I installed it today. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-03 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Tags: impish wayland-session Uname: Linux 5.13.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1949572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951599] Re: gnome-shell logs errors when ejecting SD card
Hello Bin, or anyone else affected, Accepted gnome-shell-extension-ubuntu-dock into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/70~ubuntu3.21.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-impish -- 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/1951599 Title: gnome-shell logs errors when ejecting SD card Status in OEM Priority Project: Triaged Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Impish: Fix Committed Bug description: [ Impact ] When I click eject SD card in Files(nautilus), I found the gnome-shell reported some crash logs. [ Test case ] - Mount a device - Eject the device - No errors should be shown and the device re-mountable [ Regression Potential ] Devices could be leaked if gc doesn't work as expected --- Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object .Gjs_components_autorunManager_AutorunSource (0x55a9d8e846e0), has been already deallocated — impossible to emit any signal on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object Gio.Settings (0x55a9db521970), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: == Stack trace for context 0x55a9d8a00120 == Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #0 7ffc0b63cc20 b resource:///org/gnome/shell/ui/messageTray.js:785 (bc6f58577e0 @ 149) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #1 55a9d8f150b0 i resource:///org/gnome/shell/ui/components/autorunManager.js:270 (1ec3f0bf4060 @ 69) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #2 55a9d8f15018 i resource:///org/gnome/shell/ui/components/autorunManager.js:176 (1ec3f0bf4290 @ 25) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #3 7ffc0b63d8c0 b self-hosted:850 (1ec3f0b2a650 @ 454) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1951599/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959027] Re: Various UI and theming issues in Firefox snap when running in Plasma Wayland session
** Attachment added: "Second screenshot: GTK File dialog with distorted fonts" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1959027/+attachment/5557396/+files/Screenshot_20220125_165558.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1959027 Title: Various UI and theming issues in Firefox snap when running in Plasma Wayland session Status in firefox package in Ubuntu: New Bug description: Hello, after installing the current live image of Kubuntu Jammy, I tested the preinstalled Firefox snap on the Plasma Wayland session (which I use by default), and discovered multiple UI and theming issues: 1. I had switched my global theme to Breeze Dark. Nevertheless Firefox used a light theme when I launched it for the first time. Interestingly, at further runs Firefox properly came up with a dark theme. But I had restarted my session in between and also had removed and reinstalled the Firefox snap, so it's possible that one of these actions triggered Firefox to finally use a dark theme. 2. The font size in the UI is too big (compare with other KDE apps on screenshots). 3. It apparently doesn't use Breeze (light or dark) as the UI theme, but something else (Adwaita I guess). 4. The mouse cursor uses the wrong theme and is too big (it changes visible if move the cursor in and out of the Firefox window). 5. If I click e.g. on "File -> Open file...", the file dialog is not the one from KDE but the one from GTK/Gnome. And the UI text is displayed in a rather jagged/distorted way (see screenshot). The issues described above do _not_ appear: * If I run Firefox as snap in Plasma X11 session. * If I run Firefox as deb (both Plasma Wayland and X11 session work fine). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 96.0.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BuildID: 20220119190439 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: KDE Date: Tue Jan 25 17:19:38 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-01-25 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220125.1) IpRoute: default via 192.168.178.1 dev enp4s0 proto dhcp metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.178.0/24 dev enp4s0 proto kernel scope link src 192.168.178.44 metric 100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=96.0.2/20220119190439 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1959027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959027] [NEW] Various UI and theming issues in Firefox snap when running in Plasma Wayland session
Public bug reported: Hello, after installing the current live image of Kubuntu Jammy, I tested the preinstalled Firefox snap on the Plasma Wayland session (which I use by default), and discovered multiple UI and theming issues: 1. I had switched my global theme to Breeze Dark. Nevertheless Firefox used a light theme when I launched it for the first time. Interestingly, at further runs Firefox properly came up with a dark theme. But I had restarted my session in between and also had removed and reinstalled the Firefox snap, so it's possible that one of these actions triggered Firefox to finally use a dark theme. 2. The font size in the UI is too big (compare with other KDE apps on screenshots). 3. It apparently doesn't use Breeze (light or dark) as the UI theme, but something else (Adwaita I guess). 4. The mouse cursor uses the wrong theme and is too big (it changes visible if move the cursor in and out of the Firefox window). 5. If I click e.g. on "File -> Open file...", the file dialog is not the one from KDE but the one from GTK/Gnome. And the UI text is displayed in a rather jagged/distorted way (see screenshot). The issues described above do _not_ appear: * If I run Firefox as snap in Plasma X11 session. * If I run Firefox as deb (both Plasma Wayland and X11 session work fine). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 96.0.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BuildID: 20220119190439 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: KDE Date: Tue Jan 25 17:19:38 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-01-25 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220125.1) IpRoute: default via 192.168.178.1 dev enp4s0 proto dhcp metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.178.0/24 dev enp4s0 proto kernel scope link src 192.168.178.44 metric 100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=96.0.2/20220119190439 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Wrong theme, UI font too big" https://bugs.launchpad.net/bugs/1959027/+attachment/5557383/+files/Screenshot_20220125_165617.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1959027 Title: Various UI and theming issues in Firefox snap when running in Plasma Wayland session Status in firefox package in Ubuntu: New Bug description: Hello, after installing the current live image of Kubuntu Jammy, I tested the preinstalled Firefox snap on the Plasma Wayland session (which I use by default), and discovered multiple UI and theming issues: 1. I had switched my global theme to Breeze Dark. Nevertheless Firefox used a light theme when I launched it for the first time. Interestingly, at further runs Firefox properly came up with a dark theme. But I had restarted my session in between and also had removed and reinstalled the Firefox snap, so it's possible that one of these actions triggered Firefox to finally use a dark theme. 2. The font size in the UI is too big (compare with other KDE
[Desktop-packages] [Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
The issue is not present in impish. +, for instance, works as expected there in a wayland session. ** Tags added: regression-release -- 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/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session Status in gnome-control-center package in Ubuntu: New Bug description: Currently, there is no way to define Left Alt + Left Shift key combination to change keyboard layouts in Ubuntu 22.04. In previous versions there was a convenient "Keyboard Layout Options" window in which there was able to set required key combination. Since 22.04 release I can't find a way to do that because useless "Keyboard Shortcuts" window opens instead in which unable to set Left Alt + Left Shift as "Switch to the next source" shortcut. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-01-07 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) NonfreeKernelModules: nvidia_modeset nvidia Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: jammy wayland-session ubiquity-22.04.3 Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1939210] Re: When using HWE, zfs-kmod and zfs user tools versions must match
This affects https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/index.php?1959017 (for some reason couldn't link the bug URL) GitHub URL is: https://github.com/ubuntu/zsys/issues/220 ** Also affects: zsys (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/ubuntu/zsys/issues #220 https://github.com/ubuntu/zsys/issues/220 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1939210 Title: When using HWE, zfs-kmod and zfs user tools versions must match Status in zfs-linux package in Ubuntu: Confirmed Status in zsys package in Ubuntu: New Bug description: Ubuntu 20.04.2 LTS I ran into a problem recently (https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177) due to mismatched versions when HWE upgraded the kernel from 5.8 to 5.11 where the userspace tools don't match the zfs-kmod version. After the update the system ended up with zfs-0.8.3-1ubuntu12.12 and zfs- kmod-2.0.2-1ubuntu5 My understanding from asking in the OpenZFS github is that the two versions must match. This bug is to figure out what to do for those of us who use HWE and zfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849478] Re: [snap] (experimental) pipewire support not available
I have a slightly different on Impish, with 97.0.4692.99 (1878): With the pipewire flag enabled, I do get the popup, I can select a window but then nothing happens, and the initial popup doesn't ever close, I have to cancel the screen share. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1849478 Title: [snap] (experimental) pipewire support not available Status in chromium-browser package in Ubuntu: Fix Committed Bug description: I'm using the chromium snap (currently 77.0.3865.120, rev 899), it's not possible to enable experimental support for pipewire, as the toggle doesn't show up in chrome://flags. It would be nice to have chromium compiled with pipewire support, to enable screensharing in Hangouts and similar apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959015] [NEW] Switch to new HTTPS-capable domains for PPAs
Public bug reported: As described in bug 1473091, PPAs are now being served from new domains that aren't under launchpad.net and so can safely serve HTTPS without risk of compromising Launchpad session cookies. The old domains will keep working indefinitely, but nevertheless it would be good if we could arrange for add-apt-repository to use the new domains as of 22.04. The changes are: * http://ppa.launchpad.net/ → https://ppa.launchpadcontent.net/ (or http:// works too, but we should prefer https://) * https://private-ppa.launchpad.net/ → https://private-ppa.launchpadcontent.net/ ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1959015 Title: Switch to new HTTPS-capable domains for PPAs Status in software-properties package in Ubuntu: New Bug description: As described in bug 1473091, PPAs are now being served from new domains that aren't under launchpad.net and so can safely serve HTTPS without risk of compromising Launchpad session cookies. The old domains will keep working indefinitely, but nevertheless it would be good if we could arrange for add-apt-repository to use the new domains as of 22.04. The changes are: * http://ppa.launchpad.net/ → https://ppa.launchpadcontent.net/ (or http:// works too, but we should prefer https://) * https://private-ppa.launchpad.net/ → https://private-ppa.launchpadcontent.net/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1959015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959017] [NEW] zsys-commit.service will fail when zfs tools don't match DKMS version
Public bug reported: Originally reported the bug in [zsys's github issues](https://github.com/ubuntu/zsys/issues/220), wanting to link to zfs-linux bug, reporting it here to link it. **Describe the bug** This isn't a bug in `zsys` so much as a bug in the way Ubuntu manages ZFS packages which `zsys` relies on. The root cause is already reported at: > https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939210 When using HWE based kernel, the zfs-kmod is updated (currently to 2.x) while the LTS zfs packages are at 0.8.3 Currently the solution is to update the tools, the bug linked above points to a 3rd party ppa with updated tools. The reason for reporting the bug here - it affects the `zfs promote` command, which is used after a restore from a previous state occurs. So I thought this would be a good place to document this issue. - I also suggest that `zsysctl` should test for this discrepancy and warn about it. - Hoping an Ubuntu insider would help addressing this issue with the original bug maintainers for next LTS version (coming up in a couple of months) **To Reproduce** Steps to reproduce the behavior: 1. Make sure your system uses HWE kernel 2. Run `zfs version` and get a discrepancy in versions: > ``` > zfs-0.8.3-1ubuntu12.13 > zfs-kmod-2.0.6-1ubuntu2 > ``` 2. Make sure you have a saved zsys state in your GRUB menu. 3. Reboot to GRUB and select a saved state 4. Run `systemctl status zsys-commit` to see the error. `zsys-commit` service runs the equivalent of `sudo zsysctl boot commit` which marks the boot as successful. > ``` > ● zsys-commit.service - Mark current ZSYS boot as successful > Loaded: loaded (/lib/systemd/system/zsys-commit.service; enabled; vendor > preset: enabled) > Active: failed (Result: exit-code) since Sun 2022-01-23 23:21:41 EST; 10h > ago > Main PID: 12287 (code=exited, status=1/FAILURE) > > Jan 23 23:21:40 hostname systemd[1]: Starting Mark current ZSYS boot as > successful... > Jan 23 23:21:41 hostname zsysctl[12287]: level=error msg="couldn't commit: > couldn't promote dataset \"rpool/ROOT/ubuntu_ssfirw\": couldn't promote > \"rpool/ROOT/ubuntu_ssfirw\": not a cloned filesystem" > Jan 23 23:21:41 hostname systemd[1]: zsys-commit.service: Main process > exited, code=exited, status=1/FAILURE > Jan 23 23:21:41 hostname systemd[1]: zsys-commit.service: Failed with result > 'exit-code'. > Jan 23 23:21:41 hostname systemd[1]: Failed to start Mark current ZSYS boot > as successful. > ``` **Expected behavior** > ``` > ● zsys-commit.service - Mark current ZSYS boot as successful > Loaded: loaded (/lib/systemd/system/zsys-commit.service; enabled; vendor > preset: enabled) > Active: active (exited) since Mon 2022-01-24 18:51:11 EST; 15h ago >Main PID: 297120 (code=exited, status=0/SUCCESS) > Tasks: 0 (limit: 18951) > Memory: 0B > CGroup: /system.slice/zsys-commit.service > > Jan 24 18:51:10 Sygin systemd[1]: Starting Mark current ZSYS boot as > successful... > Jan 24 18:51:11 Sygin systemd[1]: Finished Mark current ZSYS boot as > successful. > ``` **ubuntu-bug output** I'm no longer in the broken state, and didn't run `ubuntu-bug` before. Bug report (mentioned above) contains much more info. **Installed versions:** - OS: Zorin OS 16 (based on Focal Fossa - Ubuntu 20.04 LTS) - Zsysd running version: 0.4.8 **Additional context** I've documented my ordeal as an askubuntu question which I ended up answering ([link](https://askubuntu.com/a/1389086/720005)). ** Affects: zsys (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1959017 Title: zsys-commit.service will fail when zfs tools don't match DKMS version Status in zsys package in Ubuntu: New Bug description: Originally reported the bug in [zsys's github issues](https://github.com/ubuntu/zsys/issues/220), wanting to link to zfs-linux bug, reporting it here to link it. **Describe the bug** This isn't a bug in `zsys` so much as a bug in the way Ubuntu manages ZFS packages which `zsys` relies on. The root cause is already reported at: > https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939210 When using HWE based kernel, the zfs-kmod is updated (currently to 2.x) while the LTS zfs packages are at 0.8.3 Currently the solution is to update the tools, the bug linked above points to a 3rd party ppa with updated tools. The reason for reporting the bug here - it affects the `zfs promote` command, which is used after a restore from a previous state occurs. So I thought this would be a good place to document this issue. - I also suggest that `zsysctl` should test for this discrepancy and warn about it. - Hoping an Ubuntu insider would help addressing this issue with the original bug maintainers for next LTS version (coming up in a couple of months) **To
[Desktop-packages] [Bug 1952947] Re: ubuntu-bug -w (using xprop) doesn't work under wayland
it's not really a bug in those x11 utilities, since as the name indicate they are utilities for x11. The fix probably is probably to remove the option from ubuntu-bug on wayland since poking to other process is not possible by design for security reason ** Changed in: x11-utils (Ubuntu Impish) Status: New => Invalid ** Changed in: x11-utils (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-utils in Ubuntu. https://bugs.launchpad.net/bugs/1952947 Title: ubuntu-bug -w (using xprop) doesn't work under wayland Status in apport package in Ubuntu: Triaged Status in x11-utils package in Ubuntu: Invalid Status in apport source package in Impish: Triaged Status in x11-utils source package in Impish: Invalid Status in apport source package in Jammy: Triaged Status in x11-utils source package in Jammy: Invalid Bug description: I want to report a Bug about the application Studio Controls. As I did it already quite a few times, I run "ubuntu-bug -w", get a message that I can select the window of the app I want to report a bug about after closing this message. I close the message with a click on the appropriate button. I click on the window of the application "Studio Controls" that I want to report a bug about. Nothing happens. I wait for a few minutes. Still nothing happens. In the console where I started ubuntu-bug -w I see the following message: (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed What I expect: Usaully when I use this procedure, after a relatively short while a new message window pops up asking me if the bug should be reported and showing me the data that is sent to Launchpad. I tried other applications, too, same effect. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: apport 2.20.11-0ubuntu71 ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18 Uname: Linux 5.13.0-21-lowlatency x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 1 20:01:23 2021 InstallationDate: Installed on 2020-04-12 (597 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1954970] Re: remmina "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version"
** Tags removed: rls-ii-incoming ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/1954970 Title: remmina "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version" Status in freerdp2 package in Ubuntu: New Bug description: Xubuntu Jammy (21.04) after upgrade libfreerdp-client2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1) libfreerdp2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1) Remmina can't connect to any RDP server (Win2008 R2) with error: "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version" Rollback to Impish version of libs libfreerdp-client2-2 2.3.0+dfsg1-2ubuntu2 libfreerdp2-2 2.3.0+dfsg1-2ubuntu2 makes it work normal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1954970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788535] Re: gnome-control-center shows 120Hz display frequencies that the display doesn't support (really only 60Hz hardware)
This bug was fixed in the package mutter - 41.3-1ubuntu1 --- mutter (41.3-1ubuntu1) jammy; urgency=medium * Merge with debian, includes these upstream changes: - window: Don't change workspaces of unmanaged windows (LP: #1933996) - backend: Reset idletime when unplugging the power cable (LP: #1945121) - clutter/text: Invalidate actor paint volume when it has changed (LP: #1882291) - backends/native: Ensure pointer is onscreen in input thread (LP: #1933186) - OSK Enter, space and backspace keys don't work when typing in Greek (LP: #1820523) - window: Don't change workspaces of unmanaged windows (LP: #1932328) * Remainig changes with debian: - debian/gbp.conf: update upstream branch to point to ubuntu/master - debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch: + X11: Add support for fractional scaling using Randr mutter (41.3-1) unstable; urgency=medium * New upstream release: - Check keyboard serials for activation - Fix mixed up refresh rates in multi-monitor setups (LP: #1788535) - Allow disabling HW cursors - Improve damage handling (LP: #1872870) - Consider xrandr flags for advertised modes - Ensure constraints after client resize - window-group: Disable culling when rendinging clone to offscreen buffer - Fix workspace switch animation in default plugin - Fix unfullscreening of window that were mapped fullscreen - Fix DMA-BUF screencasts with unredirected fullscreen windows - Fix orientation changes on devices with 90° mutter (41.2-2) unstable; urgency=medium * Team upload * d/p/Consistently-pass-timestamp-as-uint64-when-creating-MetaS.patch: Add proposed patch to fix FTBFS on 32-bit architectures * d/patches: Update to 41.2-6-g7b64c159a - Surface damage viewport improvements * Update patch metadata with upstream status mutter (41.2-1) unstable; urgency=medium * Team upload [ Simon McVittie ] * New upstream release * d/patches: Drop patches that were applied upstream * d/patches: Update to upstream gnome-41 branch commit 41.2-3-g5d0c26631 - wayland: Check keyboard serials for activation - Sync refresh rate to the correct monitor for maximized/full-screen apps in a multi-monitor layout - Add a debug environment variable to disable hardware cursors for faulty hardware and drivers [ Laurent Bigonville ] * debian/rules: Disable systemd support on non-linux architectures mutter (41.1-1) unstable; urgency=medium * Team upload * New upstream release * Drop a patch that came from upstream * Update Lintian overrides * Replace patches for #995929 with the version that was applied upstream * Remove workaround for #994806 * d/libmutter-9-0.symbols: Ignore removal of clutter_stage_capture_into. Nothing else in Debian references this symbol, except for forks of the mutter codebase. mutter (41.0-5) unstable; urgency=medium * Team upload * Merge packaging from unstable - No changes relative to 41.0-4, except for the changelog * Close #995929 via changelog. The patches in 41.0-4 seem to have been successful. * Release to unstable (starts transition: #996607) mutter (41.0-4) experimental; urgency=medium * Team upload * d/control.in: libmutter-test-9 Depends on mutter. It wants the libdefault.so plugin, which is in mutter.deb. * Update Lintian overrides for RUNPATH * d/patches: Another try at fixing #995929 (Closes: #995929) * d/rules: Disable gvfs when running unit tests mutter (41.0-3) experimental; urgency=medium * Team upload * d/p/tests-Change-how-we-wait-for-an-orientation-change.patch: Add patch attempting to fix #995929 * d/p/tests-Add-additional-debug-in-wait_for_orientation.patch, d/p/tests-Watch-the-orientation-manager-independently.patch: Try to diagnose what's going on if #995929 is still not fixed mutter (41.0-2) experimental; urgency=medium * Team upload * Build-depend on libgl-dev instead of transitional libgl1-mesa-dev * (Build-)Depend on libgles-dev instead of transitional libgles2-mesa-dev * d/rules: Don't let log from flaky tests overwrite log from main tests * d/p/tests-dbus-runner-Make-sure-to-tear-down-even-on-test-fai.patch: Add patch from upstream to stop failing tests causing a timeout. Failing tests will generally still cause FTBFS, but failing immediately is more buildd-friendly than timing out. * d/p/tests-Don-t-use-TestEnvironment.patch, d/p/tests-Don-t-continue-if-setup-commands-fail.patch: Update patches for installed-tests to latest version submitted upstream * d/p/tests-Add-additional-debug-for-Debian-995929.patch: Add more debug logging to try to diagnose #995929 mutter (41.0-1) experimental; urgency=medium * Team upload [ Jeremy Bicha ] * debian/watch: Watch for stable releases [ Simon McVittie ] * New upstream release * Update package names for ABI break *
[Desktop-packages] [Bug 1820523] Re: OSK Enter, space and backspace keys don't work when typing in Greek
This bug was fixed in the package mutter - 41.3-1ubuntu1 --- mutter (41.3-1ubuntu1) jammy; urgency=medium * Merge with debian, includes these upstream changes: - window: Don't change workspaces of unmanaged windows (LP: #1933996) - backend: Reset idletime when unplugging the power cable (LP: #1945121) - clutter/text: Invalidate actor paint volume when it has changed (LP: #1882291) - backends/native: Ensure pointer is onscreen in input thread (LP: #1933186) - OSK Enter, space and backspace keys don't work when typing in Greek (LP: #1820523) - window: Don't change workspaces of unmanaged windows (LP: #1932328) * Remainig changes with debian: - debian/gbp.conf: update upstream branch to point to ubuntu/master - debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch: + X11: Add support for fractional scaling using Randr mutter (41.3-1) unstable; urgency=medium * New upstream release: - Check keyboard serials for activation - Fix mixed up refresh rates in multi-monitor setups (LP: #1788535) - Allow disabling HW cursors - Improve damage handling (LP: #1872870) - Consider xrandr flags for advertised modes - Ensure constraints after client resize - window-group: Disable culling when rendinging clone to offscreen buffer - Fix workspace switch animation in default plugin - Fix unfullscreening of window that were mapped fullscreen - Fix DMA-BUF screencasts with unredirected fullscreen windows - Fix orientation changes on devices with 90° mutter (41.2-2) unstable; urgency=medium * Team upload * d/p/Consistently-pass-timestamp-as-uint64-when-creating-MetaS.patch: Add proposed patch to fix FTBFS on 32-bit architectures * d/patches: Update to 41.2-6-g7b64c159a - Surface damage viewport improvements * Update patch metadata with upstream status mutter (41.2-1) unstable; urgency=medium * Team upload [ Simon McVittie ] * New upstream release * d/patches: Drop patches that were applied upstream * d/patches: Update to upstream gnome-41 branch commit 41.2-3-g5d0c26631 - wayland: Check keyboard serials for activation - Sync refresh rate to the correct monitor for maximized/full-screen apps in a multi-monitor layout - Add a debug environment variable to disable hardware cursors for faulty hardware and drivers [ Laurent Bigonville ] * debian/rules: Disable systemd support on non-linux architectures mutter (41.1-1) unstable; urgency=medium * Team upload * New upstream release * Drop a patch that came from upstream * Update Lintian overrides * Replace patches for #995929 with the version that was applied upstream * Remove workaround for #994806 * d/libmutter-9-0.symbols: Ignore removal of clutter_stage_capture_into. Nothing else in Debian references this symbol, except for forks of the mutter codebase. mutter (41.0-5) unstable; urgency=medium * Team upload * Merge packaging from unstable - No changes relative to 41.0-4, except for the changelog * Close #995929 via changelog. The patches in 41.0-4 seem to have been successful. * Release to unstable (starts transition: #996607) mutter (41.0-4) experimental; urgency=medium * Team upload * d/control.in: libmutter-test-9 Depends on mutter. It wants the libdefault.so plugin, which is in mutter.deb. * Update Lintian overrides for RUNPATH * d/patches: Another try at fixing #995929 (Closes: #995929) * d/rules: Disable gvfs when running unit tests mutter (41.0-3) experimental; urgency=medium * Team upload * d/p/tests-Change-how-we-wait-for-an-orientation-change.patch: Add patch attempting to fix #995929 * d/p/tests-Add-additional-debug-in-wait_for_orientation.patch, d/p/tests-Watch-the-orientation-manager-independently.patch: Try to diagnose what's going on if #995929 is still not fixed mutter (41.0-2) experimental; urgency=medium * Team upload * Build-depend on libgl-dev instead of transitional libgl1-mesa-dev * (Build-)Depend on libgles-dev instead of transitional libgles2-mesa-dev * d/rules: Don't let log from flaky tests overwrite log from main tests * d/p/tests-dbus-runner-Make-sure-to-tear-down-even-on-test-fai.patch: Add patch from upstream to stop failing tests causing a timeout. Failing tests will generally still cause FTBFS, but failing immediately is more buildd-friendly than timing out. * d/p/tests-Don-t-use-TestEnvironment.patch, d/p/tests-Don-t-continue-if-setup-commands-fail.patch: Update patches for installed-tests to latest version submitted upstream * d/p/tests-Add-additional-debug-for-Debian-995929.patch: Add more debug logging to try to diagnose #995929 mutter (41.0-1) experimental; urgency=medium * Team upload [ Jeremy Bicha ] * debian/watch: Watch for stable releases [ Simon McVittie ] * New upstream release * Update package names for ABI break *
[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
This bug was fixed in the package mutter - 41.3-1ubuntu1 --- mutter (41.3-1ubuntu1) jammy; urgency=medium * Merge with debian, includes these upstream changes: - window: Don't change workspaces of unmanaged windows (LP: #1933996) - backend: Reset idletime when unplugging the power cable (LP: #1945121) - clutter/text: Invalidate actor paint volume when it has changed (LP: #1882291) - backends/native: Ensure pointer is onscreen in input thread (LP: #1933186) - OSK Enter, space and backspace keys don't work when typing in Greek (LP: #1820523) - window: Don't change workspaces of unmanaged windows (LP: #1932328) * Remainig changes with debian: - debian/gbp.conf: update upstream branch to point to ubuntu/master - debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch: + X11: Add support for fractional scaling using Randr mutter (41.3-1) unstable; urgency=medium * New upstream release: - Check keyboard serials for activation - Fix mixed up refresh rates in multi-monitor setups (LP: #1788535) - Allow disabling HW cursors - Improve damage handling (LP: #1872870) - Consider xrandr flags for advertised modes - Ensure constraints after client resize - window-group: Disable culling when rendinging clone to offscreen buffer - Fix workspace switch animation in default plugin - Fix unfullscreening of window that were mapped fullscreen - Fix DMA-BUF screencasts with unredirected fullscreen windows - Fix orientation changes on devices with 90° mutter (41.2-2) unstable; urgency=medium * Team upload * d/p/Consistently-pass-timestamp-as-uint64-when-creating-MetaS.patch: Add proposed patch to fix FTBFS on 32-bit architectures * d/patches: Update to 41.2-6-g7b64c159a - Surface damage viewport improvements * Update patch metadata with upstream status mutter (41.2-1) unstable; urgency=medium * Team upload [ Simon McVittie ] * New upstream release * d/patches: Drop patches that were applied upstream * d/patches: Update to upstream gnome-41 branch commit 41.2-3-g5d0c26631 - wayland: Check keyboard serials for activation - Sync refresh rate to the correct monitor for maximized/full-screen apps in a multi-monitor layout - Add a debug environment variable to disable hardware cursors for faulty hardware and drivers [ Laurent Bigonville ] * debian/rules: Disable systemd support on non-linux architectures mutter (41.1-1) unstable; urgency=medium * Team upload * New upstream release * Drop a patch that came from upstream * Update Lintian overrides * Replace patches for #995929 with the version that was applied upstream * Remove workaround for #994806 * d/libmutter-9-0.symbols: Ignore removal of clutter_stage_capture_into. Nothing else in Debian references this symbol, except for forks of the mutter codebase. mutter (41.0-5) unstable; urgency=medium * Team upload * Merge packaging from unstable - No changes relative to 41.0-4, except for the changelog * Close #995929 via changelog. The patches in 41.0-4 seem to have been successful. * Release to unstable (starts transition: #996607) mutter (41.0-4) experimental; urgency=medium * Team upload * d/control.in: libmutter-test-9 Depends on mutter. It wants the libdefault.so plugin, which is in mutter.deb. * Update Lintian overrides for RUNPATH * d/patches: Another try at fixing #995929 (Closes: #995929) * d/rules: Disable gvfs when running unit tests mutter (41.0-3) experimental; urgency=medium * Team upload * d/p/tests-Change-how-we-wait-for-an-orientation-change.patch: Add patch attempting to fix #995929 * d/p/tests-Add-additional-debug-in-wait_for_orientation.patch, d/p/tests-Watch-the-orientation-manager-independently.patch: Try to diagnose what's going on if #995929 is still not fixed mutter (41.0-2) experimental; urgency=medium * Team upload * Build-depend on libgl-dev instead of transitional libgl1-mesa-dev * (Build-)Depend on libgles-dev instead of transitional libgles2-mesa-dev * d/rules: Don't let log from flaky tests overwrite log from main tests * d/p/tests-dbus-runner-Make-sure-to-tear-down-even-on-test-fai.patch: Add patch from upstream to stop failing tests causing a timeout. Failing tests will generally still cause FTBFS, but failing immediately is more buildd-friendly than timing out. * d/p/tests-Don-t-use-TestEnvironment.patch, d/p/tests-Don-t-continue-if-setup-commands-fail.patch: Update patches for installed-tests to latest version submitted upstream * d/p/tests-Add-additional-debug-for-Debian-995929.patch: Add more debug logging to try to diagnose #995929 mutter (41.0-1) experimental; urgency=medium * Team upload [ Jeremy Bicha ] * debian/watch: Watch for stable releases [ Simon McVittie ] * New upstream release * Update package names for ABI break *
[Desktop-packages] [Bug 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side
This bug was fixed in the package mutter - 41.3-1ubuntu1 --- mutter (41.3-1ubuntu1) jammy; urgency=medium * Merge with debian, includes these upstream changes: - window: Don't change workspaces of unmanaged windows (LP: #1933996) - backend: Reset idletime when unplugging the power cable (LP: #1945121) - clutter/text: Invalidate actor paint volume when it has changed (LP: #1882291) - backends/native: Ensure pointer is onscreen in input thread (LP: #1933186) - OSK Enter, space and backspace keys don't work when typing in Greek (LP: #1820523) - window: Don't change workspaces of unmanaged windows (LP: #1932328) * Remainig changes with debian: - debian/gbp.conf: update upstream branch to point to ubuntu/master - debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch: + X11: Add support for fractional scaling using Randr mutter (41.3-1) unstable; urgency=medium * New upstream release: - Check keyboard serials for activation - Fix mixed up refresh rates in multi-monitor setups (LP: #1788535) - Allow disabling HW cursors - Improve damage handling (LP: #1872870) - Consider xrandr flags for advertised modes - Ensure constraints after client resize - window-group: Disable culling when rendinging clone to offscreen buffer - Fix workspace switch animation in default plugin - Fix unfullscreening of window that were mapped fullscreen - Fix DMA-BUF screencasts with unredirected fullscreen windows - Fix orientation changes on devices with 90° mutter (41.2-2) unstable; urgency=medium * Team upload * d/p/Consistently-pass-timestamp-as-uint64-when-creating-MetaS.patch: Add proposed patch to fix FTBFS on 32-bit architectures * d/patches: Update to 41.2-6-g7b64c159a - Surface damage viewport improvements * Update patch metadata with upstream status mutter (41.2-1) unstable; urgency=medium * Team upload [ Simon McVittie ] * New upstream release * d/patches: Drop patches that were applied upstream * d/patches: Update to upstream gnome-41 branch commit 41.2-3-g5d0c26631 - wayland: Check keyboard serials for activation - Sync refresh rate to the correct monitor for maximized/full-screen apps in a multi-monitor layout - Add a debug environment variable to disable hardware cursors for faulty hardware and drivers [ Laurent Bigonville ] * debian/rules: Disable systemd support on non-linux architectures mutter (41.1-1) unstable; urgency=medium * Team upload * New upstream release * Drop a patch that came from upstream * Update Lintian overrides * Replace patches for #995929 with the version that was applied upstream * Remove workaround for #994806 * d/libmutter-9-0.symbols: Ignore removal of clutter_stage_capture_into. Nothing else in Debian references this symbol, except for forks of the mutter codebase. mutter (41.0-5) unstable; urgency=medium * Team upload * Merge packaging from unstable - No changes relative to 41.0-4, except for the changelog * Close #995929 via changelog. The patches in 41.0-4 seem to have been successful. * Release to unstable (starts transition: #996607) mutter (41.0-4) experimental; urgency=medium * Team upload * d/control.in: libmutter-test-9 Depends on mutter. It wants the libdefault.so plugin, which is in mutter.deb. * Update Lintian overrides for RUNPATH * d/patches: Another try at fixing #995929 (Closes: #995929) * d/rules: Disable gvfs when running unit tests mutter (41.0-3) experimental; urgency=medium * Team upload * d/p/tests-Change-how-we-wait-for-an-orientation-change.patch: Add patch attempting to fix #995929 * d/p/tests-Add-additional-debug-in-wait_for_orientation.patch, d/p/tests-Watch-the-orientation-manager-independently.patch: Try to diagnose what's going on if #995929 is still not fixed mutter (41.0-2) experimental; urgency=medium * Team upload * Build-depend on libgl-dev instead of transitional libgl1-mesa-dev * (Build-)Depend on libgles-dev instead of transitional libgles2-mesa-dev * d/rules: Don't let log from flaky tests overwrite log from main tests * d/p/tests-dbus-runner-Make-sure-to-tear-down-even-on-test-fai.patch: Add patch from upstream to stop failing tests causing a timeout. Failing tests will generally still cause FTBFS, but failing immediately is more buildd-friendly than timing out. * d/p/tests-Don-t-use-TestEnvironment.patch, d/p/tests-Don-t-continue-if-setup-commands-fail.patch: Update patches for installed-tests to latest version submitted upstream * d/p/tests-Add-additional-debug-for-Debian-995929.patch: Add more debug logging to try to diagnose #995929 mutter (41.0-1) experimental; urgency=medium * Team upload [ Jeremy Bicha ] * debian/watch: Watch for stable releases [ Simon McVittie ] * New upstream release * Update package names for ABI break *
[Desktop-packages] [Bug 1872870] Re: When zoom is enabled, mouse pointer leaves square trails on desktop
This bug was fixed in the package mutter - 41.3-1ubuntu1 --- mutter (41.3-1ubuntu1) jammy; urgency=medium * Merge with debian, includes these upstream changes: - window: Don't change workspaces of unmanaged windows (LP: #1933996) - backend: Reset idletime when unplugging the power cable (LP: #1945121) - clutter/text: Invalidate actor paint volume when it has changed (LP: #1882291) - backends/native: Ensure pointer is onscreen in input thread (LP: #1933186) - OSK Enter, space and backspace keys don't work when typing in Greek (LP: #1820523) - window: Don't change workspaces of unmanaged windows (LP: #1932328) * Remainig changes with debian: - debian/gbp.conf: update upstream branch to point to ubuntu/master - debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch: + X11: Add support for fractional scaling using Randr mutter (41.3-1) unstable; urgency=medium * New upstream release: - Check keyboard serials for activation - Fix mixed up refresh rates in multi-monitor setups (LP: #1788535) - Allow disabling HW cursors - Improve damage handling (LP: #1872870) - Consider xrandr flags for advertised modes - Ensure constraints after client resize - window-group: Disable culling when rendinging clone to offscreen buffer - Fix workspace switch animation in default plugin - Fix unfullscreening of window that were mapped fullscreen - Fix DMA-BUF screencasts with unredirected fullscreen windows - Fix orientation changes on devices with 90° mutter (41.2-2) unstable; urgency=medium * Team upload * d/p/Consistently-pass-timestamp-as-uint64-when-creating-MetaS.patch: Add proposed patch to fix FTBFS on 32-bit architectures * d/patches: Update to 41.2-6-g7b64c159a - Surface damage viewport improvements * Update patch metadata with upstream status mutter (41.2-1) unstable; urgency=medium * Team upload [ Simon McVittie ] * New upstream release * d/patches: Drop patches that were applied upstream * d/patches: Update to upstream gnome-41 branch commit 41.2-3-g5d0c26631 - wayland: Check keyboard serials for activation - Sync refresh rate to the correct monitor for maximized/full-screen apps in a multi-monitor layout - Add a debug environment variable to disable hardware cursors for faulty hardware and drivers [ Laurent Bigonville ] * debian/rules: Disable systemd support on non-linux architectures mutter (41.1-1) unstable; urgency=medium * Team upload * New upstream release * Drop a patch that came from upstream * Update Lintian overrides * Replace patches for #995929 with the version that was applied upstream * Remove workaround for #994806 * d/libmutter-9-0.symbols: Ignore removal of clutter_stage_capture_into. Nothing else in Debian references this symbol, except for forks of the mutter codebase. mutter (41.0-5) unstable; urgency=medium * Team upload * Merge packaging from unstable - No changes relative to 41.0-4, except for the changelog * Close #995929 via changelog. The patches in 41.0-4 seem to have been successful. * Release to unstable (starts transition: #996607) mutter (41.0-4) experimental; urgency=medium * Team upload * d/control.in: libmutter-test-9 Depends on mutter. It wants the libdefault.so plugin, which is in mutter.deb. * Update Lintian overrides for RUNPATH * d/patches: Another try at fixing #995929 (Closes: #995929) * d/rules: Disable gvfs when running unit tests mutter (41.0-3) experimental; urgency=medium * Team upload * d/p/tests-Change-how-we-wait-for-an-orientation-change.patch: Add patch attempting to fix #995929 * d/p/tests-Add-additional-debug-in-wait_for_orientation.patch, d/p/tests-Watch-the-orientation-manager-independently.patch: Try to diagnose what's going on if #995929 is still not fixed mutter (41.0-2) experimental; urgency=medium * Team upload * Build-depend on libgl-dev instead of transitional libgl1-mesa-dev * (Build-)Depend on libgles-dev instead of transitional libgles2-mesa-dev * d/rules: Don't let log from flaky tests overwrite log from main tests * d/p/tests-dbus-runner-Make-sure-to-tear-down-even-on-test-fai.patch: Add patch from upstream to stop failing tests causing a timeout. Failing tests will generally still cause FTBFS, but failing immediately is more buildd-friendly than timing out. * d/p/tests-Don-t-use-TestEnvironment.patch, d/p/tests-Don-t-continue-if-setup-commands-fail.patch: Update patches for installed-tests to latest version submitted upstream * d/p/tests-Add-additional-debug-for-Debian-995929.patch: Add more debug logging to try to diagnose #995929 mutter (41.0-1) experimental; urgency=medium * Team upload [ Jeremy Bicha ] * debian/watch: Watch for stable releases [ Simon McVittie ] * New upstream release * Update package names for ABI break *
[Desktop-packages] [Bug 1933186] Re: gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from met
This bug was fixed in the package mutter - 41.3-1ubuntu1 --- mutter (41.3-1ubuntu1) jammy; urgency=medium * Merge with debian, includes these upstream changes: - window: Don't change workspaces of unmanaged windows (LP: #1933996) - backend: Reset idletime when unplugging the power cable (LP: #1945121) - clutter/text: Invalidate actor paint volume when it has changed (LP: #1882291) - backends/native: Ensure pointer is onscreen in input thread (LP: #1933186) - OSK Enter, space and backspace keys don't work when typing in Greek (LP: #1820523) - window: Don't change workspaces of unmanaged windows (LP: #1932328) * Remainig changes with debian: - debian/gbp.conf: update upstream branch to point to ubuntu/master - debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch: + X11: Add support for fractional scaling using Randr mutter (41.3-1) unstable; urgency=medium * New upstream release: - Check keyboard serials for activation - Fix mixed up refresh rates in multi-monitor setups (LP: #1788535) - Allow disabling HW cursors - Improve damage handling (LP: #1872870) - Consider xrandr flags for advertised modes - Ensure constraints after client resize - window-group: Disable culling when rendinging clone to offscreen buffer - Fix workspace switch animation in default plugin - Fix unfullscreening of window that were mapped fullscreen - Fix DMA-BUF screencasts with unredirected fullscreen windows - Fix orientation changes on devices with 90° mutter (41.2-2) unstable; urgency=medium * Team upload * d/p/Consistently-pass-timestamp-as-uint64-when-creating-MetaS.patch: Add proposed patch to fix FTBFS on 32-bit architectures * d/patches: Update to 41.2-6-g7b64c159a - Surface damage viewport improvements * Update patch metadata with upstream status mutter (41.2-1) unstable; urgency=medium * Team upload [ Simon McVittie ] * New upstream release * d/patches: Drop patches that were applied upstream * d/patches: Update to upstream gnome-41 branch commit 41.2-3-g5d0c26631 - wayland: Check keyboard serials for activation - Sync refresh rate to the correct monitor for maximized/full-screen apps in a multi-monitor layout - Add a debug environment variable to disable hardware cursors for faulty hardware and drivers [ Laurent Bigonville ] * debian/rules: Disable systemd support on non-linux architectures mutter (41.1-1) unstable; urgency=medium * Team upload * New upstream release * Drop a patch that came from upstream * Update Lintian overrides * Replace patches for #995929 with the version that was applied upstream * Remove workaround for #994806 * d/libmutter-9-0.symbols: Ignore removal of clutter_stage_capture_into. Nothing else in Debian references this symbol, except for forks of the mutter codebase. mutter (41.0-5) unstable; urgency=medium * Team upload * Merge packaging from unstable - No changes relative to 41.0-4, except for the changelog * Close #995929 via changelog. The patches in 41.0-4 seem to have been successful. * Release to unstable (starts transition: #996607) mutter (41.0-4) experimental; urgency=medium * Team upload * d/control.in: libmutter-test-9 Depends on mutter. It wants the libdefault.so plugin, which is in mutter.deb. * Update Lintian overrides for RUNPATH * d/patches: Another try at fixing #995929 (Closes: #995929) * d/rules: Disable gvfs when running unit tests mutter (41.0-3) experimental; urgency=medium * Team upload * d/p/tests-Change-how-we-wait-for-an-orientation-change.patch: Add patch attempting to fix #995929 * d/p/tests-Add-additional-debug-in-wait_for_orientation.patch, d/p/tests-Watch-the-orientation-manager-independently.patch: Try to diagnose what's going on if #995929 is still not fixed mutter (41.0-2) experimental; urgency=medium * Team upload * Build-depend on libgl-dev instead of transitional libgl1-mesa-dev * (Build-)Depend on libgles-dev instead of transitional libgles2-mesa-dev * d/rules: Don't let log from flaky tests overwrite log from main tests * d/p/tests-dbus-runner-Make-sure-to-tear-down-even-on-test-fai.patch: Add patch from upstream to stop failing tests causing a timeout. Failing tests will generally still cause FTBFS, but failing immediately is more buildd-friendly than timing out. * d/p/tests-Don-t-use-TestEnvironment.patch, d/p/tests-Don-t-continue-if-setup-commands-fail.patch: Update patches for installed-tests to latest version submitted upstream * d/p/tests-Add-additional-debug-for-Debian-995929.patch: Add more debug logging to try to diagnose #995929 mutter (41.0-1) experimental; urgency=medium * Team upload [ Jeremy Bicha ] * debian/watch: Watch for stable releases [ Simon McVittie ] * New upstream release * Update package names for ABI break *
[Desktop-packages] [Bug 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]
This bug was fixed in the package mutter - 41.3-1ubuntu1 --- mutter (41.3-1ubuntu1) jammy; urgency=medium * Merge with debian, includes these upstream changes: - window: Don't change workspaces of unmanaged windows (LP: #1933996) - backend: Reset idletime when unplugging the power cable (LP: #1945121) - clutter/text: Invalidate actor paint volume when it has changed (LP: #1882291) - backends/native: Ensure pointer is onscreen in input thread (LP: #1933186) - OSK Enter, space and backspace keys don't work when typing in Greek (LP: #1820523) - window: Don't change workspaces of unmanaged windows (LP: #1932328) * Remainig changes with debian: - debian/gbp.conf: update upstream branch to point to ubuntu/master - debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch: + X11: Add support for fractional scaling using Randr mutter (41.3-1) unstable; urgency=medium * New upstream release: - Check keyboard serials for activation - Fix mixed up refresh rates in multi-monitor setups (LP: #1788535) - Allow disabling HW cursors - Improve damage handling (LP: #1872870) - Consider xrandr flags for advertised modes - Ensure constraints after client resize - window-group: Disable culling when rendinging clone to offscreen buffer - Fix workspace switch animation in default plugin - Fix unfullscreening of window that were mapped fullscreen - Fix DMA-BUF screencasts with unredirected fullscreen windows - Fix orientation changes on devices with 90° mutter (41.2-2) unstable; urgency=medium * Team upload * d/p/Consistently-pass-timestamp-as-uint64-when-creating-MetaS.patch: Add proposed patch to fix FTBFS on 32-bit architectures * d/patches: Update to 41.2-6-g7b64c159a - Surface damage viewport improvements * Update patch metadata with upstream status mutter (41.2-1) unstable; urgency=medium * Team upload [ Simon McVittie ] * New upstream release * d/patches: Drop patches that were applied upstream * d/patches: Update to upstream gnome-41 branch commit 41.2-3-g5d0c26631 - wayland: Check keyboard serials for activation - Sync refresh rate to the correct monitor for maximized/full-screen apps in a multi-monitor layout - Add a debug environment variable to disable hardware cursors for faulty hardware and drivers [ Laurent Bigonville ] * debian/rules: Disable systemd support on non-linux architectures mutter (41.1-1) unstable; urgency=medium * Team upload * New upstream release * Drop a patch that came from upstream * Update Lintian overrides * Replace patches for #995929 with the version that was applied upstream * Remove workaround for #994806 * d/libmutter-9-0.symbols: Ignore removal of clutter_stage_capture_into. Nothing else in Debian references this symbol, except for forks of the mutter codebase. mutter (41.0-5) unstable; urgency=medium * Team upload * Merge packaging from unstable - No changes relative to 41.0-4, except for the changelog * Close #995929 via changelog. The patches in 41.0-4 seem to have been successful. * Release to unstable (starts transition: #996607) mutter (41.0-4) experimental; urgency=medium * Team upload * d/control.in: libmutter-test-9 Depends on mutter. It wants the libdefault.so plugin, which is in mutter.deb. * Update Lintian overrides for RUNPATH * d/patches: Another try at fixing #995929 (Closes: #995929) * d/rules: Disable gvfs when running unit tests mutter (41.0-3) experimental; urgency=medium * Team upload * d/p/tests-Change-how-we-wait-for-an-orientation-change.patch: Add patch attempting to fix #995929 * d/p/tests-Add-additional-debug-in-wait_for_orientation.patch, d/p/tests-Watch-the-orientation-manager-independently.patch: Try to diagnose what's going on if #995929 is still not fixed mutter (41.0-2) experimental; urgency=medium * Team upload * Build-depend on libgl-dev instead of transitional libgl1-mesa-dev * (Build-)Depend on libgles-dev instead of transitional libgles2-mesa-dev * d/rules: Don't let log from flaky tests overwrite log from main tests * d/p/tests-dbus-runner-Make-sure-to-tear-down-even-on-test-fai.patch: Add patch from upstream to stop failing tests causing a timeout. Failing tests will generally still cause FTBFS, but failing immediately is more buildd-friendly than timing out. * d/p/tests-Don-t-use-TestEnvironment.patch, d/p/tests-Don-t-continue-if-setup-commands-fail.patch: Update patches for installed-tests to latest version submitted upstream * d/p/tests-Add-additional-debug-for-Debian-995929.patch: Add more debug logging to try to diagnose #995929 mutter (41.0-1) experimental; urgency=medium * Team upload [ Jeremy Bicha ] * debian/watch: Watch for stable releases [ Simon McVittie ] * New upstream release * Update package names for ABI break *
[Desktop-packages] [Bug 1945121] Re: Ubuntu auto-suspends when I unplug my laptop after not having used it for a few minutes.
This bug was fixed in the package mutter - 41.3-1ubuntu1 --- mutter (41.3-1ubuntu1) jammy; urgency=medium * Merge with debian, includes these upstream changes: - window: Don't change workspaces of unmanaged windows (LP: #1933996) - backend: Reset idletime when unplugging the power cable (LP: #1945121) - clutter/text: Invalidate actor paint volume when it has changed (LP: #1882291) - backends/native: Ensure pointer is onscreen in input thread (LP: #1933186) - OSK Enter, space and backspace keys don't work when typing in Greek (LP: #1820523) - window: Don't change workspaces of unmanaged windows (LP: #1932328) * Remainig changes with debian: - debian/gbp.conf: update upstream branch to point to ubuntu/master - debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch: + X11: Add support for fractional scaling using Randr mutter (41.3-1) unstable; urgency=medium * New upstream release: - Check keyboard serials for activation - Fix mixed up refresh rates in multi-monitor setups (LP: #1788535) - Allow disabling HW cursors - Improve damage handling (LP: #1872870) - Consider xrandr flags for advertised modes - Ensure constraints after client resize - window-group: Disable culling when rendinging clone to offscreen buffer - Fix workspace switch animation in default plugin - Fix unfullscreening of window that were mapped fullscreen - Fix DMA-BUF screencasts with unredirected fullscreen windows - Fix orientation changes on devices with 90° mutter (41.2-2) unstable; urgency=medium * Team upload * d/p/Consistently-pass-timestamp-as-uint64-when-creating-MetaS.patch: Add proposed patch to fix FTBFS on 32-bit architectures * d/patches: Update to 41.2-6-g7b64c159a - Surface damage viewport improvements * Update patch metadata with upstream status mutter (41.2-1) unstable; urgency=medium * Team upload [ Simon McVittie ] * New upstream release * d/patches: Drop patches that were applied upstream * d/patches: Update to upstream gnome-41 branch commit 41.2-3-g5d0c26631 - wayland: Check keyboard serials for activation - Sync refresh rate to the correct monitor for maximized/full-screen apps in a multi-monitor layout - Add a debug environment variable to disable hardware cursors for faulty hardware and drivers [ Laurent Bigonville ] * debian/rules: Disable systemd support on non-linux architectures mutter (41.1-1) unstable; urgency=medium * Team upload * New upstream release * Drop a patch that came from upstream * Update Lintian overrides * Replace patches for #995929 with the version that was applied upstream * Remove workaround for #994806 * d/libmutter-9-0.symbols: Ignore removal of clutter_stage_capture_into. Nothing else in Debian references this symbol, except for forks of the mutter codebase. mutter (41.0-5) unstable; urgency=medium * Team upload * Merge packaging from unstable - No changes relative to 41.0-4, except for the changelog * Close #995929 via changelog. The patches in 41.0-4 seem to have been successful. * Release to unstable (starts transition: #996607) mutter (41.0-4) experimental; urgency=medium * Team upload * d/control.in: libmutter-test-9 Depends on mutter. It wants the libdefault.so plugin, which is in mutter.deb. * Update Lintian overrides for RUNPATH * d/patches: Another try at fixing #995929 (Closes: #995929) * d/rules: Disable gvfs when running unit tests mutter (41.0-3) experimental; urgency=medium * Team upload * d/p/tests-Change-how-we-wait-for-an-orientation-change.patch: Add patch attempting to fix #995929 * d/p/tests-Add-additional-debug-in-wait_for_orientation.patch, d/p/tests-Watch-the-orientation-manager-independently.patch: Try to diagnose what's going on if #995929 is still not fixed mutter (41.0-2) experimental; urgency=medium * Team upload * Build-depend on libgl-dev instead of transitional libgl1-mesa-dev * (Build-)Depend on libgles-dev instead of transitional libgles2-mesa-dev * d/rules: Don't let log from flaky tests overwrite log from main tests * d/p/tests-dbus-runner-Make-sure-to-tear-down-even-on-test-fai.patch: Add patch from upstream to stop failing tests causing a timeout. Failing tests will generally still cause FTBFS, but failing immediately is more buildd-friendly than timing out. * d/p/tests-Don-t-use-TestEnvironment.patch, d/p/tests-Don-t-continue-if-setup-commands-fail.patch: Update patches for installed-tests to latest version submitted upstream * d/p/tests-Add-additional-debug-for-Debian-995929.patch: Add more debug logging to try to diagnose #995929 mutter (41.0-1) experimental; urgency=medium * Team upload [ Jeremy Bicha ] * debian/watch: Watch for stable releases [ Simon McVittie ] * New upstream release * Update package names for ABI break *
[Desktop-packages] [Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
I'm changing the tag, while it seems worth investigating more it doesn't seem important enough to be tracked using the rls bug process at this point ** Tags removed: rls-jj-incoming ** Tags added: rls-jj-notfixing -- 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/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session Status in gnome-control-center package in Ubuntu: New Bug description: Currently, there is no way to define Left Alt + Left Shift key combination to change keyboard layouts in Ubuntu 22.04. In previous versions there was a convenient "Keyboard Layout Options" window in which there was able to set required key combination. Since 22.04 release I can't find a way to do that because useless "Keyboard Shortcuts" window opens instead in which unable to set Left Alt + Left Shift as "Switch to the next source" shortcut. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-01-07 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) NonfreeKernelModules: nvidia_modeset nvidia Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: jammy wayland-session ubiquity-22.04.3 Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934457] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_unref() from on_window_icon_changed() from g_closure_invoke() from sig
*** This bug is a duplicate of bug 1934458 *** https://bugs.launchpad.net/bugs/1934458 ** This bug has been marked a duplicate of bug 1934458 gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() from g_object_dispatch_properties_changed() from g_object_notify_queue_thaw() from g_object_thaw_notify() from meta_window_update_icon_now() from idle_update_icon() -- 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/1934457 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_unref() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() from g_object_dispatch_properties_changed() from g_object_notify_queue_thaw() from g_object_thaw_notify() from meta_window_update_icon_now() from idle_update_icon() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.4-1ubuntu3~21.04.1, the problem page at https://errors.ubuntu.com/problem/eca665045730307781118f49eecca44ef0b9ea17 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1934457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
** Description changed: [Impact] - * In any Ubuntu series, if user using a old GPU (which supported by + * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] - * install nvidia-390 on nvidia-390 supported system. - * prime-select on-demand - * reboot - * glxinfo - * after applying this patch, it will fall back to "ON" mode after reboot. + * install nvidia-390 on nvidia-390 supported system. + * prime-select on-demand + * reboot + * glxinfo + * after applying this patch, it will fall back to "ON" mode after reboot. [Where problems could occur] - * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. - * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. + * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. + * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. + * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. + --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Impish: New Status in ubuntu-drivers-common source package in Impish: Triaged Status in nvidia-settings source package in Jammy: New Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950484] Re: Adding an admin user a Gnome Control Center should set the right groups
This bug was fixed in the package accountsservice - 0.6.55-3ubuntu4 --- accountsservice (0.6.55-3ubuntu4) jammy; urgency=medium * debian/patches/git_new_meson.patch: - include git patch to fix the build with the new meson -- Sebastien Bacher Tue, 25 Jan 2022 11:20:15 +0100 ** Changed in: accountsservice (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1950484 Title: Adding an admin user a Gnome Control Center should set the right groups Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Jammy: Fix Released Bug description: Currently when installing Ubuntu , the default admin belongs to several essential groups : adm cdrom sudo dip plugdev lpadmin lxd sambashare But when adding a user from GCC , the new admin user will only belong to : sudo This leads that the second admin cannot add printers and so on... This is observed on a clean 20.04.3 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1950484/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
@Robie I am not sure what rejecting the uploads actually accomplished (other than forcing me to re-upload the exact same sources) for something that can be amended in the bug description on Launchpad. This said, I did not notice that the section was missing. While mistakes can happen, please restrain from implying that I "just sponsor and leave". Thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Impish: New Status in ubuntu-drivers-common source package in Impish: Triaged Status in nvidia-settings source package in Jammy: New Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958710] Re: Merge network-manager 1.34.0-2 (main) from Debian unstable/testing (main)
Hi Sebastien, Thank you for the link. Good to know this list is closely monitored by the Desktop team. (Also "funny" that for "network-manager" package, the last stable upstream version is not reported: an issue with the "watch" file?) I guess for Git, I will need to continue pinging someone on IRC, that's fine :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1958710 Title: Merge network-manager 1.34.0-2 (main) from Debian unstable/testing (main) Status in network-manager package in Ubuntu: Triaged Bug description: There are some differences between versions from Debian and Ubuntu. A new version has been released a week ago. Debian Changelog: network-manager (1.34.0-2) unstable; urgency=medium * Demote wpasupplicant to Recommends. There are enough use cases for network-manager not involving Wi-Fi which justifies to make this dependency optional. (Closes: #919619, #980218) -- Michael Biebl Tue, 18 Jan 2022 20:59:36 +0100 network-manager (1.34.0-1) unstable; urgency=medium * New upstream version 1.34.0 * Rebase patches * Install nm-priv-helper service * Update symbols file for libnm0 -- Michael Biebl Fri, 14 Jan 2022 00:18:58 +0100 NM ChangeLog: = NetworkManager-1.34 Overview of changes since NetworkManager-1.32 = * initrd: wait for both IPv4 and IPv6 with "ip=dhcp,dhcp6". * core: better handle sd-resolved errors when resolving hostnames. * nmcli: fix import WireGuard profile with DNS domain and address family disabled. * ndisc: send router solicitations before expiry. * policy: send earlier the ip configs to the DNS manager. * core: support linking with LLD 13. * wireguard: importing wg-quick configuration files with nmcli no longer sets a negative, exclusive "dns-priority". This plays better with common split DNS setups that use systemd-resolved. Adjust the "dns-priority" to your liking after import yourself. * NetworkManager no longer listens for netlink events for traffic control objects (qdiscs and filters). * core: add internal nm-priv-helper service for separating privileges and have a way to drop capabilities from NetworkManager daemon. * bond: add support for setting queue-id of bond port. * dns: support configuring DNS over TLS (DoT) with systemd-resolved. * nmtui: add support for WireGuard profiles. * nmcli: add aliases `nmcli device up|down` beside connect|disconnect. * conscious language: Deprecate 'Device.Slaves' D-Bus property in favor of new 'Device.Ports' property. Depracate 'nm_device_*_get_slaves()' in favor of 'nm_device_get_ports()' in libnm. * nmcli: invoking nmcli command without arguments will now show 'default' instead of null address in route4 or route6 section. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1958710/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818990] Re: Ubuntu software (gnome-software) does not show packages from other repositorys.
Hi! I'm facing the same issue. I maintain several Ubuntu packages as part of the XtraDeb initiative. Sadly, none of my packages appear in gnome-software. Some of the packages I provide are just newer versions of already existing distro packages. I use the exact same packaging recipe. Still, my versions do not show. One of the main objective of my initiative is to facilitate the end-user life with packages that do not exist in the distro (orphans). This bug/limitation partially defeats that purpose. Is there a workaround for this? Other than: sudo apt install . Thank you! Jhonny Oliveira https://xtradeb.net -- 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/1818990 Title: Ubuntu software (gnome-software) does not show packages from other repositorys. Status in gnome-software package in Ubuntu: Confirmed Bug description: I have my repository with some packages, but I can`t find this packages from Ubuntu Software (gnome-software Ubuntu 18.04). Also I can't find software in gnome-software from next repos ppa:openshot.developers/ppa ppa:webupd8team/sublime-text-3 ppa:ubuntugis/ubuntugis-unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1818990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818990] Re: Ubuntu software (gnome-software) does not show packages from other repositorys.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed -- 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/1818990 Title: Ubuntu software (gnome-software) does not show packages from other repositorys. Status in gnome-software package in Ubuntu: Confirmed Bug description: I have my repository with some packages, but I can`t find this packages from Ubuntu Software (gnome-software Ubuntu 18.04). Also I can't find software in gnome-software from next repos ppa:openshot.developers/ppa ppa:webupd8team/sublime-text-3 ppa:ubuntugis/ubuntugis-unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1818990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1632027] Re: New Document feature missing from Nautilus 3.20+
So, https://help.launchpad.net/HelpOnFormatting says that the MoinMoin wiki syntax is supported, which it is evidently not, so here's the code bit from my post, cleaned up: [...] this experiment, which worked well: mkdir ~/.templates touch ~/.templates/document.txt Edit relevant bit in ~/.config/user-dirs.dirs: XDG_TEMPLATES_DIR="$HOME/.templates" -- 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/1632027 Title: New Document feature missing from Nautilus 3.20+ Status in Nautilus: Invalid Status in nautilus package in Ubuntu: Confirmed Bug description: Ubuntu has a patch ( 16_unity_new_documents.patch ) to enable a 'New Document' function in the right-click context menu. This patch was not ported to Nautilus 3.20 so this Ubuntu-specific feature is missing in Ubuntu 16.10. https://bazaar.launchpad.net/~ubuntu- desktop/nautilus/ubuntu/view/head:/debian/patches/16_unity_new_documents.patch While this patch being disabled is noted in the debian/changelog, here's a formal bug to document the issue and maybe give it a bit more visibility so that it will be fixed. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 10 12:54:50 2016 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.preferences' b'open-folder-on-dnd-hover' b'false' b'org.gnome.nautilus.window-state' b'sidebar-width' b'171' b'org.gnome.nautilus.window-state' b'geometry' b"'1106x542+436+438'" b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2016-08-11 (59 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1632027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1632027] Re: New Document feature missing from Nautilus 3.20+
This still (surprisingly) seems to be an issue in Ubuntu 22.04 ... Perhaps Ubuntu could add support for having the templates in a hidden folder such as `~/.templates`, and ship it just a single empty file, as a starting example? I just tried this experiment, which worked well: `mkdir ~/.templates` `touch ~/.templates/document.txt` Edit relevant bit in `~/.config/user-dirs.dirs`: `XDG_TEMPLATES_DIR="$HOME/.templates"` I was able to right-click in a folder and given a "New Document > document" option. (Comment also added in Gitlab issue #407 mentioned by 林博仁 (Buo-ren, Lin) on 2018-05-06 above) -- 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/1632027 Title: New Document feature missing from Nautilus 3.20+ Status in Nautilus: Invalid Status in nautilus package in Ubuntu: Confirmed Bug description: Ubuntu has a patch ( 16_unity_new_documents.patch ) to enable a 'New Document' function in the right-click context menu. This patch was not ported to Nautilus 3.20 so this Ubuntu-specific feature is missing in Ubuntu 16.10. https://bazaar.launchpad.net/~ubuntu- desktop/nautilus/ubuntu/view/head:/debian/patches/16_unity_new_documents.patch While this patch being disabled is noted in the debian/changelog, here's a formal bug to document the issue and maybe give it a bit more visibility so that it will be fixed. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 10 12:54:50 2016 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.preferences' b'open-folder-on-dnd-hover' b'false' b'org.gnome.nautilus.window-state' b'sidebar-width' b'171' b'org.gnome.nautilus.window-state' b'geometry' b"'1106x542+436+438'" b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2016-08-11 (59 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1632027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958972] Re: [upstream] Thunderbird 91 does not fully honor the dark theme
Launchpad has imported 3 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1720770. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2021-07-15T19:59:26+00:00 Gus-andrews wrote: Created attachment 9231417 Screen Shot 2021-07-13 at 4.52.20 PM.png User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:90.0) Gecko/20100101 Firefox/90.0 Steps to reproduce: A number of bugs indicate that Thunderbird is poorly prepared to navigate the new universe where Mac, Linux, and Windows UIs can be switched into "dark" mode. The following bugs appear to be related: bug 1544212 bug 1638233 bug 1640390 bug 1651617 bug 1663275 bug 1675862 bug 1685781 bug 1718772 bug 1720640 bug 1705497 bug 1708974 bug 1709489 bug 1712632 bug 1657833 bug 1614731 bug 1667561 In the case of that last bug, this becomes a user security issue as it is hard for the user of OpenPGP to see whether they are sending a message encrypted or not. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1958972/comments/0 On 2021-07-16T17:23:43+00:00 Vseerror wrote: you might find a few others in this query https://mzl.la/3ko7NZd Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1958972/comments/1 On 2021-07-21T21:13:47+00:00 Gus-andrews wrote: Batched by OS: Linux: bug 469300, bug 1455175, Bug 1544212 , Bug 1638233, bug 1659953, Bug 1663275 , bug 1671889, bug 1690531, bug 1694776, bug 1708974, bug 1720640, Bug 1720894, bug 1721264 Mac: bug 1624714, bug 1651617, bug 1657833, bug 1667561, bug 1675862 Windows: bug 1605727, Bug 1640390, Bug 1614731, bug 1669373, bug 1683575, bug 1685781, bug 1691316, bug 1689165, Bug 1691316, Bug 1705497, bug 1709489, Bug 1712632, bug 1718772 Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1958972/comments/2 ** Changed in: thunderbird Status: Unknown => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1958972 Title: [upstream] Thunderbird 91 does not fully honor the dark theme Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: New Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 thunderbird: Installed: 1:91.5.0+build1-0ubuntu0.20.04.1 Candidate: 1:91.5.0+build1-0ubuntu0.20.04.1 After the upgrade to Thunderbird 91, the dark theme settings are not honored in several places: * when reading an email message (either in the bottom right corner panel, or when opening a message in its own tab/window) * in the preferences These areas are "black on white" (light theme) rather than following the system settings (dark theme). The rest of the application is using dark theme. Going into Preferences -> Language & Appearance -> Colors has "Use system colors" selected by default. Also, it has "Override the colors specified by the content with my selection above" set to "Always". ANY SELECTION OF THESE TWO PARAMETERS IS BROKEN: * As I said, choosing "Always" + "Use system colors" means that Preferences + Emails are in light theme. * "Never" + "Use system colors", then the Preferences page uses the correct dark theme. The emails still appear in a light theme. * "Never" + UNSET "Use system colors", and force a white on black (dark) theme, then the preferences are in the correct dark theme (not the one forced, but the system one). The emails will appear white on black (the one forced), which is still wrong, as the system dark theme isn't black. However, if an email forces black text (e.g. HTML body), then it becomes unreadable (black text over black background). * "Always" + UNSET "Use system colors", then Preferences are in dark theme (but the one I forced, not the system one), email bodies are white on black (again, the one I forced), but any color information from the email is overridden. An HTML email with the usual "my replies are in red" won't have any red text. This is a clear regression from the earlier version of Thunderbird where all of this worked perfectly. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1958972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958972] Re: Thunderbird 91 does not fully honor the dark theme
There are a number of upstream bug reports for incomplete dark theme support, see this meta bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1720770. ** Summary changed: - Thunderbird 91 does not honor the dark theme + Thunderbird 91 does not fully honor the dark theme ** Summary changed: - Thunderbird 91 does not fully honor the dark theme + [upstream] Thunderbird 91 does not fully honor the dark theme ** Tags added: upstream ** Bug watch added: Mozilla Bugzilla #1720770 https://bugzilla.mozilla.org/show_bug.cgi?id=1720770 ** Also affects: thunderbird via https://bugzilla.mozilla.org/show_bug.cgi?id=1720770 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1958972 Title: [upstream] Thunderbird 91 does not fully honor the dark theme Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: New Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 thunderbird: Installed: 1:91.5.0+build1-0ubuntu0.20.04.1 Candidate: 1:91.5.0+build1-0ubuntu0.20.04.1 After the upgrade to Thunderbird 91, the dark theme settings are not honored in several places: * when reading an email message (either in the bottom right corner panel, or when opening a message in its own tab/window) * in the preferences These areas are "black on white" (light theme) rather than following the system settings (dark theme). The rest of the application is using dark theme. Going into Preferences -> Language & Appearance -> Colors has "Use system colors" selected by default. Also, it has "Override the colors specified by the content with my selection above" set to "Always". ANY SELECTION OF THESE TWO PARAMETERS IS BROKEN: * As I said, choosing "Always" + "Use system colors" means that Preferences + Emails are in light theme. * "Never" + "Use system colors", then the Preferences page uses the correct dark theme. The emails still appear in a light theme. * "Never" + UNSET "Use system colors", and force a white on black (dark) theme, then the preferences are in the correct dark theme (not the one forced, but the system one). The emails will appear white on black (the one forced), which is still wrong, as the system dark theme isn't black. However, if an email forces black text (e.g. HTML body), then it becomes unreadable (black text over black background). * "Always" + UNSET "Use system colors", then Preferences are in dark theme (but the one I forced, not the system one), email bodies are white on black (again, the one I forced), but any color information from the email is overridden. An HTML email with the usual "my replies are in red" won't have any red text. This is a clear regression from the earlier version of Thunderbird where all of this worked perfectly. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1958972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958972] [NEW] Thunderbird 91 does not honor the dark theme
Public bug reported: Description:Ubuntu 20.04.3 LTS Release:20.04 thunderbird: Installed: 1:91.5.0+build1-0ubuntu0.20.04.1 Candidate: 1:91.5.0+build1-0ubuntu0.20.04.1 After the upgrade to Thunderbird 91, the dark theme settings are not honored in several places: * when reading an email message (either in the bottom right corner panel, or when opening a message in its own tab/window) * in the preferences These areas are "black on white" (light theme) rather than following the system settings (dark theme). The rest of the application is using dark theme. Going into Preferences -> Language & Appearance -> Colors has "Use system colors" selected by default. Also, it has "Override the colors specified by the content with my selection above" set to "Always". ANY SELECTION OF THESE TWO PARAMETERS IS BROKEN: * As I said, choosing "Always" + "Use system colors" means that Preferences + Emails are in light theme. * "Never" + "Use system colors", then the Preferences page uses the correct dark theme. The emails still appear in a light theme. * "Never" + UNSET "Use system colors", and force a white on black (dark) theme, then the preferences are in the correct dark theme (not the one forced, but the system one). The emails will appear white on black (the one forced), which is still wrong, as the system dark theme isn't black. However, if an email forces black text (e.g. HTML body), then it becomes unreadable (black text over black background). * "Always" + UNSET "Use system colors", then Preferences are in dark theme (but the one I forced, not the system one), email bodies are white on black (again, the one I forced), but any color information from the email is overridden. An HTML email with the usual "my replies are in red" won't have any red text. This is a clear regression from the earlier version of Thunderbird where all of this worked perfectly. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1958972 Title: Thunderbird 91 does not honor the dark theme Status in thunderbird package in Ubuntu: New Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 thunderbird: Installed: 1:91.5.0+build1-0ubuntu0.20.04.1 Candidate: 1:91.5.0+build1-0ubuntu0.20.04.1 After the upgrade to Thunderbird 91, the dark theme settings are not honored in several places: * when reading an email message (either in the bottom right corner panel, or when opening a message in its own tab/window) * in the preferences These areas are "black on white" (light theme) rather than following the system settings (dark theme). The rest of the application is using dark theme. Going into Preferences -> Language & Appearance -> Colors has "Use system colors" selected by default. Also, it has "Override the colors specified by the content with my selection above" set to "Always". ANY SELECTION OF THESE TWO PARAMETERS IS BROKEN: * As I said, choosing "Always" + "Use system colors" means that Preferences + Emails are in light theme. * "Never" + "Use system colors", then the Preferences page uses the correct dark theme. The emails still appear in a light theme. * "Never" + UNSET "Use system colors", and force a white on black (dark) theme, then the preferences are in the correct dark theme (not the one forced, but the system one). The emails will appear white on black (the one forced), which is still wrong, as the system dark theme isn't black. However, if an email forces black text (e.g. HTML body), then it becomes unreadable (black text over black background). * "Always" + UNSET "Use system colors", then Preferences are in dark theme (but the one I forced, not the system one), email bodies are white on black (again, the one I forced), but any color information from the email is overridden. An HTML email with the usual "my replies are in red" won't have any red text. This is a clear regression from the earlier version of Thunderbird where all of this worked perfectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1958972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950484] Re: Adding an admin user a Gnome Control Center should set the right groups
** Package changed: gnome-control-center (Ubuntu Jammy) => accountsservice (Ubuntu Jammy) ** Changed in: accountsservice (Ubuntu Jammy) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1950484 Title: Adding an admin user a Gnome Control Center should set the right groups Status in accountsservice package in Ubuntu: Fix Committed Status in accountsservice source package in Jammy: Fix Committed Bug description: Currently when installing Ubuntu , the default admin belongs to several essential groups : adm cdrom sudo dip plugdev lpadmin lxd sambashare But when adding a user from GCC , the new admin user will only belong to : sudo This leads that the second admin cannot add printers and so on... This is observed on a clean 20.04.3 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1950484/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958970] [NEW] Auto-rotation does not work anymore
Public bug reported: With my Radeon Vega graphics card auto-rotation of the screen used to work in 21.04 but does not work anymore in 21.10. Also Cinnamon (which I have uninstall now) shows an error, saying that hardware acceleration does not work. This bug relates to https://bugs.launchpad.net/ubuntu/+bug/1958852 I reinstalled my system but still auto-rotation does not work. dmesg shows [1.990767] lis3lv02d: unknown sensor type 0x0 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 25 10:46:21 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:85de] InstallationDate: Installed on 2022-01-25 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP ENVY x360 Convertible 13-ar0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=4bbf320c-9d1b-4cb2-a03e-a7f170d88509 ro quiet nosplash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2019 dmi.bios.release: 15.19 dmi.bios.vendor: AMI dmi.bios.version: F.19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 85DE dmi.board.vendor: HP dmi.board.version: 41.36 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 41.36 dmi.modalias: dmi:bvnAMI:bvrF.19:bd12/26/2019:br15.19:efr41.36:svnHP:pnHPENVYx360Convertible13-ar0xxx:pvr:rvnHP:rn85DE:rvr41.36:cvnHP:ct31:cvrChassisVersion:sku7BR48EA#ABD: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ar0xxx dmi.product.sku: 7BR48EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubuntu wayland-session -- 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/1958970 Title: Auto-rotation does not work anymore Status in xorg package in Ubuntu: New Bug description: With my Radeon Vega graphics card auto-rotation of the screen used to work in 21.04 but does not work anymore in 21.10. Also Cinnamon (which I have uninstall now) shows an error, saying that hardware acceleration does not work. This bug relates to https://bugs.launchpad.net/ubuntu/+bug/1958852 I reinstalled my system but still auto-rotation does not work. dmesg shows [1.990767] lis3lv02d: unknown sensor type 0x0 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 25 10:46:21 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:85de] InstallationDate: Installed on 2022-01-25 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP ENVY x360 Convertible 13-ar0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=4bbf320c-9d1b-4cb2-a03e-a7f170d88509 ro quiet nosplash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present
[Desktop-packages] [Bug 1958684] Re: gnome-shell crashed with SIGFPE in meta_wayland_xdg_toplevel_send_configure() from meta_window_wayland_configure()
I would like to have it fixed in 20.04, indeed. I added the tag. Thank you for your advice and comments. For now, this should be sufficient for us to proceed. ** Tags added: rls-ff-incoming -- 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/1958684 Title: gnome-shell crashed with SIGFPE in meta_wayland_xdg_toplevel_send_configure() from meta_window_wayland_configure() Status in mutter package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/bd270ee843b327813e28ccddde4a1357b64e1326 --- To reproduce with Ubuntu 20.04: 1. Run Gnome or the Gnome-based Ubuntu Desktop on Wayland. 2. Download and install the snapshot build of Qt Creator from https://master.qt.io/snapshots/qtcreator/6.0/6.0.3/624/qt-creator-opensource-linux-x86_64-6.0.3_624.run Sorry for the inconvenience that the installer requires an account. You can easily get one free of charge. Let me know if you need help with that. 3. Start the installed Qt Creator with parameter "-tcs". "-tcs" will ignore local settings saved for Qt Creator, so it will not mess up settings you might have. The log-in session crashes. All running applications are being closed immediately and you get back to the login screen. Sure, there might be something wrong in our snapshot package, but no matter how wrong our package might be, Wayland/Gnome should not crash, should they? If I should provide any further information, please let me know. gnome-shell: 3.36.9-0ubuntu0.20.04.2 libwayland-server0: 1.18.0-1 xwayland: 2:1.20.13-1ubuntu1~20.04.2 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 18:18:40 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1621432157 InstallationDate: Installed on 2021-12-17 (35 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/qtrob RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 Signal: 8 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGFPE in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1958684/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1954649] Re: autopkgtest regressions with python3.10 as supported
** Changed in: python-hypothesis (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1954649 Title: autopkgtest regressions with python3.10 as supported Status in ipywidgets package in Ubuntu: New Status in pygobject package in Ubuntu: Fix Released Status in pytest-twisted package in Ubuntu: New Status in python-b2sdk package in Ubuntu: New Status in python-hypothesis package in Ubuntu: Fix Released Status in python-taskflow package in Ubuntu: Fix Released Status in python3-defaults package in Ubuntu: New Status in skimage package in Ubuntu: Invalid Status in supysonic package in Ubuntu: Fix Released Status in vorta package in Ubuntu: New Status in ipywidgets package in Debian: New Status in pygobject package in Debian: Fix Released Status in pytest-twisted package in Debian: New Status in python-b2sdk package in Debian: Confirmed Status in python-hypothesis package in Debian: Fix Released Status in supysonic package in Debian: Fix Released Status in vorta package in Debian: Confirmed Bug description: This bug is for tracking the packages having autopkgtest regressions with python3.10 as a supported version, blocking migration of python3-defaults/3.9.7-4. All packages are in universe except pygobject and python-taskflow in main. All packages have RC bugs in Debian except python-taskflow which is based on a newer upstream version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipywidgets/+bug/1954649/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
