Talk:GNOME

From ArchWiki

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)


_________

I am experiencing this problem https://github.com/systemd/systemd/issues/5247 and I guess that this command is problematic as is, it should be replaced —This unsigned comment is by Nsqm (talk) 14:20, 2020 April 7‎. Please sign your posts with ~~~~!

I am also having issues with the command on the page. I get A connection to the bus can't be made. Silverhammermba (talk) 12:57, 17 April 2021 (UTC)

Installing GNOME Extensions

It says

Note: Extensions from extensions.gnome.org can be installed right away with gnome-software.

This used to be the case, but I think this feature was removed. Could someone confirm?

Jennydaman (talk) 15:12, 17 May 2020 (UTC)

This is not in the article anymore --Cvlc (talk) 10:01, 28 September 2022 (UTC)

redundancy of XDG_SESSION_TYPE and GDK_BACKEND variables "Xorg sessions" section

In the "Xorg sessions" section, it suggests putting XDG_SESSION_TYPE=x11 GDK_BACKEND=x11 exec startx in ~/.bash_profile. But previously, it suggests setting XDG_SESSION_TYPE and GDK_BACKEND in ~/.xinitrc. So isn't it redundant to set them again? —This unsigned comment is by TDA (talk) 03:13, 24 August 2020 (UTC). Please sign your posts with ~~~~!

Webp Thumbnails

webp-pixbuf-loader 0.0.2-1 already includes the thumbnailer configuration file, as described https://lists.archlinux.org/archives/list/aur-requests@lists.archlinux.org/thread/QWAKG5ZRBATHJPZ7TN24STFPUDJBSQOY/ I come from this forum thread https://bbs.archlinux.org/viewtopic.php?pid=1935714

So, the section https://wiki.archlinux.org/index.php/GNOME#WEBP,_thumbnails should be deleted as it's not required anymore and the AUR link is broken.

—This unsigned comment is by Icar (talk) 11:27, 4 November 2020‎ (UTC). Please sign your posts with ~~~~!

Article has since been updated --Cvlc (talk) 10:05, 28 September 2022 (UTC)

gnome-session: alternative sessions

Should this article mention that gnome-session can be used to initiate non-GNOME sessions (technically GNOME-derivative), such as Pantheon, GNOME/Openbox, something users came up with on their own, etc.? quequotion (talk) 11:23, 14 January 2021 (UTC)

Troubleshooting no Wayland on nVidia driver

If Wayland is expected, but X11 session type is received when using echo $XDG_SESSION_TYPE) or when using loginctl show-session <sessionnum> -p Type, there might be missing kernel configuration parameter for nVidia driver.

journalctl log entry will report error:

systemd[753]: org.gnome.Shell@wayland.service: Skipped due to 'exec-condition'.
systemd[753]: Condition check resulted in GNOME Shell on Wayland being skipped.

Starting Wayland manually

dbus-run-session -- gnome-shell --display-server --wayland

will produce error messages:

mutter-Message: 14:33:45.804: Adding device '/dev/dri/card0' (nvidia-drm) using non-atomic mode setting (using atomic mode setting not allowed).
(gnome-shell:11885): GLib-CRITICAL **: 14:33:45.804: g_hash_table_destroy: assertion 'hash_table != NULL' failed
(gnome-shell:11885): mutter-WARNING **: 14:33:45.805: Failed to open gpu '/dev/dri/card0': Failed to activate universal planes: Operation not permitted
(gnome-shell:11885): mutter-WARNING **: 14:33:45.805: Failed to create backend: No GPUs found

The key error message is 1st line which includes nvidia-drm.

Enable nvidia-drm support with kernel configuration parameter.

For GRUB update boot/grub/grub.cfg file by appending to linux line:

nvidia-drm.modeset=1

—This unsigned comment is by Kulak (talk) 00:13, 20 September 2021 (UTC). Please sign your posts with ~~~~!

Removed subsection that discusses changing backgrounds of the desktop and the lock screen

Previously, GNOME only allowed backgrounds to be picked from the ~/Pictures folder. The subsection I removed used to discuss how to pick backgrounds from different directories for both the desktop and the lock screen. Today, GNOME allows backgrounds to be picked from any directory. But, you can't choose a custom lock screen background because the lock screen is just a blurred version of the desktop background. However, you can use a custom lock screen background using this extension: https://extensions.gnome.org/extension/1476/unlock-dialog-background/. If anyone finds it necessary to add a subsection for this extension in this wiki article, feel free to do so. —This unsigned comment is by Cont999 (talk) 2022-08-20T17:30:41. Please sign your posts with ~~~~!

