By default, Alt+Tab switches between applications, not windows, in GNOME 3. The companion shortcut, which allows to switch brtween multiple windows of that application, depends on the keyboard layout and is usually Alt+`. Of course, you could also navigate to a window graphically with arrow keys while the Alt+Tab is pressed.
The extension "Alt Tab: ...
In the following reddit thread one can find a solution that worked for me. Basically, there you can find in detail instruction to switch from Light-locker to XScreenSaver.
User ID: u/EMH_Mark_I
To avoid this issue with GNOME Boxes, I had to configure Guix System to add my user account to the libvirt group and enable the virtlog and libvirt system services as below.
(users (append (list (user-account
If anyone came here looking for a way to fix tiny text on Anaconda Navigator, here's what ended up working for me:
This page says:
If you have multiple screens of differing DPI, you may need to do QT_SCREEN_SCALE_FACTORS="2;2"
I have multiple screens, so I tried it and it worked; none of the methods discussed above did anything in this case.
I've reported the bug here: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3421
I also found a workaround:
Inside /usr/share/X11/xorg.conf.d/40-libinput.conf add this line:
Option "NaturalScrolling" "on"
right above the line Driver "libinput"
Reboot and test again.
This issue took me a lot of time. finally this doc saved me: https://help.ubuntu.com/community/VNC/Servers
I use debian 10 with gnome installed. I use tigervnc as vnc server.
#install vnc servrer
sudo apt install tigervnc-standalone-server
#start vncserver and allow remote login
vncserver -localhost no :1
#check the port listen stat
netstat -tul | grep 5901
From your log:
/usr/libexec/gdm-x-session: (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
/usr/libexec/gdm-x-session: (EE) NVIDIA: system's kernel log for additional error messages and
/usr/libexec/gdm-x-session: (EE) NVIDIA: consult the NVIDIA README for details.
/usr/libexec/gdm-x-session: (EE) No ...
I use a custom Fedora-based distro that uses Elogind+Eudev instead of SystemD, so GDM is not an option as screenlocker. My solution was using cinnamon-screensaver and a python3 script based on the (deprecated) python2 script posted by aseq.
Save this as /etc/xdg/autostart/gnome-shell-screenlock.desktop:
Name=GNOME Shell ...
I see the same issue with a Logitech M325 mouse. This is NOT a Bluetooth mouse; it uses the Logitech Unifying Receiver.
So I don't think it's a Bluetooth-related issue, but more likely something to do with GNOME and its underlying architecture for storing and applying hardware configuration settings.
Interestingly, this issue doesn't affect the touchpad on ...
Nothing happens magically.
Probably a software upgrade has introduced this weird behaviour. That's take a look to your pacman.log and try to downgrade inducted packages.
Instead, if you have changed any configuration option, try to login with a new user (this is the easier way to clean your $HOME/.config) to check if the issue still happens.
Best way, IMHO, is to forget about gnome-terminal. Install mate-terminal instead, which is a clone of the old gnome-terminal, and it retains the good stuff like ability to name the tabs...
Here's my startup script, which creates three named tabs, and each could be in a different directory...
GNOME Boxes uses QEMU under the hood. By default, it "emulates" a network for the guest, where it simply "passes through" on the guest the same Internet access capabilities that the host has. The host itself can be accessed by the IP address of the default gateway, which is 10.0.2.2 by default. The guest should be able to access the ...
On debian/kali please check following:
in /etc/default/bluetooth BLUETOOTH_ENABLED=0
in /etc/bluetooth/main.conf AutoEnable=false
and if you have blueman-applet, check it's plugin PowerManager settings
If you're using an apple keyboard the problem might be the keyboard not linux. You need to press the "clear" key which is top left of the numeric keyboard to enable numlock. This worked for me on Fedora.