Trying to move a window by grip-able button. On 2 other window managers, and no manager it works fine. Windows move anywhere you want pass display edge bounds. On GNOME Shell and Mutter(Gala) the window is confined to the desktop view with no part of it allowed past display edges. On Compiz I use _NET_WM_MOVERESIZE, other 2 are grab_pointer. The mutter variants won't work using _NET_WM_MOVERESIZE which is fine, but I can't figure out what property to set on the window to allow normal configure messages to get past display limits. Hint as to which it is would be appreciated, kinda would like to support the variant. Need a window_property_set or client message to root to be able to use configure_window. Using code:

#if USE_XLIB
  XMoveWindow(display, motion->event, values, values);
#else
  xcb_configure_window(session->connection, motion->event,
               XCB_CONFIG_WINDOW_X | XCB_CONFIG_WINDOW_Y, values);
#endif

This will only allow movement to the confines of 'maximize' window display. Moving left, negative x values get converted by GNOME to 0. Moving toward bottom, any value greater than window.y + window.height gets converted to display height - taskbar height - window height by GNOME. Verified by values received on configure notify. Do I need to delete a _NET_WM_STRUT property on my window or root window to use? Looking at gdk3 code they use the Xlib variant of code. **Solved**\ Problem is issue that GNOME only supports move of window correctly through their toolkit. It appears to lack proper support of both EWMH and ICCCM. Workaround is to use override-redirect, taking away its ability to mess with configure message.

My Ubuntu since recently started to consume 5-6% of CPU while idle (I wouldn't have noticed if it didn't cause cooler to spin :/ ). Looking into the System Monitor -- it's gnome-shell. I've tried disabling all extensions (and of course rebooting) but it didn't help. So I've tried journalctl /usr/bin/gnome-shell -- and the log is full of the following line repeated **thosands of times per second**: gnome-shell: (../clutter/clutter/clutter-frame-clock.c:1143):clutter_frame_clock_dispatch: code should not be reached. It seems it takes 5-6% of CPU to solely log this. At this point I'm lost as there's only a single reference to this error in the Internet. AFAIU the code in question is https://github.com/GNOME/mutter/blob/main/clutter/clutter/clutter-frame-clock.c but I'm not in position to debug it. I won't ask if anyove has experienced it (but would appreaciate a solution of course :) ) -- but how to address it in general? File a bug? To where? Mutter or Gnome? Or Ubuntu? :/ My Mutter libraries versions:

$ sudo apt list | grep mutter

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

gir1.2-mutter-14/noble-updates,now 46.2-1ubuntu0.24.04.4 amd64 [installed,automatic]
libmutter-14-0/noble-updates,now 46.2-1ubuntu0.24.04.4 amd64 [installed,automatic]
libmutter-14-dev/noble-updates 46.2-1ubuntu0.24.04.4 amd64
libmutter-test-14/noble-updates 46.2-1ubuntu0.24.04.4 amd64
mutter-14-tests/noble-updates 46.2-1ubuntu0.24.04.4 amd64
mutter-common-bin/noble-updates,now 46.2-1ubuntu0.24.04.4 amd64 [installed,automatic]
mutter-common/noble-updates,noble-updates,now 46.2-1ubuntu0.24.04.4 all [installed,automatic]
mutter/noble-updates 46.2-1ubuntu0.24.04.4 amd64

My system:

$ screenfetch
                          ./+o+-       flash@flash-NUC12WSHi5
                  yyyyy- -yyyyyy+      OS: Ubuntu 24.04 noble
               ://+//////-yyyyyyo      Kernel: x86_64 Linux 6.8.0-51-generic
           .++ .:/++++++/-.+sss/`      Uptime: 1h 25m
         .:++o:  /++++++++/:--:/-      Packages: 2260
        o:+o+:++.`..

.-/oo+++++/ Shell: bash 5.2.21 .:+o:+o/. `+sssoo+/ Resolution: 1920x1080 .++/+:+oo+o:` /sssooo. DE: GNOME 46.4 /+++//+:`oo+o /::--:. WM: Mutter \+/+o+++`o++o ++////. WM Theme: Adwaita .++.o+++oo+:` /dddhhh. GTK Theme: Yaru-dark [GTK2/3] .+.o+oo:. `oddhhhh+ Icon Theme: Yaru \+.++o+o`-