merging terminal sub-section with GNOME/Tips_and_Tricks

i think the terminal tricks included in the main article are really useful and very sought after. the default gnome terminal looks really bland, and a bit of customization to one of the programs you use the most wouldnt hurt to put up front for everybody to see. so informing the regular user about these possible customization tricks to personalize ur gnome experience isnt that bad after all, because not many people check tips and tricks sections/articles as theyre very advanced most of the time

instead of merging this sub-section with GNOME/Tips_and_Tricks, why dont we remove the duplicated content from GNOME/Tips_and_Tricks and keep it here ?

also, one of the other reasons why this merge was proposed in the first place is because it requires 'additional packages'. this entire article is suggesting additional packages, thats the nature of gnome as its not very customizable out of the box

these tweaks were even useful for me. i really didnt know it was possible to make the terminal transparent after the recent updates, but upon checking this article i found that new information

thoughts ?

—This unsigned comment is by Kami Spell (talk) 2022-08-30T10:49:27. Please sign your posts with ~~~~!

I think I might be with you on this. It took me a while to find and put together these tricks after all and I thought adding them to the Wiki would be a nice touch. However I'm by no means an expert and I can't tell for sure what's best for the Arch Wiki, wait for opinions other than mine on this. Cont999 (talk) 11:01, 30 August 2022 (UTC)
Both of you have a good point: I'd prefer to have the whole GNOME#Advanced settings section moved to GNOME/Tips and tricks at that rate, but we should have it linked more prominently in the main page instead of only having it "hidden" in the Template:Related at the top.
Would that be OK? --Erus Iluvatar (talk) 11:13, 30 August 2022 (UTC)
I think your suggestion is nice and makes total sense. However, that'll leave the GNOME article very empty. And honestly I consider most, if not all of the settings in GNOME#Advanced settings basic needs for a 'complete' feeling to a GNOME desktop environment.
Thinking about it further, I think we should leave it the way it is. It wouldn't really fit in GNOME/Tips and tricks, because the Tips and Tricks article seems very oddly specific to some rare use cases, so it only benefits those. While GNOME#Advanced settings seems generally beneficial for everyone. Mixing what's within GNOME#Advanced settings with the contents of GNOME/Tips and tricks would be kinda strange IMO. Cont999 (talk) 11:23, 30 August 2022 (UTC)
Specifically regarding GNOME Terminal, maybe we have enough content to justify a dedicated GNOME/Terminal page like what already exists for GNOME/Files, GNOME/Web or GNOME/Evolution?
While I agree that a vanilla GNOME experience is not to my taste either, calling all the content we provide in GNOME#Configuration and especially GNOME#Advanced settings "generally beneficial for everyone" is a bit of a stretch. For example GNOME#AppIndicators/Top bar icons, GNOME#Shell blur, GNOME#Rounded corners, GNOME#Dash to Dock, GNOME#Use a different window manager are objectively a matter of personal taste and would probably be a better fit in GNOME/Tips and tricks.
--Erus Iluvatar (talk) 11:59, 30 August 2022 (UTC)
The reason why I said what's within GNOME#Advanced settings is beneficial for everyone is because, for example, certain apps just disappear and keep running in the background when you close them. You'd need a tray icons extension like GNOME#AppIndicators/Top bar icons to see those apps running under tray and actually close them (or to bring them back up). This extension became so popular that it was moved to the community repository from AUR. For GNOME#Rounded corners, I believe that this is very useful for people because it brings a uniform look to your entire desktop. New GTK and libadwaita apps have all four corners rounded, while legacy/Qt apps have their bottom corners sharp. So. that extension is a nice suggestion for everyone to improve their desktop just by a tiny bit. And for GNOME#Shell blur, this is beneficial because most other popular DEs offer some sort of blur to their interface (KDE Plasma for example). While GNOME, the so-called 'modern-looking desktop environment,' still lacks behind on that. Which AFAIK people consider essential (I've been in many unixporn subreddits/Discord servers), and it really improves the look of your desktop IMO. Then finally, GNOME#Dash to Dock. That extension is one of the most popular GNOME extensions, it just makes navigation much easier (an alternative to it is Dash to Panel) while bringing 0 distraction to your work. I was literally surprised when I saw 0 mentions of this extension in the entirety of the Arch Wiki, considering how many people install it. So I decided to add it myself.
Now, for GNOME#Use a different window manager, that section is an actual candidate for GNOME/Tips and tricks because it is "advanced." This is the one that I see best suitable to move to Tips and Tricks (and add a bit of expansion, because the current section is very vague).
And finally, regarding your suggestion to create GNOME/Terminal; this is a pretty neat idea, I like it. However, if we remove duplicates from GNOME#Terminal and GNOME/Tips_and_tricks#Terminal, it will leave us with not much content for an entire article (unless we add more). Either idea really seems fine to me, keeping it in the main article or giving it its separate article. I'll wait for other opinions on that. Thanks for the nice suggestion.
To summarize my points, I believe this sections are "beneficial" for everyone, but not strictly needed by any means. They would make things easier or improve the look of your desktop, but people are just fine if they ignore them.
Cont999 (talk) 02:45, 31 August 2022 (UTC)
So your conclusion is close to the definition of Help:Style#"Tips and tricks" section:
advanced tips or examples of using the software
Regarding the fact that the GNOME/Terminal page would be short: that's not necessarily an argument against it, see Konsole.
+1 from me on waiting other chiming in about:
1/ creating GNOME/Terminal,
2a/ moving all the Terminal content and deduplicate it to GNOME/Tips and tricks#Terminal or
2b/ moving all the Terminal content and deduplicate it to GNOME#Terminal and
3/ moving most of GNOME#Advanced settings into GNOME/Tips and tricks.
--Erus Iluvatar (talk) 17:42, 31 August 2022 (UTC)
1 and 2a seem the two best options for me. Let's wait for more responses, and thank you so much for your time and participation. Cont999 (talk) 22:56, 31 August 2022 (UTC)
No other answers in two weeks: would you have to time to create GNOME/Terminal or do you prefer merging everything to GNOME/Tips and tricks#Terminal? --Erus Iluvatar (talk) 15:37, 16 September 2022 (UTC)
I have not heard back from you: I don't have the time to create a proper dedicated page, I'll merge everything to the Tips and tricks subpage. Closing. --Erus Iluvatar (talk) 18:41, 24 September 2022 (UTC)
Apologies for not replying, I forgot that I was engaged in this discussion. Merging to the Tips and tricks subpage seems enough for now, I'd try creating a dedicated subpage, but I'm totally clueless on how to do that properly. Cont999 (talk) 23:41, 29 September 2022 (UTC)
No problem :) I have merged the only relevant section about the terminal to the subpage (I thought there was more content to merge, but it appears my memory failed me). See Help:Editing#Creating pages for pointers on creating a new page. --Erus Iluvatar (talk) 07:08, 30 September 2022 (UTC)

