Candidates for removal (discussion)
- GNOME#Some_.27System_Settings.27_not_preserved - Poor language and doubles what's explained (more thoroughly) in Systemd. Should be rewritten and reference to Systemd
- GNOME#Extensions_do_not_work_after_GNOME_3_update - Advises people to skip version checks when extensions no longer load due to version incompatibility. I'm not sure this is something we should be telling users to do.
- I would also like to gather and give a private section to extensions. Currently that information is spread around the article, I think it deserves its own section within this article.
- We should move to working part of this section to GDM. Their is a on GDM-Page, necessary information is missing here (seems to be partially included on GDM-Page - this is the reason why I don't move it), lock-screen can now be configured through regular settings-UI in GNOME. Hoschi (talk) 16:43, 2 November 2013 (UTC)
- GNOME#Shutdown_via_the_status_menu - As of Gnome (3.6.2), this is no longer the case. Gnome has switched back to using Power Off in the menu.
- I see that the "Troubleshooting" section is bloated and requires cleanup. I support removal of material so as long that: It is proven to be irrelevant from this point forward, or condensed into notes/tips that are assimilated into the main article with external links for reference if need be. T1nk3r3r (talk) 21:18, 28 January 2013 (UTC)
- GNOME#Disable_Activity_hot_corner_hovering - As of GNOME Shell 3.8.3, this method doesn't work, as the mechanism of triggering "overview" display is updated and the old way is refered as "Fallback". A working hack may be to comment off
//this._pressureBarrier.connect('trigger', Lang.bind(this, this._toggleOverview));
- GNOME#Disable_Message_Tray_hovering - As of GNOME Shell 3.8.3, this method doesn't work for similar reason. A working hack may be to comment off
//Main.messageTray.openTray();Lns (talk) 06:09, 4 August 2013 (UTC)
GNOME and fontconfig settings
Since there isn't a section dedicated to fonts in GNOME 3 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: * https://bugzilla.novell.com/show_bug.cgi?id=217790• * https://bugzilla.gnome.org/show_bug.cgi?id=643704 */
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:
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> </match>
(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)
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)
- Link added, this probably deserves a section of its own now that extensions play such a vital role in GNOME. A future rewrite / restructure of this article may be needed. --stefanwilkens (talk) 23:52, 6 September 2012 (UTC)
Remove systemd configuration from 'Some 'System Settings' no preserved' section
I think that part of the 'Some 'System Settings' no preserved' section regarding switching to systemd should be removed and replaced with a link to systemd wiki. Systemd wiki explains migration more thoroughly and shows how to configure and administrate it.