GNOME/Guide/ko

From Gentoo Wiki
< GNOME
Jump to:navigation Jump to:search
This page is a translated version of the page GNOME/Guide and the translation is 18% complete.
Outdated translations are marked like this.

GNOME is a popular desktop environment capable launching Xorg and Wayland sessions. This guide attempts to describe all aspects of GNOME, including installation, configuration, and usage.

Since version 3.30, GNOME on Gentoo is able to once again run on OpenRC.[1] See GNOME without systemd for more detail.

그놈이 무엇인가요?

프로젝트

그놈 프로젝트는 유닉스/리눅스 데스크톱 프로그램 모음 및 개발 플랫폼으로서의 그놈을 개발하는데 공헌하는 자유 소프트웨어 프로젝트 입니다. 그놈 재단은 그놈 프로젝트의 개발 및 다른 분야를 위해 조직되어 있습니다.

프로그램

그놈은 데스크톱 환경이자 개발 플랫폼입니다. 이 자유 소프트웨어는 여러 산업 리더들이 선택한 데스크톱 구성요소입니다. 직장인, 가정, 개발자들에게 관심을 가지고 있습니다.

커뮤니티

다른 거대한 자유 소프트웨어 프로젝트와 같이 그놈은 잠재적으로 더 많은 사용자 및 개발자 기반을 보유하고 있습니다. 그놈 플래닛그놈 개발자 사이트에 그놈 개발자들이 모여있는 것처럼 그놈 해커와 기여자들이 모여있습니다. 그놈 라이브러리에는 최종 사용자를 위한 막대한 양의 그놈 자원을 보유하고 있씁니다. 그놈의 세상에는 그놈 관련 뉴스에 대한 인기 있는 수집 프로그램이 있습니다.

Prerequisites

Historically speaking, the Xorg display server was the standard display base for all desktop environments on Linux. With GNOME 3 and beyond, a shift to the Wayland, a newer display server protocol, has begun. Systems other than NVIDIA will have no problem running GNOME sessions over Wayland.

That said, as a general fall back, it is a good idea to first read and follow the instructions in the Xorg Guide to setup a X environment.

According to GNOME upstream, GNOME 40 is written with the systemd init system in mind. Because of this, it is a good idea for systemd users to read and comply with all necessary kernel settings from the systemd article.

그놈 설치

Profile

그놈 설치를 시작하기 전에, USE 변수를 편집하는 것이 좋습니다. X, gtk, gnome/etc/portage/make.conf의 USE 변수에 있는지 확인하십시오. 그놈이 추가적으로 사용하는 시스템 메시지 버스 dbus 지원을 사용하려는 경우 USE 플래그에 추가하십시오. KDE(또 다른 거대한 데스크톱 환경입니댜) 지원을 필요로 하지 않는다면, qt4kde를 제거하십시오. USE 플래그를 뺄 때는 음수 부호(-)를 앞에 붙여 사용하시면 됩니다. 음수 부호를 제대로 사용하느 예제는 아래에서 살펴보십시오.

중요
Read relevant documentation before performing any profile changes.

OpenRC

OpenRC users using logind can select the GNOME OpenRC profile:

root #eselect profile set default/linux/amd64/17.1/desktop/gnome

systemd

경고
Read the systemd documentation before changing to a systemd profile.

systemd users will want to select the following profile:

root #eselect profile set default/linux/amd64/17.1/desktop/gnome/systemd

Make sure that X, gtk, and gnome are in the USE variable located in /etc/portage/make.conf. It is recommended to enable support for D-Bus system-wide. systemd includes this system message bus.

파일 /etc/portage/make.conf그놈 환경에 맞춘 플래그 예제
USE="-qt4 -kde X dbus gtk gnome"
참고
desktop/gnome 프로파일을 사용한다면, 이 USE 플래그는 알아서 설정될 것입니다. eselect profile list 를 실행하여 프로파일을 확인할 수 있습니다. 루트권한으로 eselect profile set <profile-name>을 실행하면 설정을 수정할 수 있습니다. "<profile-name>" 부분은 숫자로 바꾸거나 바꾸려는 프로파일의 이름으로 바꾸십시오.

