[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.
slackware current, typo in new rc.inet1, also is gtk3 now required for firefox?
There is a typo in the new rc.inet1 script the changelog say that it was updated to dhcp timeout of 15 seconds, but it seems to only have changed the echo statement for the logger, the actual timeout is still 10 seconds.
Also its seems that firefox is now built with gtk3, is this because it has to be? or is this for xfce integration?
The compile line for firefox is actually correct as cairo-gtk3, that is not my problem. This is the first time Patrick has used gtk3 instead of gtk2, both options have been available for awhile in firefox, and I was wondering if now firefox is only going to allow being built with gtk3, or if this was a decision by Patrick to maybe fit better with changes in xfce switch to gtk3?
Yes 15 seconds is fine, I was just reporting that it actually wasn't changed like Patrick wanted, because he only changed it in the echo for the logger and not in the line that actually executes the timeout, which is still at 10 seconds.
The compile line for firefox is actually correct as cairo-gtk3, that is not my problem. This is the first time Patrick has used gtk3 instead of gtk2, both options have been available for awhile in firefox, and I was wondering if now firefox is only going to allow being built with gtk3, or if this was a decision by Patrick to maybe fit better with changes in xfce switch to gtk3?
firefox from version 53.x won't support gtk+2 anymore: I guess this is a test as the next versions will forcibly use gtk+3 so it's better to check if it's all ok with the switch.
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.
Well that sucks, but save me from bothering with recompiling, I guess theme breakage here we come. It seems at least firefox menus still show mnemonic underline without first hitting ALT, even though gtk3 made this impossible.
As far as font change for gtk3
you can edit .config/gtk-3.0/settings.ini
and change
gtk-font-name=
to whatever font and point size you want, I use Plasma 5 so not sure how that works with XFCE or KDE4
For scroll bars you will need to change your theme, if you have a theme that has stuff for both gtk2 and gtk3 they should have similar scroll bars, but if your theme is gtk2 only you will get Adwaita for gtk3, you can override this with
gtk-theme-name=
in the same settings.ini
the name will have to be of a gtk3 theme though, also theme that aren't Adwaita have a tendency to break with each new gtk3 version, though gtk are now claiming this won't happen, I'll believe it when I see it.
Last edited by pataphysician; 05-23-2017 at 01:51 PM.
Thanks for the quick reply. Indeed, I fixed the font and changed the theme the way you suggested. It seems that Slackware-current has five Gtk3 themes: Default, Emacs, HighContrast, Adwaita and Adwaita-dark, but none of them seem to have "regular" toolbar with arrows, so I guess I'll have to live with the new one for while.
Thanks for the quick reply. Indeed, I fixed the font and changed the theme the way you suggested. It seems that Slackware-current has five Gtk3 themes: Default, Emacs, HighContrast, Adwaita and Adwaita-dark, but none of them seem to have "regular" toolbar with arrows, so I guess I'll have to live with the new one for while.
There are some gtk3 themes up on slackbuild.org, Xfce is slowly moving to gtk3, so I assume at some point there will be more gtk3 themes in current.
GTK3 has been in the Firefox release channel for about a year and had to put the following in my ~/.config/gtk-3.0/settings.ini file to make the scrollbar function more normally.
Setting gtk-primary-button-warps-slider to false returns the normal one screen up/one screen down click behavior to the scroll bar (instead of jumping to the spot on the screen where the mouse click occurs).
Setting gtk-primary-button-warps-slider to false returns the normal one screen up/one screen down click behavior to the scroll bar (instead of jumping to the spot on the screen where the mouse click occurs).
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.
GTK3 has been in the Firefox release channel for about a year and had to put the following in my ~/.config/gtk-3.0/settings.ini file to make the scrollbar function more normally.
Setting gtk-primary-button-warps-slider to false returns the normal one screen up/one screen down click behavior to the scroll bar (instead of jumping to the spot on the screen where the mouse click occurs).
for that looks like Pat opted to directly patch the default behaviour in the build script
Code:
--- ./modules/libpref/init/all.js.orig 2017-04-10 21:13:21.000000000 -0500
+++ ./modules/libpref/init/all.js 2017-05-21 15:29:42.803757223 -0500
@@ -235,6 +235,9 @@
// If true, all popups won't hide automatically on blur
pref("ui.popup.disable_autohide", false);
+// Default to GTK+ v2 type scrolling:
+pref("ui.scrollToClick", 0);
+
pref("browser.display.use_document_fonts", 1); // 0 = never, 1 = quick, 2 = always
// 0 = default: always, except in high contrast mode
// 1 = always
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.