https://wiki.archlinux.org/api.php?action=feedcontributions&user=Sirrus233&feedformat=atomArchWiki - User contributions [en]2024-03-29T05:04:30ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=GNOME/Keyring&diff=755763GNOME/Keyring2022-11-03T08:40:48Z<p>Sirrus233: Issue with not providing the ssh agent service patched https://bugs.archlinux.org/task/76374</p>
<hr />
<div>[[Category:GNOME]]<br />
[[es:GNOME (Español)/Keyring]]<br />
[[ja:GNOME Keyring]]<br />
[[zh-hans:GNOME (简体中文)/Keyring]]<br />
[https://wiki.gnome.org/Projects/GnomeKeyring GNOME Keyring] is "a collection of components in GNOME that store secrets, passwords, keys, certificates and make them available to applications."<br />
<br />
== Installation ==<br />
<br />
{{Pkg|gnome-keyring}} is a member of the {{Grp|gnome}} group is thus usually present on systems running GNOME. The package can otherwise be [[install]]ed on its own. {{Pkg|libsecret}} should also be installed to grant other applications access to your keyrings. Although {{Pkg|libgnome-keyring}} is deprecated (and superseded by ''libsecret''), it may still be required by certain applications.<br />
<br />
The gnome-keyring-daemon is automatically started via a systemd user service upon logging in. It can also be started upon request via a socket.<br />
<br />
Extra utilities related to GNOME Keyring include:<br />
<br />
* {{App|secret-tool|Access the GNOME Keyring (and any other service implementing the [https://specifications.freedesktop.org/secret-service/ DBus Secret Service API]) from the command line.|https://wiki.gnome.org/Projects/Libsecret|{{Pkg|libsecret}}}}<br />
* {{App|lssecret|List all secret items using ''libsecret'' (e.g. GNOME Keyring).|https://gitlab.com/GrantMoyer/lssecret|{{AUR|lssecret-git}}}}<br />
* {{App|gnome-keyring-query|Provides a simple command-line tool for querying passwords from the password store of the GNOME Keyring.|[https://web.archive.org/web/20160326164641/https://gentoo-wiki.info/HOWTO_Use_gnome-keyring_to_store_SSH_passphrases https://gentoo-wiki.info/HOWTO_Use_gnome-keyring_to_store_SSH_passphrases] (archived)|{{AUR|gnome-keyring-query}}}}<br />
<br />
{{Note|''gnome-keyring-query'' only requires ''libgnome-keyring'' as a build dependency.}}<br />
<br />
== Manage using GUI ==<br />
<br />
You can manage the contents of GNOME Keyring using Seahorse; [[install]] the {{Pkg|seahorse}} package.<br />
<br />
Passwords for keyrings (e.g., the default keyring, "Login") can be changed and even removed. See [https://help.gnome.org/users/seahorse/stable/keyring-create.html Create a new keyring] and [https://help.gnome.org/users/seahorse/stable/keyring-update-password.html Update the keyring password] in GNOME Help for more information.<br />
<br />
== Using the keyring ==<br />
<br />
The [[PAM]] module ''pam_gnome_keyring.so'' initialises GNOME Keyring partially, unlocking the default ''login'' keyring in the process. The gnome-keyring-daemon is automatically started with a systemd user service.<br />
<br />
=== PAM step ===<br />
<br />
{{Note|To use automatic unlocking '''without automatic login''', the password for the user account should be the same as the default keyring. See [[#Automatically change keyring password with user password]].}}<br />
{{Tip|<br />
* To use automatic unlocking with automatic login, you can set a blank password for the default keyring. Note that the contents of the keyring are stored unencrypted in this case.<br />
* Alternatively, if using GDM and LUKS, GDM can unlock your keyring if it matches your LUKS password. For this to work, you need to use the [[Mkinitcpio#Common hooks|systemd init in your mkinitcpio.conf]] as well as the [[Dm-crypt/System configuration#Using sd-encrypt hook|appropriate kernel parameters]]{{Broken section link}}. See [https://reddit.com/r/Fedora/comments/jwnqq5/] for more details.<br />
* Skipping the PAM step works, because the [[#--start step|next step]]{{Broken section link}} will initialise the daemon when one is not running already; however, the default keyring is not unlocked in this case. More details are available at [https://wiki.gnome.org/Projects/GnomeKeyring/RunningDaemon].<br />
}}<br />
<br />
When using a display manager, the keyring works out of the box for most cases. [[GDM]], [[LightDM]], [[LXDM]], and [[SDDM]] already have the necessary PAM configuration. For a display manager that does not automatically unlock the keyring edit the appropriate file instead of {{ic|/etc/pam.d/login}} as mentioned below.<br />
<br />
When using console-based login, edit {{ic|/etc/pam.d/login}}:<br />
<br />
Add {{ic|auth optional pam_gnome_keyring.so}} at the end of the {{ic|auth}} section and {{ic|session optional pam_gnome_keyring.so auto_start}} at the end of the {{ic|session}} section.<br />
<br />
{{hc|/etc/pam.d/login|<br />
#%PAM-1.0<br />
<br />
auth required pam_securetty.so<br />
auth requisite pam_nologin.so<br />
auth include system-local-login<br />
'''auth optional pam_gnome_keyring.so'''<br />
account include system-local-login<br />
session include system-local-login<br />
'''session optional pam_gnome_keyring.so auto_start'''<br />
}}<br />
<br />
== SSH keys ==<br />
<br />
'''gnome-keyring-daemon''' with the '''ssh''' component will start an SSH agent and automatically load all the keys in {{ic|~/.ssh/}} that have corresponding ''.pub'' files. There is no way to remove these keys from the agent.<br />
<br />
To list all loaded keys:<br />
<br />
$ ssh-add -L<br />
<br />
When you connect to a server that uses a loaded key with a password, a dialog will popup asking you for the passphrase. It has an option to automatically unlock the key when you log in. If you check this, you will not need to enter your passphrase again!<br />
<br />
To permanently save the a passphrase in the keyring, use ssh-askpass from the {{pkg|seahorse}} package:<br />
<br />
$ /usr/lib/seahorse/ssh-askpass my_key<br />
<br />
To manually add an SSH key from another directory:<br />
<br />
$ ssh-add ~/.private/id_rsa<br />
Enter passphrase for ~/.private/id_rsa:<br />
<br />
{{Note|You have to have the corresponding ''.pub'' file in the same directory as the private key ({{ic|~/.ssh/id_rsa.pub}} in the example). Also, make sure that the public key is the file name of the private key plus ''.pub'' (for example, {{ic|my_key.pub}}).}}<br />
<br />
To disable all manually added keys:<br />
<br />
$ ssh-add -D<br />
<br />
=== Enable the keyring ssh component ===<br />
<br />
The default systemd user service shipped with the keyring does not include the '''ssh''' component. '''ssh''' must be added to the {{ic|--components}} option of the {{ic|gnome-keyring-daemon}} command in the {{ic|ExecStart}} line of the unit file.<br />
<br />
See [[Systemd#Editing provided units]] for how to edit the keyring's systemd unit file.<br />
<br />
You must also [[enable]] the {{ic|gcr-ssh-agent.service}} [[user unit]] and point an environment variable to the auth socket. {{ic|1=export SSH_AUTH_SOCK=/run/user/$(id -u)/gcr/ssh}}<br />
<br />
=== Disable keyring daemon components ===<br />
<br />
If you wish to run an alternative SSH agent (e.g. [[SSH keys#ssh-agent|ssh-agent]] or [[GnuPG#gpg-agent|gpg-agent]]), you need to disable the {{ic|ssh}} component of GNOME Keyring. To do so in an account-local way, copy {{ic|/etc/xdg/autostart/gnome-keyring-ssh.desktop}} to {{ic|~/.config/autostart/}} and then append the line {{ic|1=Hidden=true}} to the copied file. Then log out.<br />
<br />
== Tips and tricks ==<br />
<br />
=== Integration with applications ===<br />
<br />
* [[Chromium#Force a password store|Chromium]]<br />
<br />
=== Flushing passphrases ===<br />
<br />
$ gnome-keyring-daemon -r -d<br />
<br />
This command starts gnome-keyring-daemon, shutting down previously running instances.<br />
<br />
=== Git integration ===<br />
<br />
The GNOME keyring is useful in conjunction with [[Git]] when you are pushing over HTTPS. The {{Pkg|libsecret}} package [[#Installation|needs to be installed for this functionality to be available]].<br />
<br />
Configure Git to use the ''libsecret'' helper:<br />
<br />
$ git config --global credential.helper /usr/lib/git-core/git-credential-libsecret<br />
<br />
The next time you run {{ic|git push}}, you will be asked to unlock your keyring if it is not already unlocked.<br />
<br />
=== GnuPG integration ===<br />
<br />
Several applications which use GnuPG require a {{ic|pinentry-program}} to be set. Set the following to use GNOME 3 pinentry for GNOME Keyring to manage passphrase prompts.<br />
<br />
{{hc|~/.gnupg/gpg-agent.conf|<br />
pinentry-program /usr/bin/pinentry-gnome3<br />
}}<br />
<br />
Another option is to [[GnuPG#Unattended passphrase|force loopback for GPG]] which should allow the passphrase to be entered in the application.<br />
<br />
=== Renaming a keyring ===<br />
<br />
The display name for a keyring (i.e., the name that appears in Seahorse and from {{ic|file}}) can be changed by [https://ttboj.wordpress.com/2013/01/27/renaming-a-gnome-keyring-for-seahorse-the-passwords-and-keyrings-application/ changing the value of display-name in the unencrypted keyring file]. Keyrings will usually be stored in {{ic|~/.local/share/keyrings/}} with the ''.keyring'' file extension.<br />
<br />
=== Automatically change keyring password with user password ===<br />
<br />
{{Note|This only affects the default keyring.}}<br />
<br />
Add {{ic|password optional pam_gnome_keyring.so}} to the end of {{ic|/etc/pam.d/passwd}}.<br />
{{hc|/etc/pam.d/passwd|2=<br />
#%PAM-1.0<br />
<br />
#password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3<br />
#password required pam_unix.so sha512 shadow use_authtok<br />
password required pam_unix.so sha512 shadow nullok<br />
'''password optional pam_gnome_keyring.so'''<br />
}}<br />
<br />
=== Launching gnome-keyring-daemon outside desktop environments (KDE, GNOME, XFCE, ...) ===<br />
<br />
{{Accuracy|At least [[xinit]] and [[SDDM]] execute all scripts from {{ic|/etc/X11/xinit/xinitrc.d/}} and [[sway]] provides {{ic|/etc/sway/config.d/50-systemd-user.conf}} so the problem is not being "outside desktop environments". If gnome-keyring requires [[XDG Autostart]], the installation/configuration section should say so.}}<br />
<br />
If you are using sway, i3, or any window manager that does not execute<br />
<br />
* {{ic|/etc/xdg/autostart/gnome-keyring-*.desktop}}<br />
* {{ic|/etc/X11/xinit/xinitrc.d/50-systemd-user.sh}}<br />
<br />
your window manager needs to execute the following commands during window manager startup. The commands do not need to be executed in any specific order.<br />
<br />
{{bc|dbus-update-activation-environment DISPLAY XAUTHORITY WAYLAND_DISPLAY}}<br />
or<br />
{{bc|dbus-update-activation-environment --all}}<br />
<br />
This command passes environment variables from the window manager to session dbus. Without this, GUI prompts cannot be triggered over DBus. For example, this is required for seahorse password prompt.<br />
<br />
This is required because session dbus is started before graphical environment is started. Thus, session dbus does not know about the graphical environment you are in. Someone or something has to teach session dbus about the graphical environment by passing environment variables describing the graphical environment to session dbus.<br />
<br />
{{bc|1=gnome-keyring-daemon --start --components=secrets}}<br />
<br />
During login, PAM starts {{ic|gnome-keyring-daemon --login}} which is responsible for keeping gnome-keyring unlocked with login password. If {{ic|gnome-keyring-daemon --login}} is not connected to session dbus within a few minutes, {{ic|gnome-keyring-daemon --login}} dies. If {{ic|gnome-keyring-daemon --start ...}} is started against session dbus in a window manager, {{ic|gnome-keyring-daemon --login}} is connected to session dbus. If your login session does not start {{ic|gnome-keyring-daemon --start ...}} before {{ic|gnome-keyring-daemon --login}} quits, you can also use any program that uses gnome-keyring or secret service API before {{ic|gnome-keyring-daemon --login}} dies.<br />
<br />
== Troubleshooting ==<br />
<br />
=== Passwords are not remembered ===<br />
<br />
If you are prompted for a password after logging in and you find that your passwords are not saved, then you may need to create/set a default keyring. To do this using Seahorse (a.k.a. Passwords and Keys), see [https://help.gnome.org/users/seahorse/stable/keyring-create.html Create a new keyring] and [https://help.gnome.org/users/seahorse/stable/keyring-change-default.html Change the default keyring] in GNOME Help.<br />
<br />
=== Resetting the keyring ===<br />
<br />
You will need to [[#Manage using GUI|change your login keyring password]] if you receive the following error message: "The password you use to login to your computer no longer matches that of your login keyring".<br />
<br />
Alternatively, you can remove the {{ic|login.keyring}} and {{ic|user.keystore}} files from {{ic|~/.local/share/keyrings/}}. Be warned that this will permanently delete all saved keys. After removing the files, simply log out and log in again.<br />
<br />
=== Unable to locate daemon control file ===<br />
<br />
The following error may appear in the [[journal]] after logging in:<br />
<br />
gkr-pam: unable to locate daemon control file<br />
<br />
This message "can be safely ignored" if there are no other related issues [https://bbs.archlinux.org/viewtopic.php?pid=1940190#p1940190].<br />
<br />
=== No such secret collection at path: / ===<br />
<br />
If you use a custom {{ic|~/.xinitrc}} and receive this error when trying to create a new keyring with Seahorse, this may be solved by adding the following line [https://bbs.archlinux.org/viewtopic.php?pid=1640822#p1640822] <br />
<br />
{{hc|~/.xinitrc|<br />
source /etc/X11/xinit/xinitrc.d/50-systemd-user.sh<br />
}}<br />
<br />
=== Terminal gives the message "discover_other_daemon: 1" ===<br />
<br />
This is caused by gnome-keyring-deamon being started for the second time. Since a systemd service is delivered together with the daemon, you do not need to start it another way. So make sure to remove the start command from your {{ic|.zshenv}}, {{ic|.bash_profile}}, {{ic|.xinitrc}}, {{ic|config.fish}} or similar. Alternatively you can [[disable]] the {{ic|gnome-keyring-daemon.service}} and {{ic|gnome-keyring-daemon.socket}} [[user unit]]s.<br />
<br />
== See also ==<br />
<br />
* https://help.gnome.org/users/seahorse/stable/<br />
* [https://wiki.gnome.org/action/show/Projects/GnomeKeyring GNOME Wiki page]</div>Sirrus233https://wiki.archlinux.org/index.php?title=GNOME/Keyring&diff=755489GNOME/Keyring2022-11-01T13:16:32Z<p>Sirrus233: Typo fix</p>
<hr />
<div>[[Category:GNOME]]<br />
[[es:GNOME (Español)/Keyring]]<br />
[[ja:GNOME Keyring]]<br />
[[zh-hans:GNOME (简体中文)/Keyring]]<br />
[https://wiki.gnome.org/Projects/GnomeKeyring GNOME Keyring] is "a collection of components in GNOME that store secrets, passwords, keys, certificates and make them available to applications."<br />
<br />
== Installation ==<br />
<br />
{{Pkg|gnome-keyring}} is a member of the {{Grp|gnome}} group is thus usually present on systems running GNOME. The package can otherwise be [[install]]ed on its own. {{Pkg|libsecret}} should also be installed to grant other applications access to your keyrings. Although {{Pkg|libgnome-keyring}} is deprecated (and superseded by ''libsecret''), it may still be required by certain applications.<br />
<br />
The gnome-keyring-daemon is automatically started via a systemd user service upon logging in. It can also be started upon request via a socket.<br />
<br />
Extra utilities related to GNOME Keyring include:<br />
<br />
* {{App|secret-tool|Access the GNOME Keyring (and any other service implementing the [https://specifications.freedesktop.org/secret-service/ DBus Secret Service API]) from the command line.|https://wiki.gnome.org/Projects/Libsecret|{{Pkg|libsecret}}}}<br />
* {{App|lssecret|List all secret items using ''libsecret'' (e.g. GNOME Keyring).|https://gitlab.com/GrantMoyer/lssecret|{{AUR|lssecret-git}}}}<br />
* {{App|gnome-keyring-query|Provides a simple command-line tool for querying passwords from the password store of the GNOME Keyring.|[https://web.archive.org/web/20160326164641/https://gentoo-wiki.info/HOWTO_Use_gnome-keyring_to_store_SSH_passphrases https://gentoo-wiki.info/HOWTO_Use_gnome-keyring_to_store_SSH_passphrases] (archived)|{{AUR|gnome-keyring-query}}}}<br />
<br />
{{Note|''gnome-keyring-query'' only requires ''libgnome-keyring'' as a build dependency.}}<br />
<br />
== Manage using GUI ==<br />
<br />
You can manage the contents of GNOME Keyring using Seahorse; [[install]] the {{Pkg|seahorse}} package.<br />
<br />
Passwords for keyrings (e.g., the default keyring, "Login") can be changed and even removed. See [https://help.gnome.org/users/seahorse/stable/keyring-create.html Create a new keyring] and [https://help.gnome.org/users/seahorse/stable/keyring-update-password.html Update the keyring password] in GNOME Help for more information.<br />
<br />
== Using the keyring ==<br />
<br />
The [[PAM]] module ''pam_gnome_keyring.so'' initialises GNOME Keyring partially, unlocking the default ''login'' keyring in the process. The gnome-keyring-daemon is automatically started with a systemd user service.<br />
<br />
=== PAM step ===<br />
<br />
{{Note|To use automatic unlocking '''without automatic login''', the password for the user account should be the same as the default keyring. See [[#Automatically change keyring password with user password]].}}<br />
{{Tip|<br />
* To use automatic unlocking with automatic login, you can set a blank password for the default keyring. Note that the contents of the keyring are stored unencrypted in this case.<br />
* Alternatively, if using GDM and LUKS, GDM can unlock your keyring if it matches your LUKS password. For this to work, you need to use the [[Mkinitcpio#Common hooks|systemd init in your mkinitcpio.conf]] as well as the [[Dm-crypt/System configuration#Using sd-encrypt hook|appropriate kernel parameters]]{{Broken section link}}. See [https://reddit.com/r/Fedora/comments/jwnqq5/] for more details.<br />
* Skipping the PAM step works, because the [[#--start step|next step]]{{Broken section link}} will initialise the daemon when one is not running already; however, the default keyring is not unlocked in this case. More details are available at [https://wiki.gnome.org/Projects/GnomeKeyring/RunningDaemon].<br />
}}<br />
<br />
When using a display manager, the keyring works out of the box for most cases. [[GDM]], [[LightDM]], [[LXDM]], and [[SDDM]] already have the necessary PAM configuration. For a display manager that does not automatically unlock the keyring edit the appropriate file instead of {{ic|/etc/pam.d/login}} as mentioned below.<br />
<br />
When using console-based login, edit {{ic|/etc/pam.d/login}}:<br />
<br />
Add {{ic|auth optional pam_gnome_keyring.so}} at the end of the {{ic|auth}} section and {{ic|session optional pam_gnome_keyring.so auto_start}} at the end of the {{ic|session}} section.<br />
<br />
{{hc|/etc/pam.d/login|<br />
#%PAM-1.0<br />
<br />
auth required pam_securetty.so<br />
auth requisite pam_nologin.so<br />
auth include system-local-login<br />
'''auth optional pam_gnome_keyring.so'''<br />
account include system-local-login<br />
session include system-local-login<br />
'''session optional pam_gnome_keyring.so auto_start'''<br />
}}<br />
<br />
== SSH keys ==<br />
<br />
'''gnome-keyring-daemon''' with the '''ssh''' component will start an SSH agent and automatically load all the keys in {{ic|~/.ssh/}} that have corresponding ''.pub'' files. There is no way to remove these keys from the agent.<br />
<br />
To list all loaded keys:<br />
<br />
$ ssh-add -L<br />
<br />
When you connect to a server that uses a loaded key with a password, a dialog will popup asking you for the passphrase. It has an option to automatically unlock the key when you log in. If you check this, you will not need to enter your passphrase again!<br />
<br />
To permanently save the a passphrase in the keyring, use ssh-askpass from the {{pkg|seahorse}} package:<br />
<br />
$ /usr/lib/seahorse/ssh-askpass my_key<br />
<br />
To manually add an SSH key from another directory:<br />
<br />
$ ssh-add ~/.private/id_rsa<br />
Enter passphrase for ~/.private/id_rsa:<br />
<br />
{{Note|You have to have the corresponding ''.pub'' file in the same directory as the private key ({{ic|~/.ssh/id_rsa.pub}} in the example). Also, make sure that the public key is the file name of the private key plus ''.pub'' (for example, {{ic|my_key.pub}}).}}<br />
<br />
To disable all manually added keys:<br />
<br />
$ ssh-add -D<br />
<br />
=== Enable the keyring ssh component ===<br />
<br />
The default systemd user service shipped with the keyring does not include the '''ssh''' component. '''ssh''' must be added to the {{ic|--components}} option of the {{ic|gnome-keyring-daemon}} command in the {{ic|ExecStart}} line of the unit file.<br />
<br />
See [[Systemd#Editing provided units]] for how to edit the keyring's systemd unit file.<br />
<br />
You must also [[enable]] the {{ic|gcr-ssh-agent.service}} [[user unit]]. This is no longer provided in the gcr package depended on by gnome-keyring, so it is necessary to install {{Pkg|gcr-4}}.<br />
<br />
Additionally, you will need to point an environment variable to the auth socket. <br />
{{ic|1=export SSH_AUTH_SOCK=/run/user/$(id -u)/gcr/ssh}}<br />
<br />
=== Disable keyring daemon components ===<br />
<br />
If you wish to run an alternative SSH agent (e.g. [[SSH keys#ssh-agent|ssh-agent]] or [[GnuPG#gpg-agent|gpg-agent]]), you need to disable the {{ic|ssh}} component of GNOME Keyring. To do so in an account-local way, copy {{ic|/etc/xdg/autostart/gnome-keyring-ssh.desktop}} to {{ic|~/.config/autostart/}} and then append the line {{ic|1=Hidden=true}} to the copied file. Then log out.<br />
<br />
== Tips and tricks ==<br />
<br />
=== Integration with applications ===<br />
<br />
* [[Chromium#Force a password store|Chromium]]<br />
<br />
=== Flushing passphrases ===<br />
<br />
$ gnome-keyring-daemon -r -d<br />
<br />
This command starts gnome-keyring-daemon, shutting down previously running instances.<br />
<br />
=== Git integration ===<br />
<br />
The GNOME keyring is useful in conjunction with [[Git]] when you are pushing over HTTPS. The {{Pkg|libsecret}} package [[#Installation|needs to be installed for this functionality to be available]].<br />
<br />
Configure Git to use the ''libsecret'' helper:<br />
<br />
$ git config --global credential.helper /usr/lib/git-core/git-credential-libsecret<br />
<br />
The next time you run {{ic|git push}}, you will be asked to unlock your keyring if it is not already unlocked.<br />
<br />
=== GnuPG integration ===<br />
<br />
Several applications which use GnuPG require a {{ic|pinentry-program}} to be set. Set the following to use GNOME 3 pinentry for GNOME Keyring to manage passphrase prompts.<br />
<br />
{{hc|~/.gnupg/gpg-agent.conf|<br />
pinentry-program /usr/bin/pinentry-gnome3<br />
}}<br />
<br />
Another option is to [[GnuPG#Unattended passphrase|force loopback for GPG]] which should allow the passphrase to be entered in the application.<br />
<br />
=== Renaming a keyring ===<br />
<br />
The display name for a keyring (i.e., the name that appears in Seahorse and from {{ic|file}}) can be changed by [https://ttboj.wordpress.com/2013/01/27/renaming-a-gnome-keyring-for-seahorse-the-passwords-and-keyrings-application/ changing the value of display-name in the unencrypted keyring file]. Keyrings will usually be stored in {{ic|~/.local/share/keyrings/}} with the ''.keyring'' file extension.<br />
<br />
=== Automatically change keyring password with user password ===<br />
<br />
{{Note|This only affects the default keyring.}}<br />
<br />
Add {{ic|password optional pam_gnome_keyring.so}} to the end of {{ic|/etc/pam.d/passwd}}.<br />
{{hc|/etc/pam.d/passwd|2=<br />
#%PAM-1.0<br />
<br />
#password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3<br />
#password required pam_unix.so sha512 shadow use_authtok<br />
password required pam_unix.so sha512 shadow nullok<br />
'''password optional pam_gnome_keyring.so'''<br />
}}<br />
<br />
=== Launching gnome-keyring-daemon outside desktop environments (KDE, GNOME, XFCE, ...) ===<br />
<br />
{{Accuracy|At least [[xinit]] and [[SDDM]] execute all scripts from {{ic|/etc/X11/xinit/xinitrc.d/}} and [[sway]] provides {{ic|/etc/sway/config.d/50-systemd-user.conf}} so the problem is not being "outside desktop environments". If gnome-keyring requires [[XDG Autostart]], the installation/configuration section should say so.}}<br />
<br />
If you are using sway, i3, or any window manager that does not execute<br />
<br />
* {{ic|/etc/xdg/autostart/gnome-keyring-*.desktop}}<br />
* {{ic|/etc/X11/xinit/xinitrc.d/50-systemd-user.sh}}<br />
<br />
your window manager needs to execute the following commands during window manager startup. The commands do not need to be executed in any specific order.<br />
<br />
{{bc|dbus-update-activation-environment DISPLAY XAUTHORITY WAYLAND_DISPLAY}}<br />
or<br />
{{bc|dbus-update-activation-environment --all}}<br />
<br />
This command passes environment variables from the window manager to session dbus. Without this, GUI prompts cannot be triggered over DBus. For example, this is required for seahorse password prompt.<br />
<br />
This is required because session dbus is started before graphical environment is started. Thus, session dbus does not know about the graphical environment you are in. Someone or something has to teach session dbus about the graphical environment by passing environment variables describing the graphical environment to session dbus.<br />
<br />
{{bc|1=gnome-keyring-daemon --start --components=secrets}}<br />
<br />
During login, PAM starts {{ic|gnome-keyring-daemon --login}} which is responsible for keeping gnome-keyring unlocked with login password. If {{ic|gnome-keyring-daemon --login}} is not connected to session dbus within a few minutes, {{ic|gnome-keyring-daemon --login}} dies. If {{ic|gnome-keyring-daemon --start ...}} is started against session dbus in a window manager, {{ic|gnome-keyring-daemon --login}} is connected to session dbus. If your login session does not start {{ic|gnome-keyring-daemon --start ...}} before {{ic|gnome-keyring-daemon --login}} quits, you can also use any program that uses gnome-keyring or secret service API before {{ic|gnome-keyring-daemon --login}} dies.<br />
<br />
== Troubleshooting ==<br />
<br />
=== Passwords are not remembered ===<br />
<br />
If you are prompted for a password after logging in and you find that your passwords are not saved, then you may need to create/set a default keyring. To do this using Seahorse (a.k.a. Passwords and Keys), see [https://help.gnome.org/users/seahorse/stable/keyring-create.html Create a new keyring] and [https://help.gnome.org/users/seahorse/stable/keyring-change-default.html Change the default keyring] in GNOME Help.<br />
<br />
=== Resetting the keyring ===<br />
<br />
You will need to [[#Manage using GUI|change your login keyring password]] if you receive the following error message: "The password you use to login to your computer no longer matches that of your login keyring".<br />
<br />
Alternatively, you can remove the {{ic|login.keyring}} and {{ic|user.keystore}} files from {{ic|~/.local/share/keyrings/}}. Be warned that this will permanently delete all saved keys. After removing the files, simply log out and log in again.<br />
<br />
=== Unable to locate daemon control file ===<br />
<br />
The following error may appear in the [[journal]] after logging in:<br />
<br />
gkr-pam: unable to locate daemon control file<br />
<br />
This message "can be safely ignored" if there are no other related issues [https://bbs.archlinux.org/viewtopic.php?pid=1940190#p1940190].<br />
<br />
=== No such secret collection at path: / ===<br />
<br />
If you use a custom {{ic|~/.xinitrc}} and receive this error when trying to create a new keyring with Seahorse, this may be solved by adding the following line [https://bbs.archlinux.org/viewtopic.php?pid=1640822#p1640822] <br />
<br />
{{hc|~/.xinitrc|<br />
source /etc/X11/xinit/xinitrc.d/50-systemd-user.sh<br />
}}<br />
<br />
=== Terminal gives the message "discover_other_daemon: 1" ===<br />
<br />
This is caused by gnome-keyring-deamon being started for the second time. Since a systemd service is delivered together with the daemon, you do not need to start it another way. So make sure to remove the start command from your {{ic|.zshenv}}, {{ic|.bash_profile}}, {{ic|.xinitrc}}, {{ic|config.fish}} or similar. Alternatively you can [[disable]] the {{ic|gnome-keyring-daemon.service}} and {{ic|gnome-keyring-daemon.socket}} [[user unit]]s.<br />
<br />
== See also ==<br />
<br />
* https://help.gnome.org/users/seahorse/stable/<br />
* [https://wiki.gnome.org/action/show/Projects/GnomeKeyring GNOME Wiki page]</div>Sirrus233https://wiki.archlinux.org/index.php?title=GNOME/Keyring&diff=755488GNOME/Keyring2022-11-01T13:15:46Z<p>Sirrus233: Instructions for running the ssh agent with gnome keyring are out of date / incomplete</p>
<hr />
<div>[[Category:GNOME]]<br />
[[es:GNOME (Español)/Keyring]]<br />
[[ja:GNOME Keyring]]<br />
[[zh-hans:GNOME (简体中文)/Keyring]]<br />
[https://wiki.gnome.org/Projects/GnomeKeyring GNOME Keyring] is "a collection of components in GNOME that store secrets, passwords, keys, certificates and make them available to applications."<br />
<br />
== Installation ==<br />
<br />
{{Pkg|gnome-keyring}} is a member of the {{Grp|gnome}} group is thus usually present on systems running GNOME. The package can otherwise be [[install]]ed on its own. {{Pkg|libsecret}} should also be installed to grant other applications access to your keyrings. Although {{Pkg|libgnome-keyring}} is deprecated (and superseded by ''libsecret''), it may still be required by certain applications.<br />
<br />
The gnome-keyring-daemon is automatically started via a systemd user service upon logging in. It can also be started upon request via a socket.<br />
<br />
Extra utilities related to GNOME Keyring include:<br />
<br />
* {{App|secret-tool|Access the GNOME Keyring (and any other service implementing the [https://specifications.freedesktop.org/secret-service/ DBus Secret Service API]) from the command line.|https://wiki.gnome.org/Projects/Libsecret|{{Pkg|libsecret}}}}<br />
* {{App|lssecret|List all secret items using ''libsecret'' (e.g. GNOME Keyring).|https://gitlab.com/GrantMoyer/lssecret|{{AUR|lssecret-git}}}}<br />
* {{App|gnome-keyring-query|Provides a simple command-line tool for querying passwords from the password store of the GNOME Keyring.|[https://web.archive.org/web/20160326164641/https://gentoo-wiki.info/HOWTO_Use_gnome-keyring_to_store_SSH_passphrases https://gentoo-wiki.info/HOWTO_Use_gnome-keyring_to_store_SSH_passphrases] (archived)|{{AUR|gnome-keyring-query}}}}<br />
<br />
{{Note|''gnome-keyring-query'' only requires ''libgnome-keyring'' as a build dependency.}}<br />
<br />
== Manage using GUI ==<br />
<br />
You can manage the contents of GNOME Keyring using Seahorse; [[install]] the {{Pkg|seahorse}} package.<br />
<br />
Passwords for keyrings (e.g., the default keyring, "Login") can be changed and even removed. See [https://help.gnome.org/users/seahorse/stable/keyring-create.html Create a new keyring] and [https://help.gnome.org/users/seahorse/stable/keyring-update-password.html Update the keyring password] in GNOME Help for more information.<br />
<br />
== Using the keyring ==<br />
<br />
The [[PAM]] module ''pam_gnome_keyring.so'' initialises GNOME Keyring partially, unlocking the default ''login'' keyring in the process. The gnome-keyring-daemon is automatically started with a systemd user service.<br />
<br />
=== PAM step ===<br />
<br />
{{Note|To use automatic unlocking '''without automatic login''', the password for the user account should be the same as the default keyring. See [[#Automatically change keyring password with user password]].}}<br />
{{Tip|<br />
* To use automatic unlocking with automatic login, you can set a blank password for the default keyring. Note that the contents of the keyring are stored unencrypted in this case.<br />
* Alternatively, if using GDM and LUKS, GDM can unlock your keyring if it matches your LUKS password. For this to work, you need to use the [[Mkinitcpio#Common hooks|systemd init in your mkinitcpio.conf]] as well as the [[Dm-crypt/System configuration#Using sd-encrypt hook|appropriate kernel parameters]]{{Broken section link}}. See [https://reddit.com/r/Fedora/comments/jwnqq5/] for more details.<br />
* Skipping the PAM step works, because the [[#--start step|next step]]{{Broken section link}} will initialise the daemon when one is not running already; however, the default keyring is not unlocked in this case. More details are available at [https://wiki.gnome.org/Projects/GnomeKeyring/RunningDaemon].<br />
}}<br />
<br />
When using a display manager, the keyring works out of the box for most cases. [[GDM]], [[LightDM]], [[LXDM]], and [[SDDM]] already have the necessary PAM configuration. For a display manager that does not automatically unlock the keyring edit the appropriate file instead of {{ic|/etc/pam.d/login}} as mentioned below.<br />
<br />
When using console-based login, edit {{ic|/etc/pam.d/login}}:<br />
<br />
Add {{ic|auth optional pam_gnome_keyring.so}} at the end of the {{ic|auth}} section and {{ic|session optional pam_gnome_keyring.so auto_start}} at the end of the {{ic|session}} section.<br />
<br />
{{hc|/etc/pam.d/login|<br />
#%PAM-1.0<br />
<br />
auth required pam_securetty.so<br />
auth requisite pam_nologin.so<br />
auth include system-local-login<br />
'''auth optional pam_gnome_keyring.so'''<br />
account include system-local-login<br />
session include system-local-login<br />
'''session optional pam_gnome_keyring.so auto_start'''<br />
}}<br />
<br />
== SSH keys ==<br />
<br />
'''gnome-keyring-daemon''' with the '''ssh''' component will start an SSH agent and automatically load all the keys in {{ic|~/.ssh/}} that have corresponding ''.pub'' files. There is no way to remove these keys from the agent.<br />
<br />
To list all loaded keys:<br />
<br />
$ ssh-add -L<br />
<br />
When you connect to a server that uses a loaded key with a password, a dialog will popup asking you for the passphrase. It has an option to automatically unlock the key when you log in. If you check this, you will not need to enter your passphrase again!<br />
<br />
To permanently save the a passphrase in the keyring, use ssh-askpass from the {{pkg|seahorse}} package:<br />
<br />
$ /usr/lib/seahorse/ssh-askpass my_key<br />
<br />
To manually add an SSH key from another directory:<br />
<br />
$ ssh-add ~/.private/id_rsa<br />
Enter passphrase for ~/.private/id_rsa:<br />
<br />
{{Note|You have to have the corresponding ''.pub'' file in the same directory as the private key ({{ic|~/.ssh/id_rsa.pub}} in the example). Also, make sure that the public key is the file name of the private key plus ''.pub'' (for example, {{ic|my_key.pub}}).}}<br />
<br />
To disable all manually added keys:<br />
<br />
$ ssh-add -D<br />
<br />
=== Enable the keyring ssh component ===<br />
<br />
The default systemd user service shipped with the keyring does not include the '''ssh''' component. '''ssh''' must be added to the {{ic|--components}} option of the {{ic|gnome-keyring-daemon}} command in the {{ic|ExecStart}} line of the unit file.<br />
<br />
See [[Systemd#Editing provided units]] for how to edit the keyring's systemd unit file.<br />
<br />
You must also [[enable]] the {{ic|gcr-ssh-agent.service}} [[user unit]]. This is no longer provided in the gcr package depended on by gnome-keyring, so it is necessary to install {{Pkg|gcr-4}}.<br />
<br />
Additionally, you will need to point an environment variable to the auth socket. <br />
{{ic|1=export SSH_AUTH_SOCK\=/run/user/$(id -u)/gcr/ssh}}<br />
<br />
=== Disable keyring daemon components ===<br />
<br />
If you wish to run an alternative SSH agent (e.g. [[SSH keys#ssh-agent|ssh-agent]] or [[GnuPG#gpg-agent|gpg-agent]]), you need to disable the {{ic|ssh}} component of GNOME Keyring. To do so in an account-local way, copy {{ic|/etc/xdg/autostart/gnome-keyring-ssh.desktop}} to {{ic|~/.config/autostart/}} and then append the line {{ic|1=Hidden=true}} to the copied file. Then log out.<br />
<br />
== Tips and tricks ==<br />
<br />
=== Integration with applications ===<br />
<br />
* [[Chromium#Force a password store|Chromium]]<br />
<br />
=== Flushing passphrases ===<br />
<br />
$ gnome-keyring-daemon -r -d<br />
<br />
This command starts gnome-keyring-daemon, shutting down previously running instances.<br />
<br />
=== Git integration ===<br />
<br />
The GNOME keyring is useful in conjunction with [[Git]] when you are pushing over HTTPS. The {{Pkg|libsecret}} package [[#Installation|needs to be installed for this functionality to be available]].<br />
<br />
Configure Git to use the ''libsecret'' helper:<br />
<br />
$ git config --global credential.helper /usr/lib/git-core/git-credential-libsecret<br />
<br />
The next time you run {{ic|git push}}, you will be asked to unlock your keyring if it is not already unlocked.<br />
<br />
=== GnuPG integration ===<br />
<br />
Several applications which use GnuPG require a {{ic|pinentry-program}} to be set. Set the following to use GNOME 3 pinentry for GNOME Keyring to manage passphrase prompts.<br />
<br />
{{hc|~/.gnupg/gpg-agent.conf|<br />
pinentry-program /usr/bin/pinentry-gnome3<br />
}}<br />
<br />
Another option is to [[GnuPG#Unattended passphrase|force loopback for GPG]] which should allow the passphrase to be entered in the application.<br />
<br />
=== Renaming a keyring ===<br />
<br />
The display name for a keyring (i.e., the name that appears in Seahorse and from {{ic|file}}) can be changed by [https://ttboj.wordpress.com/2013/01/27/renaming-a-gnome-keyring-for-seahorse-the-passwords-and-keyrings-application/ changing the value of display-name in the unencrypted keyring file]. Keyrings will usually be stored in {{ic|~/.local/share/keyrings/}} with the ''.keyring'' file extension.<br />
<br />
=== Automatically change keyring password with user password ===<br />
<br />
{{Note|This only affects the default keyring.}}<br />
<br />
Add {{ic|password optional pam_gnome_keyring.so}} to the end of {{ic|/etc/pam.d/passwd}}.<br />
{{hc|/etc/pam.d/passwd|2=<br />
#%PAM-1.0<br />
<br />
#password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3<br />
#password required pam_unix.so sha512 shadow use_authtok<br />
password required pam_unix.so sha512 shadow nullok<br />
'''password optional pam_gnome_keyring.so'''<br />
}}<br />
<br />
=== Launching gnome-keyring-daemon outside desktop environments (KDE, GNOME, XFCE, ...) ===<br />
<br />
{{Accuracy|At least [[xinit]] and [[SDDM]] execute all scripts from {{ic|/etc/X11/xinit/xinitrc.d/}} and [[sway]] provides {{ic|/etc/sway/config.d/50-systemd-user.conf}} so the problem is not being "outside desktop environments". If gnome-keyring requires [[XDG Autostart]], the installation/configuration section should say so.}}<br />
<br />
If you are using sway, i3, or any window manager that does not execute<br />
<br />
* {{ic|/etc/xdg/autostart/gnome-keyring-*.desktop}}<br />
* {{ic|/etc/X11/xinit/xinitrc.d/50-systemd-user.sh}}<br />
<br />
your window manager needs to execute the following commands during window manager startup. The commands do not need to be executed in any specific order.<br />
<br />
{{bc|dbus-update-activation-environment DISPLAY XAUTHORITY WAYLAND_DISPLAY}}<br />
or<br />
{{bc|dbus-update-activation-environment --all}}<br />
<br />
This command passes environment variables from the window manager to session dbus. Without this, GUI prompts cannot be triggered over DBus. For example, this is required for seahorse password prompt.<br />
<br />
This is required because session dbus is started before graphical environment is started. Thus, session dbus does not know about the graphical environment you are in. Someone or something has to teach session dbus about the graphical environment by passing environment variables describing the graphical environment to session dbus.<br />
<br />
{{bc|1=gnome-keyring-daemon --start --components=secrets}}<br />
<br />
During login, PAM starts {{ic|gnome-keyring-daemon --login}} which is responsible for keeping gnome-keyring unlocked with login password. If {{ic|gnome-keyring-daemon --login}} is not connected to session dbus within a few minutes, {{ic|gnome-keyring-daemon --login}} dies. If {{ic|gnome-keyring-daemon --start ...}} is started against session dbus in a window manager, {{ic|gnome-keyring-daemon --login}} is connected to session dbus. If your login session does not start {{ic|gnome-keyring-daemon --start ...}} before {{ic|gnome-keyring-daemon --login}} quits, you can also use any program that uses gnome-keyring or secret service API before {{ic|gnome-keyring-daemon --login}} dies.<br />
<br />
== Troubleshooting ==<br />
<br />
=== Passwords are not remembered ===<br />
<br />
If you are prompted for a password after logging in and you find that your passwords are not saved, then you may need to create/set a default keyring. To do this using Seahorse (a.k.a. Passwords and Keys), see [https://help.gnome.org/users/seahorse/stable/keyring-create.html Create a new keyring] and [https://help.gnome.org/users/seahorse/stable/keyring-change-default.html Change the default keyring] in GNOME Help.<br />
<br />
=== Resetting the keyring ===<br />
<br />
You will need to [[#Manage using GUI|change your login keyring password]] if you receive the following error message: "The password you use to login to your computer no longer matches that of your login keyring".<br />
<br />
Alternatively, you can remove the {{ic|login.keyring}} and {{ic|user.keystore}} files from {{ic|~/.local/share/keyrings/}}. Be warned that this will permanently delete all saved keys. After removing the files, simply log out and log in again.<br />
<br />
=== Unable to locate daemon control file ===<br />
<br />
The following error may appear in the [[journal]] after logging in:<br />
<br />
gkr-pam: unable to locate daemon control file<br />
<br />
This message "can be safely ignored" if there are no other related issues [https://bbs.archlinux.org/viewtopic.php?pid=1940190#p1940190].<br />
<br />
=== No such secret collection at path: / ===<br />
<br />
If you use a custom {{ic|~/.xinitrc}} and receive this error when trying to create a new keyring with Seahorse, this may be solved by adding the following line [https://bbs.archlinux.org/viewtopic.php?pid=1640822#p1640822] <br />
<br />
{{hc|~/.xinitrc|<br />
source /etc/X11/xinit/xinitrc.d/50-systemd-user.sh<br />
}}<br />
<br />
=== Terminal gives the message "discover_other_daemon: 1" ===<br />
<br />
This is caused by gnome-keyring-deamon being started for the second time. Since a systemd service is delivered together with the daemon, you do not need to start it another way. So make sure to remove the start command from your {{ic|.zshenv}}, {{ic|.bash_profile}}, {{ic|.xinitrc}}, {{ic|config.fish}} or similar. Alternatively you can [[disable]] the {{ic|gnome-keyring-daemon.service}} and {{ic|gnome-keyring-daemon.socket}} [[user unit]]s.<br />
<br />
== See also ==<br />
<br />
* https://help.gnome.org/users/seahorse/stable/<br />
* [https://wiki.gnome.org/action/show/Projects/GnomeKeyring GNOME Wiki page]</div>Sirrus233https://wiki.archlinux.org/index.php?title=StarCraft_2&diff=454197StarCraft 22016-10-17T08:10:21Z<p>Sirrus233: Undo revision 454145 by Anatolik (talk) See article discussion page for justification: https://wiki.archlinux.org/index.php/Talk:StarCraft_2</p>
<hr />
<div>[[Category:Gaming]]<br />
[[Category:Wine]]<br />
[http://eu.battle.net/sc2/en/ StarCraft II] is a real-time strategy game from Blizzard Entertainment released in 2010. A native Linux version isn't available, but the game is fully playable using [[Wine]].<br />
<br />
== Installation ==<br />
<br />
==== Packages ====<br />
<br />
You need to [[install]] {{Pkg|wine}}, {{Pkg|lib32-libjpeg-turbo}}, {{Pkg|lib32-libpng}} and {{Pkg|lib32-libldap}}. If you are using [[PulseAudio]], install {{Pkg|lib32-libpulse}} and {{Pkg|lib32-alsa-plugins}} available in [[multilib]]. Optionally, instead of regular {{Pkg|wine}}, you might prefer {{Pkg|wine-staging}} - [[Wine#CSMT_patch|enabling CSMT via the Staging tab in winecfg]] may greatly improve performance, but is not required. You'll also need to use {{Pkg|winetricks}} and install the following components (to use the Map Editor and avoid crashes on certain system configurations):<br />
<br />
$ winetricks corefonts vcrun2005 vcrun2008 vcrun2015<br />
<br />
==== Configuration ====<br />
<br />
If you have a GPU which doesn't properly report the amount of memory available (older integrated or early AMD APUs), you'll need to tell Wine how much VRAM you have available. Open the Registry Editor:<br />
<br />
$ regedit<br />
<br />
Go to ''HKEY_CURRENT_USER/Software/Wine/Direct3D'' (right-click on Wine and New -> Key, ''Direct3D'', Enter, if it doesn't exist) right-click on ''Direct3D'' (if such a key doesn't exist, right-click on ''Wine'', New -> Key, ''Direct3D'', OK), select New -> String Value, ''VideoMemorySize'', which you should set to the amount of VRAM your GPU has, in MB (for example, "1024" or "2048"). If you're using an integrated GPU, try to preallocate a fair amount of RAM for your GPU in BIOS/UEFI Setup and use the same value here (512 is good enough for low-medium settings).<br />
<br />
* If the Battle.net App doesn't work, use a new Wine prefix.<br />
* '''If you are asked to install Gecko, then click Install to do so.'''<br />
* If the Battle.net App window is white, open ''winecfg'', go to ''Applications'' and set ''Windows Version'' to "Windows XP". You may do so for Battle.net.exe only, as SC2 itself works fine with this being set to anything newer.<br />
<br />
==== Installing with the Battle.net App ====<br />
<br />
Recent SC2 versions require the [http://eu.battle.net/en/app/ Battle.net App] to be installed, as it replaced the launchers for all Blizzard games. Furthermore, recent patches massively changed the file structure in their newer games - if you have a fast enough internet connection, it might be faster to download a new copy from the Battle.net App than trying to install the game from DVD. Simply install the app, select your region, log in with a Battle.net Account, then select StarCraft II on the left and click Install. You'll be able to select your game language and installation location. (Installing the game on a native Linux filesystem instead of NTFS might improve loading times.)<br />
<br />
==== Installing from DVD ====<br />
<br />
{{Note|If you have a reasonable internet connection (10Mbps or better), redownload the game. Recent patches were massive and you'll literally spend more time waiting for the game to reconfigure and patch than just redownloading the whole game again. Furthermore, you can stream the game while playing.}}<br />
<br />
* Mount DVD/DVD Image, (unhide invisible data), for example:<br />
$ mount -o ro,unhide,uid=1000 /dev/dvd /media/dvd (for the DVD)<br />
$ mount -o loop,ro,unhide,uid=''your_id'' ''starcraft.iso'' /media/dvd (for an image) <br />
* Start the installer:<br />
$ wine start /unix /media/dvd/Installer.exe<br />
<br />
==== Playing StarCraft II ====<br />
<br />
Launch the game from the Battle.net App. Should the game instacrash, click on the Battle.net logo in the Launcher -> Settings -> Game Settings -> Check <code>Launch 32-bit client (instead of 64-bit)</code>. Alternatively, you may <code>cd ~/.wine/drive_c/Program\ Files/StarCraft\ II\Support</code> (not <code>Support64</code>) and <code>wine SC2Switcher.exe</code> to start the game without the launcher - this will make debugging easier, but you may have to select your region in-game.<br />
<br />
== Hints for Performance Tuning ==<br />
<br />
* {{ic|Ctrl+Alt+F}} shows FPS.<br />
* Make sure that you are using the latest available graphics drivers. Nvidia drivers should be 256.35 or later (drivers in repositories are up to date).<br />
* Edit the variables.txt in your My Documents/Starcraft II/ following the guide [http://www.teamliquid.net/forum/viewmessage.php?topic_id=142046 here].<br />
* If you're using Intel HD Graphics 3000, you may have to set the VideoMemorySize to 128 (see the Configuration above). The game will complain about not enough VRAM otherwise.<br />
* If you have problems updating the game and see the following in the output:<br />
{{bc|<nowiki>Agent started on port #6882<br />
Executing operation: disable_firewall applicationPath="C:\users\Public\Application Data\Battle.net\Agent\Agent.4432\Agent.exe" applicationName="Battle.net Update Agent"<br />
AgentAsAdmin failed to add a firewall exception for 'C:\users\Public\Application Data\Battle.net\Agent\Agent.4432\Agent.exe'.<br />
Registered Event: "shutdown event"<br />
Registered Event: "database flush event"<br />
PostTo succeeded status: 0 for url: http://enGB.patch.battle.net:1119/patch<br />
Post Data:<br />
<version program="Agnt"><record program="Bnet" component="Win" version="1" /><record program="Agnt" component="cdn" version="1" /><record program="Agnt" component="cfg" version="1" /><record program="Agnt" component="Win" version="1199" /></version><br />
DownloadTo failed error: 0 of article: from:<br />
<br />
DownloadTo failed error: 0 of article: from:<br />
<br />
DownloadTo failed error: 0 of article: from:</nowiki>}}<br />
Launch Agent.exe --nohttpauth:<br />
$ killall Agent.exe && wine ~/.wine/drive_c/users/Public/AppData/Battle.net/Agent/Agent.exe --nohttpauth<br />
You can now restart the Battle.net App. The updater should proceed smoothly.<br />
<br />
==== Unit Preloader ====<br />
SC2 never fully loads the game initially, but rather streams and loads required files on demand. Unit Preloader is a special map which forces SC2 to load '''all''' units, animations and effects, '''causing high RAM usage''', but prevents loading the data (and massive framerate drops) during multiplayer matches. Open ''Arcade'' and search for ''Unit Preloader''. There are 3 versions - start the one which corresponds to the game edition you'll want to play in multiplayer and wait for the Victory screen. All data will be preloaded until you exit the game to desktop.<br />
<br />
== Hints for advanced hotkeys settings ==<br />
<br />
==== Preliminary ====<br />
Have a look at projects aiming at creating more ergonomic hotkeys for SCII:<br />
* [http://www.teamliquid.net/forum/sc2-strategy/341878-thecore-advanced-keyboard-layout TheCore]<br />
* [http://www.teamliquid.net/forum/sc2-strategy/333891-thecore-lite-advanced-keyboard-layout TheCore Lite]<br />
* [http://www.teamliquid.net/forum/sc2-strategy/404476-fleet-keys-refined-hotkey-systems Fleet Keys]. All of them are projects aiming at creating more ergonomic hotkeys for SCII<br />
[http://www.teamliquid.net/forum/sc2-strategy/446530-rapid-fire-hotkey-trick Rapid Fire] Hotkeys are implemented in those hotkeys settings.<br />
<br />
==== Rapid Fire Hotkey throughput ====<br />
[[Xorg]] keyboard autorepeat can be modified. It may make sense to reduce delay before autorepeat starts (default=660 [ms]). Increasing a bit the repeat rate (default=25 [/s]) is a trade-off: speed vs accuracy.<br />
<br />
To apply the settings:<br />
$ xset r rate <delay_to_activate_in_ms> <nb_of_repeats_per_second><br />
<br />
{{Tip| {{ic|xset r rate}} get X back to default autorepeat settings}}<br />
{{Tip| {{ic|xset q}} let you know the current X settings}}<br />
<br />
==== Enable double-key Rapid Fire Hotkey behaviour ====<br />
Fancy double-key Rapid Fire Trick are not possible by default for Linux.<br />
The [https://git.framasoft.org/bobo/xkb_repeat/tree/master xkb_repeat] git project may help you unlock this behaviour, providing patches to recompile your X server.<br />
<br />
==== Enable CapsLock as a Rapid Fire Hotkey ====<br />
TheCore and TheCore Lite hotkeys rely on CapsLock to be a rapid fire hotkey.<br />
This does not work by default under Linux.<br />
To make it work, CapsLock key could be remapped to another key with [[xmodmap]].<br />
Hereafter an example with "!" character that cannot be used by Starcraft2 in any case.<br />
$ xmodmap -e "remove Lock = Caps_Lock" -e "keycode 66 = exclam"<br />
<br />
The .SC2Hotkeys file would need to be modified, to take it into account to add "!" as an alternate wherever CapsLock is used<br />
$ sed -i -e "s:CapsLock:CapsLock,OEM8:g" <file>.SC2Hotkeys<br />
<br />
{{Tip| {{ic|1= xmodmap -e "add Lock = Caps_Lock" -e "keycode 66 = Caps_Lock" }} to get back to default CapsLock behavior}}<br />
<br />
==== Enable Scrollclick ====<br />
Some scrollclick demo videos:<br />
* [https://www.youtube.com/watch?v=7pQKnS1CPEQ infestor spawning infested terran]<br />
* [https://www.youtube.com/watch?v=9aPd8_9_vB4 scrollclick applied to protoss]<br />
Using [[Xmodmap#Reverse_scrolling|Xmodmap]], it possible to set your regular 3-buttons mouse with scroll wheel to practice scrollclick.<br />
First change scroll fonction to "forward mouse button" and "back mouse button":<br />
$ xmodmap -e "pointer = 1 2 3 8 9 6 7 4 5"<br />
Then add alternate key SCII hotkeys for:<br />
* Global=>Unit Management=>Choose Ability or AI target<br />
* Global=>Unit Management=>Smart Command<br />
{{Tip|{{ic|1=xmodmap -e "pointer = default"}} resets to default mouse functionality}}<br />
<br />
== Troubleshooting ==<br />
<br />
* For some, in-game resolution changing does not work. Editing 'width=x' and 'height=y' in Variables.txt in My Documents/Starcraft II solves this issue. Replace x and y with the prefered resolution.<br />
* Should you experience graphics problems (no 3D background in menu, blue non-texturized units and other glitches), launch the game without Battle.net App (see above) like this: <code>force_s3tc_enable=true wine SC2Switcher.exe</code>. You can also add this option to the .desktop entry in ~/.local/share/applications/wine/Programs/StarCraft II, or edit your <code>~/.drirc</code> file to enable this setting permanently for all apps. Using {{Pkg|driconf}}, you may just enable this setting with a simple GUI.<br />
<br />
== See also ==<br />
<br />
* [https://appdb.winehq.org/objectManager.php?sClass=application&iId=11123 StarCraft II] (WineHQ AppDB)<br />
* [http://bugs.winehq.org/show_bug.cgi?id=23806 StarCraft II crashes because of ACCESS_VIOLATION before the loading screen] (WineHQ bug tracking database)<br />
* [http://bugs.winehq.org/show_bug.cgi?id=23323 World of Warcraft crashes upon login after 3.3.5 patch.] (WineHQ bug tracking database)<br />
* [https://bbs.archlinux.org/viewtopic.php?id=101822 starcraft2 crashing on loading] (Arch Linux forums)<br />
* [https://bbs.archlinux.org/viewtopic.php?id=103354 starcraft2 fails to update to patch 1.03] (Arch Linux forums)<br />
* [http://eu.battle.net/sc2/en/forum/topic/283440977 Patch News] (battle.net EU forums)</div>Sirrus233https://wiki.archlinux.org/index.php?title=Talk:StarCraft_2&diff=454196Talk:StarCraft 22016-10-17T08:09:18Z<p>Sirrus233: /* Necessity of vcrun6sp6 library */</p>
<hr />
<div>== Direct3D settings ==<br />
In Wine 1.9.x VRAM amount is almost always detected properly, and StarCraft no longer breaks on low VRAM reported. Most GPUs not reporting VRAM properly usually are either early Intel/AMD integrated GPUs, or some AMD APUs - they almost universally can't handle SC2 on newer patches (system requirements increased). How about removing the VRAM block in the configuration section? [[User:DragoonAethis|DragoonAethis]] ([[User talk:DragoonAethis|talk]]) 20:36, 7 August 2016 (UTC)<br />
<br />
== Necessity of vcrun6sp6 library ==<br />
<br />
A recent edit suggested that the vcrun6sp6 library needs to be installed with winetricks. However, the game seems to run fine without this library. According to the edit comment, the additional library is supposed to resolve an error 'skin.dll not found', but I am unable to find any evidence that this is an issue for anyone else. I am reverting the edit for now.<br />
<br />
If the library really is required, perhaps it should be marked optional in the article? Along with a description of what bug it resolves. --[[User:Sirrus233|Sirrus233]] ([[User talk:Sirrus233|talk]]) 08:08, 17 October 2016 (UTC)</div>Sirrus233https://wiki.archlinux.org/index.php?title=Talk:StarCraft_2&diff=454195Talk:StarCraft 22016-10-17T08:08:24Z<p>Sirrus233: /* Necessity of vcrun6sp6 library */ new section</p>
<hr />
<div>== Direct3D settings ==<br />
In Wine 1.9.x VRAM amount is almost always detected properly, and StarCraft no longer breaks on low VRAM reported. Most GPUs not reporting VRAM properly usually are either early Intel/AMD integrated GPUs, or some AMD APUs - they almost universally can't handle SC2 on newer patches (system requirements increased). How about removing the VRAM block in the configuration section? [[User:DragoonAethis|DragoonAethis]] ([[User talk:DragoonAethis|talk]]) 20:36, 7 August 2016 (UTC)<br />
<br />
== Necessity of vcrun6sp6 library ==<br />
<br />
A recent edit suggested that the vcrun6sp6 library needs to be installed with winetricks. However, the game seems to run fine without this library. According to the edit comment, the additional library is supposed to resolve an error 'skin.dll not found', but I am unable to find any evidence that this is an issue for anyone else. I am reverting the edit for now.<br />
<br />
If the library really is required, perhaps it should be marked optional in the article? Along with a description of what bug it resolves.</div>Sirrus233https://wiki.archlinux.org/index.php?title=StarCraft_2&diff=443705StarCraft 22016-07-30T11:21:17Z<p>Sirrus233: /* Packages */ Added additional library to be installed via winetricks, which is required as of the latest Battle.net update to avoid a crash.</p>
<hr />
<div>[[Category:Gaming]]<br />
[[Category:Wine]]<br />
[http://eu.battle.net/sc2/en/ StarCraft II] is a real-time strategy game from Blizzard Entertainment released in 2010. A native Linux version isn't available, but the game is fully playable using Wine.<br />
<br />
== Installation ==<br />
<br />
==== Packages ====<br />
<br />
You need to [[install]] {{Pkg|wine}}, {{Pkg|lib32-libjpeg-turbo}}, {{Pkg|lib32-libpng}} and {{Pkg|lib32-libldap}}. If you are using [[PulseAudio]], install {{Pkg|lib32-libpulse}} and {{Pkg|lib32-alsa-plugins}} available in [[multilib]]. Optionally, instead of regular Wine, you might prefer [[Wine#CSMT_via_wine-staging|Wine-Staging]] - enabling CSMT via the Staging tab in winecfg may greatly improve performance, but is not required. You'll also need to use {{Pkg|winetricks}} and install the following components (to use the Map Editor and avoid crashes on certain system configurations):<br />
<br />
$ winetricks corefonts vcrun2005 vcrun2008 vcrun2015<br />
<br />
==== Configuration ====<br />
<br />
You'll need to tell Wine how much VRAM you have. Open the Registry Editor:<br />
<br />
$ regedit<br />
<br />
''(Skip in Wine 1.9.x as key doesn't exist)'' Go to ''HKEY_CURRENT_USER/Software/Wine/Direct3D'', right-click on ''Direct3D'' (if such a key doesn't exist, right-click on ''Wine'', New -> Key, ''Direct3D'', OK), select New -> String Value, ''VideoMemorySize'', which you should set to the amount of VRAM your GPU has, in MB (for example, "1024" or "2048"). If you're using an integrated GPU, try to preallocate a fair amount of RAM for your GPU in BIOS/UEFI Setup and use the same value here (512 is good enough for low-medium settings).<br />
<br />
* If the Battle.net App doesn't work, use a new Wine prefix.<br />
* '''If you are asked to install Gecko, then click Install to do so.'''<br />
* If the Battle.net App window is white, open ''winecfg'', go to ''Applications'' and set ''Windows Version'' to "Windows XP". You may do so for Battle.net.exe only, as SC2 itself works fine with this being set to anything newer.<br />
<br />
==== Installing with the Battle.net App ====<br />
<br />
Recent SC2 versions require the [http://eu.battle.net/en/app/ Battle.net App] to be installed, as it replaced the launchers for all Blizzard games. Furthermore, recent patches massively changed the file structure in their newer games - if you have a fast enough internet connection, it might be faster to download a new copy from the Battle.net App than trying to install the game from DVD. Simply install the app, select your region, log in with a Battle.net Account, then select StarCraft II on the left and click Install. You'll be able to select your game language and installation location. (Installing the game on a native Linux filesystem instead of NTFS might improve loading times.)<br />
<br />
==== Installing from DVD ====<br />
<br />
{{Note|If you have a reasonable internet connection (10Mbps or better), redownload the game. Recent patches were massive and you'll literally spend more time waiting for the game to reconfigure and patch than just redownloading the whole game again. Furthermore, you can stream the game while playing.}}<br />
<br />
* Mount DVD/DVD Image, (unhide invisible data), for example:<br />
$ mount -o ro,unhide,uid=1000 /dev/dvd /media/dvd (for the DVD)<br />
$ mount -o loop,ro,unhide,uid=''your_id'' ''starcraft.iso'' /media/dvd (for an image) <br />
* Start the installer:<br />
$ wine start /unix /media/dvd/Installer.exe<br />
<br />
==== Playing StarCraft II ====<br />
<br />
Launch the game from the Battle.net App. Should the game instacrash, click on the Battle.net logo in the Launcher -> Settings -> Game Settings -> Check <code>Launch 32-bit client (instead of 64-bit)</code>. Alternatively, you may <code>cd ~/.wine/drive_c/Program\ Files/StarCraft\ II\Support</code> (not <code>Support64</code>) and <code>wine SC2Switcher.exe</code> to start the game without the launcher - this will make debugging easier, but you may have to select your region in-game.<br />
<br />
== Hints for Performance Tuning ==<br />
<br />
* {{ic|Ctrl+Alt+F}} shows FPS.<br />
* Make sure that you are using the latest available graphics drivers. Nvidia drivers should be 256.35 or later (drivers in repositories are up to date).<br />
* Edit the variables.txt in your My Documents/Starcraft II/ following the guide [http://www.teamliquid.net/forum/viewmessage.php?topic_id=142046 here].<br />
* If you're using Intel HD Graphics 3000, you may have to set the VideoMemorySize to 128 (see the Configuration above). The game will complain about not enough VRAM otherwise.<br />
* If you have problems updating the game and see the following in the output:<br />
{{bc|<nowiki>Agent started on port #6882<br />
Executing operation: disable_firewall applicationPath="C:\users\Public\Application Data\Battle.net\Agent\Agent.4432\Agent.exe" applicationName="Battle.net Update Agent"<br />
AgentAsAdmin failed to add a firewall exception for 'C:\users\Public\Application Data\Battle.net\Agent\Agent.4432\Agent.exe'.<br />
Registered Event: "shutdown event"<br />
Registered Event: "database flush event"<br />
PostTo succeeded status: 0 for url: http://enGB.patch.battle.net:1119/patch<br />
Post Data:<br />
<version program="Agnt"><record program="Bnet" component="Win" version="1" /><record program="Agnt" component="cdn" version="1" /><record program="Agnt" component="cfg" version="1" /><record program="Agnt" component="Win" version="1199" /></version><br />
DownloadTo failed error: 0 of article: from:<br />
<br />
DownloadTo failed error: 0 of article: from:<br />
<br />
DownloadTo failed error: 0 of article: from:</nowiki>}}<br />
Launch Agent.exe --nohttpauth:<br />
$ killall Agent.exe && wine ~/.wine/drive_c/users/Public/AppData/Battle.net/Agent/Agent.exe --nohttpauth<br />
You can now restart the Battle.net App. The updater should proceed smoothly.<br />
<br />
==== Unit Preloader ====<br />
SC2 never fully loads the game initially, but rather streams and loads required files on demand. Unit Preloader is a special map which forces SC2 to load '''all''' units, animations and effects, '''causing high RAM usage''', but prevents loading the data (and massive framerate drops) during multiplayer matches. Open ''Arcade'' and search for ''Unit Preloader''. There are 3 versions - start the one which corresponds to the game edition you'll want to play in multiplayer and wait for the Victory screen. All data will be preloaded until you exit the game to desktop.<br />
<br />
== Hints for advanced hotkeys settings ==<br />
<br />
==== Preliminary ====<br />
Have a look at projects aiming at creating more ergonomic hotkeys for SCII:<br />
* [http://www.teamliquid.net/forum/sc2-strategy/341878-thecore-advanced-keyboard-layout TheCore]<br />
* [http://www.teamliquid.net/forum/sc2-strategy/333891-thecore-lite-advanced-keyboard-layout TheCore Lite]<br />
* [http://www.teamliquid.net/forum/sc2-strategy/404476-fleet-keys-refined-hotkey-systems Fleet Keys]. All of them are projects aiming at creating more ergonomic hotkeys for SCII<br />
[http://www.teamliquid.net/forum/sc2-strategy/446530-rapid-fire-hotkey-trick Rapid Fire] Hotkeys are implemented in those hotkeys settings.<br />
<br />
==== Rapid Fire Hotkey throughput ====<br />
[[Xorg]] keyboard autorepeat can be modified. It may make sense to reduce delay before autorepeat starts (default=660 [ms]). Increasing a bit the repeat rate (default=25 [/s]) is a trade-off: speed vs accuracy.<br />
<br />
To apply the settings:<br />
$ xset r rate <delay_to_activate_in_ms> <nb_of_repeats_per_second><br />
<br />
{{Tip| {{ic|xset r rate}} get X back to default autorepeat settings}}<br />
{{Tip| {{ic|xset q}} let you know the current X settings}}<br />
<br />
==== Enable double-key Rapid Fire Hotkey behaviour ====<br />
Fancy double-key Rapid Fire Trick are not possible by default for Linux.<br />
The [https://git.framasoft.org/bobo/xkb_repeat/tree/master xkb_repeat] git project may help you unlock this behaviour, providing patches to recompile your X server.<br />
<br />
==== Enable CapsLock as a Rapid Fire Hotkey ====<br />
TheCore and TheCore Lite hotkeys rely on CapsLock to be a rapid fire hotkey.<br />
This does not work by default under Linux.<br />
To make it work, CapsLock key could be remapped to another key with [[xmodmap]].<br />
Hereafter an example with "!" character that cannot be used by Starcraft2 in any case.<br />
$ xmodmap -e "remove Lock = Caps_Lock" -e "keycode 66 = exclam"<br />
<br />
The .SC2Hotkeys file would need to be modified, to take it into account to add "!" as an alternate wherever CapsLock is used<br />
$ sed -i -e "s:CapsLock:CapsLock,OEM8:g" <file>.SC2Hotkeys<br />
<br />
{{Tip| {{ic|1= xmodmap -e "add Lock = Caps_Lock" -e "keycode 66 = Caps_Lock" }} to get back to default CapsLock behavior}}<br />
<br />
==== Enable Scrollclick ====<br />
Some scrollclick demo videos:<br />
* [https://www.youtube.com/watch?v=7pQKnS1CPEQ infestor spawning infested terran]<br />
* [https://www.youtube.com/watch?v=9aPd8_9_vB4 scrollclick applied to protoss]<br />
Using [[Xmodmap#Reverse_scrolling|Xmodmap]], it possible to set your regular 3-buttons mouse with scroll wheel to practice scrollclick.<br />
First change scroll fonction to "forward mouse button" and "back mouse button":<br />
$ xmodmap -e "pointer = 1 2 3 8 9 6 7 4 5"<br />
Then add alternate key SCII hotkeys for:<br />
* Global=>Unit Management=>Choose Ability or AI target<br />
* Global=>Unit Management=>Smart Command<br />
{{Tip|{{ic|1=xmodmap -e "pointer = default"}} resets to default mouse functionality}}<br />
<br />
== Troubleshooting ==<br />
<br />
* For some, in-game resolution changing does not work. Editing 'width=x' and 'height=y' in Variables.txt in My Documents/Starcraft II solves this issue. Replace x and y with the prefered resolution.<br />
* Should you experience graphics problems (no 3D background in menu, blue non-texturized units and other glitches), launch the game without Battle.net App (see above) like this: <code>force_s3tc_enable=true wine SC2Switcher.exe</code>. You can also add this option to the .desktop entry in ~/.local/share/applications/wine/Programs/StarCraft II, or edit your <code>~/.drirc</code> file to enable this setting permanently for all apps. Using {{Pkg|driconf}}, you may just enable this setting with a simple GUI.<br />
<br />
== See also ==<br />
<br />
* [https://appdb.winehq.org/objectManager.php?sClass=application&iId=11123 StarCraft II] (WineHQ AppDB)<br />
* [http://bugs.winehq.org/show_bug.cgi?id=23806 StarCraft II crashes because of ACCESS_VIOLATION before the loading screen] (WineHQ bug tracking database)<br />
* [http://bugs.winehq.org/show_bug.cgi?id=23323 World of Warcraft crashes upon login after 3.3.5 patch.] (WineHQ bug tracking database)<br />
* [https://bbs.archlinux.org/viewtopic.php?id=101822 starcraft2 crashing on loading] (Arch Linux forums)<br />
* [https://bbs.archlinux.org/viewtopic.php?id=103354 starcraft2 fails to update to patch 1.03] (Arch Linux forums)<br />
* [http://eu.battle.net/sc2/en/forum/topic/283440977 Patch News] (battle.net EU forums)</div>Sirrus233https://wiki.archlinux.org/index.php?title=Pipelight&diff=304569Pipelight2014-03-15T03:09:05Z<p>Sirrus233: Removed mention of the _wineprefix variable, since this no longer exists in the PKGBUILD and its functionality is deprecated.</p>
<hr />
<div>[[Category:Web Browser]]<br />
[[ja:Pipelight]]<br />
{{Related articles start}}<br />
{{Related|Wine}}<br />
{{Related|Moonlight}}<br />
{{Related|Firefox}}<br />
{{Related articles end}}<br />
Description from the [https://launchpad.net/pipelight/ Launchpad page]:<br />
<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.''"<br />
<br />
Description from the [http://fds-team.de/cms/articles/2013-08/pipelight-using-silverlight-in-linux-browsers.html author's blog]:<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...''"<br />
<br />
==Installation==<br />
<br />
{{AUR|pipelight}} is not presently available in the [[Official repositories]], and will need to be installed from the [[AUR]].<br />
<br />
====Location of wine-silverlight (optional)====<br />
The location of the [[AUR|wine-silverlight]] dependency is customizable in the PKGBUILD. Please refer to the [[#Custom variables]] section below for details.<br />
<br />
{{Tip|Pipelight (along with ''wine-compholio'') can alternatively be installed from the [[Unofficial_user_repositories#pipelight|[pipelight]]] repository, maintained by the Pipelight developers.}}<br />
<br />
==Post Install==<br />
<br />
===User Agent===<br />
Since sites like Netflix refuse to stream on a Linux browser, the user agent may have to be [https://answers.launchpad.net/pipelight/+faq/2351 changed].<br />
<br />
===Verification===<br />
There is a test page available [http://bubblemark.com/sl3/TestPage.html here]. Alternatively, detected plugins can be listed in {{ic|about:plugins}}.<br />
<br />
===GPU Acceleration===<br />
GPU acceleration is enabled by default on verified systems and pages that require it: https://answers.launchpad.net/pipelight/+faq/2364.<br />
<br />
For 1080p streaming, try (needs {{ic|1=enableGPUAcceleration=true}}): http://www.iis.net/media/experiencesmoothstreaming1080p.<br />
<br />
==Custom variables==<br />
The selection of custom variables found in Wine-Silverlight and Pipelight are as following:<br />
* {{AUR|wine-Silverlight}}<br />
# {{ic|customprefix}}<br />
#* Installs Wine to {{ic|/opt}} instead of {{ic|/usr}} (to not conflict with {{pkg|wine}}).<br />
# {{ic|_prefix}}<br />
#* Allows setting a custom location. <br />
* {{AUR|pipelight}}<br />
# {{ic|_prefix}}<br />
#* Allows setting a custom location. Default is {{ic|/usr}}.<br />
# {{ic|_wine}}<br />
#* Location of Wine-Silverlight. <br />
<br />
For example, to install Wine-Silverlight in {{ic|/opt}}:<br />
* '''wine-silverlight:''' set {{ic|1=customprefix=1}}.<br />
* '''pipelight''': set {{ic|1=_wine=/opt/wine-silverlight}}.<br />
<br />
{{Warning|Failure to do this in the PKGBUILD will result in the files having to be modified manually.}}<br />
<br />
==Troubleshooting==<br />
Known issues and solutions are often listed in the [https://answers.launchpad.net/pipelight/+faqs Pipelight FAQ].<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>Sirrus233https://wiki.archlinux.org/index.php?title=Pipelight&diff=304568Pipelight2014-03-15T03:07:34Z<p>Sirrus233: Removed claim that WINEPREFIX can be customized in the PKGBUILD, as this is no longer true.</p>
<hr />
<div>[[Category:Web Browser]]<br />
[[ja:Pipelight]]<br />
{{Related articles start}}<br />
{{Related|Wine}}<br />
{{Related|Moonlight}}<br />
{{Related|Firefox}}<br />
{{Related articles end}}<br />
Description from the [https://launchpad.net/pipelight/ Launchpad page]:<br />
<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.''"<br />
<br />
Description from the [http://fds-team.de/cms/articles/2013-08/pipelight-using-silverlight-in-linux-browsers.html author's blog]:<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...''"<br />
<br />
==Installation==<br />
<br />
{{AUR|pipelight}} is not presently available in the [[Official repositories]], and will need to be installed from the [[AUR]].<br />
<br />
====Location of wine-silverlight (optional)====<br />
The location of the [[AUR|wine-silverlight]] dependency is customizable in the PKGBUILD. Please refer to the [[#Custom variables]] section below for details.<br />
<br />
{{Tip|Pipelight (along with ''wine-compholio'') can alternatively be installed from the [[Unofficial_user_repositories#pipelight|[pipelight]]] repository, maintained by the Pipelight developers.}}<br />
<br />
==Post Install==<br />
<br />
===User Agent===<br />
Since sites like Netflix refuse to stream on a Linux browser, the user agent may have to be [https://answers.launchpad.net/pipelight/+faq/2351 changed].<br />
<br />
===Verification===<br />
There is a test page available [http://bubblemark.com/sl3/TestPage.html here]. Alternatively, detected plugins can be listed in {{ic|about:plugins}}.<br />
<br />
===GPU Acceleration===<br />
GPU acceleration is enabled by default on verified systems and pages that require it: https://answers.launchpad.net/pipelight/+faq/2364.<br />
<br />
For 1080p streaming, try (needs {{ic|1=enableGPUAcceleration=true}}): http://www.iis.net/media/experiencesmoothstreaming1080p.<br />
<br />
==Custom variables==<br />
The selection of custom variables found in Wine-Silverlight and Pipelight are as following:<br />
* {{AUR|wine-Silverlight}}<br />
# {{ic|customprefix}}<br />
#* Installs Wine to {{ic|/opt}} instead of {{ic|/usr}} (to not conflict with {{pkg|wine}}).<br />
# {{ic|_prefix}}<br />
#* Allows setting a custom location. <br />
* {{AUR|pipelight}}<br />
# {{ic|_prefix}}<br />
#* Allows setting a custom location. Default is {{ic|/usr}}.<br />
# {{ic|_wine}}<br />
#* Location of Wine-Silverlight. <br />
# {{ic|_wineprefix}}<br />
#* Allows changing {{ic|WINEPREFIX}}. Default is {{ic|~/.wine-pipelight}}.<br />
<br />
For example, to install Wine-Silverlight in {{ic|/opt}}:<br />
* '''wine-silverlight:''' set {{ic|1=customprefix=1}}.<br />
* '''pipelight''': set {{ic|1=_wine=/opt/wine-silverlight}}.<br />
<br />
{{Warning|Failure to do this in the PKGBUILD will result in the files having to be modified manually.}}<br />
<br />
==Troubleshooting==<br />
Known issues and solutions are often listed in the [https://answers.launchpad.net/pipelight/+faqs Pipelight FAQ].<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>Sirrus233