[SOLVED] slackware current, typo in new rc.inet1, also is gtk3 now required for firefox?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Any pointers on how to tune the Gtk3 look? In particular, I'd like to switch back to "normal" scroll bar instead of this new thin one, and also my fonts in Firefox menus etc. are tiny now.
From an accessibility point of view it is absolutely shocking that Gtk-3 got away with those thin scrollbars. Huge titlebars, which you don't use, and tiny scrollbars, which you do use. Genius.
I patched this in the Firefox all.js so that the scrollbar behavior is the same as it was with GTK+ v2. Sorry, I meant to mention that in the ChangeLog.
Thanks Pat, I should have expected you were already on top of it.
I did have some old settings that could be used to change the width of the scrollbar, but it seems these have already been changed and deprecated, in true gtk3 fashion. So will have to look around.
FYI, Firefox no longer uses my KDE4 theme except for the title bar. How is it with Plasma 5?
It sounds like Gtk-3 has been influenced by the touch screen interface.
It's no better, the kde devs can't really do what they did for gtk2, building a theme engine that can duplicate their theme, and more importantly colors and shadows, because gtk3 has not been stable api, especially for themeing, it changes and breaks on almost every release. There is a breeze gtk3 theme for plasma 5, that just trys to create the basic look of breeze in gtk3, there was an oxygen gtk3 theme that was similar, but it is totally broken by gtk3 changes, and they can't really put the time into updating it. Neither of these will follow color theme or have menu shadows, and can easily break on any gtk3 update.
It's not just for Xfce 4 compatibility, you know. GTK 3 actually has proper HiDPI support, while GTK 2 does not.
I was more wondering about whether it was worth it for me to recompile for my personal needs, or was that pointless because this was and upstream change, which it seems its is. I was just thinking it could be for Xfce, which would be fine with me and understandable, and I would just recompile. Gtk3 has HiDpi, wayland support, and maybe better font rendering, these are also good reasons to change, for me personally most of these don't matter as much as constant theme breakage, and I need menu bar mnemonic underline on all the time without having to hit ALT to see them, which gtk3 got rid of as setting, though thankfully firefox overrides this somehow.
Last edited by pataphysician; 05-23-2017 at 04:49 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.