[Bug 2020782] Re: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages
While I do see a couple of bugs when changing display scale on Xorg, I don't see the "Failed to restore previous configuration" that is the main subject here. So it sounds like this is only occurring on Xdcv. ** Tags added: jammy xrandr-scaling -- 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/2020782 Title: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020782] Re: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages
Marco is the author of the Xrandr fractional scaling support patch so he might have some immediate ideas. I figure a lot of this is going to be affected by that patch even if you're only trying to use integer scaling. ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/2020782 Title: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020803] Re: logging in at the lock screen causes the system to log me out and start over.
After the problem occurs, please also run: dconf dump /org/gnome/shell/ > settings.txt journalctl -b0 > journal.txt and attach the resulting text files here. -- 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/2020803 Title: logging in at the lock screen causes the system to log me out and start over. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020803/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020803] Re: logging in at the lock screen causes the system to log me out and start over.
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/2020803 Title: logging in at the lock screen causes the system to log me out and start over. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020803/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2019906] Re: 23.04 : condensed, bold and black fonts can't be used for interface and title bar
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2019906 Title: 23.04 : condensed, bold and black fonts can't be used for interface and title bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/2019906/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2019906] Re: 23.04 : condensed, bold and black fonts can't be used for interface and title bar
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: budgie-desktop (Ubuntu) Status: New => Confirmed -- 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/2019906 Title: 23.04 : condensed, bold and black fonts can't be used for interface and title bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/2019906/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020822] [NEW] Update epiphany-browser to 44.3
Public bug reported: Impact -- ** Affects: epiphany-browser (Ubuntu) Importance: High Status: Fix Committed ** Tags: lunar upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/2020822 Title: Update epiphany-browser to 44.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/2020822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2017097] Re: [raspi] GNOME Shell 44.0 runs at 30 FPS unless the CPU is being stressed
Also verified on a Pi 4 (mutter 44.1-0ubuntu1); video playback is smooth again! -- 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/2017097 Title: [raspi] GNOME Shell 44.0 runs at 30 FPS unless the CPU is being stressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2017097/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020674] Re: Artifacts at window borders with mutter 44.1
This bug was fixed in the package gtk4 - 4.10.3+ds-1ubuntu2 --- gtk4 (4.10.3+ds-1ubuntu2) mantic; urgency=medium * Cherry-pick patch to fix black rectangles seen with mutter 44.1 (LP: #2020674) -- Jeremy Bícha Wed, 24 May 2023 16:32:14 -0400 ** Changed in: gtk4 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2020674 Title: Artifacts at window borders with mutter 44.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2020674/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020806] [NEW] Move to trash: file icon moved, not removed
Public bug reported: Click on file icon on nautilus window, select 'move to trash' the file is moved to trash but the icon does not disappear, but is just moved in the window. see attached screencast. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 25 19:16:31 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(861, 761)' InstallationDate: Installed on 2023-05-21 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230521) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.1-1ubuntu1 python3-nautilus 4.0-1build1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session ** Attachment added: "Screencast from 2023-05-25 08-37-23.webm" https://bugs.launchpad.net/bugs/2020806/+attachment/5675656/+files/Screencast%20from%202023-05-25%2008-37-23.webm -- 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/2020806 Title: Move to trash: file icon moved, not removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2020806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020803] [NEW] logging in at the lock screen causes the system to log me out and start over.
Public bug reported: After my system lock screen enables (whether through timeout or if I manually lock it), unlocking the system causes all programs to forcibly shut down and a new session to start. Effectively, I'm logging in fresh every time the lock screen is enabled. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gdm3 44.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 May 25 12:41:01 2023 InstallationDate: Installed on 2020-12-03 (902 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: Upgraded to lunar on 2023-04-26 (28 days ago) ** Affects: gdm3 (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 gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2020803 Title: logging in at the lock screen causes the system to log me out and start over. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2020803/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020782] Re: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages
Also tested with mutter-common 42.5-0ubuntu1 and gnome-shell 42.5-0ubuntu1: fabiomirmar@U-1JSKZM4R9U78P:~$ sudo apt-cache policy mutter-common [sudo] password for fabiomirmar: mutter-common: Installed: 42.5-0ubuntu1 Candidate: 42.5-0ubuntu1 Version table: *** 42.5-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages fabiomirmar@U-1JSKZM4R9U78P:~$ sudo apt-cache policy gnome-shell gnome-shell: Installed: 42.5-0ubuntu1 Candidate: 42.5-0ubuntu1 Version table: *** 42.5-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages And I have the same issue. When I apply the scale change I see: May 25 13:30:21 U-1JSKZM4R9U78P systemd[2514]: vte-spawn-11c0b6cb-a094-4eee-9cbf-7a694348f00a.scope: Consumed 1.272s CPU time. May 25 13:30:21 U-1JSKZM4R9U78P systemd[2514]: gnome-terminal-server.service: Consumed 1.231s CPU time. May 25 13:30:25 U-1JSKZM4R9U78P gnome-shell[2862]: Impossible to set scaling on crtc 59 to 0.615385, error id 2 May 25 13:30:25 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: Scalig CRTC 59 at 0.615385 failed May 25 13:30:25 U-1JSKZM4R9U78P gnome-shell[2862]: Xlib: extension "DPMS" missing on display ":1". May 25 13:30:25 U-1JSKZM4R9U78P gnome-shell[2862]: Missing logical monitor, using scale 1 May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Xlib: extension "DPMS" missing on display ":1". May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Missing logical monitor, using scale 1 May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Spurious clutter_actor_allocate called for actor 0x55a6ef3a4ba0/[:0x55a6ef3a4ba0] which isn't a descendent of the stage! May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: property match 'XRANDR_name'='VNC-output-0' does not exist May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: property match 'XRANDR_name'='VNC-output-1' does not exist May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: property match 'XRANDR_name'='VNC-output-2' does not exist May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: property match 'XRANDR_name'='VNC-output-3' does not exist May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: property match 'XRANDR_name'='VNC-output-0' does not exist May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: property match 'XRANDR_name'='VNC-output-1' does not exist May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: property match 'XRANDR_name'='VNC-output-2' does not exist May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: property match 'XRANDR_name'='VNC-output-3' does not exist May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views actor [:0x55a6ee826330] is on because it needs an allocation. May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views actor [:0x55a6f04896e0] is on because it needs an allocation. May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views actor [:0x55a6f048ca30] is on because it needs an allocation. May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). May 25 13:30:27 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views actor [:0x55a6ee826330] is on because it needs an allocation. May 25 13:30:27 U-1JSKZM4R9U78P gnome-shell[2862]:
[Bug 2020782] [NEW] Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages
Public bug reported: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 18:31:40 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". I'm unable to reproduce the problem if I manually install ubuntu-desktop and use the Nice DCV Server (as used by Workspaces) by following the steps from (using the xorg-x11-drv-dummy): https://docs.aws.amazon.com/dcv/latest/adminguide/setting-up-installing- linux.html One relevant difference is that Workspaces uses a custom X11 server /usr/bin/Xdcv, instead of /usr/lib/xorg/Xorg, and they have the following process being started: /usr/bin/Xdcv -output 800x600+0+0 -output 800x600+800+0 -output 800x600+1600+0 -output 800x600+2400+0 -enabledoutputs 1 vt2 -displayfd 3 -auth /run/user/541001128/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3 I'm also unable to reproduce the problem using xrdp + Xorg. While discussing this with the desktop crew, it was mentioned that we see the same problems in Xorg. And to a much lesser extent some issues in Wayland too when changing scales.
[Bug 2011251] Re: When focus-mode=mouse is set, gnome-shell gets into state where clicking on window title bars doesn't raise them
It looks like the gnome bug does acknowledge it only works for 'click' mode (I use sloppy) so presumably when that gets fixed (and it looks like they're still thinking about it!) and released then both mine and yours will too. -- 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/2011251 Title: When focus-mode=mouse is set, gnome-shell gets into state where clicking on window title bars doesn't raise them To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2011251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)
I enabled the -proposed repository and lowered the priority, then i updated mutter and gnome shell: sudo apt-get install mutter/lunar-proposed gnome-shell/lunar-proposed This fixed the raise issue for me. I do not use SNAP applications, so I can't test that -- 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/2013216 Title: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020759] Re: App bar non-responsive when not in front
*** This bug is a duplicate of bug 2013216 *** https://bugs.launchpad.net/bugs/2013216 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2013216, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** This bug has been marked a duplicate of bug 2013216 Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) -- 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/2020759 Title: App bar non-responsive when not in front To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020759/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020652] Re: gnome-shell crashed with SIGSEGV in on_swap_buffer_update_result() from on_swap_buffer_update_result() from flush_callbacks() from callback_idle() from g_main_dispatch()
The fix will be in the 44.2 update (providing we remember to refresh the triple buffering patch): https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commits/triple-buffering-v4-44/ ** Tags added: fixed-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/2020652 Title: gnome-shell crashed with SIGSEGV in on_swap_buffer_update_result() from on_swap_buffer_update_result() from flush_callbacks() from callback_idle() from g_main_dispatch() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020652/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020759] [NEW] App bar non-responsive when not in front
You have been subscribed to a public bug: When clicking on the "app bar" of some applications (containing the name and close/minimise/... button) which are not in the foreground, nothing happens. This seems to currently happen with the sioyek app (which was not installed but is running through some fuse) and Discord, but did happen to other stuff too :) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 25 10:52:01 2023 DistUpgraded: 2023-04-23 21:55:53,032 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:8292] InstallationDate: Installed on 2023-03-30 (56 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05c8:0397 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP HD Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 03f0:a31d HP, Inc HP lt4132 LTE/HSPA+ 4G Module Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 820 G4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=8b91027a-0905-472e-925a-7554704d7b0e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-23 (31 days ago) dmi.bios.date: 07/17/2018 dmi.bios.release: 1.23 dmi.bios.vendor: HP dmi.bios.version: P78 Ver. 01.23 dmi.board.name: 8292 dmi.board.vendor: HP dmi.board.version: KBC Version 45.43 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 69.67 dmi.modalias: dmi:bvnHP:bvrP78Ver.01.23:bd07/17/2018:br1.23:efr69.67:svnHP:pnHPEliteBook820G4:pvr:rvnHP:rn8292:rvrKBCVersion45.43:cvnHP:ct10:cvr:skuX3T23AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 820 G4 dmi.product.sku: X3T23AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ubuntu -- App bar non-responsive when not in front https://bugs.launchpad.net/bugs/2020759 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1888098] Re: In Xorg sessions, gnome-shell places windows on second screen when started from primary screen
** Summary changed: - gnome-shell places windows on second screen when started from primary screen + In Xorg sessions, gnome-shell places windows on second screen when started from primary screen -- 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/1888098 Title: In Xorg sessions, gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1888098/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