Requesting a rewrite for GNOME#Extensions

The current description is very inconsistent:

  • We should expand on both methods to install extensions (system-wide with pacman/AUR, and current user only with https://extensions.gnome.org/) and describe their ups and downs.
  • A more up to date description of these methods would help, since they're outdated. E.g. currently, when using the site to install and update extensions with gnome-browser-extension, you get update notifications for extensions on your desktop, and you can use the built-in Gnome extensions app to update them as well if they were installed from extensions.gnome.org.
  • However, using the site to install extensions will override the same system-extensions (if they are installed), it will ask to update all current extensions installed from the AUR and the official repositories (gnome-shell-extension-appindicator and gnome-shell-extension-gtile, as well as gnome-shell-extensions which comes shipped with GNOME) on https://extensions.gnome.org/local/, even if these system-extensions are already up to date. After you press the update on all of them, these system-extensions will be "hidden" and new user extensions will be created in place of them, which you have to update through the site as well. Making the entire description of using pacman or an AUR helper for automated updates useless when using this method, and overriding the system package gnome-shell-extensions as it will be replaced by a user extension that you have to update on the site.
  • Lastly, I think it'd be better if we take all advanced configuration sections that rely on extensions and make them subsections under extensions.

This has always been an argument in the Arch Forums and Reddit, so I think we should come up with a solution to solve all these problems. If anyone's got the time to take care of all this, please do so. Cont999 (talk) 23:35, 29 September 2022 (UTC)

Hi, I wanted to do exactly that yesterday when I moved it up but couldn't secure enough time, and wanted to think it through first.
Another thing that definitely needs to be included is Extension Manager (from here), which adds an argument to splitting the article between "system-wide" and "user-only"
-- Cvlc (talk) 00:06, 30 September 2022 (UTC)
i agree that the current description does need a rw. however, i think that adding extension manager to this section is not as important and possibly useless since what we're aiming for is gonna do the exact same thing.
this discussion should come to light, please participate and voice your opinion BOURNE86 (talk) 20:52, 30 September 2022 (UTC)