Emerge

이 과정이 끝나면 gnome을 이머지하여 그놈 설치를 시작하십시오:

root #emerge gnome-base/gnome

gnome-light를 사용하여 최소한으로 그놈을 설치할 수 있습니다. 이 옵션은 전체 그놈 설치에서 제공하는 추가 도구 없이 간편하게 설치하기 때문에 추가 꾸러미는 나중에 설치해야 합니다.

root #emerge --ask gnome-base/gnome-light

Also, consider disabling previewer for gnome-base/nautilus along with removing GNOME online accounts on low end devices to avoid net-libs/webkit-gtk and reduce build time:

파일 /etc/portage/package.use/nautilusDisabling previewer for nautilus
gnome-base/nautilus -previewer

}}

참고
{{{1}}}

좀 시간이 오래걸릴테니, 엄마가 사준 아직 펼쳐보지 못한 책을 읽어보는것이 좋겠습니다. 다 됐나요? 좋습니다. 이제 환경 변수를 업데이트할 차례입니다:

root #env-update && source /etc/profile

다음 남은 서비스와 사용자 그룹을 정리하겠습니다.

plugdev 그룹이 있는지 확인하십시오. 만약 있다면, 각 그놈 사용자가 그룹의 구성원이 될 수 있게 하는데 도움이 될 것입니다만, 이 단계는 선택 여부에 따라 달려있습니다(더이상 이 그룹은 일반적인 요소가 아닙니다).

root #getent group plugdev
plugdev:x:104:

다음 명령의 <username>을 그놈 사용자의 사용자 이름으로 바꾸십시오:

root #gpasswd -a yourUserName plugdev

첫 인상

우리가 방금 빌드한 모습을 보도록 하겠습니다. 루트 쉘을 빠져나가고 일반 사용자 계정으로 로그온 하십시오. 다음, startx 명령을 내리면 그놈을 실행할 수 있게 세션 관리자를 설정하겠습니다.(Xorg 안내서의 startx 사용하기를 참조하십시오):

Enabling GDM

참고
Help on troubleshooting issues with GDM can be found in the GNOME/GDM article.

OpenRC

For OpenRC systems, elogind is a dependency of GDM and must be started for GDM to run properly:

root #rc-update add elogind boot
root #rc-service elogind start

Next add display-manager-init to the default runlevel and start the service:

root #emerge --ask --noreplace gui-libs/display-manager-init

In /etc/conf.d/display-manager set DISPLAYMANAGER to "gdm"

파일 /etc/conf.d/display-manager
DISPLAYMANAGER="gdm"

To start on boot, add display-manager to the default runlevel:

root #rc-update add display-manager default

To start GDM either reboot or start it with rc immediately:

root #rc-service display-manager start

systemd

To start GDM upon boot:

root #systemctl enable gdm.service

To start GDM immediately, run:

root #systemctl start gdm.service
요령
The following command both enables and starts GDM immediately:
root #systemctl enable --now gdm.service

Another suggestion is to activate Network Manager, in case no other network managing service is activated.

Using startx

Exit the root shell and log in as a regular user. The next step is to configure the session manager to run GNOME when the the startx command is invoked (see using startx in the Xorg guide for more information).

user $echo "exec gnome-session" > ~/.xinitrc

gnome-base/gnome-session-2.26.2로 시작할 때, 데스크톱 시작시 ~/.xinitrc 방식을 사용할 경우 그놈 메뉴를 가져오도록 XDG_MENU_PREFIX 변수를 추가해야 합니다. (만약 ~/.xinitrc를 사용하지 않는다면 이 변수가 자동으로 처리됩니다. 더 이상의 추가 설정은 필요하지 않습니다.)

user $sed -i '1i\export XDG_MENU_PREFIX=gnome-' ~/.xinitrc

이제 startx를 실행하여 그래픽 환경을 시작하십시오:

user $startx

모든 부분이 잘 돌아간다면 GNOME에서는 반가운 인사말을 표시합니다. 그놈 설정 성공을 축하합니다!

Privacy

Removing GNOME online accounts in the control center

