Difference between revisions of "Talk:GNOME"

From ArchWiki
Jump to navigation Jump to search
m (signed post)
 
(282 intermediate revisions by 36 users not shown)
Line 1: Line 1:
== Gnome and fontconfig settings ==
+
== GNOME applications blocking window manager keyboard shortcuts? Drawing over everything? ==
  
Since there isn't a section dedicated to fonts in gnome3 I was thinking about writing one, but I put it here first:
+
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 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:
+
: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)
 +
 
 +
:Can you confirm this with another toolkit than GTK3 ? -- [[User:Alad|Alad]] ([[User talk: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
 
  /* As we cannot rely on the X server giving us good DPI information, and
Line 54: Line 62:
 
  </match>
 
  </match>
  
 +
(to be finished, please comment or fix) {{Unsigned|23:58, 8 January 2012‎|Erm67}}
  
(to be finished, please comment or fix)
+
: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)
 
 
== 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.
 
[[User:4javier|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. -- [[User:Misc|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. [[User:4javier|4javier]] 20:35, 25 April 2011 (EDT)
 
 
 
== <s>Gnome needs xorg</s> ==
 
 
 
Is it really necessary to point out that gnome needs Xorg server??? :/
 
:[https://wiki.archlinux.org/index.php?title=GNOME_3&diff=138457&oldid=138437 Fixed]. -- [[User:Karol|Karol]] 09:05, 26 April 2011 (EDT)
 
:[[User:Adispi|Adispi]] probably wanted Gnome 3 article to have the same note that could be found in [https://wiki.archlinux.org/index.php?title=GNOME&diff=prev&oldid=134279 the Gnome article]. [https://wiki.archlinux.org/index.php?title=GNOME&diff=138476&oldid=137791 I removed that one too.] -- [[User:Karol|Karol]] 10:11, 26 April 2011 (EDT)
 
:: I found that note was explicitly added by an user from italian community https://wiki.archlinux.org/index.php?title=GNOME&oldid=134279. I'll ask him what's the problem with new xorg installation system. I still think it's superfluous.
 
:::I didn't add it, I just changed a pre-existing mini procedure to install Xorg through the xorg group, which was declared out of date at that time. I agree, the note states the obvious, for me it's useless. -- [[User:Kynikos|Kynikos]] 11:02, 26 April 2011 (EDT)
 
:::IIRC [https://bugs.archlinux.org/task/23296 this] was the problem: the contents of xorg group were changed and we had to update the installation procedure in the wiki. Users were baffled that after installing the whole xorg group they couldn't start the X server (because e.g. xorg-xinit wasn't in the xorg group anymore). -- [[User:Karol|Karol]] 11:54, 26 April 2011 (EDT)
 
 
 
== Seamonkey and Pulseaudio ==
 
 
 
#I cant setup seamonkey as default webbrowser.. This is imposible in gnome-control-center without some modyfication.. Google give nothing special, only garbage.
 
#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? :)
 
[[User:3ED|3ED]] 10:03, 1 May 2011 (EDT)
 
 
 
==Nautilus bug==
 
I think nautilus bug has not too much to do with this page. I think move it to nautilus page should be appropriate.
 
--[[User:4javier|4javier]] 13:53, 4 May 2011 (EDT)
 
 
 
==Merge with [[GNOME]]==
 
I report [https://bbs.archlinux.org/viewtopic.php?id=118012 this forum discussion]: this article needs to be merged with [[GNOME]]. -- [[User:Kynikos|Kynikos]] 17:54, 4 May 2011 (EDT)
 
:I agree with cosmin, Gnome page should contain just Gnome3 info. At most we could move gnome 2.x info to a Gnome2 page or a Gnome Legacy page. --[[User:4javier|4javier]] 13:28, 6 May 2011 (EDT)
 
::I'd just merge with [[GNOME]] and discard the outdated parts (almost all), keeping what still makes sense, like the external links (some need updating); the old page would stay in the history afterall. What about [[GNOME Tips]] and [[GNOME Shell]]? -- [[User:Kynikos|Kynikos]] 19:34, 6 May 2011 (EDT)
 
 
 
I don't agree with this merge, at all. Gnome Tips is full of crap, excuse me, out of date information. If you really want to do something about it, i propose to move some tips from gnome wiki into tips but not all of it. I still want a wiki for gnome to learn how to install, what services to configure and how to start it. [[User:Wonder|Wonder]]
 
:Are you talking about merge template between Gnome and Gnome Tips? I just set it to indicate that two articles overlap in scope, and something could be done there (merge, delete or better division). Also template serves as a remainder of the existence of the other page, since I think many who write or read one of them are unaware of other.
 
 
 
:Unfortunately I'm not Gnome expert and don't know how to deal with this the best way.
 
 
 
:After I added this template, I typed KDE in search box, and - surprise - immediately found identically unclearly divided pair of articles on KDE. - [[User:corvinus|corvinus]]
 
 
 
== battery icon ==
 
 
 
I have no battery / power indicator at all! https://live.gnome.org/GnomeShell/Design/Guidelines/SystemStatus/BatteryPower
 
  
solved and added
+
::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)
  
I think this is useless. gnome-power-manager is part of gnome-extra group that's already mentioned into the wiki. --[[User:4javier|4javier]] 13:31, 6 May 2011 (EDT)
+
== Natural scrolling ==
  
== Resizing massive titlebar ==
+
I can't get reverse natural scrolling on my trackpath to work (scroll with fingers in same direction as if it was a mouse wheel). I am happy to propose some text for the wiki if someone can tell me how to do it ... --[[User:Bronze|Bronze]] ([[User talk:Bronze|talk]]) 04:33, 26 February 2017 (UTC)
  
Should not be better point that sed manipulation to ~/.themes/Adwaita/metacity-1/metacity-theme-3.xml ? --[[User:4javier|4javier]] 07:27, 7 May 2011 (EDT)
+
:Is there not a natural scrolling setting under Settings -> Mouse & Touchpad that you can toggle? -- [[User:Chazza|Chazza]] ([[User talk:Chazza|talk]]) 09:57, 26 February 2017 (UTC)
 +
:: i saw this with computers which have a keyboard with integrated touchpads like the logitech k400, and no mouse connected. not sure what makes gnome than display nothing ... --[[User:Soloturn|Soloturn]] ([[User talk:Soloturn|talk]]) 05:11, 1 April 2017 (UTC)
  
== Xmonad section ==
+
== Manually start a Wayland session ==
  
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)
+
Under: ''Starting Gnome -> Manually -> Wayland Session'' the article lists
  
== Is this still a gnome wiki? ==
+
XDG_SESSION_TYPE=wayland dbus-run-session gnome-session
  
last tip for dpms through xset I think has nothing to do...it's not a gnome feature, and it's not permanent. It should be added to startup, but the right way should be to turn off dpms statically into xorg.conf.d. I think this page is becoming too unspecific.
+
as the command to start a {{ic|gnome-session}}. But {{ic|dbus-run-session}} starts a new dbus session and this somehow prevents for example evolution to access my default keyring. I dont know why, but simply starting {{ic|gnome-session}} works. I dont know with which dbus instance the gnome-keyring starts through its .desktop files in {{ic|/etc/xdg}} but the problem seems to be that these 2 would run on different instances of dbus.
:[https://wiki.archlinux.org/index.php?title=GNOME&diff=next&oldid=141933 Thestinger to the rescue!] Fixed :-) -- [[User:Karol|Karol]] 15:20, 18 May 2011 (EDT)
 
::I know I'm getting really really boring but...https://wiki.archlinux.org/index.php/GNOME#XChat --[[User:4javier|4javier]] 16:19, 24 May 2011 (EDT)
 
:::You're not boring :-) I've moved it to [[XChat]] but I'm not sure if creating a bunch of stubs is the best way to deal with it. As I'm neither a Gnome guy nor an IRC user don't count on me to expand that article anytime soon. -- [[User:Karol|Karol]] 02:01, 25 May 2011 (EDT)
 
::::maybe is not be a gnome app but gnome-shell has included features for xchat to stack notifications.
 
::::http://git.gnome.org/browse/gnome-shell/tree/js/ui/notificationDaemon.js#n76
 
::::Maybe we should add a sectiong in gnome wiki called, Integrating apps in gnome-shell and include xchat, pidgin etc -- [[User:Wonder|Wonder]]
 
:::::I think that infos don't need a mention into the wiki at all. They're just a possible setting of a program preference... --[[User:4javier|4javier]] 06:34, 25 May 2011 (EDT)
 
cant quite follow your motivations, but if its consistent, please also move gtk3 and xmonad related "possible setting of a program preference" to their own page too. thanks.
 
:gtk3 is the base of gnome3...and it's not a program, it's the main library. About xmonad https://wiki.archlinux.org/index.php/Talk:GNOME#Xmonad_section --[[User:4javier|4javier]] 06:50, 25 May 2011 (EDT)
 
right, but the xchat options listed are specific to running it under gnome (even the new page hints that). and the gtk3 options are not specific to gnome, they are relevant under any other wm/de.
 
:You're free to create Gtk3 page and move there theming hints. :) But talk about that to wiki admin first. --[[User:4javier|4javier]] 07:43, 25 May 2011 (EDT)
 
  
== «You must install the gnome group» ==
+
I do not want to edit the wiki page as long as i dont know if this is my mistake or really a mistake on the page. I will look into this in the next week, until then, any guidance is appreciated.
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? [[User:Mons1990|Mons]] 04:53, 29 December 2011 (EST)
+
[[User:Tornado|Tornado]] ([[User talk:Tornado|talk]]) 12:55, 6 April 2018 (UTC)
: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 ({{grp|gnome}}, {{grp|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]]. -- [[User:Kynikos|Kynikos]] 06:44, 30 December 2011 (EST)
+
{{Unsigned|11:45, 6 April 2018|Tornado}}

Latest revision as of 12:55, 6 April 2018

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)

Natural scrolling

I can't get reverse natural scrolling on my trackpath to work (scroll with fingers in same direction as if it was a mouse wheel). I am happy to propose some text for the wiki if someone can tell me how to do it ... --Bronze (talk) 04:33, 26 February 2017 (UTC)

Is there not a natural scrolling setting under Settings -> Mouse & Touchpad that you can toggle? -- Chazza (talk) 09:57, 26 February 2017 (UTC)
i saw this with computers which have a keyboard with integrated touchpads like the logitech k400, and no mouse connected. not sure what makes gnome than display nothing ... --Soloturn (talk) 05:11, 1 April 2017 (UTC)

Manually start a Wayland session

Under: Starting Gnome -> Manually -> Wayland Session the article lists

XDG_SESSION_TYPE=wayland dbus-run-session gnome-session

as the command to start a gnome-session. But dbus-run-session starts a new dbus session and this somehow prevents for example evolution to access my default keyring. I dont know why, but simply starting gnome-session works. I dont know with which dbus instance the gnome-keyring starts through its .desktop files in /etc/xdg but the problem seems to be that these 2 would run on different instances of dbus.

I do not want to edit the wiki page as long as i dont know if this is my mistake or really a mistake on the page. I will look into this in the next week, until then, any guidance is appreciated. Tornado (talk) 12:55, 6 April 2018 (UTC) —This unsigned comment is by Tornado (talk) 11:45, 6 April 2018. Please sign your posts with ~~~~!