Difference between revisions of "Talk:GNOME"

From ArchWiki
Jump to navigation Jump to search
(add discussion)
Line 78: Line 78:
  
 
No reasons are given. Has anyone got any evidence to back this up? -- [[User:Chazza|Chazza]] ([[User talk:Chazza|talk]]) 10:23, 15 May 2015 (UTC)
 
No reasons are given. Has anyone got any evidence to back this up? -- [[User:Chazza|Chazza]] ([[User talk:Chazza|talk]]) 10:23, 15 May 2015 (UTC)
 +
 +
== GNOME 3.16 failing to start without gnome-control-center ==
 +
 +
When I tried GNOME 3.16 on a virtual machine with the latest updates, it failed to start, and showed the "Oh no! Something has gone wrong" screen. However, once I had installed gnome-control-center, it started successfully.
 +
 +
On further investigation, it would seem that it is not gnome-control-center itself that is required, but rather one of its dependencies. Is this a general problem, or does it only occur on specific setups? -- [[User:Adlo|Adlo]] ([[User talk:Adlo|talk]]) 14:10, 20 May 2015 (UTC)

Revision as of 14:10, 20 May 2015

GNOME applications blocking window manager keyboard shortcuts? Drawing over everything?

Seen on Fluxbox, using evince, totem, baobab.(as of 3.14.1-2, 3.14.1-1, 3.14.1-1, well, earlier) Makes these programs near-useless.Jasper1984 (talk) 15:31, 8 December 2014 (UTC)

I believe this is not just about GNOME, but all GTK+ and Qt applications [1] [2]. Haven't read through the reports, but it appears to be some flaw in Xorg. Not much we can do about this, so unless you want to discuss a workaround this can be closed. -- Alad (talk) 19:50, 8 December 2014 (UTC)
Can you confirm this with another toolkit than GTK3 ? -- Alad (talk) 17:35, 10 January 2015 (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:

org.gnome.desktop.interface.text-scaling-factor

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>
</match>

(to be finished, please comment or fix) —This unsigned comment is by Erm67 (talk) 23:58, 8 January 2012‎. Please sign your posts with ~~~~!

I think that info must be in Font configuration, linked from there if needed -- Kycok (talk) 10:57, 3 June 2014 (UTC)
Well, it is very GNOME specific and complex at the same time. I would vote for putting it into GNOME tips and crosslink it from GNOME#Fonts as well as from Font configuration. But first: Above contribution of Erm67 is a couple of years back. Does someone know whether the instructions still work like that? --Indigo (talk) 09:04, 10 November 2014 (UTC)
Update to note: GNOME tips was cleaned up removing GNOME content after I suggested above. It does not make sense to put these instructions there anymore. --Indigo (talk) 12:41, 15 January 2015 (UTC)

ownCloud Integration

I noticed missing ownCloud functionality in some GNOME applications (Nautilus & Documents) if gfvs-goa is not installed. I am not sure what else is affected or how exactly this works. I also didn't find any mention on the File manager functionality nor the GVFS pages. I was thinking of contributing to the Troubleshooting section but I do not know enough about the topic or wiki editing. Beanaroo (talk) 09:21, 3 June 2014 (UTC)

Candidate for GNOME#Online accounts perhaps? -- Chazza (talk) 14:54, 19 November 2014 (UTC)

Tear-free video with Intel HD Graphics

From the deletion template: As of 2015-02-16, the following workaround doesn't solve tearing problems (e.g. fullscreen video) anymore when Intel TearFree option does.

No reasons are given. Has anyone got any evidence to back this up? -- Chazza (talk) 10:23, 15 May 2015 (UTC)

GNOME 3.16 failing to start without gnome-control-center

When I tried GNOME 3.16 on a virtual machine with the latest updates, it failed to start, and showed the "Oh no! Something has gone wrong" screen. However, once I had installed gnome-control-center, it started successfully.

On further investigation, it would seem that it is not gnome-control-center itself that is required, but rather one of its dependencies. Is this a general problem, or does it only occur on specific setups? -- Adlo (talk) 14:10, 20 May 2015 (UTC)