- edit /etc/default/grub, set grub_timeout to 0. Run update-grub so the change sticks.
This removes the ticking 5s timer at bootup. I never use the other boot entries anyway, and if the system fails to boot, I troubleshoot from a live system.
- Create ~/.config/gtk-3.0/settings.ini and add:
[Settings]
gtk-primary-button-warps-slider = false
This makes it so when you click on a scrollbar below or above the slider, it moves down or up by one page, not to where you clicked.
- edit /etc/environment (it’s empty), add a line with: MOZ_ENABLE_WAYLAND=1
This forces firefox to use Wayland, which makes scrolling much smoother and text look better.
There’s a bunch more, but these are the first I always do so I don’t get mad. What are yours?
Isn’t option 2 the default on Windows? I never understood the rationale behind this behavior. When I click on anywhere on the scrollbar I expect it to jump where I clicked on it. Unfortunately when I’m forced to use Windows it makes the clicking on the scrollbar useless to me, and it forces me to drag the scrollbar where I want it to go - I much prefer Gnome’s default behavior. I’m curious, if you are willing to say, how is this feature useful to you?
It’s just what I’m used to, I guess.
That way I don’t have to hit an exact spot on the bar. I can just move the mouse to the right and click anywhere, and it’ll scroll down one page to keep reading.
I never need to jump to a point in a document and can accurately guess what point on the scrollbar that corresponds to. So the default behavior is useless to me.What desktop are you using where this file exists? I don’t have a settings.ini in either the gtk-3.0 nor gtk-2.0 folders.
I created it. But I just noticed, it doesn’t do what it used to do anymore.
Apparently, with Debians move to GTK4 this fix is outdated.OK but Debian has numerous desktop interfaces available. Are you saying this works with every desktop that uses GTK3, or does it just work with the specific one that you chose to install?
It’s worked with Gnome and Xfce in the past.
I can imagine it being useful as a page down key but without having to press the page down key on your keyboard? I prefer the gnome implementation as well but above all else I prefer people having the choice.
What I never understood about the “windows” implementation is if the page cut a line in half and you go down one page the line is still cut in half on the top of the page meaning you have to scroll around anyway.
Here are some of mine:
- Get changelogs and bugs on upgrades:
apt install apt-listchanges apt-listbugs reportbug
- Install apt-file to search inside packages:
apt install -y apt-file apt-file update
- Since I do all my update through CLI, I remove the software center packages and other extras
apt remove gnome-games gnome-software gnome-software-common
- To make my computer more “normal” I do install plymouth
apt install plymouth plymouth-themes plymouth-set-default-theme -R spinner
I also make sure an SSH agent is running in my desktop session so I don’t have to type out my key passphrase I connect to something.
I never knew about apt-file! Thanks!
Great tips, thanks!
- Add myself to the sudoers group:
sudo usermod -a -G sudo myusername
- Updated my sources list to include
main contrib non-free non-free-firmware
- Enable multi-arch (for Steam):
sudo dpkg --add-architecture i386
I use KDE and something that annoys me is that file explorers launch files on single click, so I always have to change that to double click in System Settings.
- Add myself to the sudoers group:
I’m a newby… does 3. work with Firefox as a flatpak install?
You can use an override for the flatpak:
sudo flatpak override --env MOZ_ENABLE_WAYLAND=1 org.mozilla.firefox
Thanks, man! Not only is scrolling so much smoother, but Youtube also stopped dropping frames like crazy, which it did before and which I just couldn’t find a fix for. It’s smootheness all around :)
Awesome! Make sure you have the ffmpeg-full flatpak runtime installed as well. On my Intel GPU video playback is pretty buggy without it.
Thank you!
I don’t know, I’m not familiar with how flatpaks work in detail.
IMHO - MOZ_ENABLE_WAYLAND=1 should go to your ~/.bashrc or similar, but not to global environment file.
It’s something I want for all users, so why not?
I for one had to boot another grub option just the other day. Some kernel headers missmatch issue. Still not sure if it was my fault or not. I guess I could just blame Nvidia, which is always a smart thing to do.
I install tmux, doas, neofetch, flatpak, pip, IBM Plex fonts, Plymouth and Linux firmware.
Set grub timeout to 0.
Add my user to the sudo group.
Remove kdepim*, libreoffice*, Firefox, Thunderbird, okular, dragonplayer, gimp.
Install those apps plus everything else I run from Flathub.
Add the repo for Signal and Chrome and install those apps as well.
Get rid of the dumb stuff KDE does like single click in the file manager, popup notifications for everything, slow animations. I set up sloppy focus, and install a proper taskbar.
Go to work.
Install a common list of basepackages like ripgrep and empty out motd