.:ohdhhhhh+     Font: Ubuntu Sans 11
         :o+++ ohhhhhhhhyo++os:      Disk: 1.3T / 3.2T (40%)
           .o:.syhhhhhhh/.oo++o      CPU: 12th Gen Intel Core i5-1240P @ 16x 4.4GHz [80.0°C]
               /osyyyyyyo++ooo+++/     GPU: Iris Xe Graphics

`` +oo+++o\: RAM: 5654MiB / 31606MiB `oo++. ```

I have Wayland running which also uses Mutter. I have been searching for quite a while and can't find anyway to lock this in. The reason I need this done is when I shut my laptop, or other random times, changes the configured refresh rate for my external monitor, which is a pain, and required manual intervention each time. If anyone has any luck with this please let me know. TLDR, I need to force a refresh rate in linux (fedora 41/gnome), I can see the bios/firmware screens fine.

today I installed AMD Catalyst on Fedora 22. After rebooting my computer, my screen was black. I have read several guidebooks, but I have not found a way to run "Catalyst" on GNOME on laptops. If someone has managed to run GNOME on Fedora 22 and has a laptop, let me know please.

I'm using Ubuntu 23.04 with Wayland. I use 3 extended displays, one being a small screen to be projected on a teleprompter. Is there a way to horizontally mirror/flip a display such that looking at it in a mirror it looks oriented correctly? This answer led me to the Mutter DBus configuration which indicates that this type of transformation seems possible but I can't figure out the incantation that would allow me to use it.

I am using fedora 37 with kernel version 6.2.9. Some of the applications like gnome-terminal and gnome software store when launched from the Dash in gnome-shell are not focused i.e. they are not being auto-focused. But when they are launched from other way like by gnome search they are working as expected and being auto-focused. Other applications are working fine even if they are launched from the Dash. Another thing is that when some other application is opened for example Firefox or nautilus then launching gnome-terminal or gnome software store works as expected and are auto-focused. I tried setting gsettings set org.gnome.desktop.wm.preferences focus-new-windows 'smart', but it makes no difference. This problem started showing after the last update which includes updating the kernel from 6.1.18 to 6.2.9, updating mutter and nvidia driver update. **UPDATE** I installed console application which is also a terminal emulator by gnome project. It is also showing the same issue as gnome-terminal and gnome software store. I think the applications which use the shell directly or in background, are showing this kind of issues.

I have a 60 Hz monitor, but Gnome 40 settings only allows 49.99 Hz (and 29.99 Hz). I'm running Wayland, obviously. Why is that? Gnome's animations don't feel smooth either, can that be related? It's quite a big monitor with 3440 × 1440 px², and in another older question https://unix.stackexchange.com/questions/444055/how-to-force-60-hz-in-1366x768-despite-kernel-bug-after-kernel-4-13 it states that there's a kernel bug that limits refresh rate on high resolutions due to power savings with Xorg. Might this still be relevant and related? I'm on a Lenovo T470s with Intel Corporation HD Graphics 620 (rev 02).

Using Zorin OS Lite. I keep getting this error when installing packages.

dpkg: unrecoverable fatal error, aborting:  files list file for package 'mutter-common' contains empty filename
E: Sub-process /usr/bin/dpkg returned an error code (2)

This seems to be the same error mentioned in this posting. https://askubuntu.com/questions/648736/i-get-this-error-dpkg-unrecoverable-fatal-error-aborting-files-list-file-for# With me, it was several different packages. I went through all of them and fixed them by the method described in Adrian Cid Almaguer's answer to that other question. However,

-common

seems to keep breaking again. Repeating the same manoeuvre fixes it, but it's odd. None of the others seem to have broken again. Any idea what's going on here and whether there's any way to get rid of it?

