Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Just annotations of little "how to's", so I know I can find how to do something I've already done when I need to do it again, in case I don't remember anymore, which is not unlikely. Hopefully they can be useful to others, but I can't guarantee that it will work, or that it won't even make things worse.
I mostly use the scrollbar as "buttons," clicking below or above the handler, rather than grabbing the handler itself. So when I've scrolled down quite a bit, I'll often mistakenly click above the handler when I really wanted to scroll down. That's kind of possibly solved if those barely useful up and down buttons were large enough to be more useful than pressing page up, down, or arrow keys instead. So this usercss does that:
This way: Open the profile folder, find the JSON file Preferences, find "printing" field (browser->extensions->printing), then add , "enabled": false into it.
I'm not aware of there being something like a "gtk-3.0-settings.d" to preserve settings.ini options between theme changes (including involuntary ones), so that's a work-around method, adding that to the session auto-start script:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.