Difference between revisions of "Talk:GNOME"

From ArchWiki
Jump to: navigation, search
(Remove systemd configuration from 'Some 'System Settings' no preserved' section)
m (Additional Necessary dependencies for the Printers Section in the Settings App: add the strikethrough)
 
(191 intermediate revisions by 23 users not shown)
Line 1: Line 1:
== Installation ==
+
== GNOME applications blocking window manager keyboard shortcuts? Drawing over everything? ==
Being that {{ic| pacman -S gnome}} produces a numbered list, wouldn't be prudent to specify packages that are ''critical'' for a workable desktop? [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 21:00, 28 January 2013 (UTC)
+
  
== Candidates for removal (discussion) ==
+
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.[[User:Jasper1984|Jasper1984]] ([[User talk:Jasper1984|talk]]) 15:31, 8 December 2014 (UTC)
  
* [[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]]
+
:I believe this is not just about GNOME, but all [[GTK+]] and [[Qt]] applications [https://bugzilla.gnome.org/show_bug.cgi?id=344059] [https://bugs.kde.org/show_bug.cgi?id=70063]. 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. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 19:50, 8 December 2014 (UTC)
  
* [[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.
+
:Can you confirm this with another toolkit than GTK3 ? -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:35, 10 January 2015 (UTC)
 
+
* [[GNOME#Login_screen]] - GDM is not part of clean GNOME, should we add this to [[GDM]] in stead?
+
:: +1. I think this part is created before [[GDM]] exist. Merge request added. -- [[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 09:33, 14 September 2012 (UTC)
+
 
+
:: 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.
+
 
+
:: +1 Added clarity to merge tag. [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 21:18, 28 January 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.  [[User:T1nk3r3r|T1nk3r3r]] ([[User talk: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
+
{{hc|/usr/share/gnome-shell/js/ui/layout.js|<nowiki>
+
        //this._pressureBarrier.connect('trigger', Lang.bind(this, this._toggleOverview));
+
</nowiki>}}
+
 
+
*[[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
+
{{hc|/usr/share/gnome-shell/js/ui/layout.js|<nowiki>
+
        //Main.messageTray.openTray();
+
</nowiki>}} [[User:Lns|Lns]] ([[User talk:Lns|talk]]) 06:09, 4 August 2013 (UTC)
+
  
 
== GNOME and fontconfig settings ==
 
== GNOME and fontconfig settings ==
Line 84: Line 62:
 
  </match>
 
  </match>
  
 +
(to be finished, please comment or fix) {{Unsigned|23:58, 8 January 2012‎|Erm67}}
 +
 +
:I think that info must be in [[Font configuration]], linked from there if needed -- [[User:Kycok|Kycok]] ([[User talk: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? --[[User:Indigo|Indigo]] ([[User talk: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. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 12:41, 15 January 2015 (UTC)
 +
 +
== Tear-free video with Intel HD Graphics /  Xorg Intel TearFree option ==
 +
 +
In the wiki article is explained, that the Xorg Intel TearFree option has the following disadvantages:
 +
''"However, the way this option acts makes it redundant with the use of a compositor (it increases memory consumption and lowers performance, ..."''
  
(to be finished, please comment or fix)
+
As far as I understand this is not true anymore.
  
== deleted manual hotkeys modification ==
+
man intel (see [http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/tree/man/intel.man]) says the following:
  
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.
+
".BI "Option \*qTearFree\*q \*q" boolean \*q
[[User:4javier|4javier]] 08:09, 25 April 2011 (EDT)
+
Disable or enable TearFree updates. This option forces X to perform all
 +
rendering to a backbuffer prior to updating the actual display. It requires
 +
an extra memory allocation the same size as a framebuffer, the occasional extra
 +
copy, and requires Damage tracking. Thus enabling TearFree requires more
 +
memory and is slower (reduced throughput) and introduces a small amount of
 +
output latency, but it should not impact input latency. However, the update to
 +
the screen is then performed synchronously with the vertical refresh of the
 +
display so that the entire update is completed before the display starts its
 +
refresh. That is only one frame is ever visible, preventing an unsightly tear
 +
between two visible and differing frames. Note that this replicates what the
 +
compositing manager should be doing, however TearFree will redirect the
 +
compositor updates (and those of fullscreen games) directly on to the scanout
 +
thus incurring no additional overhead in the composited case. Also note that
 +
not all compositing managers prevent tearing, and if the outputs are
 +
rotated, there will still be tearing without TearFree enabled.
 +
.IP
 +
Default: TearFree is disabled."
  
: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. -- [[User:Misc|Misc]] 15:40, 25 April 2011 (EDT)
+
At the beginning these disadvantages did exist, but later these option was improved and the description in the manpage was updatet:
 +
[[http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/man/intel.man?id=0ebcef4f2ebe82e9b90589aa4266a9228e2b5fdb]]
  
::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. [[User:4javier|4javier]] 20:35, 25 April 2011 (EDT)
+
Am I right or did I understand something wrong? --[[User:Aluser1137|Aluser1137]] ([[User talk:Aluser1137|talk]]) 15:31, 16 January 2016 (UTC)
  
:::Perhaps update [[Nautilus]] and reference it? Perhaps simply add that article to the related articles? --[[User:Stefanwilkens|stefanwilkens]] ([[User talk:Stefanwilkens|talk]]) 23:33, 6 September 2012 (UTC)
+
::'''''Note that this replicates what the compositing manager should be doing, however TearFree will redirect the compositor updates (and those of fullscreen games) directly on to the scanout thus incurring no additional overhead in the composited case.'''''
  
== Xmonad section ==
+
::'''''Thus enabling TearFree requires more memory and is slower (reduced throughput) and introduces a small amount of output latency, but it should not impact input latency.'''''
  
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? --[[User:4javier|4javier]] 05:40, 16 May 2011 (EDT)
+
::My assumption from reading this is that TearFree will lower performance but that using a compositor won't make things worse. We could delete the following words from the sentence in question: ''"makes it redundant with the use of a compositor (it"''
 +
::-- [[User:Chazza|Chazza]] ([[User talk:Chazza|talk]]) 16:20, 29 November 2016 (UTC)
  
== Add link to official extensions site ==
+
== <s>Additional Necessary dependencies for the Printers Section in the Settings App</s> ==
  
I think to add a link to [https://extensions.gnome.org/ extensions.gnome.org], also in order to easy manage the extensions in the browser from the [https://extensions.gnome.org/local/ /local] page. --[[User:Gimmy|Gimmy]] 05:22, 23 January 2012 (EST)
+
I noticed that Printers section needed <code>system-config-printer</code> in order to install the printer through the GUI but it is never mentioned in the Gnome Wiki. Without this, it will always say that it is not able to install the printer driver whenever you try to install the printer.
: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. --[[User:Stefanwilkens|stefanwilkens]] ([[User talk:Stefanwilkens|talk]]) 23:52, 6 September 2012 (UTC)
+
  
== Remove systemd configuration from 'Some 'System Settings' no preserved' section ==
+
[[User:CuriousTommy|CuriousTommy]] ([[User talk:CuriousTommy|talk]]) 16:26, 7 April 2016 (UTC)
  
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.
+
:{{Pkg|system-config-printer}} is listed as an optional dependency of {{Pkg|gnome-control-center}} which provides the GNOME settings panel. Closing. -- [[User:Chazza|Chazza]] ([[User talk:Chazza|talk]]) 16:13, 6 December 2016 (UTC)
:: This entire section can be removed IMO, SystemD has been the default for long enough. Objections? --[[User:Stefanwilkens|stefanwilkens]] ([[User talk:Stefanwilkens|talk]]) 20:55, 14 October 2013 (UTC)
+

Latest revision as of 16:13, 6 December 2016

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)

Tear-free video with Intel HD Graphics / Xorg Intel TearFree option

In the wiki article is explained, that the Xorg Intel TearFree option has the following disadvantages: "However, the way this option acts makes it redundant with the use of a compositor (it increases memory consumption and lowers performance, ..."

As far as I understand this is not true anymore.

man intel (see [3]) says the following:

".BI "Option \*qTearFree\*q \*q" boolean \*q Disable or enable TearFree updates. This option forces X to perform all rendering to a backbuffer prior to updating the actual display. It requires an extra memory allocation the same size as a framebuffer, the occasional extra copy, and requires Damage tracking. Thus enabling TearFree requires more memory and is slower (reduced throughput) and introduces a small amount of output latency, but it should not impact input latency. However, the update to the screen is then performed synchronously with the vertical refresh of the display so that the entire update is completed before the display starts its refresh. That is only one frame is ever visible, preventing an unsightly tear between two visible and differing frames. Note that this replicates what the compositing manager should be doing, however TearFree will redirect the compositor updates (and those of fullscreen games) directly on to the scanout thus incurring no additional overhead in the composited case. Also note that not all compositing managers prevent tearing, and if the outputs are rotated, there will still be tearing without TearFree enabled. .IP Default: TearFree is disabled."

At the beginning these disadvantages did exist, but later these option was improved and the description in the manpage was updatet: [[4]]

Am I right or did I understand something wrong? --Aluser1137 (talk) 15:31, 16 January 2016 (UTC)

Note that this replicates what the compositing manager should be doing, however TearFree will redirect the compositor updates (and those of fullscreen games) directly on to the scanout thus incurring no additional overhead in the composited case.
Thus enabling TearFree requires more memory and is slower (reduced throughput) and introduces a small amount of output latency, but it should not impact input latency.
My assumption from reading this is that TearFree will lower performance but that using a compositor won't make things worse. We could delete the following words from the sentence in question: "makes it redundant with the use of a compositor (it"
-- Chazza (talk) 16:20, 29 November 2016 (UTC)

Additional Necessary dependencies for the Printers Section in the Settings App

I noticed that Printers section needed system-config-printer in order to install the printer through the GUI but it is never mentioned in the Gnome Wiki. Without this, it will always say that it is not able to install the printer driver whenever you try to install the printer.

CuriousTommy (talk) 16:26, 7 April 2016 (UTC)

system-config-printer is listed as an optional dependency of gnome-control-center which provides the GNOME settings panel. Closing. -- Chazza (talk) 16:13, 6 December 2016 (UTC)