https://wiki.archlinux.org/api.php?action=feedcontributions&user=C0n5t4ntK&feedformat=atom
ArchWiki - User contributions [en]
2024-03-28T12:15:46Z
User contributions
MediaWiki 1.41.0
https://wiki.archlinux.org/index.php?title=Steam_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=658088
Steam (简体中文)
2021-04-07T16:52:41Z
<p>C0n5t4ntK: 维护至目前最新版</p>
<hr />
<div>[[Category:Gaming (简体中文)]]<br />
[[de:Steam]]<br />
[[en:Steam]]<br />
[[fi:Steam]]<br />
[[ja:Steam]]<br />
{{Related articles start (简体中文)}}<br />
{{Related|Steam/Troubleshooting}}<br />
{{Related|Steam/Game-specific troubleshooting}}<br />
{{Related|Gaming}}<br />
{{Related|Gamepad}}<br />
{{Related|List of games (简体中文)}}<br />
{{Related articles end}}<br />
{{TranslationStatus (简体中文)|Steam|2021-04-08|654297}}<br />
[http://store.steampowered.com/about/ Steam] 是维尔福公司推出的著名游戏分发平台。<br />
<br />
{{注意|对于 Linux 平台,Steam 只支持 Ubuntu 的长期支持版本[https://support.steampowered.com/kb_article.php?ref&#61;1504-QHXN-8366]。 因此,请不要向维尔福(Valve)公司提交 issue 以获得 Steam 对 Arch Linux 的支持。}}<br />
<br />
== 安装 ==<br />
<br />
启用 [[multilib]] 仓库并[[Help:Reading (简体中文)#安装软件包|安装]] {{Pkg|steam}} 软件包。<br />
<br />
你需要满足下列要求从而在 Arch Linux 上运行 Steam:<br />
<br />
* 安装 32 位版本的 [[Xorg#Driver installation|OpenGL 图形驱动]]。<br />
* 生成 [[Locale#Generating locales|en_US.UTF-8]] 语言环境,以避免非法指针错误。<br />
* 其图形界面大量使用 Arial 字体。详见 [[Microsoft fonts]] 。你可以通过安装 {{Pkg|ttf-liberation}} 或使用 [[Steam/Troubleshooting#Text is corrupt or missing|Steam 支持的字体问题]] 中的方法来解决。<br />
* 安装 {{Pkg|wqy-zenhei}} 以支持亚洲地区语言。<br />
<br />
=== SteamCMD ===<br />
<br />
安装 {{AUR|steamcmd}} 以使用命令行版本的 [https://developer.valvesoftware.com/wiki/SteamCMD Steam]。<br />
<br />
=== 可选 Flatpak 安装 ===<br />
<br />
Steam 也可以作为 {{ic|com.valvesoftware.Steam}} 使用 [[Flatpak]] 从 [https://flathub.org/ Flathub] 中安装。使用 Flathub 仓库和 flatpak 命令行安装是目前最简单的安装方式:<br />
<br />
flatpak --user remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo<br />
flatpak --user install flathub com.valvesoftware.Steam<br />
flatpak run com.valvesoftware.Steam<br />
<br />
目前 Flatpak 应用还不支持主题。并且你不能通过 {{ic|optirun}}/{{ic|primusrun}} 来运行游戏,更多细节详见 [https://github.com/flatpak/flatpak/issues/869 Issue#869]。<br />
<br />
默认情况下通过 Flatpak 安装的 Steam 不会有访问你的家目录的权限,并且由于安全问题,强行忽略此权限限制会导致 Steam 无法运行。不过,你可以自由地在家目录之外添加一个目录。如果你想添加一个外部库,你可以运行下面的命令来添加:<br />
<br />
flatpak override com.valvesoftware.Steam --filesystem=/path/to/directory<br />
<br />
==== Flatpak 的亚洲字体问题 ====<br />
<br />
如果你遇到了游戏中无法显示亚洲字体的问题,这是因为 org.freedesktop.Platform 并没有包含合适的字体文件进去。首先尝试挂载你的本地字体:<br />
<br />
flatpak run --filesystem=~/.local/share/fonts --filesystem=~/.config/fontconfig com.valvesoftware.Steam<br />
<br />
如果上述命令不起作用,考虑动手 hack 一下:直接将字体文件复制进 org.freedesktop.Platform 的目录下以启用字体,例如<br />
<br />
# replace ? with your version and hash<br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/etc/fonts/conf.avail<br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/etc/fonts/conf.d <br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/share/fonts<br />
<br />
== 目录结构 ==<br />
<br />
Steam 的默认安装位置是 {{ic|~/.local/share/Steam}}。如果 Steam 无法找到该目录,它会引导你重新安装或选择一个新的安装位置。这篇文章使用 {{ic|~/.steam/root}} 符号链接来表示 Steam 的安装位置。<br />
<br />
=== 库文件夹 ===<br />
<br />
每一个 Steam 应用都有一个独一无二的应用 ID,你可以通过 [http://store.steampowered.com/ Steam Store] 页面来找到它。<br />
<br />
Steam 将游戏安装到 {{ic|''LIBRARY''/steamapps/common/}} 目录下。库文件夹 {{ic|''LIBRARY''}} 一般会是<br />
{{ic|~/.steam/root}},但是你依然可以选择拥有多个库文件夹如 (''Steam > Settings > Downloads > Steam Library Folders'')。<br />
<br />
为了 Steam 能够正确识别游戏,它需要在 {{ic|''LIBRARY''/steamapps/}} 目录下找到 {{ic|appmanifest_''AppId''.acf}} 文件。此清单文件使用了<br />
[https://developer.valvesoftware.com/wiki/KeyValues KeyValues] 格式,并且它的 {{ic|installdir}} 的内容决定了游戏的目录名称。<br />
<br />
== 用法 ==<br />
<br />
steam [ -options ] [ steam:// URL ]<br />
<br />
对于可用的命令行选择,详见 [https://developer.valvesoftware.com/wiki/Command_Line_Options#Steam_.28Windows.29 Command Line Options article on the Valve Developer Wiki]。<br />
<br />
Steam 也可以接受可选的 Steam URL,详见 [https://developer.valvesoftware.com/wiki/Steam_browser_protocol Steam browser procotol]。<br />
<br />
== 启动选项 ==<br />
<br />
当你运行一个 Steam 游戏时,Steam 会使用 [[Bash]] shell 执行它的 '''启动命令'''。<br />
为了让你自由修改启动命令,Steam 提供了 '''启动选项'''。<br />
'''启动选项'''可以通过右键点击你的游戏库中的游戏,选择属性后点击'''设置启动选项'''进行修改。<br />
<br />
默认情况下 Steam 只是简单的把你设置的参数字符串添加到游戏的启动命令后。想要设置环境变量或者将一个启动命令作为参数传递给另一个命令,你可以使用 {{ic|%command%}} 以表示原启动命令。<br />
<br />
=== 示例 ===<br />
<br />
* 仅设置参数: {{ic|-foo}}<br />
* 设置环境变量: {{ic|1=FOO=bar BAZ=bar %command% -baz}}<br />
* 设置与默认完全不同的命令: {{ic|othercommand # %command%}}<br />
<br />
== 提示与技巧 ==<br />
<br />
=== 最小化启动 ===<br />
<br />
在系统启动时,使 Steam 以最小化方式自启在系统托盘处是可以实现的,并且不会占据鼠标焦点。仅仅需要添加 {{ic|-silent}} 到自启文件的参数列表中。<br />
<br />
{{hc|~/.config/autostart/steam.desktop|<nowiki><br />
...<br />
Exec=/usr/bin/steam -silent<br />
...</nowiki>}}<br />
<br />
=== Fsync 补丁 ===<br />
<br />
维尔福(Valve)公司 [https://steamcommunity.com/app/221410/discussions/0/3158631000006906163/ 发布] 了一个可以帮助提升大量多线程应用运行帧率的特殊内核补丁。这里有一些使用这个补丁的方法:<br />
<br />
* 直接使用维尔福(Valve)公司提供的二进制内核。详见 [[Unofficial user repositories#valveaur]] 并且一旦你添加了这个仓库,内核软件包 <span class="archwiki-template-pkg">linux-fsync</span> 和 <span class="archwiki-template-pkg">linux-fsync-headers</span> 便可使用。你也将可能需要将某些常用软件包 (例如 {{pkg|nvidia}}) 替换为 [[DKMS]] 软件包 (例如 {{pkg|nvidia-dkms}})。<br />
* 安装 {{Pkg|linux-zen}} 内核,其从 5.2 版本开始已包括 fsync 补丁。[https://github.com/zen-kernel/zen-kernel/commit/f39367fdbc68e8b1e623239d13db6efaa5a67ae1]<br />
* 安装 {{AUR|linux-pf}} 或 {{AUR|linux-pf-git}} 内核。<br />
<br />
=== Proton Steam-Play ===<br />
<br />
维尔福(Valve)公司开发了一个兼容性工具,用来使 Steam 可以在 Wine 和其他额外组件上运行。这使得你可以运行很多原本只能在 Windows 平台上运行的游戏 (详见 [https://www.protondb.com/ compatibility list])。<br />
<br />
此工具开源并且可以从 [https://github.com/ValveSoftware/Proton/ Github] 获得。Steam 将在 Steam Play 启用后安装它相适应的 Proton 版本。<br />
<br />
Proton 需要在 Steam 客户端启用: {{ic|Steam > 设置 > Steam Play}}。你可以为了上述那些没有被维尔福公司列入白名单的游戏启用 Steam Play。<br />
<br />
如果需要的话,为了在启动游戏时强制启用 Proton 或者指定一个确定的 Proton 版本,在游戏处右击,点击 {{ic|属性 > 常规 > 强制使用特定 Steam Play 兼容性工具}},然后选择所需版本。这样做同样可以用来强制游戏生成一个 Linux 入口用以运行 Windows 版本的游戏。<br />
<br />
你同样可以从 AUR 通过安装 {{AUR|proton}} 或 {{AUR|proton-git}} 来安装 Proton,但是需要一些额外的配置才能使 Steam 良好运行。想要了解 Steam 如何识别已安装的 Proton 的更多细节,可以前往 Proton 的 Github 页面。<br />
<br />
=== 无窗口管理器的大屏幕模式 ===<br />
<br />
想要从 [[Display manager (简体中文)]] 运行 Steam 的大屏幕模式,你可以选择以下任意一个方案:<br />
<br />
* 安装 {{AUR|steamos-compositor}}<br />
* 或者,安装 {{AUR|steamos-compositor-plus}},这可以隐藏 Proton 游戏启动时恼人的颜色闪烁,并修复游戏在后台运行的问题。<br />
* 手动添加一个 Steam 入口 (''但是你会失去 Steam 的混合平台优势:主要体现在你'''不能'''在大屏幕模式下使用键盘或手柄控制''):<br />
<br />
创建一个 {{ic|/usr/share/xsessions/steam-big-picture.desktop}} 文件,其中包含:<br />
<br />
{{hc|/usr/share/xsessions/steam-big-picture.desktop|<nowiki><br />
[Desktop Entry]<br />
Name=Steam Big Picture Mode<br />
Comment=Start Steam in Big Picture Mode<br />
Exec=/usr/bin/steam -bigpicture<br />
TryExec=/usr/bin/steam<br />
Icon=<br />
Type=Application</nowiki>}}<br />
<br />
=== Steam 皮肤 ===<br />
<br />
使用皮肤可以自定义 Steam 界面。皮肤可以被位于 {{ic|~/.steam/root}} 的界面定义文件所覆盖。<br />
<br />
想要安装一个皮肤:<br />
<br />
# 将皮肤的目录放于 {{ic|~/.steam/root/skins}}。<br />
# 按照 ''Steam > 设置 > 界面'' 依次点击并选择该皮肤。<br />
# 重启 Steam。<br />
<br />
你可以在 [http://forums.steampowered.com/forums/showthread.php?t=1161035 Steam 论坛] 获得比较完备的皮肤列表。<br />
<br />
{{注意|使用一个过期的皮肤可能会引起一些可视化错误。}}<br />
<br />
==== 自创皮肤 ====<br />
<br />
几乎所有的 Steam 风格会定义在 {{ic|~/.steam/root/resource/styles/steam.styles}} (此文件超过 3,500 行)。对于一个可以被 Steam 识别的皮肤,它需要自己的 {{ic|resource/styles/steam.styles}} 文件。<br />
当一个 Steam 的更新改变了官方的 {{ic|steam.styles}} 文件,你的皮肤可能会过期,会有造成可视化错误的潜在风险。<br />
<br />
详见 {{ic|~/.steam/root/skins/skins_readme.txt}} 以获得如何创建皮肤的初步指引。<br />
<br />
=== 改变 Steam 的通知位置 ===<br />
<br />
默认情况下 Steam 的通知会在屏幕底端右侧出现。<br />
<br />
你可以改变 Steam 通知出现的位置,通过更改 {{ic|Notifications.PanelPosition}} 文件,具体位于<br />
<br />
* {{ic|resource/styles/steam.styles}} 以调整桌面通知<br />
* {{ic|resource/styles/gameoverlay.styles}} 以调整游戏中通知<br />
<br />
以上两个文件都将在 Steam 启动时被覆写,且 {{ic|steam.styles}} 只会在启动时被读取。<br />
<br />
{{注意|一些游戏并不遵守位于 {{ic|gameoverlay.styles}} 里的设置。如《幽浮:未知敌人》。}}<br />
<br />
==== 使用一个皮肤 ====<br />
<br />
你可以创建一个皮肤去将通知位置改变成你想要的那样。比如你想要将位置设置成顶部右侧:<br />
<br />
$ cd ~/.steam/root/skins<br />
$ mkdir -p Top-Right/resource<br />
$ cp -r ~/.steam/root/resource/styles Top-Right/resource<br />
$ sed -i '/Notifications.PanelPosition/ s/"[A-Za-z]*"/"TopRight"/' Top-Right/resource/styles/*<br />
<br />
==== 实时更新 ====<br />
<br />
{{ic|gameoverlay.styles}} 文件可以在 Steam 运行时更改,这允许你对不同游戏设置不同的通知位置。<br />
<br />
{{hc|~/.steam/notifpos.sh|<br />
sed -i "/Notifications.PanelPosition/ s/\"[A-Za-z]*\"/\"$1\"/" ~/.steam/root/resource/styles/gameoverlay.styles<br />
}}<br />
<br />
由此 [[#启动选项]] 应该像下面这样:<br />
<br />
~/.steam/notifpos.sh TopLeft && %command%<br />
<br />
=== Steam 远程同乐 ===<br />
<br />
{{注意|Steam 家庭流媒体 [https://store.steampowered.com/news/51761/ 已更新为 Steam 远程同乐]。}}<br />
<br />
Steam 内置对于 [http://store.steampowered.com/streaming/ 远程同乐] 的支持。<br />
<br />
前往 [https://steamcommunity.com/sharedfiles/filedetails/?id=680514371 Steam 社区指南] 以了解如何在 Linux 上设置无头模式的流媒体服务。<br />
<br />
=== Steam Controller ===<br />
<br />
通常一个 Steam Controller 手柄需要使用 Steam 界面。不过在非 Steam 原生的 Linux 游戏中这种界面并不很实用。对此,当 Steam 客户端运行时,其会保持一个“桌面配置”。如果你有 Steam Controller 手柄,请在桌面配置中将其设置为通用 XBOX 控制器。只要 Steam 客户端在运行,你可以在其他游戏中使用 Steam Controller 手柄,例如 GOG 的游戏, 就像一个 XBOX 手柄。请确保在“常规手柄设置”已经选择了你的手柄类型。<br />
<br />
=== 使用 Proton/其他兼容层 与 Windows 共享游戏 ===<br />
<br />
多亏了维尔福(Valve)公司,使用 Proton 的游戏体验有所提升。你可以用自定义的分支如 [https://github.com/GloriousEggroll/proton-ge-custom Proton GE] 或其他的分支来提升很多游戏的运行效果,并且你甚至可以在 NTFS 文件系统下创建一个 Steam 库,不过你需要注意现在登录的用户 uid 和 gid 有相关权限,否则 Steam 可能无法写入所需的文件;并且你也需要确保在你的 [[fstab]] 下不要有 noexec 选项,否则 Steam 无法扫描到你的游戏。<br />
<br />
== 故障排除 ==<br />
<br />
参见 [[Steam/Troubleshooting]].<br />
<br />
== 另见 ==<br />
<br />
* [https://wiki.gentoo.org/wiki/Steam Gentoo Wiki article]<br />
* [https://pcgamingwiki.com/wiki/The_Big_List_of_DRM-Free_Games_on_Steam The Big List of DRM-Free Games on Steam] 位于 PCGamingWiki<br />
* [http://steam.wikia.com/wiki/List_of_DRM-free_games List of DRM-free games] 位于 Wikia<br />
* [http://store.steampowered.com/browse/linux Steam Linux store]<br />
* [https://github.com/ValveSoftware/Proton/ Proton] 支持 Steam Play 运行的基于 Wine 以及其他额外组件的兼容性工具</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=ArchWiki:Translation_Team_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=593819
ArchWiki:Translation Team (简体中文)
2020-01-03T09:05:59Z
<p>C0n5t4ntK: /* 页面维护列表 */ 更新状态</p>
<hr />
<div>[[Category:简体中文]]<br />
[[Category:ArchWiki (简体中文)]]<br />
[[ar:ArchWiki:Translation Team]]<br />
[[cs:ArchWiki:Translation Team]]<br />
[[el:ArchWiki:Translation Team]]<br />
[[en:ArchWiki:Translation Team]]<br />
[[es:ArchWiki:Translation Team]]<br />
[[fr:ArchWiki Translation Team]]<br />
[[hr:ArchWiki:Translation Team]]<br />
[[it:ArchWiki:Translation Team]]<br />
[[ja:ArchWiki 翻訳チーム]]<br />
[[ko:ArchWiki:Translation Team]]<br />
[[nl:ArchWiki:Translation Team]]<br />
[[pl:ArchWiki:Translation Team]]<br />
[[pt:ArchWiki:Translation Team]]<br />
[[ru:ArchWiki:Translation Team]]<br />
[[sk:ArchWiki:Translation Team]]<br />
[[zh-hant:ArchWiki:Translation Team]]<br />
Arch Wiki 上有许多中文页面,这其中大部分是从外文翻译过来的,这些页面是无数中文志愿者劳动的结晶。随着时间推移,有些页面因为没有及时维护,内容严重过时。而目前的翻译工作缺少组织,效率偏低。所以参照西班牙和意大利翻译组的做法,添加这个页面。<br />
<br />
如果你希望对Arch Wiki做贡献,参与Wiki建设,比如翻译英文页面和对已翻译过的中文页面进行维护,只需要编辑下面的[[#页面维护列表]],添加相应的条目,并将自己加为相关页面的维护者。如果你在列表中还没有找到想要翻译的页面,可以自行添加。另外,如果因为时间原因无法再维护页面,请及时将自己从维护者列表中删除。<br />
<br />
== 创建翻译 ==<br />
{{警告|如果不准备翻译页面的大部分内容,请尽量不要新建简体中文页面。检查英文页面的更新需要花费不少精力,没有翻译的页面会增加维护负担。}}<br />
# 如果还不知道如何编辑 wiki,请阅读 [[Help:Editing (简体中文)|编辑帮助]]。<br />
# 阅读 [[Help:i18n (简体中文)|i18n帮助]],文章给出了 ArchWiki 国际化和本地化的指南。<br />
# [[Special:UserLogin|登录]] 以进行编辑。<br />
# 选择要翻译的页面,例如从 [[Special:Random|随机页面]] 或[[#页面维护列表|页面维护列表]] 中选择一个未翻译完成的页面。假设要翻译 [[Some Page]].<br />
# 进入选择的英文页面,点击页面顶部的 '''编辑'''。<br />
# 添加要翻译文件的语言间链接, 简体中文的话加入<nowiki>[[zh-hans:Some Page]]</nowiki>,其它语言参见[[Help:i18n#Interlanguage links]])。<br />
# 复制所有页面代码。<br />
# 保存页面 (新加了语言链接)<br />
# 访问页面左边新添加的语言链接,应该会进到 [[Some Page (简体中文)]] : {{ic|<nowiki>https://wiki.archlinux.org/index.php/Some_Page_(</nowiki>''简体中文'')}}<br />
# 因为页面不存在,点击 '''创建'''。<br />
# 将显示一个编辑器 - 粘贴复制的英文页面。<br />
# 将文章分类修改为本地化版本,例如将 {{ic|<nowiki>[[Category:Internationalization]]</nowiki>}} 修改为 {{ic|<nowiki>[[Category:Internationalization (简体中文)]]</nowiki>}},参阅[[Help:Category (简体中文)]].<br />
# 修改语言间链接,指向英文页面(将 {{ic|zh-hans}} 修改为 {{ic|en}},并将英文页面移到文章顶部。<br />
# 翻译页面,进行保存。<br />
# (推荐)给翻译完成的页面加上[[Template:TranslationStatus (简体中文)|翻译状态]],后有详细介绍。<br />
# 更新所有其它语言页面,加入刚翻译文章的语言间链接。<br />
# (可选)创建一个简体中文名称的页面,指向新创建的页面:访问 {{ic|<nowiki>https://wiki.archlinux.org/index.php/</nowiki>''页面的中文名称''}}.<br />
# (可选)建立新页面,并加入:{{bc|<nowiki>#REDIRECT [[Some Page (简体中文)</nowiki>]]}}<br />
<br />
== Templates ==<br />
<br />
{{Translateme (简体中文)|Not translated}}<br />
<br />
The following table lists the [[Help:Template (简体中文)|templates]] that should be translated and their Simplified Chinese equivalent.<br />
<br />
{| class=wikitable<br />
! English template || Simplified Chinese version<br />
|-<br />
! colspan=2| Article templates<br />
|-<br />
| [[Template:Related articles start]] || [[Template:Related articles start (简体中文)]]<br />
|-<br />
| [[Template:Yes]] || [[Template:是]]<br />
|-<br />
| [[Template:No]] || [[Template:否]]<br />
|-<br />
| [[Template:Tip]] || [[Template:提示]]<br />
|-<br />
| [[Template:Note]] || [[Template:注意]]<br />
|-<br />
| [[Template:Warning]] || [[Template:警告]]<br />
|-<br />
| [[Template:Dead link]] || [[Template:失效链接]]<br />
|-<br />
| [[Template:Broken package link]] || {{-}}<br />
|-<br />
! colspan=2| Translation status templates<br />
|-<br />
| [[Template:Bad translation]] || {{-}}<br />
|-<br />
| [[Template:Translateme]] || [[Template:Translateme (简体中文)]]<br />
|-<br />
| [[Template:TranslationStatus]] || [[Template:TranslationStatus (简体中文)]]<br />
|-<br />
! colspan=2| Special templates<br />
|-<br />
| [[Template:Cat main]] || {{-}}<br />
|-<br />
| [[Template:Template]] || {{-}}<br />
|}<br />
<br />
== 完善翻译 ==<br />
[https://wiki.archlinux.org/index.php?title=Special:WhatLinksHere/Template:Translateme_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&limit=100 这个页面] 包含了需要完善翻译的简体中文页面。完善翻译的基本步骤:<br />
# 选择自己比较熟悉的文章进行翻译<br />
# 先检查英文页面的对应段落,更新成最新的英文后再翻译,避免翻译过时的内容,减少信息遗漏。<br />
# 翻译完成后删除页面中的 <nowiki>{{translateme (简体中文)}}</nowiki> 标记<br />
# (推荐)给翻译完成的页面加上[[Template:TranslationStatus (简体中文)|翻译状态]],后有详细介绍。<br />
<br />
== 更新过期页面 == <br />
如果发现有 Wiki 页面过期或错误:<br />
* 小的改动,有时间可以立即进行修改同步,维护者并不控制页面的编辑权限,越多的人参与维护越好。如果改动较大,请先联系维护者,避免重复劳动。<br />
* 没有时间查看更改,请给页面加上 {{ic|<nowiki>{{out of date}}</nowiki>}} 模版,这样其他贡献者更容易发现需要更新的页面,而读者看到过期标记就可以直接查看英文页面,以免被错误内容误导,白白耽误时间。<br />
* 没有时间翻译,请将过期的中文部分删去,从英文页面中复制更改的部分到中文页面的相应部分,去掉{{ic|<nowiki>{{out of date}}</nowiki>}}模板(如果页面上有的话)并加上{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板,这样其他贡献者就更容易发现需要翻译的页面,而读者也不会被过期的内容误导。<br />
如果发现有页面未翻译:<br />
* 有时间的话,请将页面中的英文部分翻译为中文,并去掉{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板。<br />
* 没有时间翻译,请为页面添加{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板,这样其他的贡献者就能更容易发现需要翻译的页面。<br />
{{注意|在修改页面上的模板时,请同时更新页面维护列表的翻译状态。}}<br />
<br />
== 翻译任务 ==<br />
=== 模板 Article summary 变更为 Related ===<br />
因为 Summary 中的简介基本上和正文的介绍一样,所以页面左边的介绍栏进行了简化,只保留相关文章功能。英文页面正在进行大规模修改,相应的中文页面也需要同步更新。<br />
<br />
需要注意的地方:<br />
* 将第一行改成<br />
: <nowiki>{{Related articles start (简体中文)}}</nowiki><br />
* 如果英文的相关文章存在中文翻译,则替换为简体中文页面。示例:<br />
: <nowiki>{{Related2|Display Manager (简体中文)|显示管理器}}</nowiki><br />
* 示例:[https://wiki.archlinux.org/index.php?title=Start_X_at_Login&diff=0&oldid=270155 英文变更], [https://wiki.archlinux.org/index.php?title=Start_X_at_Login_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=285643&oldid=242662 对应的翻译]<br />
<br />
== 维护翻译 ==<br />
完成页面的翻译只是初步完成任务,及时同步英文页面改动、更新翻译是一个持续性的工作,可能会耗费更多的时间。<br />
<br />
=== 页面认领 ===<br />
所有人都可以认领页面。认领后的责任包括进行翻译,关注英文页面的改动,及时同步翻译。<br />
<br />
为了更好的跟踪英文页面的修改,请务必在设置中启用监视列表邮件通知,并监视对应的英文页面(从设置中找到监视列表,加入英文页面。或者直接到英文页面点击页面顶端的监视标签。这样只要有改动,就会收到邮件通知)。<br />
<br />
{{小贴士|如果收到邮件通知后没有访问页面或者访问了页面却没有登录用户,下次页面改动时就不会再发邮件通知。可以点击监视列表中的'''标记所有页面为已读'''再次获取更新。}}<br />
<br />
如果页面有维护者但长期得不到更新,将会在维护列表中删除维护者。<br />
<br />
=== 翻译状态模板 ===<br />
Arch 作为滚动发行版,软件变化比较快,对应的文档变化也比较快。许多翻译的文章由于缺乏更新,会产生命令运行出错或不起作用等问题。而由于这些过期页面没有及时标记出来,所以用户无法及时获得更新。[[Template:TranslationStatus (简体中文)|翻译状态模板]]就是为了解决这个问题而创建。<br />
<br />
此模板可以起到如下作用:<br />
* 为用户提供翻译状况,包括翻译时间、英文页面的最后版本等<br />
* 用户可以点击查看翻译后,英文页面的改动,这样英文不是很好的用户可以只查看很小一部分英文内容,并判断出是否影响操作。<br />
* 翻译人员可以跟踪页面状况,通过[[Special:WhatLinksHere/Template:TranslationStatus_(简体中文)|模板的反向链接]]可以查找到所有标记页面,查看需要更新翻译的部分。<br />
<br />
[[Template:TranslationStatus (简体中文)|模板页面]]有详细的使用方法。<br />
<br />
=== 页面维护列表 ===<br />
{{注意|请按照拉丁字母顺序添加页面。}}<br />
<br />
翻译状态说明:<br />
;过期:页面内容未与英文页面同步,对应{{ic|<nowiki>{{out of date}}</nowiki>}} 模版<br />
;未翻译:页面中含有英文内容,对应{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板<br />
;完成:页面已与英文页面同步<br />
<br />
{| class="wikitable sortable collapsible" border="1"<br />
|-<br />
! 页面<br />
! 翻译状态<br />
! 维护者<br />
! class="unsortable" width="30%" | 备注<br />
|-<br />
| [[acpid (简体中文)]]<br />
| 过期<br />
| Cael<br />
|<br />
|-<br />
| [[Advanced Linux Sound Architecture (简体中文)]]<br />
| 翻译中<br />
| ihonliu<br />
| 无<br />
|-<br />
| [[Arch based distributions (active) (简体中文)]]<br />
| 完成<br />
| Joshua<br />
| 勘误中<br />
|-<br />
| [[Arch boot process (简体中文)]]<br />
| 翻译中<br />
| Bangbo Zheng<br />
| <br />
|-<br />
| [[Amateur radio (简体中文)]]<br />
| 翻译中<br />
| liu-shuyuan<br />
| <br />
|-<br />
| [[AMD Catalyst (简体中文)]]<br />
| 过期<br />
| Shibao Zhao<br />
| 无<br />
|-<br />
| [[ATI (简体中文)]]<br />
| 完成<br />
| skysailing<br />
| 无<br />
|-<br />
| [[AUR helpers (简体中文)]]<br />
| 完成<br />
| Kurobac<br />
| 部分用词可能需要修改<br />
|-<br />
| [[awesome (简体中文)]]<br />
| 进行中<br />
| Cael<br />
| 无<br />
|-<br />
| [[BIND (简体中文)]]<br />
| 完成<br />
| Dargasia<br />
|<br />
|-<br />
| [[Bumblebee (简体中文)]]<br />
| 完成<br />
| Peter<br />
| 无<br />
|-<br />
| [[Chromium (简体中文)]]<br />
| 完成<br />
| Bobby<br />
| 无<br />
|-<br />
| [[Ceph (简体中文)]]<br />
| 翻译中<br />
| Aaron Chen<br />
| 部分未翻译 <br />
|-<br />
| [[Cinnamon (简体中文)]]<br />
| 部分翻译 <br />
| Bobby<br />
| 部分未翻译 <br />
|- <br />
| [[Common Applications (简体中文)]]<br />
| 部分翻译 <br />
| DavidChen<br />
| 翻译中<br />
|-<br />
| [[Common Applications/Science (简体中文)]]<br />
| drop maintain<br />
| 更新,翻译中<br />
|<br />
|-<br />
| [[Compiz (简体中文)]]<br />
| 翻译中<br />
| xiii_1991<br />
| 20140813开始<br />
|-<br />
| [[Conky (简体中文)]]<br />
| 完成<br />
| upi<br />
| 无<br />
|-<br />
| [[Core utilities (简体中文)]]<br />
| 完成<br />
| rentaro, Arisaka<br />
| 无<br />
|-<br />
|-<br />
| [[Clover (简体中文)]]<br />
| 完成<br />
| Yume Kankawa<br />
| 无<br />
|-<br />
| [[Disk cloning (简体中文)]]<br />
| 翻译中<br />
| _spaike97<br />
| 无<br />
|-<br />
| [[Dynamic Kernel Module Support (简体中文)]]<br />
| 完成<br />
| Mithrandir<br />
| 完善中<br />
|-<br />
| [[Emacs (简体中文)]]<br />
| 翻译中<br />
| Jaurung yuanhang<br />
| 未完成<br />
|-<br />
| [[File recovery (简体中文)]]<br />
| 翻译中<br />
| _spaike97<br />
| 无<br />
|-<br />
| [[Fish (简体中文)]]<br />
| 完成<br />
| liu-shuyuan<br />
|<br />
|-<br />
| [[Flatpak (简体中文)]]<br />
| 完成<br />
| C0n5t4ntK<br />
| 长期维护中<br />
|-<br />
| [[Font configuration (简体中文)]]<br />
| 翻译中<br />
| Jaurung<br />
| 完善中<br />
|-<br />
| [[Fonts (简体中文)]]<br />
| 翻译中<br />
| qqbzg<br />
| 无<br />
|-<br />
| [[GDM (简体中文)]]<br />
| 翻译中<br />
| Junjie Yuan<br />
| 绝大多数内容未翻译,重新进行翻译<br />
|-<br />
| [[GNOME (简体中文)]]<br />
| 完成<br />
| skywet<br />
| <br />
|-<br />
| [[GRUB (简体中文)]]<br />
| 完成<br />
| Armodeniz<br />
| <br />
|-<br />
| [[GRUB/Tips and tricks (简体中文)]]<br />
| 完成<br />
| Armodeniz<br />
| <br />
|-<br />
| [[Java (简体中文)]]<br />
| 翻译中<br />
| CaCaCarrot<br />
| 无<br />
|-<br />
| [[KDE (简体中文)]]<br />
| 过期<br />
| <br />
| <br />
|-<br />
| [[LAMP (简体中文)]]<br />
| 完成<br />
| Liuzhengyi<br />
| 勘误中<br />
|-<br />
| [[LibreOffice (简体中文)]]<br />
| 完成<br />
| qqbzg<br />
| 勘误中<br />
|-<br />
| [[Libvirt (简体中文)]]<br />
| 完成<br />
| Kurobac<br />
| 需要格式改进<br />
|-<br />
| [[Local Mirror (简体中文)]]<br />
| 完成<br />
| Jason Zhang<br />
| 完善中<br />
|- <br />
| [[MATLAB (简体中文)]]<br />
| 部分翻译 <br />
| Liu Qinyang<br />
|<br />
|-<br />
| [[Minecraft (简体中文)]]<br />
| 完成 <br />
| Xavier Lau<br />
| 页面已经与英文版同步,长期维护中<br />
|-<br />
| [[NetworkManager (简体中文)]]<br />
| 翻译中 <br />
| Jack-lijing, leeking <br />
| 请优先翻译<br />
|-<br />
| [[Network Time Protocol daemon (简体中文)]]<br />
| 完成<br />
| sid<br />
| 完善中<br />
|-<br />
| [[Unofficial user repositories (简体中文)]]<br />
| 翻译中<br />
| TransistorLogic<br />
| 无<br />
|-<br />
| [[OpenOffice (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Opera (简体中文)]]<br />
| 未翻译<br />
| Bobby<br />
| 请优先翻译此文 <br />
|-<br />
| [[Pacman GUI Frontends (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Pidgin (简体中文)]]<br />
| 进行中<br />
| Cael<br />
| 无 <br />
|-<br />
| [[Python打包指引 (简体中文)]]<br />
| 翻译中<br />
| SherlockHolo<br />
| 无<br />
|- <br />
| [[ranger (简体中文)]]<br />
| 完成<br />
| Jason Zhang<br />
| 完善中<br />
|-<br />
| [[Raspberry Pi (简体中文)]]<br />
| 翻译中<br />
| Mithrandir<br />
| <br />
|-<br />
| [[Reporting bug guidelines (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[SDDM (简体中文)]]<br />
| 完成<br />
| C0n5t4ntK<br />
| 长期维护中<br />
|-<br />
| [[Secure Shell (简体中文)]]<br />
| 完成<br />
| Arisaka<br />
| 无<br />
|-<br />
| [[Smart Common Input Method platform (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Steam (简体中文)]]<br />
| 完成<br />
| C0n5t4ntK<br />
| 长期维护中<br />
|-<br />
| [[Systemd-timesyncd (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[TLP (简体中文)]]<br />
| 完成<br />
| Skywet<br />
| 持续更新中 <br />
|-<br />
| [[Tomcat (简体中文)]]<br />
| 完成<br />
| Starwing117<br />
| 持续更新中 <br />
|-<br />
| [[Vim (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[VirtualBox (简体中文)]]<br />
| 翻译至 2017-10-15<br />
| [[User:5long]]<br />
|<br />
|-<br />
| [[VMware (简体中文)]]<br />
| 完成<br />
| ThomasWFan<br />
| 页面已经与英文版同步,长期维护中<br />
|- <br />
| [[Xfce (简体中文)]]<br />
| 完成 <br />
| 无<br />
| 无<br />
|-<br />
| [[Xmonad (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Xrandr (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=Flatpak_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=593583
Flatpak (简体中文)
2019-12-30T13:37:41Z
<p>C0n5t4ntK: 删除中文斜体效果,润色部分语句。</p>
<hr />
<div>[[Category:Development (简体中文)]]<br />
[[en:Flatpak]]<br />
[[es:Flatpak]]<br />
[[ja:Flatpak]]<br />
[[pt:Flatpak]]<br />
{{Related articles start}}<br />
{{Related|Snapd}}<br />
{{Related|bubblewrap}}<br />
{{Related articles end}}<br />
{{TranslationStatus (简体中文)|Flatpak|2019-12-30|592857}}<br />
引自项目 [https://github.com/flatpak/flatpak/blob/master/README.md README]:“[http://flatpak.org Flatpak] 是一个 Linux 桌面程序的构建、分发和沙箱化运行系统。”<br />
<br />
引自 {{man|1|flatpak}}:<br />
<br />
:Flatpak 是一个用来管理应用和应用所使用的运行时的工具。在 Flatpak 模型中,应用的构建和分发不依赖其主系统,并且它们在运行时一定程度上独立于主系统('沙箱化')。<br />
:Flatpak 使用 [https://ostree.readthedocs.io/en/latest/ OSTree] 以分发和部署数据。它使用的仓库是 OSTree 仓库并且可以用 ostree 的工具来操作。已安装的运行时和应用都已经过 OSTree 检出。<br />
<br />
== 安装 ==<br />
<br />
[[Help:Reading (简体中文)#安装软件包|安装]] {{pkg|flatpak}} 软件包。<br />
<br />
{{注意|如果你想使用 {{ic|flatpak-builder}} 来构建 flatpak,你将需要安装可选的依赖 {{pkg|elfutils}} 和 {{pkg|patch}}。}}<br />
<br />
== 管理仓库 ==<br />
<br />
=== 添加一个仓库 ===<br />
<br />
要添加一个远程 flatpak 仓库,执行:<br />
<br />
$ flatpak remote-add ''name'' ''location''<br />
<br />
这其中 ''name'' 是新远程仓库的名字,而 ''location'' 是路径或仓库的 URL。<br />
<br />
例如要添加官方仓库 [https://flathub.org/ Flathub repository]:<br />
<br />
$ flatpak remote-add --if-not-exists flathub <nowiki>https://dl.flathub.org/repo/flathub.flatpakrepo</nowiki><br />
<br />
=== 删除一个仓库 ===<br />
<br />
要删除一个远程 flatpak 仓库,执行:<br />
<br />
$ flatpak remote-delete ''name''<br />
<br />
这其中 ''name'' 是要删除的远程仓库的名字。<br />
<br />
=== 仓库列表 ===<br />
<br />
要列出所有已添加的仓库列表,执行:<br />
<br />
$ flatpak remotes<br />
<br />
== 管理运行时和应用 ==<br />
<br />
=== 搜索远程仓库的运行时和应用 ===<br />
<br />
在能搜索新添加的远程仓库中的运行时和应用之前,我们需要为此获取软件应用流的数据:<br />
<br />
{{hc|$ flatpak update|<br />
Looking for updates...<br />
Updating appstream data for remote ''name''<br />
}}<br />
<br />
之后我们可以通过 {{ic|flatpak search ''packagename''}} 命令来实现搜索,例如在配置完成的远程仓库 {{ic|flathub}} 中搜索 {{ic|libreoffice}} 软件包:<br />
<br />
{{hc|$ flatpak search libreoffice|<br />
Application ID Version Branch Remotes Description <br />
org.libreoffice.LibreOffice stable flathub The LibreOffice productivity suite<br />
}}<br />
<br />
=== 列出所有可用的运行时和应用 ===<br />
<br />
要列出远程仓库 ''remote'' 中所有可用的运行时和应用,执行:<br />
<br />
$ flatpak remote-ls ''remote''<br />
<br />
=== 安装一个运行时或应用 ===<br />
<br />
要安装一个运行时或应用,执行:<br />
<br />
$ flatpak install ''remote'' ''name''<br />
<br />
这其中 ''remote'' 是远程仓库的名字,而 ''name'' 是待安装的应用或运行时的名字。<br />
<br />
{{提示|您可以使用部分标识符 {{ic|flatpak install ''partial-name''}} (例如 {{ic|flatpak install libreoffice}})。}}<br />
<br />
=== 列出所有已安装的运行时和应用 ===<br />
<br />
要列出所有已安装的运行时和应用,执行:<br />
<br />
$ flatpak list<br />
<br />
=== 运行应用 ===<br />
<br />
Flatpak 应用也可以通过命令行运行:<br />
<br />
$ flatpak run ''name''<br />
<br />
=== 升级一个运行时或应用 ===<br />
<br />
要升级一个名为 ''name'' 的运行时或应用,执行:<br />
<br />
$ flatpak update ''name''<br />
<br />
=== 卸载一个运行时或应用 ===<br />
<br />
要卸载一个名为 ''name'' 运行时或应用,执行:<br />
<br />
$ flatpak uninstall ''name''<br />
<br />
{{提示|你可以卸载不再使用的 flatpak 依赖(即无应用/运行时依赖的孤立包),执行 {{ic|flatpak uninstall --unused}}。}}<br />
<br />
=== 添加 Flatpak .desktop 文件到您的菜单 ===<br />
Flatpak 期望窗口管理器按照 XDG_DATA_DIRS 环境变量来查找应用。这可能需要重启此会话,或者启动器可能并不支持这些。这种情况下您想要编辑需要扫描的目录列表,可将如下路径添加到变量中:<br />
<br />
~/.local/share/flatpak/exports/share/applications<br />
/var/lib/flatpak/exports/share/applications<br />
<br />
目前已知此方法在 Awesome 中是必须的。<br />
<br />
=== 查看应用沙箱的权限 ===<br />
Flatpak 应用遵守着预定义的沙箱规则,这些规则规定了应用允许访问的资源文件系统目录。<br />
要查看确切的应用权限,执行:<br />
$ flatpak info --show-permissions ''name''<br />
沙箱权限的依赖列表可以在 [https://docs.flatpak.org/en/latest/sandbox-permissions-reference.html 官方 flatpak 说明] 中找到。<br />
<br />
=== 覆盖应用的沙箱权限 ===<br />
如果你发现应用的预定义权限过松或过紧,你可以使用 {{ic|flatpak override}} 命令更改任何你希望更改的地方。<br />
例如:<br />
flatpak override --nofilesystem=home ''name''<br />
这会禁止应用访问你的家目录。<br />
<br />
所有可以赋予权限的类型,如设备、文件系统或 socket ,都有一行命令以独立选择允许或禁止确切的权限。例如,允许访问设备时可以是 {{ic|1=--device=''device_name''}},而 {{ic|1=--nodevice=''device_name''}} 会禁止访问设备。<br />
<br />
对于所有可操作的权限类型,详见:{{man|1|flatpak-override}}<br />
<br />
下面的命令可将所有更改过的权限重设为默认:<br />
$ flatpak override --reset ''name''<br />
<br />
== 创建自定义基本运行时 ==<br />
<br />
{{Expansion|这些内容当然是可以补充的。对于 GNOME 应用它同样存在 D-Bus 相关问题。}}<br />
<br />
{{警告|如果你想向公众发布一个作为 Flatpak 的软件,那么基于 Arch 系统的运行时是不合适的。在这种情况下,您应根据 [http://docs.flatpak.org 官方说明] 来使用 [http://flatpak.org/runtimes.html 共有运行时] 将您的软件融入进合适的 Flatpak 生态系统中。}}<br />
<br />
{{注意|你可能想要使用一个不被信任的、无特权的用户账户来打包不被信任的软件,因为软件在创建应用和运行时期间是没有被沙箱化的。}}<br />
<br />
{{注意|当向其他人分发软件包时,您可能需要遵守法定义务,应要求提供一些已打包软件的源代码。你可能要使用 [[ABS]] 来从源代码生成这些软件包。}}<br />
<br />
您可以创建一个自定义的、基于 Arch 的基本运行时,并通过 pacman 使用 Flatpak 的 SDK。之后您可以使用它来创建和打包应用。对于个人使用来说,这是除了默认的 {{ic|org.freedesktop.BasePlatform}} 和 {{ic|org.freedesktop.BaseSdk}} 运行时之外的另一个选择。<br />
<br />
除了 {{Pkg|flatpak}} 以外,您需要安装 {{Pkg|fakeroot}},而为了使 pacman hooks 支持,您也需要安装 {{Pkg|fakechroot}}。<br />
<br />
首先,创建一个目录以用来作为生成运行时/应用的位置。<br />
<br />
$ mkdir ''myflatpakbuilddir''<br />
$ cd ''myflatpakbuilddir''<br />
<br />
之后您可以准备一个目录作为生成运行时基本平台的位置。这些文件子目录将会成为之后沙箱中的 {{ic|/usr}} 目录的内容。因此您将需要创建符号链接使得默认 {{ic|/usr/share}} 等源自 Arch 的路径仍然可以由通常的路径访问。<br />
<br />
$ mkdir -p ''myruntime''/files/var/lib/pacman<br />
$ touch ''myruntime''/files/.ref<br />
$ ln -s /usr/usr/share ''myruntime''/files/share<br />
$ ln -s /usr/usr/include ''myruntime''/files/include<br />
$ ln -s /usr/usr/local ''myruntime''/files/local<br />
<br />
使您的主系统字体在 Arch 运行时中可用:<br />
<br />
$ mkdir -p ''myruntime''/files/usr/share/fonts<br />
$ ln -s /run/host/fonts ''myruntime''/files/usr/share/fonts/flatpakhostfonts<br />
<br />
您需要或想要在为运行时安装软件包之前调整您的 {{ic|pacman.conf}}。复制 {{ic|/etc/pacman.conf}} 到您的构建目录,之后再进行下列改变:<br />
<br />
* 移除 {{ic|CheckSpace}} 选项,即 pacman 将不会抱怨检测硬盘空间时发现根文件系统的错误。<br />
* 移除所有不需要的自定义仓库和 {{ic|IgnorePkg}},{{ic|IgnoreGroup}},{{ic|NoUpgrade}} 和 {{ic|NoExtract}} 的设置,即只有主系统需要的这些仓库。<br />
<br />
现在为运行时安装软件包。<br />
<br />
$ fakechroot fakeroot pacman -Syu --root ''myruntime''/files --dbpath ''myruntime''/files/var/lib/pacman --config pacman.conf base<br />
$ mv pacman.conf ''myruntime''/files/etc/pacman.conf<br />
<br />
通过编辑 {{ic|''myruntime''/files/etc/locale.gen}} 设置所用的 [[Locale (简体中文)|locales]]。之后重新生成运行时的 locales。<br />
<br />
$ fakechroot chroot ''myruntime''/files locale-gen<br />
<br />
基本 SDK 可以通过基本运行时加上创建软件包和运行 pacman 所需要的应用来创建。<br />
<br />
$ cp -r ''myruntime'' mysdk<br />
$ fakechroot fakeroot pacman -S --root mysdk/files --dbpath mysdk/files/var/lib/pacman --config mysdk/files/etc/pacman.conf base-devel fakeroot fakechroot --needed<br />
<br />
插入运行时和 SDK 的元数据。<br />
<br />
{{hc|''myruntime''/metadata|2=<br />
[Runtime]<br />
name=org.mydomain.BasePlatform<br />
runtime=org.mydomain.BasePlatform/x86_64/2016-06-26<br />
sdk=org.mydomain.BaseSdk/x86_64/2016-06-26<br />
}}<br />
<br />
{{hc|mysdk/metadata|2=<br />
[Runtime]<br />
name=org.mydomain.BaseSdk<br />
runtime=org.mydomain.BasePlatform/x86_64/2016-06-26<br />
sdk=org.mydomain.BaseSdk/x86_64/2016-06-26<br />
}}<br />
<br />
加入基本运行时和 SDK 到目前目录的本地仓库中。您可能想要给它们附上合适的提交(commit)信息如 “My Arch base runtime” 和 “My Arch base SDK”。<br />
<br />
$ ostree init --mode archive-z2 --repo=.<br />
$ EDITOR="nano -w" ostree commit -b runtime/org.mydomain.BasePlatform/x86_64/2016-06-26 --tree=dir=''myruntime''<br />
$ EDITOR="nano -w" ostree commit -b runtime/org.mydomain.BaseSdk/x86_64/2016-06-26 --tree=dir=mysdk<br />
$ ostree summary -u<br />
<br />
安装运行时和 SDK。<br />
<br />
$ flatpak remote-add --user --no-gpg-verify myarchos file://$(pwd)<br />
$ flatpak install --user myarchos org.mydomain.BasePlatform 2016-06-26<br />
$ flatpak install --user myarchos org.mydomain.BaseSdk 2016-06-26<br />
<br />
=== 使用 pacman 创建应用 ===<br />
<br />
作为创建应用 [http://flatpak.org/developer.html 通常方式]的一种替代方案,我们可以使用 pacman 创建普通 Arch 软件包的一种容器化版本。注意 {{ic|/usr}} 目录在创建应用时是只读的,故我们在创建一个应用时不能使用 Arch 的软件包。要使用 pacman 创建一个真正的应用,我们可以<br />
<br />
* 使用 pacman 创建一个包含所有依赖包的运行时<br />
* 之后 [http://flatpak.org/developer.html 像往常一样] 自己编译应用,或可能通过自定义 [[PKGBUILD]] 为 Flatpak 特制的 pacman 使用 {{ic|1=--prefix=/app}} 制作 {{ic|configure}} 脚本,<br />
<br />
或者我们可以<br />
* 使用 pacman 创建一个包含所有通过 pacman 安装的应用的运行时<br />
* 之后创建一个虚拟应用来启动它。<br />
<br />
对于使用后一种方法,首先通过 pacman 创建一个运行时,比如这一个为了 {{Pkg|gedit}}。这个运行时是首先初始化,准备与 pacman 一起使用的。<br />
<br />
$ flatpak build-init -w geditruntime org.mydomain.geditruntime org.mydomain.BaseSdk org.mydomain.BasePlatform 2016-06-26<br />
$ flatpak build geditruntime sed -i "s/^#Server/Server/g" /etc/pacman.d/mirrorlist<br />
$ flatpak build geditruntime ln -s /usr/var/lib /var/lib<br />
$ flatpak build geditruntime fakeroot pacman-key --init<br />
$ flatpak build geditruntime fakeroot pacman-key --populate archlinux<br />
<br />
之后这个软件包安装完成。主系统的网络必须能够使 pacman 正常工作。<br />
<br />
$ flatpak build --share=network geditruntime fakechroot fakeroot pacman --root /usr -S gedit<br />
<br />
你可以在完成运行时前测试安装是否成功(未进行合适的沙箱化)。<br />
<br />
$ flatpak build --socket=x11 geditruntime gedit<br />
<br />
现在结束创建运行时并将其导出到一个新的本地仓库。pacman 的 GnuPG 密钥可能会有许可冲突,故需要先被移除。<br />
<br />
$ flatpak build geditruntime rm -r /etc/pacman.d/gnupg<br />
$ flatpak build-finish geditruntime<br />
$ sed -i "s/\[Application\]/\[Runtime\]/;s/runtime=org.mydomain.BasePlatform/runtime=org.mydomain.geditruntime/" geditruntime/metadata<br />
$ flatpak build-export -r geditrepo geditruntime<br />
<br />
接下来创建一个虚拟应用。<br />
<br />
$ flatpak build-init geditapp org.gnome.gedit org.mydomain.BaseSdk org.mydomain.geditruntime<br />
<br />
现在已经完成了构建虚拟应用。你可以在将应用沙箱化时,通过完成创建时给予额外的选项来微调它的访问权限。对于可用的选项,详见 [[#另见|Flatpak documentation]] 和 [https://gitlab.gnome.org/GNOME/gnome-apps-nightly/tree/master GNOME manifest files]。或者,可以在完成创建后按照您的期望调整 {{ic|geditapp/metadata}},但要在导出前完成。当元数据文件完成后,将应用导出到仓库。<br />
<br />
$ flatpak build-finish geditapp --socket=x11 ''[possibly other options]'' --command=gedit<br />
$ flatpak build-export geditrepo geditapp<br />
<br />
将它和运行时一起安装。<br />
<br />
$ flatpak --user remote-add --no-gpg-verify geditrepo geditrepo<br />
$ flatpak install --user geditrepo org.mydomain.geditruntime<br />
$ flatpak install --user geditrepo org.gnome.gedit<br />
$ flatpak run org.gnome.gedit<br />
<br />
== 另见 ==<br />
<br />
* [http://flatpak.org Official website]<br />
* [https://github.com/flatpak/flatpak/wiki Official Github wiki]<br />
* [[Wikipedia::Flatpak|Wikipedia page]]<br />
* [https://wiki.gnome.org/Projects/SandboxedApps Gnome SandboxedApps]<br />
* [https://community.kde.org/Guidelines_and_HOWTOs/Flatpak KDE Testing Runtime and Applications]</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=Flatpak_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=593572
Flatpak (简体中文)
2019-12-30T12:52:17Z
<p>C0n5t4ntK: 翻译完成。</p>
<hr />
<div>[[Category:Development (简体中文)]]<br />
[[en:Flatpak]]<br />
[[es:Flatpak]]<br />
[[ja:Flatpak]]<br />
[[pt:Flatpak]]<br />
{{Related articles start}}<br />
{{Related|Snapd}}<br />
{{Related|bubblewrap}}<br />
{{Related articles end}}<br />
{{TranslationStatus (简体中文)|Flatpak|2019-12-30|592857}}<br />
引自项目 [https://github.com/flatpak/flatpak/blob/master/README.md README]: "''[http://flatpak.org Flatpak] 是一个 Linux 桌面程序的构建、分发和沙箱化运行系统。''"<br />
<br />
引自 {{man|1|flatpak}}:<br />
<br />
:''Flatpak 是一个用来管理应用和应用所使用的运行时的工具。在 Flatpak 模型中,应用的构建和分发独立于其使用的系统,并且它们在一定程度上运行时独立于使用的系统('沙箱化')。''<br />
:''Flatpak 使用 [https://ostree.readthedocs.io/en/latest/ OSTree] 以分发和部署数据。它使用的仓库是 OSTree 仓库并且可以用 ostree 的工具来操作。已安装的运行时和应用都已经过 OSTree 检出。''<br />
<br />
== 安装 ==<br />
<br />
[[Help:Reading (简体中文)#安装软件包|安装]] {{pkg|flatpak}} 软件包。<br />
<br />
{{注意|如果你想使用 {{ic|flatpak-builder}} 来构建 flatpak,你将需要安装可选的依赖 {{pkg|elfutils}} 和 {{pkg|patch}}。}}<br />
<br />
== 管理仓库 ==<br />
<br />
=== 添加一个仓库 ===<br />
<br />
要添加一个远程 flatpak 仓库,执行:<br />
<br />
$ flatpak remote-add ''name'' ''location''<br />
<br />
这其中 ''name'' 是新远程仓库的名字,而 ''location'' 是路径或仓库的 URL。<br />
<br />
例如要添加官方仓库 [https://flathub.org/ Flathub repository]:<br />
<br />
$ flatpak remote-add --if-not-exists flathub <nowiki>https://dl.flathub.org/repo/flathub.flatpakrepo</nowiki><br />
<br />
=== 删除一个仓库 ===<br />
<br />
要删除一个远程 flatpak 仓库,执行:<br />
<br />
$ flatpak remote-delete ''name''<br />
<br />
这其中 ''name'' 是要删除的远程仓库的名字。<br />
<br />
=== 仓库列表 ===<br />
<br />
要列出所有已添加的仓库列表,执行:<br />
<br />
$ flatpak remotes<br />
<br />
== 管理运行时和应用 ==<br />
<br />
=== 搜索远程仓库的运行时和应用 ===<br />
<br />
在能搜索新添加的远程仓库中的运行时和应用之前,我们需要为此获取软件应用流的数据:<br />
<br />
{{hc|$ flatpak update|<br />
Looking for updates...<br />
Updating appstream data for remote ''name''<br />
}}<br />
<br />
之后我们可以通过 {{ic|flatpak search ''packagename''}} 命令来实现搜索,''例如''在配置完成的远程仓库 {{ic|flathub}} 中搜索 {{ic|libreoffice}} 软件包:<br />
<br />
{{hc|$ flatpak search libreoffice|<br />
Application ID Version Branch Remotes Description <br />
org.libreoffice.LibreOffice stable flathub The LibreOffice productivity suite<br />
}}<br />
<br />
=== 列出所有可用的运行时和应用 ===<br />
<br />
要列出远程仓库 ''remote'' 中所有可用的运行时和应用,执行:<br />
<br />
$ flatpak remote-ls ''remote''<br />
<br />
=== 安装一个运行时或应用 ===<br />
<br />
要安装一个运行时或应用,执行:<br />
<br />
$ flatpak install ''remote'' ''name''<br />
<br />
这其中 ''remote'' 是远程仓库的名字,而 ''name'' 是待安装的应用或运行时的名字。<br />
<br />
{{提示|您可以使用部分标识符 {{ic|flatpak install ''partial-name''}} (例如 {{ic|flatpak install libreoffice}})。}}<br />
<br />
=== 列出所有已安装的运行时和应用 ===<br />
<br />
要列出所有已安装的运行时和应用,执行:<br />
<br />
$ flatpak list<br />
<br />
=== 运行应用 ===<br />
<br />
Flatpak 应用也可以通过命令行运行:<br />
<br />
$ flatpak run ''name''<br />
<br />
=== 升级一个运行时或应用 ===<br />
<br />
要升级一个名为 ''name'' 的运行时或应用,执行:<br />
<br />
$ flatpak update ''name''<br />
<br />
=== 卸载一个运行时或应用 ===<br />
<br />
要卸载一个名为 ''name'' 运行时或应用,执行:<br />
<br />
$ flatpak uninstall ''name''<br />
<br />
{{提示|你可以卸载不再使用的 flatpak 依赖(即无应用/运行时依赖的孤立包),执行 {{ic|flatpak uninstall --unused}}。}}<br />
<br />
=== 添加 Flatpak .desktop 文件到您的菜单 ===<br />
Flatpak 期望窗口管理器按照 XDG_DATA_DIRS 环境变量来查找应用。这可能需要重启此会话,或者启动器可能并不支持这些。这种情况下您想要编辑需要扫描的目录列表,可将如下路径添加到变量中:<br />
<br />
~/.local/share/flatpak/exports/share/applications<br />
/var/lib/flatpak/exports/share/applications<br />
<br />
目前已知此方法在 Awesome 中是必须的。<br />
<br />
=== 查看应用沙箱的权限 ===<br />
Flatpak 应用遵守着预定义的沙箱规则,这些规则规定了应用允许访问的资源文件系统目录。<br />
要查看确切的应用权限,执行:<br />
$ flatpak info --show-permissions ''name''<br />
沙箱权限的依赖列表可以在 [https://docs.flatpak.org/en/latest/sandbox-permissions-reference.html 官方 flatpak 说明] 中找到。<br />
<br />
=== 覆盖应用的沙箱权限 ===<br />
如果你发现应用的预定义权限过松或过紧,你可以使用 {{ic|flatpak override}} 命令更改任何你希望更改的地方。<br />
例如:<br />
flatpak override --nofilesystem=home ''name''<br />
这会禁止应用访问你的家目录。<br />
<br />
所有可以赋予权限的类型,如设备、文件系统或 socket ,都有一行命令以独立选择允许或禁止确切的权限。例如,允许访问设备时可以是 {{ic|1=--device=''device_name''}},而 {{ic|1=--nodevice=''device_name''}} 会禁止访问设备。<br />
<br />
对于所有可操作的权限类型,详见:{{man|1|flatpak-override}}<br />
<br />
下面的命令可将所有更改过的权限重设为默认:<br />
$ flatpak override --reset ''name''<br />
<br />
== 创建自定义基本运行时 ==<br />
<br />
{{Expansion|这些内容当然是可以补充的。对于 GNOME 应用它同样存在 D-Bus 相关问题。}}<br />
<br />
{{警告|如果你想向公众发布一个作为 Flatpak 的软件,那么基于 Arch 系统的运行时是不合适的。在这种情况下,您应根据 [http://docs.flatpak.org 官方说明] 来使用 [http://flatpak.org/runtimes.html 共有运行时] 将您的软件融入进合适的 Flatpak 生态系统中。}}<br />
<br />
{{注意|你可能想要使用一个不被信任的、无特权的用户账户来打包不被信任的软件,因为软件在创建应用和运行时期间是没有被沙箱化的。}}<br />
<br />
{{注意|当向其他人分发软件包时,您可能需要遵守法定义务,应要求提供一些已打包软件的源代码。你可能要使用 [[ABS]] 来从源代码生成这些软件包。}}<br />
<br />
您可以创建一个自定义的、基于 Arch 的基本运行时,并通过 pacman 使用 Flatpak 的 SDK。之后您可以使用它来创建和打包应用。对于个人使用来说,这是除了默认的 {{ic|org.freedesktop.BasePlatform}} 和 {{ic|org.freedesktop.BaseSdk}} 运行时之外的另一个选择。<br />
<br />
除了 {{Pkg|flatpak}} 以外,您需要安装 {{Pkg|fakeroot}},而为了使 pacman hooks 支持,您也需要安装 {{Pkg|fakechroot}}。<br />
<br />
首先,创建一个目录以用来作为生成运行时/应用的位置。<br />
<br />
$ mkdir ''myflatpakbuilddir''<br />
$ cd ''myflatpakbuilddir''<br />
<br />
之后您可以准备一个目录作为生成运行时基本平台的位置。这些文件子目录将会成为之后沙箱中的 {{ic|/usr}} 目录的内容。因此您将需要创建符号链接使得默认 {{ic|/usr/share}} 等源自 Arch 的路径仍然可以由通常的路径访问。<br />
<br />
$ mkdir -p ''myruntime''/files/var/lib/pacman<br />
$ touch ''myruntime''/files/.ref<br />
$ ln -s /usr/usr/share ''myruntime''/files/share<br />
$ ln -s /usr/usr/include ''myruntime''/files/include<br />
$ ln -s /usr/usr/local ''myruntime''/files/local<br />
<br />
使您的主系统字体在 Arch 运行时中可用:<br />
<br />
$ mkdir -p ''myruntime''/files/usr/share/fonts<br />
$ ln -s /run/host/fonts ''myruntime''/files/usr/share/fonts/flatpakhostfonts<br />
<br />
您需要或想要在为运行时安装软件包之前调整您的 {{ic|pacman.conf}}。复制 {{ic|/etc/pacman.conf}} 到您的构建目录,之后再进行下列改变:<br />
<br />
* 移除 {{ic|CheckSpace}} 选项,即 pacman 将不会抱怨检测硬盘空间时发现根文件系统的错误。<br />
* 移除所有不需要的自定义仓库和 {{ic|IgnorePkg}},{{ic|IgnoreGroup}},{{ic|NoUpgrade}} 和 {{ic|NoExtract}} 的设置,即只有主系统需要的这些仓库。<br />
<br />
现在为运行时安装软件包。<br />
<br />
$ fakechroot fakeroot pacman -Syu --root ''myruntime''/files --dbpath ''myruntime''/files/var/lib/pacman --config pacman.conf base<br />
$ mv pacman.conf ''myruntime''/files/etc/pacman.conf<br />
<br />
通过编辑 {{ic|''myruntime''/files/etc/locale.gen}} 设置所用的 [[Locale (简体中文)|locales]]。之后重新生成运行时的 locales。<br />
<br />
$ fakechroot chroot ''myruntime''/files locale-gen<br />
<br />
基本 SDK 可以通过基本运行时加上创建软件包和运行 pacman 所需要的应用来创建。<br />
<br />
$ cp -r ''myruntime'' mysdk<br />
$ fakechroot fakeroot pacman -S --root mysdk/files --dbpath mysdk/files/var/lib/pacman --config mysdk/files/etc/pacman.conf base-devel fakeroot fakechroot --needed<br />
<br />
插入运行时和 SDK 的元数据。<br />
<br />
{{hc|''myruntime''/metadata|2=<br />
[Runtime]<br />
name=org.mydomain.BasePlatform<br />
runtime=org.mydomain.BasePlatform/x86_64/2016-06-26<br />
sdk=org.mydomain.BaseSdk/x86_64/2016-06-26<br />
}}<br />
<br />
{{hc|mysdk/metadata|2=<br />
[Runtime]<br />
name=org.mydomain.BaseSdk<br />
runtime=org.mydomain.BasePlatform/x86_64/2016-06-26<br />
sdk=org.mydomain.BaseSdk/x86_64/2016-06-26<br />
}}<br />
<br />
加入基本运行时和 SDK 到目前目录的本地仓库中。您可能想要给它们附上合适的提交(commit)信息如 “My Arch base runtime” 和 “My Arch base SDK”。<br />
<br />
$ ostree init --mode archive-z2 --repo=.<br />
$ EDITOR="nano -w" ostree commit -b runtime/org.mydomain.BasePlatform/x86_64/2016-06-26 --tree=dir=''myruntime''<br />
$ EDITOR="nano -w" ostree commit -b runtime/org.mydomain.BaseSdk/x86_64/2016-06-26 --tree=dir=mysdk<br />
$ ostree summary -u<br />
<br />
安装运行时和 SDK。<br />
<br />
$ flatpak remote-add --user --no-gpg-verify myarchos file://$(pwd)<br />
$ flatpak install --user myarchos org.mydomain.BasePlatform 2016-06-26<br />
$ flatpak install --user myarchos org.mydomain.BaseSdk 2016-06-26<br />
<br />
=== 使用 pacman 创建应用 ===<br />
<br />
作为创建应用 [http://flatpak.org/developer.html 通常方式]的一种替代方案,我们可以使用 pacman 创建普通 Arch 软件包的一种容器化版本。注意 {{ic|/usr}} 目录在创建应用时是只读的,故我们在创建一个应用时不能使用 Arch 的软件包。要使用 pacman 创建一个真正的应用,我们可以<br />
<br />
* 使用 pacman 创建一个包含所有依赖包的运行时<br />
* 之后 [http://flatpak.org/developer.html 像往常一样] 自己编译应用,或可能通过自定义 [[PKGBUILD]] 为 Flatpak 特制的 pacman 使用 {{ic|1=--prefix=/app}} 制作 {{ic|configure}} 脚本,<br />
<br />
或者我们可以<br />
* 使用 pacman 创建一个包含所有通过 pacman 安装的应用的运行时<br />
* 之后创建一个虚拟应用来启动它。<br />
<br />
对于使用后一种方法,首先通过 pacman 创建一个运行时,比如这一个为了 {{Pkg|gedit}}。这个运行时是首先初始化,准备与 pacman 一起使用的。<br />
<br />
$ flatpak build-init -w geditruntime org.mydomain.geditruntime org.mydomain.BaseSdk org.mydomain.BasePlatform 2016-06-26<br />
$ flatpak build geditruntime sed -i "s/^#Server/Server/g" /etc/pacman.d/mirrorlist<br />
$ flatpak build geditruntime ln -s /usr/var/lib /var/lib<br />
$ flatpak build geditruntime fakeroot pacman-key --init<br />
$ flatpak build geditruntime fakeroot pacman-key --populate archlinux<br />
<br />
之后这个软件包安装完成。主系统的网络必须能够使 pacman 正常工作。<br />
<br />
$ flatpak build --share=network geditruntime fakechroot fakeroot pacman --root /usr -S gedit<br />
<br />
你可以在完成运行时前测试安装是否成功(未进行合适的沙箱化)。<br />
<br />
$ flatpak build --socket=x11 geditruntime gedit<br />
<br />
现在结束创建运行时并将其导出到一个新的本地仓库。pacman 的 GnuPG 密钥可能会有许可冲突,故需要先被移除。<br />
<br />
$ flatpak build geditruntime rm -r /etc/pacman.d/gnupg<br />
$ flatpak build-finish geditruntime<br />
$ sed -i "s/\[Application\]/\[Runtime\]/;s/runtime=org.mydomain.BasePlatform/runtime=org.mydomain.geditruntime/" geditruntime/metadata<br />
$ flatpak build-export -r geditrepo geditruntime<br />
<br />
接下来创建一个虚拟应用。<br />
<br />
$ flatpak build-init geditapp org.gnome.gedit org.mydomain.BaseSdk org.mydomain.geditruntime<br />
<br />
现在已经完成了构建虚拟应用。你可以在将应用沙箱化时,通过完成创建时给予额外的选项来微调它的访问权限。对于可用的选项,详见 [[#另见|Flatpak documentation]] 和 [https://gitlab.gnome.org/GNOME/gnome-apps-nightly/tree/master GNOME manifest files]。或者,可以在完成创建后按照您的期望调整 {{ic|geditapp/metadata}},但要在导出前完成。当元数据文件完成后,将应用导出到仓库。<br />
<br />
$ flatpak build-finish geditapp --socket=x11 ''[possibly other options]'' --command=gedit<br />
$ flatpak build-export geditrepo geditapp<br />
<br />
将它和运行时一起安装。<br />
<br />
$ flatpak --user remote-add --no-gpg-verify geditrepo geditrepo<br />
$ flatpak install --user geditrepo org.mydomain.geditruntime<br />
$ flatpak install --user geditrepo org.gnome.gedit<br />
$ flatpak run org.gnome.gedit<br />
<br />
== 另见 ==<br />
<br />
* [http://flatpak.org Official website]<br />
* [https://github.com/flatpak/flatpak/wiki Official Github wiki]<br />
* [[Wikipedia::Flatpak|Wikipedia page]]<br />
* [https://wiki.gnome.org/Projects/SandboxedApps Gnome SandboxedApps]<br />
* [https://community.kde.org/Guidelines_and_HOWTOs/Flatpak KDE Testing Runtime and Applications]</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=Flatpak_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=593530
Flatpak (简体中文)
2019-12-30T08:32:59Z
<p>C0n5t4ntK: 前三章节翻译完成。</p>
<hr />
<div>[[Category:Development (简体中文)]]<br />
[[en:Flatpak]]<br />
[[es:Flatpak]]<br />
[[ja:Flatpak]]<br />
[[pt:Flatpak]]<br />
{{Related articles start}}<br />
{{Related|Snapd}}<br />
{{Related|bubblewrap}}<br />
{{Related articles end}}<br />
引自项目 [https://github.com/flatpak/flatpak/blob/master/README.md README]: "''[http://flatpak.org Flatpak] 是一个 Linux 桌面程序的构建、分发和沙箱化运行系统。''"<br />
<br />
引自 {{man|1|flatpak}}:<br />
<br />
:''Flatpak 是一个用来管理应用和应用所使用的运行时的工具。在 Flatpak 模型中,应用的构建和分发独立于其使用的系统,并且它们在一定程度上运行时独立于使用的系统('沙箱化')。''<br />
:''Flatpak 使用 [https://ostree.readthedocs.io/en/latest/ OSTree] 以分发和部署数据。它使用的仓库是 OSTree 仓库并且可以用 ostree 的工具来操作。已安装的运行时和应用都已经过 OSTree 检验。''<br />
<br />
== 安装 ==<br />
<br />
[[Help:Reading (简体中文)#安装软件包|安装]] {{pkg|flatpak}} 软件包。<br />
<br />
{{注意|如果你想使用 {{ic|flatpak-builder}} 来构建 flatpak,你将需要安装可选的依赖 {{pkg|elfutils}} 和 {{pkg|patch}}。}}<br />
<br />
== 管理仓库 ==<br />
<br />
=== 添加一个仓库 ===<br />
<br />
要添加一个远程 flatpak 仓库,执行:<br />
<br />
$ flatpak remote-add ''name'' ''location''<br />
<br />
这其中 ''name'' 是新远程仓库的名字,而 ''location'' 是路径或仓库的 URL。<br />
<br />
例如要添加官方仓库 [https://flathub.org/ Flathub repository]:<br />
<br />
$ flatpak remote-add --if-not-exists flathub <nowiki>https://dl.flathub.org/repo/flathub.flatpakrepo</nowiki><br />
<br />
=== 删除一个仓库 ===<br />
<br />
要删除一个远程 flatpak 仓库,执行:<br />
<br />
$ flatpak remote-delete ''name''<br />
<br />
这其中 ''name'' 是要删除的远程仓库的名字。<br />
<br />
=== 仓库列表 ===<br />
<br />
要列出所有已添加的仓库列表,执行:<br />
<br />
$ flatpak remotes<br />
<br />
== 管理运行时和应用 ==<br />
<br />
=== 搜索远程仓库的运行时和应用 ===<br />
<br />
在能搜索新添加的远程仓库中的运行时和应用之前,我们需要为此获取软件应用流的数据:<br />
<br />
{{hc|$ flatpak update|<br />
Looking for updates...<br />
Updating appstream data for remote ''name''<br />
}}<br />
<br />
之后我们可以通过 {{ic|flatpak search ''packagename''}} 命令来实现搜索,''例如''在配置完成的远程仓库 {{ic|flathub}} 中搜索 {{ic|libreoffice}} 软件包:<br />
<br />
{{hc|$ flatpak search libreoffice|<br />
Application ID Version Branch Remotes Description <br />
org.libreoffice.LibreOffice stable flathub The LibreOffice productivity suite<br />
}}<br />
<br />
=== 列出所有可用的运行时和应用 ===<br />
<br />
要列出远程仓库 ''remote'' 中所有可用的运行时和应用,执行:<br />
<br />
$ flatpak remote-ls ''remote''<br />
<br />
=== 安装一个运行时或应用 ===<br />
<br />
要安装一个运行时或应用,执行:<br />
<br />
$ flatpak install ''remote'' ''name''<br />
<br />
这其中 ''remote'' 是远程仓库的名字,而 ''name'' 是待安装的应用或运行时的名字。<br />
<br />
{{提示|您可以使用部分标识符 {{ic|flatpak install ''partial-name''}} (例如 {{ic|flatpak install libreoffice}})。}}<br />
<br />
=== 列出所有已安装的运行时和应用 ===<br />
<br />
要列出所有已安装的运行时和应用,执行:<br />
<br />
$ flatpak list<br />
<br />
=== 运行应用 ===<br />
<br />
Flatpak 应用也可以通过命令行运行:<br />
<br />
$ flatpak run ''name''<br />
<br />
=== 升级一个运行时或应用 ===<br />
<br />
要升级一个名为 ''name'' 的运行时或应用,执行:<br />
<br />
$ flatpak update ''name''<br />
<br />
=== 卸载一个运行时或应用 ===<br />
<br />
要卸载一个名为 ''name'' 运行时或应用,执行:<br />
<br />
$ flatpak uninstall ''name''<br />
<br />
{{提示|你可以卸载不再使用的 flatpak 依赖(即无应用/运行时依赖的孤立包),执行 {{ic|flatpak uninstall --unused}}。}}<br />
<br />
=== 添加 Flatpak .desktop 文件到您的菜单 ===<br />
Flatpak 期望窗口管理器按照 XDG_DATA_DIRS 环境变量来查找应用。这可能需要重启此会话,或者启动器可能并不支持这些。这种情况下您想要编辑需要扫描的目录列表,可将如下路径添加到变量中:<br />
<br />
~/.local/share/flatpak/exports/share/applications<br />
/var/lib/flatpak/exports/share/applications<br />
<br />
目前已知此方法在 Awesome 中是必须的。<br />
<br />
=== 查看应用沙箱的权限 ===<br />
Flatpak 应用遵守着预定义的沙箱规则,这些规则规定了应用允许访问的资源文件系统目录。<br />
要查看确切的应用权限,执行:<br />
$ flatpak info --show-permissions ''name''<br />
沙箱权限的依赖列表可以在 [https://docs.flatpak.org/en/latest/sandbox-permissions-reference.html 官方 flatpak 说明] 中找到。<br />
<br />
=== 覆盖应用的沙箱权限 ===<br />
如果你发现应用的预定义权限过松或过紧,你可以使用 {{ic|flatpak override}} 命令更改任何你希望更改的地方。<br />
例如:<br />
flatpak override --nofilesystem=home ''name''<br />
这会禁止应用访问你的家目录。<br />
<br />
所有可以赋予权限的类型,如设备、文件系统或 socket ,都有一行命令以独立选择允许或禁止确切的权限。例如,允许访问设备时可以是 {{ic|1=--device=''device_name''}},而 {{ic|1=--nodevice=''device_name''}} 会禁止访问设备。<br />
<br />
对于所有可操作的权限类型,详见:{{man|1|flatpak-override}}<br />
<br />
下面的命令可将所有更改过的权限重设为默认:<br />
$ flatpak override --reset ''name''<br />
<br />
== Creating a custom base runtime ==<br />
<br />
{{Expansion|This can certainly be improved. It also has problems with D-Bus for GNOME apps.}}<br />
<br />
{{Warning|If you want to release your software to the public as a Flatpak, an Arch-based runtime is unsuitable. In this case, you will want to follow [http://docs.flatpak.org official documentation] to integrate your software into the proper Flatpak ecosystem using the [http://flatpak.org/runtimes.html common runtimes].}}<br />
<br />
{{Note|You may want to use an untrusted, unprivileged user account for bundling untrusted software because the software is not sandboxed during app and runtime creation.}}<br />
<br />
{{Note|When distributing bundles to others, you may be legally obliged to provide the source code of some of the bundled software upon request. You may want to use [[ABS]] to build these packages from source.}}<br />
<br />
You can create a custom Arch-based base runtime and base SDK for Flatpak using pacman. You can then use it for building and packaging applications. This is an alternative for personal use to the default {{ic|org.freedesktop.BasePlatform}} and {{ic|org.freedesktop.BaseSdk}} runtimes.<br />
<br />
In addition to {{Pkg|flatpak}}, you need to have installed {{Pkg|fakeroot}} and for pacman hooks support also {{Pkg|fakechroot}}.<br />
<br />
First, start by creating a directory for building the runtime and possibly applications.<br />
<br />
$ mkdir ''myflatpakbuilddir''<br />
$ cd ''myflatpakbuilddir''<br />
<br />
You can then prepare a directory for building the runtime base platform. The files subdirectory will contain what will later be the {{ic|/usr}} directory in the sandbox. Therefore you will need to create symbolic links so the default {{ic|/usr/share}} etc. from Arch can still be accessed at the usual path.<br />
<br />
$ mkdir -p ''myruntime''/files/var/lib/pacman<br />
$ touch ''myruntime''/files/.ref<br />
$ ln -s /usr/usr/share ''myruntime''/files/share<br />
$ ln -s /usr/usr/include ''myruntime''/files/include<br />
$ ln -s /usr/usr/local ''myruntime''/files/local<br />
<br />
Make your host OS fonts available to the Arch runtime:<br />
<br />
$ mkdir -p ''myruntime''/files/usr/share/fonts<br />
$ ln -s /run/host/fonts ''myruntime''/files/usr/share/fonts/flatpakhostfonts<br />
<br />
You need and may want to adapt your {{ic|pacman.conf}} before installing packages to the runtime. Copy {{ic|/etc/pacman.conf}} to your build directory and then make the following changes:<br />
<br />
* Remove the {{ic|CheckSpace}} option so pacman will not complain about errors finding the root filesystem for checking disk space.<br />
* Remove any undesired custom repositories and {{ic|IgnorePkg}}, {{ic|IgnoreGroup}}, {{ic|NoUpgrade}} and {{ic|NoExtract}} settings that are needed only for the host system.<br />
<br />
Now install the packages for the runtime.<br />
<br />
$ fakechroot fakeroot pacman -Syu --root ''myruntime''/files --dbpath ''myruntime''/files/var/lib/pacman --config pacman.conf base<br />
$ mv pacman.conf ''myruntime''/files/etc/pacman.conf<br />
<br />
Set up the [[Locale|locales]] to be used by editing {{ic|''myruntime''/files/etc/locale.gen}}. Then regenerate the runtime’s locales.<br />
<br />
$ fakechroot chroot ''myruntime''/files locale-gen<br />
<br />
The base SDK can be created from the base runtime with added applications needed for building packages and running pacman.<br />
<br />
$ cp -r ''myruntime'' mysdk<br />
$ fakechroot fakeroot pacman -S --root mysdk/files --dbpath mysdk/files/var/lib/pacman --config mysdk/files/etc/pacman.conf base-devel fakeroot fakechroot --needed<br />
<br />
Insert metadata about runtime and SDK.<br />
<br />
{{hc|''myruntime''/metadata|2=<br />
[Runtime]<br />
name=org.mydomain.BasePlatform<br />
runtime=org.mydomain.BasePlatform/x86_64/2016-06-26<br />
sdk=org.mydomain.BaseSdk/x86_64/2016-06-26<br />
}}<br />
<br />
{{hc|mysdk/metadata|2=<br />
[Runtime]<br />
name=org.mydomain.BaseSdk<br />
runtime=org.mydomain.BasePlatform/x86_64/2016-06-26<br />
sdk=org.mydomain.BaseSdk/x86_64/2016-06-26<br />
}}<br />
<br />
Add base runtime and SDK to a local repository in the current directory. You may want to give them appropriate commit messages such as “My Arch base runtime” and “My Arch base SDK”.<br />
<br />
$ ostree init --mode archive-z2 --repo=.<br />
$ EDITOR="nano -w" ostree commit -b runtime/org.mydomain.BasePlatform/x86_64/2016-06-26 --tree=dir=''myruntime''<br />
$ EDITOR="nano -w" ostree commit -b runtime/org.mydomain.BaseSdk/x86_64/2016-06-26 --tree=dir=mysdk<br />
$ ostree summary -u<br />
<br />
Install the runtime and SDK.<br />
<br />
$ flatpak remote-add --user --no-gpg-verify myarchos file://$(pwd)<br />
$ flatpak install --user myarchos org.mydomain.BasePlatform 2016-06-26<br />
$ flatpak install --user myarchos org.mydomain.BaseSdk 2016-06-26<br />
<br />
=== Creating apps with pacman ===<br />
<br />
As an alternative to building applications [http://flatpak.org/developer.html the usual way], we can use pacman to create a containerized version of the regular Arch packages. Note that {{ic|/usr}} is read-only when creating apps, so we can not use Arch’s packages when building an app. To create a real app with pacman, we can either<br />
<br />
* use pacman to create a runtime containing all dependencies<br />
* and compile the app ourselves [http://flatpak.org/developer.html as usual] or perhaps using pacman with a custom [[PKGBUILD]] tailored to Flatpak which uses {{ic|1=--prefix=/app}} for the {{ic|configure}} script,<br />
<br />
or we can<br />
* use pacman to create a runtime containing the app installed with pacman<br />
* and create a dummy app to launch it.<br />
<br />
For doing the latter, first create a runtime using pacman such as this one for {{Pkg|gedit}}. The runtime is first initialized and prepared for use with pacman.<br />
<br />
$ flatpak build-init -w geditruntime org.mydomain.geditruntime org.mydomain.BaseSdk org.mydomain.BasePlatform 2016-06-26<br />
$ flatpak build geditruntime sed -i "s/^#Server/Server/g" /etc/pacman.d/mirrorlist<br />
$ flatpak build geditruntime ln -s /usr/var/lib /var/lib<br />
$ flatpak build geditruntime fakeroot pacman-key --init<br />
$ flatpak build geditruntime fakeroot pacman-key --populate archlinux<br />
<br />
Then the package is installed. The host’s network connection must be made available to pacman.<br />
<br />
$ flatpak build --share=network geditruntime fakechroot fakeroot pacman --root /usr -S gedit<br />
<br />
You can test the installation before finishing the runtime (without proper sandboxing).<br />
<br />
$ flatpak build --socket=x11 geditruntime gedit<br />
<br />
Now finish building the runtime and export it to a new local repository. pacman’s GnuPG keys have permissions that may interfere and need to be removed first.<br />
<br />
$ flatpak build geditruntime rm -r /etc/pacman.d/gnupg<br />
$ flatpak build-finish geditruntime<br />
$ sed -i "s/\[Application\]/\[Runtime\]/;s/runtime=org.mydomain.BasePlatform/runtime=org.mydomain.geditruntime/" geditruntime/metadata<br />
$ flatpak build-export -r geditrepo geditruntime<br />
<br />
Then create a dummy app.<br />
<br />
$ flatpak build-init geditapp org.gnome.gedit org.mydomain.BaseSdk org.mydomain.geditruntime<br />
<br />
Now finish the dummy app. You can fine-tune the app’s access permissions when sandboxed by giving additional options when finishing the build. For possible options see the [[#See also|Flatpak documentation]] and the [https://gitlab.gnome.org/GNOME/gnome-apps-nightly/tree/master GNOME manifest files]. Alternatively, adapt {{ic|geditapp/metadata}} to your needs after finishing the build but before exporting. When the metadata file is complete, export the app to the repository.<br />
<br />
$ flatpak build-finish geditapp --socket=x11 ''[possibly other options]'' --command=gedit<br />
$ flatpak build-export geditrepo geditapp<br />
<br />
Install it along with the runtime.<br />
<br />
$ flatpak --user remote-add --no-gpg-verify geditrepo geditrepo<br />
$ flatpak install --user geditrepo org.mydomain.geditruntime<br />
$ flatpak install --user geditrepo org.gnome.gedit<br />
$ flatpak run org.gnome.gedit<br />
<br />
== See also ==<br />
<br />
* [http://flatpak.org Official website]<br />
* [https://github.com/flatpak/flatpak/wiki Official Github wiki]<br />
* [[Wikipedia::Flatpak|Wikipedia page]]<br />
* [https://wiki.gnome.org/Projects/SandboxedApps Gnome SandboxedApps]<br />
* [https://community.kde.org/Guidelines_and_HOWTOs/Flatpak KDE Testing Runtime and Applications]</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=SDDM_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=593462
SDDM (简体中文)
2019-12-29T08:44:06Z
<p>C0n5t4ntK: 修改标点。</p>
<hr />
<div>[[Category:KDE (简体中文)]]<br />
[[Category:Display managers (简体中文)]]<br />
[[en:SDDM]]<br />
[[fr:SDDM]]<br />
[[ja:SDDM]]<br />
[[ru:SDDM]]<br />
{{Related articles start (简体中文)}}<br />
{{Related|Display manager}}<br />
{{Related|KDE (简体中文)}}<br />
{{Related articles end}}<br />
{{TranslationStatus (简体中文)|SDDM|2019-12-28|592454}}<br />
[https://github.com/sddm/sddm/ Simple Desktop Display Manager] (SDDM) 是 [[KDE (简体中文)]] Plasma 桌面环境推荐的 [[Display_manager_(简体中文)|显示管理器]]。<br />
<br />
[[Wikipedia:Simple Desktop Display Manager|维基百科]] 介绍:<br />
<br />
:Simple Desktop Display Manager (SDDM) 是用于 X11 和 wayland 视窗系统的显示管理器(图形登录界面)。SDDM 完全使用 C++11 编写并支持通过 QML 改变主题。对于KDE Plasma 5,KDE 选择了 SDDM 作为 KDE Display Manager 的接替者。<br />
<br />
{{注意|SDDM 还没有完全支持 Wayland 视窗系统 [https://github.com/sddm/sddm/issues/440]。Wayland 会话在支持之列,但 SDDM 运行于 X11。}}<br />
<br />
== 安装 ==<br />
<br />
[[Help:Reading (简体中文)#安装软件包|安装]] {{Pkg|sddm}} 软件包。对于 [[KDE#KCM|KDE Config Module]],可选安装 {{Pkg|sddm-kcm}} 软件包。<br />
<br />
然后根据 [[Display manager (简体中文)#加载显示管理器]] 的说明配置 SDDM 在系统引导时启动。<br />
<br />
== 配置 ==<br />
<br />
SDDM 的默认配置文件为 {{ic|/usr/lib/sddm/sddm.conf.d/default.conf}}。要修改配置,请在 {{ic|/etc/sddm.conf.d/}} 目录下创建配置文件。详见 {{man|5|sddm.conf}} 以获得所有配置选项。<br />
<br />
{{pkg|sddm-kcm}} 软件包 (包含在 {{grp|plasma}} 用户组) 提供了一个图形用户界面以在 Plasma 系统设置中配置 SDDM。[[AUR]] 中也有基于 [[Qt]] 的配置软件 {{AUR|sddm-config-editor-git}}。<br />
<br />
一切东西都应该开箱即用,自从 Arch Linux 使用 [[systemd]] 后,SDDM 默认使用 {{ic|systemd-logind}} 以进行会话管理。<br />
<br />
=== 自动登录 ===<br />
<br />
SDDM 通过它的配置文件来支持自动登录,例如:<br />
<br />
{{hc|/etc/sddm.conf.d/autologin.conf|2=<br />
[Autologin]<br />
User=john<br />
Session=plasma.desktop<br />
}}<br />
<br />
此配置使得在系统启动后自动以用户 {{ic|john}} 开启一个 KDE Plasma 会话。在 {{ic|/usr/share/xsessions/}} 目录下你可以找到可用的会话类型。<br />
<br />
目前尚不支持自动登录 KDE Plasma 的同时锁定会话 [https://github.com/sddm/sddm/issues/306]<br />
<br />
你可以添加一个脚本,在 KDE 自动启动时激活屏幕保护程序以作为一个解决方案:<br />
<br />
#!/bin/sh<br />
/usr/bin/dbus-send --session --type=method_call --dest=org.freedesktop.ScreenSaver /ScreenSaver org.freedesktop.ScreenSaver.Lock &<br />
<br />
=== 登录后自动解锁 KDE 钱包 ===<br />
<br />
详见 [[KDE Wallet (简体中文)#在登录时自动解锁 Kwallet]]。<br />
<br />
=== 主题设置 ===<br />
<br />
在 {{ic|[Theme]}} 小节更改主题设置。如果您使用 Plasma 的系统设置,主题可能会显示预览。<br />
<br />
设置 {{ic|breeze}} 以获得 Plasma 默认主题。<br />
<br />
[[AUR]] 有一些可用的主题,例如 {{AUR|archlinux-themes-sddm}}。<br />
<br />
==== 当前主题 ====<br />
<br />
通过 {{ic|Current}} 的值设置当前主题,例如 {{ic|1=Current=archlinux-simplyblack}}。<br />
<br />
==== 编辑主题 ====<br />
<br />
默认 SDDM 主题目录为 {{ic|/usr/share/sddm/themes/}}。你可以添加你的自制主题到该目录下一个单独的子目录中。注意 SDDM 要求这些子目录的名字要与主题的名字一致。可以通过研究已安装的文件来更改或创建属于你的主题。<br />
<br />
==== 测试(预览)主题 ====<br />
<br />
如果需要,你可以预览一个 SDDM 主题。如果你想知道一个主题看起来怎么样,或是想要编辑一个主题后在不必登出的情况下观察改动的效果,那么这将会非常有用。你可以运行下面的命令:<br />
<br />
$ sddm-greeter --test-mode --theme /usr/share/sddm/themes/breeze<br />
<br />
这应该为所有已连接的显示器打开一个新窗口以显示主题的预览。<br />
<br />
{{注意|这只是一个预览。在这个模式下,一些动作如关机、挂起或登录将不会执行。}}<br />
<br />
==== 鼠标光标 ====<br />
<br />
要设置鼠标光标的主题,将 {{ic|CursorTheme}} 设置成您喜欢的光标主题。<br />
<br />
合法的 [[Plasma]] 鼠标光标主题有 {{ic|breeze_cursors}},{{ic|Breeze_Snow}} 和 {{ic|breeze-dark}}。<br />
<br />
==== 用户图标(头像) ====<br />
<br />
SDDM 对于每个用户从相应的 {{ic|~/.face.icon}} 目录下读取 PNG 图片格式的用户图标(即“头像”),或者从 SDDM 配置文件中由 {{ic|FacesDir}} 为所有用户定义的共有位置。配置设置可以通过修改 {{ic|/etc/sddm.conf}} 文件被直接替换,更好的方法是创建一个位于 {{ic|/etc/sddm.conf.d/}} 下的文件来修改,例如 {{ic|/etc/sddm.conf.d/avatar.conf}}。<br />
<br />
要使用 {{ic|FacesDir}} 选项来确定头像位置,即在配置文件中 {{ic|FacesDir}} 所确定的位置为每一个用户放置一个 PNG 图片,命名如 {{ic|''username''.face.icon}}。{{ic|FacesDir}} 默认的路径为 {{ic|/usr/share/sddm/faces/}}。你可以更改默认 {{ic|FacesDir}} 目录以合乎你的要求。下面是一个例子:<br />
<br />
{{hc|/etc/sddm.conf.d/avatar.conf|2=<br />
[Theme]<br />
FacesDir=/var/lib/AccountsService/icons/<br />
}}<br />
<br />
另一个选项是放置一个名为 {{ic|.face.icon}} 的 PNG 图片到你的家目录下。在这种情况下,您不用对任何 SDDM 配置文件进行更改。不过,您仍需确定 {{ic|sddm}} 用户可以读取这些 PNG 图片作为用户图标。<br />
<br />
{{注意|在许多 KDE 的版本中,用户图标图像文件是 {{ic|~/.face}} 而 {{ic|~/.face.icon}} 是链接到图像文件的符号链接。如果用户的图标是符号链接,你需要为目标文件设置恰当的文件权限。}} <br />
<br />
为了 [[Access Control Lists#Set ACL|设置合适权限]] 运行:<br />
<br />
$ setfacl -m u:sddm:x ~/<br />
$ setfacl -m u:sddm:r ~/.face.icon<br />
<br />
你可以通过运行下列命令 [[Access Control Lists#Show ACL|检查权限]]:<br />
<br />
$ getfacl ~/<br />
$ getfacl ~/.face.icon<br />
<br />
详见 [https://github.com/sddm/sddm#no-user-icon SDDM README: No User Icon]。<br />
<br />
=== 数字锁 ===<br />
<br />
如果你想强制启用数字锁,在 {{ic|[General]}} 小节设置 {{ic|1=Numlock=on}}。<br />
<br />
=== 旋转显示 ===<br />
<br />
详见 [[Xrandr#Configuration]]。<br />
<br />
=== DPI 设置 ===<br />
<br />
有时位于“显示管理器”级别设置正确的显示器 DPI 是很有用的。[https://github.com/sddm/sddm/blob/master/README.md#custom-dpi] 你需要在 {{ic|ServerArguments}} 字符串的末尾加上参数 {{ic|-dpi ''your_dpi''}} 例如:<br />
<br />
{{hc|head=/etc/sddm.conf.d/dpi.conf|output=<br />
[X11]<br />
ServerArguments=-nolisten tcp -dpi 94<br />
}}<br />
<br />
=== 启用 HiDPI ===<br />
<br />
创建 [[HiDPI (简体中文)|HiDPI]] 配置文件如下:<br />
<br />
{{hc|/etc/sddm.conf.d/hidpi.conf|2=<br />
[Wayland]<br />
EnableHiDPI=true<br />
<br />
[X11]<br />
EnableHiDPI=true<br />
}}<br />
<br />
=== 使用指纹识别器 ===<br />
<br />
{{注意|在改变设置前要确定你的指纹已经注册完成。指纹支持目前并不是完全工作正常,并且看起来在使用这种方法时仅使用密码登录将不再有效。}}<br />
<br />
SDDM 使用 [[fprint]] 以使用指纹识别。在安装了 fprint 和添加指纹签名后,在添加 {{ic|/etc/pam.d/sddm}} 的开始位置添加一行 {{ic|auth sufficient pam_fprintd.so}}。<br />
<br />
{{提示|要使其在 KDE 的锁屏模式下工作,将上面提到的一行同样添加于 {{ic|/etc/pam.d/kde}} 的开始位置。}}<br />
<br />
如果你现在在空密码区域按下回车,那么指纹识别器应该开始工作了。<br />
<br />
== 故障排除 ==<br />
<br />
=== 只有空白屏幕和光标,但没有欢迎界面 ===<br />
<br />
使用 {{ic|df -h}} 命令检查您的磁盘空间。如果没有足够的空间,欢迎界面会崩溃。<br />
<br />
如果磁盘空间足够,那么这个问题可能源于此 [https://github.com/sddm/sddm/issues/1179 bug]。切换 [[Getty#Installation|到另一个 TTY]] 来 [[restart|重启]] SDDM。<br />
<br />
=== SDDM 出现欢迎界面前的加载时间过长 ===<br />
<br />
内核熵池过小会造成长时间的 SDDM 加载过程([https://github.com/sddm/sddm/issues/1036 Bug report])。详见 [[Random number generation]] 扩大内核熵池的建议。<br />
<br />
=== 登录后挂起 ===<br />
<br />
尝试移除 {{ic|~/.Xauthority}} 文件后不重启再次登入。重启会再次创建该文件即该问题依旧存在。<br />
<br />
=== SDDM 在 tty1 启动而不是 tty7 ===<br />
<br />
SDDM 根据 [http://0pointer.de/blog/projects/serial-console.html systemd 的规定] 在 tty1 启动图形会话。如果您更喜欢老派的 tty1 到 tty6 皆预留为文本终端,更改 {{ic|MinimumVT}} 变量的默认值,其位于 {{ic|[X11]}} 小节下:<br />
<br />
{{hc|/etc/sddm.conf.d/tty.conf|2=<br />
[X11]<br />
MinimumVT=7<br />
}}<br />
<br />
=== 一个或多个用户没有出现在欢迎界面 ===<br />
<br />
{{警告|用户设置过低或过高的 {{ic|UID}} 范围应该大体上不会暴露给 [[Display manager (简体中文)]]。}}<br />
<br />
SDDM 默认会显示 UID 在 1000 到 65000 范围内的用户,如果想要显示的用户的 UID 小于这个范围,那么您就不得不更改这个范围。比如,对于 UID 为 501时,可以修改:<br />
<br />
{{hc|/etc/sddm.conf.d/uid.conf|2=<br />
[Users]<br />
HideShells=/sbin/nologin,/bin/false<br />
# Hidden users, this is if any system users fall within your range, see /etc/passwd on your system.<br />
HideUsers=git,sddm,systemd-journal-remote,systemd-journal-upload<br />
<br />
# Maximum user id for displayed users<br />
MaximumUid=65000<br />
<br />
# Minimum user id for displayed users<br />
MinimumUid=500 #My UID is 501<br />
}}<br />
<br />
=== SDDM 只加载 US 键盘布局 ===<br />
<br />
SDDM 加载的键盘布局被确定在 {{ic|/etc/X11/xorg.conf.d/00-keyboard.conf}} 文件中。您可以通过 {{ic|localectl set-x11-keymap}} 命令以生成此配置文件。详见 [[Keyboard configuration in Xorg]]。<br />
<br />
SDDM 可能也会错误地显示为 US 布局,但在您开始输入您的密码时立即切换到正确的键盘布局 [https://github.com/sddm/sddm/issues/202#issuecomment-76001543]。此 bug 看起来不是来自 SDDM,而是 {{Pkg|libxcb}} (version 1.13-1 as of 2018) [https://github.com/sddm/sddm/issues/202#issuecomment-133628462]。<br />
<br />
=== 屏幕分辨率过低 ===<br />
<br />
此问题可能源于显示屏 HiDPI 的使用破坏了 [[Wikipedia:Extended Display Identification Data|EDID]] [https://github.com/sddm/sddm/issues/692]。如果你 [[#启用 HiDPI|启动了 HiDPI]],尝试关掉它。<br />
<br />
如果上述方法失败了,您可以尝试在 Xorg 配置文件中设置您的显示尺寸:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/90-monitor.conf|2=<br />
Section "Monitor"<br />
Identifier "<default monitor>"<br />
DisplaySize 345 194 # in millimeters<br />
EndSection<br />
}}<br />
<br />
=== 自动挂载家目录的加载时间过长 ===<br />
<br />
SDDM 默认会访问 {{ic|~/.face.icon}} 文件以尝试显示用户头像。如果您的家目录采用自动挂载的文件系统(autofs),例如如果您使用 [[dm-crypt]],这将会使之等待 60 秒,直到自动挂载的文件系统(autofs)返回此目录不能被挂载。<br />
<br />
您可以通过编辑 {{ic|/etc/sddm.conf}} 文件以关闭头像功能:<br />
<br />
{{hc|/etc/sddm.conf|2=<br />
[Theme]<br />
EnableAvatars=false<br />
}}</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=ArchWiki:Translation_Team_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=592860
ArchWiki:Translation Team (简体中文)
2019-12-28T12:26:29Z
<p>C0n5t4ntK: /* 页面维护列表 */ 认领页面</p>
<hr />
<div>[[Category:简体中文]]<br />
[[Category:ArchWiki (简体中文)]]<br />
[[ar:ArchWiki Translation Team]]<br />
[[cs:ArchWiki Translation Team]]<br />
[[el:ArchWiki Translation Team]]<br />
[[en:ArchWiki:Translation Team]]<br />
[[es:ArchWiki:Translation Team]]<br />
[[fr:ArchWiki Translation Team]]<br />
[[hr:ArchWiki Translation Team]]<br />
[[it:ArchWiki Translation Team]]<br />
[[ja:ArchWiki 翻訳チーム]]<br />
[[ko:ArchWiki Translation Team]]<br />
[[nl:ArchWiki Translation Team]]<br />
[[pl:ArchWiki Translation Team]]<br />
[[pt:ArchWiki:Translation Team]]<br />
[[ru:ArchWiki Translation Team]]<br />
[[sk:ArchWiki Translation Team]]<br />
[[zh-hant:ArchWiki:Translation Team]]<br />
Arch Wiki 上有许多中文页面,这其中大部分是从外文翻译过来的,这些页面是无数中文志愿者劳动的结晶。随着时间推移,有些页面因为没有及时维护,内容严重过时。而目前的翻译工作缺少组织,效率偏低。所以参照西班牙和意大利翻译组的做法,添加这个页面。<br />
<br />
如果你希望对Arch Wiki做贡献,参与Wiki建设,比如翻译英文页面和对已翻译过的中文页面进行维护,只需要编辑下面的[[#页面维护列表]],添加相应的条目,并将自己加为相关页面的维护者。如果你在列表中还没有找到想要翻译的页面,可以自行添加。另外,如果因为时间原因无法再维护页面,请及时将自己从维护者列表中删除。<br />
<br />
== 创建翻译 ==<br />
{{警告|如果不准备翻译页面的大部分内容,请尽量不要新建简体中文页面。检查英文页面的更新需要花费不少精力,没有翻译的页面会增加维护负担。}}<br />
# 如果还不知道如何编辑 wiki,请阅读 [[Help:Editing (简体中文)|编辑帮助]]。<br />
# 阅读 [[Help:i18n (简体中文)|i18n帮助]],文章给出了 ArchWiki 国际化和本地化的指南。<br />
# [[Special:UserLogin|登录]] 以进行编辑。<br />
# 选择要翻译的页面,例如从 [[Special:Random|随机页面]] 或[[#页面维护列表|页面维护列表]] 中选择一个未翻译完成的页面。假设要翻译 [[Some Page]].<br />
# 进入选择的英文页面,点击页面顶部的 '''编辑'''。<br />
# 添加要翻译文件的语言间链接, 简体中文的话加入<nowiki>[[zh-hans:Some Page]]</nowiki>,其它语言参见[[Help:i18n#Interlanguage links]])。<br />
# 复制所有页面代码。<br />
# 保存页面 (新加了语言链接)<br />
# 访问页面左边新添加的语言链接,应该会进到 [[Some Page (简体中文)]] : {{ic|<nowiki>https://wiki.archlinux.org/index.php/Some_Page_(</nowiki>''简体中文'')}}<br />
# 因为页面不存在,点击 '''创建'''。<br />
# 将显示一个编辑器 - 粘贴复制的英文页面。<br />
# 将文章分类修改为本地化版本,例如将 {{ic|<nowiki>[[Category:Internationalization]]</nowiki>}} 修改为 {{ic|<nowiki>[[Category:Internationalization (简体中文)]]</nowiki>}},参阅[[Help:Category (简体中文)]].<br />
# 修改语言间链接,指向英文页面(将 {{ic|zh-hans}} 修改为 {{ic|en}},并将英文页面移到文章顶部。<br />
# 翻译页面,进行保存。<br />
# (推荐)给翻译完成的页面加上[[Template:TranslationStatus (简体中文)|翻译状态]],后有详细介绍。<br />
# 更新所有其它语言页面,加入刚翻译文章的语言间链接。<br />
# (可选)创建一个简体中文名称的页面,指向新创建的页面:访问 {{ic|<nowiki>https://wiki.archlinux.org/index.php/</nowiki>''页面的中文名称''}}.<br />
# (可选)建立新页面,并加入:{{bc|<nowiki>#REDIRECT [[Some Page (简体中文)</nowiki>]]}}<br />
<br />
== Templates ==<br />
<br />
{{Translateme (简体中文)|Not translated}}<br />
<br />
The following table lists the [[Help:Template (简体中文)|templates]] that should be translated and their Simplified Chinese equivalent.<br />
<br />
{| class=wikitable<br />
! English template || Simplified Chinese version<br />
|-<br />
! colspan=2| Article templates<br />
|-<br />
| [[Template:Related articles start]] || [[Template:Related articles start (简体中文)]]<br />
|-<br />
| [[Template:Yes]] || [[Template:是]]<br />
|-<br />
| [[Template:No]] || [[Template:否]]<br />
|-<br />
| [[Template:Tip]] || [[Template:提示]]<br />
|-<br />
| [[Template:Note]] || [[Template:注意]]<br />
|-<br />
| [[Template:Warning]] || [[Template:警告]]<br />
|-<br />
| [[Template:Dead link]] || [[Template:失效链接]]<br />
|-<br />
| [[Template:Broken package link]] || {{-}}<br />
|-<br />
! colspan=2| Translation status templates<br />
|-<br />
| [[Template:Bad translation]] || {{-}}<br />
|-<br />
| [[Template:Translateme]] || [[Template:Translateme (简体中文)]]<br />
|-<br />
| [[Template:TranslationStatus]] || [[Template:TranslationStatus (简体中文)]]<br />
|-<br />
! colspan=2| Special templates<br />
|-<br />
| [[Template:Cat main]] || {{-}}<br />
|-<br />
| [[Template:Template]] || {{-}}<br />
|}<br />
<br />
== 完善翻译 ==<br />
[https://wiki.archlinux.org/index.php?title=Special:WhatLinksHere/Template:Translateme_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&limit=100 这个页面] 包含了需要完善翻译的简体中文页面。完善翻译的基本步骤:<br />
# 选择自己比较熟悉的文章进行翻译<br />
# 先检查英文页面的对应段落,更新成最新的英文后再翻译,避免翻译过时的内容,减少信息遗漏。<br />
# 翻译完成后删除页面中的 <nowiki>{{translateme (简体中文)}}</nowiki> 标记<br />
# (推荐)给翻译完成的页面加上[[Template:TranslationStatus (简体中文)|翻译状态]],后有详细介绍。<br />
<br />
== 更新过期页面 == <br />
如果发现有 Wiki 页面过期或错误:<br />
* 小的改动,有时间可以立即进行修改同步,维护者并不控制页面的编辑权限,越多的人参与维护越好。如果改动较大,请先联系维护者,避免重复劳动。<br />
* 没有时间查看更改,请给页面加上 {{ic|<nowiki>{{out of date}}</nowiki>}} 模版,这样其他贡献者更容易发现需要更新的页面,而读者看到过期标记就可以直接查看英文页面,以免被错误内容误导,白白耽误时间。<br />
* 没有时间翻译,请将过期的中文部分删去,从英文页面中复制更改的部分到中文页面的相应部分,去掉{{ic|<nowiki>{{out of date}}</nowiki>}}模板(如果页面上有的话)并加上{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板,这样其他贡献者就更容易发现需要翻译的页面,而读者也不会被过期的内容误导。<br />
如果发现有页面未翻译:<br />
* 有时间的话,请将页面中的英文部分翻译为中文,并去掉{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板。<br />
* 没有时间翻译,请为页面添加{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板,这样其他的贡献者就能更容易发现需要翻译的页面。<br />
{{注意|在修改页面上的模板时,请同时更新页面维护列表的翻译状态。}}<br />
<br />
== 翻译任务 ==<br />
=== 模板 Article summary 变更为 Related ===<br />
因为 Summary 中的简介基本上和正文的介绍一样,所以页面左边的介绍栏进行了简化,只保留相关文章功能。英文页面正在进行大规模修改,相应的中文页面也需要同步更新。<br />
<br />
需要注意的地方:<br />
* 将第一行改成<br />
: <nowiki>{{Related articles start (简体中文)}}</nowiki><br />
* 如果英文的相关文章存在中文翻译,则替换为简体中文页面。示例:<br />
: <nowiki>{{Related2|Display Manager (简体中文)|显示管理器}}</nowiki><br />
* 示例:[https://wiki.archlinux.org/index.php?title=Start_X_at_Login&diff=0&oldid=270155 英文变更], [https://wiki.archlinux.org/index.php?title=Start_X_at_Login_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=285643&oldid=242662 对应的翻译]<br />
<br />
== 维护翻译 ==<br />
完成页面的翻译只是初步完成任务,及时同步英文页面改动、更新翻译是一个持续性的工作,可能会耗费更多的时间。<br />
<br />
=== 页面认领 ===<br />
所有人都可以认领页面。认领后的责任包括进行翻译,关注英文页面的改动,及时同步翻译。<br />
<br />
为了更好的跟踪英文页面的修改,请务必在设置中启用监视列表邮件通知,并监视对应的英文页面(从设置中找到监视列表,加入英文页面。或者直接到英文页面点击页面顶端的监视标签。这样只要有改动,就会收到邮件通知)。<br />
<br />
{{小贴士|如果收到邮件通知后没有访问页面或者访问了页面却没有登录用户,下次页面改动时就不会再发邮件通知。可以点击监视列表中的'''标记所有页面为已读'''再次获取更新。}}<br />
<br />
如果页面有维护者但长期得不到更新,将会在维护列表中删除维护者。<br />
<br />
=== 翻译状态模板 ===<br />
Arch 作为滚动发行版,软件变化比较快,对应的文档变化也比较快。许多翻译的文章由于缺乏更新,会产生命令运行出错或不起作用等问题。而由于这些过期页面没有及时标记出来,所以用户无法及时获得更新。[[Template:TranslationStatus (简体中文)|翻译状态模板]]就是为了解决这个问题而创建。<br />
<br />
此模板可以起到如下作用:<br />
* 为用户提供翻译状况,包括翻译时间、英文页面的最后版本等<br />
* 用户可以点击查看翻译后,英文页面的改动,这样英文不是很好的用户可以只查看很小一部分英文内容,并判断出是否影响操作。<br />
* 翻译人员可以跟踪页面状况,通过[[Special:WhatLinksHere/Template:TranslationStatus_(简体中文)|模板的反向链接]]可以查找到所有标记页面,查看需要更新翻译的部分。<br />
<br />
[[Template:TranslationStatus (简体中文)|模板页面]]有详细的使用方法。<br />
<br />
=== 页面维护列表 ===<br />
{{注意|请按照拉丁字母顺序添加页面。}}<br />
<br />
翻译状态说明:<br />
;过期:页面内容未与英文页面同步,对应{{ic|<nowiki>{{out of date}}</nowiki>}} 模版<br />
;未翻译:页面中含有英文内容,对应{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板<br />
;完成:页面已与英文页面同步<br />
<br />
{| class="wikitable sortable collapsible" border="1"<br />
|-<br />
! 页面<br />
! 翻译状态<br />
! 维护者<br />
! class="unsortable" width="30%" | 备注<br />
|-<br />
| [[acpid (简体中文)]]<br />
| 过期<br />
| Cael<br />
|<br />
|-<br />
| [[Advanced Linux Sound Architecture (简体中文)]]<br />
| 翻译中<br />
| ihonliu<br />
| 无<br />
|-<br />
| [[Arch based distributions (active) (简体中文)]]<br />
| 完成<br />
| Joshua<br />
| 勘误中<br />
|-<br />
| [[Amateur radio (简体中文)]]<br />
| 翻译中<br />
| liu-shuyuan<br />
| <br />
|-<br />
| [[AMD Catalyst (简体中文)]]<br />
| 过期<br />
| Shibao Zhao<br />
| 无<br />
|-<br />
| [[ATI (简体中文)]]<br />
| 完成<br />
| skysailing<br />
| 无<br />
|-<br />
| [[AUR helpers (简体中文)]]<br />
| 完成<br />
| Kurobac<br />
| 部分用词可能需要修改<br />
|-<br />
| [[awesome (简体中文)]]<br />
| 进行中<br />
| Cael<br />
| 无<br />
|-<br />
| [[BIND (简体中文)]]<br />
| 完成<br />
| Dargasia<br />
|<br />
|-<br />
| [[Bumblebee (简体中文)]]<br />
| 完成<br />
| Peter<br />
| 无<br />
|-<br />
| [[Chromium (简体中文)]]<br />
| 完成<br />
| Bobby<br />
| 无<br />
|-<br />
| [[Ceph (简体中文)]]<br />
| 翻译中<br />
| Aaron Chen<br />
| 部分未翻译 <br />
|-<br />
| [[Cinnamon (简体中文)]]<br />
| 部分翻译 <br />
| Bobby<br />
| 部分未翻译 <br />
|- <br />
| [[Common Applications (简体中文)]]<br />
| 部分翻译 <br />
| DavidChen<br />
| 翻译中<br />
|-<br />
| [[Common Applications/Science (简体中文)]]<br />
| drop maintain<br />
| 更新,翻译中<br />
|<br />
|-<br />
| [[Compiz (简体中文)]]<br />
| 翻译中<br />
| xiii_1991<br />
| 20140813开始<br />
|-<br />
| [[Conky (简体中文)]]<br />
| 完成<br />
| upi<br />
| 无<br />
|-<br />
| [[Core utilities (简体中文)]]<br />
| 完成<br />
| rentaro, Arisaka<br />
| 无<br />
|-<br />
|-<br />
| [[Clover (简体中文)]]<br />
| 完成<br />
| Yume Kankawa<br />
| 无<br />
|-<br />
| [[Disk cloning (简体中文)]]<br />
| 翻译中<br />
| _spaike97<br />
| 无<br />
|-<br />
| [[Dynamic Kernel Module Support (简体中文)]]<br />
| 完成<br />
| Mithrandir<br />
| 完善中<br />
|-<br />
| [[Emacs (简体中文)]]<br />
| 翻译中<br />
| Jaurung yuanhang<br />
| 未完成<br />
|-<br />
| [[File recovery (简体中文)]]<br />
| 翻译中<br />
| _spaike97<br />
| 无<br />
|-<br />
| [[Fish (简体中文)]]<br />
| 完成<br />
| liu-shuyuan<br />
|<br />
|-<br />
| [[Flatpak (简体中文)]]<br />
| 翻译中<br />
| C0n5t4ntK<br />
| <br />
|-<br />
| [[Font configuration (简体中文)]]<br />
| 翻译中<br />
| Jaurung<br />
| 完善中<br />
|-<br />
| [[Fonts (简体中文)]]<br />
| 翻译中<br />
| qqbzg<br />
| 无<br />
|-<br />
| [[GDM (简体中文)]]<br />
| 翻译中<br />
| Junjie Yuan<br />
| 绝大多数内容未翻译,重新进行翻译<br />
|-<br />
| [[GNOME (简体中文)]]<br />
| 完成<br />
| skywet<br />
| <br />
|-<br />
| [[GRUB (简体中文)]]<br />
| 完成<br />
| Armodeniz<br />
| <br />
|-<br />
| [[GRUB/Tips and tricks (简体中文)]]<br />
| 完成<br />
| Armodeniz<br />
| <br />
|-<br />
| [[Java (简体中文)]]<br />
| 翻译中<br />
| CaCaCarrot<br />
| 无<br />
|-<br />
| [[KDE (简体中文)]]<br />
| 过期<br />
| <br />
| <br />
|-<br />
| [[LAMP (简体中文)]]<br />
| 完成<br />
| Liuzhengyi<br />
| 勘误中<br />
|-<br />
| [[LibreOffice (简体中文)]]<br />
| 完成<br />
| qqbzg<br />
| 勘误中<br />
|-<br />
| [[Libvirt (简体中文)]]<br />
| 完成<br />
| Kurobac<br />
| 需要格式改进<br />
|-<br />
| [[Local Mirror (简体中文)]]<br />
| 完成<br />
| Jason Zhang<br />
| 完善中<br />
|- <br />
| [[MATLAB (简体中文)]]<br />
| 部分翻译 <br />
| Liu Qinyang<br />
|<br />
|-<br />
| [[Minecraft (简体中文)]]<br />
| 完成 <br />
| Xavier Lau<br />
| 页面已经与英文版同步,长期维护中<br />
|-<br />
| [[NetworkManager (简体中文)]]<br />
| 翻译中 <br />
| Jack-lijing, leeking <br />
| 请优先翻译<br />
|-<br />
| [[Network Time Protocol daemon (简体中文)]]<br />
| 完成<br />
| sid<br />
| 完善中<br />
|-<br />
| [[OpenOffice (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Opera (简体中文)]]<br />
| 未翻译<br />
| Bobby<br />
| 请优先翻译此文 <br />
|-<br />
| [[Pacman GUI Frontends (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Pidgin (简体中文)]]<br />
| 进行中<br />
| Cael<br />
| 无 <br />
|-<br />
| [[Python打包指引 (简体中文)]]<br />
| 翻译中<br />
| SherlockHolo<br />
| 无<br />
|- <br />
| [[ranger (简体中文)]]<br />
| 完成<br />
| Jason Zhang<br />
| 完善中<br />
|-<br />
| [[Raspberry Pi (简体中文)]]<br />
| 翻译中<br />
| Mithrandir<br />
| <br />
|-<br />
| [[Reporting bug guidelines (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[SDDM (简体中文)]]<br />
| 完成<br />
| C0n5t4ntK<br />
| 长期维护中<br />
|-<br />
| [[Secure Shell (简体中文)]]<br />
| 完成<br />
| Arisaka<br />
| 无<br />
|-<br />
| [[Smart Common Input Method platform (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Steam (简体中文)]]<br />
| 完成<br />
| C0n5t4ntK<br />
| 长期维护中<br />
|-<br />
| [[Systemd-timesyncd (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[TLP (简体中文)]]<br />
| 完成<br />
| Skywet<br />
| 持续更新中 <br />
|-<br />
| [[Tomcat (简体中文)]]<br />
| 完成<br />
| Starwing117<br />
| 持续更新中 <br />
|-<br />
| [[Vim (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[VirtualBox (简体中文)]]<br />
| 翻译至 2017-10-15<br />
| [[User:5long]]<br />
|<br />
|-<br />
| [[VMware (简体中文)]]<br />
| 完成<br />
| ThomasWFan<br />
| 页面已经与英文版同步,长期维护中<br />
|- <br />
| [[Xfce (简体中文)]]<br />
| 完成 <br />
| 无<br />
| 无<br />
|-<br />
| [[Xmonad (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Xrandr (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=Flatpak_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=592859
Flatpak (简体中文)
2019-12-28T12:24:14Z
<p>C0n5t4ntK: 创建 Flatpak 简体中文页面,英文版内容移植完成。</p>
<hr />
<div>[[Category:Development (简体中文)]]<br />
[[en:Flatpak]]<br />
[[es:Flatpak]]<br />
[[ja:Flatpak]]<br />
[[pt:Flatpak]]<br />
{{Related articles start}}<br />
{{Related|Snapd}}<br />
{{Related|bubblewrap}}<br />
{{Related articles end}}<br />
From the project [https://github.com/flatpak/flatpak/blob/master/README.md README]: "''[http://flatpak.org Flatpak] is a system for building, distributing and running sandboxed desktop applications on Linux.''"<br />
<br />
From {{man|1|flatpak}}:<br />
<br />
:''Flatpak is a tool for managing applications and the runtimes they use. In the Flatpak model, applications can be built and distributed independently from the host system they are used on, and they are isolated from the host system ('sandboxed') to some degree, at runtime.''<br />
:''Flatpak uses [https://ostree.readthedocs.io/en/latest/ OSTree] to distribute and deploy data. The repositories it uses are OSTree repositories and can be manipulated with the ostree utility. Installed runtimes and applications are OSTree checkouts.''<br />
<br />
== Installation ==<br />
<br />
[[Install]] the {{pkg|flatpak}} package.<br />
<br />
{{Note|If you want to build flatpaks with {{ic|flatpak-builder}} you will need to install the optional dependencies of {{pkg|elfutils}} and {{pkg|patch}}.}}<br />
<br />
== Managing repositories ==<br />
<br />
=== Add a repository ===<br />
<br />
To add a remote flatpak repository do:<br />
<br />
$ flatpak remote-add ''name'' ''location''<br />
<br />
where ''name'' is the name for the new remote, and ''location'' is the path or URL for the repository.<br />
<br />
For example to add the official [https://flathub.org/ Flathub repository]:<br />
<br />
$ flatpak remote-add --if-not-exists flathub <nowiki>https://dl.flathub.org/repo/flathub.flatpakrepo</nowiki><br />
<br />
=== Delete a repository ===<br />
<br />
To delete a remote flatpak repository do:<br />
<br />
$ flatpak remote-delete ''name''<br />
<br />
where ''name'' is the name of the remote repository to be deleted.<br />
<br />
=== List repositories ===<br />
<br />
To list all the added repositories do:<br />
<br />
$ flatpak remotes<br />
<br />
== Managing runtimes and applications ==<br />
<br />
=== Search for a remote runtime or application ===<br />
<br />
Before being able to search for a runtime or application in a newly added remote repository, we need to retrieve the appstream data for it:<br />
<br />
{{hc|$ flatpak update|<br />
Looking for updates...<br />
Updating appstream data for remote ''name''<br />
}}<br />
<br />
Then we can proceed to search for a package with {{ic|flatpak search ''packagename''}}, ''e.g.'' to look for the package {{ic|libreoffice}} with the {{ic|flathub}} remote configured:<br />
<br />
{{hc|$ flatpak search libreoffice|<br />
Application ID Version Branch Remotes Description <br />
org.libreoffice.LibreOffice stable flathub The LibreOffice productivity suite<br />
}}<br />
<br />
=== List all available runtimes and applications ===<br />
<br />
To list all available runtimes and applications in a remote repository named ''remote'' do:<br />
<br />
$ flatpak remote-ls ''remote''<br />
<br />
=== Install a runtime or application ===<br />
<br />
To install a runtime or application do:<br />
<br />
$ flatpak install ''remote'' ''name''<br />
<br />
where ''remote'' is the name of the remote repository, and ''name'' is the name of the application or runtime to install.<br />
<br />
{{Tip|You can use partial identifiers {{ic|flatpak install ''partial-name''}} (for example {{ic|flatpak install libreoffice}}).}}<br />
<br />
=== List installed runtimes and applications ===<br />
<br />
To list installed runtimes and applications do:<br />
<br />
$ flatpak list<br />
<br />
=== Run applications ===<br />
<br />
Flatpak applications can also be run from the command line:<br />
<br />
$ flatpak run ''name''<br />
<br />
=== Update a runtime or application ===<br />
<br />
To update a runtime or application named ''name'' do:<br />
<br />
$ flatpak update ''name''<br />
<br />
=== Uninstall a runtime or application ===<br />
<br />
To uninstall a runtime or application named ''name'' do:<br />
<br />
$ flatpak uninstall ''name''<br />
<br />
{{Tip|You can uninstall unused flatpak "refs" (aka orphans with no application/runtime) with {{ic|flatpak uninstall --unused}}.}}<br />
<br />
=== Adding Flatpak .desktop files to your menu ===<br />
Flatpak expects window managers to respect the XDG_DATA_DIRS environment variable to discover applications. This may require restarting the session or the launcher may not support this. In such a case where you can edit the list of directories scanned, add these to it:<br />
<br />
~/.local/share/flatpak/exports/share/applications<br />
/var/lib/flatpak/exports/share/applications<br />
<br />
This is known to be necessary in Awesome.<br />
<br />
=== Viewing sandbox permissions of application ===<br />
Flatpak applications come with predefined sandbox rules which defines the resources and file system paths the application is allowed to access.<br />
To view the specific application permissions do:<br />
$ flatpak info --show-permissions ''name''<br />
The reference of the sandbox permission names can be found on [https://docs.flatpak.org/en/latest/sandbox-permissions-reference.html official flatpak documentation].<br />
<br />
=== Overriding sandbox permissions of applications ===<br />
If you find the predefined permissions of the application too lax or too restrictive you can change to anything you want using {{ic|flatpak override}} command.<br />
For example:<br />
flatpak override --nofilesystem=home ''name''<br />
This will prevent the application access to your home folder.<br />
<br />
Every type of permission such as device, filesystem or socket has an command line option that allows that particular permission and a separated option that denies. For example, in case of device access {{ic|1=--device=''device_name''}} allows access, {{ic|1=--nodevice=''device_name''}} denies the permission to access device.<br />
<br />
For all permission types commands consult the manual page: {{man|1|flatpak-override}}<br />
<br />
Permission overrides can be reset to defaults with command:<br />
$ flatpak override --reset ''name''<br />
<br />
== Creating a custom base runtime ==<br />
<br />
{{Expansion|This can certainly be improved. It also has problems with D-Bus for GNOME apps.}}<br />
<br />
{{Warning|If you want to release your software to the public as a Flatpak, an Arch-based runtime is unsuitable. In this case, you will want to follow [http://docs.flatpak.org official documentation] to integrate your software into the proper Flatpak ecosystem using the [http://flatpak.org/runtimes.html common runtimes].}}<br />
<br />
{{Note|You may want to use an untrusted, unprivileged user account for bundling untrusted software because the software is not sandboxed during app and runtime creation.}}<br />
<br />
{{Note|When distributing bundles to others, you may be legally obliged to provide the source code of some of the bundled software upon request. You may want to use [[ABS]] to build these packages from source.}}<br />
<br />
You can create a custom Arch-based base runtime and base SDK for Flatpak using pacman. You can then use it for building and packaging applications. This is an alternative for personal use to the default {{ic|org.freedesktop.BasePlatform}} and {{ic|org.freedesktop.BaseSdk}} runtimes.<br />
<br />
In addition to {{Pkg|flatpak}}, you need to have installed {{Pkg|fakeroot}} and for pacman hooks support also {{Pkg|fakechroot}}.<br />
<br />
First, start by creating a directory for building the runtime and possibly applications.<br />
<br />
$ mkdir ''myflatpakbuilddir''<br />
$ cd ''myflatpakbuilddir''<br />
<br />
You can then prepare a directory for building the runtime base platform. The files subdirectory will contain what will later be the {{ic|/usr}} directory in the sandbox. Therefore you will need to create symbolic links so the default {{ic|/usr/share}} etc. from Arch can still be accessed at the usual path.<br />
<br />
$ mkdir -p ''myruntime''/files/var/lib/pacman<br />
$ touch ''myruntime''/files/.ref<br />
$ ln -s /usr/usr/share ''myruntime''/files/share<br />
$ ln -s /usr/usr/include ''myruntime''/files/include<br />
$ ln -s /usr/usr/local ''myruntime''/files/local<br />
<br />
Make your host OS fonts available to the Arch runtime:<br />
<br />
$ mkdir -p ''myruntime''/files/usr/share/fonts<br />
$ ln -s /run/host/fonts ''myruntime''/files/usr/share/fonts/flatpakhostfonts<br />
<br />
You need and may want to adapt your {{ic|pacman.conf}} before installing packages to the runtime. Copy {{ic|/etc/pacman.conf}} to your build directory and then make the following changes:<br />
<br />
* Remove the {{ic|CheckSpace}} option so pacman will not complain about errors finding the root filesystem for checking disk space.<br />
* Remove any undesired custom repositories and {{ic|IgnorePkg}}, {{ic|IgnoreGroup}}, {{ic|NoUpgrade}} and {{ic|NoExtract}} settings that are needed only for the host system.<br />
<br />
Now install the packages for the runtime.<br />
<br />
$ fakechroot fakeroot pacman -Syu --root ''myruntime''/files --dbpath ''myruntime''/files/var/lib/pacman --config pacman.conf base<br />
$ mv pacman.conf ''myruntime''/files/etc/pacman.conf<br />
<br />
Set up the [[Locale|locales]] to be used by editing {{ic|''myruntime''/files/etc/locale.gen}}. Then regenerate the runtime’s locales.<br />
<br />
$ fakechroot chroot ''myruntime''/files locale-gen<br />
<br />
The base SDK can be created from the base runtime with added applications needed for building packages and running pacman.<br />
<br />
$ cp -r ''myruntime'' mysdk<br />
$ fakechroot fakeroot pacman -S --root mysdk/files --dbpath mysdk/files/var/lib/pacman --config mysdk/files/etc/pacman.conf base-devel fakeroot fakechroot --needed<br />
<br />
Insert metadata about runtime and SDK.<br />
<br />
{{hc|''myruntime''/metadata|2=<br />
[Runtime]<br />
name=org.mydomain.BasePlatform<br />
runtime=org.mydomain.BasePlatform/x86_64/2016-06-26<br />
sdk=org.mydomain.BaseSdk/x86_64/2016-06-26<br />
}}<br />
<br />
{{hc|mysdk/metadata|2=<br />
[Runtime]<br />
name=org.mydomain.BaseSdk<br />
runtime=org.mydomain.BasePlatform/x86_64/2016-06-26<br />
sdk=org.mydomain.BaseSdk/x86_64/2016-06-26<br />
}}<br />
<br />
Add base runtime and SDK to a local repository in the current directory. You may want to give them appropriate commit messages such as “My Arch base runtime” and “My Arch base SDK”.<br />
<br />
$ ostree init --mode archive-z2 --repo=.<br />
$ EDITOR="nano -w" ostree commit -b runtime/org.mydomain.BasePlatform/x86_64/2016-06-26 --tree=dir=''myruntime''<br />
$ EDITOR="nano -w" ostree commit -b runtime/org.mydomain.BaseSdk/x86_64/2016-06-26 --tree=dir=mysdk<br />
$ ostree summary -u<br />
<br />
Install the runtime and SDK.<br />
<br />
$ flatpak remote-add --user --no-gpg-verify myarchos file://$(pwd)<br />
$ flatpak install --user myarchos org.mydomain.BasePlatform 2016-06-26<br />
$ flatpak install --user myarchos org.mydomain.BaseSdk 2016-06-26<br />
<br />
=== Creating apps with pacman ===<br />
<br />
As an alternative to building applications [http://flatpak.org/developer.html the usual way], we can use pacman to create a containerized version of the regular Arch packages. Note that {{ic|/usr}} is read-only when creating apps, so we can not use Arch’s packages when building an app. To create a real app with pacman, we can either<br />
<br />
* use pacman to create a runtime containing all dependencies<br />
* and compile the app ourselves [http://flatpak.org/developer.html as usual] or perhaps using pacman with a custom [[PKGBUILD]] tailored to Flatpak which uses {{ic|1=--prefix=/app}} for the {{ic|configure}} script,<br />
<br />
or we can<br />
* use pacman to create a runtime containing the app installed with pacman<br />
* and create a dummy app to launch it.<br />
<br />
For doing the latter, first create a runtime using pacman such as this one for {{Pkg|gedit}}. The runtime is first initialized and prepared for use with pacman.<br />
<br />
$ flatpak build-init -w geditruntime org.mydomain.geditruntime org.mydomain.BaseSdk org.mydomain.BasePlatform 2016-06-26<br />
$ flatpak build geditruntime sed -i "s/^#Server/Server/g" /etc/pacman.d/mirrorlist<br />
$ flatpak build geditruntime ln -s /usr/var/lib /var/lib<br />
$ flatpak build geditruntime fakeroot pacman-key --init<br />
$ flatpak build geditruntime fakeroot pacman-key --populate archlinux<br />
<br />
Then the package is installed. The host’s network connection must be made available to pacman.<br />
<br />
$ flatpak build --share=network geditruntime fakechroot fakeroot pacman --root /usr -S gedit<br />
<br />
You can test the installation before finishing the runtime (without proper sandboxing).<br />
<br />
$ flatpak build --socket=x11 geditruntime gedit<br />
<br />
Now finish building the runtime and export it to a new local repository. pacman’s GnuPG keys have permissions that may interfere and need to be removed first.<br />
<br />
$ flatpak build geditruntime rm -r /etc/pacman.d/gnupg<br />
$ flatpak build-finish geditruntime<br />
$ sed -i "s/\[Application\]/\[Runtime\]/;s/runtime=org.mydomain.BasePlatform/runtime=org.mydomain.geditruntime/" geditruntime/metadata<br />
$ flatpak build-export -r geditrepo geditruntime<br />
<br />
Then create a dummy app.<br />
<br />
$ flatpak build-init geditapp org.gnome.gedit org.mydomain.BaseSdk org.mydomain.geditruntime<br />
<br />
Now finish the dummy app. You can fine-tune the app’s access permissions when sandboxed by giving additional options when finishing the build. For possible options see the [[#See also|Flatpak documentation]] and the [https://gitlab.gnome.org/GNOME/gnome-apps-nightly/tree/master GNOME manifest files]. Alternatively, adapt {{ic|geditapp/metadata}} to your needs after finishing the build but before exporting. When the metadata file is complete, export the app to the repository.<br />
<br />
$ flatpak build-finish geditapp --socket=x11 ''[possibly other options]'' --command=gedit<br />
$ flatpak build-export geditrepo geditapp<br />
<br />
Install it along with the runtime.<br />
<br />
$ flatpak --user remote-add --no-gpg-verify geditrepo geditrepo<br />
$ flatpak install --user geditrepo org.mydomain.geditruntime<br />
$ flatpak install --user geditrepo org.gnome.gedit<br />
$ flatpak run org.gnome.gedit<br />
<br />
== See also ==<br />
<br />
* [http://flatpak.org Official website]<br />
* [https://github.com/flatpak/flatpak/wiki Official Github wiki]<br />
* [[Wikipedia::Flatpak|Wikipedia page]]<br />
* [https://wiki.gnome.org/Projects/SandboxedApps Gnome SandboxedApps]<br />
* [https://community.kde.org/Guidelines_and_HOWTOs/Flatpak KDE Testing Runtime and Applications]</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=Flatpak&diff=592857
Flatpak
2019-12-28T12:15:16Z
<p>C0n5t4ntK: Add zh-hans link</p>
<hr />
<div>[[Category:Development]]<br />
[[es:Flatpak]]<br />
[[ja:Flatpak]]<br />
[[pt:Flatpak]]<br />
[[zh-hans:Flatpak]]<br />
{{Related articles start}}<br />
{{Related|Snapd}}<br />
{{Related|bubblewrap}}<br />
{{Related articles end}}<br />
From the project [https://github.com/flatpak/flatpak/blob/master/README.md README]: "''[http://flatpak.org Flatpak] is a system for building, distributing and running sandboxed desktop applications on Linux.''"<br />
<br />
From {{man|1|flatpak}}:<br />
<br />
:''Flatpak is a tool for managing applications and the runtimes they use. In the Flatpak model, applications can be built and distributed independently from the host system they are used on, and they are isolated from the host system ('sandboxed') to some degree, at runtime.''<br />
:''Flatpak uses [https://ostree.readthedocs.io/en/latest/ OSTree] to distribute and deploy data. The repositories it uses are OSTree repositories and can be manipulated with the ostree utility. Installed runtimes and applications are OSTree checkouts.''<br />
<br />
== Installation ==<br />
<br />
[[Install]] the {{pkg|flatpak}} package.<br />
<br />
{{Note|If you want to build flatpaks with {{ic|flatpak-builder}} you will need to install the optional dependencies of {{pkg|elfutils}} and {{pkg|patch}}.}}<br />
<br />
== Managing repositories ==<br />
<br />
=== Add a repository ===<br />
<br />
To add a remote flatpak repository do:<br />
<br />
$ flatpak remote-add ''name'' ''location''<br />
<br />
where ''name'' is the name for the new remote, and ''location'' is the path or URL for the repository.<br />
<br />
For example to add the official [https://flathub.org/ Flathub repository]:<br />
<br />
$ flatpak remote-add --if-not-exists flathub <nowiki>https://dl.flathub.org/repo/flathub.flatpakrepo</nowiki><br />
<br />
=== Delete a repository ===<br />
<br />
To delete a remote flatpak repository do:<br />
<br />
$ flatpak remote-delete ''name''<br />
<br />
where ''name'' is the name of the remote repository to be deleted.<br />
<br />
=== List repositories ===<br />
<br />
To list all the added repositories do:<br />
<br />
$ flatpak remotes<br />
<br />
== Managing runtimes and applications ==<br />
<br />
=== Search for a remote runtime or application ===<br />
<br />
Before being able to search for a runtime or application in a newly added remote repository, we need to retrieve the appstream data for it:<br />
<br />
{{hc|$ flatpak update|<br />
Looking for updates...<br />
Updating appstream data for remote ''name''<br />
}}<br />
<br />
Then we can proceed to search for a package with {{ic|flatpak search ''packagename''}}, ''e.g.'' to look for the package {{ic|libreoffice}} with the {{ic|flathub}} remote configured:<br />
<br />
{{hc|$ flatpak search libreoffice|<br />
Application ID Version Branch Remotes Description <br />
org.libreoffice.LibreOffice stable flathub The LibreOffice productivity suite<br />
}}<br />
<br />
=== List all available runtimes and applications ===<br />
<br />
To list all available runtimes and applications in a remote repository named ''remote'' do:<br />
<br />
$ flatpak remote-ls ''remote''<br />
<br />
=== Install a runtime or application ===<br />
<br />
To install a runtime or application do:<br />
<br />
$ flatpak install ''remote'' ''name''<br />
<br />
where ''remote'' is the name of the remote repository, and ''name'' is the name of the application or runtime to install.<br />
<br />
{{Tip|You can use partial identifiers {{ic|flatpak install ''partial-name''}} (for example {{ic|flatpak install libreoffice}}).}}<br />
<br />
=== List installed runtimes and applications ===<br />
<br />
To list installed runtimes and applications do:<br />
<br />
$ flatpak list<br />
<br />
=== Run applications ===<br />
<br />
Flatpak applications can also be run from the command line:<br />
<br />
$ flatpak run ''name''<br />
<br />
=== Update a runtime or application ===<br />
<br />
To update a runtime or application named ''name'' do:<br />
<br />
$ flatpak update ''name''<br />
<br />
=== Uninstall a runtime or application ===<br />
<br />
To uninstall a runtime or application named ''name'' do:<br />
<br />
$ flatpak uninstall ''name''<br />
<br />
{{Tip|You can uninstall unused flatpak "refs" (aka orphans with no application/runtime) with {{ic|flatpak uninstall --unused}}.}}<br />
<br />
=== Adding Flatpak .desktop files to your menu ===<br />
Flatpak expects window managers to respect the XDG_DATA_DIRS environment variable to discover applications. This may require restarting the session or the launcher may not support this. In such a case where you can edit the list of directories scanned, add these to it:<br />
<br />
~/.local/share/flatpak/exports/share/applications<br />
/var/lib/flatpak/exports/share/applications<br />
<br />
This is known to be necessary in Awesome.<br />
<br />
=== Viewing sandbox permissions of application ===<br />
Flatpak applications come with predefined sandbox rules which defines the resources and file system paths the application is allowed to access.<br />
To view the specific application permissions do:<br />
$ flatpak info --show-permissions ''name''<br />
The reference of the sandbox permission names can be found on [https://docs.flatpak.org/en/latest/sandbox-permissions-reference.html official flatpak documentation].<br />
<br />
=== Overriding sandbox permissions of applications ===<br />
If you find the predefined permissions of the application too lax or too restrictive you can change to anything you want using {{ic|flatpak override}} command.<br />
For example:<br />
flatpak override --nofilesystem=home ''name''<br />
This will prevent the application access to your home folder.<br />
<br />
Every type of permission such as device, filesystem or socket has an command line option that allows that particular permission and a separated option that denies. For example, in case of device access {{ic|1=--device=''device_name''}} allows access, {{ic|1=--nodevice=''device_name''}} denies the permission to access device.<br />
<br />
For all permission types commands consult the manual page: {{man|1|flatpak-override}}<br />
<br />
Permission overrides can be reset to defaults with command:<br />
$ flatpak override --reset ''name''<br />
<br />
== Creating a custom base runtime ==<br />
<br />
{{Expansion|This can certainly be improved. It also has problems with D-Bus for GNOME apps.}}<br />
<br />
{{Warning|If you want to release your software to the public as a Flatpak, an Arch-based runtime is unsuitable. In this case, you will want to follow [http://docs.flatpak.org official documentation] to integrate your software into the proper Flatpak ecosystem using the [http://flatpak.org/runtimes.html common runtimes].}}<br />
<br />
{{Note|You may want to use an untrusted, unprivileged user account for bundling untrusted software because the software is not sandboxed during app and runtime creation.}}<br />
<br />
{{Note|When distributing bundles to others, you may be legally obliged to provide the source code of some of the bundled software upon request. You may want to use [[ABS]] to build these packages from source.}}<br />
<br />
You can create a custom Arch-based base runtime and base SDK for Flatpak using pacman. You can then use it for building and packaging applications. This is an alternative for personal use to the default {{ic|org.freedesktop.BasePlatform}} and {{ic|org.freedesktop.BaseSdk}} runtimes.<br />
<br />
In addition to {{Pkg|flatpak}}, you need to have installed {{Pkg|fakeroot}} and for pacman hooks support also {{Pkg|fakechroot}}.<br />
<br />
First, start by creating a directory for building the runtime and possibly applications.<br />
<br />
$ mkdir ''myflatpakbuilddir''<br />
$ cd ''myflatpakbuilddir''<br />
<br />
You can then prepare a directory for building the runtime base platform. The files subdirectory will contain what will later be the {{ic|/usr}} directory in the sandbox. Therefore you will need to create symbolic links so the default {{ic|/usr/share}} etc. from Arch can still be accessed at the usual path.<br />
<br />
$ mkdir -p ''myruntime''/files/var/lib/pacman<br />
$ touch ''myruntime''/files/.ref<br />
$ ln -s /usr/usr/share ''myruntime''/files/share<br />
$ ln -s /usr/usr/include ''myruntime''/files/include<br />
$ ln -s /usr/usr/local ''myruntime''/files/local<br />
<br />
Make your host OS fonts available to the Arch runtime:<br />
<br />
$ mkdir -p ''myruntime''/files/usr/share/fonts<br />
$ ln -s /run/host/fonts ''myruntime''/files/usr/share/fonts/flatpakhostfonts<br />
<br />
You need and may want to adapt your {{ic|pacman.conf}} before installing packages to the runtime. Copy {{ic|/etc/pacman.conf}} to your build directory and then make the following changes:<br />
<br />
* Remove the {{ic|CheckSpace}} option so pacman will not complain about errors finding the root filesystem for checking disk space.<br />
* Remove any undesired custom repositories and {{ic|IgnorePkg}}, {{ic|IgnoreGroup}}, {{ic|NoUpgrade}} and {{ic|NoExtract}} settings that are needed only for the host system.<br />
<br />
Now install the packages for the runtime.<br />
<br />
$ fakechroot fakeroot pacman -Syu --root ''myruntime''/files --dbpath ''myruntime''/files/var/lib/pacman --config pacman.conf base<br />
$ mv pacman.conf ''myruntime''/files/etc/pacman.conf<br />
<br />
Set up the [[Locale|locales]] to be used by editing {{ic|''myruntime''/files/etc/locale.gen}}. Then regenerate the runtime’s locales.<br />
<br />
$ fakechroot chroot ''myruntime''/files locale-gen<br />
<br />
The base SDK can be created from the base runtime with added applications needed for building packages and running pacman.<br />
<br />
$ cp -r ''myruntime'' mysdk<br />
$ fakechroot fakeroot pacman -S --root mysdk/files --dbpath mysdk/files/var/lib/pacman --config mysdk/files/etc/pacman.conf base-devel fakeroot fakechroot --needed<br />
<br />
Insert metadata about runtime and SDK.<br />
<br />
{{hc|''myruntime''/metadata|2=<br />
[Runtime]<br />
name=org.mydomain.BasePlatform<br />
runtime=org.mydomain.BasePlatform/x86_64/2016-06-26<br />
sdk=org.mydomain.BaseSdk/x86_64/2016-06-26<br />
}}<br />
<br />
{{hc|mysdk/metadata|2=<br />
[Runtime]<br />
name=org.mydomain.BaseSdk<br />
runtime=org.mydomain.BasePlatform/x86_64/2016-06-26<br />
sdk=org.mydomain.BaseSdk/x86_64/2016-06-26<br />
}}<br />
<br />
Add base runtime and SDK to a local repository in the current directory. You may want to give them appropriate commit messages such as “My Arch base runtime” and “My Arch base SDK”.<br />
<br />
$ ostree init --mode archive-z2 --repo=.<br />
$ EDITOR="nano -w" ostree commit -b runtime/org.mydomain.BasePlatform/x86_64/2016-06-26 --tree=dir=''myruntime''<br />
$ EDITOR="nano -w" ostree commit -b runtime/org.mydomain.BaseSdk/x86_64/2016-06-26 --tree=dir=mysdk<br />
$ ostree summary -u<br />
<br />
Install the runtime and SDK.<br />
<br />
$ flatpak remote-add --user --no-gpg-verify myarchos file://$(pwd)<br />
$ flatpak install --user myarchos org.mydomain.BasePlatform 2016-06-26<br />
$ flatpak install --user myarchos org.mydomain.BaseSdk 2016-06-26<br />
<br />
=== Creating apps with pacman ===<br />
<br />
As an alternative to building applications [http://flatpak.org/developer.html the usual way], we can use pacman to create a containerized version of the regular Arch packages. Note that {{ic|/usr}} is read-only when creating apps, so we can not use Arch’s packages when building an app. To create a real app with pacman, we can either<br />
<br />
* use pacman to create a runtime containing all dependencies<br />
* and compile the app ourselves [http://flatpak.org/developer.html as usual] or perhaps using pacman with a custom [[PKGBUILD]] tailored to Flatpak which uses {{ic|1=--prefix=/app}} for the {{ic|configure}} script,<br />
<br />
or we can<br />
* use pacman to create a runtime containing the app installed with pacman<br />
* and create a dummy app to launch it.<br />
<br />
For doing the latter, first create a runtime using pacman such as this one for {{Pkg|gedit}}. The runtime is first initialized and prepared for use with pacman.<br />
<br />
$ flatpak build-init -w geditruntime org.mydomain.geditruntime org.mydomain.BaseSdk org.mydomain.BasePlatform 2016-06-26<br />
$ flatpak build geditruntime sed -i "s/^#Server/Server/g" /etc/pacman.d/mirrorlist<br />
$ flatpak build geditruntime ln -s /usr/var/lib /var/lib<br />
$ flatpak build geditruntime fakeroot pacman-key --init<br />
$ flatpak build geditruntime fakeroot pacman-key --populate archlinux<br />
<br />
Then the package is installed. The host’s network connection must be made available to pacman.<br />
<br />
$ flatpak build --share=network geditruntime fakechroot fakeroot pacman --root /usr -S gedit<br />
<br />
You can test the installation before finishing the runtime (without proper sandboxing).<br />
<br />
$ flatpak build --socket=x11 geditruntime gedit<br />
<br />
Now finish building the runtime and export it to a new local repository. pacman’s GnuPG keys have permissions that may interfere and need to be removed first.<br />
<br />
$ flatpak build geditruntime rm -r /etc/pacman.d/gnupg<br />
$ flatpak build-finish geditruntime<br />
$ sed -i "s/\[Application\]/\[Runtime\]/;s/runtime=org.mydomain.BasePlatform/runtime=org.mydomain.geditruntime/" geditruntime/metadata<br />
$ flatpak build-export -r geditrepo geditruntime<br />
<br />
Then create a dummy app.<br />
<br />
$ flatpak build-init geditapp org.gnome.gedit org.mydomain.BaseSdk org.mydomain.geditruntime<br />
<br />
Now finish the dummy app. You can fine-tune the app’s access permissions when sandboxed by giving additional options when finishing the build. For possible options see the [[#See also|Flatpak documentation]] and the [https://gitlab.gnome.org/GNOME/gnome-apps-nightly/tree/master GNOME manifest files]. Alternatively, adapt {{ic|geditapp/metadata}} to your needs after finishing the build but before exporting. When the metadata file is complete, export the app to the repository.<br />
<br />
$ flatpak build-finish geditapp --socket=x11 ''[possibly other options]'' --command=gedit<br />
$ flatpak build-export geditrepo geditapp<br />
<br />
Install it along with the runtime.<br />
<br />
$ flatpak --user remote-add --no-gpg-verify geditrepo geditrepo<br />
$ flatpak install --user geditrepo org.mydomain.geditruntime<br />
$ flatpak install --user geditrepo org.gnome.gedit<br />
$ flatpak run org.gnome.gedit<br />
<br />
== See also ==<br />
<br />
* [http://flatpak.org Official website]<br />
* [https://github.com/flatpak/flatpak/wiki Official Github wiki]<br />
* [[Wikipedia::Flatpak|Wikipedia page]]<br />
* [https://wiki.gnome.org/Projects/SandboxedApps Gnome SandboxedApps]<br />
* [https://community.kde.org/Guidelines_and_HOWTOs/Flatpak KDE Testing Runtime and Applications]</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=ArchWiki:Translation_Team_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=592803
ArchWiki:Translation Team (简体中文)
2019-12-28T09:13:42Z
<p>C0n5t4ntK: /* 页面维护列表 */ 更新状态</p>
<hr />
<div>[[Category:简体中文]]<br />
[[Category:ArchWiki (简体中文)]]<br />
[[ar:ArchWiki Translation Team]]<br />
[[cs:ArchWiki Translation Team]]<br />
[[el:ArchWiki Translation Team]]<br />
[[en:ArchWiki:Translation Team]]<br />
[[es:ArchWiki:Translation Team]]<br />
[[fr:ArchWiki Translation Team]]<br />
[[hr:ArchWiki Translation Team]]<br />
[[it:ArchWiki Translation Team]]<br />
[[ja:ArchWiki 翻訳チーム]]<br />
[[ko:ArchWiki Translation Team]]<br />
[[nl:ArchWiki Translation Team]]<br />
[[pl:ArchWiki Translation Team]]<br />
[[pt:ArchWiki:Translation Team]]<br />
[[ru:ArchWiki Translation Team]]<br />
[[sk:ArchWiki Translation Team]]<br />
[[zh-hant:ArchWiki:Translation Team]]<br />
Arch Wiki 上有许多中文页面,这其中大部分是从外文翻译过来的,这些页面是无数中文志愿者劳动的结晶。随着时间推移,有些页面因为没有及时维护,内容严重过时。而目前的翻译工作缺少组织,效率偏低。所以参照西班牙和意大利翻译组的做法,添加这个页面。<br />
<br />
如果你希望对Arch Wiki做贡献,参与Wiki建设,比如翻译英文页面和对已翻译过的中文页面进行维护,只需要编辑下面的[[#页面维护列表]],添加相应的条目,并将自己加为相关页面的维护者。如果你在列表中还没有找到想要翻译的页面,可以自行添加。另外,如果因为时间原因无法再维护页面,请及时将自己从维护者列表中删除。<br />
<br />
== 创建翻译 ==<br />
{{警告|如果不准备翻译页面的大部分内容,请尽量不要新建简体中文页面。检查英文页面的更新需要花费不少精力,没有翻译的页面会增加维护负担。}}<br />
# 如果还不知道如何编辑 wiki,请阅读 [[Help:Editing (简体中文)|编辑帮助]]。<br />
# 阅读 [[Help:i18n (简体中文)|i18n帮助]],文章给出了 ArchWiki 国际化和本地化的指南。<br />
# [[Special:UserLogin|登录]] 以进行编辑。<br />
# 选择要翻译的页面,例如从 [[Special:Random|随机页面]] 或[[#页面维护列表|页面维护列表]] 中选择一个未翻译完成的页面。假设要翻译 [[Some Page]].<br />
# 进入选择的英文页面,点击页面顶部的 '''编辑'''。<br />
# 添加要翻译文件的语言间链接, 简体中文的话加入<nowiki>[[zh-hans:Some Page]]</nowiki>,其它语言参见[[Help:i18n#Interlanguage links]])。<br />
# 复制所有页面代码。<br />
# 保存页面 (新加了语言链接)<br />
# 访问页面左边新添加的语言链接,应该会进到 [[Some Page (简体中文)]] : {{ic|<nowiki>https://wiki.archlinux.org/index.php/Some_Page_(</nowiki>''简体中文'')}}<br />
# 因为页面不存在,点击 '''创建'''。<br />
# 将显示一个编辑器 - 粘贴复制的英文页面。<br />
# 将文章分类修改为本地化版本,例如将 {{ic|<nowiki>[[Category:Internationalization]]</nowiki>}} 修改为 {{ic|<nowiki>[[Category:Internationalization (简体中文)]]</nowiki>}},参阅[[Help:Category (简体中文)]].<br />
# 修改语言间链接,指向英文页面(将 {{ic|zh-hans}} 修改为 {{ic|en}},并将英文页面移到文章顶部。<br />
# 翻译页面,进行保存。<br />
# (推荐)给翻译完成的页面加上[[Template:TranslationStatus (简体中文)|翻译状态]],后有详细介绍。<br />
# 更新所有其它语言页面,加入刚翻译文章的语言间链接。<br />
# (可选)创建一个简体中文名称的页面,指向新创建的页面:访问 {{ic|<nowiki>https://wiki.archlinux.org/index.php/</nowiki>''页面的中文名称''}}.<br />
# (可选)建立新页面,并加入:{{bc|<nowiki>#REDIRECT [[Some Page (简体中文)</nowiki>]]}}<br />
<br />
== Templates ==<br />
<br />
{{Translateme (简体中文)|Not translated}}<br />
<br />
The following table lists the [[Help:Template (简体中文)|templates]] that should be translated and their Simplified Chinese equivalent.<br />
<br />
{| class=wikitable<br />
! English template || Simplified Chinese version<br />
|-<br />
! colspan=2| Article templates<br />
|-<br />
| [[Template:Related articles start]] || [[Template:Related articles start (简体中文)]]<br />
|-<br />
| [[Template:Yes]] || [[Template:是]]<br />
|-<br />
| [[Template:No]] || [[Template:否]]<br />
|-<br />
| [[Template:Tip]] || [[Template:提示]]<br />
|-<br />
| [[Template:Note]] || [[Template:注意]]<br />
|-<br />
| [[Template:Warning]] || [[Template:警告]]<br />
|-<br />
| [[Template:Dead link]] || [[Template:失效链接]]<br />
|-<br />
| [[Template:Broken package link]] || {{-}}<br />
|-<br />
! colspan=2| Translation status templates<br />
|-<br />
| [[Template:Bad translation]] || {{-}}<br />
|-<br />
| [[Template:Translateme]] || [[Template:Translateme (简体中文)]]<br />
|-<br />
| [[Template:TranslationStatus]] || [[Template:TranslationStatus (简体中文)]]<br />
|-<br />
! colspan=2| Special templates<br />
|-<br />
| [[Template:Cat main]] || {{-}}<br />
|-<br />
| [[Template:Template]] || {{-}}<br />
|}<br />
<br />
== 完善翻译 ==<br />
[https://wiki.archlinux.org/index.php?title=Special:WhatLinksHere/Template:Translateme_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&limit=100 这个页面] 包含了需要完善翻译的简体中文页面。完善翻译的基本步骤:<br />
# 选择自己比较熟悉的文章进行翻译<br />
# 先检查英文页面的对应段落,更新成最新的英文后再翻译,避免翻译过时的内容,减少信息遗漏。<br />
# 翻译完成后删除页面中的 <nowiki>{{translateme (简体中文)}}</nowiki> 标记<br />
# (推荐)给翻译完成的页面加上[[Template:TranslationStatus (简体中文)|翻译状态]],后有详细介绍。<br />
<br />
== 更新过期页面 == <br />
如果发现有 Wiki 页面过期或错误:<br />
* 小的改动,有时间可以立即进行修改同步,维护者并不控制页面的编辑权限,越多的人参与维护越好。如果改动较大,请先联系维护者,避免重复劳动。<br />
* 没有时间查看更改,请给页面加上 {{ic|<nowiki>{{out of date}}</nowiki>}} 模版,这样其他贡献者更容易发现需要更新的页面,而读者看到过期标记就可以直接查看英文页面,以免被错误内容误导,白白耽误时间。<br />
* 没有时间翻译,请将过期的中文部分删去,从英文页面中复制更改的部分到中文页面的相应部分,去掉{{ic|<nowiki>{{out of date}}</nowiki>}}模板(如果页面上有的话)并加上{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板,这样其他贡献者就更容易发现需要翻译的页面,而读者也不会被过期的内容误导。<br />
如果发现有页面未翻译:<br />
* 有时间的话,请将页面中的英文部分翻译为中文,并去掉{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板。<br />
* 没有时间翻译,请为页面添加{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板,这样其他的贡献者就能更容易发现需要翻译的页面。<br />
{{注意|在修改页面上的模板时,请同时更新页面维护列表的翻译状态。}}<br />
<br />
== 翻译任务 ==<br />
=== 模板 Article summary 变更为 Related ===<br />
因为 Summary 中的简介基本上和正文的介绍一样,所以页面左边的介绍栏进行了简化,只保留相关文章功能。英文页面正在进行大规模修改,相应的中文页面也需要同步更新。<br />
<br />
需要注意的地方:<br />
* 将第一行改成<br />
: <nowiki>{{Related articles start (简体中文)}}</nowiki><br />
* 如果英文的相关文章存在中文翻译,则替换为简体中文页面。示例:<br />
: <nowiki>{{Related2|Display Manager (简体中文)|显示管理器}}</nowiki><br />
* 示例:[https://wiki.archlinux.org/index.php?title=Start_X_at_Login&diff=0&oldid=270155 英文变更], [https://wiki.archlinux.org/index.php?title=Start_X_at_Login_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=285643&oldid=242662 对应的翻译]<br />
<br />
== 维护翻译 ==<br />
完成页面的翻译只是初步完成任务,及时同步英文页面改动、更新翻译是一个持续性的工作,可能会耗费更多的时间。<br />
<br />
=== 页面认领 ===<br />
所有人都可以认领页面。认领后的责任包括进行翻译,关注英文页面的改动,及时同步翻译。<br />
<br />
为了更好的跟踪英文页面的修改,请务必在设置中启用监视列表邮件通知,并监视对应的英文页面(从设置中找到监视列表,加入英文页面。或者直接到英文页面点击页面顶端的监视标签。这样只要有改动,就会收到邮件通知)。<br />
<br />
{{小贴士|如果收到邮件通知后没有访问页面或者访问了页面却没有登录用户,下次页面改动时就不会再发邮件通知。可以点击监视列表中的'''标记所有页面为已读'''再次获取更新。}}<br />
<br />
如果页面有维护者但长期得不到更新,将会在维护列表中删除维护者。<br />
<br />
=== 翻译状态模板 ===<br />
Arch 作为滚动发行版,软件变化比较快,对应的文档变化也比较快。许多翻译的文章由于缺乏更新,会产生命令运行出错或不起作用等问题。而由于这些过期页面没有及时标记出来,所以用户无法及时获得更新。[[Template:TranslationStatus (简体中文)|翻译状态模板]]就是为了解决这个问题而创建。<br />
<br />
此模板可以起到如下作用:<br />
* 为用户提供翻译状况,包括翻译时间、英文页面的最后版本等<br />
* 用户可以点击查看翻译后,英文页面的改动,这样英文不是很好的用户可以只查看很小一部分英文内容,并判断出是否影响操作。<br />
* 翻译人员可以跟踪页面状况,通过[[Special:WhatLinksHere/Template:TranslationStatus_(简体中文)|模板的反向链接]]可以查找到所有标记页面,查看需要更新翻译的部分。<br />
<br />
[[Template:TranslationStatus (简体中文)|模板页面]]有详细的使用方法。<br />
<br />
=== 页面维护列表 ===<br />
{{注意|请按照拉丁字母顺序添加页面。}}<br />
<br />
翻译状态说明:<br />
;过期:页面内容未与英文页面同步,对应{{ic|<nowiki>{{out of date}}</nowiki>}} 模版<br />
;未翻译:页面中含有英文内容,对应{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板<br />
;完成:页面已与英文页面同步<br />
<br />
{| class="wikitable sortable collapsible" border="1"<br />
|-<br />
! 页面<br />
! 翻译状态<br />
! 维护者<br />
! class="unsortable" width="30%" | 备注<br />
|-<br />
| [[acpid (简体中文)]]<br />
| 过期<br />
| Cael<br />
|<br />
|-<br />
| [[Advanced Linux Sound Architecture (简体中文)]]<br />
| 翻译中<br />
| ihonliu<br />
| 无<br />
|-<br />
| [[Arch based distributions (active) (简体中文)]]<br />
| 完成<br />
| Joshua<br />
| 勘误中<br />
|-<br />
| [[Amateur radio (简体中文)]]<br />
| 翻译中<br />
| liu-shuyuan<br />
| <br />
|-<br />
| [[AMD Catalyst (简体中文)]]<br />
| 过期<br />
| Shibao Zhao<br />
| 无<br />
|-<br />
| [[ATI (简体中文)]]<br />
| 完成<br />
| skysailing<br />
| 无<br />
|-<br />
| [[AUR helpers (简体中文)]]<br />
| 完成<br />
| Kurobac<br />
| 部分用词可能需要修改<br />
|-<br />
| [[awesome (简体中文)]]<br />
| 进行中<br />
| Cael<br />
| 无<br />
|-<br />
| [[BIND (简体中文)]]<br />
| 完成<br />
| Dargasia<br />
|<br />
|-<br />
| [[Bumblebee (简体中文)]]<br />
| 完成<br />
| Peter<br />
| 无<br />
|-<br />
| [[Chromium (简体中文)]]<br />
| 完成<br />
| Bobby<br />
| 无<br />
|-<br />
| [[Ceph (简体中文)]]<br />
| 翻译中<br />
| Aaron Chen<br />
| 部分未翻译 <br />
|-<br />
| [[Cinnamon (简体中文)]]<br />
| 部分翻译 <br />
| Bobby<br />
| 部分未翻译 <br />
|- <br />
| [[Common Applications (简体中文)]]<br />
| 部分翻译 <br />
| DavidChen<br />
| 翻译中<br />
|-<br />
| [[Common Applications/Science (简体中文)]]<br />
| drop maintain<br />
| 更新,翻译中<br />
|<br />
|-<br />
| [[Compiz (简体中文)]]<br />
| 翻译中<br />
| xiii_1991<br />
| 20140813开始<br />
|-<br />
| [[Conky (简体中文)]]<br />
| 完成<br />
| upi<br />
| 无<br />
|-<br />
| [[Core utilities (简体中文)]]<br />
| 完成<br />
| rentaro, Arisaka<br />
| 无<br />
|-<br />
|-<br />
| [[Clover (简体中文)]]<br />
| 完成<br />
| Yume Kankawa<br />
| 无<br />
|-<br />
| [[Disk cloning (简体中文)]]<br />
| 翻译中<br />
| _spaike97<br />
| 无<br />
|-<br />
| [[Dynamic Kernel Module Support (简体中文)]]<br />
| 完成<br />
| Mithrandir<br />
| 完善中<br />
|-<br />
| [[Emacs (简体中文)]]<br />
| 翻译中<br />
| Jaurung yuanhang<br />
| 未完成<br />
|-<br />
| [[File recovery (简体中文)]]<br />
| 翻译中<br />
| _spaike97<br />
| 无<br />
|-<br />
| [[Fish (简体中文)]]<br />
| 完成<br />
| liu-shuyuan<br />
|<br />
|-<br />
| [[Font configuration (简体中文)]]<br />
| 翻译中<br />
| Jaurung<br />
| 完善中<br />
|-<br />
| [[Fonts (简体中文)]]<br />
| 翻译中<br />
| qqbzg<br />
| 无<br />
|-<br />
| [[GDM (简体中文)]]<br />
| 翻译中<br />
| Junjie Yuan<br />
| 绝大多数内容未翻译,重新进行翻译<br />
|-<br />
| [[GNOME (简体中文)]]<br />
| 完成<br />
| skywet<br />
| <br />
|-<br />
| [[GRUB (简体中文)]]<br />
| 完成<br />
| Armodeniz<br />
| <br />
|-<br />
| [[GRUB/Tips and tricks (简体中文)]]<br />
| 完成<br />
| Armodeniz<br />
| <br />
|-<br />
| [[Java (简体中文)]]<br />
| 翻译中<br />
| CaCaCarrot<br />
| 无<br />
|-<br />
| [[KDE (简体中文)]]<br />
| 过期<br />
| <br />
| <br />
|-<br />
| [[LAMP (简体中文)]]<br />
| 完成<br />
| Liuzhengyi<br />
| 勘误中<br />
|-<br />
| [[LibreOffice (简体中文)]]<br />
| 完成<br />
| qqbzg<br />
| 勘误中<br />
|-<br />
| [[Libvirt (简体中文)]]<br />
| 完成<br />
| Kurobac<br />
| 需要格式改进<br />
|-<br />
| [[Local Mirror (简体中文)]]<br />
| 完成<br />
| Jason Zhang<br />
| 完善中<br />
|- <br />
| [[MATLAB (简体中文)]]<br />
| 部分翻译 <br />
| Liu Qinyang<br />
|<br />
|-<br />
| [[Minecraft (简体中文)]]<br />
| 完成 <br />
| Xavier Lau<br />
| 页面已经与英文版同步,长期维护中<br />
|-<br />
| [[NetworkManager (简体中文)]]<br />
| 翻译中 <br />
| Jack-lijing, leeking <br />
| 请优先翻译<br />
|-<br />
| [[Network Time Protocol daemon (简体中文)]]<br />
| 完成<br />
| sid<br />
| 完善中<br />
|-<br />
| [[OpenOffice (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Opera (简体中文)]]<br />
| 未翻译<br />
| Bobby<br />
| 请优先翻译此文 <br />
|-<br />
| [[Pacman GUI Frontends (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Pidgin (简体中文)]]<br />
| 进行中<br />
| Cael<br />
| 无 <br />
|-<br />
| [[Python打包指引 (简体中文)]]<br />
| 翻译中<br />
| SherlockHolo<br />
| 无<br />
|- <br />
| [[ranger (简体中文)]]<br />
| 完成<br />
| Jason Zhang<br />
| 完善中<br />
|-<br />
| [[Raspberry Pi (简体中文)]]<br />
| 翻译中<br />
| Mithrandir<br />
| <br />
|-<br />
| [[Reporting bug guidelines (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[SDDM (简体中文)]]<br />
| 完成<br />
| C0n5t4ntK<br />
| 长期维护中<br />
|-<br />
| [[Secure Shell (简体中文)]]<br />
| 完成<br />
| Arisaka<br />
| 无<br />
|-<br />
| [[Smart Common Input Method platform (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Steam (简体中文)]]<br />
| 完成<br />
| C0n5t4ntK<br />
| 长期维护中<br />
|-<br />
| [[Systemd-timesyncd (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[TLP (简体中文)]]<br />
| 完成<br />
| Skywet<br />
| 持续更新中 <br />
|-<br />
| [[Tomcat (简体中文)]]<br />
| 完成<br />
| Starwing117<br />
| 持续更新中 <br />
|-<br />
| [[Vim (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[VirtualBox (简体中文)]]<br />
| 翻译至 2017-10-15<br />
| [[User:5long]]<br />
|<br />
|-<br />
| [[VMware (简体中文)]]<br />
| 完成<br />
| ThomasWFan<br />
| 页面已经与英文版同步,长期维护中<br />
|- <br />
| [[Xfce (简体中文)]]<br />
| 完成 <br />
| 无<br />
| 无<br />
|-<br />
| [[Xmonad (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Xrandr (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=SDDM_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=592801
SDDM (简体中文)
2019-12-28T09:08:57Z
<p>C0n5t4ntK: 添加翻译状态。</p>
<hr />
<div>[[Category:KDE (简体中文)]]<br />
[[Category:Display managers (简体中文)]]<br />
[[en:SDDM]]<br />
[[fr:SDDM]]<br />
[[ja:SDDM]]<br />
[[ru:SDDM]]<br />
{{Related articles start (简体中文)}}<br />
{{Related|Display manager}}<br />
{{Related|KDE (简体中文)}}<br />
{{Related articles end}}<br />
{{TranslationStatus (简体中文)|SDDM|2019-12-28|592454}}<br />
[https://github.com/sddm/sddm/ Simple Desktop Display Manager] (SDDM) 是 [[KDE (简体中文)]] Plasma 桌面环境推荐的 [[Display_manager_(简体中文)|显示管理器]]。<br />
<br />
[[Wikipedia:Simple Desktop Display Manager|维基百科]] 介绍:<br />
<br />
:Simple Desktop Display Manager (SDDM) 是用于 X11 和 wayland 视窗系统的显示管理器(图形登录界面)。SDDM 完全使用 C++11 编写并支持通过 QML 改变主题。对于KDE Plasma 5,KDE 选择了 SDDM 作为 KDE Display Manager 的接替者。<br />
<br />
{{注意|SDDM 还没有完全支持 Wayland 视窗系统 [https://github.com/sddm/sddm/issues/440]。Wayland 会话在支持之列,但 SDDM 运行于 X11。}}<br />
<br />
== 安装 ==<br />
<br />
[[Help:Reading (简体中文)#安装软件包|安装]] {{Pkg|sddm}} 软件包。对于 [[KDE#KCM|KDE Config Module]],可选安装 {{Pkg|sddm-kcm}} 软件包。<br />
<br />
然后根据 [[Display manager (简体中文)#加载显示管理器]] 的说明配置 SDDM 在系统引导时启动。<br />
<br />
== 配置 ==<br />
<br />
SDDM 的默认配置文件为 {{ic|/usr/lib/sddm/sddm.conf.d/default.conf}}。要修改配置,请在 {{ic|/etc/sddm.conf.d/}} 目录下创建配置文件。详见 {{man|5|sddm.conf}} 以获得所有配置选项。<br />
<br />
{{pkg|sddm-kcm}} 软件包 (包含在 {{grp|plasma}} 用户组) 提供了一个图形用户界面以在 Plasma 系统设置中配置 SDDM。[[AUR]] 中也有基于 [[Qt]] 的配置软件 {{AUR|sddm-config-editor-git}}。<br />
<br />
一切东西都应该开箱即用,自从 Arch Linux 使用 [[systemd]] 后,SDDM 默认使用 {{ic|systemd-logind}} 以进行会话管理。<br />
<br />
=== 自动登录 ===<br />
<br />
SDDM 通过它的配置文件来支持自动登录,例如:<br />
<br />
{{hc|/etc/sddm.conf.d/autologin.conf|2=<br />
[Autologin]<br />
User=john<br />
Session=plasma.desktop<br />
}}<br />
<br />
此配置使得在系统启动后自动以用户 {{ic|john}} 开启一个 KDE Plasma 会话。在 {{ic|/usr/share/xsessions/}} 目录下你可以找到可用的会话类型。<br />
<br />
目前尚不支持自动登录 KDE Plasma 的同时锁定会话 [https://github.com/sddm/sddm/issues/306]<br />
<br />
你可以添加一个脚本,在 KDE 自动启动时激活屏幕保护程序以作为一个解决方案:<br />
<br />
#!/bin/sh<br />
/usr/bin/dbus-send --session --type=method_call --dest=org.freedesktop.ScreenSaver /ScreenSaver org.freedesktop.ScreenSaver.Lock &<br />
<br />
=== 登录后自动解锁 KDE 钱包 ===<br />
<br />
详见 [[KDE Wallet (简体中文)#在登录时自动解锁 Kwallet]]。<br />
<br />
=== 主题设置 ===<br />
<br />
在 {{ic|[Theme]}} 小节更改主题设置。如果您使用 Plasma 的系统设置,主题可能会显示预览。<br />
<br />
设置 {{ic|breeze}} 以获得 Plasma 默认主题。<br />
<br />
[[AUR]] 有一些可用的主题,例如 {{AUR|archlinux-themes-sddm}}。<br />
<br />
==== 当前主题 ====<br />
<br />
通过 {{ic|Current}} 的值设置当前主题,例如 {{ic|1=Current=archlinux-simplyblack}}。<br />
<br />
==== 编辑主题 ====<br />
<br />
默认 SDDM 主题目录为 {{ic|/usr/share/sddm/themes/}}。你可以添加你的自制主题到该目录下一个单独的子目录中。注意 SDDM 要求这些子目录的名字要与主题的名字一致。可以通过研究已安装的文件来更改或创建属于你的主题。<br />
<br />
==== 测试(预览)主题 ====<br />
<br />
如果需要,你可以预览一个 SDDM 主题。如果你想知道一个主题看起来怎么样,或是想要编辑一个主题后在不必登出的情况下观察改动的效果,那么这将会非常有用。你可以运行下面的命令:<br />
<br />
$ sddm-greeter --test-mode --theme /usr/share/sddm/themes/breeze<br />
<br />
这应该为所有已连接的显示器打开一个新窗口以显示主题的预览。<br />
<br />
{{注意|这只是一个预览。在这个模式下,一些动作如关机、挂起或登录将不会执行。}}<br />
<br />
==== 鼠标光标 ====<br />
<br />
要设置鼠标光标的主题,将 {{ic|CursorTheme}} 设置成您喜欢的光标主题。<br />
<br />
合法的 [[Plasma]] 鼠标光标主题有 {{ic|breeze_cursors}},{{ic|Breeze_Snow}} 和 {{ic|breeze-dark}}。<br />
<br />
==== 用户图标(头像) ====<br />
<br />
SDDM 对于每个用户从相应的 {{ic|~/.face.icon}} 目录下读取 PNG 图片格式的用户图标(即“头像”),或者从 SDDM 配置文件中由 {{ic|FacesDir}} 为所有用户定义的共有位置。配置设置可以通过修改 {{ic|/etc/sddm.conf}} 文件被直接替换,更好的方法是创建一个位于 {{ic|/etc/sddm.conf.d/}} 下的文件来修改,例如 {{ic|/etc/sddm.conf.d/avatar.conf}}。<br />
<br />
要使用 {{ic|FacesDir}} 选项来确定头像位置,即在配置文件中 {{ic|FacesDir}} 所确定的位置为每一个用户放置一个 PNG 图片,命名如 {{ic|''username''.face.icon}}。{{ic|FacesDir}} 默认的路径为 {{ic|/usr/share/sddm/faces/}}。你可以更改默认 {{ic|FacesDir}} 目录以合乎你的要求。下面是一个例子:<br />
<br />
{{hc|/etc/sddm.conf.d/avatar.conf|2=<br />
[Theme]<br />
FacesDir=/var/lib/AccountsService/icons/<br />
}}<br />
<br />
另一个选项是放置一个名为 {{ic|.face.icon}} 的 PNG 图片到你的家目录下。在这种情况下,您不用对任何 SDDM 配置文件进行更改。不过,您仍需确定 {{ic|sddm}} 用户可以读取这些 PNG 图片作为用户图标。<br />
<br />
{{注意|在许多 KDE 的版本中,用户图标图像文件是 {{ic|~/.face}} 而 {{ic|~/.face.icon}} 是链接到图像文件的符号链接。如果用户的图标是符号链接,你需要为目标文件设置恰当的文件权限。}} <br />
<br />
为了 [[Access Control Lists#Set ACL|设置合适权限]] 运行:<br />
<br />
$ setfacl -m u:sddm:x ~/<br />
$ setfacl -m u:sddm:r ~/.face.icon<br />
<br />
你可以通过运行下列命令 [[Access Control Lists#Show ACL|检查权限]]:<br />
<br />
$ getfacl ~/<br />
$ getfacl ~/.face.icon<br />
<br />
详见 [https://github.com/sddm/sddm#no-user-icon SDDM README: No User Icon]。<br />
<br />
=== 数字锁 ===<br />
<br />
如果你想强制启用数字锁,在 {{ic|[General]}} 小节设置 {{ic|1=Numlock=on}}。<br />
<br />
=== 旋转显示 ===<br />
<br />
详见 [[Xrandr#Configuration]]。<br />
<br />
=== DPI 设置 ===<br />
<br />
有时位于“显示管理器”级别设置正确的显示器 DPI 是很有用的。[https://github.com/sddm/sddm/blob/master/README.md#custom-dpi] 你需要在 {{ic|ServerArguments}} 字符串的末尾加上参数 {{ic|-dpi ''your_dpi''}} 例如:<br />
<br />
{{hc|head=/etc/sddm.conf.d/dpi.conf|output=<br />
[X11]<br />
ServerArguments=-nolisten tcp -dpi 94<br />
}}<br />
<br />
=== 启用 HiDPI ===<br />
<br />
创建 [[HiDPI (简体中文)|HiDPI]] 配置文件如下:<br />
<br />
{{hc|/etc/sddm.conf.d/hidpi.conf|2=<br />
[Wayland]<br />
EnableHiDPI=true<br />
<br />
[X11]<br />
EnableHiDPI=true<br />
}}<br />
<br />
=== 使用指纹识别器 ===<br />
<br />
{{注意|在改变设置前要确定你的指纹已经注册完成。指纹支持目前并不是完全工作正常,并且看起来在使用这种方法时仅使用密码登录将不再有效。}}<br />
<br />
SDDM 使用 [[fprint]] 以使用指纹识别。在安装了 fprint 和添加指纹签名后,在添加 {{ic|/etc/pam.d/sddm}} 的开始位置添加一行 {{ic|auth sufficient pam_fprintd.so}}。<br />
<br />
{{提示|要使其在 KDE 的锁屏模式下工作,将上面提到的一行同样添加于 {{ic|/etc/pam.d/kde}} 的开始位置。}}<br />
<br />
如果你现在在空密码区域按下回车,那么指纹识别器应该开始工作了。<br />
<br />
== 故障排除 ==<br />
<br />
=== 只有空白屏幕和光标,但没有欢迎界面 ===<br />
<br />
使用 {{ic|df -h}} 命令检查您的磁盘空间。如果没有足够的空间,欢迎界面会崩溃。<br />
<br />
如果磁盘空间足够,那么这个问题可能源于此 [https://github.com/sddm/sddm/issues/1179 bug]。切换 [[Getty#Installation|到另一个 TTY]] 来 [[restart|重启]] SDDM。<br />
<br />
=== SDDM 出现欢迎界面前的加载时间过长 ===<br />
<br />
内核熵池过小会造成长时间的 SDDM 加载过程([https://github.com/sddm/sddm/issues/1036 Bug report])。详见 [[Random number generation]] 扩大内核熵池的建议。<br />
<br />
=== 登录后挂起 ===<br />
<br />
尝试移除 {{ic|~/.Xauthority}} 文件后不重启再次登入。重启会再次创建该文件即该问题依旧存在。<br />
<br />
=== SDDM 在 tty1 启动而不是 tty7 ===<br />
<br />
SDDM 根据 [http://0pointer.de/blog/projects/serial-console.html systemd 的规定] 在 tty1 启动图形会话。如果您更喜欢老派的 tty1 到 tty6 皆预留为文本终端,更改 {{ic|MinimumVT}} 变量的默认值,其位于 {{ic|[X11]}} 小节下:<br />
<br />
{{hc|/etc/sddm.conf.d/tty.conf|2=<br />
[X11]<br />
MinimumVT=7<br />
}}<br />
<br />
=== 一个或多个用户没有出现在欢迎界面 ===<br />
<br />
{{警告|用户设置过低或过高的 {{ic|UID}} 范围应该大体上不会暴露给 [[Display manager (简体中文)]]。}}<br />
<br />
SDDM 默认会显示 UID 在 1000 到 65000 范围内的用户,如果想要显示的用户的 UID 小于这个范围,那么您就不得不更改这个范围。比如,对于 UID 为 501时,可以修改:<br />
<br />
{{hc|/etc/sddm.conf.d/uid.conf|2=<br />
[Users]<br />
HideShells=/sbin/nologin,/bin/false<br />
# Hidden users, this is if any system users fall within your range, see /etc/passwd on your system.<br />
HideUsers=git,sddm,systemd-journal-remote,systemd-journal-upload<br />
<br />
# Maximum user id for displayed users<br />
MaximumUid=65000<br />
<br />
# Minimum user id for displayed users<br />
MinimumUid=500 #My UID is 501<br />
}}<br />
<br />
=== SDDM 只加载 US 键盘布局 ===<br />
<br />
SDDM 加载的键盘布局被确定在 {{ic|/etc/X11/xorg.conf.d/00-keyboard.conf}} 文件中。您可以通过 {{ic|localectl set-x11-keymap}} 命令以生成此配置文件。详见 [[Keyboard configuration in Xorg]]。<br />
<br />
SDDM 可能也会错误地显示为 US 布局,但在您开始输入您的密码时立即切换到正确的键盘布局 [https://github.com/sddm/sddm/issues/202#issuecomment-76001543]。此 bug 看起来不是来自 SDDM,而是 {{Pkg|libxcb}} (version 1.13-1 as of 2018) [https://github.com/sddm/sddm/issues/202#issuecomment-133628462]。<br />
<br />
=== 屏幕分辨率过低 ===<br />
<br />
此问题可能源于显示屏 HiDPI 的使用破坏了 [[Wikipedia:Extended Display Identification Data|EDID]] [https://github.com/sddm/sddm/issues/692]。如果你 [[#启用 HiDPI|启动了 HiDPI]],尝试关掉它。<br />
<br />
如果上述方法失败了,您可以尝试在 Xorg 配置文件中设置您的显示尺寸:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/90-monitor.conf|2=<br />
Section "Monitor"<br />
Identifier "<default monitor>"<br />
DisplaySize 345 194 # in millimeters<br />
EndSection<br />
}}<br />
<br />
=== 自动挂载家目录的加载时间过长 ===<br />
<br />
SDDM 默认会访问 {{ic|~/.face.icon}} 文件以尝试显示用户头像。如果您的家目录采用自动挂载的文件系统(autofs),例如如果您使用 [[dm-crypt]],这将会使之等待 60 秒,直到自动挂载的文件系统(autofs)返回此目录不能被挂载。<br />
<br />
您可以通过编辑 {{ic|/etc/sddm.conf}} 文件以关闭头像功能:<br />
<br />
{{hc|/etc/sddm.conf|2=<br />
[Theme]<br />
EnableAvatars=false<br />
}}</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=SDDM_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=592798
SDDM (简体中文)
2019-12-28T08:58:49Z
<p>C0n5t4ntK: 翻译完成</p>
<hr />
<div>[[Category:KDE (简体中文)]]<br />
[[Category:Display managers (简体中文)]]<br />
[[en:SDDM]]<br />
[[fr:SDDM]]<br />
[[ja:SDDM]]<br />
[[ru:SDDM]]<br />
{{Related articles start (简体中文)}}<br />
{{Related|Display manager}}<br />
{{Related|KDE (简体中文)}}<br />
{{Related articles end}}<br />
[https://github.com/sddm/sddm/ Simple Desktop Display Manager] (SDDM) 是 [[KDE (简体中文)]] Plasma 桌面环境推荐的 [[Display_manager_(简体中文)|显示管理器]]。<br />
<br />
[[Wikipedia:Simple Desktop Display Manager|维基百科]] 介绍:<br />
<br />
:Simple Desktop Display Manager (SDDM) 是用于 X11 和 wayland 视窗系统的显示管理器(图形登录界面)。SDDM 完全使用 C++11 编写并支持通过 QML 改变主题。对于KDE Plasma 5,KDE 选择了 SDDM 作为 KDE Display Manager 的接替者。<br />
<br />
{{注意|SDDM 还没有完全支持 Wayland 视窗系统 [https://github.com/sddm/sddm/issues/440]。Wayland 会话在支持之列,但 SDDM 运行于 X11。}}<br />
<br />
== 安装 ==<br />
<br />
[[Help:Reading (简体中文)#安装软件包|安装]] {{Pkg|sddm}} 软件包。对于 [[KDE#KCM|KDE Config Module]],可选安装 {{Pkg|sddm-kcm}} 软件包。<br />
<br />
然后根据 [[Display manager (简体中文)#加载显示管理器]] 的说明配置 SDDM 在系统引导时启动。<br />
<br />
== 配置 ==<br />
<br />
SDDM 的默认配置文件为 {{ic|/usr/lib/sddm/sddm.conf.d/default.conf}}。要修改配置,请在 {{ic|/etc/sddm.conf.d/}} 目录下创建配置文件。详见 {{man|5|sddm.conf}} 以获得所有配置选项。<br />
<br />
{{pkg|sddm-kcm}} 软件包 (包含在 {{grp|plasma}} 用户组) 提供了一个图形用户界面以在 Plasma 系统设置中配置 SDDM。[[AUR]] 中也有基于 [[Qt]] 的配置软件 {{AUR|sddm-config-editor-git}}。<br />
<br />
一切东西都应该开箱即用,自从 Arch Linux 使用 [[systemd]] 后,SDDM 默认使用 {{ic|systemd-logind}} 以进行会话管理。<br />
<br />
=== 自动登录 ===<br />
<br />
SDDM 通过它的配置文件来支持自动登录,例如:<br />
<br />
{{hc|/etc/sddm.conf.d/autologin.conf|2=<br />
[Autologin]<br />
User=john<br />
Session=plasma.desktop<br />
}}<br />
<br />
此配置使得在系统启动后自动以用户 {{ic|john}} 开启一个 KDE Plasma 会话。在 {{ic|/usr/share/xsessions/}} 目录下你可以找到可用的会话类型。<br />
<br />
目前尚不支持自动登录 KDE Plasma 的同时锁定会话 [https://github.com/sddm/sddm/issues/306]<br />
<br />
你可以添加一个脚本,在 KDE 自动启动时激活屏幕保护程序以作为一个解决方案:<br />
<br />
#!/bin/sh<br />
/usr/bin/dbus-send --session --type=method_call --dest=org.freedesktop.ScreenSaver /ScreenSaver org.freedesktop.ScreenSaver.Lock &<br />
<br />
=== 登录后自动解锁 KDE 钱包 ===<br />
<br />
详见 [[KDE Wallet (简体中文)#在登录时自动解锁 Kwallet]]。<br />
<br />
=== 主题设置 ===<br />
<br />
在 {{ic|[Theme]}} 小节更改主题设置。如果您使用 Plasma 的系统设置,主题可能会显示预览。<br />
<br />
设置 {{ic|breeze}} 以获得 Plasma 默认主题。<br />
<br />
[[AUR]] 有一些可用的主题,例如 {{AUR|archlinux-themes-sddm}}。<br />
<br />
==== 当前主题 ====<br />
<br />
通过 {{ic|Current}} 的值设置当前主题,例如 {{ic|1=Current=archlinux-simplyblack}}。<br />
<br />
==== 编辑主题 ====<br />
<br />
默认 SDDM 主题目录为 {{ic|/usr/share/sddm/themes/}}。你可以添加你的自制主题到该目录下一个单独的子目录中。注意 SDDM 要求这些子目录的名字要与主题的名字一致。可以通过研究已安装的文件来更改或创建属于你的主题。<br />
<br />
==== 测试(预览)主题 ====<br />
<br />
如果需要,你可以预览一个 SDDM 主题。如果你想知道一个主题看起来怎么样,或是想要编辑一个主题后在不必登出的情况下观察改动的效果,那么这将会非常有用。你可以运行下面的命令:<br />
<br />
$ sddm-greeter --test-mode --theme /usr/share/sddm/themes/breeze<br />
<br />
这应该为所有已连接的显示器打开一个新窗口以显示主题的预览。<br />
<br />
{{注意|这只是一个预览。在这个模式下,一些动作如关机、挂起或登录将不会执行。}}<br />
<br />
==== 鼠标光标 ====<br />
<br />
要设置鼠标光标的主题,将 {{ic|CursorTheme}} 设置成您喜欢的光标主题。<br />
<br />
合法的 [[Plasma]] 鼠标光标主题有 {{ic|breeze_cursors}},{{ic|Breeze_Snow}} 和 {{ic|breeze-dark}}。<br />
<br />
==== 用户图标(头像) ====<br />
<br />
SDDM 对于每个用户从相应的 {{ic|~/.face.icon}} 目录下读取 PNG 图片格式的用户图标(即“头像”),或者从 SDDM 配置文件中由 {{ic|FacesDir}} 为所有用户定义的共有位置。配置设置可以通过修改 {{ic|/etc/sddm.conf}} 文件被直接替换,更好的方法是创建一个位于 {{ic|/etc/sddm.conf.d/}} 下的文件来修改,例如 {{ic|/etc/sddm.conf.d/avatar.conf}}。<br />
<br />
要使用 {{ic|FacesDir}} 选项来确定头像位置,即在配置文件中 {{ic|FacesDir}} 所确定的位置为每一个用户放置一个 PNG 图片,命名如 {{ic|''username''.face.icon}}。{{ic|FacesDir}} 默认的路径为 {{ic|/usr/share/sddm/faces/}}。你可以更改默认 {{ic|FacesDir}} 目录以合乎你的要求。下面是一个例子:<br />
<br />
{{hc|/etc/sddm.conf.d/avatar.conf|2=<br />
[Theme]<br />
FacesDir=/var/lib/AccountsService/icons/<br />
}}<br />
<br />
另一个选项是放置一个名为 {{ic|.face.icon}} 的 PNG 图片到你的家目录下。在这种情况下,您不用对任何 SDDM 配置文件进行更改。不过,您仍需确定 {{ic|sddm}} 用户可以读取这些 PNG 图片作为用户图标。<br />
<br />
{{注意|在许多 KDE 的版本中,用户图标图像文件是 {{ic|~/.face}} 而 {{ic|~/.face.icon}} 是链接到图像文件的符号链接。如果用户的图标是符号链接,你需要为目标文件设置恰当的文件权限。}} <br />
<br />
为了 [[Access Control Lists#Set ACL|设置合适权限]] 运行:<br />
<br />
$ setfacl -m u:sddm:x ~/<br />
$ setfacl -m u:sddm:r ~/.face.icon<br />
<br />
你可以通过运行下列命令 [[Access Control Lists#Show ACL|检查权限]]:<br />
<br />
$ getfacl ~/<br />
$ getfacl ~/.face.icon<br />
<br />
详见 [https://github.com/sddm/sddm#no-user-icon SDDM README: No User Icon]。<br />
<br />
=== 数字锁 ===<br />
<br />
如果你想强制启用数字锁,在 {{ic|[General]}} 小节设置 {{ic|1=Numlock=on}}。<br />
<br />
=== 旋转显示 ===<br />
<br />
详见 [[Xrandr#Configuration]]。<br />
<br />
=== DPI 设置 ===<br />
<br />
有时位于“显示管理器”级别设置正确的显示器 DPI 是很有用的。[https://github.com/sddm/sddm/blob/master/README.md#custom-dpi] 你需要在 {{ic|ServerArguments}} 字符串的末尾加上参数 {{ic|-dpi ''your_dpi''}} 例如:<br />
<br />
{{hc|head=/etc/sddm.conf.d/dpi.conf|output=<br />
[X11]<br />
ServerArguments=-nolisten tcp -dpi 94<br />
}}<br />
<br />
=== 启用 HiDPI ===<br />
<br />
创建 [[HiDPI (简体中文)|HiDPI]] 配置文件如下:<br />
<br />
{{hc|/etc/sddm.conf.d/hidpi.conf|2=<br />
[Wayland]<br />
EnableHiDPI=true<br />
<br />
[X11]<br />
EnableHiDPI=true<br />
}}<br />
<br />
=== 使用指纹识别器 ===<br />
<br />
{{注意|在改变设置前要确定你的指纹已经注册完成。指纹支持目前并不是完全工作正常,并且看起来在使用这种方法时仅使用密码登录将不再有效。}}<br />
<br />
SDDM 使用 [[fprint]] 以使用指纹识别。在安装了 fprint 和添加指纹签名后,在添加 {{ic|/etc/pam.d/sddm}} 的开始位置添加一行 {{ic|auth sufficient pam_fprintd.so}}。<br />
<br />
{{提示|要使其在 KDE 的锁屏模式下工作,将上面提到的一行同样添加于 {{ic|/etc/pam.d/kde}} 的开始位置。}}<br />
<br />
如果你现在在空密码区域按下回车,那么指纹识别器应该开始工作了。<br />
<br />
== 故障排除 ==<br />
<br />
=== 只有空白屏幕和光标,但没有欢迎界面 ===<br />
<br />
使用 {{ic|df -h}} 命令检查您的磁盘空间。如果没有足够的空间,欢迎界面会崩溃。<br />
<br />
如果磁盘空间足够,那么这个问题可能源于此 [https://github.com/sddm/sddm/issues/1179 bug]。切换 [[Getty#Installation|到另一个 TTY]] 来 [[restart|重启]] SDDM。<br />
<br />
=== SDDM 出现欢迎界面前的加载时间过长 ===<br />
<br />
内核熵池过小会造成长时间的 SDDM 加载过程([https://github.com/sddm/sddm/issues/1036 Bug report])。详见 [[Random number generation]] 扩大内核熵池的建议。<br />
<br />
=== 登录后挂起 ===<br />
<br />
尝试移除 {{ic|~/.Xauthority}} 文件后不重启再次登入。重启会再次创建该文件即该问题依旧存在。<br />
<br />
=== SDDM 在 tty1 启动而不是 tty7 ===<br />
<br />
SDDM 根据 [http://0pointer.de/blog/projects/serial-console.html systemd 的规定] 在 tty1 启动图形会话。如果您更喜欢老派的 tty1 到 tty6 皆预留为文本终端,更改 {{ic|MinimumVT}} 变量的默认值,其位于 {{ic|[X11]}} 小节下:<br />
<br />
{{hc|/etc/sddm.conf.d/tty.conf|2=<br />
[X11]<br />
MinimumVT=7<br />
}}<br />
<br />
=== 一个或多个用户没有出现在欢迎界面 ===<br />
<br />
{{警告|用户设置过低或过高的 {{ic|UID}} 范围应该大体上不会暴露给 [[Display manager (简体中文)]]。}}<br />
<br />
SDDM 默认会显示 UID 在 1000 到 65000 范围内的用户,如果想要显示的用户的 UID 小于这个范围,那么您就不得不更改这个范围。比如,对于 UID 为 501时,可以修改:<br />
<br />
{{hc|/etc/sddm.conf.d/uid.conf|2=<br />
[Users]<br />
HideShells=/sbin/nologin,/bin/false<br />
# Hidden users, this is if any system users fall within your range, see /etc/passwd on your system.<br />
HideUsers=git,sddm,systemd-journal-remote,systemd-journal-upload<br />
<br />
# Maximum user id for displayed users<br />
MaximumUid=65000<br />
<br />
# Minimum user id for displayed users<br />
MinimumUid=500 #My UID is 501<br />
}}<br />
<br />
=== SDDM 只加载 US 键盘布局 ===<br />
<br />
SDDM 加载的键盘布局被确定在 {{ic|/etc/X11/xorg.conf.d/00-keyboard.conf}} 文件中。您可以通过 {{ic|localectl set-x11-keymap}} 命令以生成此配置文件。详见 [[Keyboard configuration in Xorg]]。<br />
<br />
SDDM 可能也会错误地显示为 US 布局,但在您开始输入您的密码时立即切换到正确的键盘布局 [https://github.com/sddm/sddm/issues/202#issuecomment-76001543]。此 bug 看起来不是来自 SDDM,而是 {{Pkg|libxcb}} (version 1.13-1 as of 2018) [https://github.com/sddm/sddm/issues/202#issuecomment-133628462]。<br />
<br />
=== 屏幕分辨率过低 ===<br />
<br />
此问题可能源于显示屏 HiDPI 的使用破坏了 [[Wikipedia:Extended Display Identification Data|EDID]] [https://github.com/sddm/sddm/issues/692]。如果你 [[#启用 HiDPI|启动了 HiDPI]],尝试关掉它。<br />
<br />
如果上述方法失败了,您可以尝试在 Xorg 配置文件中设置您的显示尺寸:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/90-monitor.conf|2=<br />
Section "Monitor"<br />
Identifier "<default monitor>"<br />
DisplaySize 345 194 # in millimeters<br />
EndSection<br />
}}<br />
<br />
=== 自动挂载家目录的加载时间过长 ===<br />
<br />
SDDM 默认会访问 {{ic|~/.face.icon}} 文件以尝试显示用户头像。如果您的家目录采用自动挂载的文件系统(autofs),例如如果您使用 [[dm-crypt]],这将会使之等待 60 秒,直到自动挂载的文件系统(autofs)返回此目录不能被挂载。<br />
<br />
您可以通过编辑 {{ic|/etc/sddm.conf}} 文件以关闭头像功能:<br />
<br />
{{hc|/etc/sddm.conf|2=<br />
[Theme]<br />
EnableAvatars=false<br />
}}</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=SDDM_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=592793
SDDM (简体中文)
2019-12-28T03:22:35Z
<p>C0n5t4ntK: /* 配置 */ 配置小节翻译完成。</p>
<hr />
<div>[[Category:KDE (简体中文)]]<br />
[[Category:Display managers (简体中文)]]<br />
[[en:SDDM]]<br />
[[fr:SDDM]]<br />
[[ja:SDDM]]<br />
[[ru:SDDM]]<br />
{{Related articles start (简体中文)}}<br />
{{Related|Display manager}}<br />
{{Related|KDE (简体中文)}}<br />
{{Related articles end}}<br />
[https://github.com/sddm/sddm/ Simple Desktop Display Manager] (SDDM) 是 [[KDE (简体中文)]] Plasma 桌面环境推荐的 [[Display_manager_(简体中文)|显示管理器]]。<br />
<br />
[[Wikipedia:Simple Desktop Display Manager|维基百科]] 介绍:<br />
<br />
:Simple Desktop Display Manager (SDDM) 是用于 X11 和 wayland 视窗系统的显示管理器(图形登录界面)。SDDM 完全使用 C++11 编写并支持通过 QML 改变主题。对于KDE Plasma 5,KDE 选择了 SDDM 作为 KDE Display Manager 的接替者。<br />
<br />
{{注意|SDDM 还没有完全支持 Wayland 视窗系统 [https://github.com/sddm/sddm/issues/440]。Wayland 会话在支持之列,但 SDDM 运行于 X11。}}<br />
<br />
== 安装 ==<br />
<br />
[[Help:Reading (简体中文)#安装软件包|安装]] {{Pkg|sddm}} 软件包。对于 [[KDE#KCM|KDE Config Module]],可选安装 {{Pkg|sddm-kcm}} 软件包。<br />
<br />
然后根据 [[Display manager (简体中文)#加载显示管理器]] 的说明配置 SDDM 在系统引导时启动。<br />
<br />
== 配置 ==<br />
<br />
SDDM 的默认配置文件为 {{ic|/usr/lib/sddm/sddm.conf.d/default.conf}}。要修改配置,请在 {{ic|/etc/sddm.conf.d/}} 目录下创建配置文件。详见 {{man|5|sddm.conf}} 以获得所有配置选项。<br />
<br />
{{pkg|sddm-kcm}} 软件包 (包含在 {{grp|plasma}} 用户组) 提供了一个图形用户界面以在 Plasma 系统设置中配置 SDDM。[[AUR]] 中也有基于 [[Qt]] 的配置软件 {{AUR|sddm-config-editor-git}}。<br />
<br />
一切东西都应该开箱即用,自从 Arch Linux 使用 [[systemd]] 后,SDDM 默认使用 {{ic|systemd-logind}} 以进行会话管理。<br />
<br />
=== 自动登录 ===<br />
<br />
SDDM 通过它的配置文件来支持自动登录,例如:<br />
<br />
{{hc|/etc/sddm.conf.d/autologin.conf|2=<br />
[Autologin]<br />
User=john<br />
Session=plasma.desktop<br />
}}<br />
<br />
此配置使得在系统启动后自动以用户 {{ic|john}} 开启一个 KDE Plasma 会话。在 {{ic|/usr/share/xsessions/}} 目录下你可以找到可用的会话类型。<br />
<br />
目前尚不支持自动登录 KDE Plasma 的同时锁定会话 [https://github.com/sddm/sddm/issues/306]<br />
<br />
你可以添加一个脚本,在 KDE 自动启动时激活屏幕保护程序以作为一个解决方案:<br />
<br />
#!/bin/sh<br />
/usr/bin/dbus-send --session --type=method_call --dest=org.freedesktop.ScreenSaver /ScreenSaver org.freedesktop.ScreenSaver.Lock &<br />
<br />
=== 登录后自动解锁 KDE 钱包 ===<br />
<br />
详见 [[KDE Wallet (简体中文)#在登录时自动解锁 Kwallet]]。<br />
<br />
=== 主题设置 ===<br />
<br />
在 {{ic|[Theme]}} 小节更改主题设置。如果您使用 Plasma 的系统设置,主题可能会显示预览。<br />
<br />
设置 {{ic|breeze}} 以获得 Plasma 默认主题。<br />
<br />
[[AUR]] 有一些可用的主题,例如 {{AUR|archlinux-themes-sddm}}。<br />
<br />
==== 当前主题 ====<br />
<br />
通过 {{ic|Current}} 的值设置当前主题,例如 {{ic|1=Current=archlinux-simplyblack}}。<br />
<br />
==== 编辑主题 ====<br />
<br />
默认 SDDM 主题目录为 {{ic|/usr/share/sddm/themes/}}。你可以添加你的自制主题到该目录下一个单独的子目录中。注意 SDDM 要求这些子目录的名字要与主题的名字一致。可以通过研究已安装的文件来更改或创建属于你的主题。<br />
<br />
==== 测试(预览)主题 ====<br />
<br />
如果需要,你可以预览一个 SDDM 主题。如果你想知道一个主题看起来怎么样,或是想要编辑一个主题后在不必登出的情况下观察改动的效果,那么这将会非常有用。你可以运行下面的命令:<br />
<br />
$ sddm-greeter --test-mode --theme /usr/share/sddm/themes/breeze<br />
<br />
这应该为所有已连接的显示器打开一个新窗口以显示主题的预览。<br />
<br />
{{注意|这只是一个预览。在这个模式下,一些动作如关机、挂起或登录将不会执行。}}<br />
<br />
==== 鼠标光标 ====<br />
<br />
要设置鼠标光标的主题,将 {{ic|CursorTheme}} 设置成您喜欢的光标主题。<br />
<br />
合法的 [[Plasma]] 鼠标光标主题有 {{ic|breeze_cursors}},{{ic|Breeze_Snow}} 和 {{ic|breeze-dark}}。<br />
<br />
==== 用户图标(头像) ====<br />
<br />
SDDM 对于每个用户从相应的 {{ic|~/.face.icon}} 目录下读取 PNG 图片格式的用户图标(即“头像”),或者从 SDDM 配置文件中由 {{ic|FacesDir}} 为所有用户定义的共有位置。配置设置可以通过修改 {{ic|/etc/sddm.conf}} 文件被直接替换,更好的方法是创建一个位于 {{ic|/etc/sddm.conf.d/}} 下的文件来修改,例如 {{ic|/etc/sddm.conf.d/avatar.conf}}。<br />
<br />
要使用 {{ic|FacesDir}} 选项来确定头像位置,即在配置文件中 {{ic|FacesDir}} 所确定的位置为每一个用户放置一个 PNG 图片,命名如 {{ic|''username''.face.icon}}。{{ic|FacesDir}} 默认的路径为 {{ic|/usr/share/sddm/faces/}}。你可以更改默认 {{ic|FacesDir}} 目录以合乎你的要求。下面是一个例子:<br />
<br />
{{hc|/etc/sddm.conf.d/avatar.conf|2=<br />
[Theme]<br />
FacesDir=/var/lib/AccountsService/icons/<br />
}}<br />
<br />
另一个选项是放置一个名为 {{ic|.face.icon}} 的 PNG 图片到你的家目录下。在这种情况下,您不用对任何 SDDM 配置文件进行更改。不过,您仍需确定 {{ic|sddm}} 用户可以读取这些 PNG 图片作为用户图标。<br />
<br />
{{注意|在许多 KDE 的版本中,用户图标图像文件是 {{ic|~/.face}} 而 {{ic|~/.face.icon}} 是链接到图像文件的符号链接。如果用户的图标是符号链接,你需要为目标文件设置恰当的文件权限。}} <br />
<br />
为了 [[Access Control Lists#Set ACL|设置合适权限]] 运行:<br />
<br />
$ setfacl -m u:sddm:x ~/<br />
$ setfacl -m u:sddm:r ~/.face.icon<br />
<br />
你可以通过运行下列命令 [[Access Control Lists#Show ACL|检查权限]]:<br />
<br />
$ getfacl ~/<br />
$ getfacl ~/.face.icon<br />
<br />
详见 [https://github.com/sddm/sddm#no-user-icon SDDM README: No User Icon]。<br />
<br />
=== 数字锁 ===<br />
<br />
如果你想强制启用数字锁,在 {{ic|[General]}} 小节设置 {{ic|1=Numlock=on}}。<br />
<br />
=== 旋转显示 ===<br />
<br />
详见 [[Xrandr#Configuration]]。<br />
<br />
=== DPI 设置 ===<br />
<br />
有时位于“显示管理器”级别设置正确的显示器 DPI 是很有用的。[https://github.com/sddm/sddm/blob/master/README.md#custom-dpi] 你需要在 {{ic|ServerArguments}} 字符串的末尾加上参数 {{ic|-dpi ''your_dpi''}} 例如:<br />
<br />
{{hc|head=/etc/sddm.conf.d/dpi.conf|output=<br />
[X11]<br />
ServerArguments=-nolisten tcp -dpi 94<br />
}}<br />
<br />
=== 启用 HiDPI ===<br />
<br />
创建 [[HiDPI (简体中文)|HiDPI]] 配置文件如下:<br />
<br />
{{hc|/etc/sddm.conf.d/hidpi.conf|2=<br />
[Wayland]<br />
EnableHiDPI=true<br />
<br />
[X11]<br />
EnableHiDPI=true<br />
}}<br />
<br />
=== 使用指纹识别器 ===<br />
<br />
{{注意|在改变设置前要确定你的指纹已经注册完成。指纹支持目前并不是完全工作正常,并且看起来在使用这种方法时仅使用密码登录将不再有效。}}<br />
<br />
SDDM 使用 [[fprint]] 以使用指纹识别。在安装了 fprint 和添加指纹签名后,在添加 {{ic|/etc/pam.d/sddm}} 的开始位置添加一行 {{ic|auth sufficient pam_fprintd.so}}。<br />
<br />
{{提示|要使其在 KDE 的锁屏模式下工作,将上面提到的一行同样添加于 {{ic|/etc/pam.d/kde}} 的开始位置。}}<br />
<br />
如果你现在在空密码区域按下回车,那么指纹识别器应该开始工作了。<br />
<br />
== Troubleshooting ==<br />
<br />
=== Blank screen with cursor, but no greeter shows ===<br />
<br />
Check your disk space with {{ic|df -h}}. If no available space, greeter will crash.<br />
<br />
If disk space is not the issue, it may be due to [https://github.com/sddm/sddm/issues/1179 a bug.] Switch [[Getty#Installation|to another TTY]] to [[restart]] SDDM.<br />
<br />
=== Long load time before SDDM shows the greeter ===<br />
<br />
A low entropy pool can cause long SDDM load time ([https://github.com/sddm/sddm/issues/1036 Bug report]). See [[Random number generation]] for suggestions to increase the entropy pool.<br />
<br />
=== Hangs after login ===<br />
<br />
Try removing {{ic|~/.Xauthority}} and logging in again without rebooting. Rebooting without logging in creates the file again and the problem will persist.<br />
<br />
=== SDDM starts on tty1 instead of tty7 ===<br />
<br />
SDDM follows the [http://0pointer.de/blog/projects/serial-console.html systemd convention] of starting the first graphical session on tty1. If you prefer the old convention where tty1 through tty6 are reserved for text consoles, change the default value of {{ic|MinimumVT}} variable, which comes under the {{ic|[X11]}} section:<br />
<br />
{{hc|/etc/sddm.conf.d/tty.conf|2=<br />
[X11]<br />
MinimumVT=7<br />
}}<br />
<br />
=== One or more users do not show up on the greeter ===<br />
<br />
{{Warning|Users set with a lower or higher {{ic|UID}} range should generally not be exposed to a [[Display manager]].}}<br />
<br />
SDDM only displays users with a UID in the range of 1000 to 65000 by default, if the UIDs of the desired users are below this value then you will have to modify this range. For example, for a UID of 501, say:<br />
<br />
{{hc|/etc/sddm.conf.d/uid.conf|2=<br />
[Users]<br />
HideShells=/sbin/nologin,/bin/false<br />
# Hidden users, this is if any system users fall within your range, see /etc/passwd on your system.<br />
HideUsers=git,sddm,systemd-journal-remote,systemd-journal-upload<br />
<br />
# Maximum user id for displayed users<br />
MaximumUid=65000<br />
<br />
# Minimum user id for displayed users<br />
MinimumUid=500 #My UID is 501<br />
}}<br />
<br />
=== SDDM loads only US keyboard layout ===<br />
<br />
SDDM loads the keyboard layout specified in {{ic|/etc/X11/xorg.conf.d/00-keyboard.conf}}. You can generate this configuration file by {{ic|localectl set-x11-keymap}} command. See [[Keyboard configuration in Xorg]] for more information.<br />
<br />
SDDM may also incorrectly display the layout as US but will immediately change to the correct layout after you start typing your password [https://github.com/sddm/sddm/issues/202#issuecomment-76001543]. This seems to not be a bug in SDDM but in {{Pkg|libxcb}} (version 1.13-1 as of 2018) [https://github.com/sddm/sddm/issues/202#issuecomment-133628462].<br />
<br />
=== Screen resolution is too low ===<br />
<br />
Issue may be caused by HiDPI usage for monitors with corrupted [[Wikipedia:Extended Display Identification Data|EDID]] [https://github.com/sddm/sddm/issues/692]. If you have [[#Enable HiDPI|enabled HiDPI]], try to disable it.<br />
<br />
If even the above fails, you can try setting your screen size in a Xorg configuration file:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/90-monitor.conf|2=<br />
Section "Monitor"<br />
Identifier "<default monitor>"<br />
DisplaySize 345 194 # in millimeters<br />
EndSection<br />
}}<br />
<br />
=== Long load time on autofs home directory ===<br />
<br />
SDDM by default tries to display avatars of users by accessing {{ic|~/.face.icon}} file. If your home directory is an ''autofs'', for example if you use [[dm-crypt]], this will make it wait for 60 seconds, until autofs reports that the directory cannot be mounted.<br />
<br />
You can disable avatars by editing {{ic|/etc/sddm.conf}}:<br />
<br />
{{hc|/etc/sddm.conf|2=<br />
[Theme]<br />
EnableAvatars=false<br />
}}</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=SDDM_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=592703
SDDM (简体中文)
2019-12-27T03:47:38Z
<p>C0n5t4ntK: /* 编辑主题 */ 该小节前已翻译完成。</p>
<hr />
<div>[[Category:KDE (简体中文)]]<br />
[[Category:Display managers (简体中文)]]<br />
[[en:SDDM]]<br />
[[fr:SDDM]]<br />
[[ja:SDDM]]<br />
[[ru:SDDM]]<br />
{{Related articles start (简体中文)}}<br />
{{Related|Display manager}}<br />
{{Related|KDE (简体中文)}}<br />
{{Related articles end}}<br />
[https://github.com/sddm/sddm/ Simple Desktop Display Manager] (SDDM) 是 [[KDE (简体中文)]] Plasma 桌面环境推荐的 [[Display_manager_(简体中文)|显示管理器]]。<br />
<br />
[[Wikipedia:Simple Desktop Display Manager|维基百科]] 介绍:<br />
<br />
:Simple Desktop Display Manager (SDDM) 是用于 X11 和 wayland 视窗系统的显示管理器(图形登录界面)。SDDM 完全使用 C++11 编写并支持通过 QML 改变主题。对于KDE Plasma 5,KDE 选择了 SDDM 作为 KDE Display Manager 的接替者。<br />
<br />
{{注意|SDDM 还没有完全支持 Wayland 视窗系统 [https://github.com/sddm/sddm/issues/440]。Wayland 会话在支持之列,但 SDDM 运行于 X11。}}<br />
<br />
== 安装 ==<br />
<br />
[[Help:Reading (简体中文)#安装软件包|安装]] {{Pkg|sddm}} 软件包。对于 [[KDE#KCM|KDE Config Module]],可选安装 {{Pkg|sddm-kcm}} 软件包。<br />
<br />
然后根据 [[Display manager (简体中文)#加载显示管理器]] 的说明配置 SDDM 在系统引导时启动。<br />
<br />
== 配置 ==<br />
<br />
SDDM 的默认配置文件为 {{ic|/usr/lib/sddm/sddm.conf.d/default.conf}}。要修改配置,请在 {{ic|/etc/sddm.conf.d/}} 目录下创建配置文件。详见 {{man|5|sddm.conf}} 以获得所有配置选项。<br />
<br />
{{pkg|sddm-kcm}} 软件包 (包含在 {{grp|plasma}} 用户组) 提供了一个图形用户界面以在 Plasma 系统设置中配置 SDDM。[[AUR]] 中也有基于 [[Qt]] 的配置软件 {{AUR|sddm-config-editor-git}}。<br />
<br />
一切东西都应该开箱即用,自从 Arch Linux 使用 [[systemd]] 后,SDDM 默认使用 {{ic|systemd-logind}} 以进行会话管理。<br />
<br />
=== 自动登录 ===<br />
<br />
SDDM 通过它的配置文件来支持自动登录,例如:<br />
<br />
{{hc|/etc/sddm.conf.d/autologin.conf|2=<br />
[Autologin]<br />
User=john<br />
Session=plasma.desktop<br />
}}<br />
<br />
此配置使得在系统启动后自动以用户 {{ic|john}} 开启一个 KDE Plasma 会话。在 {{ic|/usr/share/xsessions/}} 目录下你可以找到可用的会话类型。<br />
<br />
目前尚不支持自动登录 KDE Plasma 的同时锁定会话 [https://github.com/sddm/sddm/issues/306]<br />
<br />
你可以添加一个脚本,在 KDE 自动启动时激活屏幕保护程序以作为一个解决方案:<br />
<br />
#!/bin/sh<br />
/usr/bin/dbus-send --session --type=method_call --dest=org.freedesktop.ScreenSaver /ScreenSaver org.freedesktop.ScreenSaver.Lock &<br />
<br />
=== 登录后自动解锁 KDE 钱包 ===<br />
<br />
详见 [[KDE Wallet (简体中文)#在登录时自动解锁 Kwallet]]。<br />
<br />
=== 主题设置 ===<br />
<br />
在 {{ic|[Theme]}} 小节更改主题设置。如果您使用 Plasma 的系统设置,主题可能会显示预览。<br />
<br />
设置 {{ic|breeze}} 以获得 Plasma 默认主题。<br />
<br />
[[AUR]] 有一些可用的主题,例如 {{AUR|archlinux-themes-sddm}}。<br />
<br />
==== 当前主题 ====<br />
<br />
通过 {{ic|Current}} 的值设置当前主题,例如 {{ic|1=Current=archlinux-simplyblack}}。<br />
<br />
==== 编辑主题 ====<br />
<br />
默认 SDDM 主题目录为 {{ic|/usr/share/sddm/themes/}}。你可以添加你的自制主题到该目录下一个单独的子目录中。注意 SDDM 要求这些子目录的名字要与主题的名字一致。可以通过研究已安装的文件来更改或创建属于你的主题。<br />
<br />
==== Testing (previewing) a theme ====<br />
<br />
You can preview an SDDM theme if needed. This is especially helpful if you are not sure how the theme would look if selected or just edited a theme and want to see how it would look without logging out. You can run something like this:<br />
<br />
$ sddm-greeter --test-mode --theme /usr/share/sddm/themes/breeze<br />
<br />
This should open a new window for every monitor you have connected and show a preview of the theme.<br />
<br />
{{Note|This is just a preview. In this mode, some actions like shutdown, suspend or login will have no effect.}}<br />
<br />
==== Mouse cursor ====<br />
<br />
To set the mouse cursor theme, set {{ic|CursorTheme}} to your preferred cursor theme.<br />
<br />
Valid [[Plasma]] mouse cursor theme names are {{ic|breeze_cursors}}, {{ic|Breeze_Snow}} and {{ic|breeze-dark}}.<br />
<br />
==== User icon (avatar) ====<br />
<br />
SDDM reads the user icon (a.k.a. "avatar") as a PNG image from either {{ic|~/.face.icon}} for each user, or the common location for all users specified by {{ic|FacesDir}} in an SDDM configuration file. The configuration setting can be placed in either {{ic|/etc/sddm.conf}} directly, or, better, a file under {{ic|/etc/sddm.conf.d/}} such as {{ic|/etc/sddm.conf.d/avatar.conf}}.<br />
<br />
To use the {{ic|FacesDir}} location option, place a PNG image for each user named as {{ic|''username''.face.icon}} into location specified in for {{ic|FacesDir}} in the configuration file. The default location for {{ic|FacesDir}} is {{ic|/usr/share/sddm/faces/}}. You can change the default {{ic|FacesDir}} location to match your requirements. Here is an example:<br />
<br />
{{hc|/etc/sddm.conf.d/avatar.conf|2=<br />
[Theme]<br />
FacesDir=/var/lib/AccountsService/icons/<br />
}}<br />
<br />
The other option is to put a PNG image named {{ic|.face.icon}} at the root of your home directory. In this case, no changes to any SDDM configuration file is required. However, you need to make sure that {{ic|sddm}} user can read the PNG image file(s) for the user icon(s).<br />
<br />
{{Note|In many KDE versions, the user icon image file is {{ic|~/.face}} and {{ic|~/.face.icon}} is a symlink to that file. If the user icon images are symlinks, you need to set proper file permissions to the target files.}} <br />
<br />
To [[Access Control Lists#Set ACL|set proper permissions]] run:<br />
<br />
$ setfacl -m u:sddm:x ~/<br />
$ setfacl -m u:sddm:r ~/.face.icon<br />
<br />
You can [[Access Control Lists#Show ACL|check permissions]] with:<br />
<br />
$ getfacl ~/<br />
$ getfacl ~/.face.icon<br />
<br />
See [https://github.com/sddm/sddm#no-user-icon SDDM README: No User Icon].<br />
<br />
=== Numlock ===<br />
<br />
If you want to enforce Numlock to be enabled, set {{ic|1=Numlock=on}} in the {{ic|[General]}} section.<br />
<br />
=== Rotate display ===<br />
<br />
See [[Xrandr#Configuration]].<br />
<br />
=== DPI settings ===<br />
<br />
Sometimes it is useful to set up the correct monitor's PPI settings on a "Display Manager" level.[https://github.com/sddm/sddm/blob/master/README.md#custom-dpi] To do so you need to add to {{ic|ServerArguments}} the parameter {{ic|-dpi ''your_dpi''}} at the end of the string. For example:<br />
<br />
{{hc|head=/etc/sddm.conf.d/dpi.conf|output=<br />
[X11]<br />
ServerArguments=-nolisten tcp -dpi 94<br />
}}<br />
<br />
=== Enable HiDPI ===<br />
<br />
Create the following file:<br />
<br />
{{hc|/etc/sddm.conf.d/hidpi.conf|2=<br />
[Wayland]<br />
EnableHiDPI=true<br />
<br />
[X11]<br />
EnableHiDPI=true<br />
}}<br />
<br />
=== Using a fingerprint reader ===<br />
<br />
{{Note|Make sure that your fingerprint is registered before making these changes. Fingerprint support is not completely working properly yet, and it seems logging in with only a password no longer works using this method.}}<br />
<br />
SDDM works with a fingerprint reader when using [[fprint]]. After installing fprint and adding fingerprint signatures, add the line {{ic|auth sufficient pam_fprintd.so}} at the beginning of {{ic|/etc/pam.d/sddm}}.<br />
<br />
{{Tip|To make it work in KDE's lock screen, also add the same line at the beginning of {{ic|/etc/pam.d/kde}}.}}<br />
<br />
If you now press enter in the empty password field, the fingerprint reader should start working.<br />
<br />
== Troubleshooting ==<br />
<br />
=== Blank screen with cursor, but no greeter shows ===<br />
<br />
Check your disk space with {{ic|df -h}}. If no available space, greeter will crash.<br />
<br />
If disk space is not the issue, it may be due to [https://github.com/sddm/sddm/issues/1179 a bug.] Switch [[Getty#Installation|to another TTY]] to [[restart]] SDDM.<br />
<br />
=== Long load time before SDDM shows the greeter ===<br />
<br />
A low entropy pool can cause long SDDM load time ([https://github.com/sddm/sddm/issues/1036 Bug report]). See [[Random number generation]] for suggestions to increase the entropy pool.<br />
<br />
=== Hangs after login ===<br />
<br />
Try removing {{ic|~/.Xauthority}} and logging in again without rebooting. Rebooting without logging in creates the file again and the problem will persist.<br />
<br />
=== SDDM starts on tty1 instead of tty7 ===<br />
<br />
SDDM follows the [http://0pointer.de/blog/projects/serial-console.html systemd convention] of starting the first graphical session on tty1. If you prefer the old convention where tty1 through tty6 are reserved for text consoles, change the default value of {{ic|MinimumVT}} variable, which comes under the {{ic|[X11]}} section:<br />
<br />
{{hc|/etc/sddm.conf.d/tty.conf|2=<br />
[X11]<br />
MinimumVT=7<br />
}}<br />
<br />
=== One or more users do not show up on the greeter ===<br />
<br />
{{Warning|Users set with a lower or higher {{ic|UID}} range should generally not be exposed to a [[Display manager]].}}<br />
<br />
SDDM only displays users with a UID in the range of 1000 to 65000 by default, if the UIDs of the desired users are below this value then you will have to modify this range. For example, for a UID of 501, say:<br />
<br />
{{hc|/etc/sddm.conf.d/uid.conf|2=<br />
[Users]<br />
HideShells=/sbin/nologin,/bin/false<br />
# Hidden users, this is if any system users fall within your range, see /etc/passwd on your system.<br />
HideUsers=git,sddm,systemd-journal-remote,systemd-journal-upload<br />
<br />
# Maximum user id for displayed users<br />
MaximumUid=65000<br />
<br />
# Minimum user id for displayed users<br />
MinimumUid=500 #My UID is 501<br />
}}<br />
<br />
=== SDDM loads only US keyboard layout ===<br />
<br />
SDDM loads the keyboard layout specified in {{ic|/etc/X11/xorg.conf.d/00-keyboard.conf}}. You can generate this configuration file by {{ic|localectl set-x11-keymap}} command. See [[Keyboard configuration in Xorg]] for more information.<br />
<br />
SDDM may also incorrectly display the layout as US but will immediately change to the correct layout after you start typing your password [https://github.com/sddm/sddm/issues/202#issuecomment-76001543]. This seems to not be a bug in SDDM but in {{Pkg|libxcb}} (version 1.13-1 as of 2018) [https://github.com/sddm/sddm/issues/202#issuecomment-133628462].<br />
<br />
=== Screen resolution is too low ===<br />
<br />
Issue may be caused by HiDPI usage for monitors with corrupted [[Wikipedia:Extended Display Identification Data|EDID]] [https://github.com/sddm/sddm/issues/692]. If you have [[#Enable HiDPI|enabled HiDPI]], try to disable it.<br />
<br />
If even the above fails, you can try setting your screen size in a Xorg configuration file:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/90-monitor.conf|2=<br />
Section "Monitor"<br />
Identifier "<default monitor>"<br />
DisplaySize 345 194 # in millimeters<br />
EndSection<br />
}}<br />
<br />
=== Long load time on autofs home directory ===<br />
<br />
SDDM by default tries to display avatars of users by accessing {{ic|~/.face.icon}} file. If your home directory is an ''autofs'', for example if you use [[dm-crypt]], this will make it wait for 60 seconds, until autofs reports that the directory cannot be mounted.<br />
<br />
You can disable avatars by editing {{ic|/etc/sddm.conf}}:<br />
<br />
{{hc|/etc/sddm.conf|2=<br />
[Theme]<br />
EnableAvatars=false<br />
}}</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=SDDM_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=592700
SDDM (简体中文)
2019-12-27T01:52:12Z
<p>C0n5t4ntK: 中文内容已脱节,且文字总量不大,故以英文版内容全部覆盖后重新翻译。</p>
<hr />
<div>[[Category:KDE (简体中文)]]<br />
[[Category:Display managers (简体中文)]]<br />
[[en:SDDM]]<br />
[[fr:SDDM]]<br />
[[ja:SDDM]]<br />
[[ru:SDDM]]<br />
{{Related articles start (简体中文)}}<br />
{{Related|Display manager}}<br />
{{Related|KDE (简体中文)}}<br />
{{Related articles end}}<br />
[https://github.com/sddm/sddm/ Simple Desktop Display Manager] (SDDM) is the preferred [[display manager]] for [[KDE]] Plasma desktop. <br />
<br />
From [[Wikipedia:Simple Desktop Display Manager]]:<br />
<br />
:Simple Desktop Display Manager (SDDM) is a display manager (a graphical login program) for X11 and Wayland windowing systems. SDDM was written from scratch in C++11 and supports theming via QML. KDE chose SDDM to be the successor of the KDE Display Manager for KDE Plasma 5.<br />
<br />
{{Note|The Wayland windowing system is not yet fully supported [https://github.com/sddm/sddm/issues/440]. Wayland sessions are listed, but SDDM runs on X11.}}<br />
<br />
== Installation ==<br />
<br />
[[Install]] the {{Pkg|sddm}} package. Optionally install {{Pkg|sddm-kcm}} for the [[KDE#KCM|KDE Config Module]].<br />
<br />
Follow [[Display manager#Loading the display manager]] to start SDDM at boot.<br />
<br />
== Configuration ==<br />
<br />
The default configuration file for SDDM can be found at {{ic|/usr/lib/sddm/sddm.conf.d/default.conf}}. For any changes, create configuration file(s) in {{ic|/etc/sddm.conf.d/}}. See {{man|5|sddm.conf}} for all options.<br />
<br />
The {{pkg|sddm-kcm}} package (included in the {{grp|plasma}} group) provides a GUI to configure SDDM in Plasma's system settings. There is also a [[Qt]]-based {{AUR|sddm-config-editor-git}} available in the [[AUR]].<br />
<br />
Everything should work out of the box, since Arch Linux uses [[systemd]] and SDDM defaults to using {{ic|systemd-logind}} for session management.<br />
<br />
=== Autologin ===<br />
<br />
SDDM supports automatic login through its configuration file, for example:<br />
<br />
{{hc|/etc/sddm.conf.d/autologin.conf|2=<br />
[Autologin]<br />
User=john<br />
Session=plasma.desktop<br />
}}<br />
<br />
This configuration causes a KDE Plasma session to be started for user {{ic|john}} when the system is booted. Available session types can be found in {{ic|/usr/share/xsessions/}} directory.<br />
<br />
An option to autologin into KDE Plasma while simultaneously locking the session is not available [https://github.com/sddm/sddm/issues/306]<br />
<br />
You can add a script that activates the screensaver of KDE to the autostart as a workaround:<br />
<br />
#!/bin/sh<br />
/usr/bin/dbus-send --session --type=method_call --dest=org.freedesktop.ScreenSaver /ScreenSaver org.freedesktop.ScreenSaver.Lock &<br />
<br />
=== Unlock KDE Wallet automatically on login ===<br />
<br />
See [[KDE Wallet#Unlock KDE Wallet automatically on login]].<br />
<br />
=== Theme settings ===<br />
<br />
Theme settings can be changed in the {{ic|[Theme]}} section. If you use Plasma's system settings, themes may show previews.<br />
<br />
Set to {{ic|breeze}} for the default Plasma theme.<br />
<br />
Some themes are available in the [[AUR]], for example {{AUR|archlinux-themes-sddm}}.<br />
<br />
==== Current theme ====<br />
<br />
Set the current theme through the {{ic|Current}} value, e.g. {{ic|1=Current=archlinux-simplyblack}}.<br />
<br />
==== Editing themes ====<br />
<br />
The default SDDM theme directory is {{ic|/usr/share/sddm/themes/}}. You can add your custom made themes to that directory under a separate subdirectory. Note that SDDM requires these subdirectory names to be the same as the theme names. Study the files installed to modify or create your own theme.<br />
<br />
==== Testing (previewing) a theme ====<br />
<br />
You can preview an SDDM theme if needed. This is especially helpful if you are not sure how the theme would look if selected or just edited a theme and want to see how it would look without logging out. You can run something like this:<br />
<br />
$ sddm-greeter --test-mode --theme /usr/share/sddm/themes/breeze<br />
<br />
This should open a new window for every monitor you have connected and show a preview of the theme.<br />
<br />
{{Note|This is just a preview. In this mode, some actions like shutdown, suspend or login will have no effect.}}<br />
<br />
==== Mouse cursor ====<br />
<br />
To set the mouse cursor theme, set {{ic|CursorTheme}} to your preferred cursor theme.<br />
<br />
Valid [[Plasma]] mouse cursor theme names are {{ic|breeze_cursors}}, {{ic|Breeze_Snow}} and {{ic|breeze-dark}}.<br />
<br />
==== User icon (avatar) ====<br />
<br />
SDDM reads the user icon (a.k.a. "avatar") as a PNG image from either {{ic|~/.face.icon}} for each user, or the common location for all users specified by {{ic|FacesDir}} in an SDDM configuration file. The configuration setting can be placed in either {{ic|/etc/sddm.conf}} directly, or, better, a file under {{ic|/etc/sddm.conf.d/}} such as {{ic|/etc/sddm.conf.d/avatar.conf}}.<br />
<br />
To use the {{ic|FacesDir}} location option, place a PNG image for each user named as {{ic|''username''.face.icon}} into location specified in for {{ic|FacesDir}} in the configuration file. The default location for {{ic|FacesDir}} is {{ic|/usr/share/sddm/faces/}}. You can change the default {{ic|FacesDir}} location to match your requirements. Here is an example:<br />
<br />
{{hc|/etc/sddm.conf.d/avatar.conf|2=<br />
[Theme]<br />
FacesDir=/var/lib/AccountsService/icons/<br />
}}<br />
<br />
The other option is to put a PNG image named {{ic|.face.icon}} at the root of your home directory. In this case, no changes to any SDDM configuration file is required. However, you need to make sure that {{ic|sddm}} user can read the PNG image file(s) for the user icon(s).<br />
<br />
{{Note|In many KDE versions, the user icon image file is {{ic|~/.face}} and {{ic|~/.face.icon}} is a symlink to that file. If the user icon images are symlinks, you need to set proper file permissions to the target files.}} <br />
<br />
To [[Access Control Lists#Set ACL|set proper permissions]] run:<br />
<br />
$ setfacl -m u:sddm:x ~/<br />
$ setfacl -m u:sddm:r ~/.face.icon<br />
<br />
You can [[Access Control Lists#Show ACL|check permissions]] with:<br />
<br />
$ getfacl ~/<br />
$ getfacl ~/.face.icon<br />
<br />
See [https://github.com/sddm/sddm#no-user-icon SDDM README: No User Icon].<br />
<br />
=== Numlock ===<br />
<br />
If you want to enforce Numlock to be enabled, set {{ic|1=Numlock=on}} in the {{ic|[General]}} section.<br />
<br />
=== Rotate display ===<br />
<br />
See [[Xrandr#Configuration]].<br />
<br />
=== DPI settings ===<br />
<br />
Sometimes it is useful to set up the correct monitor's PPI settings on a "Display Manager" level.[https://github.com/sddm/sddm/blob/master/README.md#custom-dpi] To do so you need to add to {{ic|ServerArguments}} the parameter {{ic|-dpi ''your_dpi''}} at the end of the string. For example:<br />
<br />
{{hc|head=/etc/sddm.conf.d/dpi.conf|output=<br />
[X11]<br />
ServerArguments=-nolisten tcp -dpi 94<br />
}}<br />
<br />
=== Enable HiDPI ===<br />
<br />
Create the following file:<br />
<br />
{{hc|/etc/sddm.conf.d/hidpi.conf|2=<br />
[Wayland]<br />
EnableHiDPI=true<br />
<br />
[X11]<br />
EnableHiDPI=true<br />
}}<br />
<br />
=== Using a fingerprint reader ===<br />
<br />
{{Note|Make sure that your fingerprint is registered before making these changes. Fingerprint support is not completely working properly yet, and it seems logging in with only a password no longer works using this method.}}<br />
<br />
SDDM works with a fingerprint reader when using [[fprint]]. After installing fprint and adding fingerprint signatures, add the line {{ic|auth sufficient pam_fprintd.so}} at the beginning of {{ic|/etc/pam.d/sddm}}.<br />
<br />
{{Tip|To make it work in KDE's lock screen, also add the same line at the beginning of {{ic|/etc/pam.d/kde}}.}}<br />
<br />
If you now press enter in the empty password field, the fingerprint reader should start working.<br />
<br />
== Troubleshooting ==<br />
<br />
=== Blank screen with cursor, but no greeter shows ===<br />
<br />
Check your disk space with {{ic|df -h}}. If no available space, greeter will crash.<br />
<br />
If disk space is not the issue, it may be due to [https://github.com/sddm/sddm/issues/1179 a bug.] Switch [[Getty#Installation|to another TTY]] to [[restart]] SDDM.<br />
<br />
=== Long load time before SDDM shows the greeter ===<br />
<br />
A low entropy pool can cause long SDDM load time ([https://github.com/sddm/sddm/issues/1036 Bug report]). See [[Random number generation]] for suggestions to increase the entropy pool.<br />
<br />
=== Hangs after login ===<br />
<br />
Try removing {{ic|~/.Xauthority}} and logging in again without rebooting. Rebooting without logging in creates the file again and the problem will persist.<br />
<br />
=== SDDM starts on tty1 instead of tty7 ===<br />
<br />
SDDM follows the [http://0pointer.de/blog/projects/serial-console.html systemd convention] of starting the first graphical session on tty1. If you prefer the old convention where tty1 through tty6 are reserved for text consoles, change the default value of {{ic|MinimumVT}} variable, which comes under the {{ic|[X11]}} section:<br />
<br />
{{hc|/etc/sddm.conf.d/tty.conf|2=<br />
[X11]<br />
MinimumVT=7<br />
}}<br />
<br />
=== One or more users do not show up on the greeter ===<br />
<br />
{{Warning|Users set with a lower or higher {{ic|UID}} range should generally not be exposed to a [[Display manager]].}}<br />
<br />
SDDM only displays users with a UID in the range of 1000 to 65000 by default, if the UIDs of the desired users are below this value then you will have to modify this range. For example, for a UID of 501, say:<br />
<br />
{{hc|/etc/sddm.conf.d/uid.conf|2=<br />
[Users]<br />
HideShells=/sbin/nologin,/bin/false<br />
# Hidden users, this is if any system users fall within your range, see /etc/passwd on your system.<br />
HideUsers=git,sddm,systemd-journal-remote,systemd-journal-upload<br />
<br />
# Maximum user id for displayed users<br />
MaximumUid=65000<br />
<br />
# Minimum user id for displayed users<br />
MinimumUid=500 #My UID is 501<br />
}}<br />
<br />
=== SDDM loads only US keyboard layout ===<br />
<br />
SDDM loads the keyboard layout specified in {{ic|/etc/X11/xorg.conf.d/00-keyboard.conf}}. You can generate this configuration file by {{ic|localectl set-x11-keymap}} command. See [[Keyboard configuration in Xorg]] for more information.<br />
<br />
SDDM may also incorrectly display the layout as US but will immediately change to the correct layout after you start typing your password [https://github.com/sddm/sddm/issues/202#issuecomment-76001543]. This seems to not be a bug in SDDM but in {{Pkg|libxcb}} (version 1.13-1 as of 2018) [https://github.com/sddm/sddm/issues/202#issuecomment-133628462].<br />
<br />
=== Screen resolution is too low ===<br />
<br />
Issue may be caused by HiDPI usage for monitors with corrupted [[Wikipedia:Extended Display Identification Data|EDID]] [https://github.com/sddm/sddm/issues/692]. If you have [[#Enable HiDPI|enabled HiDPI]], try to disable it.<br />
<br />
If even the above fails, you can try setting your screen size in a Xorg configuration file:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/90-monitor.conf|2=<br />
Section "Monitor"<br />
Identifier "<default monitor>"<br />
DisplaySize 345 194 # in millimeters<br />
EndSection<br />
}}<br />
<br />
=== Long load time on autofs home directory ===<br />
<br />
SDDM by default tries to display avatars of users by accessing {{ic|~/.face.icon}} file. If your home directory is an ''autofs'', for example if you use [[dm-crypt]], this will make it wait for 60 seconds, until autofs reports that the directory cannot be mounted.<br />
<br />
You can disable avatars by editing {{ic|/etc/sddm.conf}}:<br />
<br />
{{hc|/etc/sddm.conf|2=<br />
[Theme]<br />
EnableAvatars=false<br />
}}</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=ArchWiki:Translation_Team_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=592366
ArchWiki:Translation Team (简体中文)
2019-12-22T10:40:34Z
<p>C0n5t4ntK: /* 页面维护列表 */ 认领页面</p>
<hr />
<div>[[Category:简体中文]]<br />
[[Category:ArchWiki (简体中文)]]<br />
[[ar:ArchWiki Translation Team]]<br />
[[cs:ArchWiki Translation Team]]<br />
[[el:ArchWiki Translation Team]]<br />
[[en:ArchWiki:Translation Team]]<br />
[[es:ArchWiki:Translation Team]]<br />
[[fr:ArchWiki Translation Team]]<br />
[[hr:ArchWiki Translation Team]]<br />
[[it:ArchWiki Translation Team]]<br />
[[ja:ArchWiki 翻訳チーム]]<br />
[[ko:ArchWiki Translation Team]]<br />
[[nl:ArchWiki Translation Team]]<br />
[[pl:ArchWiki Translation Team]]<br />
[[pt:ArchWiki:Translation Team]]<br />
[[ru:ArchWiki Translation Team]]<br />
[[sk:ArchWiki Translation Team]]<br />
[[zh-hant:ArchWiki:Translation Team]]<br />
Arch Wiki 上有许多中文页面,这其中大部分是从外文翻译过来的,这些页面是无数中文志愿者劳动的结晶。随着时间推移,有些页面因为没有及时维护,内容严重过时。而目前的翻译工作缺少组织,效率偏低。所以参照西班牙和意大利翻译组的做法,添加这个页面。<br />
<br />
如果你希望对Arch Wiki做贡献,参与Wiki建设,比如翻译英文页面和对已翻译过的中文页面进行维护,只需要编辑下面的[[#页面维护列表]],添加相应的条目,并将自己加为相关页面的维护者。如果你在列表中还没有找到想要翻译的页面,可以自行添加。另外,如果因为时间原因无法再维护页面,请及时将自己从维护者列表中删除。<br />
<br />
== 创建翻译 ==<br />
{{警告|如果不准备翻译页面的大部分内容,请尽量不要新建简体中文页面。检查英文页面的更新需要花费不少精力,没有翻译的页面会增加维护负担。}}<br />
# 如果还不知道如何编辑 wiki,请阅读 [[Help:Editing (简体中文)|编辑帮助]]。<br />
# 阅读 [[Help:i18n (简体中文)|i18n帮助]],文章给出了 ArchWiki 国际化和本地化的指南。<br />
# [[Special:UserLogin|登录]] 以进行编辑。<br />
# 选择要翻译的页面,例如从 [[Special:Random|随机页面]] 或[[#页面维护列表|页面维护列表]] 中选择一个未翻译完成的页面。假设要翻译 [[Some Page]].<br />
# 进入选择的英文页面,点击页面顶部的 '''编辑'''。<br />
# 添加要翻译文件的语言间链接, 简体中文的话加入<nowiki>[[zh-hans:Some Page]]</nowiki>,其它语言参见[[Help:i18n#Interlanguage links]])。<br />
# 复制所有页面代码。<br />
# 保存页面 (新加了语言链接)<br />
# 访问页面左边新添加的语言链接,应该会进到 [[Some Page (简体中文)]] : {{ic|<nowiki>https://wiki.archlinux.org/index.php/Some_Page_(</nowiki>''简体中文'')}}<br />
# 因为页面不存在,点击 '''创建'''。<br />
# 将显示一个编辑器 - 粘贴复制的英文页面。<br />
# 将文章分类修改为本地化版本,例如将 {{ic|<nowiki>[[Category:Internationalization]]</nowiki>}} 修改为 {{ic|<nowiki>[[Category:Internationalization (简体中文)]]</nowiki>}},参阅[[Help:Category (简体中文)]].<br />
# 修改语言间链接,指向英文页面(将 {{ic|zh-hans}} 修改为 {{ic|en}},并将英文页面移到文章顶部。<br />
# 翻译页面,进行保存。<br />
# (推荐)给翻译完成的页面加上[[Template:TranslationStatus (简体中文)|翻译状态]],后有详细介绍。<br />
# 更新所有其它语言页面,加入刚翻译文章的语言间链接。<br />
# (可选)创建一个简体中文名称的页面,指向新创建的页面:访问 {{ic|<nowiki>https://wiki.archlinux.org/index.php/</nowiki>''页面的中文名称''}}.<br />
# (可选)建立新页面,并加入:{{bc|<nowiki>#REDIRECT [[Some Page (简体中文)</nowiki>]]}}<br />
<br />
== Templates ==<br />
<br />
{{Translateme (简体中文)|Not translated}}<br />
<br />
The following table lists the [[Help:Template (简体中文)|templates]] that should be translated and their Simplified Chinese equivalent.<br />
<br />
{| class=wikitable<br />
! English template || Simplified Chinese version<br />
|-<br />
! colspan=2| Article templates<br />
|-<br />
| [[Template:Related articles start]] || [[Template:Related articles start (简体中文)]]<br />
|-<br />
| [[Template:Yes]] || [[Template:是]]<br />
|-<br />
| [[Template:No]] || [[Template:否]]<br />
|-<br />
| [[Template:Tip]] || [[Template:提示]]<br />
|-<br />
| [[Template:Note]] || [[Template:注意]]<br />
|-<br />
| [[Template:Warning]] || [[Template:警告]]<br />
|-<br />
| [[Template:Dead link]] || [[Template:失效链接]]<br />
|-<br />
| [[Template:Broken package link]] || {{-}}<br />
|-<br />
! colspan=2| Translation status templates<br />
|-<br />
| [[Template:Bad translation]] || {{-}}<br />
|-<br />
| [[Template:Translateme]] || [[Template:Translateme (简体中文)]]<br />
|-<br />
| [[Template:TranslationStatus]] || [[Template:TranslationStatus (简体中文)]]<br />
|-<br />
! colspan=2| Special templates<br />
|-<br />
| [[Template:Cat main]] || {{-}}<br />
|-<br />
| [[Template:Template]] || {{-}}<br />
|}<br />
<br />
== 完善翻译 ==<br />
[https://wiki.archlinux.org/index.php?title=Special:WhatLinksHere/Template:Translateme_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&limit=100 这个页面] 包含了需要完善翻译的简体中文页面。完善翻译的基本步骤:<br />
# 选择自己比较熟悉的文章进行翻译<br />
# 先检查英文页面的对应段落,更新成最新的英文后再翻译,避免翻译过时的内容,减少信息遗漏。<br />
# 翻译完成后删除页面中的 <nowiki>{{translateme (简体中文)}}</nowiki> 标记<br />
# (推荐)给翻译完成的页面加上[[Template:TranslationStatus (简体中文)|翻译状态]],后有详细介绍。<br />
<br />
== 更新过期页面 == <br />
如果发现有 Wiki 页面过期或错误:<br />
* 小的改动,有时间可以立即进行修改同步,维护者并不控制页面的编辑权限,越多的人参与维护越好。如果改动较大,请先联系维护者,避免重复劳动。<br />
* 没有时间查看更改,请给页面加上 {{ic|<nowiki>{{out of date}}</nowiki>}} 模版,这样其他贡献者更容易发现需要更新的页面,而读者看到过期标记就可以直接查看英文页面,以免被错误内容误导,白白耽误时间。<br />
* 没有时间翻译,请将过期的中文部分删去,从英文页面中复制更改的部分到中文页面的相应部分,去掉{{ic|<nowiki>{{out of date}}</nowiki>}}模板(如果页面上有的话)并加上{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板,这样其他贡献者就更容易发现需要翻译的页面,而读者也不会被过期的内容误导。<br />
如果发现有页面未翻译:<br />
* 有时间的话,请将页面中的英文部分翻译为中文,并去掉{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板。<br />
* 没有时间翻译,请为页面添加{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板,这样其他的贡献者就能更容易发现需要翻译的页面。<br />
{{注意|在修改页面上的模板时,请同时更新页面维护列表的翻译状态。}}<br />
<br />
== 翻译任务 ==<br />
=== 模板 Article summary 变更为 Related ===<br />
因为 Summary 中的简介基本上和正文的介绍一样,所以页面左边的介绍栏进行了简化,只保留相关文章功能。英文页面正在进行大规模修改,相应的中文页面也需要同步更新。<br />
<br />
需要注意的地方:<br />
* 将第一行改成<br />
: <nowiki>{{Related articles start (简体中文)}}</nowiki><br />
* 如果英文的相关文章存在中文翻译,则替换为简体中文页面。示例:<br />
: <nowiki>{{Related2|Display Manager (简体中文)|显示管理器}}</nowiki><br />
* 示例:[https://wiki.archlinux.org/index.php?title=Start_X_at_Login&diff=0&oldid=270155 英文变更], [https://wiki.archlinux.org/index.php?title=Start_X_at_Login_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=285643&oldid=242662 对应的翻译]<br />
<br />
== 维护翻译 ==<br />
完成页面的翻译只是初步完成任务,及时同步英文页面改动、更新翻译是一个持续性的工作,可能会耗费更多的时间。<br />
<br />
=== 页面认领 ===<br />
所有人都可以认领页面。认领后的责任包括进行翻译,关注英文页面的改动,及时同步翻译。<br />
<br />
为了更好的跟踪英文页面的修改,请务必在设置中启用监视列表邮件通知,并监视对应的英文页面(从设置中找到监视列表,加入英文页面。或者直接到英文页面点击页面顶端的监视标签。这样只要有改动,就会收到邮件通知)。<br />
<br />
{{小贴士|如果收到邮件通知后没有访问页面或者访问了页面却没有登录用户,下次页面改动时就不会再发邮件通知。可以点击监视列表中的'''标记所有页面为已读'''再次获取更新。}}<br />
<br />
如果页面有维护者但长期得不到更新,将会在维护列表中删除维护者。<br />
<br />
=== 翻译状态模板 ===<br />
Arch 作为滚动发行版,软件变化比较快,对应的文档变化也比较快。许多翻译的文章由于缺乏更新,会产生命令运行出错或不起作用等问题。而由于这些过期页面没有及时标记出来,所以用户无法及时获得更新。[[Template:TranslationStatus (简体中文)|翻译状态模板]]就是为了解决这个问题而创建。<br />
<br />
此模板可以起到如下作用:<br />
* 为用户提供翻译状况,包括翻译时间、英文页面的最后版本等<br />
* 用户可以点击查看翻译后,英文页面的改动,这样英文不是很好的用户可以只查看很小一部分英文内容,并判断出是否影响操作。<br />
* 翻译人员可以跟踪页面状况,通过[[Special:WhatLinksHere/Template:TranslationStatus_(简体中文)|模板的反向链接]]可以查找到所有标记页面,查看需要更新翻译的部分。<br />
<br />
[[Template:TranslationStatus (简体中文)|模板页面]]有详细的使用方法。<br />
<br />
=== 页面维护列表 ===<br />
{{注意|请按照拉丁字母顺序添加页面。}}<br />
<br />
翻译状态说明:<br />
;过期:页面内容未与英文页面同步,对应{{ic|<nowiki>{{out of date}}</nowiki>}} 模版<br />
;未翻译:页面中含有英文内容,对应{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板<br />
;完成:页面已与英文页面同步<br />
<br />
{| class="wikitable sortable collapsible" border="1"<br />
|-<br />
! 页面<br />
! 翻译状态<br />
! 维护者<br />
! class="unsortable" width="30%" | 备注<br />
|-<br />
| [[acpid (简体中文)]]<br />
| 过期<br />
| Cael<br />
|<br />
|-<br />
| [[Advanced Linux Sound Architecture (简体中文)]]<br />
| 翻译中<br />
| ihonliu<br />
| 无<br />
|-<br />
| [[Arch based distributions (active) (简体中文)]]<br />
| 完成<br />
| Joshua<br />
| 勘误中<br />
|-<br />
| [[Amateur radio (简体中文)]]<br />
| 翻译中<br />
| liu-shuyuan<br />
| <br />
|-<br />
| [[AMD Catalyst (简体中文)]]<br />
| 过期<br />
| Shibao Zhao<br />
| 无<br />
|-<br />
| [[ATI (简体中文)]]<br />
| 完成<br />
| skysailing<br />
| 无<br />
|-<br />
| [[AUR helpers (简体中文)]]<br />
| 完成<br />
| Kurobac<br />
| 部分用词可能需要修改<br />
|-<br />
| [[awesome (简体中文)]]<br />
| 进行中<br />
| Cael<br />
| 无<br />
|-<br />
| [[BIND (简体中文)]]<br />
| 完成<br />
| Dargasia<br />
|<br />
|-<br />
| [[Bumblebee (简体中文)]]<br />
| 完成<br />
| Peter<br />
| 无<br />
|-<br />
| [[Chromium (简体中文)]]<br />
| 完成<br />
| Bobby<br />
| 无<br />
|-<br />
| [[Ceph (简体中文)]]<br />
| 翻译中<br />
| Aaron Chen<br />
| 部分未翻译 <br />
|-<br />
| [[Cinnamon (简体中文)]]<br />
| 部分翻译 <br />
| Bobby<br />
| 部分未翻译 <br />
|- <br />
| [[Common Applications (简体中文)]]<br />
| 部分翻译 <br />
| DavidChen<br />
| 翻译中<br />
|-<br />
| [[Common Applications/Science (简体中文)]]<br />
| drop maintain<br />
| 更新,翻译中<br />
|<br />
|-<br />
| [[Compiz (简体中文)]]<br />
| 翻译中<br />
| xiii_1991<br />
| 20140813开始<br />
|-<br />
| [[Conky (简体中文)]]<br />
| 完成<br />
| upi<br />
| 无<br />
|-<br />
| [[Core utilities (简体中文)]]<br />
| 完成<br />
| rentaro, Arisaka<br />
| 无<br />
|-<br />
|-<br />
| [[Clover (简体中文)]]<br />
| 完成<br />
| Yume Kankawa<br />
| 无<br />
|-<br />
| [[Disk cloning (简体中文)]]<br />
| 翻译中<br />
| _spaike97<br />
| 无<br />
|-<br />
| [[Dynamic Kernel Module Support (简体中文)]]<br />
| 完成<br />
| Mithrandir<br />
| 完善中<br />
|-<br />
| [[Emacs (简体中文)]]<br />
| 翻译中<br />
| Jaurung yuanhang<br />
| 未完成<br />
|-<br />
| [[File recovery (简体中文)]]<br />
| 翻译中<br />
| _spaike97<br />
| 无<br />
|-<br />
| [[Fish (简体中文)]]<br />
| 完成<br />
| liu-shuyuan<br />
|<br />
|-<br />
| [[Font configuration (简体中文)]]<br />
| 翻译中<br />
| Jaurung<br />
| 完善中<br />
|-<br />
| [[Fonts (简体中文)]]<br />
| 翻译中<br />
| qqbzg<br />
| 无<br />
|-<br />
| [[GDM (简体中文)]]<br />
| 翻译中<br />
| Junjie Yuan<br />
| 绝大多数内容未翻译,重新进行翻译<br />
|-<br />
| [[GNOME (简体中文)]]<br />
| 完成<br />
| skywet<br />
| <br />
|-<br />
| [[GRUB (简体中文)]]<br />
| 完成<br />
| Armodeniz<br />
| <br />
|-<br />
| [[GRUB/Tips and tricks (简体中文)]]<br />
| 完成<br />
| Armodeniz<br />
| <br />
|-<br />
| [[Java (简体中文)]]<br />
| 翻译中<br />
| CaCaCarrot<br />
| 无<br />
|-<br />
| [[KDE (简体中文)]]<br />
| 过期<br />
| <br />
| <br />
|-<br />
| [[LAMP (简体中文)]]<br />
| 完成<br />
| Liuzhengyi<br />
| 勘误中<br />
|-<br />
| [[LibreOffice (简体中文)]]<br />
| 完成<br />
| qqbzg<br />
| 勘误中<br />
|-<br />
| [[Libvirt (简体中文)]]<br />
| 完成<br />
| Kurobac<br />
| 需要格式改进<br />
|-<br />
| [[Local Mirror (简体中文)]]<br />
| 完成<br />
| Jason Zhang<br />
| 完善中<br />
|- <br />
| [[MATLAB (简体中文)]]<br />
| 部分翻译 <br />
| Liu Qinyang<br />
|<br />
|-<br />
| [[Minecraft (简体中文)]]<br />
| 完成 <br />
| Xavier Lau<br />
| 页面已经与英文版同步,长期维护中<br />
|-<br />
| [[NetworkManager (简体中文)]]<br />
| 翻译中 <br />
| Jack-lijing, leeking <br />
| 请优先翻译<br />
|-<br />
| [[Network Time Protocol daemon (简体中文)]]<br />
| 完成<br />
| sid<br />
| 完善中<br />
|-<br />
| [[OpenOffice (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Opera (简体中文)]]<br />
| 未翻译<br />
| Bobby<br />
| 请优先翻译此文 <br />
|-<br />
| [[Pacman GUI Frontends (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Pidgin (简体中文)]]<br />
| 进行中<br />
| Cael<br />
| 无 <br />
|-<br />
| [[Python打包指引 (简体中文)]]<br />
| 翻译中<br />
| SherlockHolo<br />
| 无<br />
|- <br />
| [[ranger (简体中文)]]<br />
| 完成<br />
| Jason Zhang<br />
| 完善中<br />
|-<br />
| [[Raspberry Pi (简体中文)]]<br />
| 翻译中<br />
| Mithrandir<br />
| <br />
|-<br />
| [[Reporting bug guidelines (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[SDDM (简体中文)]]<br />
| 过期<br />
| C0n5t4ntK<br />
| 同步翻译中<br />
|-<br />
| [[Secure Shell (简体中文)]]<br />
| 完成<br />
| Arisaka<br />
| 无<br />
|-<br />
| [[Smart Common Input Method platform (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Steam (简体中文)]]<br />
| 完成<br />
| C0n5t4ntK<br />
| 长期维护中<br />
|-<br />
| [[Systemd-timesyncd (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[TLP (简体中文)]]<br />
| 完成<br />
| Skywet<br />
| 持续更新中 <br />
|-<br />
| [[Tomcat (简体中文)]]<br />
| 完成<br />
| Starwing117<br />
| 持续更新中 <br />
|-<br />
| [[Vim (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[VirtualBox (简体中文)]]<br />
| 翻译至 2017-10-15<br />
| [[User:5long]]<br />
|<br />
|-<br />
| [[VMware (简体中文)]]<br />
| 完成<br />
| ThomasWFan<br />
| 页面已经与英文版同步,长期维护中<br />
|- <br />
| [[Xfce (简体中文)]]<br />
| 完成 <br />
| 无<br />
| 无<br />
|-<br />
| [[Xmonad (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Xrandr (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=ArchWiki:Translation_Team_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=592060
ArchWiki:Translation Team (简体中文)
2019-12-17T09:27:37Z
<p>C0n5t4ntK: /* 页面维护列表 */ 更新状态</p>
<hr />
<div>[[Category:简体中文]]<br />
[[Category:ArchWiki (简体中文)]]<br />
[[ar:ArchWiki Translation Team]]<br />
[[cs:ArchWiki Translation Team]]<br />
[[el:ArchWiki Translation Team]]<br />
[[en:ArchWiki:Translation Team]]<br />
[[es:ArchWiki:Translation Team]]<br />
[[fr:ArchWiki Translation Team]]<br />
[[hr:ArchWiki Translation Team]]<br />
[[it:ArchWiki Translation Team]]<br />
[[ja:ArchWiki 翻訳チーム]]<br />
[[ko:ArchWiki Translation Team]]<br />
[[nl:ArchWiki Translation Team]]<br />
[[pl:ArchWiki Translation Team]]<br />
[[pt:ArchWiki:Translation Team]]<br />
[[ru:ArchWiki Translation Team]]<br />
[[sk:ArchWiki Translation Team]]<br />
[[zh-hant:ArchWiki:Translation Team]]<br />
Arch Wiki 上有许多中文页面,这其中大部分是从外文翻译过来的,这些页面是无数中文志愿者劳动的结晶。随着时间推移,有些页面因为没有及时维护,内容严重过时。而目前的翻译工作缺少组织,效率偏低。所以参照西班牙和意大利翻译组的做法,添加这个页面。<br />
<br />
如果你希望对Arch Wiki做贡献,参与Wiki建设,比如翻译英文页面和对已翻译过的中文页面进行维护,只需要编辑下面的[[#页面维护列表]],添加相应的条目,并将自己加为相关页面的维护者。如果你在列表中还没有找到想要翻译的页面,可以自行添加。另外,如果因为时间原因无法再维护页面,请及时将自己从维护者列表中删除。<br />
<br />
== 创建翻译 ==<br />
{{警告|如果不准备翻译页面的大部分内容,请尽量不要新建简体中文页面。检查英文页面的更新需要花费不少精力,没有翻译的页面会增加维护负担。}}<br />
# 如果还不知道如何编辑 wiki,请阅读 [[Help:Editing (简体中文)|编辑帮助]]。<br />
# 阅读 [[Help:i18n (简体中文)|i18n帮助]],文章给出了 ArchWiki 国际化和本地化的指南。<br />
# [[Special:UserLogin|登录]] 以进行编辑。<br />
# 选择要翻译的页面,例如从 [[Special:Random|随机页面]] 或[[#页面维护列表|页面维护列表]] 中选择一个未翻译完成的页面。假设要翻译 [[Some Page]].<br />
# 进入选择的英文页面,点击页面顶部的 '''编辑'''。<br />
# 添加要翻译文件的语言间链接, 简体中文的话加入<nowiki>[[zh-hans:Some Page]]</nowiki>,其它语言参见[[Help:i18n#Interlanguage links]])。<br />
# 复制所有页面代码。<br />
# 保存页面 (新加了语言链接)<br />
# 访问页面左边新添加的语言链接,应该会进到 [[Some Page (简体中文)]] : {{ic|<nowiki>https://wiki.archlinux.org/index.php/Some_Page_(</nowiki>''简体中文'')}}<br />
# 因为页面不存在,点击 '''创建'''。<br />
# 将显示一个编辑器 - 粘贴复制的英文页面。<br />
# 将文章分类修改为本地化版本,例如将 {{ic|<nowiki>[[Category:Internationalization]]</nowiki>}} 修改为 {{ic|<nowiki>[[Category:Internationalization (简体中文)]]</nowiki>}},参阅[[Help:Category (简体中文)]].<br />
# 修改语言间链接,指向英文页面(将 {{ic|zh-hans}} 修改为 {{ic|en}},并将英文页面移到文章顶部。<br />
# 翻译页面,进行保存。<br />
# (推荐)给翻译完成的页面加上[[Template:TranslationStatus (简体中文)|翻译状态]],后有详细介绍。<br />
# 更新所有其它语言页面,加入刚翻译文章的语言间链接。<br />
# (可选)创建一个简体中文名称的页面,指向新创建的页面:访问 {{ic|<nowiki>https://wiki.archlinux.org/index.php/</nowiki>''页面的中文名称''}}.<br />
# (可选)建立新页面,并加入:{{bc|<nowiki>#REDIRECT [[Some Page (简体中文)</nowiki>]]}}<br />
<br />
== Templates ==<br />
<br />
{{Translateme (简体中文)|Not translated}}<br />
<br />
The following table lists the [[Help:Template (简体中文)|templates]] that should be translated and their Simplified Chinese equivalent.<br />
<br />
{| class=wikitable<br />
! English template || Simplified Chinese version<br />
|-<br />
! colspan=2| Article templates<br />
|-<br />
| [[Template:Related articles start]] || [[Template:Related articles start (简体中文)]]<br />
|-<br />
| [[Template:Yes]] || [[Template:是]]<br />
|-<br />
| [[Template:No]] || [[Template:否]]<br />
|-<br />
| [[Template:Tip]] || [[Template:提示]]<br />
|-<br />
| [[Template:Note]] || [[Template:注意]]<br />
|-<br />
| [[Template:Warning]] || [[Template:警告]]<br />
|-<br />
| [[Template:Dead link]] || [[Template:失效链接]]<br />
|-<br />
| [[Template:Broken package link]] || {{-}}<br />
|-<br />
! colspan=2| Translation status templates<br />
|-<br />
| [[Template:Bad translation]] || {{-}}<br />
|-<br />
| [[Template:Translateme]] || [[Template:Translateme (简体中文)]]<br />
|-<br />
| [[Template:TranslationStatus]] || [[Template:TranslationStatus (简体中文)]]<br />
|-<br />
! colspan=2| Special templates<br />
|-<br />
| [[Template:Cat main]] || {{-}}<br />
|-<br />
| [[Template:Template]] || {{-}}<br />
|}<br />
<br />
== 完善翻译 ==<br />
[https://wiki.archlinux.org/index.php?title=Special:WhatLinksHere/Template:Translateme_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&limit=100 这个页面] 包含了需要完善翻译的简体中文页面。完善翻译的基本步骤:<br />
# 选择自己比较熟悉的文章进行翻译<br />
# 先检查英文页面的对应段落,更新成最新的英文后再翻译,避免翻译过时的内容,减少信息遗漏。<br />
# 翻译完成后删除页面中的 <nowiki>{{translateme (简体中文)}}</nowiki> 标记<br />
# (推荐)给翻译完成的页面加上[[Template:TranslationStatus (简体中文)|翻译状态]],后有详细介绍。<br />
<br />
== 更新过期页面 == <br />
如果发现有 Wiki 页面过期或错误:<br />
* 小的改动,有时间可以立即进行修改同步,维护者并不控制页面的编辑权限,越多的人参与维护越好。如果改动较大,请先联系维护者,避免重复劳动。<br />
* 没有时间查看更改,请给页面加上 {{ic|<nowiki>{{out of date}}</nowiki>}} 模版,这样其他贡献者更容易发现需要更新的页面,而读者看到过期标记就可以直接查看英文页面,以免被错误内容误导,白白耽误时间。<br />
* 没有时间翻译,请将过期的中文部分删去,从英文页面中复制更改的部分到中文页面的相应部分,去掉{{ic|<nowiki>{{out of date}}</nowiki>}}模板(如果页面上有的话)并加上{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板,这样其他贡献者就更容易发现需要翻译的页面,而读者也不会被过期的内容误导。<br />
如果发现有页面未翻译:<br />
* 有时间的话,请将页面中的英文部分翻译为中文,并去掉{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板。<br />
* 没有时间翻译,请为页面添加{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板,这样其他的贡献者就能更容易发现需要翻译的页面。<br />
{{注意|在修改页面上的模板时,请同时更新页面维护列表的翻译状态。}}<br />
<br />
== 翻译任务 ==<br />
=== 模板 Article summary 变更为 Related ===<br />
因为 Summary 中的简介基本上和正文的介绍一样,所以页面左边的介绍栏进行了简化,只保留相关文章功能。英文页面正在进行大规模修改,相应的中文页面也需要同步更新。<br />
<br />
需要注意的地方:<br />
* 将第一行改成<br />
: <nowiki>{{Related articles start (简体中文)}}</nowiki><br />
* 如果英文的相关文章存在中文翻译,则替换为简体中文页面。示例:<br />
: <nowiki>{{Related2|Display Manager (简体中文)|显示管理器}}</nowiki><br />
* 示例:[https://wiki.archlinux.org/index.php?title=Start_X_at_Login&diff=0&oldid=270155 英文变更], [https://wiki.archlinux.org/index.php?title=Start_X_at_Login_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=285643&oldid=242662 对应的翻译]<br />
<br />
== 维护翻译 ==<br />
完成页面的翻译只是初步完成任务,及时同步英文页面改动、更新翻译是一个持续性的工作,可能会耗费更多的时间。<br />
<br />
=== 页面认领 ===<br />
所有人都可以认领页面。认领后的责任包括进行翻译,关注英文页面的改动,及时同步翻译。<br />
<br />
为了更好的跟踪英文页面的修改,请务必在设置中启用监视列表邮件通知,并监视对应的英文页面(从设置中找到监视列表,加入英文页面。或者直接到英文页面点击页面顶端的监视标签。这样只要有改动,就会收到邮件通知)。<br />
<br />
{{小贴士|如果收到邮件通知后没有访问页面或者访问了页面却没有登录用户,下次页面改动时就不会再发邮件通知。可以点击监视列表中的'''标记所有页面为已读'''再次获取更新。}}<br />
<br />
如果页面有维护者但长期得不到更新,将会在维护列表中删除维护者。<br />
<br />
=== 翻译状态模板 ===<br />
Arch 作为滚动发行版,软件变化比较快,对应的文档变化也比较快。许多翻译的文章由于缺乏更新,会产生命令运行出错或不起作用等问题。而由于这些过期页面没有及时标记出来,所以用户无法及时获得更新。[[Template:TranslationStatus (简体中文)|翻译状态模板]]就是为了解决这个问题而创建。<br />
<br />
此模板可以起到如下作用:<br />
* 为用户提供翻译状况,包括翻译时间、英文页面的最后版本等<br />
* 用户可以点击查看翻译后,英文页面的改动,这样英文不是很好的用户可以只查看很小一部分英文内容,并判断出是否影响操作。<br />
* 翻译人员可以跟踪页面状况,通过[[Special:WhatLinksHere/Template:TranslationStatus_(简体中文)|模板的反向链接]]可以查找到所有标记页面,查看需要更新翻译的部分。<br />
<br />
[[Template:TranslationStatus (简体中文)|模板页面]]有详细的使用方法。<br />
<br />
=== 页面维护列表 ===<br />
{{注意|请按照拉丁字母顺序添加页面。}}<br />
<br />
翻译状态说明:<br />
;过期:页面内容未与英文页面同步,对应{{ic|<nowiki>{{out of date}}</nowiki>}} 模版<br />
;未翻译:页面中含有英文内容,对应{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板<br />
;完成:页面已与英文页面同步<br />
<br />
{| class="wikitable sortable collapsible" border="1"<br />
|-<br />
! 页面<br />
! 翻译状态<br />
! 维护者<br />
! class="unsortable" width="30%" | 备注<br />
|-<br />
| [[acpid (简体中文)]]<br />
| 过期<br />
| Cael<br />
|<br />
|-<br />
| [[Advanced Linux Sound Architecture (简体中文)]]<br />
| 翻译中<br />
| ihonliu<br />
| 无<br />
|-<br />
| [[Arch based distributions (active) (简体中文)]]<br />
| 完成<br />
| Joshua<br />
| 勘误中<br />
|-<br />
| [[Amateur radio (简体中文)]]<br />
| 翻译中<br />
| liu-shuyuan<br />
| <br />
|-<br />
| [[AMD Catalyst (简体中文)]]<br />
| 过期<br />
| Shibao Zhao<br />
| 无<br />
|-<br />
| [[ATI (简体中文)]]<br />
| 完成<br />
| skysailing<br />
| 无<br />
|-<br />
| [[AUR helpers (简体中文)]]<br />
| 完成<br />
| Kurobac<br />
| 部分用词可能需要修改<br />
|-<br />
| [[awesome (简体中文)]]<br />
| 进行中<br />
| Cael<br />
| 无<br />
|-<br />
| [[BIND (简体中文)]]<br />
| 完成<br />
| Dargasia<br />
|<br />
|-<br />
| [[Bumblebee (简体中文)]]<br />
| 完成<br />
| Peter<br />
| 无<br />
|-<br />
| [[Chromium (简体中文)]]<br />
| 完成<br />
| Bobby<br />
| 无<br />
|-<br />
| [[Ceph (简体中文)]]<br />
| 翻译中<br />
| Aaron Chen<br />
| 部分未翻译 <br />
|-<br />
| [[Cinnamon (简体中文)]]<br />
| 部分翻译 <br />
| Bobby<br />
| 部分未翻译 <br />
|- <br />
| [[Common Applications (简体中文)]]<br />
| 部分翻译 <br />
| DavidChen<br />
| 翻译中<br />
|-<br />
| [[Common Applications/Science (简体中文)]]<br />
| drop maintain<br />
| 更新,翻译中<br />
|<br />
|-<br />
| [[Compiz (简体中文)]]<br />
| 翻译中<br />
| xiii_1991<br />
| 20140813开始<br />
|-<br />
| [[Conky (简体中文)]]<br />
| 完成<br />
| upi<br />
| 无<br />
|-<br />
| [[Core utilities (简体中文)]]<br />
| 完成<br />
| rentaro, Arisaka<br />
| 无<br />
|-<br />
|-<br />
| [[Clover (简体中文)]]<br />
| 完成<br />
| Yume Kankawa<br />
| 无<br />
|-<br />
| [[Disk cloning (简体中文)]]<br />
| 翻译中<br />
| _spaike97<br />
| 无<br />
|-<br />
| [[Dynamic Kernel Module Support (简体中文)]]<br />
| 完成<br />
| Mithrandir<br />
| 完善中<br />
|-<br />
| [[Emacs (简体中文)]]<br />
| 翻译中<br />
| Jaurung yuanhang<br />
| 未完成<br />
|-<br />
| [[File recovery (简体中文)]]<br />
| 翻译中<br />
| _spaike97<br />
| 无<br />
|-<br />
| [[Fish (简体中文)]]<br />
| 完成<br />
| liu-shuyuan<br />
|<br />
|-<br />
| [[Font configuration (简体中文)]]<br />
| 翻译中<br />
| Jaurung<br />
| 完善中<br />
|-<br />
| [[Fonts (简体中文)]]<br />
| 翻译中<br />
| qqbzg<br />
| 无<br />
|-<br />
| [[GDM (简体中文)]]<br />
| 翻译中<br />
| Junjie Yuan<br />
| 绝大多数内容未翻译,重新进行翻译<br />
|-<br />
| [[GNOME (简体中文)]]<br />
| 完成<br />
| skywet<br />
| <br />
|-<br />
| [[GRUB (简体中文)]]<br />
| 完成<br />
| Armodeniz<br />
| <br />
|-<br />
| [[GRUB/Tips and tricks (简体中文)]]<br />
| 完成<br />
| Armodeniz<br />
| <br />
|-<br />
| [[Java (简体中文)]]<br />
| 翻译中<br />
| CaCaCarrot<br />
| 无<br />
|-<br />
| [[KDE (简体中文)]]<br />
| 过期<br />
| <br />
| <br />
|-<br />
| [[LAMP (简体中文)]]<br />
| 完成<br />
| Liuzhengyi<br />
| 勘误中<br />
|-<br />
| [[LibreOffice (简体中文)]]<br />
| 完成<br />
| qqbzg<br />
| 勘误中<br />
|-<br />
| [[Libvirt (简体中文)]]<br />
| 完成<br />
| Kurobac<br />
| 需要格式改进<br />
|-<br />
| [[Local Mirror (简体中文)]]<br />
| 完成<br />
| Jason Zhang<br />
| 完善中<br />
|- <br />
| [[MATLAB (简体中文)]]<br />
| 部分翻译 <br />
| Liu Qinyang<br />
|<br />
|-<br />
| [[Minecraft (简体中文)]]<br />
| 完成 <br />
| Xavier Lau<br />
| 页面已经与英文版同步,长期维护中<br />
|-<br />
| [[NetworkManager (简体中文)]]<br />
| 翻译中 <br />
| Jack-lijing, leeking <br />
| 请优先翻译<br />
|-<br />
| [[Network Time Protocol daemon (简体中文)]]<br />
| 完成<br />
| sid<br />
| 完善中<br />
|-<br />
| [[OpenOffice (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Opera (简体中文)]]<br />
| 未翻译<br />
| Bobby<br />
| 请优先翻译此文 <br />
|-<br />
| [[Pacman GUI Frontends (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Pidgin (简体中文)]]<br />
| 进行中<br />
| Cael<br />
| 无 <br />
|-<br />
| [[Python打包指引 (简体中文)]]<br />
| 翻译中<br />
| SherlockHolo<br />
| 无<br />
|- <br />
| [[ranger (简体中文)]]<br />
| 完成<br />
| Jason Zhang<br />
| 完善中<br />
|-<br />
| [[Raspberry Pi (简体中文)]]<br />
| 翻译中<br />
| Mithrandir<br />
| <br />
|-<br />
| [[Reporting bug guidelines (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Secure Shell (简体中文)]]<br />
| 完成<br />
| Arisaka<br />
| 无<br />
|-<br />
| [[Smart Common Input Method platform (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Steam (简体中文)]]<br />
| 完成<br />
| C0n5t4ntK<br />
| 长期维护中<br />
|-<br />
| [[Systemd-timesyncd (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[TLP (简体中文)]]<br />
| 完成<br />
| Skywet<br />
| 持续更新中 <br />
|-<br />
| [[Tomcat (简体中文)]]<br />
| 完成<br />
| Starwing117<br />
| 持续更新中 <br />
|-<br />
| [[Vim (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[VirtualBox (简体中文)]]<br />
| 翻译至 2017-10-15<br />
| [[User:5long]]<br />
|<br />
|-<br />
| [[VMware (简体中文)]]<br />
| 完成<br />
| ThomasWFan<br />
| 页面已经与英文版同步,长期维护中<br />
|- <br />
| [[Xfce (简体中文)]]<br />
| 完成 <br />
| 无<br />
| 无<br />
|-<br />
| [[Xmonad (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Xrandr (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=Steam_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=592059
Steam (简体中文)
2019-12-17T09:25:14Z
<p>C0n5t4ntK: 翻译完成</p>
<hr />
<div>[[Category:Gaming (简体中文)]]<br />
[[en:Steam]]<br />
[[ja:Steam]]<br />
[[ru:Steam]]<br />
{{Related articles start (简体中文)}}<br />
{{Related|Steam/Troubleshooting}}<br />
{{Related|Steam/Game-specific troubleshooting}}<br />
{{Related|Gaming}}<br />
{{Related|Gamepad}}<br />
{{Related|List of games (简体中文)}}<br />
{{Related articles end}}<br />
{{TranslationStatus (简体中文)|Steam|2019-12-17|591269}}<br />
[http://store.steampowered.com/about/ Steam] 是维尔福公司推出的著名游戏分发平台。<br />
<br />
{{注意|对于 Linux 平台,Steam 只支持 Ubuntu 的长期支持版本[https://support.steampowered.com/kb_article.php?ref&#61;1504-QHXN-8366]。 因此,请不要向维尔福公司提交 issue 以获得 Steam 对 Arch Linux 的支持。}}<br />
<br />
== 安装 ==<br />
<br />
启用 [[multilib]] 仓库并[[Help:Reading (简体中文)#安装软件包|安装]] {{Pkg|steam}} 软件包。<br />
<br />
你需要满足下列要求从而在 Arch Linux 上运行 Steam:<br />
<br />
* 安装 32 位版本的 [[Xorg#Driver installation|OpenGL 图形驱动]]。<br />
* 生成 [[Locale#Generating locales|en_US.UTF-8]] 语言环境,以避免非法指针错误。<br />
* 其图形界面大量使用 Arial 字体。详见 [[Microsoft fonts]] 。你可以通过安装 {{Pkg|ttf-liberation}} 或使用 [[Steam/Troubleshooting#Text is corrupt or missing|Steam 支持的字体问题]] 中的方法来解决。<br />
* 安装 {{Pkg|wqy-zenhei}} 以支持亚洲地区语言。<br />
<br />
=== SteamCMD ===<br />
<br />
安装 {{AUR|steamcmd}} 以使用命令行版本的 [https://developer.valvesoftware.com/wiki/SteamCMD Steam]。<br />
<br />
=== 可选 Flatpak 安装 ===<br />
<br />
Steam 也可以作为 {{ic|com.valvesoftware.Steam}} 使用 [[Flatpak]] 从 [https://flathub.org/ Flathub] 中安装。使用 Flathub 仓库和 flatpak 命令行安装是目前最简单的安装方式:<br />
<br />
flatpak --user remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo<br />
flatpak --user install flathub com.valvesoftware.Steam<br />
flatpak run com.valvesoftware.Steam<br />
<br />
目前 Flatpak 应用还不支持主题。并且你不能通过 {{ic|optirun}}/{{ic|primusrun}} 来运行游戏,更多细节详见 [https://github.com/flatpak/flatpak/issues/869 Issue#869]。<br />
<br />
默认情况下 Steam 不会有访问你的家目录的权限,你可以运行下列命令来授予权限,以获得更类似于在 Ubuntu 或 SteamOS 下的运行效果:<br />
<br />
flatpak override com.valvesoftware.Steam --filesystem=$HOME<br />
<br />
==== Flatpak 的亚洲字体问题 ====<br />
<br />
如果你遇到了游戏中无法显示亚洲字体的问题,这是因为 org.freedesktop.Platform 并没有包含合适的字体文件进去。首先尝试挂载你的本地字体:<br />
<br />
flatpak run --filesystems=~/.local/share/fonts --filesystem=~/.config/fontconfig com.valvesoftware.Steam<br />
<br />
如果上述命令不起作用,考虑动手 hack 一下:直接将字体文件复制进 org.freedesktop.Platform 的目录下以启用字体,例如<br />
<br />
# replace ? with your version and hash<br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/etc/fonts/conf.avail<br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/etc/fonts/conf.d <br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/share/fonts<br />
<br />
== 目录结构 ==<br />
<br />
Steam 的默认安装位置是 {{ic|~/.local/share/Steam}}。如果 Steam 无法找到该目录,它会引导你重新安装或选择一个新的安装位置。这篇文章使用 {{ic|~/.steam/root}} 符号链接来表示 Steam 的安装位置。<br />
<br />
=== 库文件夹 ===<br />
<br />
每一个 Steam 应用都有一个独一无二的应用 ID,你可以通过 [http://store.steampowered.com/ Steam Store] 页面路径来找到它。<br />
<br />
Steam 将游戏安装到 {{ic|''LIBRARY''/steamapps/common/}} 目录下。库文件夹 {{ic|''LIBRARY''}} 一般会是<br />
{{ic|~/.steam/root}},但是你依然可以选择拥有多个库文件夹如 (''Steam > Settings > Downloads > Steam Library Folders'')。<br />
<br />
为了 Steam 能够正确识别游戏,它需要在 {{ic|''LIBRARY''/steamapps/}} 目录下找到 {{ic|appmanifest_''AppId''.acf}} 文件。此文件使用了<br />
[https://developer.valvesoftware.com/wiki/KeyValues KeyValues] 格式,并且它的 {{ic|installdir}} 的内容决定了游戏的目录名称。<br />
<br />
== 用法 ==<br />
<br />
steam [ -options ] [ steam:// URL ]<br />
<br />
对于可用的命令行选择,详见 [https://developer.valvesoftware.com/wiki/Command_Line_Options#Steam_.28Windows.29 Command Line Options article on the Valve Developer Wiki]。<br />
<br />
Steam 也可以接受可选的 Steam URL,详见 [https://developer.valvesoftware.com/wiki/Steam_browser_protocol Steam browser procotol]。<br />
<br />
== 启动选项 ==<br />
<br />
当你运行一个 Steam 游戏时,Steam 会使用 [[Bash]] shell 执行它的 '''启动命令'''。<br />
为了让你随意修改启动命令,Steam 提供了 '''启动选项'''。<br />
'''启动选项'''可以通过右键点击你的游戏库中的游戏,选择属性后点击'''设置启动选项'''进行修改。<br />
<br />
默认情况下 Steam 只是简单的把你设置的参数字符串添加到游戏的启动命令后。想要设置环境变量或者将一个启动命令作为参数传递给另一个命令,你可以使用 {{ic|%command%}} 以表示原启动命令。<br />
<br />
=== 实例 ===<br />
<br />
* 仅设置参数: {{ic|-foo}}<br />
* 设置环境变量: {{ic|1=FOO=bar BAZ=bar %command% -baz}}<br />
* 设置与默认完全不同的命令: {{ic|othercommand # %command%}}<br />
<br />
== 提示与技巧 ==<br />
<br />
=== Fsync 补丁 ===<br />
<br />
维尔福公司 [https://steamcommunity.com/app/221410/discussions/0/3158631000006906163/ 发布] 了一个可以帮助提升大量多线程应用运行帧率的特殊内核补丁。这里有一些使用这个补丁的方法:<br />
<br />
* 直接使用维尔福公司提供的二进制内核。详见 [[Unofficial user repositories#valveaur]] 并且一旦你添加了这个仓库,内核软件 {{AUR|linux-fsync}} 和 {{AUR|linux-fsync-headers}} 便可使用。你将可能需要替换某些常用软件包 (例如 {{pkg|nvidia}}) 和 [[DKMS]] 软件包 (例如 {{pkg|nvidia-dkms}})。<br />
* 安装 {{AUR|linux-fsync}} 内核。<br />
* 安装 {{Pkg|linux-zen}} 内核,其从 5.2 版本开始已包括 fsync 补丁。[https://github.com/zen-kernel/zen-kernel/commit/f39367fdbc68e8b1e623239d13db6efaa5a67ae1]<br />
<br />
=== Proton Steam-Play ===<br />
<br />
维尔福公司开发了一个兼容性工具,用来使 Steam 可以在 Wine 和其他额外组件上运行。这使得你可以运行很多只能在 Windows 平台上运行的游戏 (详见 [https://www.protondb.com/ compatibility list])。<br />
<br />
此工具开源并且可以从 [https://github.com/ValveSoftware/Proton/ Github] 获得。Steam 将在 Steam Play 启用后安装它相适应的 Proton 版本。<br />
<br />
Proton 需要在 Steam 客户端启用: {{ic|Steam > 设置 > Steam Play}}。你可以为了上述那些没有被维尔福公司列入白名单的游戏启用 Steam Play。<br />
<br />
如果需要的话,为了在启动游戏时强制启用 Proton 或者指定一个确定的 Proton 版本,在游戏处右击,点击 {{ic|属性 > 常规 > 强制使用特定 Steam Play 兼容性工具}},然后选择所需版本。这样做同样可以用来强制游戏生成一个 Linux 入口用以运行 Windows 版本的游戏。<br />
<br />
你同样可以从 AUR 通过安装 {{AUR|proton}} 或 {{AUR|proton-git}} 来安装 Proton,但是需要一些额外的配置才能使 Steam 良好运行。想要了解 Steam 如何识别已安装的 Proton 的更多细节,可以前往 Proton 的 Github 页面。<br />
<br />
=== 无需窗口管理器的大屏幕模式 ===<br />
<br />
想要从 [[Display manager (简体中文)]] 运行 Steam 的大屏幕模式,你可以选择以下任意一个方案:<br />
<br />
* 安装 {{AUR|steamos-compositor}}<br />
* 或者,安装 {{AUR|steamos-compositor-plus}},这可以隐藏 Proton 游戏启动时恼人的颜色闪烁,并修复游戏在后台运行的问题。<br />
* 手动添加一个 Steam 入口 (''但是你会失去 Steam 的混合平台优势:主要体现在你'''不能'''使用键盘或手柄控制大屏幕模式''):<br />
<br />
创建一个 {{ic|/usr/share/xsessions/steam-big-picture.desktop}} 文件,其中包含:<br />
<br />
{{hc|/usr/share/xsessions/steam-big-picture.desktop|<nowiki><br />
[Desktop Entry]<br />
Name=Steam Big Picture Mode<br />
Comment=Start Steam in Big Picture Mode<br />
Exec=/usr/bin/steam -bigpicture<br />
TryExec=/usr/bin/steam<br />
Icon=<br />
Type=Application</nowiki>}}<br />
<br />
=== Steam 皮肤 ===<br />
<br />
使用皮肤可以自定义 Steam 界面。皮肤可以被位于 {{ic|~/.steam/root}} 的界面定义文件所覆盖。<br />
<br />
想要安装一个皮肤:<br />
<br />
# 将皮肤的目录放于 {{ic|~/.steam/root/skins}}。<br />
# 按照 ''Steam > 设置 > 界面'' 依次点击并选择该皮肤。<br />
# 重启 Steam。<br />
<br />
你可以在 [http://forums.steampowered.com/forums/showthread.php?t=1161035 Steam 论坛] 获得比较完备的皮肤列表。<br />
<br />
{{注意|使用一个过期的皮肤可能会引起一些可视化错误。}}<br />
<br />
==== 自创皮肤 ====<br />
<br />
几乎所有的 Steam 风格会定义在 {{ic|~/.steam/root/resource/styles/steam.styles}} (此文件超过 3,500 行)。对于一个可以被 Steam 识别的皮肤,它需要自己的 {{ic|resource/styles/steam.styles}} 文件。<br />
当一个 Steam 的更新改变了官方的 {{ic|steam.styles}} 文件,你的皮肤可能会过期,会有造成可视化错误的潜在风险。<br />
<br />
详见 {{ic|~/.steam/root/skins/skins_readme.txt}} 以获得如何创建皮肤的初步指引。<br />
<br />
=== 改变 Steam 的通知位置 ===<br />
<br />
默认情况下 Steam 的通知会在屏幕底端右侧出现。<br />
<br />
你可以改变 Steam 通知出现的位置,通过更改 {{ic|Notifications.PanelPosition}} 文件,具体位于<br />
<br />
* {{ic|resource/styles/steam.styles}} 以调整桌面通知<br />
* {{ic|resource/styles/gameoverlay.styles}} 以调整游戏中通知<br />
<br />
以上两个文件都将在 Steam 启动时被覆写,且 {{ic|steam.styles}} 只会在启动时被读取。<br />
<br />
{{注意|一些游戏并不遵守位于 {{ic|gameoverlay.styles}} 里的设置。如《幽浮:未知敌人》。}}<br />
<br />
==== 使用一个皮肤 ====<br />
<br />
你可以创建一个皮肤去将通知位置改变成你想要的那样。比如你想要将位置设置成顶部右侧:<br />
<br />
$ cd ~/.steam/root/skins<br />
$ mkdir -p Top-Right/resource<br />
$ cp -r ~/.steam/root/resource/styles Top-Right/resource<br />
$ sed -i '/Notifications.PanelPosition/ s/"[A-Za-z]*"/"TopRight"/' Top-Right/resource/styles/*<br />
<br />
==== 实时更新 ====<br />
<br />
{{ic|gameoverlay.styles}} 文件可以在 Steam 运行时更改,这允许你对不同游戏设置不同的通知位置。<br />
<br />
{{hc|~/.steam/notifpos.sh|<br />
sed -i "/Notifications.PanelPosition/ s/\"[A-Za-z]*\"/\"$1\"/" ~/.steam/root/resource/styles/gameoverlay.styles<br />
}}<br />
<br />
由此 [[#启动选项]] 应该像下面这样:<br />
<br />
~/.steam/notifpos.sh TopLeft && %command%<br />
<br />
=== Steam 远程同乐 ===<br />
<br />
{{注意|Steam 家庭流媒体 [https://store.steampowered.com/news/51761/ 已变为 Steam 远程同乐]。}}<br />
<br />
Steam 内置对于 [http://store.steampowered.com/streaming/ 远程同乐] 的支持。<br />
<br />
前往 [https://steamcommunity.com/sharedfiles/filedetails/?id=680514371 Steam 社区指南] 以了解如何在 Linux 上设置 headless 模式的流式服务器。<br />
<br />
==== 不同子网 ====<br />
<br />
{{Remove|本解决方案将不再具有参考意义,因为此方案已经变为 [https://store.steampowered.com/news/51761/ Steam 远程同乐] 的一个特性。}}<br />
<br />
Steam 客户端如果处在不同的子网中,那么将不能检测到主机,这种情况常见于当你使用 VPN 去连接你的家庭网络时。就算服务端与服务器都可以互相 ping 通 —— Steam 客户端将仍然不会检测主机,因此你需要去强制检测。想要达到目标,你需要使用下面的命令启动 Steam:<br />
<br />
$ steam -console<br />
<br />
请耐心等待,直到 Steam 已经启动。一旦它加载完成,你会发现一个名为“控制台”的额外标签。打开它并将已替换为正确主机 IP 的下列命令粘贴上去:<br />
<br />
connect_remote <host_ip>:27036<br />
<br />
你将会看到通知说:你可以从主机来流式运行游戏了。<br />
<br />
{{注意|如果上述的命令不起作用 —— Windows 可能会屏蔽来自不同子网的所有流入流量,这意味着所有来自 VPN 管道的连接将会被丢弃。如果你向你的 VPN 客户端发出了 ping 的请求但没有任何的应答,那么就可以确定是上述的问题。要解决它,配置(或关闭)所有 Windows 防火墙(包括已经运行的杀毒软件)。}}<br />
<br />
{{提示|如果上述方案均不起作用,参见 [[Gaming#Remote gaming]] 以查找其他方法。}}<br />
<br />
=== Steam 控制器 ===<br />
<br />
通常一个 Steam 控制器需要使用 Steam 界面。不过在非 Steam 的原生 Linux 游戏中这种界面并不很实用。对此,当 Steam 客户端运行时,其会保持一个“桌面配置”。如果你有 Steam 控制器,请在桌面配置中将其设置为通用 XBOX 控制器。只要 Steam 客户端在运行,你可以在其他游戏中使用 Steam 控制器,例如 GOG 的游戏, 就像一个 XBOX 控制器。确保已经选择了你的控制器类型以实现“常规控制器设置”的映射。<br />
<br />
== 故障排除 ==<br />
<br />
参见 [[Steam/Troubleshooting]].<br />
<br />
== 另见 ==<br />
<br />
* [https://wiki.gentoo.org/wiki/Steam Gentoo Wiki article]<br />
* [https://pcgamingwiki.com/wiki/The_Big_List_of_DRM-Free_Games_on_Steam The Big List of DRM-Free Games on Steam] 位于 PCGamingWiki<br />
* [http://steam.wikia.com/wiki/List_of_DRM-free_games List of DRM-free games] 位于 Wikia<br />
* [http://store.steampowered.com/browse/linux Steam Linux store]<br />
* [https://github.com/ValveSoftware/Proton/ Proton] 支持 Steam Play 运行的基于 Wine 以及其他额外组件的兼容性工具</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=Steam_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=592051
Steam (简体中文)
2019-12-17T04:45:50Z
<p>C0n5t4ntK: /* 无需窗口管理器的大屏幕模式 */ 翻译完成。</p>
<hr />
<div>[[Category:Gaming (简体中文)]]<br />
[[en:Steam]]<br />
[[ja:Steam]]<br />
[[ru:Steam]]<br />
{{Related articles start (简体中文)}}<br />
{{Related|Steam/Troubleshooting}}<br />
{{Related|Steam/Game-specific troubleshooting}}<br />
{{Related|Gaming}}<br />
{{Related|Gamepad}}<br />
{{Related|List of games (简体中文)}}<br />
{{Related articles end}}<br />
[http://store.steampowered.com/about/ Steam] 是维尔福公司推出的著名游戏分发平台。<br />
<br />
{{注意|对于 Linux 平台,Steam 只支持 Ubuntu 的长期支持版本[https://support.steampowered.com/kb_article.php?ref&#61;1504-QHXN-8366]。 因此,请不要向维尔福公司提交 issue 以获得 Steam 对 Arch Linux 的支持。}}<br />
<br />
== 安装 ==<br />
<br />
启用 [[multilib]] 仓库并[[Help:Reading (简体中文)#安装软件包|安装]] {{Pkg|steam}} 软件包。<br />
<br />
你需要满足下列要求从而在 Arch Linux 上运行 Steam:<br />
<br />
* 安装 32 位版本的 [[Xorg#Driver installation|OpenGL 图形驱动]]。<br />
* 生成 [[Locale#Generating locales|en_US.UTF-8]] 语言环境,以避免非法指针错误。<br />
* 其图形界面大量使用 Arial 字体。详见 [[Microsoft fonts]] 。你可以通过安装 {{Pkg|ttf-liberation}} 或使用 [[Steam/Troubleshooting#Text is corrupt or missing|Steam 支持的字体问题]] 中的方法来解决。<br />
* 安装 {{Pkg|wqy-zenhei}} 以支持亚洲地区语言。<br />
<br />
=== SteamCMD ===<br />
<br />
安装 {{AUR|steamcmd}} 以使用命令行版本的 [https://developer.valvesoftware.com/wiki/SteamCMD Steam]。<br />
<br />
=== 可选 Flatpak 安装 ===<br />
<br />
Steam 也可以作为 {{ic|com.valvesoftware.Steam}} 使用 [[Flatpak]] 从 [https://flathub.org/ Flathub] 中安装。使用 Flathub 仓库和 flatpak 命令行安装是目前最简单的安装方式:<br />
<br />
flatpak --user remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo<br />
flatpak --user install flathub com.valvesoftware.Steam<br />
flatpak run com.valvesoftware.Steam<br />
<br />
目前 Flatpak 应用还不支持主题。并且你不能通过 {{ic|optirun}}/{{ic|primusrun}} 来运行游戏,更多细节详见 [https://github.com/flatpak/flatpak/issues/869 Issue#869]。<br />
<br />
默认情况下 Steam 不会有访问你的家目录的权限,你可以运行下列命令来授予权限,以获得更类似于在 Ubuntu 或 SteamOS 下的运行效果:<br />
<br />
flatpak override com.valvesoftware.Steam --filesystem=$HOME<br />
<br />
==== Flatpak 的亚洲字体问题 ====<br />
<br />
如果你遇到了游戏中无法显示亚洲字体的问题,这是因为 org.freedesktop.Platform 并没有包含合适的字体文件进去。首先尝试挂载你的本地字体:<br />
<br />
flatpak run --filesystems=~/.local/share/fonts --filesystem=~/.config/fontconfig com.valvesoftware.Steam<br />
<br />
如果上述命令不起作用,考虑动手 hack 一下:直接将字体文件复制进 org.freedesktop.Platform 的目录下以启用字体,例如<br />
<br />
# replace ? with your version and hash<br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/etc/fonts/conf.avail<br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/etc/fonts/conf.d <br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/share/fonts<br />
<br />
== 目录结构 ==<br />
<br />
Steam 的默认安装位置是 {{ic|~/.local/share/Steam}}。如果 Steam 无法找到该目录,它会引导你重新安装或选择一个新的安装位置。这篇文章使用 {{ic|~/.steam/root}} 符号链接来表示 Steam 的安装位置。<br />
<br />
=== 库文件夹 ===<br />
<br />
每一个 Steam 应用都有一个独一无二的应用 ID,你可以通过 [http://store.steampowered.com/ Steam Store] 页面路径来找到它。<br />
<br />
Steam 将游戏安装到 {{ic|''LIBRARY''/steamapps/common/}} 目录下。库文件夹 {{ic|''LIBRARY''}} 一般会是<br />
{{ic|~/.steam/root}},但是你依然可以选择拥有多个库文件夹如 (''Steam > Settings > Downloads > Steam Library Folders'')。<br />
<br />
为了 Steam 能够正确识别游戏,它需要在 {{ic|''LIBRARY''/steamapps/}} 目录下找到 {{ic|appmanifest_''AppId''.acf}} 文件。此文件使用了<br />
[https://developer.valvesoftware.com/wiki/KeyValues KeyValues] 格式,并且它的 {{ic|installdir}} 的内容决定了游戏的目录名称。<br />
<br />
== 用法 ==<br />
<br />
steam [ -options ] [ steam:// URL ]<br />
<br />
对于可用的命令行选择,详见 [https://developer.valvesoftware.com/wiki/Command_Line_Options#Steam_.28Windows.29 Command Line Options article on the Valve Developer Wiki]。<br />
<br />
Steam 也可以接受可选的 Steam URL,详见 [https://developer.valvesoftware.com/wiki/Steam_browser_protocol Steam browser procotol]。<br />
<br />
== 启动选项 ==<br />
<br />
当你运行一个 Steam 游戏时,Steam 会使用 [[Bash]] shell 执行它的 '''启动命令'''。<br />
为了让你随意修改启动命令,Steam 提供了 '''启动选项'''。<br />
'''启动选项'''可以通过右键点击你的游戏库中的游戏,选择属性后点击'''设置启动选项'''进行修改。<br />
<br />
默认情况下 Steam 只是简单的把你设置的参数字符串添加到游戏的启动命令后。想要设置环境变量或者将一个启动命令作为参数传递给另一个命令,你可以使用 {{ic|%command%}} 以表示原启动命令。<br />
<br />
=== 实例 ===<br />
<br />
* 仅设置参数: {{ic|-foo}}<br />
* 设置环境变量: {{ic|1=FOO=bar BAZ=bar %command% -baz}}<br />
* 设置与默认完全不同的命令: {{ic|othercommand # %command%}}<br />
<br />
== 提示与技巧 ==<br />
<br />
=== Fsync 补丁 ===<br />
<br />
维尔福公司 [https://steamcommunity.com/app/221410/discussions/0/3158631000006906163/ 发布] 了一个可以帮助提升大量多线程应用运行帧率的特殊内核补丁。这里有一些使用这个补丁的方法:<br />
<br />
* 直接使用维尔福公司提供的二进制内核。详见 [[Unofficial user repositories#valveaur]] 并且一旦你添加了这个仓库,内核软件 {{AUR|linux-fsync}} 和 {{AUR|linux-fsync-headers}} 便可使用。你将可能需要替换某些常用软件包 (例如 {{pkg|nvidia}}) 和 [[DKMS]] 软件包 (例如 {{pkg|nvidia-dkms}})。<br />
* 安装 {{AUR|linux-fsync}} 内核。<br />
* 安装 {{Pkg|linux-zen}} 内核,其从 5.2 版本开始已包括 fsync 补丁。[https://github.com/zen-kernel/zen-kernel/commit/f39367fdbc68e8b1e623239d13db6efaa5a67ae1]<br />
<br />
=== Proton Steam-Play ===<br />
<br />
维尔福公司开发了一个兼容性工具,用来使 Steam 可以在 Wine 和其他额外组件上运行。这使得你可以运行很多只能在 Windows 平台上运行的游戏 (详见 [https://www.protondb.com/ compatibility list])。<br />
<br />
此工具开源并且可以从 [https://github.com/ValveSoftware/Proton/ Github] 获得。Steam 将在 Steam Play 启用后安装它相适应的 Proton 版本。<br />
<br />
Proton 需要在 Steam 客户端启用: {{ic|Steam > 设置 > Steam Play}}。你可以为了上述那些没有被维尔福公司列入白名单的游戏启用 Steam Play。<br />
<br />
如果需要的话,为了在启动游戏时强制启用 Proton 或者指定一个确定的 Proton 版本,在游戏处右击,点击 {{ic|属性 > 常规 > 强制使用特定 Steam Play 兼容性工具}},然后选择所需版本。这样做同样可以用来强制游戏生成一个 Linux 入口用以运行 Windows 版本的游戏。<br />
<br />
你同样可以从 AUR 通过安装 {{AUR|proton}} 或 {{AUR|proton-git}} 来安装 Proton,但是需要一些额外的配置才能使 Steam 良好运行。想要了解 Steam 如何识别已安装的 Proton 的更多细节,可以前往 Proton 的 Github 页面。<br />
<br />
=== 无需窗口管理器的大屏幕模式 ===<br />
<br />
想要从 [[Display manager (简体中文)]] 运行 Steam 的大屏幕模式,你可以选择以下任意一个方案:<br />
<br />
* 安装 {{AUR|steamos-compositor}}<br />
* 或者,安装 {{AUR|steamos-compositor-plus}},这可以隐藏 Proton 游戏启动时恼人的颜色闪烁,并修复游戏在后台运行的问题。<br />
* 手动添加一个 Steam 入口 (''但是你会失去 Steam 的混合平台优势:主要体现在你'''不能'''使用键盘或手柄控制大屏幕模式''):<br />
<br />
创建一个 {{ic|/usr/share/xsessions/steam-big-picture.desktop}} 文件,其中包含:<br />
<br />
{{hc|/usr/share/xsessions/steam-big-picture.desktop|<nowiki><br />
[Desktop Entry]<br />
Name=Steam Big Picture Mode<br />
Comment=Start Steam in Big Picture Mode<br />
Exec=/usr/bin/steam -bigpicture<br />
TryExec=/usr/bin/steam<br />
Icon=<br />
Type=Application</nowiki>}}<br />
<br />
=== Steam skins ===<br />
<br />
The Steam interface can be customized using skins. Skins can overwrite interface-specific files in {{ic|~/.steam/root}}.<br />
<br />
To install a skin:<br />
<br />
# Place its directory in {{ic|~/.steam/root/skins}}.<br />
# Open ''Steam > Settings > Interface'' and select it.<br />
# Restart Steam.<br />
<br />
An extensive list of skins can be found in [http://forums.steampowered.com/forums/showthread.php?t=1161035 this Steam forums post].<br />
<br />
{{Note|Using an outdated skin may cause visual errors.}}<br />
<br />
==== Creating skins ====<br />
<br />
Nearly all Steam styles are defined in {{ic|~/.steam/root/resource/styles/steam.styles}} (the file is over 3,500 lines long). For a skin to be recognized it needs its own {{ic|resource/styles/steam.styles}}.<br />
When a Steam update changes the official {{ic|steam.styles}} your skin may become outdated, potentially resulting in visual errors.<br />
<br />
See {{ic|~/.steam/root/skins/skins_readme.txt}} for a primer on how to create skins.<br />
<br />
=== Changing the Steam notification position ===<br />
<br />
The default Steam notification position is bottom right.<br />
<br />
You can change the Steam notification position by altering {{ic|Notifications.PanelPosition}} in<br />
<br />
* {{ic|resource/styles/steam.styles}} for desktop notifications, and<br />
* {{ic|resource/styles/gameoverlay.styles}} for in-game notifications<br />
<br />
Both files are overwritten by Steam on startup and {{ic|steam.styles}} is only read on startup.<br />
<br />
{{Note|Some games do not respect the setting in {{ic|gameoverlay.styles}} e.g. XCOM: Enemy Unknown.}}<br />
<br />
==== Use a skin ====<br />
<br />
You can create a skin to change the notification position to your liking. For example to change the position to top right:<br />
<br />
$ cd ~/.steam/root/skins<br />
$ mkdir -p Top-Right/resource<br />
$ cp -r ~/.steam/root/resource/styles Top-Right/resource<br />
$ sed -i '/Notifications.PanelPosition/ s/"[A-Za-z]*"/"TopRight"/' Top-Right/resource/styles/*<br />
<br />
==== Live patching ====<br />
<br />
{{ic|gameoverlay.styles}} can be overwritten while Steam is running, allowing you to have game-specific notification positions.<br />
<br />
{{hc|~/.steam/notifpos.sh|<br />
sed -i "/Notifications.PanelPosition/ s/\"[A-Za-z]*\"/\"$1\"/" ~/.steam/root/resource/styles/gameoverlay.styles<br />
}}<br />
<br />
And the [[#Launch options]] should be something like:<br />
<br />
~/.steam/notifpos.sh TopLeft && %command%<br />
<br />
=== Steam Remote Play ===<br />
<br />
{{Note|Steam In-Home Streaming [https://store.steampowered.com/news/51761/ has become Steam Remote Play].}}<br />
<br />
Steam has built-in support for [http://store.steampowered.com/streaming/ remote play].<br />
<br />
See [https://steamcommunity.com/sharedfiles/filedetails/?id=680514371 this Steam Community guide] on how to setup a headless streaming server on Linux.<br />
<br />
==== Different subnets ====<br />
<br />
{{Remove|This workaround/hack seems to be no longer relevant since it became a feature of [https://store.steampowered.com/news/51761/ Steam Remote Play].}}<br />
<br />
Steam client will not be able to detect host if both are on different subnets, which is common case when using VPN to your home network. Even if both client and server can ping each other - steam client would still not be able to detect host, so you need to force it. To do it, start Steam with below command:<br />
<br />
$ steam -console<br />
<br />
Wait until Steam starts. Once it loaded, you will find extra tab named "Console". Open it and then paste below command with correct host IP address:<br />
<br />
connect_remote <host_ip>:27036<br />
<br />
You will see notification that you can now stream games from host machine.<br />
<br />
{{Note|If above doesn't work - Windows is likely blocking all incoming traffic from different subnets, which means any connections coming from VPN tunnel will be dropped. This also can be confirmed by simply performing ping requests without any response to Windows machine from your VPN client. To workaround this, configure (or disable) all Windows firewalls (including existing antiviruses).}}<br />
<br />
{{Tip|See [[Gaming#Remote gaming]] for alternatives if above solution does not work.}}<br />
<br />
=== Steam Controller ===<br />
<br />
Normally a Steam controller requires the use of the Steam-overlay. In non-Steam native Linux games however the overlay may not be practical. For that, while the Steam client is running it will maintain a "desktop configuration". With your Steam controller, configure the desktop configuration for it as a generic XBOX controller. As long as the Steam client is running you can then use your Steam controller in other games, such as GOG games, as an XBOX controller. Make sure to select your type of controller to map to in "general controller settings".<br />
<br />
== Troubleshooting ==<br />
<br />
See [[Steam/Troubleshooting]].<br />
<br />
== See also ==<br />
<br />
* [https://wiki.gentoo.org/wiki/Steam Gentoo Wiki article]<br />
* [https://pcgamingwiki.com/wiki/The_Big_List_of_DRM-Free_Games_on_Steam The Big List of DRM-Free Games on Steam] at PCGamingWiki<br />
* [http://steam.wikia.com/wiki/List_of_DRM-free_games List of DRM-free games] at Wikia<br />
* [http://store.steampowered.com/browse/linux Steam Linux store]<br />
* [https://github.com/ValveSoftware/Proton/ Proton] Compatibility tool for Steam Play based on Wine and additional components.</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=Steam_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=592030
Steam (简体中文)
2019-12-16T15:55:34Z
<p>C0n5t4ntK: /* 提示与技巧 */ 部分翻译完成。</p>
<hr />
<div>[[Category:Gaming (简体中文)]]<br />
[[en:Steam]]<br />
[[ja:Steam]]<br />
[[ru:Steam]]<br />
{{Related articles start (简体中文)}}<br />
{{Related|Steam/Troubleshooting}}<br />
{{Related|Steam/Game-specific troubleshooting}}<br />
{{Related|Gaming}}<br />
{{Related|Gamepad}}<br />
{{Related|List of games (简体中文)}}<br />
{{Related articles end}}<br />
[http://store.steampowered.com/about/ Steam] 是维尔福公司推出的著名游戏分发平台。<br />
<br />
{{注意|对于 Linux 平台,Steam 只支持 Ubuntu 的长期支持版本[https://support.steampowered.com/kb_article.php?ref&#61;1504-QHXN-8366]。 因此,请不要向维尔福公司提交 issue 以获得 Steam 对 Arch Linux 的支持。}}<br />
<br />
== 安装 ==<br />
<br />
启用 [[multilib]] 仓库并[[Help:Reading (简体中文)#安装软件包|安装]] {{Pkg|steam}} 软件包。<br />
<br />
你需要满足下列要求从而在 Arch Linux 上运行 Steam:<br />
<br />
* 安装 32 位版本的 [[Xorg#Driver installation|OpenGL 图形驱动]]。<br />
* 生成 [[Locale#Generating locales|en_US.UTF-8]] 语言环境,以避免非法指针错误。<br />
* 其图形界面大量使用 Arial 字体。详见 [[Microsoft fonts]] 。你可以通过安装 {{Pkg|ttf-liberation}} 或使用 [[Steam/Troubleshooting#Text is corrupt or missing|Steam 支持的字体问题]] 中的方法来解决。<br />
* 安装 {{Pkg|wqy-zenhei}} 以支持亚洲地区语言。<br />
<br />
=== SteamCMD ===<br />
<br />
安装 {{AUR|steamcmd}} 以使用命令行版本的 [https://developer.valvesoftware.com/wiki/SteamCMD Steam]。<br />
<br />
=== 可选 Flatpak 安装 ===<br />
<br />
Steam 也可以作为 {{ic|com.valvesoftware.Steam}} 使用 [[Flatpak]] 从 [https://flathub.org/ Flathub] 中安装。使用 Flathub 仓库和 flatpak 命令行安装是目前最简单的安装方式:<br />
<br />
flatpak --user remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo<br />
flatpak --user install flathub com.valvesoftware.Steam<br />
flatpak run com.valvesoftware.Steam<br />
<br />
目前 Flatpak 应用还不支持主题。并且你不能通过 {{ic|optirun}}/{{ic|primusrun}} 来运行游戏,更多细节详见 [https://github.com/flatpak/flatpak/issues/869 Issue#869]。<br />
<br />
默认情况下 Steam 不会有访问你的家目录的权限,你可以运行下列命令来授予权限,以获得更类似于在 Ubuntu 或 SteamOS 下的运行效果:<br />
<br />
flatpak override com.valvesoftware.Steam --filesystem=$HOME<br />
<br />
==== Flatpak 的亚洲字体问题 ====<br />
<br />
如果你遇到了游戏中无法显示亚洲字体的问题,这是因为 org.freedesktop.Platform 并没有包含合适的字体文件进去。首先尝试挂载你的本地字体:<br />
<br />
flatpak run --filesystems=~/.local/share/fonts --filesystem=~/.config/fontconfig com.valvesoftware.Steam<br />
<br />
如果上述命令不起作用,考虑动手 hack 一下:直接将字体文件复制进 org.freedesktop.Platform 的目录下以启用字体,例如<br />
<br />
# replace ? with your version and hash<br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/etc/fonts/conf.avail<br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/etc/fonts/conf.d <br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/share/fonts<br />
<br />
== 目录结构 ==<br />
<br />
Steam 的默认安装位置是 {{ic|~/.local/share/Steam}}。如果 Steam 无法找到该目录,它会引导你重新安装或选择一个新的安装位置。这篇文章使用 {{ic|~/.steam/root}} 符号链接来表示 Steam 的安装位置。<br />
<br />
=== 库文件夹 ===<br />
<br />
每一个 Steam 应用都有一个独一无二的应用 ID,你可以通过 [http://store.steampowered.com/ Steam Store] 页面路径来找到它。<br />
<br />
Steam 将游戏安装到 {{ic|''LIBRARY''/steamapps/common/}} 目录下。库文件夹 {{ic|''LIBRARY''}} 一般会是<br />
{{ic|~/.steam/root}},但是你依然可以选择拥有多个库文件夹如 (''Steam > Settings > Downloads > Steam Library Folders'')。<br />
<br />
为了 Steam 能够正确识别游戏,它需要在 {{ic|''LIBRARY''/steamapps/}} 目录下找到 {{ic|appmanifest_''AppId''.acf}} 文件。此文件使用了<br />
[https://developer.valvesoftware.com/wiki/KeyValues KeyValues] 格式,并且它的 {{ic|installdir}} 的内容决定了游戏的目录名称。<br />
<br />
== 用法 ==<br />
<br />
steam [ -options ] [ steam:// URL ]<br />
<br />
对于可用的命令行选择,详见 [https://developer.valvesoftware.com/wiki/Command_Line_Options#Steam_.28Windows.29 Command Line Options article on the Valve Developer Wiki]。<br />
<br />
Steam 也可以接受可选的 Steam URL,详见 [https://developer.valvesoftware.com/wiki/Steam_browser_protocol Steam browser procotol]。<br />
<br />
== 启动选项 ==<br />
<br />
当你运行一个 Steam 游戏时,Steam 会使用 [[Bash]] shell 执行它的 '''启动命令'''。<br />
为了让你随意修改启动命令,Steam 提供了 '''启动选项'''。<br />
'''启动选项'''可以通过右键点击你的游戏库中的游戏,选择属性后点击'''设置启动选项'''进行修改。<br />
<br />
默认情况下 Steam 只是简单的把你设置的参数字符串添加到游戏的启动命令后。想要设置环境变量或者将一个启动命令作为参数传递给另一个命令,你可以使用 {{ic|%command%}} 以表示原启动命令。<br />
<br />
=== 实例 ===<br />
<br />
* 仅设置参数: {{ic|-foo}}<br />
* 设置环境变量: {{ic|1=FOO=bar BAZ=bar %command% -baz}}<br />
* 设置与默认完全不同的命令: {{ic|othercommand # %command%}}<br />
<br />
== 提示与技巧 ==<br />
<br />
=== Fsync 补丁 ===<br />
<br />
维尔福公司 [https://steamcommunity.com/app/221410/discussions/0/3158631000006906163/ 发布] 了一个可以帮助提升大量多线程应用运行帧率的特殊内核补丁。这里有一些使用这个补丁的方法:<br />
<br />
* 直接使用维尔福公司提供的二进制内核。详见 [[Unofficial user repositories#valveaur]] 并且一旦你添加了这个仓库,内核软件 {{AUR|linux-fsync}} 和 {{AUR|linux-fsync-headers}} 便可使用。你将可能需要替换某些常用软件包 (例如 {{pkg|nvidia}}) 和 [[DKMS]] 软件包 (例如 {{pkg|nvidia-dkms}})。<br />
* 安装 {{AUR|linux-fsync}} 内核。<br />
* 安装 {{Pkg|linux-zen}} 内核,其从 5.2 版本开始已包括 fsync 补丁。[https://github.com/zen-kernel/zen-kernel/commit/f39367fdbc68e8b1e623239d13db6efaa5a67ae1]<br />
<br />
=== Proton Steam-Play ===<br />
<br />
维尔福公司开发了一个兼容性工具,用来使 Steam 可以在 Wine 和其他额外组件上运行。这使得你可以运行很多只能在 Windows 平台上运行的游戏 (详见 [https://www.protondb.com/ compatibility list])。<br />
<br />
此工具开源并且可以从 [https://github.com/ValveSoftware/Proton/ Github] 获得。Steam 将在 Steam Play 启用后安装它相适应的 Proton 版本。<br />
<br />
Proton 需要在 Steam 客户端启用: {{ic|Steam > 设置 > Steam Play}}。你可以为了上述那些没有被维尔福公司列入白名单的游戏启用 Steam Play。<br />
<br />
如果需要的话,为了在启动游戏时强制启用 Proton 或者指定一个确定的 Proton 版本,在游戏处右击,点击 {{ic|属性 > 常规 > 强制使用特定 Steam Play 兼容性工具}},然后选择所需版本。这样做同样可以用来强制游戏生成一个 Linux 入口用以运行 Windows 版本的游戏。<br />
<br />
你同样可以从 AUR 通过安装 {{AUR|proton}} 或 {{AUR|proton-git}} 来安装 Proton,但是需要一些额外的配置才能使 Steam 良好运行。欲了解 Steam 如何识别已安装的 Proton 的更多细节,可以前往 Proton 的 Github 页面。<br />
<br />
=== Big Picture Mode without a window manager ===<br />
<br />
To start Steam in Big Picture Mode from a [[Display manager]], you can either:<br />
<br />
* Install {{AUR|steamos-compositor}}<br />
* Alternatively, install {{AUR|steamos-compositor-plus}}, which hides the annoying color flashing on startup of Proton games and adds a fix for games that start in the background<br />
* Manually add a Steam entry (''but you lose the steam compositor advantages: mainly you '''can't''' control Big Picture mode with keyboard or gamepad''):<br />
<br />
create a {{ic|/usr/share/xsessions/steam-big-picture.desktop}} file with the following contents: <br />
<br />
{{hc|/usr/share/xsessions/steam-big-picture.desktop|<nowiki><br />
[Desktop Entry]<br />
Name=Steam Big Picture Mode<br />
Comment=Start Steam in Big Picture Mode<br />
Exec=/usr/bin/steam -bigpicture<br />
TryExec=/usr/bin/steam<br />
Icon=<br />
Type=Application</nowiki>}}<br />
<br />
=== Steam skins ===<br />
<br />
The Steam interface can be customized using skins. Skins can overwrite interface-specific files in {{ic|~/.steam/root}}.<br />
<br />
To install a skin:<br />
<br />
# Place its directory in {{ic|~/.steam/root/skins}}.<br />
# Open ''Steam > Settings > Interface'' and select it.<br />
# Restart Steam.<br />
<br />
An extensive list of skins can be found in [http://forums.steampowered.com/forums/showthread.php?t=1161035 this Steam forums post].<br />
<br />
{{Note|Using an outdated skin may cause visual errors.}}<br />
<br />
==== Creating skins ====<br />
<br />
Nearly all Steam styles are defined in {{ic|~/.steam/root/resource/styles/steam.styles}} (the file is over 3,500 lines long). For a skin to be recognized it needs its own {{ic|resource/styles/steam.styles}}.<br />
When a Steam update changes the official {{ic|steam.styles}} your skin may become outdated, potentially resulting in visual errors.<br />
<br />
See {{ic|~/.steam/root/skins/skins_readme.txt}} for a primer on how to create skins.<br />
<br />
=== Changing the Steam notification position ===<br />
<br />
The default Steam notification position is bottom right.<br />
<br />
You can change the Steam notification position by altering {{ic|Notifications.PanelPosition}} in<br />
<br />
* {{ic|resource/styles/steam.styles}} for desktop notifications, and<br />
* {{ic|resource/styles/gameoverlay.styles}} for in-game notifications<br />
<br />
Both files are overwritten by Steam on startup and {{ic|steam.styles}} is only read on startup.<br />
<br />
{{Note|Some games do not respect the setting in {{ic|gameoverlay.styles}} e.g. XCOM: Enemy Unknown.}}<br />
<br />
==== Use a skin ====<br />
<br />
You can create a skin to change the notification position to your liking. For example to change the position to top right:<br />
<br />
$ cd ~/.steam/root/skins<br />
$ mkdir -p Top-Right/resource<br />
$ cp -r ~/.steam/root/resource/styles Top-Right/resource<br />
$ sed -i '/Notifications.PanelPosition/ s/"[A-Za-z]*"/"TopRight"/' Top-Right/resource/styles/*<br />
<br />
==== Live patching ====<br />
<br />
{{ic|gameoverlay.styles}} can be overwritten while Steam is running, allowing you to have game-specific notification positions.<br />
<br />
{{hc|~/.steam/notifpos.sh|<br />
sed -i "/Notifications.PanelPosition/ s/\"[A-Za-z]*\"/\"$1\"/" ~/.steam/root/resource/styles/gameoverlay.styles<br />
}}<br />
<br />
And the [[#Launch options]] should be something like:<br />
<br />
~/.steam/notifpos.sh TopLeft && %command%<br />
<br />
=== Steam Remote Play ===<br />
<br />
{{Note|Steam In-Home Streaming [https://store.steampowered.com/news/51761/ has become Steam Remote Play].}}<br />
<br />
Steam has built-in support for [http://store.steampowered.com/streaming/ remote play].<br />
<br />
See [https://steamcommunity.com/sharedfiles/filedetails/?id=680514371 this Steam Community guide] on how to setup a headless streaming server on Linux.<br />
<br />
==== Different subnets ====<br />
<br />
{{Remove|This workaround/hack seems to be no longer relevant since it became a feature of [https://store.steampowered.com/news/51761/ Steam Remote Play].}}<br />
<br />
Steam client will not be able to detect host if both are on different subnets, which is common case when using VPN to your home network. Even if both client and server can ping each other - steam client would still not be able to detect host, so you need to force it. To do it, start Steam with below command:<br />
<br />
$ steam -console<br />
<br />
Wait until Steam starts. Once it loaded, you will find extra tab named "Console". Open it and then paste below command with correct host IP address:<br />
<br />
connect_remote <host_ip>:27036<br />
<br />
You will see notification that you can now stream games from host machine.<br />
<br />
{{Note|If above doesn't work - Windows is likely blocking all incoming traffic from different subnets, which means any connections coming from VPN tunnel will be dropped. This also can be confirmed by simply performing ping requests without any response to Windows machine from your VPN client. To workaround this, configure (or disable) all Windows firewalls (including existing antiviruses).}}<br />
<br />
{{Tip|See [[Gaming#Remote gaming]] for alternatives if above solution does not work.}}<br />
<br />
=== Steam Controller ===<br />
<br />
Normally a Steam controller requires the use of the Steam-overlay. In non-Steam native Linux games however the overlay may not be practical. For that, while the Steam client is running it will maintain a "desktop configuration". With your Steam controller, configure the desktop configuration for it as a generic XBOX controller. As long as the Steam client is running you can then use your Steam controller in other games, such as GOG games, as an XBOX controller. Make sure to select your type of controller to map to in "general controller settings".<br />
<br />
== Troubleshooting ==<br />
<br />
See [[Steam/Troubleshooting]].<br />
<br />
== See also ==<br />
<br />
* [https://wiki.gentoo.org/wiki/Steam Gentoo Wiki article]<br />
* [https://pcgamingwiki.com/wiki/The_Big_List_of_DRM-Free_Games_on_Steam The Big List of DRM-Free Games on Steam] at PCGamingWiki<br />
* [http://steam.wikia.com/wiki/List_of_DRM-free_games List of DRM-free games] at Wikia<br />
* [http://store.steampowered.com/browse/linux Steam Linux store]<br />
* [https://github.com/ValveSoftware/Proton/ Proton] Compatibility tool for Steam Play based on Wine and additional components.</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=Steam_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=591756
Steam (简体中文)
2019-12-14T04:22:48Z
<p>C0n5t4ntK: /* 用法 */ 用法部分翻译完成;/* 启动选项 */ 启动选项部分翻译完成。</p>
<hr />
<div>[[Category:Gaming (简体中文)]]<br />
[[en:Steam]]<br />
[[ja:Steam]]<br />
[[ru:Steam]]<br />
{{Related articles start (简体中文)}}<br />
{{Related|Steam/Troubleshooting}}<br />
{{Related|Steam/Game-specific troubleshooting}}<br />
{{Related|Gaming}}<br />
{{Related|Gamepad}}<br />
{{Related|List of games (简体中文)}}<br />
{{Related articles end}}<br />
[http://store.steampowered.com/about/ Steam] 是维尔福公司推出的著名游戏分发平台。<br />
<br />
{{注意|对于 Linux 平台,Steam 只支持 Ubuntu 的长期支持版本[https://support.steampowered.com/kb_article.php?ref&#61;1504-QHXN-8366]。 因此,请不要向维尔福公司提交 issue 以获得 Steam 对 Arch Linux 的支持。}}<br />
<br />
== 安装 ==<br />
<br />
启用 [[multilib]] 仓库并[[Help:Reading (简体中文)#安装软件包|安装]] {{Pkg|steam}} 软件包。<br />
<br />
你需要满足下列要求从而在 Arch Linux 上运行 Steam:<br />
<br />
* 安装 32 位版本的 [[Xorg#Driver installation|OpenGL 图形驱动]]。<br />
* 生成 [[Locale#Generating locales|en_US.UTF-8]] 语言环境,以避免非法指针错误。<br />
* 其图形界面大量使用 Arial 字体。详见 [[Microsoft fonts]] 。你可以通过安装 {{Pkg|ttf-liberation}} 或使用 [[Steam/Troubleshooting#Text is corrupt or missing|Steam 支持的字体问题]] 中的方法来解决。<br />
* 安装 {{Pkg|wqy-zenhei}} 以支持亚洲地区语言。<br />
<br />
=== SteamCMD ===<br />
<br />
安装 {{AUR|steamcmd}} 以使用命令行版本的 [https://developer.valvesoftware.com/wiki/SteamCMD Steam]。<br />
<br />
=== 可选 Flatpak 安装 ===<br />
<br />
Steam 也可以作为 {{ic|com.valvesoftware.Steam}} 使用 [[Flatpak]] 从 [https://flathub.org/ Flathub] 中安装。使用 Flathub 仓库和 flatpak 命令行安装是目前最简单的安装方式:<br />
<br />
flatpak --user remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo<br />
flatpak --user install flathub com.valvesoftware.Steam<br />
flatpak run com.valvesoftware.Steam<br />
<br />
目前 Flatpak 应用还不支持主题。并且你不能通过 {{ic|optirun}}/{{ic|primusrun}} 来运行游戏,更多细节详见 [https://github.com/flatpak/flatpak/issues/869 Issue#869]。<br />
<br />
默认情况下 Steam 不会有访问你的家目录的权限,你可以运行下列命令来授予权限,以获得更类似于在 Ubuntu 或 SteamOS 下的运行效果:<br />
<br />
flatpak override com.valvesoftware.Steam --filesystem=$HOME<br />
<br />
==== Flatpak 的亚洲字体问题 ====<br />
<br />
如果你遇到了游戏中无法显示亚洲字体的问题,这是因为 org.freedesktop.Platform 并没有包含合适的字体文件进去。首先尝试挂载你的本地字体:<br />
<br />
flatpak run --filesystems=~/.local/share/fonts --filesystem=~/.config/fontconfig com.valvesoftware.Steam<br />
<br />
如果上述命令不起作用,考虑动手 hack 一下:直接将字体文件复制进 org.freedesktop.Platform 的目录下以启用字体,例如<br />
<br />
# replace ? with your version and hash<br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/etc/fonts/conf.avail<br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/etc/fonts/conf.d <br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/share/fonts<br />
<br />
== 目录结构 ==<br />
<br />
Steam 的默认安装位置是 {{ic|~/.local/share/Steam}}。如果 Steam 无法找到该目录,它会引导你重新安装或选择一个新的安装位置。这篇文章使用 {{ic|~/.steam/root}} 符号链接来表示 Steam 的安装位置。<br />
<br />
=== 库文件夹 ===<br />
<br />
每一个 Steam 应用都有一个独一无二的应用 ID,你可以通过 [http://store.steampowered.com/ Steam Store] 页面路径来找到它。<br />
<br />
Steam 将游戏安装到 {{ic|''LIBRARY''/steamapps/common/}} 目录下。库文件夹 {{ic|''LIBRARY''}} 一般会是<br />
{{ic|~/.steam/root}},但是你依然可以选择拥有多个库文件夹如 (''Steam > Settings > Downloads > Steam Library Folders'')。<br />
<br />
为了 Steam 能够正确识别游戏,它需要在 {{ic|''LIBRARY''/steamapps/}} 目录下找到 {{ic|appmanifest_''AppId''.acf}} 文件。此文件使用了<br />
[https://developer.valvesoftware.com/wiki/KeyValues KeyValues] 格式,并且它的 {{ic|installdir}} 的内容决定了游戏的目录名称。<br />
<br />
== 用法 ==<br />
<br />
steam [ -options ] [ steam:// URL ]<br />
<br />
对于可用的命令行选择,详见 [https://developer.valvesoftware.com/wiki/Command_Line_Options#Steam_.28Windows.29 Command Line Options article on the Valve Developer Wiki]。<br />
<br />
Steam 也可以接受可选的 Steam URL,详见 [https://developer.valvesoftware.com/wiki/Steam_browser_protocol Steam browser procotol]。<br />
<br />
== 启动选项 ==<br />
<br />
当你运行一个 Steam 游戏时,Steam 会使用 [[Bash]] shell 执行它的 '''启动命令'''。<br />
为了让你随意修改启动命令,Steam 提供了 '''启动选项'''。<br />
'''启动选项'''可以通过右键点击你的游戏库中的游戏,选择属性后点击'''设置启动选项'''进行修改。<br />
<br />
默认情况下 Steam 只是简单的把你设置的参数字符串添加到游戏的启动命令后。想要设置环境变量或者将一个启动命令作为参数传递给另一个命令,你可以使用 {{ic|%command%}} 以表示原启动命令。<br />
<br />
=== 实例 ===<br />
<br />
* 仅设置参数: {{ic|-foo}}<br />
* 设置环境变量: {{ic|1=FOO=bar BAZ=bar %command% -baz}}<br />
* 设置与默认完全不同的命令: {{ic|othercommand # %command%}}<br />
<br />
== Tips and tricks ==<br />
<br />
=== Fsync patch ===<br />
<br />
Valve has [https://steamcommunity.com/app/221410/discussions/0/3158631000006906163/ released] a special kernel patch that should help increase FPS in massively-threaded applications. There are few methods to get and use this patch:<br />
<br />
* Use binary kernel provided directly from Valve. See [[Unofficial user repositories#valveaur]] and once you add this repository, kernel packages {{AUR|linux-fsync}} and {{AUR|linux-fsync-headers}} become available. You will likely need to replace some regular packages (e.g. {{pkg|nvidia}}) with [[DKMS]] packages (e.g. {{pkg|nvidia-dkms}}) as well.<br />
* Install {{AUR|linux-fsync}} kernel.<br />
* Install {{Pkg|linux-zen}} kernel that includes the fsync patches since the 5.2 release[https://github.com/zen-kernel/zen-kernel/commit/f39367fdbc68e8b1e623239d13db6efaa5a67ae1]<br />
<br />
=== Proton Steam-Play ===<br />
<br />
Valve developed a compatibility tool for Steam Play based on Wine and additional components. It allows you to launch many Windows games (see [https://www.protondb.com/ compatibility list]).<br />
<br />
It's open-source and available on [https://github.com/ValveSoftware/Proton/ Github]. Steam will install its own versions of Proton when Steam Play is enabled.<br />
<br />
Proton needs to be enabled on Steam client : {{ic|Steam > Settings > Steam Play}}. You can enable Steam Play for games that have and have not been whitelisted by Valve in that dialog.<br />
<br />
If needed, to force enable Proton or a specific version of Proton for a game, right click on the game, click {{ic|Properties > General > Force the use of a specific Steam Play compatibility tool}}, and select the desired version. Doing so can also be used to force games that have a Linux port to use the Windows version.<br />
<br />
You can also install Proton from AUR with {{AUR|proton}} or {{AUR|proton-git}}, but extra setup is required for them to work with Steam. See the Proton Github for details on how Steam recognizes Proton installs.<br />
<br />
=== Big Picture Mode without a window manager ===<br />
<br />
To start Steam in Big Picture Mode from a [[Display manager]], you can either:<br />
<br />
* Install {{AUR|steamos-compositor}}<br />
* Alternatively, install {{AUR|steamos-compositor-plus}}, which hides the annoying color flashing on startup of Proton games and adds a fix for games that start in the background<br />
* Manually add a Steam entry (''but you lose the steam compositor advantages: mainly you '''can't''' control Big Picture mode with keyboard or gamepad''):<br />
<br />
create a {{ic|/usr/share/xsessions/steam-big-picture.desktop}} file with the following contents: <br />
<br />
{{hc|/usr/share/xsessions/steam-big-picture.desktop|<nowiki><br />
[Desktop Entry]<br />
Name=Steam Big Picture Mode<br />
Comment=Start Steam in Big Picture Mode<br />
Exec=/usr/bin/steam -bigpicture<br />
TryExec=/usr/bin/steam<br />
Icon=<br />
Type=Application</nowiki>}}<br />
<br />
=== Steam skins ===<br />
<br />
The Steam interface can be customized using skins. Skins can overwrite interface-specific files in {{ic|~/.steam/root}}.<br />
<br />
To install a skin:<br />
<br />
# Place its directory in {{ic|~/.steam/root/skins}}.<br />
# Open ''Steam > Settings > Interface'' and select it.<br />
# Restart Steam.<br />
<br />
An extensive list of skins can be found in [http://forums.steampowered.com/forums/showthread.php?t=1161035 this Steam forums post].<br />
<br />
{{Note|Using an outdated skin may cause visual errors.}}<br />
<br />
==== Creating skins ====<br />
<br />
Nearly all Steam styles are defined in {{ic|~/.steam/root/resource/styles/steam.styles}} (the file is over 3,500 lines long). For a skin to be recognized it needs its own {{ic|resource/styles/steam.styles}}.<br />
When a Steam update changes the official {{ic|steam.styles}} your skin may become outdated, potentially resulting in visual errors.<br />
<br />
See {{ic|~/.steam/root/skins/skins_readme.txt}} for a primer on how to create skins.<br />
<br />
=== Changing the Steam notification position ===<br />
<br />
The default Steam notification position is bottom right.<br />
<br />
You can change the Steam notification position by altering {{ic|Notifications.PanelPosition}} in<br />
<br />
* {{ic|resource/styles/steam.styles}} for desktop notifications, and<br />
* {{ic|resource/styles/gameoverlay.styles}} for in-game notifications<br />
<br />
Both files are overwritten by Steam on startup and {{ic|steam.styles}} is only read on startup.<br />
<br />
{{Note|Some games do not respect the setting in {{ic|gameoverlay.styles}} e.g. XCOM: Enemy Unknown.}}<br />
<br />
==== Use a skin ====<br />
<br />
You can create a skin to change the notification position to your liking. For example to change the position to top right:<br />
<br />
$ cd ~/.steam/root/skins<br />
$ mkdir -p Top-Right/resource<br />
$ cp -r ~/.steam/root/resource/styles Top-Right/resource<br />
$ sed -i '/Notifications.PanelPosition/ s/"[A-Za-z]*"/"TopRight"/' Top-Right/resource/styles/*<br />
<br />
==== Live patching ====<br />
<br />
{{ic|gameoverlay.styles}} can be overwritten while Steam is running, allowing you to have game-specific notification positions.<br />
<br />
{{hc|~/.steam/notifpos.sh|<br />
sed -i "/Notifications.PanelPosition/ s/\"[A-Za-z]*\"/\"$1\"/" ~/.steam/root/resource/styles/gameoverlay.styles<br />
}}<br />
<br />
And the [[#Launch options]] should be something like:<br />
<br />
~/.steam/notifpos.sh TopLeft && %command%<br />
<br />
=== Steam Remote Play ===<br />
<br />
{{Note|Steam In-Home Streaming [https://store.steampowered.com/news/51761/ has become Steam Remote Play].}}<br />
<br />
Steam has built-in support for [http://store.steampowered.com/streaming/ remote play].<br />
<br />
See [https://steamcommunity.com/sharedfiles/filedetails/?id=680514371 this Steam Community guide] on how to setup a headless streaming server on Linux.<br />
<br />
==== Different subnets ====<br />
<br />
{{Remove|This workaround/hack seems to be no longer relevant since it became a feature of [https://store.steampowered.com/news/51761/ Steam Remote Play].}}<br />
<br />
Steam client will not be able to detect host if both are on different subnets, which is common case when using VPN to your home network. Even if both client and server can ping each other - steam client would still not be able to detect host, so you need to force it. To do it, start Steam with below command:<br />
<br />
$ steam -console<br />
<br />
Wait until Steam starts. Once it loaded, you will find extra tab named "Console". Open it and then paste below command with correct host IP address:<br />
<br />
connect_remote <host_ip>:27036<br />
<br />
You will see notification that you can now stream games from host machine.<br />
<br />
{{Note|If above doesn't work - Windows is likely blocking all incoming traffic from different subnets, which means any connections coming from VPN tunnel will be dropped. This also can be confirmed by simply performing ping requests without any response to Windows machine from your VPN client. To workaround this, configure (or disable) all Windows firewalls (including existing antiviruses).}}<br />
<br />
{{Tip|See [[Gaming#Remote gaming]] for alternatives if above solution does not work.}}<br />
<br />
=== Steam Controller ===<br />
<br />
Normally a Steam controller requires the use of the Steam-overlay. In non-Steam native Linux games however the overlay may not be practical. For that, while the Steam client is running it will maintain a "desktop configuration". With your Steam controller, configure the desktop configuration for it as a generic XBOX controller. As long as the Steam client is running you can then use your Steam controller in other games, such as GOG games, as an XBOX controller. Make sure to select your type of controller to map to in "general controller settings".<br />
<br />
== Troubleshooting ==<br />
<br />
See [[Steam/Troubleshooting]].<br />
<br />
== See also ==<br />
<br />
* [https://wiki.gentoo.org/wiki/Steam Gentoo Wiki article]<br />
* [https://pcgamingwiki.com/wiki/The_Big_List_of_DRM-Free_Games_on_Steam The Big List of DRM-Free Games on Steam] at PCGamingWiki<br />
* [http://steam.wikia.com/wiki/List_of_DRM-free_games List of DRM-free games] at Wikia<br />
* [http://store.steampowered.com/browse/linux Steam Linux store]<br />
* [https://github.com/ValveSoftware/Proton/ Proton] Compatibility tool for Steam Play based on Wine and additional components.</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=Steam_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=591655
Steam (简体中文)
2019-12-13T03:29:23Z
<p>C0n5t4ntK: /* 目录结构 */ 目录结构部分翻译完成。</p>
<hr />
<div>[[Category:Gaming (简体中文)]]<br />
[[en:Steam]]<br />
[[ja:Steam]]<br />
[[ru:Steam]]<br />
{{Related articles start (简体中文)}}<br />
{{Related|Steam/Troubleshooting}}<br />
{{Related|Steam/Game-specific troubleshooting}}<br />
{{Related|Gaming}}<br />
{{Related|Gamepad}}<br />
{{Related|List of games (简体中文)}}<br />
{{Related articles end}}<br />
[http://store.steampowered.com/about/ Steam] 是维尔福公司推出的著名游戏分发平台。<br />
<br />
{{注意|对于 Linux 平台,Steam 只支持 Ubuntu 的长期支持版本[https://support.steampowered.com/kb_article.php?ref&#61;1504-QHXN-8366]。 因此,请不要向维尔福公司提交 issue 以获得 Steam 对 Arch Linux 的支持。}}<br />
<br />
== 安装 ==<br />
<br />
启用 [[multilib]] 仓库并[[Help:Reading (简体中文)#安装软件包|安装]] {{Pkg|steam}} 软件包。<br />
<br />
你需要满足下列要求从而在 Arch Linux 上运行 Steam:<br />
<br />
* 安装 32 位版本的 [[Xorg#Driver installation|OpenGL 图形驱动]]。<br />
* 生成 [[Locale#Generating locales|en_US.UTF-8]] 语言环境,以避免非法指针错误。<br />
* 其图形界面大量使用 Arial 字体。详见 [[Microsoft fonts]] 。你可以通过安装 {{Pkg|ttf-liberation}} 或使用 [[Steam/Troubleshooting#Text is corrupt or missing|Steam 支持的字体问题]] 中的方法来解决。<br />
* 安装 {{Pkg|wqy-zenhei}} 以支持亚洲地区语言。<br />
<br />
=== SteamCMD ===<br />
<br />
安装 {{AUR|steamcmd}} 以使用命令行版本的 [https://developer.valvesoftware.com/wiki/SteamCMD Steam]。<br />
<br />
=== 可选 Flatpak 安装 ===<br />
<br />
Steam 也可以作为 {{ic|com.valvesoftware.Steam}} 使用 [[Flatpak]] 从 [https://flathub.org/ Flathub] 中安装。使用 Flathub 仓库和 flatpak 命令行安装是目前最简单的安装方式:<br />
<br />
flatpak --user remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo<br />
flatpak --user install flathub com.valvesoftware.Steam<br />
flatpak run com.valvesoftware.Steam<br />
<br />
目前 Flatpak 应用还不支持主题。并且你不能通过 {{ic|optirun}}/{{ic|primusrun}} 来运行游戏,更多细节详见 [https://github.com/flatpak/flatpak/issues/869 Issue#869]。<br />
<br />
默认情况下 Steam 不会有访问你的家目录的权限,你可以运行下列命令来授予权限,以获得更类似于在 Ubuntu 或 SteamOS 下的运行效果:<br />
<br />
flatpak override com.valvesoftware.Steam --filesystem=$HOME<br />
<br />
==== Flatpak 的亚洲字体问题 ====<br />
<br />
如果你遇到了游戏中无法显示亚洲字体的问题,这是因为 org.freedesktop.Platform 并没有包含合适的字体文件进去。首先尝试挂载你的本地字体:<br />
<br />
flatpak run --filesystems=~/.local/share/fonts --filesystem=~/.config/fontconfig com.valvesoftware.Steam<br />
<br />
如果上述命令不起作用,考虑动手 hack 一下:直接将字体文件复制进 org.freedesktop.Platform 的目录下以启用字体,例如<br />
<br />
# replace ? with your version and hash<br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/etc/fonts/conf.avail<br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/etc/fonts/conf.d <br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/share/fonts<br />
<br />
== 目录结构 ==<br />
<br />
Steam 的默认安装位置是 {{ic|~/.local/share/Steam}}。如果 Steam 无法找到该目录,它会引导你重新安装或选择一个新的安装位置。这篇文章使用 {{ic|~/.steam/root}} 符号链接来表示 Steam 的安装位置。<br />
<br />
=== 库文件夹 ===<br />
<br />
每一个 Steam 应用都有一个独一无二的应用 ID,你可以通过 [http://store.steampowered.com/ Steam Store] 页面路径来找到它。<br />
<br />
Steam 将游戏安装到 {{ic|''LIBRARY''/steamapps/common/}} 目录下。库文件夹 {{ic|''LIBRARY''}} 一般会是<br />
{{ic|~/.steam/root}},但是你依然可以选择拥有多个库文件夹如 (''Steam > Settings > Downloads > Steam Library Folders'')。<br />
<br />
为了 Steam 能够正确识别游戏,它需要在 {{ic|''LIBRARY''/steamapps/}} 目录下找到 {{ic|appmanifest_''AppId''.acf}} 文件。此文件使用了<br />
[https://developer.valvesoftware.com/wiki/KeyValues KeyValues] 格式,并且它的 {{ic|installdir}} 的内容决定了游戏的目录名称。<br />
<br />
== Usage ==<br />
<br />
steam [ -options ] [ steam:// URL ]<br />
<br />
For the available command-line options see the [https://developer.valvesoftware.com/wiki/Command_Line_Options#Steam_.28Windows.29 Command Line Options article on the Valve Developer Wiki].<br />
<br />
Steam also accepts an optional Steam URL, see the [https://developer.valvesoftware.com/wiki/Steam_browser_protocol Steam browser procotol].<br />
<br />
== Launch options ==<br />
<br />
When you launch a Steam game, Steam executes its '''launch command''' in a [[Bash]] shell.<br />
To let you alter the launch command Steam provides '''launch options''',<br />
which can be set for a game by right-clicking on it in your library, selecting Properties and clicking on ''Set Launch Options''.<br />
<br />
By default Steam simply appends your option string to the launch command. To set environment variables or<br />
pass the launch command as an argument to another command you can use the {{ic|%command%}} substitute.<br />
<br />
=== Examples ===<br />
<br />
* only arguments: {{ic|-foo}}<br />
* environment variables: {{ic|1=FOO=bar BAZ=bar %command% -baz}}<br />
* completely different command: {{ic|othercommand # %command%}}<br />
<br />
== Tips and tricks ==<br />
<br />
=== Fsync patch ===<br />
<br />
Valve has [https://steamcommunity.com/app/221410/discussions/0/3158631000006906163/ released] a special kernel patch that should help increase FPS in massively-threaded applications. There are few methods to get and use this patch:<br />
<br />
* Use binary kernel provided directly from Valve. See [[Unofficial user repositories#valveaur]] and once you add this repository, kernel packages {{AUR|linux-fsync}} and {{AUR|linux-fsync-headers}} become available. You will likely need to replace some regular packages (e.g. {{pkg|nvidia}}) with [[DKMS]] packages (e.g. {{pkg|nvidia-dkms}}) as well.<br />
* Install {{AUR|linux-fsync}} kernel.<br />
* Install {{Pkg|linux-zen}} kernel that includes the fsync patches since the 5.2 release[https://github.com/zen-kernel/zen-kernel/commit/f39367fdbc68e8b1e623239d13db6efaa5a67ae1]<br />
<br />
=== Proton Steam-Play ===<br />
<br />
Valve developed a compatibility tool for Steam Play based on Wine and additional components. It allows you to launch many Windows games (see [https://www.protondb.com/ compatibility list]).<br />
<br />
It's open-source and available on [https://github.com/ValveSoftware/Proton/ Github]. Steam will install its own versions of Proton when Steam Play is enabled.<br />
<br />
Proton needs to be enabled on Steam client : {{ic|Steam > Settings > Steam Play}}. You can enable Steam Play for games that have and have not been whitelisted by Valve in that dialog.<br />
<br />
If needed, to force enable Proton or a specific version of Proton for a game, right click on the game, click {{ic|Properties > General > Force the use of a specific Steam Play compatibility tool}}, and select the desired version. Doing so can also be used to force games that have a Linux port to use the Windows version.<br />
<br />
You can also install Proton from AUR with {{AUR|proton}} or {{AUR|proton-git}}, but extra setup is required for them to work with Steam. See the Proton Github for details on how Steam recognizes Proton installs.<br />
<br />
=== Big Picture Mode without a window manager ===<br />
<br />
To start Steam in Big Picture Mode from a [[Display manager]], you can either:<br />
<br />
* Install {{AUR|steamos-compositor}}<br />
* Alternatively, install {{AUR|steamos-compositor-plus}}, which hides the annoying color flashing on startup of Proton games and adds a fix for games that start in the background<br />
* Manually add a Steam entry (''but you lose the steam compositor advantages: mainly you '''can't''' control Big Picture mode with keyboard or gamepad''):<br />
<br />
create a {{ic|/usr/share/xsessions/steam-big-picture.desktop}} file with the following contents: <br />
<br />
{{hc|/usr/share/xsessions/steam-big-picture.desktop|<nowiki><br />
[Desktop Entry]<br />
Name=Steam Big Picture Mode<br />
Comment=Start Steam in Big Picture Mode<br />
Exec=/usr/bin/steam -bigpicture<br />
TryExec=/usr/bin/steam<br />
Icon=<br />
Type=Application</nowiki>}}<br />
<br />
=== Steam skins ===<br />
<br />
The Steam interface can be customized using skins. Skins can overwrite interface-specific files in {{ic|~/.steam/root}}.<br />
<br />
To install a skin:<br />
<br />
# Place its directory in {{ic|~/.steam/root/skins}}.<br />
# Open ''Steam > Settings > Interface'' and select it.<br />
# Restart Steam.<br />
<br />
An extensive list of skins can be found in [http://forums.steampowered.com/forums/showthread.php?t=1161035 this Steam forums post].<br />
<br />
{{Note|Using an outdated skin may cause visual errors.}}<br />
<br />
==== Creating skins ====<br />
<br />
Nearly all Steam styles are defined in {{ic|~/.steam/root/resource/styles/steam.styles}} (the file is over 3,500 lines long). For a skin to be recognized it needs its own {{ic|resource/styles/steam.styles}}.<br />
When a Steam update changes the official {{ic|steam.styles}} your skin may become outdated, potentially resulting in visual errors.<br />
<br />
See {{ic|~/.steam/root/skins/skins_readme.txt}} for a primer on how to create skins.<br />
<br />
=== Changing the Steam notification position ===<br />
<br />
The default Steam notification position is bottom right.<br />
<br />
You can change the Steam notification position by altering {{ic|Notifications.PanelPosition}} in<br />
<br />
* {{ic|resource/styles/steam.styles}} for desktop notifications, and<br />
* {{ic|resource/styles/gameoverlay.styles}} for in-game notifications<br />
<br />
Both files are overwritten by Steam on startup and {{ic|steam.styles}} is only read on startup.<br />
<br />
{{Note|Some games do not respect the setting in {{ic|gameoverlay.styles}} e.g. XCOM: Enemy Unknown.}}<br />
<br />
==== Use a skin ====<br />
<br />
You can create a skin to change the notification position to your liking. For example to change the position to top right:<br />
<br />
$ cd ~/.steam/root/skins<br />
$ mkdir -p Top-Right/resource<br />
$ cp -r ~/.steam/root/resource/styles Top-Right/resource<br />
$ sed -i '/Notifications.PanelPosition/ s/"[A-Za-z]*"/"TopRight"/' Top-Right/resource/styles/*<br />
<br />
==== Live patching ====<br />
<br />
{{ic|gameoverlay.styles}} can be overwritten while Steam is running, allowing you to have game-specific notification positions.<br />
<br />
{{hc|~/.steam/notifpos.sh|<br />
sed -i "/Notifications.PanelPosition/ s/\"[A-Za-z]*\"/\"$1\"/" ~/.steam/root/resource/styles/gameoverlay.styles<br />
}}<br />
<br />
And the [[#Launch options]] should be something like:<br />
<br />
~/.steam/notifpos.sh TopLeft && %command%<br />
<br />
=== Steam Remote Play ===<br />
<br />
{{Note|Steam In-Home Streaming [https://store.steampowered.com/news/51761/ has become Steam Remote Play].}}<br />
<br />
Steam has built-in support for [http://store.steampowered.com/streaming/ remote play].<br />
<br />
See [https://steamcommunity.com/sharedfiles/filedetails/?id=680514371 this Steam Community guide] on how to setup a headless streaming server on Linux.<br />
<br />
==== Different subnets ====<br />
<br />
{{Remove|This workaround/hack seems to be no longer relevant since it became a feature of [https://store.steampowered.com/news/51761/ Steam Remote Play].}}<br />
<br />
Steam client will not be able to detect host if both are on different subnets, which is common case when using VPN to your home network. Even if both client and server can ping each other - steam client would still not be able to detect host, so you need to force it. To do it, start Steam with below command:<br />
<br />
$ steam -console<br />
<br />
Wait until Steam starts. Once it loaded, you will find extra tab named "Console". Open it and then paste below command with correct host IP address:<br />
<br />
connect_remote <host_ip>:27036<br />
<br />
You will see notification that you can now stream games from host machine.<br />
<br />
{{Note|If above doesn't work - Windows is likely blocking all incoming traffic from different subnets, which means any connections coming from VPN tunnel will be dropped. This also can be confirmed by simply performing ping requests without any response to Windows machine from your VPN client. To workaround this, configure (or disable) all Windows firewalls (including existing antiviruses).}}<br />
<br />
{{Tip|See [[Gaming#Remote gaming]] for alternatives if above solution does not work.}}<br />
<br />
=== Steam Controller ===<br />
<br />
Normally a Steam controller requires the use of the Steam-overlay. In non-Steam native Linux games however the overlay may not be practical. For that, while the Steam client is running it will maintain a "desktop configuration". With your Steam controller, configure the desktop configuration for it as a generic XBOX controller. As long as the Steam client is running you can then use your Steam controller in other games, such as GOG games, as an XBOX controller. Make sure to select your type of controller to map to in "general controller settings".<br />
<br />
== Troubleshooting ==<br />
<br />
See [[Steam/Troubleshooting]].<br />
<br />
== See also ==<br />
<br />
* [https://wiki.gentoo.org/wiki/Steam Gentoo Wiki article]<br />
* [https://pcgamingwiki.com/wiki/The_Big_List_of_DRM-Free_Games_on_Steam The Big List of DRM-Free Games on Steam] at PCGamingWiki<br />
* [http://steam.wikia.com/wiki/List_of_DRM-free_games List of DRM-free games] at Wikia<br />
* [http://store.steampowered.com/browse/linux Steam Linux store]<br />
* [https://github.com/ValveSoftware/Proton/ Proton] Compatibility tool for Steam Play based on Wine and additional components.</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=Steam_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=591636
Steam (简体中文)
2019-12-12T15:00:18Z
<p>C0n5t4ntK: /* Flatpak 的亚洲字体问题 */ 润色部分语句。</p>
<hr />
<div>[[Category:Gaming (简体中文)]]<br />
[[en:Steam]]<br />
[[ja:Steam]]<br />
[[ru:Steam]]<br />
{{Related articles start (简体中文)}}<br />
{{Related|Steam/Troubleshooting}}<br />
{{Related|Steam/Game-specific troubleshooting}}<br />
{{Related|Gaming}}<br />
{{Related|Gamepad}}<br />
{{Related|List of games (简体中文)}}<br />
{{Related articles end}}<br />
[http://store.steampowered.com/about/ Steam] 是维尔福公司推出的著名游戏分发平台。<br />
<br />
{{注意|对于 Linux 平台,Steam 只支持 Ubuntu 的长期支持版本[https://support.steampowered.com/kb_article.php?ref&#61;1504-QHXN-8366]。 因此,请不要向维尔福公司提交 issue 以获得 Steam 对 Arch Linux 的支持。}}<br />
<br />
== 安装 ==<br />
<br />
启用 [[multilib]] 仓库并[[Help:Reading (简体中文)#安装软件包|安装]] {{Pkg|steam}} 软件包。<br />
<br />
你需要满足下列要求从而在 Arch Linux 上运行 Steam:<br />
<br />
* 安装 32 位版本的 [[Xorg#Driver installation|OpenGL 图形驱动]]。<br />
* 生成 [[Locale#Generating locales|en_US.UTF-8]] 语言环境,以避免非法指针错误。<br />
* 其图形界面大量使用 Arial 字体。详见 [[Microsoft fonts]] 。你可以通过安装 {{Pkg|ttf-liberation}} 或使用 [[Steam/Troubleshooting#Text is corrupt or missing|Steam 支持的字体问题]] 中的方法来解决。<br />
* 安装 {{Pkg|wqy-zenhei}} 以支持亚洲地区语言。<br />
<br />
=== SteamCMD ===<br />
<br />
安装 {{AUR|steamcmd}} 以使用命令行版本的 [https://developer.valvesoftware.com/wiki/SteamCMD Steam]。<br />
<br />
=== 可选 Flatpak 安装 ===<br />
<br />
Steam 也可以作为 {{ic|com.valvesoftware.Steam}} 使用 [[Flatpak]] 从 [https://flathub.org/ Flathub] 中安装。使用 Flathub 仓库和 flatpak 命令行安装是目前最简单的安装方式:<br />
<br />
flatpak --user remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo<br />
flatpak --user install flathub com.valvesoftware.Steam<br />
flatpak run com.valvesoftware.Steam<br />
<br />
目前 Flatpak 应用还不支持主题。并且你不能通过 {{ic|optirun}}/{{ic|primusrun}} 来运行游戏,更多细节详见 [https://github.com/flatpak/flatpak/issues/869 Issue#869]。<br />
<br />
默认情况下 Steam 不会有访问你的家目录的权限,你可以运行下列命令来授予权限,以获得更类似于在 Ubuntu 或 SteamOS 下的运行效果:<br />
<br />
flatpak override com.valvesoftware.Steam --filesystem=$HOME<br />
<br />
==== Flatpak 的亚洲字体问题 ====<br />
<br />
如果你遇到了游戏中无法显示亚洲字体的问题,这是因为 org.freedesktop.Platform 并没有包含合适的字体文件进去。首先尝试挂载你的本地字体:<br />
<br />
flatpak run --filesystems=~/.local/share/fonts --filesystem=~/.config/fontconfig com.valvesoftware.Steam<br />
<br />
如果上述命令不起作用,考虑动手 hack 一下:直接将字体文件复制进 org.freedesktop.Platform 的目录下以启用字体,例如<br />
<br />
# replace ? with your version and hash<br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/etc/fonts/conf.avail<br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/etc/fonts/conf.d <br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/share/fonts<br />
<br />
== Directory structure ==<br />
<br />
The default Steam install location is {{ic|~/.local/share/Steam}}. If Steam cannot find it, it will prompt you to reinstall it or select the new location. This article uses the {{ic|~/.steam/root}} symlink to refer to the install location.<br />
<br />
=== Library folders ===<br />
<br />
Every Steam application has a unique AppID, which you can find out by looking at its [http://store.steampowered.com/ Steam Store] page path.<br />
<br />
Steam installs games into a directory under {{ic|''LIBRARY''/steamapps/common/}}. {{ic|''LIBRARY''}} normally is <br />
{{ic|~/.steam/root}} but you can also have multiple library folders (''Steam > Settings > Downloads > Steam Library Folders'').<br />
<br />
In order for Steam to recognize a game it needs to have an<br />
{{ic|appmanifest_''AppId''.acf}} file in {{ic|''LIBRARY''/steamapps/}}. The appmanifest file uses the <br />
[https://developer.valvesoftware.com/wiki/KeyValues KeyValues] format and its {{ic|installdir}} property<br />
determines the game directory name.<br />
<br />
== Usage ==<br />
<br />
steam [ -options ] [ steam:// URL ]<br />
<br />
For the available command-line options see the [https://developer.valvesoftware.com/wiki/Command_Line_Options#Steam_.28Windows.29 Command Line Options article on the Valve Developer Wiki].<br />
<br />
Steam also accepts an optional Steam URL, see the [https://developer.valvesoftware.com/wiki/Steam_browser_protocol Steam browser procotol].<br />
<br />
== Launch options ==<br />
<br />
When you launch a Steam game, Steam executes its '''launch command''' in a [[Bash]] shell.<br />
To let you alter the launch command Steam provides '''launch options''',<br />
which can be set for a game by right-clicking on it in your library, selecting Properties and clicking on ''Set Launch Options''.<br />
<br />
By default Steam simply appends your option string to the launch command. To set environment variables or<br />
pass the launch command as an argument to another command you can use the {{ic|%command%}} substitute.<br />
<br />
=== Examples ===<br />
<br />
* only arguments: {{ic|-foo}}<br />
* environment variables: {{ic|1=FOO=bar BAZ=bar %command% -baz}}<br />
* completely different command: {{ic|othercommand # %command%}}<br />
<br />
== Tips and tricks ==<br />
<br />
=== Fsync patch ===<br />
<br />
Valve has [https://steamcommunity.com/app/221410/discussions/0/3158631000006906163/ released] a special kernel patch that should help increase FPS in massively-threaded applications. There are few methods to get and use this patch:<br />
<br />
* Use binary kernel provided directly from Valve. See [[Unofficial user repositories#valveaur]] and once you add this repository, kernel packages {{AUR|linux-fsync}} and {{AUR|linux-fsync-headers}} become available. You will likely need to replace some regular packages (e.g. {{pkg|nvidia}}) with [[DKMS]] packages (e.g. {{pkg|nvidia-dkms}}) as well.<br />
* Install {{AUR|linux-fsync}} kernel.<br />
* Install {{Pkg|linux-zen}} kernel that includes the fsync patches since the 5.2 release[https://github.com/zen-kernel/zen-kernel/commit/f39367fdbc68e8b1e623239d13db6efaa5a67ae1]<br />
<br />
=== Proton Steam-Play ===<br />
<br />
Valve developed a compatibility tool for Steam Play based on Wine and additional components. It allows you to launch many Windows games (see [https://www.protondb.com/ compatibility list]).<br />
<br />
It's open-source and available on [https://github.com/ValveSoftware/Proton/ Github]. Steam will install its own versions of Proton when Steam Play is enabled.<br />
<br />
Proton needs to be enabled on Steam client : {{ic|Steam > Settings > Steam Play}}. You can enable Steam Play for games that have and have not been whitelisted by Valve in that dialog.<br />
<br />
If needed, to force enable Proton or a specific version of Proton for a game, right click on the game, click {{ic|Properties > General > Force the use of a specific Steam Play compatibility tool}}, and select the desired version. Doing so can also be used to force games that have a Linux port to use the Windows version.<br />
<br />
You can also install Proton from AUR with {{AUR|proton}} or {{AUR|proton-git}}, but extra setup is required for them to work with Steam. See the Proton Github for details on how Steam recognizes Proton installs.<br />
<br />
=== Big Picture Mode without a window manager ===<br />
<br />
To start Steam in Big Picture Mode from a [[Display manager]], you can either:<br />
<br />
* Install {{AUR|steamos-compositor}}<br />
* Alternatively, install {{AUR|steamos-compositor-plus}}, which hides the annoying color flashing on startup of Proton games and adds a fix for games that start in the background<br />
* Manually add a Steam entry (''but you lose the steam compositor advantages: mainly you '''can't''' control Big Picture mode with keyboard or gamepad''):<br />
<br />
create a {{ic|/usr/share/xsessions/steam-big-picture.desktop}} file with the following contents: <br />
<br />
{{hc|/usr/share/xsessions/steam-big-picture.desktop|<nowiki><br />
[Desktop Entry]<br />
Name=Steam Big Picture Mode<br />
Comment=Start Steam in Big Picture Mode<br />
Exec=/usr/bin/steam -bigpicture<br />
TryExec=/usr/bin/steam<br />
Icon=<br />
Type=Application</nowiki>}}<br />
<br />
=== Steam skins ===<br />
<br />
The Steam interface can be customized using skins. Skins can overwrite interface-specific files in {{ic|~/.steam/root}}.<br />
<br />
To install a skin:<br />
<br />
# Place its directory in {{ic|~/.steam/root/skins}}.<br />
# Open ''Steam > Settings > Interface'' and select it.<br />
# Restart Steam.<br />
<br />
An extensive list of skins can be found in [http://forums.steampowered.com/forums/showthread.php?t=1161035 this Steam forums post].<br />
<br />
{{Note|Using an outdated skin may cause visual errors.}}<br />
<br />
==== Creating skins ====<br />
<br />
Nearly all Steam styles are defined in {{ic|~/.steam/root/resource/styles/steam.styles}} (the file is over 3,500 lines long). For a skin to be recognized it needs its own {{ic|resource/styles/steam.styles}}.<br />
When a Steam update changes the official {{ic|steam.styles}} your skin may become outdated, potentially resulting in visual errors.<br />
<br />
See {{ic|~/.steam/root/skins/skins_readme.txt}} for a primer on how to create skins.<br />
<br />
=== Changing the Steam notification position ===<br />
<br />
The default Steam notification position is bottom right.<br />
<br />
You can change the Steam notification position by altering {{ic|Notifications.PanelPosition}} in<br />
<br />
* {{ic|resource/styles/steam.styles}} for desktop notifications, and<br />
* {{ic|resource/styles/gameoverlay.styles}} for in-game notifications<br />
<br />
Both files are overwritten by Steam on startup and {{ic|steam.styles}} is only read on startup.<br />
<br />
{{Note|Some games do not respect the setting in {{ic|gameoverlay.styles}} e.g. XCOM: Enemy Unknown.}}<br />
<br />
==== Use a skin ====<br />
<br />
You can create a skin to change the notification position to your liking. For example to change the position to top right:<br />
<br />
$ cd ~/.steam/root/skins<br />
$ mkdir -p Top-Right/resource<br />
$ cp -r ~/.steam/root/resource/styles Top-Right/resource<br />
$ sed -i '/Notifications.PanelPosition/ s/"[A-Za-z]*"/"TopRight"/' Top-Right/resource/styles/*<br />
<br />
==== Live patching ====<br />
<br />
{{ic|gameoverlay.styles}} can be overwritten while Steam is running, allowing you to have game-specific notification positions.<br />
<br />
{{hc|~/.steam/notifpos.sh|<br />
sed -i "/Notifications.PanelPosition/ s/\"[A-Za-z]*\"/\"$1\"/" ~/.steam/root/resource/styles/gameoverlay.styles<br />
}}<br />
<br />
And the [[#Launch options]] should be something like:<br />
<br />
~/.steam/notifpos.sh TopLeft && %command%<br />
<br />
=== Steam Remote Play ===<br />
<br />
{{Note|Steam In-Home Streaming [https://store.steampowered.com/news/51761/ has become Steam Remote Play].}}<br />
<br />
Steam has built-in support for [http://store.steampowered.com/streaming/ remote play].<br />
<br />
See [https://steamcommunity.com/sharedfiles/filedetails/?id=680514371 this Steam Community guide] on how to setup a headless streaming server on Linux.<br />
<br />
==== Different subnets ====<br />
<br />
{{Remove|This workaround/hack seems to be no longer relevant since it became a feature of [https://store.steampowered.com/news/51761/ Steam Remote Play].}}<br />
<br />
Steam client will not be able to detect host if both are on different subnets, which is common case when using VPN to your home network. Even if both client and server can ping each other - steam client would still not be able to detect host, so you need to force it. To do it, start Steam with below command:<br />
<br />
$ steam -console<br />
<br />
Wait until Steam starts. Once it loaded, you will find extra tab named "Console". Open it and then paste below command with correct host IP address:<br />
<br />
connect_remote <host_ip>:27036<br />
<br />
You will see notification that you can now stream games from host machine.<br />
<br />
{{Note|If above doesn't work - Windows is likely blocking all incoming traffic from different subnets, which means any connections coming from VPN tunnel will be dropped. This also can be confirmed by simply performing ping requests without any response to Windows machine from your VPN client. To workaround this, configure (or disable) all Windows firewalls (including existing antiviruses).}}<br />
<br />
{{Tip|See [[Gaming#Remote gaming]] for alternatives if above solution does not work.}}<br />
<br />
=== Steam Controller ===<br />
<br />
Normally a Steam controller requires the use of the Steam-overlay. In non-Steam native Linux games however the overlay may not be practical. For that, while the Steam client is running it will maintain a "desktop configuration". With your Steam controller, configure the desktop configuration for it as a generic XBOX controller. As long as the Steam client is running you can then use your Steam controller in other games, such as GOG games, as an XBOX controller. Make sure to select your type of controller to map to in "general controller settings".<br />
<br />
== Troubleshooting ==<br />
<br />
See [[Steam/Troubleshooting]].<br />
<br />
== See also ==<br />
<br />
* [https://wiki.gentoo.org/wiki/Steam Gentoo Wiki article]<br />
* [https://pcgamingwiki.com/wiki/The_Big_List_of_DRM-Free_Games_on_Steam The Big List of DRM-Free Games on Steam] at PCGamingWiki<br />
* [http://steam.wikia.com/wiki/List_of_DRM-free_games List of DRM-free games] at Wikia<br />
* [http://store.steampowered.com/browse/linux Steam Linux store]<br />
* [https://github.com/ValveSoftware/Proton/ Proton] Compatibility tool for Steam Play based on Wine and additional components.</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=Steam_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=591635
Steam (简体中文)
2019-12-12T14:54:47Z
<p>C0n5t4ntK: /* 安装 */ 安装部分翻译完成。</p>
<hr />
<div>[[Category:Gaming (简体中文)]]<br />
[[en:Steam]]<br />
[[ja:Steam]]<br />
[[ru:Steam]]<br />
{{Related articles start (简体中文)}}<br />
{{Related|Steam/Troubleshooting}}<br />
{{Related|Steam/Game-specific troubleshooting}}<br />
{{Related|Gaming}}<br />
{{Related|Gamepad}}<br />
{{Related|List of games (简体中文)}}<br />
{{Related articles end}}<br />
[http://store.steampowered.com/about/ Steam] 是维尔福公司推出的著名游戏分发平台。<br />
<br />
{{注意|对于 Linux 平台,Steam 只支持 Ubuntu 的长期支持版本[https://support.steampowered.com/kb_article.php?ref&#61;1504-QHXN-8366]。 因此,请不要向维尔福公司提交 issue 以获得 Steam 对 Arch Linux 的支持。}}<br />
<br />
== 安装 ==<br />
<br />
启用 [[multilib]] 仓库并[[Help:Reading (简体中文)#安装软件包|安装]] {{Pkg|steam}} 软件包。<br />
<br />
你需要满足下列要求从而在 Arch Linux 上运行 Steam:<br />
<br />
* 安装 32 位版本的 [[Xorg#Driver installation|OpenGL 图形驱动]]。<br />
* 生成 [[Locale#Generating locales|en_US.UTF-8]] 语言环境,以避免非法指针错误。<br />
* 其图形界面大量使用 Arial 字体。详见 [[Microsoft fonts]] 。你可以通过安装 {{Pkg|ttf-liberation}} 或使用 [[Steam/Troubleshooting#Text is corrupt or missing|Steam 支持的字体问题]] 中的方法来解决。<br />
* 安装 {{Pkg|wqy-zenhei}} 以支持亚洲地区语言。<br />
<br />
=== SteamCMD ===<br />
<br />
安装 {{AUR|steamcmd}} 以使用命令行版本的 [https://developer.valvesoftware.com/wiki/SteamCMD Steam]。<br />
<br />
=== 可选 Flatpak 安装 ===<br />
<br />
Steam 也可以作为 {{ic|com.valvesoftware.Steam}} 使用 [[Flatpak]] 从 [https://flathub.org/ Flathub] 中安装。使用 Flathub 仓库和 flatpak 命令行安装是目前最简单的安装方式:<br />
<br />
flatpak --user remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo<br />
flatpak --user install flathub com.valvesoftware.Steam<br />
flatpak run com.valvesoftware.Steam<br />
<br />
目前 Flatpak 应用还不支持主题。并且你不能通过 {{ic|optirun}}/{{ic|primusrun}} 来运行游戏,更多细节详见 [https://github.com/flatpak/flatpak/issues/869 Issue#869]。<br />
<br />
默认情况下 Steam 不会有访问你的家目录的权限,你可以运行下列命令来授予权限,以获得更类似于在 Ubuntu 或 SteamOS 下的运行效果:<br />
<br />
flatpak override com.valvesoftware.Steam --filesystem=$HOME<br />
<br />
==== Flatpak 的亚洲字体问题 ====<br />
<br />
如果你遇到了游戏中无法显示亚洲字体的问题,这是因为 org.freedesktop.Platform 并没有包含进去。首先尝试挂载你的本地字体:<br />
<br />
flatpak run --filesystems=~/.local/share/fonts --filesystem=~/.config/fontconfig com.valvesoftware.Steam<br />
<br />
如果上述命令不起作用,考虑动手 hack 一下:直接将字体文件复制进 org.freedesktop.Platform 的目录下以启用字体,例如<br />
<br />
# replace ? with your version and hash<br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/etc/fonts/conf.avail<br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/etc/fonts/conf.d <br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/share/fonts<br />
<br />
== Directory structure ==<br />
<br />
The default Steam install location is {{ic|~/.local/share/Steam}}. If Steam cannot find it, it will prompt you to reinstall it or select the new location. This article uses the {{ic|~/.steam/root}} symlink to refer to the install location.<br />
<br />
=== Library folders ===<br />
<br />
Every Steam application has a unique AppID, which you can find out by looking at its [http://store.steampowered.com/ Steam Store] page path.<br />
<br />
Steam installs games into a directory under {{ic|''LIBRARY''/steamapps/common/}}. {{ic|''LIBRARY''}} normally is <br />
{{ic|~/.steam/root}} but you can also have multiple library folders (''Steam > Settings > Downloads > Steam Library Folders'').<br />
<br />
In order for Steam to recognize a game it needs to have an<br />
{{ic|appmanifest_''AppId''.acf}} file in {{ic|''LIBRARY''/steamapps/}}. The appmanifest file uses the <br />
[https://developer.valvesoftware.com/wiki/KeyValues KeyValues] format and its {{ic|installdir}} property<br />
determines the game directory name.<br />
<br />
== Usage ==<br />
<br />
steam [ -options ] [ steam:// URL ]<br />
<br />
For the available command-line options see the [https://developer.valvesoftware.com/wiki/Command_Line_Options#Steam_.28Windows.29 Command Line Options article on the Valve Developer Wiki].<br />
<br />
Steam also accepts an optional Steam URL, see the [https://developer.valvesoftware.com/wiki/Steam_browser_protocol Steam browser procotol].<br />
<br />
== Launch options ==<br />
<br />
When you launch a Steam game, Steam executes its '''launch command''' in a [[Bash]] shell.<br />
To let you alter the launch command Steam provides '''launch options''',<br />
which can be set for a game by right-clicking on it in your library, selecting Properties and clicking on ''Set Launch Options''.<br />
<br />
By default Steam simply appends your option string to the launch command. To set environment variables or<br />
pass the launch command as an argument to another command you can use the {{ic|%command%}} substitute.<br />
<br />
=== Examples ===<br />
<br />
* only arguments: {{ic|-foo}}<br />
* environment variables: {{ic|1=FOO=bar BAZ=bar %command% -baz}}<br />
* completely different command: {{ic|othercommand # %command%}}<br />
<br />
== Tips and tricks ==<br />
<br />
=== Fsync patch ===<br />
<br />
Valve has [https://steamcommunity.com/app/221410/discussions/0/3158631000006906163/ released] a special kernel patch that should help increase FPS in massively-threaded applications. There are few methods to get and use this patch:<br />
<br />
* Use binary kernel provided directly from Valve. See [[Unofficial user repositories#valveaur]] and once you add this repository, kernel packages {{AUR|linux-fsync}} and {{AUR|linux-fsync-headers}} become available. You will likely need to replace some regular packages (e.g. {{pkg|nvidia}}) with [[DKMS]] packages (e.g. {{pkg|nvidia-dkms}}) as well.<br />
* Install {{AUR|linux-fsync}} kernel.<br />
* Install {{Pkg|linux-zen}} kernel that includes the fsync patches since the 5.2 release[https://github.com/zen-kernel/zen-kernel/commit/f39367fdbc68e8b1e623239d13db6efaa5a67ae1]<br />
<br />
=== Proton Steam-Play ===<br />
<br />
Valve developed a compatibility tool for Steam Play based on Wine and additional components. It allows you to launch many Windows games (see [https://www.protondb.com/ compatibility list]).<br />
<br />
It's open-source and available on [https://github.com/ValveSoftware/Proton/ Github]. Steam will install its own versions of Proton when Steam Play is enabled.<br />
<br />
Proton needs to be enabled on Steam client : {{ic|Steam > Settings > Steam Play}}. You can enable Steam Play for games that have and have not been whitelisted by Valve in that dialog.<br />
<br />
If needed, to force enable Proton or a specific version of Proton for a game, right click on the game, click {{ic|Properties > General > Force the use of a specific Steam Play compatibility tool}}, and select the desired version. Doing so can also be used to force games that have a Linux port to use the Windows version.<br />
<br />
You can also install Proton from AUR with {{AUR|proton}} or {{AUR|proton-git}}, but extra setup is required for them to work with Steam. See the Proton Github for details on how Steam recognizes Proton installs.<br />
<br />
=== Big Picture Mode without a window manager ===<br />
<br />
To start Steam in Big Picture Mode from a [[Display manager]], you can either:<br />
<br />
* Install {{AUR|steamos-compositor}}<br />
* Alternatively, install {{AUR|steamos-compositor-plus}}, which hides the annoying color flashing on startup of Proton games and adds a fix for games that start in the background<br />
* Manually add a Steam entry (''but you lose the steam compositor advantages: mainly you '''can't''' control Big Picture mode with keyboard or gamepad''):<br />
<br />
create a {{ic|/usr/share/xsessions/steam-big-picture.desktop}} file with the following contents: <br />
<br />
{{hc|/usr/share/xsessions/steam-big-picture.desktop|<nowiki><br />
[Desktop Entry]<br />
Name=Steam Big Picture Mode<br />
Comment=Start Steam in Big Picture Mode<br />
Exec=/usr/bin/steam -bigpicture<br />
TryExec=/usr/bin/steam<br />
Icon=<br />
Type=Application</nowiki>}}<br />
<br />
=== Steam skins ===<br />
<br />
The Steam interface can be customized using skins. Skins can overwrite interface-specific files in {{ic|~/.steam/root}}.<br />
<br />
To install a skin:<br />
<br />
# Place its directory in {{ic|~/.steam/root/skins}}.<br />
# Open ''Steam > Settings > Interface'' and select it.<br />
# Restart Steam.<br />
<br />
An extensive list of skins can be found in [http://forums.steampowered.com/forums/showthread.php?t=1161035 this Steam forums post].<br />
<br />
{{Note|Using an outdated skin may cause visual errors.}}<br />
<br />
==== Creating skins ====<br />
<br />
Nearly all Steam styles are defined in {{ic|~/.steam/root/resource/styles/steam.styles}} (the file is over 3,500 lines long). For a skin to be recognized it needs its own {{ic|resource/styles/steam.styles}}.<br />
When a Steam update changes the official {{ic|steam.styles}} your skin may become outdated, potentially resulting in visual errors.<br />
<br />
See {{ic|~/.steam/root/skins/skins_readme.txt}} for a primer on how to create skins.<br />
<br />
=== Changing the Steam notification position ===<br />
<br />
The default Steam notification position is bottom right.<br />
<br />
You can change the Steam notification position by altering {{ic|Notifications.PanelPosition}} in<br />
<br />
* {{ic|resource/styles/steam.styles}} for desktop notifications, and<br />
* {{ic|resource/styles/gameoverlay.styles}} for in-game notifications<br />
<br />
Both files are overwritten by Steam on startup and {{ic|steam.styles}} is only read on startup.<br />
<br />
{{Note|Some games do not respect the setting in {{ic|gameoverlay.styles}} e.g. XCOM: Enemy Unknown.}}<br />
<br />
==== Use a skin ====<br />
<br />
You can create a skin to change the notification position to your liking. For example to change the position to top right:<br />
<br />
$ cd ~/.steam/root/skins<br />
$ mkdir -p Top-Right/resource<br />
$ cp -r ~/.steam/root/resource/styles Top-Right/resource<br />
$ sed -i '/Notifications.PanelPosition/ s/"[A-Za-z]*"/"TopRight"/' Top-Right/resource/styles/*<br />
<br />
==== Live patching ====<br />
<br />
{{ic|gameoverlay.styles}} can be overwritten while Steam is running, allowing you to have game-specific notification positions.<br />
<br />
{{hc|~/.steam/notifpos.sh|<br />
sed -i "/Notifications.PanelPosition/ s/\"[A-Za-z]*\"/\"$1\"/" ~/.steam/root/resource/styles/gameoverlay.styles<br />
}}<br />
<br />
And the [[#Launch options]] should be something like:<br />
<br />
~/.steam/notifpos.sh TopLeft && %command%<br />
<br />
=== Steam Remote Play ===<br />
<br />
{{Note|Steam In-Home Streaming [https://store.steampowered.com/news/51761/ has become Steam Remote Play].}}<br />
<br />
Steam has built-in support for [http://store.steampowered.com/streaming/ remote play].<br />
<br />
See [https://steamcommunity.com/sharedfiles/filedetails/?id=680514371 this Steam Community guide] on how to setup a headless streaming server on Linux.<br />
<br />
==== Different subnets ====<br />
<br />
{{Remove|This workaround/hack seems to be no longer relevant since it became a feature of [https://store.steampowered.com/news/51761/ Steam Remote Play].}}<br />
<br />
Steam client will not be able to detect host if both are on different subnets, which is common case when using VPN to your home network. Even if both client and server can ping each other - steam client would still not be able to detect host, so you need to force it. To do it, start Steam with below command:<br />
<br />
$ steam -console<br />
<br />
Wait until Steam starts. Once it loaded, you will find extra tab named "Console". Open it and then paste below command with correct host IP address:<br />
<br />
connect_remote <host_ip>:27036<br />
<br />
You will see notification that you can now stream games from host machine.<br />
<br />
{{Note|If above doesn't work - Windows is likely blocking all incoming traffic from different subnets, which means any connections coming from VPN tunnel will be dropped. This also can be confirmed by simply performing ping requests without any response to Windows machine from your VPN client. To workaround this, configure (or disable) all Windows firewalls (including existing antiviruses).}}<br />
<br />
{{Tip|See [[Gaming#Remote gaming]] for alternatives if above solution does not work.}}<br />
<br />
=== Steam Controller ===<br />
<br />
Normally a Steam controller requires the use of the Steam-overlay. In non-Steam native Linux games however the overlay may not be practical. For that, while the Steam client is running it will maintain a "desktop configuration". With your Steam controller, configure the desktop configuration for it as a generic XBOX controller. As long as the Steam client is running you can then use your Steam controller in other games, such as GOG games, as an XBOX controller. Make sure to select your type of controller to map to in "general controller settings".<br />
<br />
== Troubleshooting ==<br />
<br />
See [[Steam/Troubleshooting]].<br />
<br />
== See also ==<br />
<br />
* [https://wiki.gentoo.org/wiki/Steam Gentoo Wiki article]<br />
* [https://pcgamingwiki.com/wiki/The_Big_List_of_DRM-Free_Games_on_Steam The Big List of DRM-Free Games on Steam] at PCGamingWiki<br />
* [http://steam.wikia.com/wiki/List_of_DRM-free_games List of DRM-free games] at Wikia<br />
* [http://store.steampowered.com/browse/linux Steam Linux store]<br />
* [https://github.com/ValveSoftware/Proton/ Proton] Compatibility tool for Steam Play based on Wine and additional components.</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=Steam_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=591631
Steam (简体中文)
2019-12-12T13:24:01Z
<p>C0n5t4ntK: 中文内容完全脱节,且已翻译部分不多,故以英文版内容全部覆盖后重新翻译。</p>
<hr />
<div>[[Category:Gaming (简体中文)]]<br />
[[en:Steam]]<br />
[[ja:Steam]]<br />
[[ru:Steam]]<br />
{{Related articles start (简体中文)}}<br />
{{Related|Steam/Troubleshooting}}<br />
{{Related|Steam/Game-specific troubleshooting}}<br />
{{Related|Gaming}}<br />
{{Related|Gamepad}}<br />
{{Related|List of games (简体中文)}}<br />
{{Related articles end}}<br />
[http://store.steampowered.com/about/ Steam] is a popular game distribution platform by Valve.<br />
<br />
{{Note|Steam for Linux only supports Ubuntu LTS.[https://support.steampowered.com/kb_article.php?ref&#61;1504-QHXN-8366] Thus, do not turn to Valve for support for issues with Steam on Arch Linux.}}<br />
<br />
== Installation ==<br />
<br />
Enable the [[multilib]] repository and [[install]] the {{Pkg|steam}} package.<br />
<br />
The following requirements must be fulfilled in order to run Steam on Arch Linux:<br />
<br />
* Installed 32-bit version [[Xorg#Driver installation|OpenGL graphics driver]].<br />
* Generated [[Locale#Generating locales|en_US.UTF-8]] locale, preventing invalid pointer error.<br />
* The GUI heavily uses the Arial font. See [[Microsoft fonts]]. An alternative is to use {{Pkg|ttf-liberation}} or [[Steam/Troubleshooting#Text is corrupt or missing|fonts provided by Steam]] instead.<br />
* Install {{Pkg|wqy-zenhei}} to add support for Asian languages.<br />
<br />
=== SteamCMD ===<br />
<br />
Install {{AUR|steamcmd}} for the command-line version of [https://developer.valvesoftware.com/wiki/SteamCMD Steam].<br />
<br />
=== Alternative Flatpak installation ===<br />
<br />
Steam can also be installed with [[Flatpak]] as {{ic|com.valvesoftware.Steam}} from [https://flathub.org/ Flathub]. The easiest way to install it for the current user is by using the Flathub repo and flatpak command:<br />
<br />
flatpak --user remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo<br />
flatpak --user install flathub com.valvesoftware.Steam<br />
flatpak run com.valvesoftware.Steam<br />
<br />
The Flatpak application currently does not support themes. Also you currently can't run games via {{ic|optirun}}/{{ic|primusrun}}, see [https://github.com/flatpak/flatpak/issues/869 Issue#869] for more details.<br />
<br />
By default Steam won't be able to access your home directory, you can run the following command to allow it, so that it behaves like on Ubuntu or SteamOS:<br />
<br />
flatpak override com.valvesoftware.Steam --filesystem=$HOME<br />
<br />
==== Asian Font Problems with Flatpak ====<br />
<br />
If you are having problem getting Asian fonts to show in game, it's because org.freedesktop.Platform does not include it. First try mounting your local font :<br />
<br />
flatpak run --filesystems=~/.local/share/fonts --filesystem=~/.config/fontconfig com.valvesoftware.Steam<br />
<br />
If that doesn't work, consider this hack: make the fonts available by directly copying the font files into org.freedesktop.Platform's directories, e.g.<br />
<br />
# replace ? with your version and hash<br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/etc/fonts/conf.avail<br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/etc/fonts/conf.d <br />
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/?/?/files/share/fonts<br />
<br />
== Directory structure ==<br />
<br />
The default Steam install location is {{ic|~/.local/share/Steam}}. If Steam cannot find it, it will prompt you to reinstall it or select the new location. This article uses the {{ic|~/.steam/root}} symlink to refer to the install location.<br />
<br />
=== Library folders ===<br />
<br />
Every Steam application has a unique AppID, which you can find out by looking at its [http://store.steampowered.com/ Steam Store] page path.<br />
<br />
Steam installs games into a directory under {{ic|''LIBRARY''/steamapps/common/}}. {{ic|''LIBRARY''}} normally is <br />
{{ic|~/.steam/root}} but you can also have multiple library folders (''Steam > Settings > Downloads > Steam Library Folders'').<br />
<br />
In order for Steam to recognize a game it needs to have an<br />
{{ic|appmanifest_''AppId''.acf}} file in {{ic|''LIBRARY''/steamapps/}}. The appmanifest file uses the <br />
[https://developer.valvesoftware.com/wiki/KeyValues KeyValues] format and its {{ic|installdir}} property<br />
determines the game directory name.<br />
<br />
== Usage ==<br />
<br />
steam [ -options ] [ steam:// URL ]<br />
<br />
For the available command-line options see the [https://developer.valvesoftware.com/wiki/Command_Line_Options#Steam_.28Windows.29 Command Line Options article on the Valve Developer Wiki].<br />
<br />
Steam also accepts an optional Steam URL, see the [https://developer.valvesoftware.com/wiki/Steam_browser_protocol Steam browser procotol].<br />
<br />
== Launch options ==<br />
<br />
When you launch a Steam game, Steam executes its '''launch command''' in a [[Bash]] shell.<br />
To let you alter the launch command Steam provides '''launch options''',<br />
which can be set for a game by right-clicking on it in your library, selecting Properties and clicking on ''Set Launch Options''.<br />
<br />
By default Steam simply appends your option string to the launch command. To set environment variables or<br />
pass the launch command as an argument to another command you can use the {{ic|%command%}} substitute.<br />
<br />
=== Examples ===<br />
<br />
* only arguments: {{ic|-foo}}<br />
* environment variables: {{ic|1=FOO=bar BAZ=bar %command% -baz}}<br />
* completely different command: {{ic|othercommand # %command%}}<br />
<br />
== Tips and tricks ==<br />
<br />
=== Fsync patch ===<br />
<br />
Valve has [https://steamcommunity.com/app/221410/discussions/0/3158631000006906163/ released] a special kernel patch that should help increase FPS in massively-threaded applications. There are few methods to get and use this patch:<br />
<br />
* Use binary kernel provided directly from Valve. See [[Unofficial user repositories#valveaur]] and once you add this repository, kernel packages {{AUR|linux-fsync}} and {{AUR|linux-fsync-headers}} become available. You will likely need to replace some regular packages (e.g. {{pkg|nvidia}}) with [[DKMS]] packages (e.g. {{pkg|nvidia-dkms}}) as well.<br />
* Install {{AUR|linux-fsync}} kernel.<br />
* Install {{Pkg|linux-zen}} kernel that includes the fsync patches since the 5.2 release[https://github.com/zen-kernel/zen-kernel/commit/f39367fdbc68e8b1e623239d13db6efaa5a67ae1]<br />
<br />
=== Proton Steam-Play ===<br />
<br />
Valve developed a compatibility tool for Steam Play based on Wine and additional components. It allows you to launch many Windows games (see [https://www.protondb.com/ compatibility list]).<br />
<br />
It's open-source and available on [https://github.com/ValveSoftware/Proton/ Github]. Steam will install its own versions of Proton when Steam Play is enabled.<br />
<br />
Proton needs to be enabled on Steam client : {{ic|Steam > Settings > Steam Play}}. You can enable Steam Play for games that have and have not been whitelisted by Valve in that dialog.<br />
<br />
If needed, to force enable Proton or a specific version of Proton for a game, right click on the game, click {{ic|Properties > General > Force the use of a specific Steam Play compatibility tool}}, and select the desired version. Doing so can also be used to force games that have a Linux port to use the Windows version.<br />
<br />
You can also install Proton from AUR with {{AUR|proton}} or {{AUR|proton-git}}, but extra setup is required for them to work with Steam. See the Proton Github for details on how Steam recognizes Proton installs.<br />
<br />
=== Big Picture Mode without a window manager ===<br />
<br />
To start Steam in Big Picture Mode from a [[Display manager]], you can either:<br />
<br />
* Install {{AUR|steamos-compositor}}<br />
* Alternatively, install {{AUR|steamos-compositor-plus}}, which hides the annoying color flashing on startup of Proton games and adds a fix for games that start in the background<br />
* Manually add a Steam entry (''but you lose the steam compositor advantages: mainly you '''can't''' control Big Picture mode with keyboard or gamepad''):<br />
<br />
create a {{ic|/usr/share/xsessions/steam-big-picture.desktop}} file with the following contents: <br />
<br />
{{hc|/usr/share/xsessions/steam-big-picture.desktop|<nowiki><br />
[Desktop Entry]<br />
Name=Steam Big Picture Mode<br />
Comment=Start Steam in Big Picture Mode<br />
Exec=/usr/bin/steam -bigpicture<br />
TryExec=/usr/bin/steam<br />
Icon=<br />
Type=Application</nowiki>}}<br />
<br />
=== Steam skins ===<br />
<br />
The Steam interface can be customized using skins. Skins can overwrite interface-specific files in {{ic|~/.steam/root}}.<br />
<br />
To install a skin:<br />
<br />
# Place its directory in {{ic|~/.steam/root/skins}}.<br />
# Open ''Steam > Settings > Interface'' and select it.<br />
# Restart Steam.<br />
<br />
An extensive list of skins can be found in [http://forums.steampowered.com/forums/showthread.php?t=1161035 this Steam forums post].<br />
<br />
{{Note|Using an outdated skin may cause visual errors.}}<br />
<br />
==== Creating skins ====<br />
<br />
Nearly all Steam styles are defined in {{ic|~/.steam/root/resource/styles/steam.styles}} (the file is over 3,500 lines long). For a skin to be recognized it needs its own {{ic|resource/styles/steam.styles}}.<br />
When a Steam update changes the official {{ic|steam.styles}} your skin may become outdated, potentially resulting in visual errors.<br />
<br />
See {{ic|~/.steam/root/skins/skins_readme.txt}} for a primer on how to create skins.<br />
<br />
=== Changing the Steam notification position ===<br />
<br />
The default Steam notification position is bottom right.<br />
<br />
You can change the Steam notification position by altering {{ic|Notifications.PanelPosition}} in<br />
<br />
* {{ic|resource/styles/steam.styles}} for desktop notifications, and<br />
* {{ic|resource/styles/gameoverlay.styles}} for in-game notifications<br />
<br />
Both files are overwritten by Steam on startup and {{ic|steam.styles}} is only read on startup.<br />
<br />
{{Note|Some games do not respect the setting in {{ic|gameoverlay.styles}} e.g. XCOM: Enemy Unknown.}}<br />
<br />
==== Use a skin ====<br />
<br />
You can create a skin to change the notification position to your liking. For example to change the position to top right:<br />
<br />
$ cd ~/.steam/root/skins<br />
$ mkdir -p Top-Right/resource<br />
$ cp -r ~/.steam/root/resource/styles Top-Right/resource<br />
$ sed -i '/Notifications.PanelPosition/ s/"[A-Za-z]*"/"TopRight"/' Top-Right/resource/styles/*<br />
<br />
==== Live patching ====<br />
<br />
{{ic|gameoverlay.styles}} can be overwritten while Steam is running, allowing you to have game-specific notification positions.<br />
<br />
{{hc|~/.steam/notifpos.sh|<br />
sed -i "/Notifications.PanelPosition/ s/\"[A-Za-z]*\"/\"$1\"/" ~/.steam/root/resource/styles/gameoverlay.styles<br />
}}<br />
<br />
And the [[#Launch options]] should be something like:<br />
<br />
~/.steam/notifpos.sh TopLeft && %command%<br />
<br />
=== Steam Remote Play ===<br />
<br />
{{Note|Steam In-Home Streaming [https://store.steampowered.com/news/51761/ has become Steam Remote Play].}}<br />
<br />
Steam has built-in support for [http://store.steampowered.com/streaming/ remote play].<br />
<br />
See [https://steamcommunity.com/sharedfiles/filedetails/?id=680514371 this Steam Community guide] on how to setup a headless streaming server on Linux.<br />
<br />
==== Different subnets ====<br />
<br />
{{Remove|This workaround/hack seems to be no longer relevant since it became a feature of [https://store.steampowered.com/news/51761/ Steam Remote Play].}}<br />
<br />
Steam client will not be able to detect host if both are on different subnets, which is common case when using VPN to your home network. Even if both client and server can ping each other - steam client would still not be able to detect host, so you need to force it. To do it, start Steam with below command:<br />
<br />
$ steam -console<br />
<br />
Wait until Steam starts. Once it loaded, you will find extra tab named "Console". Open it and then paste below command with correct host IP address:<br />
<br />
connect_remote <host_ip>:27036<br />
<br />
You will see notification that you can now stream games from host machine.<br />
<br />
{{Note|If above doesn't work - Windows is likely blocking all incoming traffic from different subnets, which means any connections coming from VPN tunnel will be dropped. This also can be confirmed by simply performing ping requests without any response to Windows machine from your VPN client. To workaround this, configure (or disable) all Windows firewalls (including existing antiviruses).}}<br />
<br />
{{Tip|See [[Gaming#Remote gaming]] for alternatives if above solution does not work.}}<br />
<br />
=== Steam Controller ===<br />
<br />
Normally a Steam controller requires the use of the Steam-overlay. In non-Steam native Linux games however the overlay may not be practical. For that, while the Steam client is running it will maintain a "desktop configuration". With your Steam controller, configure the desktop configuration for it as a generic XBOX controller. As long as the Steam client is running you can then use your Steam controller in other games, such as GOG games, as an XBOX controller. Make sure to select your type of controller to map to in "general controller settings".<br />
<br />
== Troubleshooting ==<br />
<br />
See [[Steam/Troubleshooting]].<br />
<br />
== See also ==<br />
<br />
* [https://wiki.gentoo.org/wiki/Steam Gentoo Wiki article]<br />
* [https://pcgamingwiki.com/wiki/The_Big_List_of_DRM-Free_Games_on_Steam The Big List of DRM-Free Games on Steam] at PCGamingWiki<br />
* [http://steam.wikia.com/wiki/List_of_DRM-free_games List of DRM-free games] at Wikia<br />
* [http://store.steampowered.com/browse/linux Steam Linux store]<br />
* [https://github.com/ValveSoftware/Proton/ Proton] Compatibility tool for Steam Play based on Wine and additional components.</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=ArchWiki:Translation_Team_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=591592
ArchWiki:Translation Team (简体中文)
2019-12-11T13:32:58Z
<p>C0n5t4ntK: /* 页面维护列表 */ 调整列表字典序</p>
<hr />
<div>[[Category:简体中文]]<br />
[[Category:ArchWiki (简体中文)]]<br />
[[ar:ArchWiki Translation Team]]<br />
[[cs:ArchWiki Translation Team]]<br />
[[el:ArchWiki Translation Team]]<br />
[[en:ArchWiki:Translation Team]]<br />
[[es:ArchWiki:Translation Team]]<br />
[[fr:ArchWiki Translation Team]]<br />
[[hr:ArchWiki Translation Team]]<br />
[[it:ArchWiki Translation Team]]<br />
[[ja:ArchWiki 翻訳チーム]]<br />
[[ko:ArchWiki Translation Team]]<br />
[[nl:ArchWiki Translation Team]]<br />
[[pl:ArchWiki Translation Team]]<br />
[[pt:ArchWiki:Translation Team]]<br />
[[ru:ArchWiki Translation Team]]<br />
[[sk:ArchWiki Translation Team]]<br />
[[zh-hant:ArchWiki:Translation Team]]<br />
Arch Wiki 上有许多中文页面,这其中大部分是从外文翻译过来的,这些页面是无数中文志愿者劳动的结晶。随着时间推移,有些页面因为没有及时维护,内容严重过时。而目前的翻译工作缺少组织,效率偏低。所以参照西班牙和意大利翻译组的做法,添加这个页面。<br />
<br />
如果你希望对Arch Wiki做贡献,参与Wiki建设,比如翻译英文页面和对已翻译过的中文页面进行维护,只需要编辑下面的[[#页面维护列表]],添加相应的条目,并将自己加为相关页面的维护者。如果你在列表中还没有找到想要翻译的页面,可以自行添加。另外,如果因为时间原因无法再维护页面,请及时将自己从维护者列表中删除。<br />
<br />
== 创建翻译 ==<br />
{{警告|如果不准备翻译页面的大部分内容,请尽量不要新建简体中文页面。检查英文页面的更新需要花费不少精力,没有翻译的页面会增加维护负担。}}<br />
# 如果还不知道如何编辑 wiki,请阅读 [[Help:Editing (简体中文)|编辑帮助]]。<br />
# 阅读 [[Help:i18n (简体中文)|i18n帮助]],文章给出了 ArchWiki 国际化和本地化的指南。<br />
# [[Special:UserLogin|登录]] 以进行编辑。<br />
# 选择要翻译的页面,例如从 [[Special:Random|随机页面]] 或[[#页面维护列表|页面维护列表]] 中选择一个未翻译完成的页面。假设要翻译 [[Some Page]].<br />
# 进入选择的英文页面,点击页面顶部的 '''编辑'''。<br />
# 添加要翻译文件的语言间链接, 简体中文的话加入<nowiki>[[zh-hans:Some Page]]</nowiki>,其它语言参见[[Help:i18n#Interlanguage links]])。<br />
# 复制所有页面代码。<br />
# 保存页面 (新加了语言链接)<br />
# 访问页面左边新添加的语言链接,应该会进到 [[Some Page (简体中文)]] : {{ic|<nowiki>https://wiki.archlinux.org/index.php/Some_Page_(</nowiki>''简体中文'')}}<br />
# 因为页面不存在,点击 '''创建'''。<br />
# 将显示一个编辑器 - 粘贴复制的英文页面。<br />
# 将文章分类修改为本地化版本,例如将 {{ic|<nowiki>[[Category:Internationalization]]</nowiki>}} 修改为 {{ic|<nowiki>[[Category:Internationalization (简体中文)]]</nowiki>}},参阅[[Help:Category (简体中文)]].<br />
# 修改语言间链接,指向英文页面(将 {{ic|zh-hans}} 修改为 {{ic|en}},并将英文页面移到文章顶部。<br />
# 翻译页面,进行保存。<br />
# (推荐)给翻译完成的页面加上[[Template:TranslationStatus (简体中文)|翻译状态]],后有详细介绍。<br />
# 更新所有其它语言页面,加入刚翻译文章的语言间链接。<br />
# (可选)创建一个简体中文名称的页面,指向新创建的页面:访问 {{ic|<nowiki>https://wiki.archlinux.org/index.php/</nowiki>''页面的中文名称''}}.<br />
# (可选)建立新页面,并加入:{{bc|<nowiki>#REDIRECT [[Some Page (简体中文)</nowiki>]]}}<br />
<br />
== Templates ==<br />
<br />
{{Translateme (简体中文)|Not translated}}<br />
<br />
The following table lists the [[Help:Template (简体中文)|templates]] that should be translated and their Simplified Chinese equivalent.<br />
<br />
{| class=wikitable<br />
! English template || Simplified Chinese version<br />
|-<br />
! colspan=2| Article templates<br />
|-<br />
| [[Template:Related articles start]] || [[Template:Related articles start (简体中文)]]<br />
|-<br />
| [[Template:Yes]] || [[Template:是]]<br />
|-<br />
| [[Template:No]] || [[Template:否]]<br />
|-<br />
| [[Template:Tip]] || [[Template:提示]]<br />
|-<br />
| [[Template:Note]] || [[Template:注意]]<br />
|-<br />
| [[Template:Warning]] || [[Template:警告]]<br />
|-<br />
| [[Template:Dead link]] || [[Template:失效链接]]<br />
|-<br />
| [[Template:Broken package link]] || {{-}}<br />
|-<br />
! colspan=2| Translation status templates<br />
|-<br />
| [[Template:Bad translation]] || {{-}}<br />
|-<br />
| [[Template:Translateme]] || [[Template:Translateme (简体中文)]]<br />
|-<br />
| [[Template:TranslationStatus]] || [[Template:TranslationStatus (简体中文)]]<br />
|-<br />
! colspan=2| Special templates<br />
|-<br />
| [[Template:Cat main]] || {{-}}<br />
|-<br />
| [[Template:Template]] || {{-}}<br />
|}<br />
<br />
== 完善翻译 ==<br />
[https://wiki.archlinux.org/index.php?title=Special:WhatLinksHere/Template:Translateme_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&limit=100 这个页面] 包含了需要完善翻译的简体中文页面。完善翻译的基本步骤:<br />
# 选择自己比较熟悉的文章进行翻译<br />
# 先检查英文页面的对应段落,更新成最新的英文后再翻译,避免翻译过时的内容,减少信息遗漏。<br />
# 翻译完成后删除页面中的 <nowiki>{{translateme (简体中文)}}</nowiki> 标记<br />
# (推荐)给翻译完成的页面加上[[Template:TranslationStatus (简体中文)|翻译状态]],后有详细介绍。<br />
<br />
== 更新过期页面 == <br />
如果发现有 Wiki 页面过期或错误:<br />
* 小的改动,有时间可以立即进行修改同步,维护者并不控制页面的编辑权限,越多的人参与维护越好。如果改动较大,请先联系维护者,避免重复劳动。<br />
* 没有时间查看更改,请给页面加上 {{ic|<nowiki>{{out of date}}</nowiki>}} 模版,这样其他贡献者更容易发现需要更新的页面,而读者看到过期标记就可以直接查看英文页面,以免被错误内容误导,白白耽误时间。<br />
* 没有时间翻译,请将过期的中文部分删去,从英文页面中复制更改的部分到中文页面的相应部分,去掉{{ic|<nowiki>{{out of date}}</nowiki>}}模板(如果页面上有的话)并加上{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板,这样其他贡献者就更容易发现需要翻译的页面,而读者也不会被过期的内容误导。<br />
如果发现有页面未翻译:<br />
* 有时间的话,请将页面中的英文部分翻译为中文,并去掉{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板。<br />
* 没有时间翻译,请为页面添加{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板,这样其他的贡献者就能更容易发现需要翻译的页面。<br />
{{注意|在修改页面上的模板时,请同时更新页面维护列表的翻译状态。}}<br />
<br />
== 翻译任务 ==<br />
=== 模板 Article summary 变更为 Related ===<br />
因为 Summary 中的简介基本上和正文的介绍一样,所以页面左边的介绍栏进行了简化,只保留相关文章功能。英文页面正在进行大规模修改,相应的中文页面也需要同步更新。<br />
<br />
需要注意的地方:<br />
* 将第一行改成<br />
: <nowiki>{{Related articles start (简体中文)}}</nowiki><br />
* 如果英文的相关文章存在中文翻译,则替换为简体中文页面。示例:<br />
: <nowiki>{{Related2|Display Manager (简体中文)|显示管理器}}</nowiki><br />
* 示例:[https://wiki.archlinux.org/index.php?title=Start_X_at_Login&diff=0&oldid=270155 英文变更], [https://wiki.archlinux.org/index.php?title=Start_X_at_Login_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=285643&oldid=242662 对应的翻译]<br />
<br />
== 维护翻译 ==<br />
完成页面的翻译只是初步完成任务,及时同步英文页面改动、更新翻译是一个持续性的工作,可能会耗费更多的时间。<br />
<br />
=== 页面认领 ===<br />
所有人都可以认领页面。认领后的责任包括进行翻译,关注英文页面的改动,及时同步翻译。<br />
<br />
为了更好的跟踪英文页面的修改,请务必在设置中启用监视列表邮件通知,并监视对应的英文页面(从设置中找到监视列表,加入英文页面。或者直接到英文页面点击页面顶端的监视标签。这样只要有改动,就会收到邮件通知)。<br />
<br />
{{小贴士|如果收到邮件通知后没有访问页面或者访问了页面却没有登录用户,下次页面改动时就不会再发邮件通知。可以点击监视列表中的'''标记所有页面为已读'''再次获取更新。}}<br />
<br />
如果页面有维护者但长期得不到更新,将会在维护列表中删除维护者。<br />
<br />
=== 翻译状态模板 ===<br />
Arch 作为滚动发行版,软件变化比较快,对应的文档变化也比较快。许多翻译的文章由于缺乏更新,会产生命令运行出错或不起作用等问题。而由于这些过期页面没有及时标记出来,所以用户无法及时获得更新。[[Template:TranslationStatus (简体中文)|翻译状态模板]]就是为了解决这个问题而创建。<br />
<br />
此模板可以起到如下作用:<br />
* 为用户提供翻译状况,包括翻译时间、英文页面的最后版本等<br />
* 用户可以点击查看翻译后,英文页面的改动,这样英文不是很好的用户可以只查看很小一部分英文内容,并判断出是否影响操作。<br />
* 翻译人员可以跟踪页面状况,通过[[Special:WhatLinksHere/Template:TranslationStatus_(简体中文)|模板的反向链接]]可以查找到所有标记页面,查看需要更新翻译的部分。<br />
<br />
[[Template:TranslationStatus (简体中文)|模板页面]]有详细的使用方法。<br />
<br />
=== 页面维护列表 ===<br />
{{注意|请按照拉丁字母顺序添加页面。}}<br />
<br />
翻译状态说明:<br />
;过期:页面内容未与英文页面同步,对应{{ic|<nowiki>{{out of date}}</nowiki>}} 模版<br />
;未翻译:页面中含有英文内容,对应{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板<br />
;完成:页面已与英文页面同步<br />
<br />
{| class="wikitable sortable collapsible" border="1"<br />
|-<br />
! 页面<br />
! 翻译状态<br />
! 维护者<br />
! class="unsortable" width="30%" | 备注<br />
|-<br />
| [[acpid (简体中文)]]<br />
| 过期<br />
| Cael<br />
|<br />
|-<br />
| [[Advanced Linux Sound Architecture (简体中文)]]<br />
| 翻译中<br />
| ihonliu<br />
| 无<br />
|-<br />
| [[Arch based distributions (active) (简体中文)]]<br />
| 完成<br />
| Joshua<br />
| 勘误中<br />
|-<br />
| [[Amateur radio (简体中文)]]<br />
| 翻译中<br />
| liu-shuyuan<br />
| <br />
|-<br />
| [[AMD Catalyst (简体中文)]]<br />
| 过期<br />
| Shibao Zhao<br />
| 无<br />
|-<br />
| [[ATI (简体中文)]]<br />
| 完成<br />
| skysailing<br />
| 无<br />
|-<br />
| [[AUR helpers (简体中文)]]<br />
| 完成<br />
| Kurobac<br />
| 部分用词可能需要修改<br />
|-<br />
| [[awesome (简体中文)]]<br />
| 进行中<br />
| Cael<br />
| 无<br />
|-<br />
| [[BIND (简体中文)]]<br />
| 完成<br />
| Dargasia<br />
|<br />
|-<br />
| [[Bumblebee (简体中文)]]<br />
| 完成<br />
| Peter<br />
| 无<br />
|-<br />
| [[Chromium (简体中文)]]<br />
| 完成<br />
| Bobby<br />
| 无<br />
|-<br />
| [[Ceph (简体中文)]]<br />
| 翻译中<br />
| Aaron Chen<br />
| 部分未翻译 <br />
|-<br />
| [[Cinnamon (简体中文)]]<br />
| 部分翻译 <br />
| Bobby<br />
| 部分未翻译 <br />
|- <br />
| [[Common Applications (简体中文)]]<br />
| 部分翻译 <br />
| DavidChen<br />
| 翻译中<br />
|-<br />
| [[Common Applications/Science (简体中文)]]<br />
| drop maintain<br />
| 更新,翻译中<br />
|<br />
|-<br />
| [[Compiz (简体中文)]]<br />
| 翻译中<br />
| xiii_1991<br />
| 20140813开始<br />
|-<br />
| [[Conky (简体中文)]]<br />
| 完成<br />
| upi<br />
| 无<br />
|-<br />
| [[Core utilities (简体中文)]]<br />
| 完成<br />
| rentaro, Arisaka<br />
| 无<br />
|-<br />
|-<br />
| [[Clover (简体中文)]]<br />
| 完成<br />
| Yume Kankawa<br />
| 无<br />
|-<br />
| [[Disk cloning (简体中文)]]<br />
| 翻译中<br />
| _spaike97<br />
| 无<br />
|-<br />
| [[Dynamic Kernel Module Support (简体中文)]]<br />
| 完成<br />
| Mithrandir<br />
| 完善中<br />
|-<br />
| [[Emacs (简体中文)]]<br />
| 翻译中<br />
| Jaurung yuanhang<br />
| 未完成<br />
|-<br />
| [[File recovery (简体中文)]]<br />
| 翻译中<br />
| _spaike97<br />
| 无<br />
|-<br />
| [[Fish (简体中文)]]<br />
| 完成<br />
| liu-shuyuan<br />
|<br />
|-<br />
| [[Font configuration (简体中文)]]<br />
| 翻译中<br />
| Jaurung<br />
| 完善中<br />
|-<br />
| [[Fonts (简体中文)]]<br />
| 翻译中<br />
| qqbzg<br />
| 无<br />
|-<br />
| [[GDM (简体中文)]]<br />
| 翻译中<br />
| Junjie Yuan<br />
| 绝大多数内容未翻译,重新进行翻译<br />
|-<br />
| [[GNOME (简体中文)]]<br />
| 完成<br />
| skywet<br />
| <br />
|-<br />
| [[GRUB (简体中文)]]<br />
| 完成<br />
| Armodeniz<br />
| <br />
|-<br />
| [[GRUB/Tips and tricks (简体中文)]]<br />
| 完成<br />
| Armodeniz<br />
| <br />
|-<br />
| [[Java (简体中文)]]<br />
| 翻译中<br />
| CaCaCarrot<br />
| 无<br />
|-<br />
| [[KDE (简体中文)]]<br />
| 过期<br />
| <br />
| <br />
|-<br />
| [[LAMP (简体中文)]]<br />
| 完成<br />
| Liuzhengyi<br />
| 勘误中<br />
|-<br />
| [[LibreOffice (简体中文)]]<br />
| 完成<br />
| qqbzg<br />
| 勘误中<br />
|-<br />
| [[Libvirt (简体中文)]]<br />
| 完成<br />
| Kurobac<br />
| 需要格式改进<br />
|-<br />
| [[Local Mirror (简体中文)]]<br />
| 完成<br />
| Jason Zhang<br />
| 完善中<br />
|- <br />
| [[MATLAB (简体中文)]]<br />
| 部分翻译 <br />
| Liu Qinyang<br />
|<br />
|-<br />
| [[Minecraft (简体中文)]]<br />
| 完成 <br />
| Xavier Lau<br />
| 页面已经与英文版同步,长期维护中<br />
|-<br />
| [[NetworkManager (简体中文)]]<br />
| 翻译中 <br />
| Jack-lijing, leeking <br />
| 请优先翻译<br />
|-<br />
| [[Network Time Protocol daemon (简体中文)]]<br />
| 完成<br />
| sid<br />
| 完善中<br />
|-<br />
| [[OpenOffice (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Opera (简体中文)]]<br />
| 未翻译<br />
| Bobby<br />
| 请优先翻译此文 <br />
|-<br />
| [[Pacman GUI Frontends (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Pidgin (简体中文)]]<br />
| 进行中<br />
| Cael<br />
| 无 <br />
|-<br />
| [[Python打包指引 (简体中文)]]<br />
| 翻译中<br />
| SherlockHolo<br />
| 无<br />
|- <br />
| [[ranger (简体中文)]]<br />
| 完成<br />
| Jason Zhang<br />
| 完善中<br />
|-<br />
| [[Raspberry Pi (简体中文)]]<br />
| 翻译中<br />
| Mithrandir<br />
| <br />
|-<br />
| [[Reporting bug guidelines (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Secure Shell (简体中文)]]<br />
| 完成<br />
| Arisaka<br />
| 无<br />
|-<br />
| [[Smart Common Input Method platform (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Steam (简体中文)]]<br />
| 过期<br />
| C0n5t4ntK<br />
| 翻译中<br />
|-<br />
| [[Systemd-timesyncd (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[TLP (简体中文)]]<br />
| 完成<br />
| Skywet<br />
| 持续更新中 <br />
|-<br />
| [[Tomcat (简体中文)]]<br />
| 完成<br />
| Starwing117<br />
| 持续更新中 <br />
|-<br />
| [[Vim (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[VirtualBox (简体中文)]]<br />
| 翻译至 2017-10-15<br />
| [[User:5long]]<br />
|<br />
|-<br />
| [[VMware (简体中文)]]<br />
| 完成<br />
| ThomasWFan<br />
| 页面已经与英文版同步,长期维护中<br />
|- <br />
| [[Xfce (简体中文)]]<br />
| 完成 <br />
| 无<br />
| 无<br />
|-<br />
| [[Xmonad (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Xrandr (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无</div>
C0n5t4ntK
https://wiki.archlinux.org/index.php?title=ArchWiki:Translation_Team_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=591591
ArchWiki:Translation Team (简体中文)
2019-12-11T12:31:16Z
<p>C0n5t4ntK: 认领Steam (简体中文)页面</p>
<hr />
<div>[[Category:简体中文]]<br />
[[Category:ArchWiki (简体中文)]]<br />
[[ar:ArchWiki Translation Team]]<br />
[[cs:ArchWiki Translation Team]]<br />
[[el:ArchWiki Translation Team]]<br />
[[en:ArchWiki:Translation Team]]<br />
[[es:ArchWiki:Translation Team]]<br />
[[fr:ArchWiki Translation Team]]<br />
[[hr:ArchWiki Translation Team]]<br />
[[it:ArchWiki Translation Team]]<br />
[[ja:ArchWiki 翻訳チーム]]<br />
[[ko:ArchWiki Translation Team]]<br />
[[nl:ArchWiki Translation Team]]<br />
[[pl:ArchWiki Translation Team]]<br />
[[pt:ArchWiki:Translation Team]]<br />
[[ru:ArchWiki Translation Team]]<br />
[[sk:ArchWiki Translation Team]]<br />
[[zh-hant:ArchWiki:Translation Team]]<br />
Arch Wiki 上有许多中文页面,这其中大部分是从外文翻译过来的,这些页面是无数中文志愿者劳动的结晶。随着时间推移,有些页面因为没有及时维护,内容严重过时。而目前的翻译工作缺少组织,效率偏低。所以参照西班牙和意大利翻译组的做法,添加这个页面。<br />
<br />
如果你希望对Arch Wiki做贡献,参与Wiki建设,比如翻译英文页面和对已翻译过的中文页面进行维护,只需要编辑下面的[[#页面维护列表]],添加相应的条目,并将自己加为相关页面的维护者。如果你在列表中还没有找到想要翻译的页面,可以自行添加。另外,如果因为时间原因无法再维护页面,请及时将自己从维护者列表中删除。<br />
<br />
== 创建翻译 ==<br />
{{警告|如果不准备翻译页面的大部分内容,请尽量不要新建简体中文页面。检查英文页面的更新需要花费不少精力,没有翻译的页面会增加维护负担。}}<br />
# 如果还不知道如何编辑 wiki,请阅读 [[Help:Editing (简体中文)|编辑帮助]]。<br />
# 阅读 [[Help:i18n (简体中文)|i18n帮助]],文章给出了 ArchWiki 国际化和本地化的指南。<br />
# [[Special:UserLogin|登录]] 以进行编辑。<br />
# 选择要翻译的页面,例如从 [[Special:Random|随机页面]] 或[[#页面维护列表|页面维护列表]] 中选择一个未翻译完成的页面。假设要翻译 [[Some Page]].<br />
# 进入选择的英文页面,点击页面顶部的 '''编辑'''。<br />
# 添加要翻译文件的语言间链接, 简体中文的话加入<nowiki>[[zh-hans:Some Page]]</nowiki>,其它语言参见[[Help:i18n#Interlanguage links]])。<br />
# 复制所有页面代码。<br />
# 保存页面 (新加了语言链接)<br />
# 访问页面左边新添加的语言链接,应该会进到 [[Some Page (简体中文)]] : {{ic|<nowiki>https://wiki.archlinux.org/index.php/Some_Page_(</nowiki>''简体中文'')}}<br />
# 因为页面不存在,点击 '''创建'''。<br />
# 将显示一个编辑器 - 粘贴复制的英文页面。<br />
# 将文章分类修改为本地化版本,例如将 {{ic|<nowiki>[[Category:Internationalization]]</nowiki>}} 修改为 {{ic|<nowiki>[[Category:Internationalization (简体中文)]]</nowiki>}},参阅[[Help:Category (简体中文)]].<br />
# 修改语言间链接,指向英文页面(将 {{ic|zh-hans}} 修改为 {{ic|en}},并将英文页面移到文章顶部。<br />
# 翻译页面,进行保存。<br />
# (推荐)给翻译完成的页面加上[[Template:TranslationStatus (简体中文)|翻译状态]],后有详细介绍。<br />
# 更新所有其它语言页面,加入刚翻译文章的语言间链接。<br />
# (可选)创建一个简体中文名称的页面,指向新创建的页面:访问 {{ic|<nowiki>https://wiki.archlinux.org/index.php/</nowiki>''页面的中文名称''}}.<br />
# (可选)建立新页面,并加入:{{bc|<nowiki>#REDIRECT [[Some Page (简体中文)</nowiki>]]}}<br />
<br />
== Templates ==<br />
<br />
{{Translateme (简体中文)|Not translated}}<br />
<br />
The following table lists the [[Help:Template (简体中文)|templates]] that should be translated and their Simplified Chinese equivalent.<br />
<br />
{| class=wikitable<br />
! English template || Simplified Chinese version<br />
|-<br />
! colspan=2| Article templates<br />
|-<br />
| [[Template:Related articles start]] || [[Template:Related articles start (简体中文)]]<br />
|-<br />
| [[Template:Yes]] || [[Template:是]]<br />
|-<br />
| [[Template:No]] || [[Template:否]]<br />
|-<br />
| [[Template:Tip]] || [[Template:提示]]<br />
|-<br />
| [[Template:Note]] || [[Template:注意]]<br />
|-<br />
| [[Template:Warning]] || [[Template:警告]]<br />
|-<br />
| [[Template:Dead link]] || [[Template:失效链接]]<br />
|-<br />
| [[Template:Broken package link]] || {{-}}<br />
|-<br />
! colspan=2| Translation status templates<br />
|-<br />
| [[Template:Bad translation]] || {{-}}<br />
|-<br />
| [[Template:Translateme]] || [[Template:Translateme (简体中文)]]<br />
|-<br />
| [[Template:TranslationStatus]] || [[Template:TranslationStatus (简体中文)]]<br />
|-<br />
! colspan=2| Special templates<br />
|-<br />
| [[Template:Cat main]] || {{-}}<br />
|-<br />
| [[Template:Template]] || {{-}}<br />
|}<br />
<br />
== 完善翻译 ==<br />
[https://wiki.archlinux.org/index.php?title=Special:WhatLinksHere/Template:Translateme_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&limit=100 这个页面] 包含了需要完善翻译的简体中文页面。完善翻译的基本步骤:<br />
# 选择自己比较熟悉的文章进行翻译<br />
# 先检查英文页面的对应段落,更新成最新的英文后再翻译,避免翻译过时的内容,减少信息遗漏。<br />
# 翻译完成后删除页面中的 <nowiki>{{translateme (简体中文)}}</nowiki> 标记<br />
# (推荐)给翻译完成的页面加上[[Template:TranslationStatus (简体中文)|翻译状态]],后有详细介绍。<br />
<br />
== 更新过期页面 == <br />
如果发现有 Wiki 页面过期或错误:<br />
* 小的改动,有时间可以立即进行修改同步,维护者并不控制页面的编辑权限,越多的人参与维护越好。如果改动较大,请先联系维护者,避免重复劳动。<br />
* 没有时间查看更改,请给页面加上 {{ic|<nowiki>{{out of date}}</nowiki>}} 模版,这样其他贡献者更容易发现需要更新的页面,而读者看到过期标记就可以直接查看英文页面,以免被错误内容误导,白白耽误时间。<br />
* 没有时间翻译,请将过期的中文部分删去,从英文页面中复制更改的部分到中文页面的相应部分,去掉{{ic|<nowiki>{{out of date}}</nowiki>}}模板(如果页面上有的话)并加上{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板,这样其他贡献者就更容易发现需要翻译的页面,而读者也不会被过期的内容误导。<br />
如果发现有页面未翻译:<br />
* 有时间的话,请将页面中的英文部分翻译为中文,并去掉{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板。<br />
* 没有时间翻译,请为页面添加{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板,这样其他的贡献者就能更容易发现需要翻译的页面。<br />
{{注意|在修改页面上的模板时,请同时更新页面维护列表的翻译状态。}}<br />
<br />
== 翻译任务 ==<br />
=== 模板 Article summary 变更为 Related ===<br />
因为 Summary 中的简介基本上和正文的介绍一样,所以页面左边的介绍栏进行了简化,只保留相关文章功能。英文页面正在进行大规模修改,相应的中文页面也需要同步更新。<br />
<br />
需要注意的地方:<br />
* 将第一行改成<br />
: <nowiki>{{Related articles start (简体中文)}}</nowiki><br />
* 如果英文的相关文章存在中文翻译,则替换为简体中文页面。示例:<br />
: <nowiki>{{Related2|Display Manager (简体中文)|显示管理器}}</nowiki><br />
* 示例:[https://wiki.archlinux.org/index.php?title=Start_X_at_Login&diff=0&oldid=270155 英文变更], [https://wiki.archlinux.org/index.php?title=Start_X_at_Login_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=285643&oldid=242662 对应的翻译]<br />
<br />
== 维护翻译 ==<br />
完成页面的翻译只是初步完成任务,及时同步英文页面改动、更新翻译是一个持续性的工作,可能会耗费更多的时间。<br />
<br />
=== 页面认领 ===<br />
所有人都可以认领页面。认领后的责任包括进行翻译,关注英文页面的改动,及时同步翻译。<br />
<br />
为了更好的跟踪英文页面的修改,请务必在设置中启用监视列表邮件通知,并监视对应的英文页面(从设置中找到监视列表,加入英文页面。或者直接到英文页面点击页面顶端的监视标签。这样只要有改动,就会收到邮件通知)。<br />
<br />
{{小贴士|如果收到邮件通知后没有访问页面或者访问了页面却没有登录用户,下次页面改动时就不会再发邮件通知。可以点击监视列表中的'''标记所有页面为已读'''再次获取更新。}}<br />
<br />
如果页面有维护者但长期得不到更新,将会在维护列表中删除维护者。<br />
<br />
=== 翻译状态模板 ===<br />
Arch 作为滚动发行版,软件变化比较快,对应的文档变化也比较快。许多翻译的文章由于缺乏更新,会产生命令运行出错或不起作用等问题。而由于这些过期页面没有及时标记出来,所以用户无法及时获得更新。[[Template:TranslationStatus (简体中文)|翻译状态模板]]就是为了解决这个问题而创建。<br />
<br />
此模板可以起到如下作用:<br />
* 为用户提供翻译状况,包括翻译时间、英文页面的最后版本等<br />
* 用户可以点击查看翻译后,英文页面的改动,这样英文不是很好的用户可以只查看很小一部分英文内容,并判断出是否影响操作。<br />
* 翻译人员可以跟踪页面状况,通过[[Special:WhatLinksHere/Template:TranslationStatus_(简体中文)|模板的反向链接]]可以查找到所有标记页面,查看需要更新翻译的部分。<br />
<br />
[[Template:TranslationStatus (简体中文)|模板页面]]有详细的使用方法。<br />
<br />
=== 页面维护列表 ===<br />
{{注意|请按照拉丁字母顺序添加页面。}}<br />
<br />
翻译状态说明:<br />
;过期:页面内容未与英文页面同步,对应{{ic|<nowiki>{{out of date}}</nowiki>}} 模版<br />
;未翻译:页面中含有英文内容,对应{{ic|<nowiki>{{translateme (简体中文)}}</nowiki>}}模板<br />
;完成:页面已与英文页面同步<br />
<br />
{| class="wikitable sortable collapsible" border="1"<br />
|-<br />
! 页面<br />
! 翻译状态<br />
! 维护者<br />
! class="unsortable" width="30%" | 备注<br />
|-<br />
| [[acpid (简体中文)]]<br />
| 过期<br />
| Cael<br />
|<br />
|-<br />
| [[Advanced Linux Sound Architecture (简体中文)]]<br />
| 翻译中<br />
| ihonliu<br />
| 无<br />
|-<br />
| [[Arch based distributions (active) (简体中文)]]<br />
| 完成<br />
| Joshua<br />
| 勘误中<br />
|-<br />
| [[Amateur radio (简体中文)]]<br />
| 翻译中<br />
| liu-shuyuan<br />
| <br />
|-<br />
| [[AMD Catalyst (简体中文)]]<br />
| 过期<br />
| Shibao Zhao<br />
| 无<br />
|-<br />
| [[ATI (简体中文)]]<br />
| 完成<br />
| skysailing<br />
| 无<br />
|-<br />
| [[AUR helpers (简体中文)]]<br />
| 完成<br />
| Kurobac<br />
| 部分用词可能需要修改<br />
|-<br />
| [[awesome (简体中文)]]<br />
| 进行中<br />
| Cael<br />
| 无<br />
|-<br />
| [[BIND (简体中文)]]<br />
| 完成<br />
| Dargasia<br />
|<br />
|-<br />
| [[Bumblebee (简体中文)]]<br />
| 完成<br />
| Peter<br />
| 无<br />
|-<br />
| [[Chromium (简体中文)]]<br />
| 完成<br />
| Bobby<br />
| 无<br />
|-<br />
| [[Ceph (简体中文)]]<br />
| 翻译中<br />
| Aaron Chen<br />
| 部分未翻译 <br />
|-<br />
| [[Cinnamon (简体中文)]]<br />
| 部分翻译 <br />
| Bobby<br />
| 部分未翻译 <br />
|- <br />
| [[Common Applications (简体中文)]]<br />
| 部分翻译 <br />
| DavidChen<br />
| 翻译中<br />
|-<br />
| [[Common Applications/Science (简体中文)]]<br />
| drop maintain<br />
| 更新,翻译中<br />
|<br />
|-<br />
| [[Compiz (简体中文)]]<br />
| 翻译中<br />
| xiii_1991<br />
| 20140813开始<br />
|-<br />
| [[Conky (简体中文)]]<br />
| 完成<br />
| upi<br />
| 无<br />
|-<br />
| [[Core utilities (简体中文)]]<br />
| 完成<br />
| rentaro, Arisaka<br />
| 无<br />
|-<br />
|-<br />
| [[Clover (简体中文)]]<br />
| 完成<br />
| Yume Kankawa<br />
| 无<br />
|-<br />
| [[Disk cloning (简体中文)]]<br />
| 翻译中<br />
| _spaike97<br />
| 无<br />
|-<br />
| [[Dynamic Kernel Module Support (简体中文)]]<br />
| 完成<br />
| Mithrandir<br />
| 完善中<br />
|-<br />
| [[Emacs (简体中文)]]<br />
| 翻译中<br />
| Jaurung yuanhang<br />
| 未完成<br />
|-<br />
| [[File recovery (简体中文)]]<br />
| 翻译中<br />
| _spaike97<br />
| 无<br />
|-<br />
| [[Fish (简体中文)]]<br />
| 完成<br />
| liu-shuyuan<br />
|<br />
|-<br />
| [[Font configuration (简体中文)]]<br />
| 翻译中<br />
| Jaurung<br />
| 完善中<br />
|-<br />
| [[Fonts (简体中文)]]<br />
| 翻译中<br />
| qqbzg<br />
| 无<br />
|-<br />
| [[GDM (简体中文)]]<br />
| 翻译中<br />
| Junjie Yuan<br />
| 绝大多数内容未翻译,重新进行翻译<br />
|-<br />
| [[GNOME (简体中文)]]<br />
| 完成<br />
| skywet<br />
| <br />
|-<br />
| [[GRUB (简体中文)]]<br />
| 完成<br />
| Armodeniz<br />
| <br />
|-<br />
| [[GRUB/Tips and tricks (简体中文)]]<br />
| 完成<br />
| Armodeniz<br />
| <br />
|-<br />
| [[KDE (简体中文)]]<br />
| 过期<br />
| <br />
| <br />
|-<br />
| [[LAMP (简体中文)]]<br />
| 完成<br />
| Liuzhengyi<br />
| 勘误中<br />
|-<br />
| [[LibreOffice (简体中文)]]<br />
| 完成<br />
| qqbzg<br />
| 勘误中<br />
|-<br />
| [[Libvirt (简体中文)]]<br />
| 完成<br />
| Kurobac<br />
| 需要格式改进<br />
|-<br />
| [[Local Mirror (简体中文)]]<br />
| 完成<br />
| Jason Zhang<br />
| 完善中<br />
|- <br />
| [[MATLAB (简体中文)]]<br />
| 部分翻译 <br />
| Liu Qinyang<br />
|<br />
|-<br />
| [[Minecraft (简体中文)]]<br />
| 完成 <br />
| Xavier Lau<br />
| 页面已经与英文版同步,长期维护中<br />
|-<br />
| [[NetworkManager (简体中文)]]<br />
| 翻译中 <br />
| Jack-lijing, leeking <br />
| 请优先翻译<br />
|-<br />
| [[Network Time Protocol daemon (简体中文)]]<br />
| 完成<br />
| sid<br />
| 完善中<br />
|-<br />
| [[OpenOffice (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Opera (简体中文)]]<br />
| 未翻译<br />
| Bobby<br />
| 请优先翻译此文 <br />
|-<br />
| [[Pacman GUI Frontends (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Pidgin (简体中文)]]<br />
| 进行中<br />
| Cael<br />
| 无 <br />
|- <br />
| [[ranger (简体中文)]]<br />
| 完成<br />
| Jason Zhang<br />
| 完善中<br />
|-<br />
| [[Raspberry Pi (简体中文)]]<br />
| 翻译中<br />
| Mithrandir<br />
| <br />
|-<br />
| [[Reporting bug guidelines (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[Secure Shell (简体中文)]]<br />
| 完成<br />
| Arisaka<br />
| 无<br />
|-<br />
| [[Smart Common Input Method platform (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Steam (简体中文)]]<br />
| 过期<br />
| C0n5t4ntK<br />
| 翻译中<br />
|-<br />
| [[Systemd-timesyncd (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[TLP (简体中文)]]<br />
| 完成<br />
| Skywet<br />
| 持续更新中 <br />
|-<br />
| [[Tomcat (简体中文)]]<br />
| 完成<br />
| Starwing117<br />
| 持续更新中 <br />
|-<br />
| [[Vim (简体中文)]]<br />
| 完成<br />
| 无<br />
| 无<br />
|-<br />
| [[VirtualBox (简体中文)]]<br />
| 翻译至 2017-10-15<br />
| [[User:5long]]<br />
|<br />
|-<br />
| [[VMware (简体中文)]]<br />
| 完成<br />
| ThomasWFan<br />
| 页面已经与英文版同步,长期维护中<br />
|- <br />
| [[Xfce (简体中文)]]<br />
| 完成 <br />
| 无<br />
| 无<br />
|-<br />
| [[Xmonad (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Xrandr (简体中文)]]<br />
| 过期<br />
| 无<br />
| 无<br />
|-<br />
| [[Python打包指引 (简体中文)]]<br />
| 翻译中<br />
| SherlockHolo<br />
| 无<br />
|-<br />
| [[Java (简体中文)]]<br />
| 翻译中<br />
| CaCaCarrot<br />
| 无</div>
C0n5t4ntK