https://wiki.archlinux.org/api.php?action=feedcontributions&user=Hagabaka&feedformat=atomArchWiki - User contributions [en]2024-03-29T13:18:43ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Talk:Samsung_NP740U3L-L02US&diff=457325Talk:Samsung NP740U3L-L02US2016-11-21T00:31:20Z<p>Hagabaka: Add comments about NVidia card and volume buttons</p>
<hr />
<div>The laptop has a NVidia GM108M (GeForce 940MX) graphics card using Optimus technology. I followed instructions on [[Bumblebee]], and it works after reboot, but stops working after resuming after suspend. This may be a [https://github.com/Bumblebee-Project/bbswitch/issues/132 bug] in Bumblebee.<br />
<br />
After recent kernel upgrades, the volume up/down buttons on the side of the laptop stopped working. Possibly related to this [https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629415 bug].<br />
<br />
[[User:Hagabaka|Hagabaka]] ([[User talk:Hagabaka|talk]]) 00:31, 21 November 2016 (UTC)</div>Hagabakahttps://wiki.archlinux.org/index.php?title=SDDM&diff=361486SDDM2015-02-17T08:33:38Z<p>Hagabaka: Add section on configuration GUIs</p>
<hr />
<div>[[Category:KDE]]<br />
[[Category:Display managers]]<br />
[[ja:SDDM]]<br />
[[ru:SDDM]]<br />
[[zh-CN:SDDM]]<br />
{{Related articles start}}<br />
{{Related|Display manager}}<br />
{{Related|Plasma}}<br />
{{Related articles end}}<br />
The [[Wikipedia:Simple Desktop Display Manager|Simple Desktop Display Manager]] (SDDM) is the preferred [[display manager]] for [[KDE]] [[Plasma]] desktop. From Wikipedia:<br />
<br />
:''Simple Desktop Display Manager (SDDM) is a display manager (a graphical login program) for the windowing systems X11 and Wayland. SDDM was written from scratch in C++11 and supports theming via QML. It is the successor of the KDE Display Manager and is used in conjunction with KDE Frameworks 5, KDE Plasma 5 and KDE Applications 5.''<br />
<br />
== Installation ==<br />
<br />
[[pacman|Install]] the {{Pkg|sddm}} package from the [[official repositories]].<br />
<br />
Then follow [[Display manager#Loading the display manager]] to start SDDM at boot. If you're migrating from KDM, the following should work for you:<br />
<br />
{{hc |<br />
# systemctl disable kdm && systemctl enable sddm |<br />
Removed symlink /etc/systemd/system/display-manager.service.<br />
Created symlink from /etc/systemd/system/display-manager.service to /usr/lib/systemd/sddm.service.}}<br />
<br />
== Configuration ==<br />
<br />
The configuration file for SDDM can be found at {{ic|/etc/sddm.conf}}. See {{ic|man sddm.conf}} for all options.<br />
<br />
On systems controlled by [[systemd]], everything should work out of the box, since SDDM defaults to using {{ic|systemd-logind}} for session management. The configuration file will therefore not be created at package installation time. SDDM offers a command for generating a sample configuration file with the default settings if you really want one:<br />
<br />
# sddm --example-config > /etc/sddm.conf<br />
<br />
=== Autologin ===<br />
<br />
SDDM supports automatic login through its configuration file, for example:<br />
<br />
{{hc|<br />
1=/etc/sddm.conf|<br />
2=[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 />
{{Warning|If wrongly configured, automatic login could cause an attacker that has physical access to your notebook to break into your desktop effortlessly. It should only be enabled when another authentication prompt secures the system, e.&nbsp;g.&nbsp;the passphrase for your [[Encrypted Root Filesystem|encrypted root filesystem]].}}<br />
<br />
An option to autologin into KDE Plasma while simultaneously locking the session is not available [https://github.com/sddm/sddm/issues/306 as of the time of this writing].<br />
<br />
You can add a little script that activates the screensaver of KDE to the autostart as a workaround:<br />
<br />
#!/bin/bash <br />
/usr/bin/qdbus-qt4 org.kde.screensaver /ScreenSaver SetActive true &<br />
exit 0<br />
<br />
=== Theme settings ===<br />
<br />
Theme settings can be changed in the {{ic|[Theme]}} section.<br />
<br />
==== Main theme ====<br />
<br />
Set the main theme through the {{ic|Current}} value, e.g. {{ic|1=Current=archlinux}}.<br />
<br />
==== Mouse cursor ====<br />
<br />
To set the mouse cursor theme, set {{ic|CursorTheme}} to your preferred cursor theme.<br />
<br />
==== Changing your avatar ====<br />
<br />
You can simply put a png image named {{ic|username.face.icon}} into the default directory {{ic|/usr/share/sddm/faces/}}. Alternatively you can change the default directory to match your desires, e.g. {{ic|1=FacesDir=/var/lib/AccountsService/users/}}.<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 />
=== Configuration GUI ===<br />
<br />
* KDE Frameworks' System Settings contains an SDDM configuration module.<br />
* There is a Qt-based [https://aur.archlinux.org/packages/sddm-config-editor-git/ sddm-config-editor] in the AUR.<br />
<br />
== Troubleshooting ==<br />
<br />
=== No desktop effects in KDE Plasma ===<br />
<br />
When I changed from KDM to SDDM and logged into KDE Plasma 4, desktop effects were disabled and could not be enabled. It turned out that SDDM wrongly started KDE Plasma in ''Failsafe'' mode. If you cannot enable desktop effects, log out and check the session selection in SDDM before logging back in.<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, add the following to your {{ic|sddm.conf}}:<br />
<br />
{{hc|<br />
1=/etc/sddm.conf|<br />
2=[XDisplay]<br />
MinimumVT=7}}<br />
<br />
=== One or more users don't show up on the greeter ===<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. Modify your {{ic|sddm.conf}} to (for a UID of 501, say):<br />
<br />
{{hc|<br />
1=/etc/sddm.conf|<br />
2=[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}}</div>Hagabakahttps://wiki.archlinux.org/index.php?title=Dofus&diff=336753Dofus2014-09-22T16:27:09Z<p>Hagabaka: /* Manual Installation */ Fix indentation</p>
<hr />
<div>[[Category:Gaming]]<br />
[http://www.dofus.com Dofus] is an MMORPG by [http://www.ankama.com Ankama].<br />
<br />
== AUR ==<br />
Installation can be automated with the [[AUR]] package {{AUR|dofus}}, which depends on {{AUR|ankama-transition}}, the updater.<br />
<br />
Currently the game files are installed under the "games" group with group writability. You can add your user to the group (<tt>usermod -a -G games ''username''</tt>) to take advantage of this. Otherwise, you may need to enter your password in order to update the game files. <br />
<br />
== Manual Installation ==<br />
Ankama provides official Linux packages for Dofus, but some modifications are necessary for them to work on Arch Linux.<br />
<br />
There is no Adobe Air runtime on Arch Linux, so it is necessary to use this [[Adobe air|workaround]] involving <tt>adobe-air-sdk</tt>. <tt>transition</tt> needs to be configured to use the sdk launcher instead of binaries provided by Dofus. Additionally, <tt>transition</tt> will by default attempt to install Adobe Air, and this needs to be disabled in its configuration.<br />
<br />
The {{AUR|dofus}} AUR package accomplishes these with the following code in <tt>transition.conf</tt>:<br />
<br />
bypass_air_installation = true<br />
dofus.reg.path = "${root}/share/reg/bin/air-generic-launcher.sh"<br />
<br />
launcher.command = """<br />
"${root}/bin/air-generic-launcher.sh" --lang=${i18n.lang} --update-server-port=${service_port} --updater_version=v2<br />
<br />
It installs <tt>air-generic-launcher.sh</tt> in the same locations as the game client and sound engine executables, to run them with the SDK launcher:<br />
<br />
#!/bin/bash<br />
<br />
# This is a generic launcher script for AIR applications on Arch Linux<br />
<br />
SCRIPT_PATH=`readlink -f $0`<br />
SCRIPT_DIR=`dirname $SCRIPT_PATH`<br />
BASE_DIR=`readlink -f $SCRIPT_DIR/..`<br />
<br />
if [ "`uname -m`" == "x86_64" ]; then<br />
export GTK_PATH=/usr/lib32/gtk-2.0<br />
export G_FILENAME_ENCODING=UTF-8<br />
fi<br />
<br />
/opt/adobe-air-sdk/bin/adl -nodebug $BASE_DIR/share/META-INF/AIR/application.xml $BASE_DIR/share -- $*<br />
<br />
== Troubleshooting ==<br />
When debugging problems, it is helpful to set the environment variable {{ic|1=AK_LOG_CONSOLE=1}} when running Dofus. It will then print detailed logs in the console.<br />
<br />
A known problem is that some systems require <tt>unset SESSION_MANAGER</tt> in the environment, to avoid crashes on start up.<br />
<br />
Occasionally the updater cannot function because of a leftover process from previous runs. Killing <tt>transition</tt> processes can solve this problem.</div>Hagabakahttps://wiki.archlinux.org/index.php?title=Dofus&diff=336752Dofus2014-09-22T16:26:26Z<p>Hagabaka: /* Manual Installation */ Add air-generic-launcher.sh</p>
<hr />
<div>[[Category:Gaming]]<br />
[http://www.dofus.com Dofus] is an MMORPG by [http://www.ankama.com Ankama].<br />
<br />
== AUR ==<br />
Installation can be automated with the [[AUR]] package {{AUR|dofus}}, which depends on {{AUR|ankama-transition}}, the updater.<br />
<br />
Currently the game files are installed under the "games" group with group writability. You can add your user to the group (<tt>usermod -a -G games ''username''</tt>) to take advantage of this. Otherwise, you may need to enter your password in order to update the game files. <br />
<br />
== Manual Installation ==<br />
Ankama provides official Linux packages for Dofus, but some modifications are necessary for them to work on Arch Linux.<br />
<br />
There is no Adobe Air runtime on Arch Linux, so it is necessary to use this [[Adobe air|workaround]] involving <tt>adobe-air-sdk</tt>. <tt>transition</tt> needs to be configured to use the sdk launcher instead of binaries provided by Dofus. Additionally, <tt>transition</tt> will by default attempt to install Adobe Air, and this needs to be disabled in its configuration.<br />
<br />
The {{AUR|dofus}} AUR package accomplishes these with the following code in <tt>transition.conf</tt>:<br />
<br />
bypass_air_installation = true<br />
dofus.reg.path = "${root}/share/reg/bin/air-generic-launcher.sh"<br />
<br />
launcher.command = """<br />
"${root}/bin/air-generic-launcher.sh" --lang=${i18n.lang} --update-server-port=${service_port} --updater_version=v2<br />
<br />
It installs <tt>air-generic-launcher.sh</tt> in the same locations as the game client and sound engine executables, to run them with the SDK launcher:<br />
<br />
#!/bin/bash<br />
<br />
# This is a generic launcher script for AIR applications on Arch Linux<br />
<br />
SCRIPT_PATH=`readlink -f $0`<br />
SCRIPT_DIR=`dirname $SCRIPT_PATH`<br />
BASE_DIR=`readlink -f $SCRIPT_DIR/..`<br />
<br />
if [ "`uname -m`" == "x86_64" ]; then<br />
export GTK_PATH=/usr/lib32/gtk-2.0<br />
export G_FILENAME_ENCODING=UTF-8<br />
fi<br />
<br />
/opt/adobe-air-sdk/bin/adl -nodebug $BASE_DIR/share/META-INF/AIR/application.xml $BASE_DIR/share -- $*<br />
<br />
== Troubleshooting ==<br />
When debugging problems, it is helpful to set the environment variable {{ic|1=AK_LOG_CONSOLE=1}} when running Dofus. It will then print detailed logs in the console.<br />
<br />
A known problem is that some systems require <tt>unset SESSION_MANAGER</tt> in the environment, to avoid crashes on start up.<br />
<br />
Occasionally the updater cannot function because of a leftover process from previous runs. Killing <tt>transition</tt> processes can solve this problem.</div>Hagabakahttps://wiki.archlinux.org/index.php?title=Dofus&diff=331735Dofus2014-08-21T16:13:52Z<p>Hagabaka: Created page with "[http://www.dofus.com Dofus] is an MMORPG by [http://www.ankama.com Ankama]. === AUR === Installation can be automated with the AUR package [https://aur.archlinux.org/package..."</p>
<hr />
<div>[http://www.dofus.com Dofus] is an MMORPG by [http://www.ankama.com Ankama].<br />
<br />
=== AUR ===<br />
Installation can be automated with the AUR package [https://aur.archlinux.org/packages/dofus/ <tt>dofus</tt>], which depends on [https://aur.archlinux.org/packages/ankama-transition <tt>ankama-transition</tt>], the updater.<br />
<br />
Currently the game files are installed under the "games" group with group writability. You can add your user to the group (<tt>usermod -a -G games ''username''</tt>) to take advantage of this. Otherwise, you may need to enter your password in order to update the game files. <br />
<br />
=== Manual Installation ===<br />
Ankama provides official Linux packages for Dofus, but some modifications are necessary for them to work on Arch Linux.<br />
<br />
There is no Adobe Air runtime on Arch Linux, so it is necessary to use this [https://wiki.archlinux.org/index.php/Adobe_air workaround] involving <tt>adobe-air-sdk</tt>. <tt>transition</tt> needs to be configured to use the sdk launcher instead of binaries provided by Dofus. Additionally, <tt>transition</tt> will by default attempt to install Adobe Air, and this needs to be disabled in its configuration.<br />
<br />
The <tt>dofus</tt> AUR package accomplishes these with the following code in <tt>transition.conf</tt>, and an <tt>air-generic-launcher.sh</tt> file which runs the game client and sound engine with SDK launcher:<br />
<br />
bypass_air_installation = true<br />
dofus.reg.path = "${root}/share/reg/bin/air-generic-launcher.sh"<br />
<br />
launcher.command = """<br />
"${root}/bin/air-generic-launcher.sh" --lang=${i18n.lang} --update-server-port=${service_port} --updater_version=v2<br />
<br />
=== Troubleshooting ===<br />
When debugging problems, it is helpful to set the environment variable <tt>AK_LOG_CONSOLE=1</tt> when running Dofus. It will then print detailed logs in the console.<br />
<br />
A known problem is that some systems require <tt>unset SESSION_MANAGER</tt> in the environment, to avoid crashes on start up.<br />
<br />
Occasionally the updater cannot function because of a leftover process from previous runs. Killing <tt>transition</tt> processes can solve this problem.</div>Hagabakahttps://wiki.archlinux.org/index.php?title=Unofficial_user_repositories&diff=298423Unofficial user repositories2014-02-16T20:17:55Z<p>Hagabaka: Add pipelight repository</p>
<hr />
<div>[[Category:Package management]]<br />
{{Related articles start}}<br />
{{Related|pacman-key}}<br />
{{Related|Official repositories}}<br />
{{Related articles end}} <br />
Because the AUR only allows users to upload PKGBUILD and other package build related files, but does not provide a means for distributing a binary package, a user may want to create a binary repository of their packages elsewhere. See [[Pacman Tips#Custom local repository]] for more information.<br />
<br />
If you have your own repository, please add it to this page, so that all the other users will know where to find your packages. Please keep the following rules when adding new repositories:<br />
<br />
* Keep the lists in alphabetical order.<br />
* Include some information about the maintainer: include at least a (nick)name and some form of contact information (web site, email address, user page on ArchWiki or the forums, etc.).<br />
* If the repository is of the ''signed'' variety, please include a key-id, possibly using it as the anchor for a link to its keyserver; if the key is not on a keyserver, include a link to the key file.<br />
* Include some short description (e.g. the category of packages provided in the repository).<br />
* If there is a page (either on ArchWiki or external) containing more information about the repository, include a link to it.<br />
* If possible, avoid using comments in code blocks. The formatted description is much more readable. Users who want some comments in their {{ic|pacman.conf}} can easily create it on their own.<br />
<br />
{{Note|If you are looking to add a signed repository to your {{ic|pacman.conf}}, you must be familiar with [[Pacman-key#Adding unofficial keys]].}}<br />
<br />
{{Expansion|Please fill in the missing information about maintainers.}}<br />
<br />
== Any ==<br />
<br />
"Any" repositories are architecture-independent. In other words, they can be used on both i686 and x86_64 systems.<br />
<br />
=== Signed ===<br />
<br />
==== infinality-bundle-fonts ====<br />
<br />
* '''Maintainer:''' [http://bohoomil.cu.cc/ bohoomil]<br />
* '''Description:''' infinality-bundle-fonts repository.<br />
* '''Upstream page:''' [[Infinality-bundle+fonts]]<br />
* '''Key-ID:''' 962DDE58<br />
<br />
{{bc|<nowiki><br />
[infinality-bundle-fonts]<br />
Server = http://ibn.net63.net/infinality-bundle-fonts<br />
</nowiki>}}<br />
<br />
==== xyne-any ====<br />
<br />
* '''Maintainer:''' [https://www.archlinux.org/trustedusers/#xyne Xyne]<br />
* '''Description:''' A repository for Xyne's own projects containing packages for "any" architecture.<br />
* '''Upstream page:''' http://xyne.archlinux.ca/projects/<br />
* '''Key-ID:''' Not needed, as maintainer is a TU<br />
<br />
{{Note|Use this repository only if there is no matching {{ic|[xyne-*]}} repository for your architecture.}}<br />
<br />
{{bc|<nowiki><br />
[xyne-any]<br />
Server = http://xyne.archlinux.ca/repos/xyne<br />
</nowiki>}}<br />
<br />
=== Unsigned ===<br />
<br />
==== archlinuxgr-any ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' The Hellenic (Greek) unofficial Arch Linux repository with many interesting packages.<br />
<br />
{{bc|<nowiki><br />
[archlinuxgr-any]<br />
Server = http://archlinuxgr.tiven.org/archlinux/any<br />
</nowiki>}}<br />
<br />
== Both i686 and x86_64 ==<br />
<br />
Repositories with both i686 and x86_64 versions. The {{ic|$arch}} variable will be set automatically by pacman.<br />
<br />
=== Signed ===<br />
<br />
==== apathism ====<br />
<br />
* '''Maintainer:''' Koryabkin Ivan ([https://aur.archlinux.org/account/apathism/ apathism])<br />
* '''Upstream page:''' https://apathism.net/<br />
* '''Description:''' AUR packages that would take long to build, such as {{AUR|firefox-kde-opensuse}} and {{AUR|mysql-workbench}}.<br />
* '''Key-ID:''' 3E37398D<br />
* '''Keyfile:''' http://www.apathism.net/archlinux/apathism.key<br />
<br />
{{bc|<nowiki><br />
[apathism]<br />
Server = http://apathism.net/archlinux/<br />
</nowiki>}}<br />
<br />
==== blackarch ====<br />
<br />
* '''Maintainer''' (There are multiple maintainers. The person listed is the one whose key-id is given): Evan Teitelman (paraxor)<br />
* '''Description:''' Tools for penetration testing, security auditing, and security research.<br />
* '''Upstream page:''' http://blackarch.org/<br />
* '''Key-ID:''' EA87E4E3<br />
<br />
{{bc|<nowiki><br />
[blackarch]<br />
Server = http://blackarch.org/blackarch/$repo/os/$arch<br />
</nowiki>}}<br />
<br />
==== carstene1ns ====<br />
<br />
* '''Maintainer:''' [[User:Carstene1ns|Carsten Teibes]]<br />
* '''Description:''' AUR packages maintained and/or used by Carsten Teibes (games/Wii/lib32/Python)<br />
* '''Upstream page:''' http://arch.carsten-teibes.de (still under construction)<br />
* '''Key-ID:''' 2476B20B<br />
<br />
{{bc|<nowiki><br />
[carstene1ns]<br />
Server = http://repo.carsten-teibes.de/$arch<br />
</nowiki>}}<br />
<br />
==== catalyst ====<br />
<br />
* '''Maintainer:''' [[User:Vi0L0 | Vi0l0]]<br />
* '''Description:''' ATI Catalyst proprietary drivers.<br />
* '''Upstream Page:''' http://catalyst.wirephire.com<br />
* '''Key-ID:''' 653C3094<br />
<br />
{{bc|<nowiki><br />
[catalyst]<br />
Server = http://catalyst.wirephire.com/repo/catalyst/$arch<br />
## Mirrors, if the primary server does not work or is too slow:<br />
#Server = http://70.239.162.206/catalyst-mirror/repo/catalyst/$arch<br />
#Server = http://mirror.rts-informatique.fr/archlinux-catalyst/repo/catalyst/$arch<br />
</nowiki>}}<br />
<br />
==== catalyst-hd234k ====<br />
<br />
* '''Maintainer:''' [[User:Vi0L0 | Vi0l0]]<br />
* '''Description:''' ATI Catalyst proprietary drivers.<br />
* '''Upstream Page:''' http://catalyst.wirephire.com<br />
* '''Key-ID:''' 653C3094<br />
<br />
{{bc|<nowiki><br />
[catalyst-hd234k]<br />
Server = http://catalyst.wirephire.com/repo/catalyst-hd234k/$arch<br />
## Mirrors, if the primary server does not work or is too slow:<br />
#Server = http://70.239.162.206/catalyst-mirror/repo/catalyst-hd234k/$arch<br />
#Server = http://mirror.rts-informatique.fr/archlinux-catalyst/repo/catalyst-hd234k/$arch<br />
</nowiki>}}<br />
<br />
==== city ====<br />
<br />
* '''Maintainer:''' [https://www.archlinux.org/trustedusers/#bgyorgy Balló György]<br />
* '''Description:''' Experimental/unpopular packages.<br />
* '''Upstream page:''' http://pkgbuild.com/~bgyorgy/city.html<br />
* '''Key-ID:''' Not needed, as maintainer is a TU<br />
<br />
{{bc|<nowiki><br />
[city]<br />
Server = http://pkgbuild.com/~bgyorgy/$repo/os/$arch<br />
</nowiki>}}<br />
<br />
==== crypto ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' Includes tomb, tomb-git, and other related software.<br />
<br />
{{bc|<nowiki><br />
[crypto]<br />
Server = http://tomb.dyne.org/arch_repo/$arch<br />
</nowiki>}}<br />
<br />
==== demz-repo-core ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' Packages for ZFS on Arch Linux.<br />
* '''Upstream page:''' http://demizerone.com/archzfs<br />
* '''Key-ID:''' 0EE7A126<br />
<br />
{{bc|<nowiki><br />
[demz-repo-core]<br />
Server = http://demizerone.com/$repo/$arch<br />
</nowiki>}}<br />
<br />
==== demz-repo-archiso ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' Packages for installing ZFSfrom an Arch ISO live disk<br />
* '''Upstream page:''' http://demizerone.com/archzfs<br />
* '''Key-ID:''' 0EE7A126<br />
<br />
{{bc|<nowiki><br />
[demz-repo-archiso]<br />
Server = http://demizerone.com/$repo/$arch<br />
</nowiki>}}<br />
<br />
==== gtmanfred ====<br />
<br />
* '''Maintainer:''' [https://www.archlinux.org/trustedusers/#dwallace Daniel Wallace]<br />
* '''Description:''' This repository contains git/svn/hg versions of a lot of my packages.<br />
* '''Key ID:''' Not required, as the maintainer is a TU<br />
<br />
{{bc|<nowiki><br />
[gtmanfred]<br />
Server = http://code.gtmanfred.com/$repo/$arch<br />
</nowiki>}}<br />
<br />
==== infinality-bundle ====<br />
<br />
* '''Maintainer:''' [http://bohoomil.cu.cc/ bohoomil]<br />
* '''Description:''' infinality-bundle main repository.<br />
* '''Upstream page:''' [[Infinality-bundle+fonts]]<br />
* '''Key-ID:''' 962DDE58<br />
<br />
{{bc|<nowiki><br />
[infinality-bundle]<br />
Server = http://ibn.net63.net/infinality-bundle/$arch<br />
</nowiki>}}<br />
<br />
==== pipelight ====<br />
<br />
* '''Maintainer:''' <br />
* '''Description:''' Pipelight and wine-compholio<br />
* '''Upstream page:''' [http://fds-team.de/ fds-team.de]<br />
* '''Key-ID:''' E49CC0415DC2D5CA<br />
* '''Keyfile:''' http://repos.fds-team.de/Release.key<br />
{{bc|<nowiki>[pipelight]<br />
Server = http://repos.fds-team.de/stable/arch/$arch</nowiki>}}<br />
<br />
==== repo-ck ====<br />
<br />
* '''Maintainer:''' [[User:Graysky|graysky]]<br />
* '''Description:''' Kernel and modules with Brain Fuck Scheduler and all the goodies in the ck1 patch set.<br />
* '''Upstream page:''' [http://repo-ck.com repo-ck.com]<br />
* '''Wiki:''' [[repo-ck]]<br />
* '''Key-ID:''' 5EE46C4C<br />
<br />
{{bc|<nowiki><br />
[repo-ck]<br />
Server = http://repo-ck.com/$arch<br />
</nowiki>}}<br />
<br />
==== sergej-repo ====<br />
<br />
* '''Maintainer:''' [https://www.archlinux.org/trustedusers/#spupykin Sergej Pupykin]<br />
* '''Description:''' psi-plus, owncloud-git, ziproxy, android, MySQL, and other stuff. Some packages also available for armv7h.<br />
* '''Key-ID:''' Not required, as maintainer is a TU<br />
<br />
{{bc|<nowiki><br />
[sergej-repo]<br />
Server = http://repo.p5n.pp.ru/$repo/os/$arch<br />
</nowiki>}}<br />
<br />
=== Unsigned ===<br />
<br />
{{Note|Users will need to add the following to these entries: {{ic|1=SigLevel = PackageOptional}}}}<br />
<br />
==== alucryd ====<br />
<br />
* '''Maintainer:''' [https://www.archlinux.org/trustedusers/#alucryd Maxime Gauduin]<br />
* '''Description:''' Repository containing various packages Maxime Gauduin maintains (or not) in the AUR.<br />
<br />
{{bc|<nowiki><br />
[alucryd]<br />
Server = http://pkgbuild.com/~alucryd/$repo/$arch<br />
</nowiki>}}<br />
<br />
==== archaudio-production ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' verified PKGBUILDs ''and'' tested packages<br />
<br />
{{bc|<nowiki><br />
[archaudio-production]<br />
Server = http://repos.archaudio.org/$repo/$arch<br />
</nowiki>}}<br />
<br />
==== archaudio-preview ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' unverified PKGBUILDs ''and/or'' untested packages<br />
<br />
{{bc|<nowiki><br />
[archaudio-preview]<br />
Server = http://repos.archaudio.org/$repo/$arch<br />
</nowiki>}}<br />
<br />
==== archaudio-nightly ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' verified development PKGBUILDs<br />
<br />
{{bc|<nowiki><br />
[archaudio-nightly]<br />
Server = http://repos.archaudio.org/$repo/$arch<br />
</nowiki>}}<br />
<br />
==== archaudio-experimental ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' unverified development PKGBUILDs<br />
<br />
{{bc|<nowiki><br />
[archaudio-experimental]<br />
Server = http://repos.archaudio.org/$repo/$arch<br />
</nowiki>}}<br />
<br />
==== archlinuxcn ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' The Chinese Arch Linux communities packages.<br />
<br />
{{bc|<nowiki><br />
[archlinuxcn]<br />
Server = http://repo.archlinuxcn.org/$arch<br />
</nowiki>}}<br />
<br />
==== archlinuxfr ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:'''<br />
* '''Upstream page:''' http://afur.archlinux.fr<br />
<br />
{{bc|<nowiki><br />
[archlinuxfr]<br />
Server = http://repo.archlinux.fr/$arch<br />
</nowiki>}}<br />
<br />
==== archlinuxgis ====<br />
* '''Maintainer:'''<br />
* '''Description:''' Maintainers needed - low bandwidth<br />
<br />
{{bc|<nowiki><br />
[archlinuxgis]<br />
Server = http://archlinuxgis.no-ip.org/$arch<br />
</nowiki>}}<br />
<br />
==== archlinuxgr ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:'''<br />
<br />
{{bc|<nowiki><br />
[archlinuxgr]<br />
Server = http://archlinuxgr.tiven.org/archlinux/$arch<br />
</nowiki>}}<br />
<br />
==== archlinuxgr-kde4 ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' KDE4 packages (plasmoids, themes etc) provided by the Hellenic (Greek) Arch Linux community<br />
<br />
{{bc|<nowiki><br />
[archlinuxgr-kde4]<br />
Server = http://archlinuxgr.tiven.org/archlinux-kde4/$arch<br />
</nowiki>}}<br />
<br />
==== archstuff ====<br />
{{Note|Off-line since 2014-01-06.}}<br />
* '''Maintainer:'''<br />
* '''Description:''' AUR's most voted and many bin32-* and lib32-* packages.<br />
<br />
{{bc|<nowiki><br />
[archstuff]<br />
Server = http://archstuff.vs169092.vserver.de/$arch<br />
</nowiki>}}<br />
<br />
==== arsch ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' From users of orgizm.net<br />
<br />
{{bc|<nowiki><br />
[arsch]<br />
Server = http://arsch.orgizm.net/$arch<br />
</nowiki>}}<br />
<br />
==== aurbin ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' Automated build of AUR packages<br />
<br />
{{bc|<nowiki><br />
[aurbin]<br />
Server = http://aurbin.net/$arch<br />
</nowiki>}}<br />
<br />
==== cinnamon ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' Stable and actively developed Cinnamon packages (Applets, Themes, Extensions), plus others (Hotot, qBitTorrent, GTK themes, Perl modules, and more).<br />
<br />
{{bc|<nowiki><br />
[cinnamon]<br />
Server = http://archlinux.zoelife4u.org/cinnamon/$arch<br />
</nowiki>}}<br />
<br />
==== ede ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' Equinox Desktop Environment repository<br />
<br />
{{bc|<nowiki><br />
[ede]<br />
Server = http://www.equinox-project.org/repos/arch/$arch<br />
</nowiki>}}<br />
<br />
==== haskell-core ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' Arch-Haskell repository<br />
* '''Upstream page:''' [[Haskell Package Guidelines]]<br />
<br />
{{bc|<nowiki><br />
[haskell-core]<br />
Server = http://xsounds.org/~haskell/core/$arch<br />
</nowiki>}}<br />
<br />
==== heftig ====<br />
<br />
* '''Maintainer:''' [https://www.archlinux.org/trustedusers/#heftig Jan Steffens]<br />
* '''Description:''' Includes linux-zen and aurora (Firefox development build - works alongside {{Pkg|firefox}} in the ''extra'' repository).<br />
* '''Upstream page:''' https://bbs.archlinux.org/viewtopic.php?id=117157<br />
<br />
{{bc|<nowiki><br />
[heftig]<br />
Server = http://pkgbuild.com/~heftig/repo/$arch<br />
</nowiki>}}<br />
<br />
==== herecura-stable ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' additional packages not found in the ''community'' repository<br />
<br />
{{bc|<nowiki><br />
[herecura-stable]<br />
Server = http://repo.herecura.be/herecura-stable/$arch<br />
</nowiki>}}<br />
<br />
==== herecura-testing ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' additional packages for testing build against stable arch<br />
<br />
{{bc|<nowiki><br />
[herecura-testing]<br />
Server = http://repo.herecura.be/herecura-testing/$arch<br />
</nowiki>}}<br />
<br />
==== jelle ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:'''<br />
<br />
{{bc|<nowiki><br />
[jelle]<br />
Server = http://pkgbuild.com/~jelle/repo/$arch<br />
</nowiki>}}<br />
<br />
==== mesa-git ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' Mesa git builds for the ''testing'' and ''multilib-testing'' repositories<br />
<br />
{{bc|<nowiki><br />
[mesa-git]<br />
Server = http://pkgbuild.com/~lcarlier/$repo/$arch<br />
</nowiki>}}<br />
<br />
==== oracle ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' Oracle database client<br />
<br />
{{Warning|By adding this you are agreeing to the Oracle license at http://www.oracle.com/technetwork/licenses/instant-client-lic-152016.html}}<br />
<br />
{{bc|<nowiki><br />
[oracle]<br />
Server = http://linux.shikadi.net/arch/$repo/$arch/<br />
</nowiki>}}<br />
<br />
==== pantheon ====<br />
<br />
* '''Maintainer:''' [https://www.archlinux.org/trustedusers/#alucryd Maxime Gauduin]<br />
* '''Description:''' Repository containing Pantheon-related packages<br />
<br />
{{bc|<nowiki><br />
[pantheon]<br />
Server = http://pkgbuild.com/~alucryd/$repo/$arch<br />
</nowiki>}}<br />
<br />
==== paulburton-fitbitd ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' Contains fitbitd for synchronizing FitBit trackers<br />
<br />
{{bc|<nowiki><br />
[paulburton-fitbitd]<br />
Server = http://www.paulburton.eu/arch/fitbitd/$arch<br />
</nowiki>}}<br />
<br />
==== pfkernel ====<br />
<br />
* '''Maintainer:''' [[User:Nous|nous]]<br />
* '''Description:''' Generic and optimized binaries of the ARCH kernel patched with BFS, TuxOnIce, BFQ, Aufs3, linux-pf, kernel26-pf, gdm-old, nvidia-pf, nvidia-96xx, xchat-greek, arora-git<br />
* '''Note:''' To browse through the repository, one needs to append {{ic|index.html}} after the server URL (this is an intentional quirk of Dropbox). For example, for x86_64, point your browser to http://dl.dropbox.com/u/11734958/x86_64/index.html or start at http://tiny.cc/linux-pf<br />
<br />
{{bc|<nowiki><br />
[pfkernel]<br />
Server = http://dl.dropbox.com/u/11734958/$arch<br />
</nowiki>}}<br />
<br />
==== suckless ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' suckless.org packages<br />
<br />
{{bc|<nowiki><br />
[suckless]<br />
Server = http://dl.suckless.org/arch/$arch<br />
</nowiki>}}<br />
<br />
==== unity ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' unity packages for Arch<br />
<br />
{{bc|<nowiki><br />
[unity]<br />
Server = http://unity.xe-xe.org/$arch<br />
</nowiki>}}<br />
<br />
==== unity-extra ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' unity extra packages for Arch<br />
<br />
{{bc|<nowiki><br />
[unity-extra]<br />
Server = http://unity.xe-xe.org/extra/$arch<br />
</nowiki>}}<br />
<br />
==== unity ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' unity packages for Arch<br />
<br />
{{bc|<nowiki><br />
[unity]<br />
Server = http://unity.humbug.in/$arch<br />
</nowiki>}}<br />
<br />
==== unity-extra ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' unity extra packages for Arch<br />
<br />
{{bc|<nowiki><br />
[unity-extra]<br />
Server = http://unity.humbug.in/extra/$arch<br />
</nowiki>}}<br />
<br />
==== home_tarakbumba_archlinux_Arch_Extra_standard ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' Contains a few pre-built AUR packages (zemberek, firefox-kde-opensuse, etc.)<br />
<br />
{{bc|<nowiki><br />
[home_tarakbumba_archlinux_Arch_Extra_standard]<br />
Server = http://download.opensuse.org/repositories/home:/tarakbumba:/archlinux/Arch_Extra_standard/$arch<br />
</nowiki>}}<br />
<br />
== i686 only ==<br />
<br />
=== Signed ===<br />
<br />
==== eee-ck ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' Kernel and modules optimized for Asus Eee PC 701, with -ck patchset.<br />
<br />
{{bc|<nowiki><br />
[eee-ck]<br />
Server = http://zembla.shatteredsymmetry.com/repo<br />
</nowiki>}}<br />
<br />
==== xyne-i686 ====<br />
<br />
* '''Maintainer:''' [https://www.archlinux.org/trustedusers/#xyne Xyne]<br />
* '''Description:''' A repository for Xyne's own projects containing packages for the "i686" architecture.<br />
* '''Upstream page:''' http://xyne.archlinux.ca/projects/<br />
* '''Key-ID:''' Not required, as maintainer is a TU<br />
<br />
{{Note|This includes all packages in [[#xyne-any|<nowiki>[xyne-any]</nowiki>]].}}<br />
<br />
{{bc|<nowiki><br />
[xyne-i686]<br />
Server = http://xyne.archlinux.ca/repos/xyne<br />
</nowiki>}}<br />
<br />
=== Unsigned ===<br />
<br />
==== andrwe ====<br />
<br />
* '''Maintainer:''' Andrwe Lord Weber<br />
* '''Description:''' each program I'm using on x86_64 is compiled for i686 too<br />
* '''Upstream page:''' http://andrwe.org/linux/repository<br />
<br />
{{bc|<nowiki><br />
[andrwe]<br />
Server = http://repo.andrwe.org/i686<br />
</nowiki>}}<br />
<br />
==== batchbin ====<br />
{{Expansion|Who is the maintainer?}}<br />
{{Note|Offline since 2014-02-15.}}<br />
* '''Maintainer:'''<br />
* '''Description:''' My personal projects and utilities which I feel can benefit others.<br />
<br />
{{bc|<nowiki><br />
[batchbin]<br />
Server = http://batchbin.ueuo.com/archlinux<br />
</nowiki>}}<br />
<br />
==== esclinux ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' Mostly games, interactive fiction, and abc notation stuff already on the AUR.<br />
<br />
{{bc|<nowiki><br />
[esclinux]<br />
Server = http://download.tuxfamily.org/esclinuxcd/ressources/repo/i686/<br />
</nowiki>}}<br />
<br />
==== kpiche ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' Stable OpenSync packages.<br />
<br />
{{bc|<nowiki><br />
[kpiche]<br />
Server = http://kpiche.archlinux.ca/repo<br />
</nowiki>}}<br />
<br />
==== kernel26-pae ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' PAE-enabled 32-bit kernel 2.6.39<br />
<br />
{{bc|<nowiki><br />
[kernel26-pae]<br />
Server = http://kernel26-pae.archlinux.ca/<br />
</nowiki>}}<br />
<br />
==== linux-pae ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' PAE-enabled 32-bit kernel 3.0<br />
<br />
{{bc|<nowiki><br />
[linux-pae]<br />
Server = http://pae.archlinux.ca/<br />
</nowiki>}}<br />
<br />
==== rfad ====<br />
<br />
* '''Maintainer:''' requiem [at] archlinux.us <br />
* '''Description:''' Repository made by haxit<br />
<br />
{{bc|<nowiki><br />
[rfad]<br />
Server = http://web.ncf.ca/ey723/archlinux/repo/<br />
</nowiki>}}<br />
<br />
==== studioidefix ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' Precompiled boxee packages.<br />
<br />
{{bc|<nowiki><br />
[studioidefix]<br />
Server = http://studioidefix.googlecode.com/hg/repo/i686<br />
</nowiki>}}<br />
<br />
== x86_64 only ==<br />
<br />
=== Signed ===<br />
<br />
==== freifunk-rheinland ====<br />
<br />
* '''Maintainer:''' nomaster<br />
* '''Description:''' Packages for the Freifunk project: batman-adv, batctl, fastd and dependencies.<br />
<br />
{{bc|<nowiki><br />
[freifunk-rheinland]<br />
Server = http://mirror.fluxent.de/archlinux-custom/$repo/os/$arch<br />
</nowiki>}}<br />
<br />
==== heimdal ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' Packages are compiled against Heimdal instead of MIT KRB5. Meant to be dropped before {{ic|[core]}} in {{ic|pacman.conf}}. All packages are signed.<br />
* '''Upstream page:''' https://github.com/Kiwilight/Heimdal-Pkgbuilds<br />
{{Warning|Be careful. Do not use this unless you know what you are doing because many of these packages override packages from the ''core'' and ''extra'' repositories}}<br />
<br />
{{bc|<nowiki><br />
[heimdal]<br />
Server = http://www.kiwilight.com/heimdal/$arch/<br />
</nowiki>}}<br />
<br />
==== infinality-bundle-multilib ====<br />
<br />
* '''Maintainer:''' [http://bohoomil.cu.cc/ bohoomil]<br />
* '''Description:''' infinality-bundle multilib repository.<br />
* '''Upstream page:''' [[Infinality-bundle+fonts]]<br />
* '''Key-ID:''' 962DDE58<br />
<br />
{{bc|<nowiki><br />
[infinality-bundle-multilib]<br />
Server = http://ibn.net63.net/infinality-bundle-multilib/$arch<br />
</nowiki>}}<br />
<br />
==== siosm-aur ====<br />
<br />
* '''Maintainer:''' [https://tim.siosm.fr/about/ Timothee Ravier]<br />
* '''Description:''' packages also available in the Arch User Repository, sometimes with minor fixes<br />
* '''Upstream page:''' https://tim.siosm.fr/repositories/<br />
* '''Key-ID:''' 78688F83<br />
<br />
{{bc|<nowiki><br />
[siosm-aur]<br />
Server = http://repo.siosm.fr/$repo/<br />
</nowiki>}}<br />
<br />
==== siosm-selinux ====<br />
<br />
* '''Maintainer:''' [https://tim.siosm.fr/about/ Timothee Ravier]<br />
* '''Description:''' packages required for SELinux support – work in progress (notably, missing an Arch Linux-compatible SELinux policy). See the [[SELinux]] page for details.<br />
* '''Upstream page:''' https://tim.siosm.fr/repositories/<br />
* '''Key-ID:''' 78688F83<br />
<br />
{{bc|<nowiki><br />
[siosm-selinux]<br />
Server = http://repo.siosm.fr/$repo/<br />
</nowiki>}}<br />
<br />
==== subtitlecomposer ====<br />
<br />
* '''Maintainer:''' Mladen Milinkovic (maxrd2)<br />
* '''Description:''' Subtitle Composer stable and nightly builds<br />
* '''Upstream page:''' https://github.com/maxrd2/subtitlecomposer<br />
* '''Key-ID:''' EA8CEBEE<br />
<br />
{{bc|<nowiki><br />
[subtitlecomposer]<br />
Server = http://smoothware.net/$repo/$arch<br />
</nowiki>}}<br />
<br />
==== xyne-x86_64 ====<br />
<br />
* '''Maintainer:''' [https://www.archlinux.org/trustedusers/#xyne Xyne]<br />
* '''Description:''' A repository for Xyne's own projects containing packages for the "x86_64" architecture.<br />
* '''Upstream page:''' http://xyne.archlinux.ca/projects/<br />
* '''Key-ID:''' Not required as maintainer is a TU<br />
<br />
{{Note|This includes all packages in [[#xyne-any|<nowiki>[xyne-any]</nowiki>]].}}<br />
<br />
{{bc|<nowiki><br />
[xyne-x86_64]<br />
Server = http://xyne.archlinux.ca/repos/xyne<br />
</nowiki>}}<br />
<br />
=== Unsigned ===<br />
<br />
{{Note|Users will need to add the following to these entries: {{ic|1=SigLevel = PackageOptional}}}}<br />
<br />
==== andrwe ====<br />
<br />
* '''Maintainer:''' Andrwe Lord Weber<br />
* '''Description:''' contains programs I'm using on many systems<br />
* '''Upstream page:''' http://andrwe.dyndns.org/doku.php/blog/repository {{Linkrot|2013|11|30}}<br />
<br />
{{bc|<nowiki><br />
[andrwe]<br />
Server = http://repo.andrwe.org/x86_64<br />
</nowiki>}}<br />
<br />
==== archstudio ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' Audio and Music Packages optimized for Intel Core i3, i5, and i7.<br />
* '''Upstream page:''' http://www.xsounds.org/~archstudio<br />
<br />
{{bc|<nowiki><br />
[archstudio]<br />
Server = http://www.xsounds.org/~archstudio/x86_64<br />
</nowiki>}}<br />
<br />
==== brtln ====<br />
<br />
* '''Maintainer:''' [https://www.archlinux.org/trustedusers/#bpiotrowski Bartłomiej Piotrowski]<br />
* '''Description:''' Alpha releases of MariaDB, Wine with win32 support only, and some VCS packages.<br />
<br />
{{bc|<nowiki><br />
[brtln]<br />
Server = http://pkgbuild.com/~barthalion/brtln/$arch/<br />
</nowiki>}}<br />
<br />
==== hawaii ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' hawaii Qt5/Wayland-based desktop environment<br />
* '''Upstream page:''' http://www.maui-project.org/<br />
<br />
{{bc|<nowiki><br />
[hawaii]<br />
Server = http://archive.maui-project.org/archlinux/$repo/os/$arch<br />
</nowiki>}}<br />
<br />
==== pnsft-pur ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' Japanese input method packages Mozc (vanilla) and libkkc<br />
<br />
{{bc|<nowiki><br />
[pnsft-pur]<br />
Server = http://downloads.sourceforge.net/project/pnsft-aur/pur/x86_64<br />
</nowiki>}}<br />
<br />
==== mingw-w64 ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' Almost all mingw-w64 packages in the AUR updated every 8 hours.<br />
* '''Upstream page:''' http://arch.linuxx.org<br />
<br />
{{bc|<nowiki><br />
[mingw-w64]<br />
Server = http://downloads.sourceforge.net/project/mingw-w64-archlinux/$arch<br />
Server = http://arch.linuxx.org/archlinux/$repo/os/$arch<br />
</nowiki>}}<br />
<br />
==== rightscale ====<br />
<br />
* '''Maintainer:''' Chris Fordham <chris@fordham-nagy.id.au><br />
* '''Description:''' Packages for RightScale including the RightLink cloud instance agent. Install the package, rightscale-agent.<br />
<br />
{{bc|<nowiki><br />
[rightscale]<br />
Server = https://s3-us-west-1.amazonaws.com/archlinux-rightscale/$arch<br />
</nowiki>}}<br />
<br />
==== seiichiro ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' VDR and some plugins, mms, foo2zjs-drivers<br />
<br />
{{bc|<nowiki><br />
[seiichiro]<br />
Server = http://repo.seiichiro0185.org/x86_64<br />
</nowiki>}}<br />
<br />
==== studioidefix ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' Precompiled boxee packages.<br />
<br />
{{bc|<nowiki><br />
[studioidefix]<br />
Server = http://studioidefix.googlecode.com/hg/repo/x86_64<br />
</nowiki>}}<br />
<br />
==== zen ====<br />
<br />
* '''Maintainer:'''<br />
* '''Description:''' Various and zengeist AUR packages.<br />
<br />
{{bc|<nowiki><br />
[zen]<br />
Server = http://zloduch.cz/archlinux/x86_64<br />
</nowiki>}}<br />
<br />
== armv6h only ==<br />
<br />
=== Unsigned ===<br />
<br />
==== arch-fook-armv6h ====<br />
<br />
* '''Maintainer:''' Jaska Kivelä <jaska@kivela.net><br />
* '''Description:''' Stuff that I have compiled for my Raspberry PI. Including Enlightenment and home automation stuff.<br />
<br />
{{bc|<nowiki><br />
[arch-fook-armv6h]<br />
Server = http://kivela.net/jaska/arch-fook-armv6h<br />
</nowiki>}}</div>Hagabakahttps://wiki.archlinux.org/index.php?title=Pipelight&diff=298420Pipelight2014-02-16T20:07:37Z<p>Hagabaka: /* Repository */</p>
<hr />
<div>[[Category:Web Browser]]<br />
{{Related articles start}}<br />
{{Related|Wine}}<br />
{{Related|Moonlight}}<br />
{{Related|Firefox}}<br />
{{Related|AUR}}<br />
{{Related articles end}}<br />
''Pipelight is a special browser plugin which allows one to use windows only plugins inside Linux browsers. We are currently focusing on Silverlight and its features like watching DRM protected videos. The project needs a patched version of Wine to execute the Silverlight DLL.'' From [https://launchpad.net/pipelight/ here].<br />
<br />
''Pipelight allows [you] to run your favorite Silverlight application directly inside your Linux browser. The project combines the effort by Erich E. Hoover with a new browser plugin that embeds Silverlight directly in any Linux browser supporting the Netscape Plugin API. He worked on a set of Wine patches to get Playready DRM protected content working inside Wine and afterwards created an Ubuntu package called {{AUR|Netflix Desktop}}. This package allows one to use Silverlight inside a Windows version of Firefox, which works as a temporary solution but is not really user-friendly and moreover requires Wine to translate all API calls of the browser. '''To solve this problem we created Pipelight.'''<br />
<br />
''Pipelight consists out of two parts: A Linux library which is loaded into the browser and a Windows program started in Wine. The Windows program, called pluginloader.exe, simply simulates a browser and loads the Silverlight DLLs. When you open a page with a Silverlight application the library will send all commands from the browser through a pipe to the Windows process and act like a bridge between your browser and Silverlight. The used pipes do not have any big impact on the speed of the rendered video since all the video and audio data is not send through the pipe. Only the initialization parameters and (sometimes) the network traffic is send through them. As a user you will not notice anything from that "magic" and you can simply use Silverlight the same way as on Windows...'' From [http://fds-team.de/cms/articles/2013-08/pipelight-using-silverlight-in-linux-browsers.html here].<br />
<br />
==Installation==<br />
===From AUR===<br />
Install {{AUR|pipelight}} from the [[AUR]]. Consider using an [[AUR Helpers|AUR helper]] that resolves dependencies from the AUR and the [[Official Repositories]] as Pipelight requires {{AUR|wine-silverlight}} (a patched version of wine with silverlight support) which is also in AUR.<br />
<br />
====Install location====<br />
The location of wine-silverlight and wineprefix are all customizable in the PKGBUILD. Please refer to the [[Pipelight#Variables|Variables]] section below for details<br />
<br />
{{Warning|Firefox should be closed during the installation of Pipelight. Failure to do so may result in [https://answers.launchpad.net/pipelight/+faq/2357 this issue]}}<br />
<br />
===Repository===<br />
There is a repository maintained by pipelight developers, containing pipelight release and wine-compholio packages:<br />
* '''Key-ID:''' E49CC0415DC2D5CA<br />
* '''Keyfile:''' http://repos.fds-team.de/Release.key<br />
{{bc|<nowiki>[pipelight]<br />
Server = http://repos.fds-team.de/stable/arch/$arch</nowiki>}}<br />
<br />
===Silverlight initialization===<br />
Once Pipelight has completed installing, there is one more step that you need to do:<br />
<br />
# Change the user agent string of your browser as described [https://answers.launchpad.net/pipelight/+faq/2351 here]. {{Note|This is required because even though you are now capable of running Netflix, Netflix will not stream if it detects that the browser is on GNU/Linux.}}<br />
<br />
===Checking your work===<br />
You can verify that the Silverlight plugin was installed correctly even before changing the user agent by visiting [http://bubblemark.com/sl3/TestPage.html this page]. Alternatively, you can check Firefox/Chrome plugins with {{ic|about:plugins}}.<br />
<br />
===Enable GPU Acceleration===<br />
{{Note| You need {{AUR|wine-silverlight}} 1.7.0-6 and {{AUR|pipelight}} 1-12 or higher to use gpu acceleration correctly}}<br />
As for pipelight 1-12, GPU acceleration is automatically enabled on supported cards. Refer note below for debugging instructions<br />
{{Note|Instructions for enabling GPU have been simplified a lot, please refer to https://answers.launchpad.net/pipelight/+faq/2364}}<br />
You can use this page (or even just netflix) to test out 1080p streaming : http://www.iis.net/media/experiencesmoothstreaming1080p (Needs ForceGPUAcceleration set) <br />
====Blank video window after enabling gpu acceleration====<br />
If you see this issue, try setting embed = false in the pipelight config file.<br />
<br />
==Paths==<br />
{{Note| If you adjusted the the values of _prefix in the PKGBUILD, then the location of the installer will vary accordingly. If your {{AUR|wine-silverlight}} is not installed in the default location, then you need to modify the value _wine in the PKGBUILD to the actual prefix. Similarly, the package installs and looks for the actual silverlight plugin in ~/.wine-pipelight by default. However, you can change this by modifying the value of _wineprefix in the PKGBUILD.}}<br />
<br />
If you change the value of _wine in the PKGBUILD to, for example, {{ic|/opt/wine-silverlight}}, then this will be automatically propogated to the plugin installer script as well as the Pipelight configuration.<br />
<br />
{{Note|You only have to give the path to where bin/wine is.}}<br />
<br />
{{Warning|If you do not do this in the PKGBUILD, you need to edit the installer as well as the config file manually later on.}}<br />
<br />
For example, to use wine-silverlight installed in /opt/wine-silverlight/ you need to follow the following steps :<br />
# When compiling wine-silverlight uncomment the line 'customprefix=1'<br />
# When compiling pipelight set the _wine variable to /opt/wine-silverlight<br />
<br />
==Variables==<br />
The selection of variables involved in configuring Wine-Silverlight and Pipelight are explained below<br />
* '''Wine-Silverlight'''<br />
# {{ic|customprefix}}<br />
#* This is commented out by default. Uncommenting this in will install wine to {{ic|/opt/wine-silverlight}} instead of {{ic|/bin}}.<br />
#* This must be set to 1 for a custom install prefix. The default is {{ic|/usr}}.<br />
# {{ic|_prefix}}<br />
#* This controls the default custom prefix path. <br />
#* If you do not want to use {{ic|/opt/wine-silverlight}}, then ''customprefix'' must be set as explained in the previous section for your changes to work.{{Warning|Do not give the full path to the Wine binary here. Only use where {{ic|/bin}} should go. For example {{ic|/opt/wine-silverlight}} will result in the Wine executable being located at {{ic|/opt/wine-silverlight/bin/wine}}.}}<br />
* '''Pipelight'''<br />
# {{ic|_prefix}}<br />
#* Similar to Wine-Silverlight, this controls where Pipelight is installed. The default is {{ic|/usr/share/pipelight}}.<br />
# {{ic|_wine}}<br />
#* This is the location of the Wine-Silverlight executable. <br />
#* It must be same as what was used while compiling wine-silverlight.<br />
# {{ic|_wineprefix}}<br />
#* This is the location of where the Silverlight plugin used by Pipelight gets installed. The default is {{ic|~/.wine-pipelight}}.<br />
<br />
==Troubleshooting==<br />
Known issues with Pipelight and solutions are often listed [https://answers.launchpad.net/pipelight/+faqs here].<br />
<br />
==See also==<br />
* [https://answers.launchpad.net/pipelight/+faqs Launchpad FAQ]<br />
* [http://fds-team.de/cms/articles/2013-08/pipelight-using-silverlight-in-linux-browsers.html Official website]<br />
* [https://launchpad.net/pipelight/ Launchpad]</div>Hagabakahttps://wiki.archlinux.org/index.php?title=Pipelight&diff=298418Pipelight2014-02-16T20:02:24Z<p>Hagabaka: Add repository information</p>
<hr />
<div>[[Category:Web Browser]]<br />
{{Related articles start}}<br />
{{Related|Wine}}<br />
{{Related|Moonlight}}<br />
{{Related|Firefox}}<br />
{{Related|AUR}}<br />
{{Related articles end}}<br />
''Pipelight is a special browser plugin which allows one to use windows only plugins inside Linux browsers. We are currently focusing on Silverlight and its features like watching DRM protected videos. The project needs a patched version of Wine to execute the Silverlight DLL.'' From [https://launchpad.net/pipelight/ here].<br />
<br />
''Pipelight allows [you] to run your favorite Silverlight application directly inside your Linux browser. The project combines the effort by Erich E. Hoover with a new browser plugin that embeds Silverlight directly in any Linux browser supporting the Netscape Plugin API. He worked on a set of Wine patches to get Playready DRM protected content working inside Wine and afterwards created an Ubuntu package called {{AUR|Netflix Desktop}}. This package allows one to use Silverlight inside a Windows version of Firefox, which works as a temporary solution but is not really user-friendly and moreover requires Wine to translate all API calls of the browser. '''To solve this problem we created Pipelight.'''<br />
<br />
''Pipelight consists out of two parts: A Linux library which is loaded into the browser and a Windows program started in Wine. The Windows program, called pluginloader.exe, simply simulates a browser and loads the Silverlight DLLs. When you open a page with a Silverlight application the library will send all commands from the browser through a pipe to the Windows process and act like a bridge between your browser and Silverlight. The used pipes do not have any big impact on the speed of the rendered video since all the video and audio data is not send through the pipe. Only the initialization parameters and (sometimes) the network traffic is send through them. As a user you will not notice anything from that "magic" and you can simply use Silverlight the same way as on Windows...'' From [http://fds-team.de/cms/articles/2013-08/pipelight-using-silverlight-in-linux-browsers.html here].<br />
<br />
==Installation==<br />
===From AUR===<br />
Install {{AUR|pipelight}} from the [[AUR]]. Consider using an [[AUR Helpers|AUR helper]] that resolves dependencies from the AUR and the [[Official Repositories]] as Pipelight requires {{AUR|wine-silverlight}} (a patched version of wine with silverlight support) which is also in AUR.<br />
<br />
====Install location====<br />
The location of wine-silverlight and wineprefix are all customizable in the PKGBUILD. Please refer to the [[Pipelight#Variables|Variables]] section below for details<br />
<br />
{{Warning|Firefox should be closed during the installation of Pipelight. Failure to do so may result in [https://answers.launchpad.net/pipelight/+faq/2357 this issue]}}<br />
<br />
===Repository===<br />
There is a repository maintained by pipelight developers, containing pipelight release and wine-compholio packages:<br />
[pipelight]<br />
Server = http://repos.fds-team.de/stable/arch/$arch<br />
<br />
The signing key is located [http://repos.fds-team.de/Release.key here].<br />
<br />
===Silverlight initialization===<br />
Once Pipelight has completed installing, there is one more step that you need to do:<br />
<br />
# Change the user agent string of your browser as described [https://answers.launchpad.net/pipelight/+faq/2351 here]. {{Note|This is required because even though you are now capable of running Netflix, Netflix will not stream if it detects that the browser is on GNU/Linux.}}<br />
<br />
===Checking your work===<br />
You can verify that the Silverlight plugin was installed correctly even before changing the user agent by visiting [http://bubblemark.com/sl3/TestPage.html this page]. Alternatively, you can check Firefox/Chrome plugins with {{ic|about:plugins}}.<br />
<br />
===Enable GPU Acceleration===<br />
{{Note| You need {{AUR|wine-silverlight}} 1.7.0-6 and {{AUR|pipelight}} 1-12 or higher to use gpu acceleration correctly}}<br />
As for pipelight 1-12, GPU acceleration is automatically enabled on supported cards. Refer note below for debugging instructions<br />
{{Note|Instructions for enabling GPU have been simplified a lot, please refer to https://answers.launchpad.net/pipelight/+faq/2364}}<br />
You can use this page (or even just netflix) to test out 1080p streaming : http://www.iis.net/media/experiencesmoothstreaming1080p (Needs ForceGPUAcceleration set) <br />
====Blank video window after enabling gpu acceleration====<br />
If you see this issue, try setting embed = false in the pipelight config file.<br />
<br />
==Paths==<br />
{{Note| If you adjusted the the values of _prefix in the PKGBUILD, then the location of the installer will vary accordingly. If your {{AUR|wine-silverlight}} is not installed in the default location, then you need to modify the value _wine in the PKGBUILD to the actual prefix. Similarly, the package installs and looks for the actual silverlight plugin in ~/.wine-pipelight by default. However, you can change this by modifying the value of _wineprefix in the PKGBUILD.}}<br />
<br />
If you change the value of _wine in the PKGBUILD to, for example, {{ic|/opt/wine-silverlight}}, then this will be automatically propogated to the plugin installer script as well as the Pipelight configuration.<br />
<br />
{{Note|You only have to give the path to where bin/wine is.}}<br />
<br />
{{Warning|If you do not do this in the PKGBUILD, you need to edit the installer as well as the config file manually later on.}}<br />
<br />
For example, to use wine-silverlight installed in /opt/wine-silverlight/ you need to follow the following steps :<br />
# When compiling wine-silverlight uncomment the line 'customprefix=1'<br />
# When compiling pipelight set the _wine variable to /opt/wine-silverlight<br />
<br />
==Variables==<br />
The selection of variables involved in configuring Wine-Silverlight and Pipelight are explained below<br />
* '''Wine-Silverlight'''<br />
# {{ic|customprefix}}<br />
#* This is commented out by default. Uncommenting this in will install wine to {{ic|/opt/wine-silverlight}} instead of {{ic|/bin}}.<br />
#* This must be set to 1 for a custom install prefix. The default is {{ic|/usr}}.<br />
# {{ic|_prefix}}<br />
#* This controls the default custom prefix path. <br />
#* If you do not want to use {{ic|/opt/wine-silverlight}}, then ''customprefix'' must be set as explained in the previous section for your changes to work.{{Warning|Do not give the full path to the Wine binary here. Only use where {{ic|/bin}} should go. For example {{ic|/opt/wine-silverlight}} will result in the Wine executable being located at {{ic|/opt/wine-silverlight/bin/wine}}.}}<br />
* '''Pipelight'''<br />
# {{ic|_prefix}}<br />
#* Similar to Wine-Silverlight, this controls where Pipelight is installed. The default is {{ic|/usr/share/pipelight}}.<br />
# {{ic|_wine}}<br />
#* This is the location of the Wine-Silverlight executable. <br />
#* It must be same as what was used while compiling wine-silverlight.<br />
# {{ic|_wineprefix}}<br />
#* This is the location of where the Silverlight plugin used by Pipelight gets installed. The default is {{ic|~/.wine-pipelight}}.<br />
<br />
==Troubleshooting==<br />
Known issues with Pipelight and solutions are often listed [https://answers.launchpad.net/pipelight/+faqs here].<br />
<br />
==See also==<br />
* [https://answers.launchpad.net/pipelight/+faqs Launchpad FAQ]<br />
* [http://fds-team.de/cms/articles/2013-08/pipelight-using-silverlight-in-linux-browsers.html Official website]<br />
* [https://launchpad.net/pipelight/ Launchpad]</div>Hagabakahttps://wiki.archlinux.org/index.php?title=IBus&diff=179029IBus2012-01-18T20:20:08Z<p>Hagabaka: /* Kimpanel */</p>
<hr />
<div>[[Category:Internationalization (English)]]<br />
{{i18n|IBus}}<br />
[http://en.wikipedia.org/wiki/Intelligent_Input_Bus IBus] ("Intelligent Input Bus") is an [http://en.wikipedia.org/wiki/Input_method input method framework], a system for entering foreign characters. IBus functions similarly to [[SCIM]] and [[UIM]]. <br />
<br />
==Installation==<br />
# pacman -S ibus<br />
<br />
Additionally, to enable IBus for Qt applications, install the ibus-qt library:<br />
# pacman -S ibus-qt <br />
<br />
===Input Method Engines===<br />
You will need at least one input method, corresponding to the language you wish to type. Available input methods include:<br />
<br />
* ibus-anthy: A Japanese IME, based on {{Package Official|anthy}}.<br />
* ibus-pinyin: An intelligent Chinese Phonetic IME for Hanyu pinyin and Zhuyin (Bopomofo) users. Designed by IBus main author and has many advance features such as English spell checking.<br />
* ibus-chewing: An intelligent Chinese Phonetic IME for Zhuyin (Bopomofo) users, based on {{Package Official|libchewing}}.<br />
* ibus-hangul: A Korean IME, based on {{Package Official|libhangul}}.<br />
* ibus-unikey: An IME for typing Vietnamese characters.<br />
* ibus-table: An IME that accommodates table-based IMs.<br />
* ibus-m17n: A m17n IME which allows input of many languages using the input methods from m17n-db.<br />
<br />
To see all available input methods:<br />
$ pacman -Ss ^ibus-*<br />
<br />
Others packages are also available in the [[AUR]].<br />
<br />
===Initial Setup===<br />
Now, run ibus-setup (as the user who will use IBus):<br />
$ ibus-setup<br />
It will start the daemon and give you this message:<br />
IBus has been started! If you cannot use IBus, please add below lines in $HOME/.bashrc, and relogin your desktop.<br />
export GTK_IM_MODULE=ibus<br />
export XMODIFIERS=@im=ibus<br />
export QT_IM_MODULE=ibus<br />
{{Note|Although IBus uses a daemon, it is not the sort of daemon managed by the DAEMONS array in /etc/rc.conf: it runs as an ordinary user and will be started for you when you login.}}<br />
{{Note|If, however, ibus is ''not'' autostarted upon login, then move the “export …” lines above to $HOME/.xprofile instead, and append this line to the same file: “ibus-daemon -x -d”, and relogin your desktop.}}<br />
You will then see a configuration screen; you can access this screen whenever IBus is running by right-clicking the icon in the system tray and choosing "Preferences". See [[#Configuration|Configuration]].<br />
<br />
If IBus doesn't work in Qt/KDE applications, ensure that the ibus-qt library is installed and define IBus as the default IME in the Qt configuration editor:<br />
$ qtconfig<br />
In "Interface" -> "Default Input Method", select "ibus" instead of "xim".<br />
<br />
==Configuration==<br />
{{Note|You need to have [[Fonts_FAQ#Chinese.2C_Japanese.2C_Korean.2C_Vietnamese|East Asian fonts]] installed if you want to enter Chinese, Japanese, Korean or Vietnamese characters.}}<br />
The default "General" settings should be fine, but go to "Input Methods" and select your input method(s) in the drop down box, then press "Add". You can use multiple input methods if you wish.<br />
Once IBus is set up, you can press Ctrl+Space to use it (multiple times to cycle through available input methods). IBus will remember which input method you are using in each window, so you will have to reactivate it for each new window. You can override this behavior by right clicking the system tray icon, selecting "Preferences", and going to the "Advanced" tab.<br />
<br />
==Tips and tricks==<br />
===Pinyin usage===<br />
When using ibus-pinyin,<br />
* First type the pinyin (sans tones) for the characters you wish to enter.<br />
* Press Up and Down repeatedly to select a character (going on to the next page if necessary).<br />
* Press Space to use a character.<br />
* You can also use PageUp or PageDown to scroll pages, and use the number keys 1-5 to select the character you need.<br />
* You can enter multiple characters that form a word or phrase at a time (such as "zhongwen" to enter "中文"). ibus-pinyin will remember which characters you type most frequently and over time make suggestions that are more tuned to your typing profile.<br />
<br />
==Troubleshooting==<br />
<br />
===Kimpanel===<br />
IBus main interface is currently only available in GTK, but {{Package Official|Kimpanel}} provides a native Qt/KDE input interface. Since kdeplasma-addons-applets-kimpanel version 4.7.95-3, the package is compiled to support ibus. However, ibus needs to be launched as following to be able to communicate with the panel:<br />
<br />
$ ibus-daemon --xim --panel=/usr/lib/kde4/libexec/kimpanel-ibus-panel<br />
<br />
To get a menu entry for launching ibus this way, save the following file to ~/.local/share/applications/ibus-kimpanel.desktop<br />
[Desktop Entry]<br />
Encoding=UTF-8<br />
Name=IBus (KIMPanel)<br />
Name[ar]=IBus (KIMPanel)<br />
Name[as]=IBus (KIMPanel)<br />
Name[bn_IN]=IBus (KIMPanel)<br />
Name[ca]=IBus (KIMPanel)<br />
Name[da]=IBus (KIMPanel)<br />
Name[de]=IBus (KIMPanel)<br />
Name[en_GB]=IBus (KIMPanel)<br />
Name[es]=IBus (KIMPanel)<br />
Name[fr]=IBus (KIMPanel)<br />
Name[gu]=IBus (KIMPanel)<br />
Name[hi]=IBus (KIMPanel)<br />
Name[hu]=IBus (KIMPanel)<br />
Name[it]=IBus (KIMPanel)<br />
Name[ja]=IBus (KIMPanel)<br />
Name[kn]=IBus (KIMPanel)<br />
Name[ko]=IBus (KIMPanel)<br />
Name[ml]=IBus (KIMPanel)<br />
Name[mr]=IBus (KIMPanel)<br />
Name[nl]=IBus (KIMPanel)<br />
Name[or]=IBus (KIMPanel)<br />
Name[pa]=IBus (KIMPanel)<br />
Name[pl]=iBus (KIMPanel)<br />
Name[pt_BR]=IBus (KIMPanel)<br />
Name[ru]=IBus (KIMPanel)<br />
Name[sr]=IBus (KIMPanel)<br />
Name[sr@latin]=IBus (KIMPanel)<br />
Name[ta]=IBus (KIMPanel)<br />
Name[te]=IBus (KIMPanel)<br />
Name[uk]=IBus (KIMPanel)<br />
Name[vi]=IBus (KIMPanel)<br />
Name[zh_CN]=IBus (KIMPanel)<br />
Name[zh_HK]=IBus (KIMPanel)<br />
Name[zh_TW]=IBus (KIMPanel)<br />
GenericName=Input Method Framework<br />
GenericName[as]=ইনপুট পদ্ধতি গাথনি<br />
GenericName[bn_IN]=ইনপুট পদ্ধতির পরিকাঠামো<br />
GenericName[da]=Framework for inputmetode<br />
GenericName[de]=Eingabemethode-Framework<br />
GenericName[en_GB]=Input Method Framework<br />
GenericName[es]=Marco de trabajo para métodos de entrada<br />
GenericName[fr]=Framework de méthode de saisie<br />
GenericName[gu]=ઇનપુટ પદ્દતિ ફ્રેમવર્ક<br />
GenericName[hi]=IBus विधि फ्रेमवर्क<br />
GenericName[it]=Framework del metodo di input<br />
GenericName[ja]=インプットメソッドフレームワーク<br />
GenericName[kn]=IBus ವಿಧಾನದ ಫ್ರೇಮ್ವರ್ಕ್<br />
GenericName[ko]=입력 방식 프레임워크<br />
GenericName[ml]=ഇന്പുട്ട് മെഥേഡ് ആകൃതി<br />
GenericName[mr]=इन्पुट पद्धत फ्रेमवर्क<br />
GenericName[nl]=Invoer methode kader<br />
GenericName[or]=ନିବେଶ ପ୍ରଣାଳୀ ଫ୍ରେମୱର୍କ<br />
GenericName[pa]=ਇੰਪੁੱਟ ਢੰਗ ਫਰੇਮਵਰਕ<br />
GenericName[pl]=Struktura metody wprowadzania<br />
GenericName[pt_BR]=Framework do método de entrada<br />
GenericName[ru]=Система методов ввода<br />
GenericName[ta]=உள்ளீடு முறை ஃபிரேம்வொர்க்<br />
GenericName[te]=ఇన్పుట్ పద్ధతి ఫ్రేమ్వర్క్<br />
GenericName[uk]=Оболонка способів введення<br />
GenericName[zh_CN]=输入法框架<br />
GenericName[zh_TW]=輸入法框架<br />
Comment=Start IBus Input Method Framework<br />
Comment[as]=IBus ইনপুট পদ্ধতি গাথনি আৰম্ভ কৰা<br />
Comment[bn_IN]=IBus ইনপুট পদ্ধতির পরিকাঠামো আরম্ভ করা হবে<br />
Comment[da]=Start IBus, framework for inputmetode<br />
Comment[de]=IBus-Eingabemethode-Framework starten<br />
Comment[en_GB]=Start IBus Input Method Framework<br />
Comment[es]=Inicie el marco de trabajo para métodos de entrada IBus<br />
Comment[fr]=Démarrer le framework de méthode de saisie IBus<br />
Comment[gu]=IBus ઇનપુટ પદ્દતિ ફ્રેમવર્કને શરૂ કરો<br />
Comment[hi]=IBus इनपुट विधि फ्रेमवर्क आरंभ करें<br />
Comment[it]=Avvia il framework del metodo di input di IBus<br />
Comment[ja]=IBus インプットメソッドフレームワークを起動<br />
Comment[kn]=IBus ಇನ್ಪುಟ್ ವಿಧಾನದ ಫ್ರೇಮ್ವರ್ಕ್ ಅನ್ನು ಆರಂಭಿಸು<br />
Comment[ko]=IBus 입력 방식 프레임워크 시작<br />
Comment[ml]=IBus ഇന്പുട്ട് മെഥേഡ് ആകൃതി ആരംഭിയ്ക്കുക<br />
Comment[mr]=IBus इन्पुट पद्धती फ्रेमवर्क सुरू करा<br />
Comment[nl]=Start IBus invoer methode kader<br />
Comment[or]=IBus ନିବେଶ ପ୍ରଣାଳୀ ଫ୍ରେମୱର୍କକୁ ଆରମ୍ଭ କରନ୍ତୁ<br />
Comment[pa]=ਆਈਬਸ ਇੰਪੁੱਟ ਢੰਗ ਫਰੇਮਵਰਕ ਸ਼ੁਰੂ ਕਰੋ<br />
Comment[pl]=Uruchomienie struktury metody wprowadzania iBus<br />
Comment[pt_BR]=Iniciar Framework do método de entrada IBus<br />
Comment[ru]=Запустить систему методов ввода IBus<br />
Comment[ta]=IBus உள்ளீடு முறை ஃபிரேம்வொர்க்கை துவக்கு<br />
Comment[te]=IBus ఇన్పుట్ పద్ధతి ఫ్రేమ్వర్కును ప్రారంభించుము<br />
Comment[uk]=Запуск оболонки способів введення IBus<br />
Comment[zh_CN]=启动IBus 输入法框架<br />
Comment[zh_TW]=啟動 IBus 輸入法框架<br />
Exec=ibus-daemon --xim --panel=/usr/lib/kde4/libexec/kimpanel-ibus-panel<br />
Icon=ibus<br />
Terminal=false<br />
Type=Application<br />
Categories=System;Utility;<br />
X-GNOME-Autostart-Phase=Applications<br />
X-GNOME-AutoRestart=false<br />
X-GNOME-Autostart-Notify=true<br />
X-KDE-autostart-after=panel<br />
<br />
Then you can either let KDE autostart ibus, or set it as the input method application in Kimpanel, and manually click on the kimpanel icon to start it. In either case, choose Utility/Ibus (Kimpanel) in the Choose Application dialog.<br />
<br />
===rxvt-unicode===<br />
If anyone has any issues with iBus and rxvt-unicode, the following steps should solve it.<br />
<br />
Add the following to your .Xdefaults (possibly not required -- try first without):<br />
URxvt.inputMethod: ibus<br />
URxvt.preeditType: OnTheSpot,None<br />
<br />
And start ibus with:<br />
ibus-daemon --xim<br />
<br />
If you start ibus-daemon automatically (e.g. in ~/.xinitrc or ~/.xsession) but used to use `ibus-daemon &' without the `--xim' option, make sure to kill the existing process before testing the new command.<br />
<br />
===GTK applications===<br />
Some users have had problems using Input Methods with GTK applications, because it seems that the gtk.immodules file can't be found. Adding <br />
export GTK_IM_MODULE_FILE=/etc/gtk-2.0/gtk.immodules<br />
<br />
(currently changed to)<br />
export GTK_IM_MODULE_FILE=/etc/gtk-3.0/gtk.immodules<br />
in addition to the three lines above in your $HOME/.bashrc seems to fix the problem.<br />
<br />
===Chinese Input===<br />
If you encounter problems when using chinese input, check your locale settting. For example in Hong Kong, export LANG=zh_HK.utf8.<br />
<br />
{{Note| There are large revisions after ibus1.4, you might not be able to input chinese words with ibus-pinyin or ibus-sunpinyin, which are written in C. So the solution is:<br />
<br />
* Recompile ibus-sunpinyin in ABS by yourself. or<br />
* Install ibus-googlepinyin, which is developed in python. <br />
}}<br />
You can install {{AUR|ibus-googlepinyin}} from the [[AUR]].<br />
<br />
To start ibus with gnome, add this in ~/.profile and restart the gnome.<br />
<br />
export GTK_IM_MODULE=ibus<br />
export XMODIFIERS=@im=ibus<br />
export QT_IM_MODULE=ibus<br />
ibus-daemon -d -x<br />
<br />
Chinese users can refer to this [http://forum.ubuntu.org.cn/viewtopic.php?f=155&t=346639 page] for detailed solution concerning this bug.<br />
<br />
===LibreOffice===<br />
LibreOffice (and OpenOffice) ship with an old libc version which causes ibus to fail to load. To fix this, remove the shipped libstdc++.so.6 at "/usr/lib/libreoffice/basis-link/ure-link/lib/libstdc++.so.6".<br />
<br />
If IBus does load but doesn't see LibreOffice as an input window, put "export OOO_FORCE_DESKTOP="gnome"" in your $HOME/.xprofile, even if you are using KDE. This is due to a bug with new KDE integration code.</div>Hagabakahttps://wiki.archlinux.org/index.php?title=IBus&diff=179028IBus2012-01-18T20:19:32Z<p>Hagabaka: update instructions since kimpanel now includes ibus backend</p>
<hr />
<div>[[Category:Internationalization (English)]]<br />
{{i18n|IBus}}<br />
[http://en.wikipedia.org/wiki/Intelligent_Input_Bus IBus] ("Intelligent Input Bus") is an [http://en.wikipedia.org/wiki/Input_method input method framework], a system for entering foreign characters. IBus functions similarly to [[SCIM]] and [[UIM]]. <br />
<br />
==Installation==<br />
# pacman -S ibus<br />
<br />
Additionally, to enable IBus for Qt applications, install the ibus-qt library:<br />
# pacman -S ibus-qt <br />
<br />
===Input Method Engines===<br />
You will need at least one input method, corresponding to the language you wish to type. Available input methods include:<br />
<br />
* ibus-anthy: A Japanese IME, based on {{Package Official|anthy}}.<br />
* ibus-pinyin: An intelligent Chinese Phonetic IME for Hanyu pinyin and Zhuyin (Bopomofo) users. Designed by IBus main author and has many advance features such as English spell checking.<br />
* ibus-chewing: An intelligent Chinese Phonetic IME for Zhuyin (Bopomofo) users, based on {{Package Official|libchewing}}.<br />
* ibus-hangul: A Korean IME, based on {{Package Official|libhangul}}.<br />
* ibus-unikey: An IME for typing Vietnamese characters.<br />
* ibus-table: An IME that accommodates table-based IMs.<br />
* ibus-m17n: A m17n IME which allows input of many languages using the input methods from m17n-db.<br />
<br />
To see all available input methods:<br />
$ pacman -Ss ^ibus-*<br />
<br />
Others packages are also available in the [[AUR]].<br />
<br />
===Initial Setup===<br />
Now, run ibus-setup (as the user who will use IBus):<br />
$ ibus-setup<br />
It will start the daemon and give you this message:<br />
IBus has been started! If you cannot use IBus, please add below lines in $HOME/.bashrc, and relogin your desktop.<br />
export GTK_IM_MODULE=ibus<br />
export XMODIFIERS=@im=ibus<br />
export QT_IM_MODULE=ibus<br />
{{Note|Although IBus uses a daemon, it is not the sort of daemon managed by the DAEMONS array in /etc/rc.conf: it runs as an ordinary user and will be started for you when you login.}}<br />
{{Note|If, however, ibus is ''not'' autostarted upon login, then move the “export …” lines above to $HOME/.xprofile instead, and append this line to the same file: “ibus-daemon -x -d”, and relogin your desktop.}}<br />
You will then see a configuration screen; you can access this screen whenever IBus is running by right-clicking the icon in the system tray and choosing "Preferences". See [[#Configuration|Configuration]].<br />
<br />
If IBus doesn't work in Qt/KDE applications, ensure that the ibus-qt library is installed and define IBus as the default IME in the Qt configuration editor:<br />
$ qtconfig<br />
In "Interface" -> "Default Input Method", select "ibus" instead of "xim".<br />
<br />
==Configuration==<br />
{{Note|You need to have [[Fonts_FAQ#Chinese.2C_Japanese.2C_Korean.2C_Vietnamese|East Asian fonts]] installed if you want to enter Chinese, Japanese, Korean or Vietnamese characters.}}<br />
The default "General" settings should be fine, but go to "Input Methods" and select your input method(s) in the drop down box, then press "Add". You can use multiple input methods if you wish.<br />
Once IBus is set up, you can press Ctrl+Space to use it (multiple times to cycle through available input methods). IBus will remember which input method you are using in each window, so you will have to reactivate it for each new window. You can override this behavior by right clicking the system tray icon, selecting "Preferences", and going to the "Advanced" tab.<br />
<br />
==Tips and tricks==<br />
===Pinyin usage===<br />
When using ibus-pinyin,<br />
* First type the pinyin (sans tones) for the characters you wish to enter.<br />
* Press Up and Down repeatedly to select a character (going on to the next page if necessary).<br />
* Press Space to use a character.<br />
* You can also use PageUp or PageDown to scroll pages, and use the number keys 1-5 to select the character you need.<br />
* You can enter multiple characters that form a word or phrase at a time (such as "zhongwen" to enter "中文"). ibus-pinyin will remember which characters you type most frequently and over time make suggestions that are more tuned to your typing profile.<br />
<br />
==Troubleshooting==<br />
<br />
===Kimpanel===<br />
IBus main interface is currently only available in GTK, but {{Package Official|Kimpanel}} provides a native Qt/KDE input interface. Since kdeplasma-addons-applets-kimpanel version 4.7.95-3, the package is compiled to support ibus. In addition, ibus needs to be launched as following to be able to communicate with the panel:<br />
<br />
$ ibus-daemon --xim --panel=/usr/lib/kde4/libexec/kimpanel-ibus-panel<br />
<br />
To get a menu entry for launching ibus this way, save the following file to ~/.local/share/applications/ibus-kimpanel.desktop<br />
[Desktop Entry]<br />
Encoding=UTF-8<br />
Name=IBus (KIMPanel)<br />
Name[ar]=IBus (KIMPanel)<br />
Name[as]=IBus (KIMPanel)<br />
Name[bn_IN]=IBus (KIMPanel)<br />
Name[ca]=IBus (KIMPanel)<br />
Name[da]=IBus (KIMPanel)<br />
Name[de]=IBus (KIMPanel)<br />
Name[en_GB]=IBus (KIMPanel)<br />
Name[es]=IBus (KIMPanel)<br />
Name[fr]=IBus (KIMPanel)<br />
Name[gu]=IBus (KIMPanel)<br />
Name[hi]=IBus (KIMPanel)<br />
Name[hu]=IBus (KIMPanel)<br />
Name[it]=IBus (KIMPanel)<br />
Name[ja]=IBus (KIMPanel)<br />
Name[kn]=IBus (KIMPanel)<br />
Name[ko]=IBus (KIMPanel)<br />
Name[ml]=IBus (KIMPanel)<br />
Name[mr]=IBus (KIMPanel)<br />
Name[nl]=IBus (KIMPanel)<br />
Name[or]=IBus (KIMPanel)<br />
Name[pa]=IBus (KIMPanel)<br />
Name[pl]=iBus (KIMPanel)<br />
Name[pt_BR]=IBus (KIMPanel)<br />
Name[ru]=IBus (KIMPanel)<br />
Name[sr]=IBus (KIMPanel)<br />
Name[sr@latin]=IBus (KIMPanel)<br />
Name[ta]=IBus (KIMPanel)<br />
Name[te]=IBus (KIMPanel)<br />
Name[uk]=IBus (KIMPanel)<br />
Name[vi]=IBus (KIMPanel)<br />
Name[zh_CN]=IBus (KIMPanel)<br />
Name[zh_HK]=IBus (KIMPanel)<br />
Name[zh_TW]=IBus (KIMPanel)<br />
GenericName=Input Method Framework<br />
GenericName[as]=ইনপুট পদ্ধতি গাথনি<br />
GenericName[bn_IN]=ইনপুট পদ্ধতির পরিকাঠামো<br />
GenericName[da]=Framework for inputmetode<br />
GenericName[de]=Eingabemethode-Framework<br />
GenericName[en_GB]=Input Method Framework<br />
GenericName[es]=Marco de trabajo para métodos de entrada<br />
GenericName[fr]=Framework de méthode de saisie<br />
GenericName[gu]=ઇનપુટ પદ્દતિ ફ્રેમવર્ક<br />
GenericName[hi]=IBus विधि फ्रेमवर्क<br />
GenericName[it]=Framework del metodo di input<br />
GenericName[ja]=インプットメソッドフレームワーク<br />
GenericName[kn]=IBus ವಿಧಾನದ ಫ್ರೇಮ್ವರ್ಕ್<br />
GenericName[ko]=입력 방식 프레임워크<br />
GenericName[ml]=ഇന്പുട്ട് മെഥേഡ് ആകൃതി<br />
GenericName[mr]=इन्पुट पद्धत फ्रेमवर्क<br />
GenericName[nl]=Invoer methode kader<br />
GenericName[or]=ନିବେଶ ପ୍ରଣାଳୀ ଫ୍ରେମୱର୍କ<br />
GenericName[pa]=ਇੰਪੁੱਟ ਢੰਗ ਫਰੇਮਵਰਕ<br />
GenericName[pl]=Struktura metody wprowadzania<br />
GenericName[pt_BR]=Framework do método de entrada<br />
GenericName[ru]=Система методов ввода<br />
GenericName[ta]=உள்ளீடு முறை ஃபிரேம்வொர்க்<br />
GenericName[te]=ఇన్పుట్ పద్ధతి ఫ్రేమ్వర్క్<br />
GenericName[uk]=Оболонка способів введення<br />
GenericName[zh_CN]=输入法框架<br />
GenericName[zh_TW]=輸入法框架<br />
Comment=Start IBus Input Method Framework<br />
Comment[as]=IBus ইনপুট পদ্ধতি গাথনি আৰম্ভ কৰা<br />
Comment[bn_IN]=IBus ইনপুট পদ্ধতির পরিকাঠামো আরম্ভ করা হবে<br />
Comment[da]=Start IBus, framework for inputmetode<br />
Comment[de]=IBus-Eingabemethode-Framework starten<br />
Comment[en_GB]=Start IBus Input Method Framework<br />
Comment[es]=Inicie el marco de trabajo para métodos de entrada IBus<br />
Comment[fr]=Démarrer le framework de méthode de saisie IBus<br />
Comment[gu]=IBus ઇનપુટ પદ્દતિ ફ્રેમવર્કને શરૂ કરો<br />
Comment[hi]=IBus इनपुट विधि फ्रेमवर्क आरंभ करें<br />
Comment[it]=Avvia il framework del metodo di input di IBus<br />
Comment[ja]=IBus インプットメソッドフレームワークを起動<br />
Comment[kn]=IBus ಇನ್ಪುಟ್ ವಿಧಾನದ ಫ್ರೇಮ್ವರ್ಕ್ ಅನ್ನು ಆರಂಭಿಸು<br />
Comment[ko]=IBus 입력 방식 프레임워크 시작<br />
Comment[ml]=IBus ഇന്പുട്ട് മെഥേഡ് ആകൃതി ആരംഭിയ്ക്കുക<br />
Comment[mr]=IBus इन्पुट पद्धती फ्रेमवर्क सुरू करा<br />
Comment[nl]=Start IBus invoer methode kader<br />
Comment[or]=IBus ନିବେଶ ପ୍ରଣାଳୀ ଫ୍ରେମୱର୍କକୁ ଆରମ୍ଭ କରନ୍ତୁ<br />
Comment[pa]=ਆਈਬਸ ਇੰਪੁੱਟ ਢੰਗ ਫਰੇਮਵਰਕ ਸ਼ੁਰੂ ਕਰੋ<br />
Comment[pl]=Uruchomienie struktury metody wprowadzania iBus<br />
Comment[pt_BR]=Iniciar Framework do método de entrada IBus<br />
Comment[ru]=Запустить систему методов ввода IBus<br />
Comment[ta]=IBus உள்ளீடு முறை ஃபிரேம்வொர்க்கை துவக்கு<br />
Comment[te]=IBus ఇన్పుట్ పద్ధతి ఫ్రేమ్వర్కును ప్రారంభించుము<br />
Comment[uk]=Запуск оболонки способів введення IBus<br />
Comment[zh_CN]=启动IBus 输入法框架<br />
Comment[zh_TW]=啟動 IBus 輸入法框架<br />
Exec=ibus-daemon --xim --panel=/usr/lib/kde4/libexec/kimpanel-ibus-panel<br />
Icon=ibus<br />
Terminal=false<br />
Type=Application<br />
Categories=System;Utility;<br />
X-GNOME-Autostart-Phase=Applications<br />
X-GNOME-AutoRestart=false<br />
X-GNOME-Autostart-Notify=true<br />
X-KDE-autostart-after=panel<br />
<br />
Then you can either let KDE autostart ibus, or set it as the input method application in Kimpanel, and manually click on the kimpanel icon to start it. In either case, choose Utility/Ibus (Kimpanel) in the Choose Application dialog.<br />
<br />
===rxvt-unicode===<br />
If anyone has any issues with iBus and rxvt-unicode, the following steps should solve it.<br />
<br />
Add the following to your .Xdefaults (possibly not required -- try first without):<br />
URxvt.inputMethod: ibus<br />
URxvt.preeditType: OnTheSpot,None<br />
<br />
And start ibus with:<br />
ibus-daemon --xim<br />
<br />
If you start ibus-daemon automatically (e.g. in ~/.xinitrc or ~/.xsession) but used to use `ibus-daemon &' without the `--xim' option, make sure to kill the existing process before testing the new command.<br />
<br />
===GTK applications===<br />
Some users have had problems using Input Methods with GTK applications, because it seems that the gtk.immodules file can't be found. Adding <br />
export GTK_IM_MODULE_FILE=/etc/gtk-2.0/gtk.immodules<br />
<br />
(currently changed to)<br />
export GTK_IM_MODULE_FILE=/etc/gtk-3.0/gtk.immodules<br />
in addition to the three lines above in your $HOME/.bashrc seems to fix the problem.<br />
<br />
===Chinese Input===<br />
If you encounter problems when using chinese input, check your locale settting. For example in Hong Kong, export LANG=zh_HK.utf8.<br />
<br />
{{Note| There are large revisions after ibus1.4, you might not be able to input chinese words with ibus-pinyin or ibus-sunpinyin, which are written in C. So the solution is:<br />
<br />
* Recompile ibus-sunpinyin in ABS by yourself. or<br />
* Install ibus-googlepinyin, which is developed in python. <br />
}}<br />
You can install {{AUR|ibus-googlepinyin}} from the [[AUR]].<br />
<br />
To start ibus with gnome, add this in ~/.profile and restart the gnome.<br />
<br />
export GTK_IM_MODULE=ibus<br />
export XMODIFIERS=@im=ibus<br />
export QT_IM_MODULE=ibus<br />
ibus-daemon -d -x<br />
<br />
Chinese users can refer to this [http://forum.ubuntu.org.cn/viewtopic.php?f=155&t=346639 page] for detailed solution concerning this bug.<br />
<br />
===LibreOffice===<br />
LibreOffice (and OpenOffice) ship with an old libc version which causes ibus to fail to load. To fix this, remove the shipped libstdc++.so.6 at "/usr/lib/libreoffice/basis-link/ure-link/lib/libstdc++.so.6".<br />
<br />
If IBus does load but doesn't see LibreOffice as an input window, put "export OOO_FORCE_DESKTOP="gnome"" in your $HOME/.xprofile, even if you are using KDE. This is due to a bug with new KDE integration code.</div>Hagabaka