From ArchWiki
Revision as of 17:38, 31 August 2012 by Stefanwilkens (Talk | contribs) (Gnome and Systemd: Invalid argument on my side, removing.)

Jump to: navigation, search

Gnome and fontconfig settings

Since there isn't a section dedicated to fonts in gnome3 I was thinking about writing one, but I put it here first:

Gnome doesn't use the dpi settings set by xorg server to scale fonts, instead it uses a fixed dpi of 96 that cannot be changed unlike previous versions:

/* As we cannot rely on the X server giving us good DPI information, and
 * that we don't want multi-monitor screens to have different DPIs (thus
 * different text sizes), we'll hard-code the value of the DPI
 * See also:

The gnome-settings-daemon plugin xsettings relies on this hardcoded value for some calculations and there is currently no way of changing it beside customizing the code in abs. The dimension of text can be tweaked changing the text-scaling-factor (1.0 by default), using gnome-tweak-tool or editing the following key in dconf-editor:


The xsettings plugins will also merge some Xft values in the X resources db overwriting values set in .Xresources od .Xdefaults files. The defaults are:

Xft.antialias:	1
Xft.dpi:	96
Xft.hinting:	1
Xft.hintstyle:	hintmedium
Xft.lcdfilter:	lcddefault
Xft.rgba:	none

Some of those values can be changed using dconf-editor (org.gnome.settings-daemon.plugins.xsettings) or gnome-tweak-tool. It is possible to change this values using xrdb -merge ~/.Xresources after gnome is started but gnome will still use its values internally so it is not a good idea.

It is a good idea to configure your fonts.conf in a way consistent with the gnome settings otherwise, at least on my laptop, fonts will looks weird in some gnome apps.

The dpi setting of the Xserver can be changed to 96 following this guide, this way it will be the same for all applications, the drawback is that fonts might look too small or too big in other application if the real DPI of your monitor differs too much from 96.

For and LCD monitor it is a good idea to activate the lcd filter setting the following keys in dconf-editor:

org.gnome.settings-daemon.plugins.xsettings.antialiasing rgba
org.gnome.settings-daemon.plugins.xsettings.rgba-order rgb, bgr, vrgb or vbgr (as your monitor requires)

Since the lcdfilter is not designed to work together with autohinting it is a good idea to disable it also in fonts.conf. It is also a good idea to use the same hinting value as in your font.conf, the default in gnome is medium:

org.gnome.settings-daemon.plugins.xsettings.hinting medium

This values in fonts.conf will match the gnome settings:

<match target="font">
 <edit mode="assign" name="rgba"><const>rgb</const></edit>
 <edit mode="assign" name="autohint"><bool>false</bool></edit>
 <edit mode="assign" name="hinting"><bool>true</bool></edit>
 <edit mode="assign" name="hintstyle"><const>hintmedium</const></edit>
 <edit mode="assign" name="antialias"><bool>true</bool></edit>
 <edit mode="assign" name="lcdfilter"><const>lcddefault</const></edit>

(to be finished, please comment or fix)

deleted manual hotkeys modification

Manual edit of accel.scm into nautilus config doesn't fit with this page. And this can't be a generic method, cause not every application has an accels.scm file, even if it has that, it's location in ~/.config is not mandatory. 4javier 08:09, 25 April 2011 (EDT)

It fits with this page just as much as the remaining part on changing hotkeys does because both serve the same purpose. So I disagree with that it should be downright deleted, particularly as for me (thus possibly others) the can-change-accels way did not work. I added it again (a bit more carefully phrased) to the "Troubleshooting" section. -- Misc 15:40, 25 April 2011 (EDT)
I still think that applications' specific method of changing accels should be mentioned in the application page itself. Into this page I'd leave just a reminder (i.e. "If this method doesn't work see application's wiki page for app specific file"). But I don't delete it anymore until somebody else tell us his opinion. 4javier 20:35, 25 April 2011 (EDT)

Seamonkey and Pulseaudio

  1. I cant setup seamonkey as default webbrowser.. This is imposible in gnome-control-center without some modyfication.. Google give nothing special, only garbage.
  2. I have "Audigy2 value" and ld10k1 from alsa-tools. How can I do this to work in 5.1? (If you have that problem or/and you know what do, tell me..) Can I disable pa and where? :)

3ED 10:03, 1 May 2011 (EDT)

Resizing titlebar in user configuration

Should not be better point that sed manipulation to ~/.themes/Adwaita/metacity-1/metacity-theme-3.xml ? --4javier 07:27, 7 May 2011 (EDT)

Good idea. Sed is not really needed here. I changed it to direct instruction. --Fengchao (talk) 07:11, 29 May 2012 (UTC)
Well done making the edit request more explicit, however I think 4javier was wondering if suggesting a per-user configuration would be more appropriate (~/.themes/... instead of /usr/share/themes/...), reopening this :) I don't use GNOME so I can't test it at the moment. -- Kynikos (talk) 10:10, 30 May 2012 (UTC)

Xmonad section

I think xmonad section should be generalized for every other wm: openbox, fluxbox, ratpoison etc. Is there some gnome3 user who can test the method with other wm than xmonad? --4javier 05:40, 16 May 2011 (EDT)

«You must install the gnome group»

This sentence is written in bold characters in the Installation section. I don't agree: I really don't want to install Epiphany in my system and I really don't want install gnome-applets in my system. These (and others) are not fundamental components of the Gnome DE, so IMHO they have to be moved in gnome-extra or their function has to be explained in the wiki, so people can choose which of them install. What you think about it? Mons 04:53, 29 December 2011 (EST)

Definitely, that section must be rewritten in a more neutral way, giving the readers all the information they need to make their own unbiased decisions. It should also make use of Template:Grp to provide quick links to the package lists (gnome, gnome-extra - unfortunately this template is i686-centric) and should avoid giving examples of how to install (groups of) packages with pacman, in accordance to Help:Style#Official packages. -- Kynikos 06:44, 30 December 2011 (EST)

Add link to official extensions site

I think to add a link to, also in order to easy manage the extensions in the browser from the /local page. --Gimmy 05:22, 23 January 2012 (EST)

Hiding icons in the top bar

This used to be a link to gnome-shell-extension-noa11y-gitAUR. As far as I can tell, it was replaced with instructions for doing manually what the shell-extension does automatically. The upside is it apparently works for any of the tray icons without having to install an extension. The downside is it's more cumbersome to toggle it on and off. Also, I'm not sure if there are any bugs introduced by the manual method that have been worked out by the people writing the extension. We could include mention of the AUR package, at least as an alternate method. -Emiralle (talk) 23:45, 8 July 2012 (UTC)

It's in the Arch Way to leave the choice to the end user, so mentioning the old (removed) method [1] as an alternative would probably be the best thing to do. -- Kynikos (talk) 11:24, 9 July 2012 (UTC)
I took a first stab at replacing the info on the AUR packages. A couple of concerns remaining:
  1. There used to be instructions for creating a GNOME shell extension based on gnome-shell-extension-noa11y-gitAUR to remove the bluetooth icon. I didn't bring it back (though I mention the idea) because I don't think it belongs in the wiki. One can always submit such a thing to the AUR where it can be properly tested and maintained.
  2. I think there's a problem with the code for /usr/share/gnome-shell/js/ui/panel.js. It has bluetooth under STANDARD_STATUS_AREA_ORDER, so it should probably have a corresponding entry under STANDARD_STATUS_AREA_SHELL_IMPLEMENTATION. But I'm not a GNOME user, so I can't check the file myself.
--Emiralle (talk) 00:24, 12 July 2012 (UTC)
Good job Emiralle! I agree on point (1) and about (2) I too guess that a 'bluetooth' entry is missing, but that's something that the next GNOME user using that trick can notice and fix, I'm closing this discussion. -- Kynikos (talk) 09:51, 13 July 2012 (UTC)