Some users might be concerned about the fact that there is an online accounts section is the GNOME control center, which enables the user to connect the system to various services like Google, Microsoft, etc. In Portage, a USE flag can be set to remove this functionality:

파일 /etc/portage/make.conf
USE="... -gnome-online-accounts"

This will tell Portage to not install the net-libs/gnome-online-accounts package if possible.

Re-emerge world with the --changed-use flag and clean unused dependencies.

root #emerge --ask --changed-use --update --deep @world
root #emerge --depclean
참고
Because of gnome-extra/gnome-contacts package being part of gnome-base/gnome via gnome-base/gnome-core-apps, the -gnome-online-accounts USE cannot be set as gnome-extra/gnome-contacts makes this a hard requirement to be enabled. gnome-base/gnome-light is an alternative though several other packages may be required for a full experience.

Configuration

Mixed localization

It could be general to have C as the global default locale, with a different one for the desktop. This can be achieved by add settings:

파일 ~/.config/environment.d/01_localize.confOverride locale for user session
LANG="zh_CN.utf8"
LC_MESSAGES="zh_CN.utf8"
LC_TIME="zh_CN.utf8"

Then choose the region for locale in gnome-setting-center, or via command:

user $gsettings set org.gnome.system.locale region 'zh_CN.utf8'
참고
With global locale default to C, only set the region is not likely to change the locale for desktop, for which, configuration in environment.d is necessary, especially the LC_MESSAGES variable. And to make it work for sure, the following packages may be necessary: ≥ sys-apps/systemd-249.6-r1 and ≥ gnome-base/gnome-40.0.

Log out, make sure the old session is killed and re-login, these settings will be applied to the new session.

To override session's locale for terminal in gnome, add:

파일 ~/.bashrcOverride locale for terminal
LANG="C.utf8"
LC_MESSAGES="C.utf8" 
LC_TIME="C.utf8"

Tweaking GNOME

For extra configuration options in GNOME 40 install the gnome-extra/gnome-tweaks package. The tweak tool allows customization at a deeper level than the standard Settings frame.

Advanced tweaking

Advanced tweaking for GNOME can be performed from the command line via the gsettings or dconf commands or graphically via dconf-editor. All modifiable settings are accessible using these tools. For more information, see upstream's documentation.

Widgets in GNOME 40

By default on Gentoo GNOME 40 does not support widgets. For users who wish to obtain widget functionality a separate package is available:

root #emerge --ask gnome-extra/gnome-shell-extensions

After the shell extensions are installed, eselect can be used to control defaults on a global level:

root #eselect gnome-shell-extensions list
Available extensions (* means enabled for all users by default):
  [1]   alternate-tab@gnome-shell-extensions.gcampax.github.com
  [2]   apps-menu@gnome-shell-extensions.gcampax.github.com
  [3]   auto-move-windows@gnome-shell-extensions.gcampax.github.com
  [4]   drive-menu@gnome-shell-extensions.gcampax.github.com
  [5]   launch-new-instance@gnome-shell-extensions.gcampax.github.com
  [6]   native-window-placement@gnome-shell-extensions.gcampax.github.com
  [7]   places-menu@gnome-shell-extensions.gcampax.github.com
  [8]   screenshot-window-sizer@gnome-shell-extensions.gcampax.github.com
  [9]   user-theme@gnome-shell-extensions.gcampax.github.com
  [10]  window-list@gnome-shell-extensions.gcampax.github.com
  [11]  windowsNavigator@gnome-shell-extensions.gcampax.github.com
  [12]  workspace-indicator@gnome-shell-extensions.gcampax.github.com

Enable click-to-install Shell Extensions through the web browser

For web browsers such as Google Chrome, Chromium, and Vivaldi be sure to get the required browser add-on through the Chrome store: https://chrome.google.com/webstore/detail/gphhapmejobijbbhgpjhcjognlahblep

After the add-on has been installed for the browser of choice, a backend must also be emerged:

root #emerge --ask gnome-extra/gnome-browser-connector

It should now be possible to install, manage, and uninstall shell extensions at https://extensions.gnome.org/

If things are not working as expected check the upstream installation instructions for news.

Non-root user authentication for dialogs

