[Bug 1975410] Re: Maximized window border under status bar in Wayland / Mutter
Thanks for the screenshot. This makes me suspect your issue is caused by one of the many unsupported extensions that are enabled: ' changetopf...@romano.rgtti.com', 'temperature@xtranophilist', 'anti- bt-i...@orzechowskid.github.com', 'putwin...@clemens.lab21.org', 'freon@UshakovVasilii_Github.yahoo.com', 'alternate-tab@gnome-shell- extensions.gcampax.github.com', 'tray...@polof.github.com', 'topic...@phocean.net', 'systemMonitor@gnome-shell- extensions.gcampax.github.com', 'pulseaudio-equali...@s8dragon.vn', 'dash-to-pa...@jderose9.github.com', 'TaskBar@zpydr', 'task...@ttux.net', 'windowIsReady_Remover@nunofarr...@gmail.com', 'battery-percent...@nohales.org', 'nohotcor...@azuri.free.fr', 'recentit...@bananenfisch.net', 'appmenu-regular-ic...@example.com', 'tinkerer@joebodo', 'battery-percent...@mubaris.github.io', 'desktop- icons@csoriano', 'coverflowalt...@palatis.blogspot.com', 'compiz-alike- windows-eff...@hermes83.github.com', 'no-overview@fthx', 'compiz- windows-eff...@hermes83.github.com', 'trayiconsreloa...@selfmade.pl' Please uninstall ALL of them. If you're not sure how then just run: cd ~/.local/share/gnome-shell/ rm -rf extensions and then log in again. Does the bug still occur? -- 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/1975410 Title: Maximized window border under status bar in Wayland / Mutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
** Description changed: [Summary] The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB [Steps to reproduce] 1. Attact DA310 or WD19TB to DUT 2. Cold Boot into OS 3. Plug the DP/HDMI cable to DA310 or WD19TB 4. Check the external monitor has signal 5. Click keyboard or move mouse to check system can work well [Expected result] System won't be freeze with external monitor. [Actual result] - System will be freeze. + Screen will freeze, but ssh can still reach out DUT. Keyboard and mouse + don't work during the screen freeze. It can be recovered after unplug the external monitor sometime. [gnome-shell stack trace] - 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). - 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). - 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). - 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed - 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg - 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001) - 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root - 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. - 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == - 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == - 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. - 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. - 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. - 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. + 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). + 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). + 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). + 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed + 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg + 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001) + 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root + 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. + 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == + 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == + 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640.
[Bug 1969893] Re: gnome-shell crashes with SIGSEGV just after logging "JS ERROR: TypeError: window is null" from _destroyWindow() [windowManager.js:1543:9]
** Tags added: fixed-in-42.2 -- 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/1969893 Title: gnome-shell crashes with SIGSEGV just after logging "JS ERROR: TypeError: window is null" from _destroyWindow() [windowManager.js:1543:9] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969893/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1973467] Re: [Ubuntu 22.04] [nvidia] [Wayland] Screen Blank: External screen is not turned off in sleep mode
** Changed in: mutter (Ubuntu) Status: Incomplete => 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/1973467 Title: [Ubuntu 22.04] [nvidia] [Wayland] Screen Blank: External screen is not turned off in sleep mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1973467/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
I add commit mentioned in #13 to build mutter packages. https://launchpad.net/~kchsieh/+archive/ubuntu/verification/ It doesn't help the 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1975945] Re: Update gnome-control-center to 41.7
I completed all 3 test cases successfully with gnome-control-center 1:41.7-0ubuntu0.22.04.1 ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-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/1975945 Title: Update gnome-control-center to 41.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1975945/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976120] Re: Update nautilus to 42.2
I successfully completed all 3 test cases with nautilus 1:42.2-0ubuntu1 ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/1976120 Title: Update nautilus to 42.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1976120/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969893] Re: gnome-shell crashes with SIGSEGV just after logging "JS ERROR: TypeError: window is null" from _destroyWindow() [windowManager.js:1543:9]
** Changed in: mutter (Ubuntu Jammy) Status: Triaged => In Progress ** Description changed: + Impact + == + GNOME Shell crashes when it's restarted on Xorg. (There is no option to restart GNOME Shell on Wayland.) + + Test Case + = + Install the update + On the login screen, select your name. + Click the gear button in the lower right and choose Ubuntu on Xorg + Enter your password to finish logging in. + Open the file browser. + Press Alt-F2. + In the dialog, enter 'r' + GNOME Shell should restart without a crash message. Your file browser window should remain open. + + What Could Go Wrong + === + See the master bug for this update LP: #1976381 + + More Details + gnome-shell crashes with SIGSEGV just after logging: gnome-shell[3117]: JS ERROR: TypeError: window is null _destroyWindow@resource:///org/gnome/shell/ui/windowManager.js:1543:9 _initializeUI/<@resource:///org/gnome/shell/ui/main.js:260:16 Examples: https://errors.ubuntu.com/oops/96ee1700-c208-11ec-a3de-fa163ef35206 https://errors.ubuntu.com/oops/e97480f0-c1bc-11ec-a3d8-fa163ef35206 https://errors.ubuntu.com/oops/aa5bf652-d517-11ec-9aa3-fa163e55efd0 Tracking in: https://errors.ubuntu.com/problem/eb1d2411708c44f1299f717f5a9c19c03cf80470 ^^^ this is the second most common gnome-shell crash on errors.ubuntu.com -- 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/1969893 Title: gnome-shell crashes with SIGSEGV just after logging "JS ERROR: TypeError: window is null" from _destroyWindow() [windowManager.js:1543:9] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969893/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976381] Re: Update mutter to 42.2
** Changed in: mutter (Ubuntu Jammy) Status: Triaged => In Progress -- 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/1976381 Title: Update mutter to 42.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1976381/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
Some updates here: The shell isn't really hanging... The fact is that the input/output GLib Sources that the shell adds to the main context are starving and never processed because we add thousands of timeouts and `Meta.Later` sources as per a `window-removed` signal that is triggered thousand times (source is actually `[gnome-shell] this._queueCheckWorkspaces`). This leads to CPU being 100% spending time in processing such sources (https://usercontent.irccloud-cdn.com/file/v1ZGs5f6/image.png) thousands of GSources being added: https://i.imgur.com/QUuuZA1.png And these are added via https://usercontent.irccloud- cdn.com/file/V4jfRY94/with%20laters%20added%20at that sends the window- removed signal (https://i.imgur.com/PNBn6Cv.png). Now, it seems possible that the fixes part of 42.2 in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2413 fix this case. But we still need to 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
** Also 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969396] Re: Right Alt not working reliably as compose key unless the layout in effect is first in the list of sources
While an annoying issue and a regression, it's impacting some configurations only and is workaroundable so we are not going to handle it as a rls issue. We will work on trying to provide a fix if possible though ** Tags removed: rls-jj-incoming ** Tags added: rls-jj-notfixing -- 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/1969396 Title: Right Alt not working reliably as compose key unless the layout in effect is first in the list of sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969396/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969855] Re: Livepatch status icon does not appear in top bar
** Changed in: canonical-livepatch-client Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1969855 Title: Livepatch status icon does not appear in top bar To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-livepatch-client/+bug/1969855/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967121] Re: Dock auto-hides when a right click context menu is opened while a window is under the dock
** Changed in: dash-to-dock Status: New => Fix Released -- 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/1967121 Title: Dock auto-hides when a right click context menu is opened while a window is under the dock To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1967121/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1974026] Re: webdav doesn't work with folder
** Changed in: gvfs Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1974026 Title: webdav doesn't work with folder To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1974026/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971144] Re: Black screen after login when using CKLau-64HUA KVM switch
OK then, fix released... somewhere. ** No longer affects: mutter (Ubuntu) ** Package changed: linux (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Confirmed => Fix Released -- 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/1971144 Title: Black screen after login when using CKLau-64HUA KVM switch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1971144/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1970636] Re: Top bar menus are unavailable on login/lock screen
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Released ** Tags added: fixed-in-42.2 fixed-upstream -- 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/1970636 Title: Top bar menus are unavailable on login/lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1970636/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963264] Re: Gnome screen recorder doesn't work on dist-upgraded jammy systems
That's tricky. I'm not sure removing files from users' home directories is something we can do in a package update. Ideally we would instead find the bug in the offending gstreamer/whatever package and fix the source code instead. Without any idea what package is even causing the bug we may not be able to ever get a fix. -- 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/1963264 Title: Gnome screen recorder doesn't work on dist-upgraded jammy systems To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1963264/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1970291] Re: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions
Yes, 1. Add this to /etc/environment: CLUTTER_SHOW_FPS=1 2. Reboot. 3. Watch the log: journalctl -f /usr/bin/gnome-shell ** No longer affects: mutter -- 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/1970291 Title: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
> Adding MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 doesn't help. > Is there any way to disable the screen blanking? Yes it does solve this bug. If it doesn't solve your issue then you need to report a NEW bug. -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968910] Re: Extension NAME already installed in /usr/share/gnome-shell/extensions/NAME. /usr/share/gnome-shell/extensions/NAME will not be loaded
Try :~$ gnome-shell-extension-prefs I had the same problem and somehow extensions where disabled globally while having the exact same log messages. If that's what you are experiencing, the bug is reduced to misleading log entries. -- 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/1968910 Title: Extension NAME already installed in /usr/share/gnome- shell/extensions/NAME. /usr/share/gnome-shell/extensions/NAME will not be loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969294] Re: Ubuntu 22.04 gdm3 freezes with Nvidia GPU
Karl and everyone else, please report your own bug by running: ubuntu-bug gnome-shell -- 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/1969294 Title: Ubuntu 22.04 gdm3 freezes with Nvidia GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969294/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1955593] Re: Ubuntu 21.10 "gnome-shell[1453]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed"
*** This bug is a duplicate of bug 1871262 *** https://bugs.launchpad.net/bugs/1871262 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 1871262, 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. ** This bug has been marked a duplicate of bug 1871262 gnome-shell freezes/crashes with meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed -- 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/1955593 Title: Ubuntu 21.10 "gnome-shell[1453]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1955593/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966787] Re: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error
Just had the same issue with Totem 42.0 in Ubuntu 22.04. Removing of ".config/totem" helped me. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1966787 Title: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1966787/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1812506] Re: gnome-control-center > Devices > Removable_media > Ask_what_to_do - does not ask
** Tags added: kinetic -- 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/1812506 Title: gnome-control-center > Devices > Removable_media > Ask_what_to_do - does not ask To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968910] Re: Extension NAME already installed in /usr/share/gnome-shell/extensions/NAME. /usr/share/gnome-shell/extensions/NAME will not be loaded
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1968910 Title: Extension NAME already installed in /usr/share/gnome- shell/extensions/NAME. /usr/share/gnome-shell/extensions/NAME will not be loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1735986] Re: Unable to set different scale correctly on different monitors
Sören, this bug has been idle a few years... To help us confirm which issue you are really experiencing in 22.04, please report it as a new bug by running: ubuntu-bug gnome-shell -- 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/1735986 Title: Unable to set different scale correctly on different monitors To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1735986/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1972034] Re: On browser download/save dialog, filename in name box is highlighted as if it is active, but typing doesn't edit name unless you click into the box
it could be different gtk series. Which version on Ubuntu did you try on? For the firefox snap the selector comes from the gnome xdg portal which is using gtk4. Could you try if gnome-text-editor is showing the issue? -- 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/1972034 Title: On browser download/save dialog, filename in name box is highlighted as if it is active, but typing doesn't edit name unless you click into the box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1972034/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1977655] Re: Nautilus Open Files and Save File... dialogs keep growing
*** This bug is a duplicate of bug 1971112 *** https://bugs.launchpad.net/bugs/1971112 ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 1971112 File picker gets bigger more and more each time! -- 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/1977655 Title: Nautilus Open Files and Save File... dialogs keep growing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1977655/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1974026] Re: webdav doesn't work with folder
Thanks, upstream requested another log with a debug env set ** Changed in: nautilus (Ubuntu) Status: New => Triaged ** Package changed: nautilus (Ubuntu) => gvfs (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/gvfs/-/issues #632 https://gitlab.gnome.org/GNOME/gvfs/-/issues/632 ** Also affects: gvfs via https://gitlab.gnome.org/GNOME/gvfs/-/issues/632 Importance: Unknown Status: Unknown -- 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/1974026 Title: webdav doesn't work with folder To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1974026/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1977643] Re: gdm crash when unlocking screen if using Nouveau driver
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gdm3 (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/1977643 Title: gdm crash when unlocking screen if using Nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1977643/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1977660] Re: Power settings have no effect and offer nonexisting options
Thank you for your bug report. Could you provide the output of $ powerprofilesctl and $ cpupower frequency-info after changing the profile ? ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- 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/1977660 Title: Power settings have no effect and offer nonexisting options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1977660/+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)
** Changed in: gnome-shell Status: Unknown => New -- 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 1961508] Re: Dock displaying over window after resuming from blank screen
** Changed in: mutter Status: Unknown => 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/1961508 Title: Dock displaying over window after resuming from blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1961508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961508] Re: Dock displaying over window after resuming from blank screen
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1627 https://gitlab.gnome.org/GNOME/mutter/-/issues/1627 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1627 Importance: Unknown Status: Unknown ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1961508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
I'm away from Ubuntu for now, so can anyone check if the following command solves this issue: xset -dpms -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892456] Re: [MIR] malcontent
AFAIU https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1812456 needs to be completed to unblock this one here as well. There is a discussion between Security and others - but that seems stalled for almost a year now. Maybe worth to ping there (or the involved people) to get it back on track? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to malcontent in Ubuntu. https://bugs.launchpad.net/bugs/1892456 Title: [MIR] malcontent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/malcontent/+bug/1892456/+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)
You don't need to remove a colour profile to fix the problem, just disable it: 1. Settings > Colour > turn off the toggle switch for your monitor. 2. Restart any affected apps. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4492 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4492 ** Changed in: gnome-shell Remote watch: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3033 => gitlab.gnome.org/GNOME/gnome-shell/-/issues #4492 ** Description changed: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: - Settings > Devices > Colour > + Settings > Colour > and disable or remove your monitor's colour profile Originally reported in https://bugzilla.gnome.org/show_bug.cgi?id=675645 ** Description changed: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: - Settings > Colour > - and disable or remove your monitor's colour profile + 1. Settings > Colour > turn off the toggle switch for your monitor. + + 2. Restart any affected apps. Originally reported in https://bugzilla.gnome.org/show_bug.cgi?id=675645 -- 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