I'm trying to get my head around shell scripting to solve a minor Wayland/Mutter bug that hasn't been addressed in over two years. I'm completely unfamiliar with shell scripting, but I think this should be possible. The problem is that on Wayland the xkb option to indicate keyboard layouts with a LED doesn't work correctly. It works on first layout switch, turning the LED on, but then stops working, leaving the LED always on. So my idea is to have a script that would check for the contents of the system LED file upon pressing a particular key (CapsLock in my case), and change it to the opposite value. The logic would be as follows: listen to CapsLock and upon keypress do cat /sys/class/leds/input7::capslock/brightness if cat returns 0 then echo 1 > /sys/class/leds/input7::capslock/brightness if cat returns 1 then echo 0 > /sys/class/leds/input7::capslock/brightness wait for next CapsLock keypress I'm good at learning stuff from examples, but I couldn't find relevant info online. I guess I just don't know how to phrase this correctly to get relevant results. So any tips and pointers in the right direction greatly appreciated! **UPD:**
I got as far as creating the shell script that switches the LED on and off depending on the current state of the LED. How do I make it execute every time CapsLock is pressed? #!/bin/bash led=cat /sys/class/leds/input7::capslock/brightness if [[ $led = "1" ]] then echo 0 > /sys/class/leds/input7::capslock/brightness else echo 1 > /sys/class/leds/input7::capslock/brightness fi **UPD2:**
I obviously made the shell script executable, moved it to /usr/local/bin/, and added it to a file in /etc/sudoers.d/ to allow it to run without a password. **UPD3**
I noticed that the ìnput number in the directory structure can change between reboots, so I modified the script to account for that. #!/bin/bash led=cat /sys/class/leds/input?::capslock/brightness file=ls /sys/class/leds/input?::capslock/brightness if [[ $led = "1" ]] then echo 0 > $file else echo 1 > $file fi Now I need to execute this every time Caps Lock is pressed. **UPD4:**
Maybe I should be trying to catch the actual keyboard layout change event instead of CapsLock press? This way would be more universal and allow the LED indicator to show the alternative layout irrespective of the shortcut being used to switch layouts. Is there a way to monitor such events?

In Gnome 3.18, it was possible to change the titlebar height of all windows by changing the css in ~/.config/gtk-3.0/gtk.css as per https://unix.stackexchange.com/questions/257163/reduce-title-bar-height-in-gnome-3-gtk-3 . .header-bar.default-decoration { padding-top: 0px; padding-bottom: 0px; } .header-bar.default-decoration .button.titlebutton { padding-top: 0px; padding-bottom: 0px; } /* No line below the title bar */ .ssd .titlebar { border-width: 0; box-shadow: none; } In Gnome 3.20, this appears to no longer apply to windows with a headerbar/CSD (gnome-specific buttons in the title bar), such as Nautilus (Files), Settings, Photos, Contacts, etc. The tweak still reduces the titlebar height for other applications, such as gnome-terminal and gVim. How do I reduce the height of the titlebar in gnome-programs such as Nautilus in Gnome 3.20? --- ### Update I have also tried what is suggested in this reddit thread . I tried both window.ssd and .ssd only, no dice. _This works, see the answer I posted for more details_ window.ssd headerbar.titlebar { padding-top: 1px; padding-bottom: 1px; min-height: 0; } window.ssd headerbar.titlebar button.titlebutton { padding-top: 1px; padding-bottom: 1px; min-height: 0; } and /* shrink headebars */ headerbar { min-height: 38px; padding-left: 2px; /* same as childrens vertical margins for nicer proportions */ padding-right: 2px; } headerbar entry, headerbar spinbutton, headerbar button, headerbar separator { margin-top: 2px; /* same as headerbar side padding for nicer proportions */ margin-bottom: 2px; } /* shrink ssd titlebars */ .default-decoration { min-height: 0; /* let the entry and button drive the titlebar size */ padding: 2px } .default-decoration .titlebutton { min-height: 26px; /* tweak these two props to reduce button size */ min-width: 26px; }

I had recently installed kali from parrot. After Successful installation. I run

sudo apt-get update
sudo apt upgrade

Now I am unable to install any package. It shows me error:

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.30.2-7 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

When I try to run

apt full-upgrade

, Another error:

libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