Certain GNOME dialogs such as Printers, adding wireless networks, and Users require administrator authentication. This is handled through sys-auth/polkit and operates independently from app-admin/sudo. By default in Gentoo, the root account is the only administrator, and so even if a user account can run root commands through sudo, authentication in these GNOME dialogs will fail.

If you would like all users of the group wheel to be administrators, create a copy of /usr/share/polkit-1/rules.d/50-default.rules starting with a number lower than 50, and edit the line return ["unix-user:0"] to the following:

파일 /etc/polkit-1/rules.d/49-wheel.rulesAdministrator wheel group
polkit.addAdminRule(function(action, subject) {
    return ["unix-group:wheel"];
});

The Polkit page provides more details on rules configuration.

GNOME hotspot

In order for gnome-hotspot to work, the wireless card must support AP (access point) infrastructure mode. The following package USE flags are also needed:

파일 /etc/portage/package.useConnection Sharing and Access Point Support
net-misc/networkmanager connection-sharing
net-wireless/wpa_supplicant ap

In addition, the following kernel options are necessary:

커널 NAT options (locations for kernel 4.14)
Networking support (NET [=y])
    Networking options --->
        Network packet filtering framework (Netfilter) (NETFILTER [=y]) --->
            IP: Netfilter Configuration --->
                <*/M> IPv4 NAT (CONFIG_NF_NAT_IPv4)
                <*/M> IPv4 masquerade support
                <*/M> IP tables support (required for filtering/masq/NAT) (IP_NF_IPTABLES [=y])
                <*/M> iptables NAT support

제거

Unmerge

그놈 설치를 확실하게 제거하는 방법은 gnome-base/gnome 꾸러미를 분명하게 설치 제거하고 꾸러미 의존 요소를 제거하는 방식입니다.

제대로 삭제하려면 포티지 저장소를 동기화했는지 확인하십시오:

root #emerge --sync

world를 업데이트하여 시스템을 완전히 최신상태로 만드십시오:

root #emerge --ask --update --newuse --deep --with-bdeps=y @world

그놈 베이스 꾸러미를 언머지하십시오:

root #emerge --ask --depclean gnome-base/gnome

마지막으로 의존 요소를 제거하십시오:

root #emerge --ask --depclean

이제 그놈을 제거했습니다.

Troubleshooting

Login failure with message "Oh no something has gone wrong"

One source of this error can be the permissions for the video device. When logging in fails and a message appears that says "Oh no, something has gone wrong", then try to become a member of the video group. Add the user to the video group with gpasswd like so:

root #gpasswd -a <user> video

GNOME on Wayland session is not launching with NVIDIA

Attempting to launch GNOME on Wayland sessions is a known issue. Unfortunately some older versions of the NVIDIA binary blob drivers are not compatible with Wayland. Systems that simply have older versions of the NVIDIA binary blob driver installed, but are not using it, can see this workaround.

For at least gnome-base/gdm-44.1 it is required to set NVreg_PreserveVideoMemoryAllocations=1 in /etc/modprobe.d/nvidia.conf, otherwise Wayland support is being disabled.

GNOME built-in screen recorder is not working

GNOME's screen recorder uses vp8 codec which is developed by Google. The recorder needs this codec and pipewire screencast feature to record the desktop. It can be enabled it via the the vpx and screencast USE flags in either the make.conf or package.use files.

파일 /etc/portage/make.conf
USE="vpx screencast"

GNOME and Pinentry not working with GPG

For example when using Evolution to sign emails with PGP, the private key needs to be decrypted. If this key has a password, a Pinentry dialogue trys to open. To enable the Gtk version, these configuration files need to be edited.

파일 ~/.gnupg/gpg.conf
use-agent
pinentry-mode loopback
파일 ~/.gnupg/gpg-agent.conf
pinentry-program /usr/bin/pinentry-gnome3

외부 자료

References


This page is based on a document formerly found on our main website gentoo.org.
The following people contributed to the original document: Lars Strojny,
They are listed here because wiki history does not allow for any external attribution. If you edit the wiki article, please do not add yourself here; your contributions are recorded on each article's associated history page.