[Bug 2065175] Re: In music-folder sometimes by clicking properties of a file, nautilus freezes
I'm also having this issue. I've seen it happen with flac files and mp3 files. The problem happens every time but only with certain files. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2065175 Title: In music-folder sometimes by clicking properties of a file, nautilus freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2065175/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2064177] Re: Window borders and shadows missing from GTK3 dialogs
I don't use autologin. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2064177 Title: Window borders and shadows missing from GTK3 dialogs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064177/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2064192] Re: Unable to resize windows
I don't use Autologin and have the same problem -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2064192 Title: Unable to resize windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064192/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2064177] Re: Window borders and shadows missing from GTK3 dialogs
I've noticed something, maybe this will help: all windows with SSD don't work properly, windows with CSD work as expected. Firefox main window with CSD works, sub-windows without don't. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2064177 Title: Window borders and shadows missing from GTK3 dialogs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064177/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2064192] Re: Unable to resize windows
In my test all applications have this problem only GTK4 and libadwaita do not, maybe also GTK3? Firefox with CSD works, but sub-windows without CSD don't work. Maybe this is related to SSD -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2064192 Title: Unable to resize windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064192/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2065072] [NEW] German translation for "Copy" is incorrect in Ubuntu 24.04
Public bug reported: Ubuntu 24.04 GNOME nautilus 46.0 (1:46.0-0ubuntu2) When you try to copy a file it adds (Copy) to the file but since Ubuntu 24.04 with German translations, Nautilus appends "(Kopieren)" to the file name. This is incorrect, as "Kopieren" means "to copy" in German, while the desired behavior would be to use the noun "(Kopie)" meaning "copy". In older Ubuntu versions (22.04, 23.10) this works as expected and appends "(Kopie)" ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2065072 Title: German translation for "Copy" is incorrect in Ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2065072/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2064177] Re: Window borders and shadows missing from GTK3 dialogs
I have also encountered this issue. Also QT and Electron applications have no border/shadow. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2064177 Title: Window borders and shadows missing from GTK3 dialogs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064177/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2064192] Re: Unable to resize windows
I have the same problem, can't resize any windows tested with Krita and VSCodium. I don't know if this is related, but sometimes the mouse clicks through the windows to the window below the current one. (only for those that don't resize) basically unusable -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2064192 Title: Unable to resize windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064192/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060993] [NEW] Startup applications / gnome-session-properties does not persist between logins
Public bug reported: Having installed Guake I tried adding `/usr/bin/guake --hide` to Startup Applications. However, it was not in the list of startup applications when I next booted. I tested logging off and logging on again and found it wasn't persisting between logins. Data I entered was: Name: Guake Command: /usr/bin/guake --hide Comment: Guake terminal I also tried just command=/usr/bin/guake ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-startup-applications 46.0-1ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 11 17:22:47 2024 InstallationDate: Installed on 2024-04-09 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240409) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2060993 Title: Startup applications / gnome-session-properties does not persist between logins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2060993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
It seems that the usual password keyring called Login is not automatically created in gnome-keyring. In fact there are no credentials of any kind in there on logging in after a clean install. If you change your password via the control panel, the login keyring is then created. However, when you reboot the Login keyring is not automatically unlocked, as it should be. So, any items you have stored in there are not accessible and you are asked for the password when a service needs credentials from it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060667] [NEW] No default keyring and does not unlock on login
Public bug reported: On a fresh install of Ubuntu 24.04 numbat, gnome-keyring does not seem to be properly configured. If I attempt to add an online account via settings > online accounts, after authentication with the online account gnome-keyring prompts me to create a default keyring because one does not exist yet, so I cancelled. Opening gnome-keyring reveals there is no entry under Passwords when I think there should be a "Login" password keyring that's automatically unlocked on login. Setting a new password via settings > system > users creates a new Loging keyring. However, this keyring is not automatically unlocked on login. So, whenever I first use an app after login that uses a keyring, such as connecting to Google drive via Nautilus, I'm prompted for the keyring password. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-keyring 46.1-2build1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 9 12:19:00 2024 InstallationDate: Installed on 2024-04-09 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240409) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060667 Title: No default keyring and does not unlock on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060667/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060137] Re: Gnome freezes on login with X11 and nvidia
*** This bug is a duplicate of bug 2059847 *** https://bugs.launchpad.net/bugs/2059847 I'm sorry if I'm wrong, I've now read the problems mentioned but I'm not having any problems related to input delay, when I try to log into the session it freezes and or black screens. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2060137 Title: Gnome freezes on login with X11 and nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060137] [NEW] Gnome freezes on login with X11 and nvidia
Public bug reported: Recently i updated muttter-common(42.9-0ubuntu7) and libmutter(42.9-0ubuntu7), gir1.2-mutter(42.9-0ubuntu7) on Ubuntu 22.04 LTS after which when I try to login the following issue happens but only when I use the nvidia driver and X11 this does not happen when using Wayland or Nouveau driver. The problem is when I try to log in, tested on nvidia drivers 535 and 545. in most cases: Desktop freezes for ~15s, then ~4s black screen, then ~20s grey screen, then works as expected. In some cases: Gnome locks up and needs a hard reset (mouse cursor does not freeze) In rare cases: Works as expected, except high CPU usage There are new error messages in the syslog file that weren't there before: gnome-shell[...]: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? gnome-shell[...]: Window manager warning: MetaSyncRing: Too many reboots -- disabling ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2060137 Title: Gnome freezes on login with X11 and nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046801] Re: Unable to launch Evolution: bwrap: Creating new namespace failed: Permission denied
As mentioned in the Mantic release notes, you can make a minimal
permissive AppArmor profile just for evolution. Create a file
/etc/apparmor.d/usr.bin.evolution (the filename is important) with the
contents below and restart AppArmor with "systemctl restart apparmor"
abi ,
include
/usr/bin/evolution flags=(unconfined) {
userns,
# Site-specific additions and overrides. See local/README for details.
include if exists
}
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/2046801
Title:
Unable to launch Evolution: bwrap: Creating new namespace failed:
Permission denied
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/2046801/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2048913] [NEW] "No CA certificate required" checkbox unselects after saving
Public bug reported: 1) Description: Ubuntu 22.04.3 LTS Release: 22.04 2) gnome-control-center: Installed: 1:41.7-0ubuntu0.22.04.8 Candidate: 1:41.7-0ubuntu0.22.04.8 3) When setting Protected EAP settings in the security tab of internet connections setting the check box for "No CA certificate required" should stay marked when editing the settings a future time. 4) When setting Protected EAP settings in the security tab of internet connections setting the check box for "No CA certificate required" doesn't stay set. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot of the settings" https://bugs.launchpad.net/bugs/2048913/+attachment/5738097/+files/gnome-security.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2048913 Title: "No CA certificate required" checkbox unselects after saving To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2048913/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878617] Re: Apple pages file type should be added to MIME types
Fantastic! I can confirm that this is fixed on Ubuntu 23.10. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1878617 Title: Apple pages file type should be added to MIME types To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1878617/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2042695] [NEW] gnome-control-center crashes
Public bug reported: This sums it up. I don't know what has changed recently to cause this. $ gnome-control-center (gnome-control-center:30888): GLib-CRITICAL **: 12:03:40.812: g_strsplit: assertion 'string != NULL' failed Segmentation fault (core dumped) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.7 ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 3 12:06:59 2023 InstallationDate: Installed on 2021-03-28 (949 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-04-30 (552 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2042695 Title: gnome-control-center crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2042695/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2013542] Re: [lunar] windows size/position is not saved for some apps
Also experiencing this issue in: Slack Terminator But not Firefox (interestingly). Also, any app that runs in fullscreen is fine. It's only maximized. This is on X11 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2013542 Title: [lunar] windows size/position is not saved for some apps To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2013542/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2033197] [NEW] ubuntu (perhaps its the gnome desktop) freezes every few seconds saying wait or force quit window then unfreezes, this still happens after reboot
Public bug reported: The windows for a number of apps e.g. Firefox or libreoffice etc freeze momentarily and displays a message saying either click to wait or click to force click the app which is not responding. After waiting a few seconds the app becomes responsive again and again repeats in minutes. Rebooting, updating and upgrading doesn't help. I check online and the bug reports to see if others had the same problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 27 10:10:49 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-23 (461 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2033197 Title: ubuntu (perhaps its the gnome desktop) freezes every few seconds saying wait or force quit window then unfreezes, this still happens after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2033197/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971434] Re: Display powersave only blanks, but does not turn off
Hello Daniel, I'm on 22.04, I can confirm that adding the config in your #33 fixes the issue for me. I have Ryzen graphics. Prior to the fix, running "xset dpms force off" resulted in the screen turning off and then turning on after a couple of seconds. After the fix, the screen stays off until input is entered, and the screensaver does turn off the monitor as expected. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1281580] Re: glib-compile-schemas doesn't compile relocatable schemas
With that said, should we change the title to include which types of relocatable schemas that are not compiled by glib-compile-schemas? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1281580 Title: glib-compile-schemas doesn't compile relocatable schemas To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1281580/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1281580] Re: glib-compile-schemas doesn't compile relocatable schemas
I filed the MATE counterpart for this bug at https://github.com/mate- desktop/mate-desktop/issues/562 # Workaround for some entries: Exclude "[:PATH]" **Disclaimer: This solution cannot be used for custom keyboard shortcuts (org.mate.control-center.keybinding), not even a single custom keyboard shortcut. Also, this method should not work for schemas that require sub-paths, even if they are not custom.** * Run this in a terminal: ``` sudo tee /usr/share/glib-2.0/schemas/zzz.gschema.override > /dev/null << 'EOF' # green mate-panel background color. type='color' must be set in addition [org.mate.panel.toplevel.background] color='#00ff00' type='color' # Terminal: Don't use color theme [org.mate.terminal.profile] use-theme-colors=false EOF sudo glib-compile-schemas /usr/share/glib-2.0/schemas/ ``` * No error was reported by glib-compile-schemas * Log out, and log in from MATE * Run this ``` # Check the values: gsettings get org.mate.panel.toplevel.background:/org/mate/panel/toplevels/top/background/ color # Output: # '#00ff00' gsettings get org.mate.panel.toplevel.background:/org/mate/panel/toplevels/top/background/ type # Output: # 'color' gsettings get org.mate.terminal.profile:/org/mate/terminal/profiles/default/ use-theme-colors # Output: # false # Reset to the new system wide default settings: gsettings reset-recursively org.mate.panel.toplevel.background:/org/mate/panel/toplevels/top/background/ gsettings reset org.mate.terminal.profile:/org/mate/terminal/profiles/default/ use-theme-colors # Check the values again to compare them with their previous output: gsettings get org.mate.panel.toplevel.background:/org/mate/panel/toplevels/top/background/ color # '#00ff00' gsettings get org.mate.panel.toplevel.background:/org/mate/panel/toplevels/top/background/ type # Output: # 'color' gsettings get org.mate.terminal.profile:/org/mate/terminal/profiles/default/ use-theme-colors # Output: # true ``` * As you can see, the values are changed. # Distributions Ubuntu MATE 22.04: ``` $ apt-cache show libglib2.0-bin | head -8 Package: libglib2.0-bin Architecture: amd64 Version: 2.72.4-0ubuntu2.2 Multi-Arch: foreign Priority: optional Section: misc Source: glib2.0 Origin: Ubuntu ``` Ubuntu MATE 23.04: ``` $ apt-cache show libglib2.0-bin | head -8 Package: libglib2.0-bin Architecture: amd64 Version: 2.76.1-1 Multi-Arch: foreign Priority: optional Section: misc Source: glib2.0 Origin: Ubuntu ``` ** Bug watch added: github.com/mate-desktop/mate-desktop/issues #562 https://github.com/mate-desktop/mate-desktop/issues/562 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1281580 Title: glib-compile-schemas doesn't compile relocatable schemas To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1281580/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
** Description changed: * "$HOME/.config/monitors.xml" is not installed by default in Ubuntu during the installation at this writing, you have to generate it by running the GUI preferences `$ gnome-control-center display` for GNOME, and `$ mate-display-properties` for MATE. * Both GNOME and MATE can be run on the same distro, which causes compatibility issues with monitors.xml: monitors.xml in Ubuntu 22.04, and 23.04 (GNOME) is starting with ``, while in Ubuntu MATE 22.04, and 23.04 it is starting with `` * The monitors.xml file name for MATE is defined at https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and for GNOME it is defined at https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008. Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour - monitors.xml in Ubuntu 23.04, and 22.04: + monitors.xml in Ubuntu 23.10, 23.04, and 22.04: ``` - - - 0 - 0 - 1 - yes - - - Virtual-1 - unknown - unknown - unknown - - - 1600 - 900 - 60.000 - - - - + + + 0 + 0 + 1 + yes + + + Virtual-1 + unknown + unknown + unknown + + + 1600 + 900 + 60.000 + + + + ``` monitors.xml in Ubuntu 22.04 (with ubuntu-mate-desktop installed), or 23.04 (with ubuntu-mate-desktop installed): ``` - - - - 0 - 0 - yes - - - Virtual-1 - ??? - 0x - 0x - - - 1600 - 900 - 60.000 - - - - - - - 0 - 0 - 1 - yes - - - Virtual-1 - unknown - unknown - unknown - - - 1280 - 800 - 59.810 - - - - + + + + 0 + 0 + yes + + + Virtual-1 + ??? + 0x + 0x + + + 1600 + 900 + 60.000 + + + + + + + 0 + 0 + 1 + yes + + + Virtual-1 + unknown + unknown + unknown + + + 1280 + 800 + 59.810 + + + + ``` monitors.xml in Ubuntu MATE 22.04, Ubuntu MATE 23.04, ubuntu-mate-desktop from Ubuntu 22.04, or ubuntu-mate-desktop from Ubuntu 23.04: ``` - - no - - ??? - 0x - 0x - 1600 - 900 - 60 - 0 - 0 - normal - no - no - yes - - - - - - - - + + no + + ??? + 0x + 0x + 1600 + 900 + 60 + 0 + 0 + normal + no + no + yes + + + + + + + + ``` Steps to reproduce the behaviour Steps I used to reproduce the issue in Ubuntu 22.04 with ubuntu-mate-desktop installed: * Log into GNOME * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` * Log out, and log in to MATE. * Run `$ mate-display-properties`, just click on the "Apply" button (you don't have to click on the "Keep this configuration" button that pop-ups in the dialoge-box), it will generate "$HOME/.config/monitors.xml" * Log out from MATE. From the display manager, log into GNOME. * As you can see, the screen resolution (1600x900 configured in MATE) not used by GNOME (https://github.com/mate-desktop/mate-control-center/assets/6416073/1b978bd7-22dd-4b42-a5b5-d32ec2d42f21), instead a fallback resolution is used. * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) move "$HOME/.config/monitors.xml" (that was generated by MATE) to "$HOME/.config/monitors-v1-backup.xml" 2) generate a new "$HOME/.config/monitors.xml" 3) Change the screen resolution directly (https://github.com/mate-desktop/mate-control-center/assets/6416073/6a841086-6936-4a21-9d43-ca1a605a9806). Close the window. *
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
** Description changed: - * monitors.xml in Ubuntu 22.04, and 23.04 (GNOME) is starting with ``, while in Ubuntu MATE 22.04, and 23.04 it is starting with `` - * The monitors.xml file name is defined here for MATE: https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and here for GNOME: https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008 + * "$HOME/.config/monitors.xml" is not installed by default in Ubuntu during the installation at this writing, you have to generate it by running the GUI preferences `$ gnome-control-center display` for GNOME, and `$ mate-display-properties` for MATE. + * Both GNOME and MATE can be run on the same distro, which causes compatibility issues with monitors.xml: monitors.xml in Ubuntu 22.04, and 23.04 (GNOME) is starting with ``, while in Ubuntu MATE 22.04, and 23.04 it is starting with `` + * The monitors.xml file name for MATE is defined at https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and for GNOME it is defined at https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008. Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour monitors.xml in Ubuntu 23.04, and 22.04: ``` 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60.000 ``` monitors.xml in Ubuntu 22.04 (with ubuntu-mate-desktop installed), or 23.04 (with ubuntu-mate-desktop installed): ``` 0 0 yes Virtual-1 ??? 0x 0x 1600 900 60.000 0 0 1 yes Virtual-1 unknown unknown unknown 1280 800 59.810 ``` monitors.xml in Ubuntu MATE 22.04, Ubuntu MATE 23.04, ubuntu-mate-desktop from Ubuntu 22.04, or ubuntu-mate-desktop from Ubuntu 23.04: ``` no ??? 0x 0x 1600 900 60 0 0 normal no no yes ``` Steps to reproduce the behaviour - Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: - * GNOME via `$ gnome-control-center display` - * MATE via `$ mate-display-properties` - - Steps I used to reproduce the issue in Ubuntu 22.04 (as a virtual machine): + Steps I used to reproduce the issue in Ubuntu 22.04 with ubuntu-mate-desktop installed: * Log into GNOME * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` - * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) generate "$HOME/.config/monitors.xml", 2) [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56](/uploads/dc4ba73ddfae955fcafa948e3a164581/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56.png). Close the window. + * Log out, and log in to MATE. + * Run `$ mate-display-properties`, just click on the "Apply" button (you don't have to click on the "Keep this configuration" button that pop-ups in the dialoge-box), it will generate "$HOME/.config/monitors.xml" + * Log out from MATE. From the display manager, log into GNOME. + * As you can see, the screen resolution (1600x900 configured in MATE) not used by GNOME (https://github.com/mate-desktop/mate-control-center/assets/6416073/1b978bd7-22dd-4b42-a5b5-d32ec2d42f21), instead a fallback resolution is used. + * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) move "$HOME/.config/monitors.xml" (that was generated by MATE) to "$HOME/.config/monitors-v1-backup.xml" 2) generate a new "$HOME/.config/monitors.xml" 3) Change the screen resolution directly (https://github.com/mate-desktop/mate-control-center/assets/6416073/6a841086-6936-4a21-9d43-ca1a605a9806). Close the window. * Log out from GNOME. From the display manager, log into
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
** Description changed: * monitors.xml in Ubuntu 22.04, and 23.04 (GNOME) is starting with ``, while in Ubuntu MATE 22.04, and 23.04 it is starting with `` * The monitors.xml file name is defined here for MATE: https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and here for GNOME: https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008 Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour monitors.xml in Ubuntu 23.04, and 22.04: ``` 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60.000 ``` - monitors.xml in Ubuntu MATE 22.04, and 23.04: + monitors.xml in Ubuntu 22.04 (with ubuntu-mate-desktop installed), or + 23.04 (with ubuntu-mate-desktop installed): + + ``` + + + + + 0 + 0 + yes + + + Virtual-1 + ??? + 0x + 0x + + + 1600 + 900 + 60.000 + + + + + + + 0 + 0 + 1 + yes + + + Virtual-1 + unknown + unknown + unknown + + + 1280 + 800 + 59.810 + + + + + + ``` + + monitors.xml in Ubuntu MATE 22.04, Ubuntu MATE 23.04, ubuntu-mate-desktop from Ubuntu 22.04, or ubuntu-mate-desktop from Ubuntu 23.04: ``` - - no - - ??? - 0x - 0x - 1600 - 900 - 60 - 0 - 0 - normal - no - no - yes - - - - - - - - + + no + + ??? + 0x + 0x + 1600 + 900 + 60 + 0 + 0 + normal + no + no + yes + + + + + + + + ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` Steps I used to reproduce the issue in Ubuntu 22.04 (as a virtual machine): * Log into GNOME * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) generate "$HOME/.config/monitors.xml", 2) [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56](/uploads/dc4ba73ddfae955fcafa948e3a164581/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56.png). Close the window. * Log out from GNOME. From the display manager, log into MATE. * As you can see, the [screen resolution (1600x900 configured in GNOME) not used by MATE](https://github.com/mate-desktop/mate-control-center/assets/6416073/adffa08e-cf08-499d-8dc3-9e7800e4d7e9), instead a fallback resolution is used. * Run `$ mate-display-properties`, just click on the "Apply" button (you don't have to click on the "Keep this configuration" button that pop-ups in the dialoge-box), it will overwrite "$HOME/.config/monitors.xml" * Log out from MATE. From the display manager, log into GNOME. * As you can see, [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11](/uploads/013b2b1abf582caf7e6c4c70733ea5ac/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11.png), instead a fallback resolution is used. ## Links to bug reports [Feature request] mate-display-properties: Please upgrade monitors.xml from to - https://bugs.launchpad.net/ubuntu/+bug/2028818 GNOME https://gitlab.gnome.org/GNOME/mutter/-/issues/2919 MATE https://github.com/mate-desktop/mate-control-center/issues/712 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 01:24:22 2023 InstallationDate: Installed on 2023-04-17 (97
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
** Description changed: * monitors.xml in Ubuntu 22.04, and 23.04 (GNOME) is starting with ``, while in Ubuntu MATE 22.04, and 23.04 it is starting with `` * The monitors.xml file name is defined here for MATE: https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and here for GNOME: https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008 Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour - monitors.xml in Ubuntu 23.04: + monitors.xml in Ubuntu 23.04, and 22.04: ``` 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60.000 - - ``` - - monitors.xml in Ubuntu 22.04: - - ``` - - - - - 0 - 0 - yes - - - Virtual-1 - ??? - 0x - 0x - - - 1600 - 900 - 60 - - - - - - - 0 - 0 - 1 - yes - - - Virtual-1 - unknown - unknown - unknown - - - 1600 - 900 - 60 - - - - ``` monitors.xml in Ubuntu MATE 22.04, and 23.04: ``` no ??? 0x 0x 1600 900 60 0 0 normal no no yes ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` Steps I used to reproduce the issue in Ubuntu 22.04 (as a virtual machine): * Log into GNOME * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) generate "$HOME/.config/monitors.xml", 2) [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56](/uploads/dc4ba73ddfae955fcafa948e3a164581/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56.png). Close the window. * Log out from GNOME. From the display manager, log into MATE. * As you can see, the [screen resolution (1600x900 configured in GNOME) not used by MATE](https://github.com/mate-desktop/mate-control-center/assets/6416073/adffa08e-cf08-499d-8dc3-9e7800e4d7e9), instead a fallback resolution is used. * Run `$ mate-display-properties`, just click on the "Apply" button (you don't have to click on the "Keep this configuration" button that pop-ups in the dialoge-box), it will overwrite "$HOME/.config/monitors.xml" * Log out from MATE. From the display manager, log into GNOME. * As you can see, [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11](/uploads/013b2b1abf582caf7e6c4c70733ea5ac/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11.png), instead a fallback resolution is used. ## Links to bug reports [Feature request] mate-display-properties: Please upgrade monitors.xml from to - https://bugs.launchpad.net/ubuntu/+bug/2028818 GNOME https://gitlab.gnome.org/GNOME/mutter/-/issues/2919 MATE https://github.com/mate-desktop/mate-control-center/issues/712 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 01:24:22 2023 InstallationDate: Installed on 2023-04-17 (97 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2028469 Title: Use less generic name for monitors.xml to avoid clashing with other desktops To manage notifications about this
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
** Description changed: - * monitors.xml in Ubuntu 22.04, and 23.04 (both version are using GNOME) is starting with ``, while in Ubuntu MATE 22.04, and 23.04 it is starting with `` + * monitors.xml in Ubuntu 22.04, and 23.04 (GNOME) is starting with ``, while in Ubuntu MATE 22.04, and 23.04 it is starting with `` * The monitors.xml file name is defined here for MATE: https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and here for GNOME: https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008 Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour GNOME's monitors.xml: ``` 0 0 yes Virtual-1 ??? 0x 0x 1600 900 60 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60 ``` monitors.xml in Ubuntu MATE 22.04, and 23.04: ``` no ??? 0x 0x 1600 900 60 0 0 normal no no yes ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` Steps I used to reproduce the issue in Ubuntu 22.04 (as a virtual machine): * Log into GNOME * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) generate "$HOME/.config/monitors.xml", 2) [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56](/uploads/dc4ba73ddfae955fcafa948e3a164581/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56.png). Close the window. * Log out from GNOME. From the display manager, log into MATE. * As you can see, the [screen resolution (1600x900 configured in GNOME) not used by MATE](https://github.com/mate-desktop/mate-control-center/assets/6416073/adffa08e-cf08-499d-8dc3-9e7800e4d7e9), instead a fallback resolution is used. * Run `$ mate-display-properties`, just click on the "Apply" button (you don't have to click on the "Keep this configuration" button that pop-ups in the dialoge-box), it will overwrite "$HOME/.config/monitors.xml" * Log out from MATE. From the display manager, log into GNOME. * As you can see, [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11](/uploads/013b2b1abf582caf7e6c4c70733ea5ac/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11.png), instead a fallback resolution is used. ## Links to bug reports [Feature request] mate-display-properties: Please upgrade monitors.xml from to - https://bugs.launchpad.net/ubuntu/+bug/2028818 GNOME https://gitlab.gnome.org/GNOME/mutter/-/issues/2919 MATE https://github.com/mate-desktop/mate-control-center/issues/712 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 01:24:22 2023 InstallationDate: Installed on 2023-04-17 (97 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: * monitors.xml in Ubuntu 22.04, and 23.04 (GNOME) is starting with ``, while in Ubuntu MATE 22.04, and 23.04 it is starting with `` * The monitors.xml file name is defined here for MATE: https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and here for GNOME: https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008 Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
** Description changed: - * GNOME's monitors.xml is starting with , and that MATE's monitors.xml is starting with + * monitors.xml in Ubuntu 22.04, and 23.04 (both version are using GNOME) is starting with ``, while in Ubuntu MATE 22.04, and 23.04 it is starting with `` * The monitors.xml file name is defined here for MATE: https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and here for GNOME: https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008 Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour GNOME's monitors.xml: ``` 0 0 yes Virtual-1 ??? 0x 0x 1600 900 60 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60 ``` monitors.xml in Ubuntu MATE 22.04, and 23.04: ``` no ??? 0x 0x 1600 900 60 0 0 normal no no yes ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` Steps I used to reproduce the issue in Ubuntu 22.04 (as a virtual machine): * Log into GNOME * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) generate "$HOME/.config/monitors.xml", 2) [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56](/uploads/dc4ba73ddfae955fcafa948e3a164581/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56.png). Close the window. * Log out from GNOME. From the display manager, log into MATE. * As you can see, the [screen resolution (1600x900 configured in GNOME) not used by MATE](https://github.com/mate-desktop/mate-control-center/assets/6416073/adffa08e-cf08-499d-8dc3-9e7800e4d7e9), instead a fallback resolution is used. * Run `$ mate-display-properties`, just click on the "Apply" button (you don't have to click on the "Keep this configuration" button that pop-ups in the dialoge-box), it will overwrite "$HOME/.config/monitors.xml" * Log out from MATE. From the display manager, log into GNOME. * As you can see, [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11](/uploads/013b2b1abf582caf7e6c4c70733ea5ac/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11.png), instead a fallback resolution is used. ## Links to bug reports [Feature request] mate-display-properties: Please upgrade monitors.xml from to - https://bugs.launchpad.net/ubuntu/+bug/2028818 GNOME https://gitlab.gnome.org/GNOME/mutter/-/issues/2919 MATE https://github.com/mate-desktop/mate-control-center/issues/712 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 01:24:22 2023 InstallationDate: Installed on 2023-04-17 (97 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2028469 Title: Use less generic name for monitors.xml to avoid clashing with other desktops To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2028469/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
I just filed: [Feature request] mate-display-properties: Please upgrade monitors.xml from to - https://bugs.launchpad.net/ubuntu/+bug/2028818 -- I pointed out that there will certainly be times when GNOME and MATE will not be able to use the same version of monitors.xml in the future. ** Description changed: * GNOME's monitors.xml is starting with , and that MATE's monitors.xml is starting with * The monitors.xml file name is defined here for MATE: https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and here for GNOME: https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008 - Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour GNOME's monitors.xml: ``` 0 0 yes Virtual-1 ??? 0x 0x 1600 900 60 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60 ``` MATE's monitors.xml: ``` no ??? 0x 0x 1600 900 60 0 0 normal no no yes ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` Steps I used to reproduce the issue in Ubuntu 22.04 (as a virtual machine): * Log into GNOME * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) generate "$HOME/.config/monitors.xml", 2) [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56](/uploads/dc4ba73ddfae955fcafa948e3a164581/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56.png). Close the window. * Log out from GNOME. From the display manager, log into MATE. * As you can see, the [screen resolution (1600x900 configured in GNOME) not used by MATE](https://github.com/mate-desktop/mate-control-center/assets/6416073/adffa08e-cf08-499d-8dc3-9e7800e4d7e9), instead a fallback resolution is used. * Run `$ mate-display-properties`, just click on the "Apply" button (you don't have to click on the "Keep this configuration" button that pop-ups in the dialoge-box), it will overwrite "$HOME/.config/monitors.xml" * Log out from MATE. From the display manager, log into GNOME. * As you can see, [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11](/uploads/013b2b1abf582caf7e6c4c70733ea5ac/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11.png), instead a fallback resolution is used. ## Links to bug reports + [Feature request] mate-display-properties: Please upgrade monitors.xml from to - https://bugs.launchpad.net/ubuntu/+bug/2028818 GNOME https://gitlab.gnome.org/GNOME/mutter/-/issues/2919 MATE https://github.com/mate-desktop/mate-control-center/issues/712 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 01:24:22 2023 InstallationDate: Installed on 2023-04-17 (97 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: * GNOME's monitors.xml is starting with , and that MATE's monitors.xml is starting with * The monitors.xml file name is defined here for MATE: https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and here for GNOME: https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008 Expected behaviour cinnamon is using a dedicated name,
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
** Description changed: + * GNOME's monitors.xml is starting with , and that MATE's monitors.xml is starting with + * The monitors.xml file name is defined here for MATE: https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and here for GNOME: https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008 + + Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour - Disclaimer: GNOME's monitors.xml is starting with , and that MATE's monitors.xml is starting with - GNOME's monitors.xml: ``` 0 0 yes Virtual-1 ??? 0x 0x 1600 900 60 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60 ``` MATE's monitors.xml: ``` no ??? 0x 0x 1600 900 60 0 0 normal no no yes ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` Steps I used to reproduce the issue in Ubuntu 22.04 (as a virtual machine): * Log into GNOME * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) generate "$HOME/.config/monitors.xml", 2) [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56](/uploads/dc4ba73ddfae955fcafa948e3a164581/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56.png). Close the window. * Log out from GNOME. From the display manager, log into MATE. * As you can see, the [screen resolution (1600x900 configured in GNOME) not used by MATE](https://github.com/mate-desktop/mate-control-center/assets/6416073/adffa08e-cf08-499d-8dc3-9e7800e4d7e9), instead a fallback resolution is used. * Run `$ mate-display-properties`, just click on the "Apply" button (you don't have to click on the "Keep this configuration" button that pop-ups in the dialoge-box), it will overwrite "$HOME/.config/monitors.xml" * Log out from MATE. From the display manager, log into GNOME. * As you can see, [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11](/uploads/013b2b1abf582caf7e6c4c70733ea5ac/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11.png), instead a fallback resolution is used. ## Links to bug reports GNOME https://gitlab.gnome.org/GNOME/mutter/-/issues/2919 MATE https://github.com/mate-desktop/mate-control-center/issues/712 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 01:24:22 2023 InstallationDate: Installed on 2023-04-17 (97 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2028469 Title: Use less generic name for monitors.xml to avoid clashing with other desktops To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2028469/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
** Description changed: Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour + Disclaimer: GNOME's monitors.xml is starting with , and that MATE's monitors.xml is starting with + GNOME's monitors.xml: ``` 0 0 yes Virtual-1 ??? 0x 0x 1600 900 60 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60 ``` MATE's monitors.xml: ``` no ??? 0x 0x 1600 900 60 0 0 normal no no yes ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` Steps I used to reproduce the issue in Ubuntu 22.04 (as a virtual machine): * Log into GNOME * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) generate "$HOME/.config/monitors.xml", 2) [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56](/uploads/dc4ba73ddfae955fcafa948e3a164581/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56.png). Close the window. * Log out from GNOME. From the display manager, log into MATE. * As you can see, the [screen resolution (1600x900 configured in GNOME) not used by MATE](https://github.com/mate-desktop/mate-control-center/assets/6416073/adffa08e-cf08-499d-8dc3-9e7800e4d7e9), instead a fallback resolution is used. * Run `$ mate-display-properties`, just click on the "Apply" button (you don't have to click on the "Keep this configuration" button that pop-ups in the dialoge-box), it will overwrite "$HOME/.config/monitors.xml" * Log out from MATE. From the display manager, log into GNOME. * As you can see, [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11](/uploads/013b2b1abf582caf7e6c4c70733ea5ac/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11.png), instead a fallback resolution is used. ## Links to bug reports GNOME https://gitlab.gnome.org/GNOME/mutter/-/issues/2919 MATE https://github.com/mate-desktop/mate-control-center/issues/712 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 01:24:22 2023 InstallationDate: Installed on 2023-04-17 (97 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2028469 Title: Use less generic name for monitors.xml to avoid clashing with other desktops To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2028469/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2028469 Title: Use less generic name for monitors.xml to avoid clashing with other desktops To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2028469/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
> As mentioned in the other bug, I think that's more a bug in MATE if it has become incompatible. Oh, interesting! Can you please humbly ask if this is the cause in the MATE entry page that I filed for this issue: https://github.com/mate-desktop/mate-control-center/issues/712 ? But please mention that GNOME's monitors.xml is starting with , and that MATE's monitors.xml is starting with ** Bug watch added: github.com/mate-desktop/mate-control-center/issues #712 https://github.com/mate-desktop/mate-control-center/issues/712 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2028469 Title: Use less generic name for monitors.xml to avoid clashing with other desktops To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2028469/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
> I've always thought the generic name is useful because it potentially allows multiple desktop environments to share a single layout... Assuming that didn't break any of them. monitors.xml generated by GNOME is incompatible with monitors.xml generated by MATE (see file layouts in the top post), which is indicated in the title of this issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2028469 Title: Use less generic name for monitors.xml to avoid clashing with other desktops To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2028469/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
** Description changed: Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour GNOME's monitors.xml: ``` 0 0 yes Virtual-1 ??? 0x 0x 1600 900 60 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60 ``` MATE's monitors.xml: ``` no ??? 0x 0x 1600 900 60 0 0 normal no no yes ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` The screen resolution is used directly (no need to log out). However, when you switch to the other desktop environment, the screen resolution is reset because their setup in monitors.xml is different. ## Links to bug reports - GNOME https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2579 + GNOME https://gitlab.gnome.org/GNOME/mutter/-/issues/2919 MATE https://github.com/mate-desktop/mate-control-center/issues/712 - ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 01:24:22 2023 InstallationDate: Installed on 2023-04-17 (97 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour GNOME's monitors.xml: ``` 0 0 yes Virtual-1 ??? 0x 0x 1600 900 60 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60 ``` MATE's monitors.xml: ``` no ??? 0x 0x 1600 900 60 0 0 normal no no yes ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` - The screen resolution is used directly (no need to log out). However, - when you switch to the other desktop environment, the screen resolution - is reset because their setup in monitors.xml is different. + Steps I used to reproduce the issue in Ubuntu 22.04 (as a virtual machine): + * Log into GNOME + * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` + * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) generate "$HOME/.config/monitors.xml", 2)
[Bug 2026886] Re: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2
awesome, thank you. I will keep the flag set :-) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2026886 Title: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2026886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
** Summary changed: - monitors.xml is incompatible with MATE (and vice versa) + Use less generic name for monitors.xml to avoid clashing with other desktops -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2028469 Title: Use less generic name for monitors.xml to avoid clashing with other desktops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2028469/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026886] Re: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2
Hi Daniel, sorry for the delayed response. MUTTER_DEBUG_SEND_KMS_MODIFIERS=1 fixes the issue. I can now use chrome with hardware acceleration enabled without rendering problems. Is there any long-term downside with leaving this flag set? Or should I drop the environment entry when upstream has fixes? Thanks again for your help :-) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2026886 Title: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2026886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028469] [NEW] monitors.xml is incompatible with MATE (and vice versa)
Public bug reported: Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour GNOME's monitors.xml: ``` 0 0 yes Virtual-1 ??? 0x 0x 1600 900 60 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60 ``` MATE's monitors.xml: ``` no ??? 0x 0x 1600 900 60 0 0 normal no no yes ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` The screen resolution is used directly (no need to log out). However, when you switch to the other desktop environment, the screen resolution is reset because their setup in monitors.xml is different. ## Links to bug reports GNOME https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2579 MATE https://github.com/mate-desktop/mate-control-center/issues/712 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 01:24:22 2023 InstallationDate: Installed on 2023-04-17 (97 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Description changed: Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour GNOME's monitors.xml: ``` - - - - 0 - 0 - yes - - - Virtual-1 - ??? - 0x - 0x - - - 1600 - 900 - 60 - - - - - - - 0 - 0 - 1 - yes - - - Virtual-1 - unknown - unknown - unknown - - - 1600 - 900 - 60 - - - - + + + + 0 + 0 + yes + + + Virtual-1 + ??? + 0x + 0x + + + 1600 + 900 + 60 + + + + + + + 0 + 0 + 1 + yes + + + Virtual-1 + unknown + unknown + unknown + + + 1600 + 900 + 60 + + + + ``` MATE's monitors.xml: ``` - - no - - ??? - 0x - 0x - 1600 - 900 - 60 - 0 - 0 - normal - no - no - yes - - - - - - - - + + no + + ??? + 0x + 0x + 1600 + 900 + 60 + 0 + 0 + normal + no + no + yes + + + + + + + + ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` The screen resolution is used directly (no need to log out). However, when you switch to the other desktop environment,
[Bug 2028301] Re: Feature request: Use dark text on a bright background
See also this Trisquel issue: mate-terminal: Proposed theme profile for improved ergonomics - https://gitlab.trisquel.org/trisquel/package- helpers/-/issues/95 ** Bug watch added: gitlab.trisquel.org/trisquel/package-helpers/-/issues #95 https://gitlab.trisquel.org/trisquel/package-helpers/-/issues/95 ** Description changed: * The default background color in Ubuntu MATE 22.04 is white. * The default background color in Ubuntu 22.04, and 23.04, is tyrian purple-ish (very dark). A dark background will cause eye-straining on day time use. This will turn off the default theme and use a light-purple background instead: profile_key=$(gsettings get org.gnome.Terminal.ProfilesList default | sed -e "s/'//g" | tr -d "\n") gsettings set org.gnome.Terminal.Legacy.Profile:/org/gnome/terminal/legacy/profiles:/:$profile_key/ use-theme-colors false gsettings set org.gnome.Terminal.Legacy.Profile:/org/gnome/terminal/legacy/profiles:/:$profile_key/ background-color "'rgb(255,224,255)'" + + + See also: + * Trisquel issue: mate-terminal: Proposed theme profile for improved ergonomics - https://gitlab.trisquel.org/trisquel/package-helpers/-/issues/95 + * mate-terminal (unpackaged): [Feature request]: Use bright background #441 - https://github.com/mate-desktop/mate-terminal/issues/441 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-terminal 3.48.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jul 20 17:06:24 2023 InstallationDate: Installed on 2023-04-23 (87 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2028301 Title: Feature request: Use dark text on a bright background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2028301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028301] [NEW] Feature request: Use dark text on a bright background
Public bug reported: * The default background color in Ubuntu MATE 22.04 is white. * The default background color in Ubuntu 22.04, and 23.04, is tyrian purple-ish (very dark). A dark background will cause eye-straining on day time use. This will turn off the default theme and use a light-purple background instead: profile_key=$(gsettings get org.gnome.Terminal.ProfilesList default | sed -e "s/'//g" | tr -d "\n") gsettings set org.gnome.Terminal.Legacy.Profile:/org/gnome/terminal/legacy/profiles:/:$profile_key/ use-theme-colors false gsettings set org.gnome.Terminal.Legacy.Profile:/org/gnome/terminal/legacy/profiles:/:$profile_key/ background-color "'rgb(255,224,255)'" ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-terminal 3.48.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jul 20 17:06:24 2023 InstallationDate: Installed on 2023-04-23 (87 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2028301 Title: Feature request: Use dark text on a bright background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2028301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026886] Re: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2
Daniel van Vught wrote: > I'm still struggling to understand how gnome-shell is triggering the > corruption. Maybe try switching between 42.5 and 42.9 a few times again and > verify in both cases the mutter packages remain 42.9. I tried everything again from the beginning, and I _can_ reproduce this with mutter 42.9 and gnome-shell 42.0. So I think you're right - this is probably a mutter bug. When I was testing initially, I relied on the built in chrome 'relaunch' button, which does not give a full clean restart. I have to fully restart the application for the bug to manifest (after re-enabling hardware acceleration). I tried to downgrade mutter to confirm that this package was the problem, but I can't go all the way back to v42.0 without apt trying to remove a whole bunch of critical packages. Unfortunately, I couldn't find v42.5 in my local cache or the repositories, either, to test with. Maybe you have a better suggestion that I could do to try and isolate the offending package? > Also can you find any other app affected? I haven't been able to reproduce this with any other applications, though I don't really use anything that stresses the GPU (likes games and such). I could look this weekend for something to try -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026886 Title: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026886] Re: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2
Daniel van Vugt wrote: > On the slight chance this is related to another AMD GPU issue I've heard > about in 42.9, please try adding this to /etc/environment: > MUTTER_DEBUG_USE_KMS_MODIFIERS=0 This didn't help, unfortunately. What I did: - Re-enabled hardware acceleration in chrome - Confirmed rendering is broken - Added MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment - Rebooted - Confirmed rendering is still broken in chrome -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026886 Title: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026886] Re: google chrome hardware acceleration broken on 42.9-0ubuntu2
I was a bit premature with my last comment. If I restart chrome after re-enabling hardware acceleration, rendering breaks again. So the overall behavior looks like: - Start at v42.0 of gnome-shell and gnome-shell-common - Upgrade to v42.9 of gnome-shell and gnome-shell-common - Note strange rendering in chrome - Logout/login - Note strange rendering in chrome persists - Reboot - Note strange rendering in chrome persists - Disable hardware acceleration in chrome - Click 'relaunch' - Note rendering in chrome is now fixed With some additional strange behavior - hardware acceleration appears to work temporarily after being re-enabled: - Re-enable hardware acceleration in chrome - Click 'relaunch' - Note rendering in chrome still works - Manually close chrome - Open chrome - Note rendering in chrome is broken again -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026886 Title: google chrome hardware acceleration broken on 42.9-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026886] Re: google chrome hardware acceleration broken on 42.9-0ubuntu2
Thank you for responding so quickly :-) Danial van Vugt wrote: > When reporting bugs in the future please use apport by using 'ubuntu-bug' and > the name of the package affected. Can do :-) > Or if you prefer to collect info manually, please run these commands while the problem is happening [...] and attach the resulting text files here. Done. Let me know if I can provide anything else > Was it only downgrading gnome-shell that helped or were you actually > downgrading the mutter packages too? I only downgraded gnome-shell and gnome-shell-common. I left mutter as it was. Something else strange that I noticed: if I disable hardware acceleration, then enable it again, chrome appears to work fine. So the behavior I'm seeing looks like: - Start at v42.0 of gnome-shell and gnome-shell-common - Upgrade to v42.9 of gnome-shell and gnome-shell-common - Note strange rendering in chrome - Logout/login - Note strange rendering in chrome persists - Reboot - Note strange rendering in chrome persists - Disable hardware acceleration in chrome - Note rendering in chrome is now fixed - Enable hardware acceleration in chrome - Note rendering in chrome still works -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026886 Title: google chrome hardware acceleration broken on 42.9-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026886] Re: google chrome hardware acceleration broken on 42.9-0ubuntu2
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026886/+attachment/5685720/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026886 Title: google chrome hardware acceleration broken on 42.9-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026886] Re: google chrome hardware acceleration broken on 42.9-0ubuntu2
** Attachment added: "lscpu.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026886/+attachment/5685719/+files/lscpu.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026886 Title: google chrome hardware acceleration broken on 42.9-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026886] Re: google chrome hardware acceleration broken on 42.9-0ubuntu2
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026886/+attachment/5685718/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026886 Title: google chrome hardware acceleration broken on 42.9-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026886] Re: google chrome hardware acceleration broken on 42.9-0ubuntu2
** Attachment added: "packages.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026886/+attachment/5685717/+files/packages.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026886 Title: google chrome hardware acceleration broken on 42.9-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026886] Re: google chrome hardware acceleration broken on 42.9-0ubuntu2
** Description changed: This morning, I upgraded gnome-shell and gnome-shell-common from 42.5-0ubuntu1 to 42.9-0ubuntu2, and I noticed that chrome no longer renders properly. Notice the missing image header on the Ubuntu website and the garbled right click menu here: https://i.imgur.com/BPnqfVG.png - I downgraded to gnome-shell and gnome-shell-common version + I downgraded gnome-shell and gnome-shell-common version to 42.0-2ubuntu1, restarted gnome, and the rendering issues went away: https://i.imgur.com/CzEPgqY.png I upgraded gnome-shell and gnome-shell-common again to the latest and the rendering issues came back. Going to chrome://settings/system and disabling hardware acceleration fixes the rendering issues (but now I don't have hardware acceleration). --- $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 42.9-0ubuntu2 Candidate: 42.9-0ubuntu2 Version table: *** 42.9-0ubuntu2 500 (phased 40%) 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ** Description changed: This morning, I upgraded gnome-shell and gnome-shell-common from 42.5-0ubuntu1 to 42.9-0ubuntu2, and I noticed that chrome no longer renders properly. Notice the missing image header on the Ubuntu website and the garbled right click menu here: https://i.imgur.com/BPnqfVG.png I downgraded gnome-shell and gnome-shell-common version to 42.0-2ubuntu1, restarted gnome, and the rendering issues went away: https://i.imgur.com/CzEPgqY.png I upgraded gnome-shell and gnome-shell-common again to the latest and the rendering issues came back. Going to chrome://settings/system and disabling hardware acceleration fixes the rendering issues (but now I don't have hardware acceleration). + I'm running the latest stable version of chrome: 114.0.5735.198 --- $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 42.9-0ubuntu2 Candidate: 42.9-0ubuntu2 Version table: *** 42.9-0ubuntu2 500 (phased 40%) 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ** Description changed: This morning, I upgraded gnome-shell and gnome-shell-common from 42.5-0ubuntu1 to 42.9-0ubuntu2, and I noticed that chrome no longer renders properly. Notice the missing image header on the Ubuntu website and the garbled right click menu here: https://i.imgur.com/BPnqfVG.png I downgraded gnome-shell and gnome-shell-common version to 42.0-2ubuntu1, restarted gnome, and the rendering issues went away: https://i.imgur.com/CzEPgqY.png I upgraded gnome-shell and gnome-shell-common again to the latest and the rendering issues came back. Going to chrome://settings/system and disabling hardware acceleration fixes the rendering issues (but now I don't have hardware acceleration). I'm running the latest stable version of chrome: 114.0.5735.198 + --- $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 42.9-0ubuntu2 Candidate: 42.9-0ubuntu2 Version table: *** 42.9-0ubuntu2 500 (phased 40%) 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ** Description changed: This morning, I upgraded gnome-shell and gnome-shell-common from 42.5-0ubuntu1 to 42.9-0ubuntu2, and I noticed that chrome no longer renders properly. Notice the missing image header on the Ubuntu website and the garbled right click menu here: https://i.imgur.com/BPnqfVG.png I downgraded gnome-shell and gnome-shell-common version to 42.0-2ubuntu1, restarted gnome, and the rendering issues went away: https://i.imgur.com/CzEPgqY.png I upgraded gnome-shell and gnome-shell-common again to the latest and the rendering issues came back. Going to chrome://settings/system and disabling hardware acceleration fixes the rendering issues (but now I don't have hardware acceleration). - I'm running the latest stable version of chrome: 114.0.5735.198 + I'm running the latest stable version of chrome which was released a few + weeks ago: 114.0.5735.198 --- $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 42.9-0ubuntu2 Candidate: 42.9-0ubuntu2 Version table: ***
[Bug 2026886] [NEW] google chrome hardware acceleration broken on 42.9-0ubuntu2
Public bug reported: This morning, I upgraded gnome-shell and gnome-shell-common from 42.5-0ubuntu1 to 42.9-0ubuntu2, and I noticed that chrome no longer renders properly. Notice the missing image header on the Ubuntu website and the garbled right click menu here: https://i.imgur.com/BPnqfVG.png I downgraded to gnome-shell and gnome-shell-common version 42.0-2ubuntu1, restarted gnome, and the rendering issues went away: https://i.imgur.com/CzEPgqY.png I upgraded gnome-shell and gnome-shell-common again to the latest and the rendering issues came back. Going to chrome://settings/system and disabling hardware acceleration fixes the rendering issues (but now I don't have hardware acceleration). --- $ lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 42.9-0ubuntu2 Candidate: 42.9-0ubuntu2 Version table: *** 42.9-0ubuntu2 500 (phased 40%) 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Description changed: This morning, I upgraded gnome-shell and gnome-shell-common from 42.5-0ubuntu1 to 42.9-0ubuntu2, and I noticed that chrome no longer renders properly. Notice the missing image header on the Ubuntu website and the garbled right click menu here: https://i.imgur.com/BPnqfVG.png I downgraded to gnome-shell and gnome-shell-common version 42.0-2ubuntu1, restarted gnome, and the rendering issues went away: https://i.imgur.com/CzEPgqY.png - I upgrade gnome-shell and gnome-shell-common again to the latest and the - rendering issues came back. Going to chrome://settings/system and + I upgraded gnome-shell and gnome-shell-common again to the latest and + the rendering issues came back. Going to chrome://settings/system and disabling hardware acceleration fixes the rendering issues (but now I don't have hardware acceleration). --- $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy gnome-shell gnome-shell: - Installed: 42.9-0ubuntu2 - Candidate: 42.9-0ubuntu2 - Version table: - *** 42.9-0ubuntu2 500 (phased 40%) - 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 42.0-2ubuntu1 500 - 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages + Installed: 42.9-0ubuntu2 + Candidate: 42.9-0ubuntu2 + Version table: + *** 42.9-0ubuntu2 500 (phased 40%) + 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 42.0-2ubuntu1 500 + 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026886 Title: google chrome hardware acceleration broken on 42.9-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2022369] Re: 200% scaling on wayland touchpad feels laggy on X1 Carbon 9th
Tested the 23.04 Wayland session and can confirm that it is better! Feel free to close the bug as this will be fixed with updates / future releases. Thanks for the professional bug handling. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2022369 Title: 200% scaling on wayland touchpad feels laggy on X1 Carbon 9th To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/2022369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2022369] Re: 200% scaling on wayland touchpad feels laggy on X1 Carbon 9th
Yes runs on wayland. Libinput 1.23.0 Mutter 44.2 It is hard to actually objectively judge this as stutter/lag is very subjective. Though Fedora feels a lot less fluid (i.e. the cursor doesn't seem to lag a few frames). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2022369 Title: 200% scaling on wayland touchpad feels laggy on X1 Carbon 9th To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/2022369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2022369] Re: 200% scaling on wayland touchpad feels laggy on X1 Carbon 9th
Trying to pinpoint where the problem can be I found that the problem is not present in fedora with the exact same set up. I think there is something in Mutter or Gnome that is different in Ubuntu that let's this bug appear. Using Fedora fixes the issue for me but I thought I'd post it here for future reference. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2022369 Title: 200% scaling on wayland touchpad feels laggy on X1 Carbon 9th To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/2022369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2022369] Re: 200% scaling on wayland touchpad feels laggy on X1 Carbon 9th
I can confirm that using Kubuntu with Wayland as well as X11 session the issue is not present. Hence, I believe this is a Gnome / Mutter issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2022369 Title: 200% scaling on wayland touchpad feels laggy on X1 Carbon 9th To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/2022369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2022369] Re: 200% scaling on wayland touchpad feels laggy on X1 Carbon 9th
Created upstream bug: https://gitlab.freedesktop.org/libinput/libinput/-/issues/907 ** Bug watch added: gitlab.freedesktop.org/libinput/libinput/-/issues #907 https://gitlab.freedesktop.org/libinput/libinput/-/issues/907 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2022369 Title: 200% scaling on wayland touchpad feels laggy on X1 Carbon 9th To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/2022369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2022369] Re: 200% scaling on wayland touchpad feels laggy on X1 Carbon 9th
This is very subjective and I could be wrong. Upon disabling the extensions the lag was still present. With a USB mouse the lag is not present or at least not as noticable. Interestingly if I switch to 1080p the issue dissapears. I think that subjectively the default mouse acceleration for 4k with 200% scaling should behave the same as 1080p with 100% scaling which is not the case (though this might be debatable / there might be good reasons why this is not the case). Will report this upstream. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2022369 Title: 200% scaling on wayland touchpad feels laggy on X1 Carbon 9th To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/2022369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2022369] [NEW] 200% scaling on wayland touchpad feels laggy
Public bug reported: I have an X1 carbon 9th gen with a 4k screen where I use 200% scaling. Unfortunately, the touchpad feels laggy and imprecise when trying to hit click targets. Switching to X11 helps as well as the flat acceleration profile in gnome tweaks. I feel like this is related to how gnome or libinput upscale mouse movement. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 2 16:57:16 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-15 (18 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2022369 Title: 200% scaling on wayland touchpad feels laggy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2022369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983768] Re: Resize: Filesystem enlargement depends of manual partition mounting
** Bug watch added: gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues #292 https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/292 ** Also affects: gnome-disk-utility via https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/292 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1983768 Title: Resize: Filesystem enlargement depends of manual partition mounting To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1983768/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771041] Re: Remove gconf from Ubuntu
ooo-thumbnailer is an abandoned project and is being removed from Debian. Project link: https://launchpad.net/ooo-thumbnailer ** Changed in: ooo-thumbnailer (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1771041 Title: Remove gconf from Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktopnova/+bug/1771041/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1974293]
Restart after Fedora38 upgrade process. reporter: libreport-2.17.9 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=48494ce3d31d44b6bf62d07f4e449f62;i=1423d;b=be2da266a31c463fbc93932abd856f95;m=44db4cc;t=5f9e404d4e539;x=b0edb8d74707a3d2 executable: /usr/bin/gnome-shell cmdline:/usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.Shell@wayland.service rootdir:/ uid:1000 kernel: 6.2.11-300.fc38.x86_64 package:gnome-shell-44.0-4.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: js::gc::Cell::storeBuffer comment:Restart after Fedora38 upgrade process. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1974293 Title: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl() To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1974293/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015704] Re: Gnome Flashback Metacity crashes and logs me out at login. Flashback Compiz runs OK.
The message when logging in to Flashback on Metacity: Oh no! Something has gone wrong. A problem has occurerred and the system can't recover. Please log out and try again. Situation did not change after: from Ubuntu on x Windows: sudo apt reinstall gnome-session-flashback or using Gnome Tweaks 42.beta Reset to defaults -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/2015704 Title: Gnome Flashback Metacity crashes and logs me out at login. Flashback Compiz runs OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/2015704/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015704] [NEW] Gnome Flashback Metacity crashes and logs me out at login. Flashback Compiz runs OK.
Public bug reported: While modifying the Gnome Flashback Metacity panels: I moved the top panel to the left. OK Was changing which applets were shown, removing some, adding some. The panel shifted almost off-screen, then flickered several times. I got a display message that a problem kept happening, Gnome could not continue, and I would be logged out. When I log in again with Flashback Metacity, this happens immediately. Writing this up from Flashback Compiz. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-panel 1:3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Flashback:GNOME Date: Sun Apr 9 23:08:18 2023 GsettingsChanges: b'org.gnome.gnome-panel.layout' b'object-id-list' b"['menu-bar', 'show-desktop', 'workspace-switcher', 'indicator-complete', 'battstat', 'workspace-switcher-0', 'workspace-switcher-1']" b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['top-panel', 'bottom-panel']" InstallationDate: Installed on 2023-04-09 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug flashback jammy metacity ** Attachment added: "gnome panel crash file when running Gnome Flashback Metacity" https://bugs.launchpad.net/bugs/2015704/+attachment/5662524/+files/_usr_bin_gnome-panel.1000.crash -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/2015704 Title: Gnome Flashback Metacity crashes and logs me out at login. Flashback Compiz runs OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/2015704/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 435928] Re: Password works in virtual terminal but not in Gnome screensaver
This bug affects me, and I'm running 20.04. It started a couple of months ago. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/435928 Title: Password works in virtual terminal but not in Gnome screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/435928/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 353356] Re: Gnome screensaver lock always reports "incorrect password"
I have this same issue, started a couple months ago. Everything worked previously. The fixes mentioned above did not help, other than the "switch user and exit X" tip. Must have a regression somewhere because the most recent comment above is 12 years old (I'm running 20.04). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/353356 Title: Gnome screensaver lock always reports "incorrect password" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/353356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1594085] Re: Software app very slow to fully start up
i have also facing the same issue on my client's site: https://www.pikashowhd.com/pikashow-for-pc/ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1594085 Title: Software app very slow to fully start up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1594085/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)
Hello, I experienced this issue as well (EOG 42 on Pop!_OS/Ubuntu 22.04 LTS). I just described it here: https://gitlab.gnome.org/GNOME/eog/-/issues/289 I solved the issue by disabling the auto-generated colour profile in the gnome settings. As I said in the description, I can't assess if this issue is related to some specific monitors (I have a ThinkPad T480 monitor), or it's a common problem. ** Bug watch added: gitlab.gnome.org/GNOME/eog/-/issues #289 https://gitlab.gnome.org/GNOME/eog/-/issues/289 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/938751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1988393] Re: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
Hello! Can you please clarify whether this fix is expected to land in Kinetic or not until Lunar? Thanks! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1988393 Title: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1988393/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1995729] [NEW] JS error crashes Firefox
Public bug reported: I have a ".desktop" file which opens Firefox. I click the file and I see the mouse cursor icon is change to a "loading" icon, but firefox window doesn't appear. The loading icon continues for a few seconds (about 10sec) and then the normal cursor icon is seen. Overall, Firefox doesn't appear. This issue started just recently, in the last week (probably due to an upgrade, I assume). This issue happen only sometimes - meaning, sometimes when I click the ".desktop" file then firefox starts normally, but in some other times then Firefox will not appear. I performed some debug and found out the it is related to the gnome-shell program, or more specifically to the extension "ubuntu-dock". By inspecting the file "/var/log/syslog", whenever the issue happens, then the following error appears in the file (omitted irrelevant data): " gnome-shell[2129]: JS ERROR: TypeError: window is undefined#012activateWindow@resource:///org/gnome/shell/ui/main.js:764:30#012IsolatedOverview@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1546:29#012_create/object[name]@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/utils.js:290:68#012launchNewWindow@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:677:26#012activate@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:615:18#012vfunc_clicked@resource:///org/gnome/shell/ui/appDisplay.js:3168:14 " - Info according to the guidelines: 1) $ lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 2) $ apt-cache policy "gnome-shell-extension-ubuntu-dock" gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.1 Candidate: 72~ubuntu5.22.04.1 Version table: *** 72~ubuntu5.22.04.1 500 500 http://il.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://il.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5 500 500 http://il.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://il.archive.ubuntu.com/ubuntu jammy/main i386 Packages 3) I expected a Firefox window to appear. 4) Instead, a Firefox window doesn't appear. ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1995729 Title: JS error crashes Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1995729/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1992949] [NEW] evinve does not send credentials to cups when printing
Public bug reported: Printing with evince fails as the user credentials are not send to the cups server. Okular is including the credentials, and thus printing works. This is on ubuntu 20.04.5, evince 3.36.10-0ubuntu1 ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Attachment added: "apport.evince.2evb9da8.apport" https://bugs.launchpad.net/bugs/1992949/+attachment/5624051/+files/apport.evince.2evb9da8.apport -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1992949 Title: evinve does not send credentials to cups when printing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1992949/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 175904]
(In reply to Jeremy Nickurak from comment #23) > Created attachment 343829 > Shell script to open a URL strictly in a new firefox tab on the current > workspace > > As a substitute for a fix of this bug, I've worked around it with a shell > script that uses wmctrl to get the ideal behavior. It'll check to see if > there's an existing firefox window open on the current workspace, and if so, > (optionally) focus it, and load a url in a new tab there. If there's no such > window, it'll simply open it in a new window on the current workspace. Thanks for that script, it works very well. This is the behavior I wish Firefox could have out of the box (Reuse-window-in-current-desktop otherwise create-new-in-current-desktop). Much better than jumping to another desktop or opening tabs hidden into another desktop. Any chance for this to happen? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/175904 Title: Firefox window moves to current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/175904/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
I forgot to add SYSTEM INFO: $ cat /proc/version Linux version 5.15.0-46-generic (buildd@lcy02-amd64-115) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022 $ uname -r 5.15.0-46-generic $ hostnamectl | grep Kernel Kernel: Linux 5.15.0-46-generic $ sudo lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 39 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Vendor ID: GenuineIntel Model name:Intel(R) Core(TM) i7-7700T CPU @ 2.90GHz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968887] Re: Save As Dialog Box does not get focus in Ubuntu 22.04
*** This bug is a duplicate of bug 1949340 *** https://bugs.launchpad.net/bugs/1949340 I upgraded to Ubuntu 22.04 yesterday and this bug now affects me. Also, I have Mint Linux (20.3) Cinnamon (5.2.7) on another machine and it's been like that since day 1 of the installation. In both versions of the operating system, when using a program (Firefox, VSCode, and Typora) that generates a Dialogue box, it does not get focused. This means, you can't just type to use the Dialogue box, you have to force focus on the window to use it by clicking it. SYSTEM INFO: $ cat /proc/version Linux version 5.15.0-46-generic (buildd@lcy02-amd64-115) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022 $ uname -r 5.15.0-46-generic $ hostnamectl | grep Kernel Kernel: Linux 5.15.0-46-generic $ sudo lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 39 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Vendor ID: GenuineIntel Model name:Intel(R) Core(TM) i7-7700T CPU @ 2.90GHz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968887 Title: Save As Dialog Box does not get focus in Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968887/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
I upgraded to Ubuntu 22.04 yesterday and this bug now affects me. Also, I have Mint Linux (20.3) Cinnamon (5.2.7) on another machine and its been like that since day 1 of the install. In both versions of the operating system, when using a browser to right- click a file and "save as", the Save As Dialogue box does not get focus. This means, you can't just type the name of the file you want, you have to force focus on the Save As Dialogue box to use it by clicking it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983768] Re: Resize: Filesystem enlargement depends of manual partition mounting
** Description changed: - Package: gnome-disk-utility 3.36.3 - This issue is for gnome-disks, for its Resize function. I've only evaluated this for EXT4 file systems. Works: 1) In a terminal, run $ lsblk 2) Open gnome-disks 3) Select a partition, and click on the "Mount selected" partition button. 4) Click on the "Additional partition options" button, and then on the "Resize..." entry to open the "Resize Volume" window. 5) In the "Resize Volume" window, enlarge the "Current size" and then click on the "Resize" button. 6) In the terminal, run $ lsblk again, and compare the SIZE of the partition with the previously output from lsblk 7) Result: Both the partition and the _file system_ will be enlarged. Does not work: * Run the above steps but skip step 3 (do not mount the partition). * Result: The partition will be enlarged, but not the _file system_ will not be enlarged. Solution: The Resize function should automatically resize the file system, regardless if the partition is mounted or not, like gparted. If it helps, the gparted log says that its using: $ resize2fs -p '/dev/sda2' - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-03 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: gnome-disk-utility 42.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Tags: wayland-session jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1983768 Title: Resize: Filesystem enlargement depends of manual partition mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1983768/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983768] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1983768/+attachment/5608258/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1983768 Title: Resize: Filesystem enlargement depends of manual partition mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1983768/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983768] Re: Resize: Filesystem enlargement depends of manual partition mounting
apport information ** Tags added: apport-collected jammy wayland-session ** Description changed: Package: gnome-disk-utility 3.36.3 This issue is for gnome-disks, for its Resize function. I've only evaluated this for EXT4 file systems. Works: 1) In a terminal, run $ lsblk 2) Open gnome-disks 3) Select a partition, and click on the "Mount selected" partition button. 4) Click on the "Additional partition options" button, and then on the "Resize..." entry to open the "Resize Volume" window. 5) In the "Resize Volume" window, enlarge the "Current size" and then click on the "Resize" button. 6) In the terminal, run $ lsblk again, and compare the SIZE of the partition with the previously output from lsblk 7) Result: Both the partition and the _file system_ will be enlarged. Does not work: * Run the above steps but skip step 3 (do not mount the partition). * Result: The partition will be enlarged, but not the _file system_ will not be enlarged. Solution: The Resize function should automatically resize the file system, regardless if the partition is mounted or not, like gparted. - If it helps, the gparted log says that its using: $ resize2fs -p - '/dev/sda2' + If it helps, the gparted log says that its using: $ resize2fs -p '/dev/sda2' + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-08-03 (8 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) + Package: gnome-disk-utility 42.0-1ubuntu1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 + Tags: wayland-session jammy + Uname: Linux 5.15.0-46-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1983768/+attachment/5608257/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1983768 Title: Resize: Filesystem enlargement depends of manual partition mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1983768/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983768] Re: Resize: Filesystem enlargement depends of manual partition mounting
** Description changed: + Package: gnome-disk-utility 3.36.3 + This issue is for gnome-disks, for its Resize function. I've only evaluated this for EXT4 file systems. Works: 1) In a terminal, run $ lsblk 2) Open gnome-disks 3) Select a partition, and click on the "Mount selected" partition button. 4) Click on the "Additional partition options" button, and then on the "Resize..." entry to open the "Resize Volume" window. 5) In the "Resize Volume" window, enlarge the "Current size" and then click on the "Resize" button. 6) In the terminal, run $ lsblk again, and compare the SIZE of the partition with the previously output from lsblk 7) Result: Both the partition and the _file system_ will be enlarged. Does not work: * Run the above steps but skip step 3 (do not mount the partition). * Result: The partition will be enlarged, but not the _file system_ will not be enlarged. Solution: The Resize function should automatically resize the file system, regardless if the partition is mounted or not, like gparted. If it helps, the gparted log says that its using: $ resize2fs -p '/dev/sda2' -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1983768 Title: Resize: Filesystem enlargement depends of manual partition mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1983768/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983768] [NEW] Resize: Filesystem enlargement depends of manual partition mounting
Public bug reported: This issue is for gnome-disks, for its Resize function. I've only evaluated this for EXT4 file systems. Works: 1) In a terminal, run $ lsblk 2) Open gnome-disks 3) Select a partition, and click on the "Mount selected" partition button. 4) Click on the "Additional partition options" button, and then on the "Resize..." entry to open the "Resize Volume" window. 5) In the "Resize Volume" window, enlarge the "Current size" and then click on the "Resize" button. 6) In the terminal, run $ lsblk again, and compare the SIZE of the partition with the previously output from lsblk 7) Result: Both the partition and the _file system_ will be enlarged. Does not work: * Run the above steps but skip step 3 (do not mount the partition). * Result: The partition will be enlarged, but not the _file system_ will not be enlarged. Solution: The Resize function should automatically resize the file system, regardless if the partition is mounted or not, like gparted. If it helps, the gparted log says that its using: $ resize2fs -p '/dev/sda2' ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1983768 Title: Resize: Filesystem enlargement depends of manual partition mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1983768/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983490] Re: Auto-hide taskbar does not work quite right
Additional info on this issue, how to reproduce. If I have multiple windows open in an app but collapsed onto the task bar, then click on the taskbar app icon and put up one window and then left-click on the icon again to see the other windows and then select another one (left- click), the 2nd window pops up but the task bar hides even if the window is not overlapping. Worst case is if I then minimize all windows I can't get the task bar back unless I either disable auto-hide OR right click on the desktop to bring up a new terminal window and then drag it down into the task bar region and back up again. Just mousing into the hidden task bar region does nothing. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1983490 Title: Auto-hide taskbar does not work quite right To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1983490/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1632211] Re: Evolution constantly loses connection to gmail
Still present in jammy jellyfish evolution 3.44.1-0ubuntu1 Jacob's workaround does not work consistently. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1632211 Title: Evolution constantly loses connection to gmail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1632211/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1980606] Re: gnome-control-centre crashes after enabling "Sharing"
Hi @jbicha, It looks like gnome-remote-desktop may have been uninstalled during the upgrade to jammy due to conflicts from the remmina-next PPA. I had to manually uninstall a few packages and then was able to reinstall gnome- remote-desktop: ``` david@polar:~$ sudo apt install gnome-remote-desktop ... The following packages have unmet dependencies. libfreerdp-server2-2 : Depends: libfreerdp2-2 (= 2.7.0+git202204251304-0+remmina202205020710.r40ee5d3bc.d776065661~ubuntu22.04.1) but 2.7.0+git202204251304-0+remmina202205020710.r40ee5d3bc.da996883ab~ubuntu20.04.1 is to be installed ``` ``` david@polar:~$ sudo apt remove libfreerdp2-2 libvncserver1 libwinpr2-2 ... ``` Following this, I was able to successfully install gnome-remote-desktop. (I know PPAs are unsupported, I'm documenting in case anyone else hits the same issue.) Thank you for looking into this issue. Cheers, David -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1980606 Title: gnome-control-centre crashes after enabling "Sharing" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1980606/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1980606] Re: gnome-control-centre crashes after enabling "Sharing"
Hi @jbicha, It appears we both responded simultaneously. Given that the crash occurs in gnome-control-centre, I'd suggest that the issue lies there - regardless of whether a key exists in a DB, that is the application that faulted and fails to re-open afterwards. Cheers, David -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1980606 Title: gnome-control-centre crashes after enabling "Sharing" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1980606/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1980606] Re: gnome-control-centre crashes after enabling "Sharing"
Hi @jbicha, That would be 42.0-1ubuntu1: ``` $ apt show gsettings-desktop-schemas Package: gsettings-desktop-schemas Version: 42.0-1ubuntu1 Priority: optional ... ``` Cheers, David Edit: that information is available in the file `Dependencies.txt` uploaded with the original issue report. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1980606 Title: gnome-control-centre crashes after enabling "Sharing" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1980606/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1980606] Re: gnome-control-centre crashes after enabling "Sharing"
Looks like the logs that apport-bug uploaded didn't include the syslog. Please find the relevant statements below: ``` david@polar:~$ grep gnome-control-c /var/log/syslog Jul 3 09:30:27 polar gnome-control-c[19523]: Failed to load module "xapp-gtk3-module" Jul 3 10:27:10 polar gnome-control-c[23204]: Failed to load module "xapp-gtk3-module" Jul 3 10:35:51 polar gnome-control-c[23657]: Failed to load module "xapp-gtk3-module" Jul 3 11:26:13 polar gnome-control-c[27128]: Failed to load module "xapp-gtk3-module" Jul 3 20:38:08 polar gnome-control-c[11235]: Failed to load module "xapp-gtk3-module" Jul 3 20:38:11 polar dbus-daemon[1765]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.132' (uid=1000 pid=11235 comm="gnome-control-center " label="unconfined") Jul 3 20:38:11 polar gnome-control-c[11235]: Settings schema 'org.gnome.desktop.remote-desktop.vnc' does not contain a key named 'enable' Jul 3 20:38:11 polar kernel: [ 699.349484] traps: gnome-control-c[11235] trap int3 ip:7f7a5281eccf sp:7ffdf1107bf0 error:0 in libglib-2.0.so.0.7200.1[7f7a527df000+8f000] Jul 3 20:38:12 polar whoopsie-upload-all[11302]: INFO:root:Collecting info for /var/crash/_usr_bin_gnome-control-center.1000.crash... Jul 3 20:38:24 polar whoopsie-upload-all[11302]: INFO:root:Marking /var/crash/_usr_bin_gnome-control-center.1000.crash for whoopsie upload Jul 3 20:38:24 polar whoopsie-upload-all[11302]: INFO:root: missing (remaining: 20 s): /var/crash/_usr_bin_gnome-control-center.1000.uploaded Jul 3 20:38:24 polar whoopsie[13512]: [20:38:24] Parsing /var/crash/_usr_bin_gnome-control-center.1000.crash. Jul 3 20:38:24 polar whoopsie[13512]: [20:38:24] Uploading /var/crash/_usr_bin_gnome-control-center.1000.crash. Jul 3 21:03:14 polar gnome-control-c[16759]: Failed to load module "xapp-gtk3-module" Jul 3 21:03:15 polar dbus-daemon[1765]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.138' (uid=1000 pid=16759 comm="gnome-control-center " label="unconfined") Jul 3 21:03:15 polar gnome-control-c[16759]: Settings schema 'org.gnome.desktop.remote-desktop.vnc' does not contain a key named 'enable' Jul 3 21:03:15 polar kernel: [ 2203.199215] traps: gnome-control-c[16759] trap int3 ip:7f7488c2accf sp:7ffc4b7325d0 error:0 in libglib-2.0.so.0.7200.1[7f7488beb000+8f000] Jul 3 21:03:16 polar whoopsie[16783]: [21:03:16] Parsing /var/crash/_usr_bin_gnome-control-center.1000.crash. Jul 3 21:03:16 polar whoopsie[16783]: [21:03:16] Unable to parse report (/var/crash/_usr_bin_gnome-control-center.1000.crash): /var/crash/_usr_bin_gnome-control-center.1000.crash could not be opened. Jul 3 21:03:16 polar whoopsie-upload-all[16782]: INFO:root:Collecting info for /var/crash/_usr_bin_gnome-control-center.1000.crash... Jul 3 21:03:24 polar whoopsie-upload-all[16782]: INFO:root:Marking /var/crash/_usr_bin_gnome-control-center.1000.crash for whoopsie upload Jul 3 21:03:24 polar whoopsie-upload-all[16782]: INFO:root: missing (remaining: 20 s): /var/crash/_usr_bin_gnome-control-center.1000.uploaded Jul 3 21:03:24 polar whoopsie[18923]: [21:03:24] Parsing /var/crash/_usr_bin_gnome-control-center.1000.crash. Jul 3 21:03:24 polar whoopsie[18923]: [21:03:24] Uploading /var/crash/_usr_bin_gnome-control-center.1000.crash. Jul 3 21:04:30 polar gnome-control-c[18989]: Failed to load module "xapp-gtk3-module" Jul 3 21:04:31 polar gnome-control-c[19142]: Failed to load module "xapp-gtk3-module" Jul 3 21:04:32 polar dbus-daemon[1765]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.145' (uid=1000 pid=19142 comm="gnome-control-center " label="unconfined") Jul 3 21:04:32 polar gnome-control-c[19142]: Settings schema 'org.gnome.desktop.remote-desktop.vnc' does not contain a key named 'enable' Jul 3 21:04:32 polar kernel: [ 2279.903582] traps: gnome-control-c[19142] trap int3 ip:7f88fcf51ccf sp:7fff64c9aaf0 error:0 in libglib-2.0.so.0.7200.1[7f88fcf12000+8f000] Jul 3 21:04:43 polar gnome-control-c[19317]: Failed to load module "xapp-gtk3-module" Jul 3 21:04:46 polar gnome-control-c[19317]: Settings schema 'org.gnome.desktop.remote-desktop.vnc' does not contain a key named 'enable' Jul 3 21:04:46 polar kernel: [ 2294.319951] traps: gnome-control-c[19317] trap int3 ip:7f8823f4accf sp:7fffa4ddd080 error:0 in libglib-2.0.so.0.7200.1[7f8823f0b000+8f000] Jul 3 21:26:49 polar whoopsie-upload-all[20211]: INFO:root:/var/crash/_usr_bin_gnome-control-center.1000.crash already marked for upload, skipping Jul 3 21:41:09 polar gnome-control-c[20800]: Failed to load module "xapp-gtk3-module" J
[Bug 1980606] [NEW] gnome-control-centre crashes after enabling "Sharing"
Public bug reported: After the crash, gnome-control-centre fails to launch again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Jul 3 20:39:04 2022 InstallationDate: Installed on 2017-05-24 (1866 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-05-31 (33 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1980606 Title: gnome-control-centre crashes after enabling "Sharing" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1980606/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971434] Re: Display powersave only blanks, but does not turn off
I had the same issue after upgrading to ubuntu 22.04 and the logs showed the following error. Failed to connect to the screen saver: Error al llamar StartSereviceByName para org.gnome.ScreenSaver: Failed to execute program org.gnome.ScreenSaver: No such file or directory The missing file was /usr/bin/gjs which I was able to solve by installing the gjs package. After restarting session the display powered off as espected. I hope your problem is the same and you can solve it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878617] Re: Apple pages file type should be added to MIME types
A fix was released upstream in shared-mime-info 2.2 (2022-03-27). Sadly, this didn't make it to Ubuntu 22.04 LTS. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1878617 Title: Apple pages file type should be added to MIME types To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1878617/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option
I managed to get Wayland working on my Nvidia 3070 based machine by changing the below labels RUN command from 'false' to 'true' in "/lib/udev/rules.d/61-gdm.rules". This block is at the bottom of the file. LABEL="gdm_disable_wayland" RUN+="/usr/libexec/gdm-runtime-config set daemon WaylandEnable true" # RUN+="/usr/libexec/gdm-runtime-config set daemon WaylandEnable false" GOTO="gdm_end" Patiently awaiting a proper fix :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1969243 Title: gdm 42.0-1ubuntu4 no longer shows Wayland option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1952107] Re: Google Contacts API Deprecated
Any chance this will get fixed in focal? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965820] Re: Screen goes black when opening Settings [Unhandled promise rejection in _loadFile@resource:///org/gnome/shell/ui/background.js:503:20]
The black screen occurs regularly (but not systematically) when I click on "Settings" or sometimes even when I try to change a setting, like Bluetooth or WiFi. And this error is one of those that appear in the logs. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965820 Title: Screen goes black when opening Settings [Unhandled promise rejection in _loadFile@resource:///org/gnome/shell/ui/background.js:503:20] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965820/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958721] Re: appstreamcli refresh-cache reports MDB_MAP_FULL
using appstreamcli 0.15.2 build from git master (g...@github.com:ximion/appstream.git) does not result in any error: david@bee:~/src/appstream/build$ ./tools/appstreamcli --version AppStream version: 0.15.2 david@bee:~/src/appstream/build$ sudo ./tools/appstreamcli refresh --force ** (appstreamcli:311703): WARNING **: 09:35:44.249: Found icon of unknown type 'unknown' in 'system/flatpak/flatpak/cc.nift.nsm/*', skipping it. ** (appstreamcli:311703): WARNING **: 09:35:44.250: Found icon of unknown type 'unknown' in 'system/flatpak/flatpak/cc.nift.nsm/*', skipping it. ? Metadata cache was updated successfully. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1958721 Title: appstreamcli refresh-cache reports MDB_MAP_FULL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1958721/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958721] Re: appstreamcli refresh-cache reports MDB_MAP_FULL
> You have a cache bigger than 256MB?? This issue is already fixed with appstream 0.15.0, but I still would like to know why your cache is so huge. What's you system locale? I would like to understand it too. System locale: david@bee:~$ locale -a C C.UTF-8 POSIX en_US.utf8 david@bee:~$ locale LANG=C.UTF-8 LANGUAGE=C LC_CTYPE="C" LC_NUMERIC="C" LC_TIME="C" LC_COLLATE="C" LC_MONETARY="C" LC_MESSAGES="C" LC_PAPER="C" LC_NAME="C" LC_ADDRESS="C" LC_TELEPHONE="C" LC_MEASUREMENT="C" LC_IDENTIFICATION="C" LC_ALL=C If you could provide any tips on how to determine how or why my cache would be so large, it might help identify the source of this problem. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1958721 Title: appstreamcli refresh-cache reports MDB_MAP_FULL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1958721/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958721] [NEW] appstreamcli refresh-cache reports MDB_MAP_FULL
Public bug reported: On Ubuntu 21.10 aarch64 AppStream version: 0.14.5 I get the following error: % sudo appstreamcli refresh-cache --force Unable to add data: MDB_MAP_FULL: Environment mapsize limit reached Using: sudo ltrace -f -l liblmdb.so.0 appstreamcli refresh-cache I see that the DB is initialized with a 256MB size [pid 244512] libappstream.so.4->mdb_env_set_mapsize(0xd38f46e0, 0x1000, 0xd38f46e0, 0) = 0 ** Affects: appstream (Ubuntu) Importance: Undecided Status: New ** Attachment added: "ltrace from appstreamcli" https://bugs.launchpad.net/bugs/1958721/+attachment/5556389/+files/appstreamcli.ltrace.bz2 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1958721 Title: appstreamcli refresh-cache reports MDB_MAP_FULL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1958721/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1950054] [NEW] files app loses orange dot in dock when usb drive is selected
Public bug reported: When I use a flash drive and select it in files app, the orange 'running' dot in dock for 'pinned' files app vanishes - it returns if you select Documents or Downloads a few times. Also, flash drives do not auto-mount, even though 'gsettings get org.gnome.desktop.media-handling automount' is set to true. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 17:38:10 2021 InstallationDate: Installed on 2021-05-01 (189 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to impish on 2021-11-02 (3 days ago) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1950054 Title: files app loses orange dot in dock when usb drive is selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1950054/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1901584] Re: vcdimager plug-in can't be enabled in Brasero
*** This bug is a duplicate of bug 1880385 *** https://bugs.launchpad.net/bugs/1880385 ** Bug watch added: gitlab.gnome.org/GNOME/brasero/-/issues #343 https://gitlab.gnome.org/GNOME/brasero/-/issues/343 ** Also affects: brasero via https://gitlab.gnome.org/GNOME/brasero/-/issues/343 Importance: Unknown Status: Unknown ** This bug has been marked a duplicate of bug 1880385 vcdimager plug-in can't be enabled. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1901584 Title: vcdimager plug-in can't be enabled in Brasero To manage notifications about this bug go to: https://bugs.launchpad.net/brasero/+bug/1901584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1938853] [NEW] Wacom tablet tracking mode is not persistent
Public bug reported: Setting Wacom tablet from Absolute to Relative works correctly. However upon system restart, the setting remains as "Relative" but behaviour defaults back to "Absolute". At this point changing the system setting via gnome-control-centre from Relative to Absolute (no change - still absolute) and then back again to Relative results in correct (relative) behaviour. Ubuntu 20.04 Wacom Graphire4 Tablet ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 4 15:16:32 2021 InstallationDate: Installed on 2020-05-03 (457 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1938853 Title: Wacom tablet tracking mode is not persistent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1938853/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1933168] [NEW] Show Applications button does not bring up application after setting show-favorites to false
Public bug reported: Description: When setting show-favorites to false by following command, log out/in or reboot, show applications button does not bring up applications: gsettings set org.gnome.shell.extensions.dash-to-dock show-favorites false Expect results: Show Applications button can bring up application Actual results: Show Applications button does not do anything, applications won't show up OS: Ubuntu 20.04.2 LTS Gnome-shell version: 3.36.7-0ubuntu0.20.04.1 gnome-shell-extension-ubuntu-dock version: 68ubuntu1~20.04.1 Error: gnome-shell[2110]: JS ERROR: TypeError: Main.overview.viewSelector._activePage is null _onShowAppsButtonToggled@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1912:25 ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1933168 Title: Show Applications button does not bring up application after setting show-favorites to false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1933168/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions)
Just upgrade, I just tried Ubuntu again and I didn't get the problem this time. Looks like it's fixed in Ubuntu -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions)
I tried to install both, Ubuntu 20.04.2 lts and pop_os 20.04, this glitch when resizing is the only problem I can't fix. Both were fresh installations so i assume it is present and I couldn't find a solution other than to enable wayland. I don't know how to change GRUB_DEFAULT_LINUX or disable a device that crashes the laptop (I can disable it with xinput and then no problem). That's why I haven't changed to wayland. But the bug is still there. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
