https://wiki.archlinux.org/api.php?action=feedcontributions&user=Dreivier&feedformat=atomArchWiki - User contributions [en]2024-03-29T02:32:39ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=User_talk:Altercation/Bullet_Proof_Arch_Install&diff=465521User talk:Altercation/Bullet Proof Arch Install2017-01-16T19:02:03Z<p>Dreivier: /* Questions */ gist to script</p>
<hr />
<div>== <s>Tables</s> ==<br />
<br />
Just wanted to say those partitioning tables are pretty cool. And their source is readable at that! Cheers -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 09:22, 2 December 2016 (UTC)<br />
<br />
:Thanks [[User:Alad]], they took me a while! Still some cleanup to do, but I felt that there needed to be a visual to make things clear. Appreciate the feedback. -Ethan<br />
<br />
==Questions==<br />
Hm, install works fine but I can't boot. Could you add an EFI boot section? I tried with efibootmgr and systed-boot but somehow I don't know how to properly get my root partition. [[User:Dreivier|Dreivier]] ([[User talk:Dreivier|talk]]) 15:00, 2 January 2017 (UTC)<br />
<br />
--> solved it and will post my solution latern on [[User:Dreivier|Dreivier]] ([[User talk:Dreivier|talk]]) 08:00, 10 January 2017 (UTC)<br />
--> here it is: https://gist.github.com/burningTyger/cb6e61afdeb527f4b87e57774ac40f16</div>Dreivierhttps://wiki.archlinux.org/index.php?title=User_talk:Altercation/Bullet_Proof_Arch_Install&diff=462192User talk:Altercation/Bullet Proof Arch Install2017-01-10T08:00:38Z<p>Dreivier: /* Questions */ solved it</p>
<hr />
<div>== <s>Tables</s> ==<br />
<br />
Just wanted to say those partitioning tables are pretty cool. And their source is readable at that! Cheers -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 09:22, 2 December 2016 (UTC)<br />
<br />
:Thanks [[User:Alad]], they took me a while! Still some cleanup to do, but I felt that there needed to be a visual to make things clear. Appreciate the feedback. -Ethan<br />
<br />
==Questions==<br />
Hm, install works fine but I can't boot. Could you add an EFI boot section? I tried with efibootmgr and systed-boot but somehow I don't know how to properly get my root partition. [[User:Dreivier|Dreivier]] ([[User talk:Dreivier|talk]]) 15:00, 2 January 2017 (UTC)<br />
<br />
--> solved it and will post my solution latern on [[User:Dreivier|Dreivier]] ([[User talk:Dreivier|talk]]) 08:00, 10 January 2017 (UTC)</div>Dreivierhttps://wiki.archlinux.org/index.php?title=User_talk:Altercation/Bullet_Proof_Arch_Install&diff=461140User talk:Altercation/Bullet Proof Arch Install2017-01-02T15:00:42Z<p>Dreivier: Q</p>
<hr />
<div>== <s>Tables</s> ==<br />
<br />
Just wanted to say those partitioning tables are pretty cool. And their source is readable at that! Cheers -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 09:22, 2 December 2016 (UTC)<br />
<br />
:Thanks [[User:Alad]], they took me a while! Still some cleanup to do, but I felt that there needed to be a visual to make things clear. Appreciate the feedback. -Ethan<br />
<br />
==Questions==<br />
Hm, install works fine but I can't boot. Could you add an EFI boot section? I tried with efibootmgr and systed-boot but somehow I don't know how to properly get my root partition. [[User:Dreivier|Dreivier]] ([[User talk:Dreivier|talk]]) 15:00, 2 January 2017 (UTC)</div>Dreivierhttps://wiki.archlinux.org/index.php?title=Avahi&diff=405448Avahi2015-10-18T13:36:14Z<p>Dreivier: /* Installation */ ipv6 is not set by default anymore.</p>
<hr />
<div>[[Category:Networking]]<br />
[[fr:Avahi]]<br />
[[ja:Avahi]]<br />
From [[Wikipedia:Avahi (software)]]:<br />
:''"[http://avahi.org/ Avahi] is a free [[Wikipedia:Zero-configuration networking|Zero-configuration networking]] (zeroconf) implementation, including a system for multicast DNS/DNS-SD service discovery. It allows programs to publish and discover services and hosts running on a local network with no specific configuration. For example you can plug into a network and instantly find printers to print to, files to look at and people to talk to. It is licensed under the GNU Lesser General Public License (LGPL)."''<br />
<br />
== Installation ==<br />
[[Install]] the {{Pkg|avahi}} package.<br />
<br />
You can manage the Avahi daemon with {{ic|avahi-daemon.service}} [[systemd#Using units|using systemd]].<br />
<br />
== Using Avahi ==<br />
<br />
=== Hostname resolution ===<br />
Avahi provides local hostname resolution using a "''hostname''.local" naming scheme. To enable it, install the {{Pkg|nss-mdns}} package and start {{ic|avahi-daemon.service}}.<br />
<br />
Then, edit the file {{ic|/etc/nsswitch.conf}} and change the line:<br />
hosts: files dns myhostname<br />
to:<br />
hosts: files mdns_minimal [NOTFOUND=return] dns myhostname<br />
<br />
==== Additional info about mdns ====<br />
<br />
The {{ic|mdns_minimal}} module handles queries for the {{ic|.local}} TLD only. Note the {{ic|<nowiki>[NOTFOUND=return]</nowiki>}}, which specifies that if {{ic|mdns_minimal}} cannot find {{ic|*.local}}, it will not continue to search for it in {{ic|dns}}, {{ic|myhostname}}, etc. In case you have configured Avahi to use a different TLD, you should replace {{ic|1=mdns_minimal [NOTFOUND=return]}} with the full {{ic|mdns}} module. There also are IPv4-only and IPv6-only modules {{ic|mdns[46](_minimal)}}.<br />
<br />
==== Tools ====<br />
<br />
Avahi includes several utilities which help you discover the services running on a network. For example, run<br />
avahi-browse -alr<br />
to discover services in your network.<br />
<br />
The Avahi Zeroconf Browser ({{ic|avahi-discover}} – note that it needs avahi's optional dependencies {{Pkg|pygtk}} and {{Pkg|python2-dbus}}) shows the various services on your network. You can also browse SSH and VNC Servers using {{ic|bssh}} and {{ic|bvnc}} respectively.<br />
<br />
There's a good list of software with Avahi support at their website: http://avahi.org/wiki/Avah4users<br />
<br />
===File sharing===<br />
<br />
====NFS====<br />
If you have an [[NFS]] share set up, you can use Avahi to be able to automount them in Zeroconf-enabled browsers (such as Konqueror on KDE and Finder on OS X).<br />
<br />
Create a {{ic|.service}} file in {{ic|/etc/avahi/services}} with the following contents:<br />
{{hc|/etc/avahi/services/nfs_Zephyrus_Music.service|<nowiki><br />
<?xml version="1.0" standalone='no'?><br />
<!DOCTYPE service-group SYSTEM "avahi-service.dtd"><br />
<service-group><br />
<name replace-wildcards="yes">NFS Music Share on %h</name><br />
<service><br />
<type>_nfs._tcp</type><br />
<port>2049</port><br />
<txt-record>path=/data/shared/Music</txt-record><br />
</service><br />
</service-group></nowiki>}}<br />
<br />
The port is correct if you have ''insecure'' as an option in your {{ic|/etc/exports}}; otherwise, it needs to be changed (note that ''insecure'' is needed for OS X clients). The path is the path to your export, or a subdirectory of it. For some reason the automount functionality has been removed from Leopard, however [http://www.macosxhints.com/article.php?story=20071116042238744 a script is available]. This was based upon [http://ubuntuforums.org/showthread.php?p=4387032#post4387032 this post].<br />
<br />
====Samba====<br />
With the Avahi daemon running on both the server and client, the file manager on the client should automatically find the server.<br />
<br />
====Vsftpd====<br />
You can also auto-discover regular FTP servers, such as vsftpd. Install the {{Pkg|vsftpd}} package and change the settings of vsftpd according to your own personal preferences (see [http://ubuntuforums.org/showthread.php?t=218630 this thread on ubuntuforums.org] or {{ic|man vsftpd.conf}}).<br />
<br />
Create a {{ic|.service}} file in {{ic|/etc/avahi/services}} with the following contents:<br />
{{hc|/etc/avahi/services/ftp.service|<nowiki><br />
<?xml version="1.0" standalone='no'?><br />
<!DOCTYPE service-group SYSTEM "avahi-service.dtd"><br />
<service-group><br />
<name>FTP file sharing</name><br />
<service><br />
<type>_ftp._tcp</type><br />
<port>21</port><br />
</service><br />
</service-group><br />
</nowiki>}}<br />
When you are done, [[restart]] the {{ic|avahi-daemon.service}} and {{ic|vsftpd.service}} services.<br />
<br />
The FTP server should now be advertised by Avahi. You should now be able to find the FTP server from a file manager on another computer in your network. You might need to enable [[#Hostname resolution]] on the client.<br />
<br />
===Link-Local (Bonjour/Zeroconf) chat===<br />
<br />
Avahi can be used for bonjour protocol support under linux. Check [[Wikipedia:Comparison of instant messaging clients]] or [[List of applications#Instant messaging]] for a list of clients supporting the bonjour protocol.<br />
<br />
===Airprint from Mobile Devices===<br />
Avahi along with CUPS also provides the capability to print to just about any printer from airprint compatible mobile devices. In order to enable print capability from your device, simply create an avahi service file for your printer in /etc/avahi/services and restart avahi. An example of a generic services file for an HP-Laserjet printer would be similar to the following with the {{ic|name}}, {{ic|rp}}, {{ic|ty}}, {{ic|adminurl}} and {{ic|note}} fields changed.<br />
<br />
{{hc|/etc/avahi/services/youFileName.service|<nowiki><br />
<?xml version="1.0" standalone='no'?><!--*-nxml-*--><br />
<!DOCTYPE service-group SYSTEM "avahi-service.dtd"><br />
<service-group><br />
<name>yourPrnterName</name><br />
<service><br />
<type>_ipp._tcp</type><br />
<subtype>_universal._sub._ipp._tcp</subtype><br />
<port>631</port><br />
<txt-record>txtver=1</txt-record><br />
<txt-record>qtotal=1</txt-record><br />
<txt-record>rp=printers/yourPrnterName</txt-record><br />
<txt-record>ty=yourPrnterName</txt-record><br />
<txt-record>adminurl=http://198.168.7.15:631/printers/yourPrnterName</txt-record><br />
<txt-record>note=Office Laserjet 4100n</txt-record><br />
<txt-record>priority=0</txt-record><br />
<txt-record>product=(GPL Ghostscript)</txt-record><br />
<txt-record>printer-state=3</txt-record><br />
<txt-record>printer-type=0x801046</txt-record><br />
<txt-record>Transparent=T</txt-record><br />
<txt-record>Binary=T</txt-record><br />
<txt-record>Fax=F</txt-record><br />
<txt-record>Color=T</txt-record><br />
<txt-record>Duplex=T</txt-record><br />
<txt-record>Staple=F</txt-record><br />
<txt-record>Copies=T</txt-record><br />
<txt-record>Collate=F</txt-record><br />
<txt-record>Punch=F</txt-record><br />
<txt-record>Bind=F</txt-record><br />
<txt-record>Sort=F</txt-record><br />
<txt-record>Scan=F</txt-record><br />
<txt-record>pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/urf</txt-record><br />
<txt-record>URF=W8,SRGB24,CP1,RS600</txt-record><br />
</service><br />
</service-group><br />
</nowiki>}}<br />
<br />
Alternatively, https://raw.github.com/tjfontaine/airprint-generate/master/airprint-generate.py can be used to generate Avahi service files. It depends on python2 and pycups. The script can be run using:<br />
<br />
# python2 airprint-generate.py -d /etc/avahi/services<br />
<br />
{{Note|If your printer under http://localhost:631/printers is "Not Shared", this python script won't output any file to /etc/avahi/services; in that case, you'll need to "Modify Printer" under one of the CUPS drop-down menus to turn sharing on. If that doesn't work, check out the ArchWiki on [[CUPS printer sharing]].}}<br />
<br />
=== Firewall ===<br />
<br />
Be sure to open UDP port 5353 if you're using iptables:<br />
# iptables -A INPUT -p udp -m udp --dport 5353 -j ACCEPT<br />
<br />
If you're following the more-than-useful [[Simple stateful firewall]] format for your firewall:<br />
# iptables -A UDP -p udp -m udp --dport 5353 -j ACCEPT<br />
<br />
=== Obtaining IPv4LL IP address ===<br />
<br />
{{Merge|dhcpcd|should be merged into the main page}}<br />
<br />
By default, if you are getting IP using DHCP, you are using the {{Pkg|dhcpcd}} package. It can attempt to obtain an IPv4LL address if it failed to get one via DHCP. By default this option is disabled. To enable it, comment noipv4ll string:<br />
<br />
{{hc|/etc/dhcpcd.conf|<br />
...<br />
#noipv4ll<br />
...}}<br />
<br />
Alternatively, run {{ic|avahi-autoipd}}:<br />
# avahi-autoipd -D<br />
<br />
=== Customizing Avahi ===<br />
==== Adding Services ====<br />
<br />
Avahi advertises the services whose {{ic|*.service}} files are found in {{ic|/etc/avahi/services}}. If you want to advertise a service for which there is no {{ic|*.service}} file, it is very easy to create your own.<br />
<br />
As an example, let's say you wanted to advertise a quote of the day (QOTD) service operating per [http://tools.ietf.org/html/rfc865 RFC865] on TCP port 17 which you are running on your machine<br />
<br />
The first thing to do is to determine the {{ic|<type>}}. {{ic|man avahi.service}} indicates that the <br />
type should be "the DNS-SD service type for this service. e.g. '_http._tcp'". Since the [http://www.dns-sd.org/ServiceTypes.html DNS-SD register was merged into the IANA register in 2010], we look for the service name on the [http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml IANA register] or in {{ic|/etc/services}} file. The service name shown there is {{ic|qotd}}. Since we're running QOTD on tcp, we now know the service is {{ic|_qotd._tcp}} and the port (per IANA and RFC865) is 17.<br />
<br />
Our {{ic|qotd.service}} file is thus:<br />
<br />
{{bc|<nowiki><br />
<?xml version="1.0" standalone='no'?><!--*-nxml-*--><br />
<!DOCTYPE service-group SYSTEM "avahi-service.dtd"><br />
<br />
<!--<br />
This file is part of avahi.<br />
<br />
avahi is free software; you can redistribute it and/or modify it<br />
under the terms of the GNU Lesser General Public License as<br />
published by the Free Software Foundation; either version 2 of the<br />
License, or (at your option) any later version.<br />
<br />
avahi is distributed in the hope that it will be useful, but<br />
WITHOUT ANY WARRANTY; without even the implied warranty of<br />
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU<br />
General Public License for more details.<br />
<br />
You should have received a copy of the GNU Lesser General Public<br />
License along with avahi; if not, write to the Free Software<br />
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA<br />
02111-1307 USA.<br />
--><br />
<br />
<!-- See avahi.service(5) for more information about this configuration file --><br />
<br />
<service-group><br />
<br />
<name replace-wildcards="yes">%h</name><br />
<br />
<service><br />
<type>_qotd._tcp</type><br />
<port>17</port><br />
</service><br />
<br />
</service-group><br />
</nowiki>}}<br />
<br />
For more complicated scenarios, such as advertising services running on a different server, DNS sub-types and so on, consult {{ic|man avahi.service}}.<br />
<br />
==== Modifying the service-types database ====<br />
As noted above, avahi comes with tools to browse advertised services. Both {{ic|avahi-browse}} and {{ic|avahi-discover}} use a database file to furnish descriptions of the relevant service. That database contains the names of many, but not all, services.<br />
<br />
Sadly, it doesn't contain the QOTD service we just created. Thus {{ic|avahi-browse -a}} would show the following ugly entry<br />
<br />
+ wlp2s0 IPv4 MyServer _qotd._tcp local<br />
<br />
===== Getting the Sources ===== <br />
<br />
First, download the files {{ic|build-db.in}} and {{ic|service-types}} files from the {{ic|service-type-database}} subdirectory in the [https://github.com/Distrotech/avahi the avahi github mirror] to a build directory.<br />
<br />
wget https://raw.githubusercontent.com/Distrotech/avahi/distrotech-avahi/service-type-database/build-db.in<br />
wget https://raw.githubusercontent.com/Distrotech/avahi/distrotech-avahi/service-type-database/service-types<br />
<br />
===== Modify the Sources =====<br />
<br />
Second, create the following script:<br />
<br />
#!/bin/bash<br />
sed -e 's,@PYTHON\@,/usr/bin/python2.7,g' \<br />
-e 's,@DBM\@,gdbm,g' < build-db.in > build-db<br />
chmod +x build-db<br />
<br />
This mimics what the Makefile would do if one were building all of avahi. It creates a file named build-b.<br />
<br />
$./whatever_you_named_the_script.sh<br />
$ ls<br />
build-db build-db.in service-types whatever_you_named_the_script.sh<br />
<br />
Third, make the changes needed to add your new QOTD service to the {{ic|service-types}} file. This file has one entry per line, with the entries in the format {{ic|type:Human Readable Description}}. Note that the human readable description can contain spaces.<br />
<br />
In our example, we add the following entry to the end of the file:<br />
<br />
_qotd._tcp:Quote of the Day (QOTD) Server<br />
<br />
===== Build and Install the New Database =====<br />
<br />
Now run the {{ic|build-db}} python script (be sure to use python2 not python3). This will build the {{ic|service-types.db}} file. Check to make sure it's been built and use {{ic|gdbmtools}} to make sure the new database is loadable and contains the new entry: <br />
<br />
$/usr/bin/python2.7 build-db<br />
$ls<br />
build-db build-db.in service-types service-types.db whatever_you_named_the_script.sh<br />
$gdbmtool service-types.db<br />
<br />
Welcome to the gdbm tool. Type ? for help.<br />
<br />
gdbmtool>fetch _qotd._tcp<br />
Quote of the Day (QOTD) Server<br />
gdbmtool>quit<br />
<br />
Now copy the old database to a backup location, move the new database to the live directory and use {{ic|avahi-browse}} database dump command to make sure avahi sees the new entry:<br />
<br />
$cp /usr/lib/avahi/service-types.db /backup-directory<br />
$sudo cp /build-directory/service-types.db /usr/lib/avahi/service-types.db<br />
$avahi-browse -b | grep QOTD<br />
Quote of the Day (QOTD) Server<br />
<br />
The entry in {{ic|avahi-browse}} should now be:<br />
<br />
+ wlp2s0 IPv4 MyServer Quote of the Day (QOTD) Server local<br />
<br />
==See also==<br />
* [http://avahi.org/ Avahi] - Official project website<br />
* [http://en.wikipedia.org/wiki/Avahi_%28software%29 Wikipedia entry]<br />
* [http://www.apple.com/support/downloads/bonjourforwindows.html Bonjour for Windows] - Enable Zeroconf on Windows<br />
* http://www.zeroconf.org/</div>Dreivierhttps://wiki.archlinux.org/index.php?title=Talk:Pacaur&diff=335416Talk:Pacaur2014-09-13T21:27:30Z<p>Dreivier: orphans</p>
<hr />
<div>== Orphaned packages ==<br />
pacaur tells me there are orphan packages after a failed build. What about them. Do I manually remove them or is there a simple command to clean up? <br />
[[User:Dreivier|Dreivier]] ([[User talk:Dreivier|talk]]) 21:27, 13 September 2014 (UTC)</div>Dreivierhttps://wiki.archlinux.org/index.php?title=User:Dreivier&diff=333082User:Dreivier2014-08-30T10:58:08Z<p>Dreivier: </p>
<hr />
<div>== Hi there ==<br />
<br />
I'm new here. I will add stuff to the wiki because I just started using Arch. Any shortcomings in the wiki may or may not be fixed.<br />
<br />
August 2014, [[User:Dreivier|Dreivier]] ([[User talk:Dreivier|talk]]) 10:58, 30 August 2014 (UTC) (The older this message the less likely that it will be true)</div>Dreivierhttps://wiki.archlinux.org/index.php?title=User:Dreivier&diff=333081User:Dreivier2014-08-30T10:57:18Z<p>Dreivier: Created page with "== Hi there == I'm new here. I will add stuff to the wiki because I just started using Arch. Any shortcomings in the wiki may or may not be fixed."</p>
<hr />
<div>== Hi there ==<br />
<br />
I'm new here. I will add stuff to the wiki because I just started using Arch. Any shortcomings in the wiki may or may not be fixed.</div>Dreivierhttps://wiki.archlinux.org/index.php?title=Talk:GNOME&diff=333080Talk:GNOME2014-08-30T10:54:58Z<p>Dreivier: </p>
<hr />
<div>== Candidates for removal (discussion) ==<br />
<br />
* <s>[[GNOME#Some_.27System_Settings.27_not_preserved]]</s> - Poor language and doubles what's explained (more thoroughly) in [[Systemd]]. Should be rewritten and reference to [[Systemd]]<br />
::Done per [[#Remove_systemd_configuration_from_.27Some_.27System_Settings.27_no_preserved.27_section]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 22:30, 19 August 2014 (UTC)<br />
<br />
* [[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.<br />
<br />
* <s>[[GNOME#Login_screen]]</s> - GDM is not part of clean GNOME, should we add this to [[GDM]] in stead?<br />
:: +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) <br />
<br />
:: 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.<br />
<br />
:: +1 Added clarity to merge tag. [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 21:18, 28 January 2013 (UTC)<br />
<br />
::: *very good* info about exporting DBUS vars and editing GDM's dconf was killed in haste (12:19, 8 August 2013 Lahwaacz) [[User:Extofme|Extofme]] ([[User talk:Extofme|talk]]) 12:39, 22 October 2013 (UTC)<br />
<br />
::::You can still restore that, maybe in [[GDM#Configuration]]. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 11:00, 24 October 2013 (UTC)<br />
<br />
::::: We should move to working part of this section to GDM. Their is a own page for GDM and this blows up the page for GNOME, necessary information is missing here (seems to be partially included on GDM-Page - this is the reason why I don't move it) and the lock-screen can now be configured through regular settings-UI in GNOME. [[User:Hoschi|Hoschi]] ([[User talk:Hoschi|talk]]) 16:43, 2 November 2013 (UTC)<br />
<br />
:::::: The content in question was moved to the GDM article on the 13th January. -- [[User:Chazza|Chazza]] ([[User talk:Chazza|talk]]) 09:07, 11 April 2014 (UTC)<br />
<br />
*<s>[[GNOME#Shutdown_via_the_status_menu]]</s> - As of Gnome (3.6.2), this is no longer the case. Gnome has switched back to using Power Off in the menu.<br />
<br />
: 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)<br />
:: The section in question no longer exists. -- [[User:Chazza|Chazza]] ([[User talk:Chazza|talk]]) 09:09, 11 April 2014 (UTC)<br />
<br />
*[[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 <br />
{{hc|/usr/share/gnome-shell/js/ui/layout.js|<nowiki><br />
//this._pressureBarrier.connect('trigger', Lang.bind(this, this._toggleOverview));<br />
</nowiki>}}<br />
<br />
*[[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 <br />
{{hc|/usr/share/gnome-shell/js/ui/layout.js|<nowiki><br />
//Main.messageTray.openTray();<br />
</nowiki>}} [[User:Lns|Lns]] ([[User talk:Lns|talk]]) 06:09, 4 August 2013 (UTC)<br />
<br />
== GNOME and fontconfig settings ==<br />
<br />
Since there isn't a section dedicated to fonts in GNOME 3 I was thinking about writing one, but I put it here first:<br />
<br />
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:<br />
<br />
/* As we cannot rely on the X server giving us good DPI information, and<br />
* that we don't want multi-monitor screens to have different DPIs (thus<br />
* different text sizes), we'll hard-code the value of the DPI<br />
*<br />
* See also:<br />
* https://bugzilla.novell.com/show_bug.cgi?id=217790•<br />
* https://bugzilla.gnome.org/show_bug.cgi?id=643704<br />
*/<br />
<br />
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:<br />
<br />
org.gnome.desktop.interface.text-scaling-factor<br />
<br />
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:<br />
<br />
Xft.antialias: 1<br />
Xft.dpi: 96<br />
Xft.hinting: 1<br />
Xft.hintstyle: hintmedium<br />
Xft.lcdfilter: lcddefault<br />
Xft.rgba: none<br />
<br />
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.<br />
<br />
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. <br />
<br />
The dpi setting of the Xserver can be changed to 96 following [https://wiki.archlinux.org/index.php/Xorg#Display_Size_and_DPI 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.<br />
<br />
For and LCD monitor it is a good idea to activate the lcd filter setting the following keys in dconf-editor:<br />
<br />
org.gnome.settings-daemon.plugins.xsettings.antialiasing rgba<br />
org.gnome.settings-daemon.plugins.xsettings.rgba-order rgb, bgr, vrgb or vbgr (as your monitor requires)<br />
<br />
Since the lcdfilter is not designed to work together with autohinting it is a good idea to disable it also in fonts.conf.<br />
It is also a good idea to use the same hinting value as in your font.conf, the default in gnome is medium:<br />
<br />
org.gnome.settings-daemon.plugins.xsettings.hinting medium<br />
<br />
This values in fonts.conf will match the gnome settings:<br />
<br />
<match target="font"><br />
<edit mode="assign" name="rgba"><const>rgb</const></edit><br />
<edit mode="assign" name="autohint"><bool>false</bool></edit><br />
<edit mode="assign" name="hinting"><bool>true</bool></edit><br />
<edit mode="assign" name="hintstyle"><const>hintmedium</const></edit><br />
<edit mode="assign" name="antialias"><bool>true</bool></edit><br />
<edit mode="assign" name="lcdfilter"><const>lcddefault</const></edit><br />
</match><br />
<br />
(to be finished, please comment or fix) {{Unsigned|23:58, 8 January 2012|Erm67}}<br />
<br />
: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)<br />
<br />
== deleted manual hotkeys modification ==<br />
<br />
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.<br />
[[User:4javier|4javier]] 08:09, 25 April 2011 (EDT)<br />
<br />
: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)<br />
<br />
::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)<br />
<br />
:::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)<br />
<br />
== Xmonad section ==<br />
<br />
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)<br />
<br />
== Add link to official extensions site ==<br />
<br />
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)<br />
: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)<br />
<br />
== Reference to NetworkManager ==<br />
<br />
GNOME 3 uses network-manager-applet, which in turn uses NetworkManager. Maybe this page should contain a reference to NetworkManager, so people with network problems in GNOME know where to look for the solution. I suppose many people do not know that using GNOME means using NetworkManager. [[User:Pelzflorian|Pelzflorian]] ([[User talk:Pelzflorian|talk]]) 16:31, 14 March 2014 (UTC)<br />
<br />
:Using GNOME not always means using NetworkManager :) But it's a dependency for network in GNOME, so I vote +1 -- [[User:Kycok|Kycok]] ([[User talk:Kycok|talk]]) 11:00, 3 June 2014 (UTC)<br />
<br />
== ownCloud Integration ==<br />
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. [[User:Beanaroo|Beanaroo]] ([[User talk:Beanaroo|talk]]) 09:21, 3 June 2014 (UTC)<br />
<br />
== Display Dimming Change ==<br />
<br />
Re https://wiki.archlinux.org/index.php/GNOME#Display_dimming: https://git.gnome.org/browse/gnome-control-center has commit ''bd3b8beeae9a3d88483aa0d33fd10042593735a6'' from January 16 that removes "idle-dim-time" from GSettings and has this additional comment:<br />
<br />
And make the default time for the dimming be based upon the idle timeout.<br />
If there is no idle timeout, dim at one minute of idle.<br />
If there is an idle timeout, ensure that the dim time is at least 10<br />
seconds, otherwise a third of the idle-delay<br />
<br />
I'm not sure if we should remove the [[#Display_dimming]] section of this wiki or update it to say something else.<br />
<br />
{{Unsigned|22:51, 27 June 2014|Paulie4}}<br />
<br />
== Dependencies ==<br />
I added xorg and xorg-xinit to the install paragraph but it was reverted. I don't think it's obvious for the new arch user to install these. I started as a very new user, installed arch according to the beginner's guide and went straight to the gnome wiki page to install my desktop. And it didn't work because I was missing the twop dependencies. It is not obvious and the beginner's guide does not tell me to check the general recommendations. I don't see a problem adding these two lines.<br />
[[User:Dreivier|Dreivier]] ([[User talk:Dreivier|talk]])</div>Dreivierhttps://wiki.archlinux.org/index.php?title=Talk:GNOME&diff=333079Talk:GNOME2014-08-30T10:54:28Z<p>Dreivier: lamenting a revert</p>
<hr />
<div>== Candidates for removal (discussion) ==<br />
<br />
* <s>[[GNOME#Some_.27System_Settings.27_not_preserved]]</s> - Poor language and doubles what's explained (more thoroughly) in [[Systemd]]. Should be rewritten and reference to [[Systemd]]<br />
::Done per [[#Remove_systemd_configuration_from_.27Some_.27System_Settings.27_no_preserved.27_section]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 22:30, 19 August 2014 (UTC)<br />
<br />
* [[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.<br />
<br />
* <s>[[GNOME#Login_screen]]</s> - GDM is not part of clean GNOME, should we add this to [[GDM]] in stead?<br />
:: +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) <br />
<br />
:: 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.<br />
<br />
:: +1 Added clarity to merge tag. [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 21:18, 28 January 2013 (UTC)<br />
<br />
::: *very good* info about exporting DBUS vars and editing GDM's dconf was killed in haste (12:19, 8 August 2013 Lahwaacz) [[User:Extofme|Extofme]] ([[User talk:Extofme|talk]]) 12:39, 22 October 2013 (UTC)<br />
<br />
::::You can still restore that, maybe in [[GDM#Configuration]]. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 11:00, 24 October 2013 (UTC)<br />
<br />
::::: We should move to working part of this section to GDM. Their is a own page for GDM and this blows up the page for GNOME, necessary information is missing here (seems to be partially included on GDM-Page - this is the reason why I don't move it) and the lock-screen can now be configured through regular settings-UI in GNOME. [[User:Hoschi|Hoschi]] ([[User talk:Hoschi|talk]]) 16:43, 2 November 2013 (UTC)<br />
<br />
:::::: The content in question was moved to the GDM article on the 13th January. -- [[User:Chazza|Chazza]] ([[User talk:Chazza|talk]]) 09:07, 11 April 2014 (UTC)<br />
<br />
*<s>[[GNOME#Shutdown_via_the_status_menu]]</s> - As of Gnome (3.6.2), this is no longer the case. Gnome has switched back to using Power Off in the menu.<br />
<br />
: 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)<br />
:: The section in question no longer exists. -- [[User:Chazza|Chazza]] ([[User talk:Chazza|talk]]) 09:09, 11 April 2014 (UTC)<br />
<br />
*[[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 <br />
{{hc|/usr/share/gnome-shell/js/ui/layout.js|<nowiki><br />
//this._pressureBarrier.connect('trigger', Lang.bind(this, this._toggleOverview));<br />
</nowiki>}}<br />
<br />
*[[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 <br />
{{hc|/usr/share/gnome-shell/js/ui/layout.js|<nowiki><br />
//Main.messageTray.openTray();<br />
</nowiki>}} [[User:Lns|Lns]] ([[User talk:Lns|talk]]) 06:09, 4 August 2013 (UTC)<br />
<br />
== GNOME and fontconfig settings ==<br />
<br />
Since there isn't a section dedicated to fonts in GNOME 3 I was thinking about writing one, but I put it here first:<br />
<br />
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:<br />
<br />
/* As we cannot rely on the X server giving us good DPI information, and<br />
* that we don't want multi-monitor screens to have different DPIs (thus<br />
* different text sizes), we'll hard-code the value of the DPI<br />
*<br />
* See also:<br />
* https://bugzilla.novell.com/show_bug.cgi?id=217790•<br />
* https://bugzilla.gnome.org/show_bug.cgi?id=643704<br />
*/<br />
<br />
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:<br />
<br />
org.gnome.desktop.interface.text-scaling-factor<br />
<br />
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:<br />
<br />
Xft.antialias: 1<br />
Xft.dpi: 96<br />
Xft.hinting: 1<br />
Xft.hintstyle: hintmedium<br />
Xft.lcdfilter: lcddefault<br />
Xft.rgba: none<br />
<br />
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.<br />
<br />
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. <br />
<br />
The dpi setting of the Xserver can be changed to 96 following [https://wiki.archlinux.org/index.php/Xorg#Display_Size_and_DPI 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.<br />
<br />
For and LCD monitor it is a good idea to activate the lcd filter setting the following keys in dconf-editor:<br />
<br />
org.gnome.settings-daemon.plugins.xsettings.antialiasing rgba<br />
org.gnome.settings-daemon.plugins.xsettings.rgba-order rgb, bgr, vrgb or vbgr (as your monitor requires)<br />
<br />
Since the lcdfilter is not designed to work together with autohinting it is a good idea to disable it also in fonts.conf.<br />
It is also a good idea to use the same hinting value as in your font.conf, the default in gnome is medium:<br />
<br />
org.gnome.settings-daemon.plugins.xsettings.hinting medium<br />
<br />
This values in fonts.conf will match the gnome settings:<br />
<br />
<match target="font"><br />
<edit mode="assign" name="rgba"><const>rgb</const></edit><br />
<edit mode="assign" name="autohint"><bool>false</bool></edit><br />
<edit mode="assign" name="hinting"><bool>true</bool></edit><br />
<edit mode="assign" name="hintstyle"><const>hintmedium</const></edit><br />
<edit mode="assign" name="antialias"><bool>true</bool></edit><br />
<edit mode="assign" name="lcdfilter"><const>lcddefault</const></edit><br />
</match><br />
<br />
(to be finished, please comment or fix) {{Unsigned|23:58, 8 January 2012|Erm67}}<br />
<br />
: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)<br />
<br />
== deleted manual hotkeys modification ==<br />
<br />
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.<br />
[[User:4javier|4javier]] 08:09, 25 April 2011 (EDT)<br />
<br />
: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)<br />
<br />
::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)<br />
<br />
:::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)<br />
<br />
== Xmonad section ==<br />
<br />
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)<br />
<br />
== Add link to official extensions site ==<br />
<br />
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)<br />
: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)<br />
<br />
== Reference to NetworkManager ==<br />
<br />
GNOME 3 uses network-manager-applet, which in turn uses NetworkManager. Maybe this page should contain a reference to NetworkManager, so people with network problems in GNOME know where to look for the solution. I suppose many people do not know that using GNOME means using NetworkManager. [[User:Pelzflorian|Pelzflorian]] ([[User talk:Pelzflorian|talk]]) 16:31, 14 March 2014 (UTC)<br />
<br />
:Using GNOME not always means using NetworkManager :) But it's a dependency for network in GNOME, so I vote +1 -- [[User:Kycok|Kycok]] ([[User talk:Kycok|talk]]) 11:00, 3 June 2014 (UTC)<br />
<br />
== ownCloud Integration ==<br />
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. [[User:Beanaroo|Beanaroo]] ([[User talk:Beanaroo|talk]]) 09:21, 3 June 2014 (UTC)<br />
<br />
== Display Dimming Change ==<br />
<br />
Re https://wiki.archlinux.org/index.php/GNOME#Display_dimming: https://git.gnome.org/browse/gnome-control-center has commit ''bd3b8beeae9a3d88483aa0d33fd10042593735a6'' from January 16 that removes "idle-dim-time" from GSettings and has this additional comment:<br />
<br />
And make the default time for the dimming be based upon the idle timeout.<br />
If there is no idle timeout, dim at one minute of idle.<br />
If there is an idle timeout, ensure that the dim time is at least 10<br />
seconds, otherwise a third of the idle-delay<br />
<br />
I'm not sure if we should remove the [[#Display_dimming]] section of this wiki or update it to say something else.<br />
<br />
{{Unsigned|22:51, 27 June 2014|Paulie4}}<br />
<br />
== Dependencies ==<br />
I added xorg and xorg-xinit to the install paragraph but it was reverted. I don't think it's obvious for the new arch user to install these. I started as a very new user, installed arch according to the beginner's guide and went straight to the gnome wiki page to install my desktop. And it didn't work because I was missing the twop dependencies. It is not obvious and the beginner's guide does not tell me to check the general recommendations. I don't see a problem adding these two lines.</div>Dreivierhttps://wiki.archlinux.org/index.php?title=GNOME&diff=331883GNOME2014-08-22T16:47:36Z<p>Dreivier: Tell reader that xorg and xorg-xinit are needed as well on a new system</p>
<hr />
<div>[[Category:GNOME]]<br />
[[cs:GNOME]]<br />
[[de:GNOME]]<br />
[[es:GNOME]]<br />
[[fr:GNOME]]<br />
[[it:GNOME]]<br />
[[ja:GNOME]]<br />
[[nl:GNOME]]<br />
[[pl:GNOME]]<br />
[[pt:GNOME]]<br />
[[ru:GNOME]]<br />
[[sr:GNOME]]<br />
[[th:GNOME]]<br />
[[tr:Gnome Masaüstü Ortamı]]<br />
[[uk:GNOME]]<br />
[[zh-CN:GNOME]]<br />
[[zh-TW:GNOME]]<br />
{{Related articles start}}<br />
{{Related|Desktop environment}}<br />
{{Related|Display manager}}<br />
{{Related|Window manager}}<br />
{{Related|GTK+}}<br />
{{Related|GDM}}<br />
{{Related|GNOME Files}}<br />
{{Related|Gedit}}<br />
{{Related|GNOME Web}}<br />
{{Related|GNOME Flashback}}<br />
{{Related articles end}}<br />
[http://www.gnome.org/ GNOME] is a [[desktop environment]] developed by The GNOME Project.<br />
<br />
GNOME 3 has ''two'' sessions:<br />
<br />
*'''GNOME''' is the default, innovative layout.<br />
*'''GNOME Classic''' is a traditional desktop layout, similar to the GNOME 2 user interface whilst using GNOME 3 technologies. It does so through the use of pre-activated extensions and parameters (see [http://worldofgnome.org/welcome-to-gnome-3-8-flintstones-mode/ here] for a list). Hence it is more of a customized GNOME Shell than a truly distinct mode.<br />
<br />
Both of them use GNOME Shell, a desktop shell and plugin of the Mutter window manager. Mutter acts as a composite manager for the desktop, employing hardware graphics acceleration to provide effects aimed at reducing screen clutter. GNOME session manager automatically detects if your video driver is capable of running GNOME Shell and if not, falls back to software rendering using llvmpipe.<br />
<br />
== Installation ==<br />
<br />
GNOME 3 is available in the [[official repositories]] and can be [[pacman|installed]] with one of the following:<br />
*The {{Pkg|gnome-shell}} package provides a minimal desktop shell.<br />
*The {{Grp|gnome}} group contains the core desktop environment and applications required for the standard GNOME experience.<br />
*The {{Grp|gnome-extra}} group contains various optional tools such as an editor, an archive manager, a disk burner, a mail client, games, development tools and other non-critical applications that integrate well with the GNOME desktop. Installing just the {{Grp|gnome-extra}} group will not pull in the whole {{Grp|gnome}} group via dependencies. If you want to install all GNOME packages then you will need to explicitly install both groups.<br />
<br />
If you start with a newly installed system you will also have to install the two packages {{Pkg|xorg}} and {{Pkg|xorg-xinit}}. Otherwise the following instructions won't work and Gnome cannot be started.<br />
<br />
== Starting GNOME ==<br />
<br />
'''Graphical log-in'''<br />
<br />
For the best desktop integration, [[GDM]] (the GNOME [[Display manager]]) is recommended. GDM is installed as part of the {{grp|gnome}} group and can be used by enabling {{ic|gdm.service}} [[systemd#Using units|using systemd]].<br />
<br />
Other display managers can be used in place of GDM if desired.<br />
<br />
{{note|Native support for screenlocking in GNOME is provided by GDM. If you choose to not use GDM you will need to use a different screenlocking program such as [[XScreenSaver]].}} <br />
<br />
'''Starting GNOME manually'''<br />
<br />
If you prefer to start GNOME manually from the console, add the following line to your {{ic|~/.xinitrc}} file:<br />
{{hc|~/.xinitrc|<nowiki><br />
exec gnome-session<br />
</nowiki>}}<br />
<br />
Or {{ic|exec env GNOME_SHELL_SESSION_MODE&#61;classic gnome-session --session gnome-classic}} for GNOME Classic. After editing your {{ic|~/.xinitrc}}, GNOME can be launched by typing {{ic|startx}}.<br />
<br />
See [[xinitrc]] for details, such as preserving the logind session.<br />
<br />
After setting up your {{ic|~/.xinitrc}} file you can also arrange to [[Start X at Login]] so that you don't have to run {{ic|startx}} manually.<br />
<br />
== Using the shell ==<br />
<br />
=== GNOME Cheat Sheet ===<br />
<br />
The [https://wiki.gnome.org/Projects/GnomeShell/CheatSheet GNOME Shell Cheat Sheet] on the GNOME Wiki explains task switching, keyboard use, window control, the panel, overview mode, and more.<br />
<br />
=== Restarting the shell ===<br />
<br />
After appearance tweaks you are often asked to restart the GNOME shell. You could log out and log back in, but it is simpler and faster to issue the following keyboard command. Restart the shell by pressing {{ic|Alt}} + {{ic|F2}} then {{ic|r}} then {{ic|Enter}}<br />
<br />
=== Shell crashes ===<br />
<br />
Certain tweaks and/or repeated shell restarts may cause the shell to crash when a restart is attempted. In this case, you are informed about the crash and then forced to log out. Some shell changes cannot be accomplished via a keyboard restart; you must log out and log back in to effect them.<br />
<br />
{{note|Valuable documents should be saved (and perhaps closed) before attempting a shell restart. It is not strictly necessary; open windows and documents usually remain intact after a shell restart however there is a risk that data could be lost if documents are not saved.}}<br />
<br />
=== Shell freezes ===<br />
<br />
Sometimes shell extensions freeze the GNOME Shell. In this case a possible strategy is to switch to another terminal via {{ic|Ctrl+Alt+F2}} through {{ic|Ctrl+Alt+F6}}, log in, and restart gnome-shell with:<br />
<br />
# pkill -HUP gnome-shell<br />
<br />
All open applications will still be available after restarting the shell.<br />
<br />
Sometimes, however, merely restarting the shell might not be enough. Then you will have to restart X, losing all work in progress. You can restart X by:<br />
<br />
# pkill X<br />
<br />
The GNOME Shell then restarts automatically.<br />
<br />
If this does not work, you can try to restart your login manager. For instance, if you use GDM, try:<br />
<br />
# systemctl restart gdm.service<br />
<br />
{{Tip|You can also use '''htop''' in tty; press ''t'', select the ''gnome-shell'' tree, press ''k'' and send ''SIGKILL''.}}<br />
<br />
== Pacman integration: GNOME PackageKit ==<br />
{{Warning|1=As of Gnome 3.12 the pacman integration with packagekit is very outdated. See [https://bbs.archlinux.org/viewtopic.php?pid=1334848#p1334848 this forum thread] and [http://worldofgnome.org/gnome-software-on-arch/ this article] for more information.}}<br />
<br />
GNOME has its own Pacman GUI: {{Pkg|gnome-packagekit}}.<br />
<br />
Using the [https://www.archlinux.org/pacman/libalpm.3.html alpm] backend, it supports the following features:<br />
<br />
* Install and remove packages from the repos.<br />
* Periodically refresh package databases and prompt for updates.<br />
* Install packages from tarballs.<br />
* Search for packages by name, description, category or file.<br />
* Show package dependencies, files and reverse dependencies.<br />
* Ignore IgnorePkgs and hold HoldPkgs.<br />
* Report optional dependencies, .pacnew files, etc.<br />
<br />
You can change the {{ic|remove}} operation from -Rc to -Rsc by setting the DConf key {{ic|org.gnome.packagekit.enable-autoremove}}.<br />
<br />
=== Packages updates notifications ===<br />
<br />
If you want GNOME to check automatically for updates, you must install {{AUR|gnome-settings-daemon-updates}} from the official repository.<br />
<br />
== Customizing GNOME appearance ==<br />
<br />
The ''Systems Settings'' tool (provided by {{pkg|gnome-control-center}}) is a simple and streamlined panel which covers most basic settings. <br />
<br />
More elaborate graphical customization (such as modifying fonts, themes, titlebar buttons and such) can be done using the graphical ''GNOME tweak tool''. {{Pkg|gnome-tweak-tool}} is available from the [[official repositories]]. See [[#Theming]] below for more information about the subject.<br />
<br />
More extensive customisation may require more low-level configuration, using [[#gsettings and dconf]].<br />
<br />
==== Theming ====<br />
<br />
To install a new theme or icon set, put it in {{ic|~/.local/share/themes}} or {{ic|~/.local/share/icons}}. You can then activate it using ''GNOME tweak tool'', that is described above.<br />
<br />
Alternatively, you can set a GTK (icon) theme via {{ic|~/.config/gtk-3.0/settings.ini}}. In this file you can set the GTK theme ({{ic|gtk-theme-name}}), the icon theme ({{ic|gtk-icon-theme-name}}), the font ({{ic|gtk-font-name}}) and more.<br />
<br />
''Adwaita,'' the default GNOME 3 theme, is a part of {{pkg|gnome-themes-standard}}. Additional GTK3 themes can be found at [http://browse.deviantart.com/customization/skins/linuxutil/desktopenv/gnome/gtk3/ Deviantart web site]. For example:<br />
{{hc|~/gtk-3.0/settings.ini|<nowiki><br />
[Settings]<br />
gtk-theme-name = Adwaita<br />
# next option is applicable only if selected theme supports it<br />
gtk-application-prefer-dark-theme = true<br />
# set font name and dimension<br />
gtk-font-name = Sans 10<br />
</nowiki>}}<br />
<br />
It is necessary to restart the GNOME shell for settings to be applied. More GTK options are found at [http://developer.gnome.org/gtk3/3.0/GtkSettings.html#GtkSettings.properties GNOME developer documentation].<br />
<br />
==== gsettings and dconf ====<br />
<br />
dconf is a data store used by GNOME to store its settings. It can be edited with the graphical {{ic|dconf-editor}} or the command line {{ic|gsettings}} tool. See [http://blog.fpmurphy.com/2011/03/customizing-the-gnome-3-shell.html Customizing the GNOME Shell] for a tutorial on using gsettings.<br />
<br />
=== Customize top bar ===<br />
<br />
==== Show date in top bar ====<br />
<br />
By default GNOME displays only the weekday and time in the top bar. This can be changed with the following command. Changes take effect immediately. <br />
<br />
# gsettings set org.gnome.desktop.interface clock-show-date true<br />
<br />
==== Hiding icons in the top bar ====<br />
<br />
When installing GNOME, some unwanted icons might appear in the panel. These icons can be removed by manually editing the GNOME panel script.<br />
<br />
For example, to remove the keyboard button, comment out the {{ic|'keyboard'}} line in {{ic|PANEL_ITEM_IMPLEMENTATIONS}}:<br />
<br />
{{hc|/usr/share/gnome-shell/js/ui/panel.js|<nowiki><br />
const PANEL_ITEM_IMPLEMENTATIONS = {<br />
'activities': ActivitiesButton,<br />
'aggregateMenu': AggregateMenu,<br />
'appMenu': AppMenuButton,<br />
'dateMenu': imports.ui.dateMenu.DateMenuButton,<br />
'a11y': imports.ui.status.accessibility.ATIndicator,<br />
'a11yGreeter': imports.ui.status.accessibility.ATGreeterIndicator,<br />
//'keyboard': imports.ui.status.keyboard.InputSourceIndicator,<br />
};<br />
</nowiki>}}<br />
<br />
Then, save your results and restart the shell:<br />
<br />
#{{ic|Alt+F2}}<br />
#{{ic|r}}<br />
#{{ic|Enter}}<br />
<br />
==== Eliminate delay when logging out ====<br />
<br />
The following tweak removes the confirmation dialog and sixty second delay for logging out.<br />
<br />
This dialog normally appears when you log out with the status menu. This tweak affects the '''''Power Off''''' dialog as well. This is not a system-wide change; it affects only the user who enters this command. The change takes effect immediately after entering the command:<br />
<br />
$ gsettings set org.gnome.SessionManager logout-prompt 'false'<br />
<br />
==== Show system monitor ====<br />
<br />
The [https://extensions.gnome.org/extension/120/system-monitor/ system-monitor] extension is included in the {{pkg|gnome-shell-extensions}} package. The git version is available as {{AUR|gnome-shell-system-monitor-applet-git}} in the [[AUR]].<br />
<br />
==== Show weather information ====<br />
<br />
The [https://extensions.gnome.org/extension/613/weather/ Weather] extension can be installed from [https://extensions.gnome.org/extension/613/weather/ the official extension website]. The git version is available as {{AUR|gnome-shell-extension-weather-git}} in the [[AUR]].<br />
<br />
=== Activity view ===<br />
<br />
==== Remove entries from Applications view ====<br />
<br />
Like most desktop environments, GNOME uses .desktop files to populate its Applications view. These text files are located in the '''{{ic|/usr/share/applications}}''' folder. It is not possible to edit these files from a folder view ‒ Files does not treat their icons as text files. Use a terminal to display or edit .desktop file entries. You will need root privileges to edit the .desktop files.<br />
<br />
# ls /usr/share/applications<br />
# nano /usr/share/applications/foo.desktop<br />
<br />
For system wide changes, edit files in '''{{ic|/usr/share/applications}}'''. For local changes, make a copy of ''foo.desktop'' in your home folder.<br />
<br />
$ cp /usr/share/applications/foo.desktop ~/.local/share/applications/<br />
<br />
Edit .desktop files to fit your wishes. <br />
<br />
{{Note|Removing a .desktop file does not uninstall an application, but instead removes its desktop integration: MIME types, shortcuts, and so forth.}}<br />
<br />
To hide an application launcher open its .desktop file in a text editor and add the following line:<br />
<br />
NoDisplay=true<br />
<br />
==== Sort applications into folders ====<br />
<br />
Gnome 3.12 allows the user to sort applications into folders. A GUI for this is provided by Gnome Software, which Arch does not package (due to PackageKit incompatibilities). However, applications can still be sorted into folders manually via dconf. To add a folder, navigate via dconf to '''{{ic|org.gnome.desktop.app-folders}}''' and set the value of '''{{ic|folder-children}}''' to an array of comma separated folder names:<br />
<br />
['Utilities', 'Sundry']<br />
<br />
To add applications to these folders, use '''{{ic|gsettings}}''':<br />
<br />
gsettings set org.gnome.desktop.app-folders.folder:/org/gnome/desktop/app-folders/folders/Sundry/ apps "['alacarte.desktop', 'dconf-editor.desktop']"<br />
<br />
This adds the applications corresponding to '''{{ic|alacarte.desktop}}''' and '''{{ic|dconf-editor.desktop}}'''' to the Sundry folder.<br />
<br />
This will also create the folder '''{{ic|org.gnome.desktop.app-folders.folders.Sundry}}'''. The constituents of the folder can be updated from dconf or from '''{{ic|gsettings}}''', by appending applications to the list.<br />
<br />
To name the folder (if it has no name it will simply appear at the top of the applications), set the name key via '''{{ic|gsettings}}''':<br />
<br />
gsettings set org.gnome.desktop.app-folders.folder:/org/gnome/desktop/app-folders/folders/Sundry/ name "Sundry"<br />
<br />
Applications can also be sorted by their category (specified in their '''{{ic|.desktop}}''' file):<br />
<br />
gsettings set org.gnome.desktop.app-folders.folder:/org/gnome/desktop/app-folders/folders/Sundry/ categories "['Office']"<br />
<br />
If certain applications matching a category are not wanted in a certain folder, exclusions can be set:<br />
<br />
gsettings set org.gnome.desktop.app-folders.folder:/org/gnome/desktop/app-folders/folders/Sundry/ excluded-apps "['libreoffice-draw.desktop']"<br />
<br />
For further information, refer to the [https://git.gnome.org/browse/gsettings-desktop-schemas/tree/schemas/org.gnome.desktop.app-folders.gschema.xml.in.in app-folders schema].<br />
<br />
==== Change icon size ====<br />
<br />
===== For applications in activity view =====<br />
<br />
To change the application icon size it is necessary to edit the GNOME-Shell theme.<br />
<br />
You can edit system files directly (make a backup first) or copy theme files to your local folder and edit these files. <br />
* For the '''default''' theme, edit '''{{ic|/usr/share/gnome-shell/theme/gnome-shell.css}}'''<br />
<br />
* For '''user themes''', edit '''{{ic|/usr/share/themes/<UserTheme>/gnome-shell/gnome-shell.css}}'''<br />
<br />
Edit ''gnome-shell.css'' and replace the following values. Afterward, [[#Restarting the shell|restart the GNOME shell]].<br />
<br />
{{hc|gnome-shell.css|<nowiki><br />
...<br />
/* Application Launchers and Grid */<br />
<br />
.icon-grid {<br />
spacing: 18px;<br />
-shell-grid-horizontal-item-size: 82px;<br />
-shell-grid-vertical-item-size: 82px;<br />
}<br />
<br />
.icon-grid .overview-icon {<br />
icon-size: 48px;<br />
}<br />
...<br />
</nowiki>}}<br />
<br />
===== In dash =====<br />
<br />
GNOME's Activities view has a dash on the left hand side, the size of the icons in this dash will scale depending on the amount of icons set to display. The scaling can be manipulated or set to a constant icon size. To do so, edit {{ic|/usr/share/gnome-shell/js/ui/dash.js}}.<br />
<br />
{{hc|dash.js|<nowiki><br />
...<br />
<br />
let iconSizes = [ 16, 22, 24, 32, 48, 64 ];<br />
<br />
...<br />
</nowiki>}}<br />
<br />
===== For switcher (alt-tab) =====<br />
<br />
GNOME comes with a built in task switcher, the size of the icons in this task switcher will scale depending on the amount of icons set to display. The scaling can be manipulated or set to a constant icon size. To do so, edit {{ic|/usr/share/gnome-shell/js/ui/altTab.js}}<br />
<br />
{{hc|altTab.js|<nowiki><br />
...<br />
<br />
const iconSizes = [96, 64, 48, 32, 22];<br />
<br />
...<br />
</nowiki>}}<br />
<br />
===== For system tray =====<br />
<br />
GNOME comes with a built in system tray, visible when the mouse is hovered over the bottom right corner of the screen. The size of the icons in this tray is set to a fixed value of 24. To change this value, edit {{ic|/usr/share/gnome-shell/js/ui/messageTray.js}}<br />
{{hc|messageTray.js|<nowiki><br />
...<br />
<br />
ICON_SIZE: 24,<br />
<br />
...<br />
</nowiki>}}<br />
<br />
==== Disable hot corner hovering ====<br />
<br />
===== Activity view =====<br />
<br />
To disable automatic activity view when the hot corner is hovered, edit {{ic|/usr/share/gnome-shell/js/ui/layout.js}} (that was ''panel.js'' in GNOME 3.0.x) :<br />
{{hc|layout.js|<nowiki><br />
this._corner = new Clutter.Rectangle({ name: 'hot-corner',<br />
width: 1,<br />
height: 1,<br />
opacity: 0,<br />
reactive: true });icon-size: 48px;<br />
}<br />
</nowiki>}}<br />
and set {{ic|reactive}} to {{ic|false}}. GNOME Shell needs to be restarted.<br />
<br />
{{tip|There are also [[GNOME#GNOME_shell_extensions|GNOME Shell extensions]] that can be installed which will modify this behaviour.}}<br />
<br />
===== Message Tray =====<br />
<br />
The message tray is shown when the mouse hovers at the bottom of the screen for one second. To disable this behavior, comment out the following line in {{ic|/usr/share/gnome-shell/js/ui/messageTray.js}}:<br />
{{hc|messageTray.js|<nowiki><br />
//pointerWatcher.addWatch(TRAY_DWELL_CHECK_INTERVAL, Lang.bind(this, this._checkTrayDwell));<br />
</nowiki>}}<br />
GNOME Shell needs to be restarted. The message tray is still visible in activity view.<br />
<br />
=== Titlebar ===<br />
<br />
==== Reduce title bar height ====<br />
<br />
* ''' global''' - edit {{ic|/usr/share/themes/Adwaita/metacity-1/metacity-theme-3.xml}}, search for {{ic|title_vertical_pad}} and reduce its value to a minimum of {{ic|0}}.<br />
* '''user-only''' - copy {{ic|/usr/share/themes/Adwaita/metacity-1/metacity-theme-3.xml}} to {{ic|/home/$USER/.local/share/themes/Adwaita/metacity-1/metacity-theme-3.xml}}, search for {{ic|title_vertical_pad}} and reduce its value to a minimum of {{ic|0}}.<br />
<br />
Then restart the GNOME shell. <br />
<br />
To restore the original values, [[pacman|install]] the package {{Pkg|gnome-themes-standard}} from the [[official repositories]] or remove {{ic|/home/$USER/.local/share/themes/Adwaita/metacity-1/metacity-theme-3.xml}}.<br />
<br />
==== Reorder titlebar buttons ====<br />
<br />
At present this setting can be changed through '''dconf-editor.'''<br />
<br />
For example, to move the close and minimize buttons to the left side of the titlebar, open '''dconf-editor''' and locate the '''''org.gnome.shell.overrides.button_layout''''' key. Change its value to '''{{ic|close,minimize:}}''' (colon symbol designates the spacer between left side and right side of the titlebar). Place the buttons in your preferred order. You cannot use a button more than once. Also, keep in mind that certain buttons are deprecated.<br />
<br />
For a more complete experience, one might need to set more values:<br />
<br />
gsettings set org.gnome.desktop.wm.preferences button-layout 'close,minimize,maximize:'<br />
gsettings set org.gnome.shell.overrides button-layout 'close,minimize,maximize:'<br />
gsettings set org.gnome.settings-daemon.plugins.xsettings overrides "{'Gtk/DecorationLayout' <'close,minimize,maximize:'>}"<br />
<br />
The first entry sets the order for the ''Gnome window manager''. The second entry sets the order for the Gnome window manager when used together with ''Gnome Shell'' (the latter uses this key, which defaults to ':close', to override the previous non-Shell setting). The last one sets the order for [[GTK%2B#Client-side decorations]].<br />
<br />
==== Hide titlebar when maximized ====<br />
<br />
To hide titlebar when windows are maximised, open file {{ic|/usr/share/themes/Adwaita/metacity-1/metacity-theme-3.xml}}, search for the following tag and change its properties, children and the properties of its children tags as follows:<br />
<br />
<frame_geometry name="max" has_title="false"<br />
hide_buttons="true"<br />
parent="normal"<br />
rounded_top_left="false"<br />
rounded_top_right="false"><br />
<distance name="left_width" value="0" /><br />
<distance name="right_width" value="0" /><br />
<distance name="left_titlebar_edge" value="0"/><br />
<distance name="right_titlebar_edge" value="0"/><br />
<distance name="title_vertical_pad" value="0"/><br />
<border name="title_border" left="0" right="0" top="0" bottom="0"/><br />
<border name="button_border" left="0" right="0" top="0" bottom="0"/><br />
<distance name="bottom_height" value="0" /><br />
</frame_geometry><br />
<br />
Once the file has been saved, restart GNOME shell by pressing {{ic|Alt + F2}} and then typing {{ic|r}}. After this tweak, you may find it difficult to un-maximize a window when there is no titlebar to grab.<br />
<br />
With suitable keybindings, you should be able to use {{ic|Alt + F5}}, {{ic|Alt + F10}} or {{ic|Alt + Space}} to remedy the situation.<br />
<br />
To prevent {{ic|metacity-theme-3.xml}} from being overwritten each time package {{pkg|gnome-themes-standard}} is upgraded, add its name to {{ic|/etc/pacman.conf}} with {{ic|NoUpgrade}}:<br />
<br />
{{hc|/etc/pacman.conf|<nowiki>... previous lines ...<br />
<br />
# Pacman will not upgrade packages listed in IgnorePkg and members of IgnoreGroup<br />
# IgnorePkg =<br />
# IgnoreGroup =<br />
<br />
NoUpgrade = usr/share/themes/Adwaita/metacity-1/metacity-theme-3.xml # Do not add a leading slash to the path<br />
<br />
... more lines ...</nowiki>}}<br />
<br />
To restore original Adwaita theme values, install the {{pkg|gnome-themes-standard}} package.<br />
<br />
== Miscellaneous settings ==<br />
<br />
=== Power Management ===<br />
<br />
==== Turn off Suspend-To-RAM (S3) when closing the LID ====<br />
This setting is not available in GNOME, ''gnome-control-center'' and ''dconf'' make this available. The current approach is to manage this on the level of [[systemd]]. Edit {{ic|/etc/systemd/logind.conf}}, uncomment the {{ic|HandleLidSwitch}} line and set it to {{ic|ignore}}:<br />
<br />
{{hc|/etc/systemd/logind.conf|HandleLidSwitch&#61;ignore}}<br />
<br />
See the [[Power management#ACPI_events]] article for more information.<br />
<br />
==== No reaction on lid close ====<br />
<br />
When configuring the lid close events via [[Power management#ACPI_events]], the settings may seem to have no effect. If you have an external monitor connected to your laptop, this is default GNOME behaviour. Disconnect the monitor and the settings should work, otherwise your {{ic|/etc/systemd/logind.conf}} may be incorrect.<br />
To change default behaviour open the {{ic|dconf-editor}} and change {{ic|org.gnome.settings-daemon.plugins.xrandr.default-monitors-setup}} to {{ic|"do-nothing"}}.<br />
<br />
==== Change Critical Battery Level Action (for Laptops) ====<br />
<br />
The ''System Settings'' panel only allows the user to choose between ''Suspend'' or ''Hibernate''. To choose another option such as ''Do Nothing'' open the {{ic|dconf-editor}} and navigate to {{ic|org.gnome.settings-daemon.plugins.power}}. Edit the {{ic|"critical-battery-action"}} value to {{ic|"nothing"}}.<br />
<br />
=== Switch back scrolling behavior ===<br />
If you do not like the new scrollbar behavior just put {{ic|<nowiki>gtk-primary-button-warps-slider = false</nowiki>}} under the {{ic|<nowiki>[Settings]</nowiki>}} section in {{ic|~/.config/gtk-3.0/settings.ini}}:<br />
<br />
{{hc|~/.config/gtk-3.0/settings.ini|<nowiki><br />
[Settings]<br />
gtk-primary-button-warps-slider = false<br />
...<br />
</nowiki>}}<br />
<br />
=== Autostarting / Automatic program launch upon logging in ===<br />
<br />
As of Gnome 3.12 ''gnome-session-properties'' is deprecated. Specify which programs must start automatically after logging in using ''gnome-tweak-tool'' or via the manual method described [http://linuxandfriends.com/how-to-add-startup-programs-in-gnome-3/ here].<br />
<br />
{{Tip|Some users are unable to add autostart applications when {{ic|gnome-tweak-tool}} is launched from Gnome's overview. Launching it from a terminal sometimes fixes this. This issue can also be resolved by making changes described in this [https://bbs.archlinux.org/viewtopic.php?pid&#61;1414443#p1414443 post]. But users will still be unable to add any custom autostart programs such as scripts. <br> {{AUR|gnome-session-properties}} is still available in the [[AUR]].}}<br />
<br />
=== Editing applications menu ===<br />
<br />
{{pkg|alacarte}} provides a more complete menu editor for adding/editing menu entries.<br />
<br />
=== Gnome Terminal ===<br />
<br />
==== Inner padding ====<br />
<br />
To move the terminal output away from the window borders create the stylesheet {{ic|~/.config/gtk-3.0/gtk.css}} with the following setting:<br />
<br />
TerminalScreen {<br />
-VteTerminal-inner-border: 10px 10px 10px 10px;<br />
}<br />
<br />
==== Disable blinking cursor ====<br />
<br />
Since Gnome 3.8 and the migration to gsettings and dconf the key required to modify in order to disable the blinking cursor in the Terminal differs slightly in contrast to the old gconf key. To disable the blinking cursor in Gnome 3.8 use:<br />
<br />
gsettings set org.gnome.desktop.interface cursor-blink false<br />
<br />
If you prefer dconf to the gsettings CLI then open {{ic|dconf-editor}}, go to org -> gnome -> desktop -> interface and untick the option labelled '''cursor-blink'''.<br />
<br />
To disable the blinking cursor in Terminal only use (make sure profile uid is correct one):<br />
<br />
dconf write /org/gnome/terminal/legacy/profiles:/:b1dcc9dd-5262-4d8d-a863-c897e6d979b9/cursor-blink-mode "'off'"<br />
<br />
==== Make new tabs inherit current directory (for Gnome Terminal 3.8+) ====<br />
<br />
In Gnome 3.8, the behaviour of how current directories are tracked has changed. To restore this behaviour, you need to source the {{ic|/etc/profile.d/vte.sh}} file, put this in your {{ic|~/.bashrc}} or {{ic|~/.zshrc}} for zsh users:<br />
<br />
source /etc/profile.d/vte.sh<br />
<br />
For more information refer to the [https://wiki.gnome.org/action/show/Apps/Terminal/FAQ?action=show&redirect=Terminal%252FFAQ#How_can_I_make_new_terminals_start_in_the_working_directory_of_the_current_terminal.3F Gnome wiki].<br />
<br />
=== Move dialog windows ===<br />
The default configuration for dialogs will not allow you to move them which causes problems in some cases. To change this you will need to use gconf-editor and change this setting:<br />
<br />
/desktop/gnome/shell/windows/attach_modal_dialogs<br />
<br />
After the change you will need to restart the shell for it to take affect.<br />
<br />
=== GNOME shell extensions ===<br />
<br />
GNOME Shell can be customized with extensions. These provide features such as a dock or a widget for changing the theme.<br />
<br />
Many extensions are collected and hosted by [https://extensions.gnome.org/ extensions.gnome.org]. They can be browsed and installed simply activating them in the browser. More information about gnome shell extensions can be found [https://extensions.gnome.org/about/ here].<br />
<br />
See [[#When an extension breaks GNOME|when an extension breaks GNOME]] for troubleshooting information.<br />
<br />
=== Default Applications ===<br />
<br />
While one can right click any file and set the default applications in 'Preferences', the settings are actually saved in {{ic | $HOME/.local/share/applications/mimeapps.list}} and {{ic| $HOME/.local/share/applications/mimeinfo.cache}}.<br />
<br />
{{tip|If you are making the change systemwide you may to create the {{ic|/usr/share/applications/mimeapps.list}} file yourself.}}<br />
<br />
==== File browser/replace Files ====<br />
<br />
You can specify a different file manager in the ''mimeapps.list'' file as shown below:<br />
<br />
'''User only''': add the line {{ic|<nowiki>inode/directory=myfilemanager.desktop</nowiki>}} to {{ic|~/.local/share/applications/mimeapps.list}}<br />
<br />
'''Systemwide''': add the line {{ic|<nowiki>inode/directory=myfilemanager.desktop</nowiki>}} to {{ic|/usr/share/applications/mimeapps.list}}<br />
<br />
Where my filemanager.desktop is the correct .desktop file for the file manager of your choice.<br />
<br />
Alternatively you can trick GNOME into using another file browser by editing the {{ic|Exec}} line in {{ic|/usr/share/applications/nautilus.desktop}}. See the correct parameters in the {{ic|.desktop}} file of the file manager of your choice, e.g.:<br />
<br />
{{hc|/usr/share/applications/nautilus.desktop|<br />
2=[...]<br />
Exec=thunar %F<br />
OR<br />
Exec=pcmanfm %U<br />
OR<br />
Exec=nemo %U<br />
[...]<br />
}}<br />
<br />
==== PDF viewer ====<br />
<br />
In some cases when you have installed Inkscape or other graphic programs Evince Document Viewer might no longer be selected as the default PDF application. If it is not available in the '''Open With''' entry which would be the GUI solution, you can use the following user command to make it the default application again:<br />
<br />
xdg-mime default evince.desktop application/pdf<br />
<br />
=== Middle mouse button ===<br />
<br />
By default, GNOME 3 disables middle mouse button emulation regardless of [[Xorg]] settings ('''Emulate3Buttons'''). To enable middle mouse button emulation use:<br />
<br />
$ gsettings set org.gnome.settings-daemon.peripherals.mouse middle-button-enabled true<br />
<br />
=== Display dimming ===<br />
<br />
By default GNOME 3 has a ten second idle timeout to dim the screen regardless of the battery and AC state:<br />
<br />
# gsettings get org.gnome.settings-daemon.plugins.power idle-dim-time<br />
<br />
To set a new value type the following<br />
<br />
# gsettings set org.gnome.settings-daemon.plugins.power idle-dim-time <int><br />
<br />
where <int> is the value in seconds.<br />
<br />
=== Changing hotkeys ===<br />
Certain hotkeys cannot be changed directly via the ''System Settings'' panel. In order to change these keys, use dconf-editor. An example of particular note is the hotkey Alt-Above_Tab. On US keyboards, this is Alt-`: is a hotkey often used in the [[Emacs]] editor. It can be changed by opening dconf-editor and modifying the ''switch-group'' key found in {{ic|org.gnome.desktop.wm.keybindings}}.<br />
<br />
It is possible to manually change the keys via an application's so-called accel map file. Where it is to be found is up to the application: For instance, Thunar's is at ~/.config/Thunar/accels.scm, whereas Files's is located at ~/.config/nautilus/accels and ~/.gnome2/accels/nautilus on old release.<br />
<br />
The file should contain a list of possible hotkeys, each unchanged line commented out with a leading ";" that has to be removed for a change to become active.<br />
For example to replace the hotkey used by Files to move files to the trash folder, change the line:<br />
<br />
; (gtk_accel_path "<Actions>/DirViewActions/Trash" "<Primary>Delete")<br />
to this:<br />
<br />
(gtk_accel_path "<Actions>/DirViewActions/Trash" "Delete")<br />
<br />
The file is regenerated regularly so do not comment the file. The uncommented line will stay but every comment you add will be lost.<br />
<br />
==== Hotkeys in Files 3.4 and older ====<br />
Firstly, use '''dconf-editor''' to place a checkmark next to {{ic|can-change-accels}} in the key named ''org.gnome.desktop.interface.''<br />
<br />
We will replace the hotkey — a.k.a. keyboard shortcut, keyboard accelerator — used by Files to move files to the trash folder.<br />
The default assignment is a somewhat-awkward {{ic|Ctrl+Delete}}.<br />
* Open Files, select any file, and click '''Edit''' on the menu bar.<br />
* Hover over the ''Move to Trash'' menu item.<br />
* While hovering, press {{ic|Delete}}. The current accelerator is now unset.<br />
* Press the key that you wish to become the new keyboard accelerator.<br />
* Press {{ic|Delete}} to make the new accelerator be the Delete key.<br />
Unless you select a file or folder, ''Move to Trash'' will be grayed-out. Finally, disable {{ic|can-change-accels}} to prevent accidental hotkey changes.<br />
<br />
=== Screencast recording ===<br />
<br />
Gnome features the built-in possbility to create screencasts easily. Thereby Control+Shift+Alt+R keybinding starts and stops the recording. A red circle is displayed in the bottom right corner of the screen when the recording is in progress. After the recording is finished, a file named 'Screencast from %d%u-%c.webm' is saved in the Videos directory. In order to use the screencast feature you need to have installed the gst plugins which are:<br />
<br />
$ pacman -Qs gst<br />
<br />
=== Modify Keyboard with XkbOptions ===<br />
<br />
Using the '''dconf-editor''', navigate to the key named {{ic|org.gnome.desktop.input-sources.xkb-options}} and add desired XkbOptions (e.g. ''caps:swapescape'') to the list.<br />
<br />
See {{ic|/usr/share/X11/xkb/rules/xorg}} for all XkbOptions and {{ic|/usr/share/X11/xkb/symbols/*}} for the respective descriptions.<br />
<br />
{{Note|To enable the {{ic|Ctrl+Alt+Backspace}} combination to terminate Xorg, use the {{Pkg|gnome-tweak-tool}} from [[official repositories]]. Within the '''Tweak Tool''', navigate to ''Typing > Terminate'' and select the option {{ic|Ctrl+Alt+Backspace}} from the dropdown menu.}}<br />
<br />
=== Toggle keyboard layouts ===<br />
Since Gnome does not consider any configuration in {{ic|/etc/X11/conf.d/*.conf}} you have to set the command for layout switching either via the control center with the options ''Switch to previous source'' and ''Switch to next source'' or if you want to use Alt - Shift combination you have to use the Gnome-Tweak-Tool and set ''Typing -> Modifiers-only input sources -> select Alt-shift''. For more information see also the forum [https://bbs.archlinux.org/viewtopic.php?id=152127 thread].<br />
<br />
=== HiDPI Support (Retina Screens) ===<br />
<br />
See [[HiDPI]].<br />
<br />
=== Other tips ===<br />
See [[GNOME tips]].<br />
<br />
== Tracker (search program) ==<br />
The {{Pkg|tracker}} provides the Tracker program, an indexing application. You can configure it with {{ic|tracker-preferences}}, and monitor status with {{ic|tracker-control}}. Once installed, indexing should start automatically when you log in. You can explicitly start indexing with {{ic|tracker-control -s}}. Search settings can also be configured in the ''System Settings'' panel.<br />
<br />
== Totem (movie player) ==<br />
<br />
Totem is a movie player based on [[GStreamer]]. For information about adding codecs or hardware acceleration, see [[GStreamer]].<br />
<br />
== Empathy (integrated messaging) and GNOME Online Accounts ==<br />
<br />
Empathy, the engine behind integrated messaging, GNOME Online Accounts, and all other system settings based on messaging accounts will not function correctly unless the {{grp|telepathy}} group of packages or at least one of the backends ({{pkg|telepathy-gabble}}, or {{pkg|telepathy-haze}}, for example) is installed.<br />
<br />
These packages are '''not''' included in either the {{grp|gnome}} or {{grp|gnome-extra}} groups . You can install the Telepathy and optionally any backends with:<br />
<br />
# pacman -S telepathy<br />
<br />
Without telepathy, Empathy will not open the account management dialog and can get stuck in this state. If this happens -- even after quitting Empathy cleanly -- the {{ic|/usr/bin/empathy-accounts}} application can remain running and will need to be killed before you can add any new accounts. Likewise, without telepathy installed, the 'Add an online account' button in GNOME Online Accounts will do nothing.<br />
<br />
View descriptions of telepathy components on the [http://telepathy.freedesktop.org/wiki/Components freedesktop.org telepathy wiki].<br />
<br />
[[Avahi]] daemon is required for connecting with the People Nearby account, and also in order for some desktop extensions to work correctly like [https://extensions.gnome.org/extension/746/chat-status/ Chat Status].<br />
<br />
== Known issues ==<br />
<br />
=== Artifacts when maximizing windows ===<br />
<br />
Maximizing windows may cause artifacts as of GNOME 3.12.0 [https://bbs.archlinux.org/viewtopic.php?id=183617] [https://bugzilla.gnome.org/show_bug.cgi?id=728385].<br />
<br />
== Troubleshooting ==<br />
<br />
=== Cannot change settings in dconf-editor ===<br />
<br />
When one cannot set settings in {{pkg|dconf}}, it is possible their dconf user settings are corrupt. In this case it is best to delete the user dconf files in {{ic|~/.config/dconf/user*}} and set the settings in dconf-editor after.<br />
<br />
=== Extensions ===<br />
<br />
==== When an extension breaks GNOME ====<br />
<br />
When enabling shell extensions causes GNOME breakage, you should first remove the ''user-theme'' and ''auto-move-windows'' extensions from their installation directory.<br />
<br />
The installation directory could be one of {{ic|~/.local/share/gnome‑shell/extensions}}, {{ic|/usr/share/gnome‑shell/extensions}} or {{ic|/usr/local/share/gnome‑shell/extensions}}. Removing these two extension-containing folders may fix the breakage. Otherwise, isolate the problem extension with trial‑and‑error.<br />
<br />
Removing or adding an extension-containing folder to the aforementioned directories removes or adds the corresponding extension to your system. Details on GNOME Shell extensions are available at the [https://live.gnome.org/GnomeShell/Extensions GNOME web site.]<br />
<br />
==== Extensions do not work after GNOME 3 update ====<br />
<br />
Locate the folder where your extensions are installed. It might be {{ic|~/.local/share/gnome-shell/extensions}} or {{ic|/usr/share/gnome-shell/extensions}}.<br />
<br />
Edit each occurrence of {{ic|metadata.json}} which appears in each extension sub-folder.<br />
<br />
{| border="0"<br />
| Insert: || {{ic|"shell-version": ["3.6"]}}<br />
|-<br />
| Instead of (for example): || {{ic|"shell-version": ["3.4"]}}<br />
|}<br />
<br />
{{ic|"3.x"}} indicates the extension works with every shell version. If it breaks, you will know to change it back.<br />
<br />
==== Remove Gnome Shell Extensions ====<br />
<br />
If you have trouble with uninstalling Gnome Extensions via https://extensions.gnome.org/local/, then probably they have been installed as system-wide extensions with {{ic|pacman -S gnome-shell-extensions}} before. To remove them, you have to be careful, because the following instruction removes all extensions from other user's, too:<br />
<br />
# pacman -R gnome-shell-extensions<br />
<br />
Following that, you refresh Gnome Shell by pressing ALT+F2 and entering {{ic|restart}}.<br />
<br />
Then go to https://extensions.gnome.org/local/ again and have a look for your installed extensions list. It should have changed.<br />
<br />
All other extensions should be removable by pressing the red X icon to the right. If not, something may be broken. <br />
<br />
As a final step, you can remove them manually from {{ic|~/.local/share/gnome-shell/extensions/*}} and/or {{ic|/usr/share/gnome-shell/extensions}}. Restart Gnome Shell again and you should be fine.<br />
<br />
=== The "Windows" key ===<br />
By default, this key is mapped to the "overlay-key" to launch the Overview. You can remove this key mapping to free up your {{ic|Windows Key}} (also called {{ic|Mod4}}), which GNOME calls {{ic|Super_L}}, by utilizing {{ic|gsettings}}.<br />
<br />
Example:<br />
{{ic| gsettings set org.gnome.mutter overlay-key 'Foo';}}.<br />
You can leave out '''Foo''' to simply remove any binding to that function.<br />
<br />
{{Note| GNOME also uses {{ic|Alt+F1}} to launch the Overview.}}<br />
<br />
=== Keyboard Shortcut do not work with only conky running ===<br />
The gnome-shell keyboard shortcuts like {{ic|Alt+F2}}, {{ic|Alt+F1}}, and the media key shortcuts do not work if conky is the only program running. However if another application like gedit is running, then the keyboard shortcuts work.<br />
<br />
solution: edit .conkyrc <br />
<br />
own_window yes<br />
own_window_transparent yes<br />
own_window_argb_visual yes<br />
own_window_type dock<br />
own_window_class Conky<br />
own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager<br />
<br />
=== Window opens behind other windows when using multiple monitors ===<br />
<br />
This is possibly a bug in GNOME Shell which causes new windows to open behind others.<br />
Unchecking "workspaces_only_on_primary" in desktop/gnome/shell/windows using gconf-editor solves this problem.<br />
<br />
=== Multiple monitors and dock extension ===<br />
<br />
If you have multiple monitors configured using Nvidia Twinview, the dock extension may get sandwiched in-between the monitors. You can edit the source of this extension to reposition the dock to a position of your choosing.<br />
<br />
Edit {{ic|/usr/share/gnome-shell/extensions/dock@gnome-shell-extensions.gnome.org/extension.js}} and locate this line in the source:<br />
<br />
this.actor.set_position(primary.width-this._item_size-this._spacing-2, (primary.height-height)/2);<br />
<br />
The first parameter is the X position of the dock display, by subtracting 15 pixels as opposed to 2 pixels from this it correctly positioned on my primary monitor, you can play around with any X,Y coordinate pair to position it correctly.<br />
<br />
this.actor.set_position(primary.width-this._item_size-this._spacing-15, (primary.height-height)/2);<br />
<br />
=== "Show Desktop" keyboard shortcut does not work ===<br />
<br />
GNOME developers treated the corresponding binding as bug (see https://bugzilla.gnome.org/show_bug.cgi?id=643609) due to Minimization being deprecated. To show the desktop again assign ALT+STRG+D to the following setting:<br />
<br />
System Settings --> Keyboard --> Shortcuts --> Navigation --> Hide all normal windows<br />
<br />
=== Unable to apply stored configuration for monitors ===<br />
<br />
If you encounter this message try to disable the xrandr gnome-settings-daemon plugin :<br />
<br />
$ dconf write /org/gnome/settings-daemon/plugins/xrandr/active false<br />
<br />
=== Lock button fails to re-enable touchpad ===<br />
<br />
Some laptops have a touchpad lock button that disables the touchpad so that users can type without worrying about touching the touchpad. It appears currently that although GNOME can lock the touchpad by pressing this button, it cannot unlock it. If the touchpad gets locked you can do the following to unlock it:<br />
<br />
# Start a terminal. You can do this by pressing {{ic|Alt+F2}}, then typing {{ic|gnome-terminal}} followed by pressing {{ic|Enter}}.<br />
# Type in the following command:<br />
<br />
$ xinput set-prop "SynPS/2 Synaptics TouchPad" "Device Enabled" 1<br />
<br />
=== Consistent cursor theme ===<br />
<br />
You may find that the cursor theme used in GNOME is not consistent. For example, it may change when moving the cursor across different application windows. To fix this problem, set the cursor theme by creating an {{ic|index.theme}} file which defines the cursor theme according to the XDG icon theme specification. See the following section of the [[Cursor Themes]] article: [[Cursor Themes#Using an index.theme file (recommended)]].<br />
<br />
=== Tracker & Documents do not list any local files ===<br />
<br />
In order for Tracker (and, therefore, Documents) to detect your local files, they must be stored in directories that it knows of. If your documents are contained in one of the usual XDG standard directories (i.e. "Documents" or "Music"), you should install {{Pkg|xdg-user-dirs}} and run:<br />
<br />
# xdg-user-dirs-update<br />
<br />
This will create all of the usual XDG home directories if they do not already exist and it will create the config file definining these directories that Tracker and Documents depend upon.<br />
<br />
=== Passwords are not remembered ===<br />
<br />
If you get a password prompt every time you login, and you find password are not saved, you might need to create/set a default keyring.<br />
<br />
Install {{pkg|seahorse}}. Open "Passwords and Keys" from the menu or run {{ic|seahorse}}. Select View > By Keyring. If there is no keyring in the left column (it will be marked with a lock icon), go to File > New > Password Keyring and give it a nice name. You will be asked to enter a password. If you do not give it a password it will be unlocked automatically even when using autologin, but passwords will not be stored securely. Finally, right-click on the keyring you just created and select "Set as default".<br />
<br />
=== Windows cannot be modified with Alt-Key + Mouse-Button ===<br />
<br />
Change the dconf-setting "org.gnome.desktop.wm.preferences.mouse-button-modifier" from <Super> back to <Alt>. It is not possible to change this with ''System Settings'' > "Keyboard" > "Shortcuts", you will find there only the regular keybindings. The developers of GNOME decided to change this from 3.4 to 3.6 because of this bug report https://bugzilla.gnome.org/show_bug.cgi?id=607797<br />
<br />
=== Gnome-shell 3.8.x fails to load with a black screen + cursor ===<br />
<br />
If you have a non-UTF8 language enabled, Gnome 3 can fail to load. Disable non-UTF-8 locales and perform a locale-gen until this is resolved.<br />
For more information see [https://bugzilla.gnome.org/show_bug.cgi?id=698952 this bug report].<br />
<br />
Additionally, if multiple locales of different languages are enabled, it may be necessary to disable all locales except for one (which is UTF-8).<br />
<br />
=== UI elements scale incorrectly ===<br />
<br />
Gnome introduced HDPI support in version 3.10. If your display does not provide the correct screen size through EDID, this can lead to incorrectly scaled UI elements. As a workaround you can open dconf-editor and find the key {{ic|scaling-factor}} in {{ic|org.gnome.desktop.interface}}. Set it to {{ic|1}} to get the standard scale.<br />
<br />
=== Tear-free video with Intel HD Graphics ===<br />
Enabling the [[Intel _Graphics#Tear-free_video|Xorg Intel TearFree option]] is a known workaround to tearing problems on Intel adapters, however the way this option acts makes it redundant with the use of a compositor (adds up memory consumption and lowers performance, see [https://bugs.freedesktop.org/show_bug.cgi?id=37686#c123 the original bug report's final comment]).<br />
<br />
On the other hand, GNOME Shell uses Mutter as a compositor which has a tweak known to address tearing problems (see [https://bugzilla.gnome.org/show_bug.cgi?id=657071#c1 the original suggestion for this fix] and its mention in [https://bugs.freedesktop.org/show_bug.cgi?id=37686#c59 the Freedesktop bug report]): the line {{ic|1=CLUTTER_PAINT=disable-clipped-redraws:disable-culling}} must be appended to {{ic|/etc/environment}} and Xorg server restarted. This tweak solved tearing problems.<br />
<br />
=== Logging in through GDM or lightdm quickly returns to the login screen without any feedback ===<br />
As discovered by the person in [http://forums.debian.net/viewtopic.php?f=6&t=84115 this] thread, some aspect of checking for the existence of and then sourcing a bash_completion script seems to cause this issue. In addition to the bash completion setup in package {{Pkg|bash-completion}}, the Ruby Version Manager (RVM) includes the invocation of a bash completion script as part of it's init. It's worth keeping in mind that whatever causes this issue likely exists outside the exclusive realm of bash completion scripts, and that /etc/profile* is still worth poking around in while debugging even if a completion script isn't found.<br />
<br />
=== Gnome System Icons are not loaded properly ===<br />
Problems with the loading of system icons, such the ones in the title bar of Files, might be solved by [[pacman#Installing specific packages|(re)installing]] the package {{Pkg|gdk-pixbuf2}}.<br />
<br />
This may also fix the "oh no" screen and/or very slow loading and login with GDM as described in [https://bbs.archlinux.org/viewtopic.php?pid=1414157 this] thread.<br />
<br />
== External links ==<br />
* [http://www.gnome.org/ The Official Website of GNOME]<br />
* [http://extensions.gnome.org/ Extensions for GNOME-shell]<br />
* Themes, icons, and backgrounds:<br />
** [http://art.gnome.org/ GNOME Art]<br />
** [http://www.gnome-look.org/ GNOME Look]<br />
* GTK/GNOME programs:<br />
** [http://www.gnomefiles.org/ GNOME Files]<br />
** [http://www.gnome.org/projects/ GNOME Project Listing]</div>Dreivier