The issue is that I scaled my font using "Gnome Tweak" to 1.17. Apparently, the display doesn't like it when I scale my text to 1.17x of normal size.
I adjusted to 1.20 and everything fine now.
More than likely you have a swap problem.
Let's increase your /swapfile from 2G to 4G.
Note: Incorrect use of the dd command can cause data loss. Suggest copy/paste.
sudo swapoff -a # turn off swap
sudo rm -i /swapfile # remove old /swapfile
sudo dd if=/dev/zero of=/swapfile bs=1M count=4096
sudo chmod 600 /swapfile # set proper file ...
After raking my brains for days on end I've finally figured out that it has something to do with gnome extensions. I've restarted the machine with and without extensions turned on several times and the test is conclusive: every single time I have extensions turned on the desktop would fail to load.
Now it's about figuring out whether it's one in particular, ...
You can use Brightness Controller, a GUI frontend of xrandr, which supports multiple monitors.
sudo add-apt-repository ppa:apandada1/brightness-controller
sudo apt update
sudo apt install brightness-controller
Now you can select your primary and secondary monitor, and change their RGB color temperatures using the sliders. There is an option to save your ...
As detailed by @WinEunuuchs2Unix this is a boltd bug however I have found a usable workaround until a fix is backported to 20.04 Focal.
Install the Panel Indicators extension that moves the power/network icons to the status area and the 'cable-snake' will never appear.
Much better than a dancing ...
This wonderful Gnome Shell extension do the job:
and once installed you only use Super+i to invert 100% colors on the window currently focused!
In newer Gnome versions Comment and Terminal sections become mandatory so minimal .desktop file is now:
Name=Sample Application Name
Comment=A sample application
I turned my Wi-fi connection off and strangely everything worked fine. Turns out that MEGAsync, a cloud software, somehow causes gnome-shell to use all of my CPU's capacity. I reported a bug.
So this is not a "solution" to the problem, but a workaround.
It is not possible to have two workspaces displayed on a single screen, not in Gnome Shell and not in any other desktop environment I know.
An easy way to put your browser in half of the screen is to use the shortcut key Super+Left/right. This will tile the browser window on the left or right of your screen. With similar hotkeys, other applications can then ...
You can do this with the GNOME-Extension ShellTile
The simplest way to use the extension is to first, enable it by clicking the slider to set it one then holding down the Ctrl key, slide another window over the first (during which there will be a screen highlighting) after which release and the two windows will self position. The trick is to move windows ...
I found the cause of my issue. The Icon-Theme, Cupertino-Catalina-iCons, selected for the user account was causing the problem. When other icon-themes were selected, the abrupt user logout phenomenon did not occur.
I came to this discovery after googling org.gnome.Shell.desktop: mutter:ERROR:core/window.c:5332:get_default_window_icon: assertion failed:...
Based on my experience, there are 2 packages required:
Luckily, these 2 can be installed easily with the following command:
sudo apt install gnome-shell-extension-system-monitor gnome-tweaks
That's it, problem solved. No reboot required in my case.
Desktop icons are now provided by a Gnome Shell extension, which is still very new and underdevelopped.
A workaround is to navigate your icons in the file manager: they live in the "Desktop" folder.
If an active desktop is critical in your workflow, you better move to a desktop environment that fully supports them: Xubuntu, Kubuntu, ... Ubuntu uses ...
You can install the "Arc Menu" GNOME extension and use it as a replacement for a traditional menu.
Alternatively, if you are an Emacs user with "counsel" package installed. You can use counsel-linux-app command, preferably with Emacs service enabled, you can bind a command like this to Alt-F1:
# try to ultilize Emacs server if it's ...
The image is known as a cable snake:
From the author's blog:
The GNOME shell bits to enable Thunderbolt 3 support were merged some
time ago and made it into 3.28. This means that the GNOME shell will
act as authorization agent and will automatically authorize new
thunderbolt 3 devices — if the user has administrator rights, is
currently logged ...
Do you have installed any power managment software like tlp or powertop?
I had the same situation with ThinkPad TB3 dock station. After investigation I found that problem was with auto suspending one of the dock station USB devices. So I added this device to the blacklist for tlp and the problem is gone.
I'm not sure that it's only UX problem. For me it's a ...
Just in case anybody has a similar issue, I had CPU usage of 80% consistently from GNOME Shell and I switched the various extensions off for testing, on version 20.04.
It turned out I had the performance monitor in the top right hand side bar (system load monitor) - once that was quit, everything was back to normal. If anybody has any suggestions how to ...
Disclaimer - I will post some information even though it's not the solution for the problem but maybe others can pitch in and provide more information to find the solution.
The process causing appearing is boltd/boltctl. As in
Dumitru Alexandru Surdu's answer is described you can check what's happening with boltctl monitor. You will message Probing started ...
Okay I "fixed" the problem. It was related to an activated Hyper-V feature. After turning this off it works. Theoretically VirtualBox shall support Hyper-V since version 6. But it looks like it was not working as expected.
I experience this too, with fresh Ubuntu 20.04 installation. I see the root cause of this was found ( https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440 ).
I can offer my workaround: add to autostart a trivial command that explicitly sets the "text scaling factor" after login. This change will be correctly noticed by the GNOME shell, ...
The bug is related to the "panel mode" option. Disabling it restores scrolling in overview, like mentioned here.
As Ubuntu Dock is based on the dash to dock extension, my solution was to disable Ubuntu dock and install Dash to Dock and disable panel mode from there. It has plenty of other useful settings.