This is my /etc/apt/sources.list:

http://http.kali.org/kali  kali-last-snapshot main non-free contrib

And, ''apt-cache policy mutter'':

mutter:
  Installed: 3.30.2-7
  Candidate: 3.36.4-1
  Version table:
     3.36.4-1 500
        500 http://http.kali.org/kali  kali-rolling/main amd64 Packages
 *** 3.30.2-7 100
        100 /var/lib/dpkg/status

Please Help. Is anything extra I had to Post?

I'm using Arch Linux, and have both Gnome and the i3 window manager installed. When running i3, I'm trying to initiate the composite manager Compton. But trying to do so results in the following error: $ compton [ 04/11/2019 22:32:36.443 register_cm FATAL ERROR ] Another composite manager is already running I think this means that Compton is already running, or Mutter is running, but I'm not sure which. **Is there a command I can use to determine which composite manager is currently running?**

In gnome 3.28 on ubuntu 18.04 SUPER+← snaps a window to the left SUPER+→ snaps a window to the right These actions are called "View split on Left" or "View Split on Right" in the list of Gnome keyboard shortcuts in Settings. Once windows have been snapped, one can then drag the location of the split (which defaults to center) to the left or right, giving more room to one window and less to the other (and any subsequently snapped windows obey this new split location). IMO it is a beautiful and polished implementation. My question is how to move the default split location away from center. I love having an 80 character wide terminal window on the right (which takes up less than half my 16:9 screen's width) and giving the wider, remaining space to a browser window on the left. Basically, I want to avoid manually dragging the left/right snap boundary after a reboot. Here is a screenshot of split windows with my preferred boundary location: Note how the the snapped windows no longer have rounded edges, but take up the entire rectangular area on either side of the split. Since the split location can be altered with a mouse drag, perhaps this variable can be programmatically set on boot? Perhaps, though, the variable is reset upon an initial window snap and there is no way to force this... Perhaps I should just switch to a tiled wm like dwm xD but gnome is otherwise fine for me.

I have a java graphic application using Swing library. If the application is minimized and the graphic content changes (color or whatever), I should see the modification when restoring the window. However, the window is not updated and is still like the previous state. If I resize the window or move it, it is refreshed. I run this program on a linux system using X11 1.17.2 and Mutter 3.14.4 as window manager. I know the problem come from the message sent by X11 or from mutter configuration because the program worked on another system working with X11 1.10.4 and Metacity 2.28.0. How can I configure Mutter to permit it to update applications on deiconify, as well as it does for resizing ? Or have I to configure X11 ? I do not know how to solve this problem at all...

I would like to be able to resize maximized windows on Mutter. Is there any way to tell Mutter to not remove the borders when the state is "maximized", so that I can maximize and then resize? Or, if there was a way to "hijack" where Mutter performs this action and override the behavior--even forking Mutter.

I'd like to make my IDE window partially transparent. I achieved this in Unity using compiz as described in the accepted answer to: How to make a window transparent in gnome . However I don't believe compiz will work for this with gnome unless I'm mistaken. There WAS a gnome extension for this but it has been abandoned and the github repo is gone. Anyone know of a way to achieve this? I'm on ubuntu 17.10

My goal is to remove the dropshadow from all metacity windows. I realize there is not a setting to do this and I may need to recompile metacity. If I can simply do it by editing source files without compiling, an ideas where I can start on that?

Does somebody knows how to maximize a window to the half top or half bottom of a screen in gnome? I have found only how to do it left/right, but not top/bottom. Any ideas?

Where can I find gnome-shell error (or debug) log? I'm interested in mutter error/warning messages since I have a GLX problem I need to debug and I believe the key could be in gnome-shell's messages.

I want to create a very simple Desktop Environment using mutter or libmutter. I found out that mutter is a very simple wm but it can only be customized if I write a plugin for it. so I want to create a gnome-shell like plugin for mutter which would only tweak some window animation styles. but I am very new to creating such a thing so I would want to know how to get started. I would want it to be as simple as possible and possible in a single script file (as I want to tweak very little) .. also how do I compile it and make it to start like gnome-shell does.?