https://wiki.archlinux.org/api.php?action=feedcontributions&user=JKAbrams&feedformat=atomArchWiki - User contributions [en]2024-03-19T11:11:59ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=KDE&diff=373307KDE2015-05-10T21:34:27Z<p>JKAbrams: spelling</p>
<hr />
<div>[[Category:KDE]]<br />
[[cs:KDE]]<br />
[[de:KDE]]<br />
[[es:KDE]]<br />
[[fr:KDE]]<br />
[[it:KDE]]<br />
[[ja:KDE]]<br />
[[pl:KDE]]<br />
[[ru:KDE]]<br />
[[tr:KDE_Masaüstü_Ortamı]]<br />
[[zh-CN:KDE]]<br />
[[zh-TW:KDE]]<br />
{{Related articles start}}<br />
{{Related|Desktop environment}}<br />
{{Related|Display manager}}<br />
{{Related|Window manager}}<br />
{{Related|Plasma}}<br />
{{Related|Qt}}<br />
{{Related|KDM}}<br />
{{Related|KDevelop 4}}<br />
{{Related|Uniform Look for Qt and GTK Applications}}<br />
{{Related articles end}}<br />
<br />
From [http://www.kde.org/community/whatiskde/softwarecompilation.php KDE Software Compilation] and [http://www.kde.org/download/ Getting KDE Software]:<br />
<br />
:The KDE Software Compilation is the set of frameworks, workspaces, and applications produced by KDE to create a beautiful, functional and free desktop computing environment for Linux and similar operating systems. It consists of a large number of individual applications and a desktop workspace as a shell to run these applications.<br />
<br />
The KDE upstream has a well maintained [http://userbase.kde.org/ UserBase wiki]. Users can get detailed information about most KDE applications there.<br />
<br />
{{note| The term "KDE Software Compilation" is now outdated. KDE is moving to a new way of organizing itself, see: [[Plasma]].}}<br />
== Installation ==<br />
<br />
Before installing KDE, make sure you have a working [[Xorg]] installation on your system.<br />
<br />
Starting in 2014, the KDE project has changed the way it names and organizes itself. There is no KDE Software Compilation anymore, the project is now split into different products with their own names, version numbering and development cycles including: Frameworks (KDE libraries), Plasma (the workspace) and Applications (built on top of KDE libraries). <br />
<br />
=== Plasma 5 ===<br />
<br />
See [[Plasma]].<br />
<br />
=== KDE 4 Workspace ===<br />
<br />
To get the KDE4 version of the Plasma Desktop, install the {{Pkg|kdebase-workspace}} package and, optionally, the {{Pkg|kdebase-plasma}} package (folder view applet) and the {{Grp|kdeplasma4-addons}} and {{Grp|kdeartwork}} groups for additional plasmoids and artwork. Note that the KDE4 Plasma Desktop is currently in maintenance mode, and is expected to reach EOL in August 2015.<br />
<br />
=== KDE Applications ===<br />
<br />
To install the full set of KDE Applications, use the {{Grp|kde-applications}} group, or the {{Grp|kde-applications-meta}} meta-packages to install specific modules. Note that this will only install Applications, it will not install any version of the Plasma Desktop.<br />
<br />
==== Language pack ====<br />
<br />
If you need language files, install {{ic|kde-l10n-yourlanguagehere}} (e.g. {{Pkg|kde-l10n-de}} for the German language).<br />
<br />
For a full list of available languages see [https://www.archlinux.org/packages/extra/any/kde-l10n/ this link].<br />
<br />
== Starting Plasma ==<br />
See [[Plasma#Starting Plasma]].<br />
<br />
== Configuration ==<br />
<br />
All KDE 4 configurations are saved in the {{ic|~/.kde4}} folder, otherwise {{ic|~/.config}} is used. If KDE is giving you a lot of trouble or if you ever want a fresh installation of KDE, just backup and rename this folder and restart your X session. KDE will re-create it with all the default configuration files. If you want very fine-grained control over KDE programs, you may want to edit the files in this folder.<br />
<br />
However, configuring KDE is primarily done in '''System Settings'''. A few other options for the desktop are available in '''Default Desktop Settings''' in the desktop's context menu.<br />
<br />
For other personalization options not covered below such as activities, different wallpapers on one cube, etc., please refer to the [[Plasma]] wiki page.<br />
<br />
=== Personalization ===<br />
<br />
How to set up the KDE desktop to your personal style: use different Plasma themes, window decorations and icon themes.<br />
{{tip|1=Applications using the new frameworks 5 use the same configurations as under the old kdebase-workspace 4 but read from new locations. To allow frameworks 5 applications running in kdebase-workspace 4 to share the same configurations they may be moved to the new locations and symlinked back to the old. Examples are:<br />
*Konsole profiles from ~/.kde4/share/apps/konsole to ~/.local/share/konsole/<br />
*Application appearance from ~/.kde4/share/config/kdeglobals to ~/.config/kdeglobals<br />
This information was gathered from the [https://bbs.archlinux.org/viewforum.php?id=18 Applications & Desktop Environments] section of the forums. }}<br />
<br />
==== Plasma desktop ====<br />
<br />
===== Themes =====<br />
See [[Plasma#Themes]]<br />
<br />
===== Widgets =====<br />
<br />
Plasmoids are little scripted (plasmoid scripts) or coded (plasmoid binaries) KDE applications designed to enhance the functionality of your desktop.<br />
<br />
Plasmoid binaries can be installed using PKGBUILDs from [https://aur.archlinux.org/packages.php?O=0&K=plasmoid&do_Search=Go&PP=25&SO=d&SB=v AUR], or you can write your own PKGBUILD.<br />
<br />
The easiest way to install plasmoid scripts is by right-clicking onto a panel or the desktop:<br />
<br />
Add Widgets > Get new Widgets > Download Widgets<br />
<br />
This will present a nice frontend for [http://www.kde-look.org/ kde-look.org] that allows you to install, uninstall, or update third-party plasmoid scripts with literally just one click.<br />
<br />
Most plasmoids are not created officially by KDE developers. You can also try installing Mac OS X widgets, Microsoft Windows Vista/7 widgets, Google Widgets, and even SuperKaramba widgets.<br />
<br />
===== Sound applet in the system tray =====<br />
<br />
Install Kmix ({{Pkg|kdemultimedia-kmix}} for KDE 4, or {{Pkg|kmix}} for Plasma 5) from the official repositories and start it from the application launcher. Since KDE, by default, autostarts programs from the previous session, it does not need to be started manually upon every login.<br />
<br />
{{Note|1=To adjust the [https://bugs.kde.org/show_bug.cgi?id=313579#c28 step size of volume increments/decrements], add e.g. {{ic|1=VolumePercentageStep=1}} in the {{ic|[Global]}} section of {{ic|~/.kde4/share/config/kmixrc}}}}<br />
<br />
===== Adding a Global Menu to the desktop =====<br />
<br />
Install {{Pkg|appmenu-qt}} from the official repositories and {{AUR|appmenu-gtk}} and {{AUR|appmenu-qt5}} from the AUR in order to complete the preliminaries for a Mac OS X style always-on global menu. To get Firefox and LibreOffice to use the global menu as well, install {{AUR|firefox-extension-globalmenu}}{{Broken package link|package not found}} and {{AUR|libreoffice-extension-menubar}} from the AUR.<br />
<br />
{{Note|<br />
* {{AUR|appmenu-gtk}} is orphaned and Canonical has abandoned appmenu-gtk in favor of unity-gtk-module that is depending on Unity desktop. As of October 2014 there is no way of exporting gtk2,3 menus in KDE.<br />
* Install {{AUR|firefox-ubuntu}}, available in the AUR, which has Canonical's patch for getting the global menu to work with the current version of Firefox (as of November 2013).<br />
}}<br />
<br />
To actually get the global menu, install {{AUR|kdeplasma-applets-menubar}} from the AUR. Create a plasma-panel on top of your screen and add the window menubar applet to the panel. To export the menus to your global menu, go to ''System Settings > Application Appearance > Style''. Now click the fine-tuning tab and use the drop-down list to select ''only export'' as your menubar style.<br />
<br />
===== Disable panel shadow =====<br />
<br />
As the plasma panel is on top of other windows, its shadow is drawn over them. [https://bbs.archlinux.org/viewtopic.php?pid=1228394#p1228394] To disable this behaviour without impacting other shadows, [[install]] {{Pkg|xorg-xprop}} and run:<br />
<br />
$ xprop -remove _KDE_NET_WM_SHADOW<br />
<br />
then select the panel with the plus-sized cursor. [https://forum.kde.org/viewtopic.php?f=285&t=121592] For automation, install {{Pkg|xorg-xwininfo}} and create the following script:<br />
<br />
{{hc|/usr/local/bin/kde-no-shadow|<nowiki><br />
#!/bin/bash<br />
for WID in $(xwininfo -root -tree | sed '/"plasma-desktop": ("Plasma" "Plasma")/!d; s/^ *\([^ ]*\) .*/\1/g'); do<br />
xprop -id $WID -remove _KDE_NET_WM_SHADOW<br />
done<br />
</nowiki>}}<br />
<br />
The script can be run on login with ''Add Script'' in ''Autostart'':<br />
<br />
$ kcmshell4 autostart<br />
<br />
==== Window decorations ====<br />
<br />
[http://kde-look.org/index.php?xcontentmode=75 Window decorations] can be changed in:<br />
System Settings > Workspace Appearance > Window Decorations<br />
There you can also directly download and install more themes with one click, and some are available in the [https://aur.archlinux.org/packages.php?O=0&K=kdestyle&do_Search=Go&PP=25&SO=d&SB=v AUR].<br />
<br />
==== Icon themes ====<br />
<br />
Not many full system icons themes are available for KDE 4. You can open up ''System Settings > Application Appearance > Icons'' and browse for new ones or install them manually. Many of them can be found on [http://www.kde-look.org/ kde-look.org].<br />
<br />
Official logos, icons, CD labels and other artwork for Arch Linux are provided in the {{AUR|archlinux-artwork}} package. After installing you can find such artwork at {{ic|/usr/share/archlinux/}}.<br />
<br />
===== Qt 5 icons theme =====<br />
<br />
If you are on Plasma 5, use ''System Settings > Icons''.<br />
While if you are on KDE 4 use {{ic|kcmshell5 icons}} to set the icons theme.<br />
<br />
==== Fonts ====<br />
<br />
===== Fonts in KDE look poor =====<br />
<br />
Try installing the {{Pkg|ttf-dejavu}} and {{Pkg|ttf-liberation}} packages.<br />
<br />
After the installation, be sure to log out and back in. You should not have to modify anything in ''System Settings > Fonts''.<br />
<br />
If you have personally set up how your [[Fonts]] render, be aware that System Settings may alter their appearance. When you go ''System Settings > Appearance > Fonts'', System Settings will likely alter your font configuration file ({{ic|fonts.conf}}).<br />
<br />
There is no way to prevent this, but, if you set the values to match your {{ic|fonts.conf}} file, the expected font rendering will return (it will require you to restart your application or in a few cases restart your desktop). Note that Gnome's Font Preferences also does this.<br />
<br />
===== Fonts are huge or seem disproportional =====<br />
<br />
Try to force font DPI to '''96''' in ''System Settings > Application Appearance > Fonts''.<br />
<br />
If that does not work, try setting the DPI directly in your Xorg configuration as documented [[Xorg#Setting_DPI_manually|here]].<br />
<br />
==== Space efficiency ====<br />
<br />
Users with small screens (e.g. netbooks) can change some setting to make KDE more space efficient. See the [http://userbase.kde.org/KWin#Using_with_small_screens_(eg_Netbooks) upstream wiki] for more information. Also, you can use [http://www.kde.org/workspaces/plasmanetbook/ KDE's Plasma Netbook] which is a workspace made specifically for small, lightweight netbook devices.<br />
<br />
=== Networking ===<br />
<br />
You can choose from the following tools:<br />
* NetworkManager. See [[NetworkManager#KDE|NetworkManager]] for more information.<br />
* Wicd. See [[Wicd]] for more information.<br />
<br />
=== Printing ===<br />
<br />
{{Tip|Use the [[CUPS]] web interface for faster configuration. Printers configured in this way can be used in KDE applications. }}<br />
<br />
You can also configure printers in ''System Settings > Printer Configuration''. To use this method, you must first install {{Pkg|print-manager}} and {{Pkg|cups}}.<br />
<br />
The {{ic|avahi-daemon}} and {{ic|cupsd}} daemons must be started first; otherwise, you will get the following error:<br />
The service 'Printer Configuration' does not provide an interface 'KCModule'<br />
with keyword 'system-config- printer-kde/system-config-printer-kde.py'<br />
The factory does not support creating components of the specified type.<br />
<br />
If you are getting the following error, you need to give your user the right to manage printers.<br />
There was an error during CUPS operation: 'cups-authorization-canceled'<br />
<br />
For CUPS, this is set in {{ic|/etc/cups/cups-files.conf}}.<br />
<br />
Adding {{ic|lpadmin}} to {{ic|/etc/group}} and then to the {{ic|SystemGroup}} directive in {{ic|/etc/cups/cups-files.conf}} allows anyone in the {{ic|lpadmin}} group to configure printers. Do ''not'' add the {{ic|lp}} group to the {{ic|SystemGroup}} directive, or printing will fail.<br />
<br />
# groupadd -g107 lpadmin<br />
<br />
{{hc|/etc/cups/cups-files.conf|# Administrator user group...<br />
SystemGroup sys root lpadmin}}<br />
<br />
{{Tip|Read [[CUPS#CUPS administration]] to get more details on how to configure CUPS.}}<br />
<br />
=== Samba/Windows support ===<br />
<br />
If you want to have access to Windows services, install [[Samba]] (package {{Pkg|samba}}).<br />
<br />
The Dolphin share functionality requires usershares, which the stock smb.conf does not have enabled. Instructions to add them are in [[Samba#Creating_user_share_path|the Samba article]], after which sharing in Dolphin should work out of the box after restarting Samba.<br />
<br />
=== KDE Desktop activities ===<br />
<br />
KDE Desktop Activities are Plasma-based virtual-desktop-like sets of Plasma Widgets where you can independently configure widgets as if you have more than one screen or desktop.<br />
<br />
On your desktop, click the Cashew Plasmoid and, on the pop-up window, press "Activities".<br />
<br />
A plasma bar presenting you the current existing Plasma Desktop Activities will appear at the bottom of the screen. You can navigate between them by pressing the correspondent icons.<br />
<br />
=== Power saving ===<br />
<br />
KDE has an integrated power saving service called "'''Powerdevil Power Management'''" that may adjust the power saving profile of the system and/or the brightness of the screen (if supported).<br />
<br />
Since KDE 4.6, CPU frequency scaling is no longer managed by KDE. Instead it is assumed to be handled automatically by the the hardware and/or kernel. Arch has used {{ic|ondemand}} as the default CPU frequency governor since kernel version 3.3, so no additional configuration is needed in most cases. For details on fine-tuning the governor, see [[CPU frequency scaling]].<br />
<br />
=== Monitoring changes on local files and directories ===<br />
<br />
KDE now uses '''inotify''' directly from the kernel with '''kdirwatch''' (included in kdelibs), so Gamin or FAM are no longer needed. You may want to install this {{AUR|kdirwatch}} from AUR which is a GUI frontend for kdirwatch.<br />
<br />
== System administration ==<br />
<br />
=== Set keyboard ===<br />
<br />
Navigate to:<br />
System Settings > Hardware > Input Devices > Keyboard<br />
In the first tab, you can choose your keyboard model.<br />
<br />
In the "'''Layouts'''" tab, you can choose the languages you may want to use by pressing the "Add Layout" button and subsequently choosing the variant and the language.<br />
<br />
In the "'''Advanced'''" tab, you can choose the keyboard combination you want in order to change the layouts in the "Key(s) to change layout" sub-menu.<br />
<br />
=== Terminate Xorg server through KDE system settings ===<br />
<br />
Navigate to the submenu:<br />
System Settings > Input Devices > Keyboard > Advanced (tab) > "Key Sequence to kill the X server"<br />
and tick the checkbox.<br />
<br />
=== KCM ===<br />
<br />
KCM stands for '''KC'''onfig '''M'''odule. KCMs can help you configure your system by providing interfaces in System Settings.<br />
<br />
'''Configuration for look and feel of GTK applications.'''<br />
* {{Pkg|kde-gtk-config}}<br />
* {{AUR|kcm-gtk}}<br />
* {{AUR|kcm-qt-graphicssystem}}<br />
<br />
'''Configuration for the GRUB bootloader.'''<br />
* {{AUR|grub2-editor}}<br />
<br />
'''Configuration for Synaptics touchpads.'''<br />
* {{Pkg|kcm-touchpad}}<br />
* {{Pkg|kcm-touchpad-frameworks}}{{Broken package link|replaced by {{Pkg|plasma-desktop}}}} (Plasma 5)<br />
* {{AUR|synaptiks}}{{Broken package link|package not found}}<br />
* {{AUR|kcm_touchpad}}<br />
* {{AUR|kcm-touchpad-git}}{{Broken package link|package not found}}<br />
<br />
'''Configuration for the [[Uncomplicated Firewall]] (UFW)'''<br />
* {{AUR|kcm-ufw}}<br />
<br />
'''Configuration for [[PolicyKit]]'''<br />
* {{AUR|kcm-polkit-kde-git}}<br />
<br />
'''Configuration for Wacom tablets'''<br />
* {{AUR|kcm-wacomtablet}}<br />
<br />
'''Configuration for systemd'''<br />
* {{Pkg|kcmsystemd}} (Plasma 5)<br />
<br />
More KCMs can be found at [http://kde-apps.org/index.php?xcontentmode=273 kde-apps.org].<br />
<br />
===Auto Login===<br />
Go to ''System Settings > System Administration > Login Screen > Convenience'', check ''Enable Auto-Login'' box and select user.<br />
<br />
== Desktop search and semantic desktop ==<br />
<br />
According to [[wikipedia:Semantic_desktop|Wikipedia]]:<br />
:''"the Semantic Desktop is a collective term for ideas related to changing a computer's user interface and data handling capabilities so that data is more easily shared between different applications or tasks and so that data that once could not be automatically processed by a computer can be (automatically processed)."''<br />
<br />
The KDE implementation of this concept is tied to (as of KDE Applications 4.13) two major pieces of software: Akonadi and Baloo. Between the two of them, these programs look at your data and make an easily searchable index of it. The idea behind these pieces of software is to make your system "aware" of your data and give it context using meta-data and user-supplied tags. Baloo uses Xapian to store its data.<br />
<br />
=== Baloo ===<br />
<br />
==== Using and configuring Baloo ====<br />
<br />
In order to search using Baloo on the KDE Plasma Desktop, press {{ic|ALT+F2}} and type in your query. Within Dophin press {{ic|CTRL+F}}.<br />
<br />
By default the Desktop Search KCM exposes only two options: A panel to blacklist folders and, as of 4.13.1, a way to disable it with one click.<br />
<br />
Alternatively you can edit your {{ic|~/.kde4/share/config/baloofilerc}} (KDE4) or {{ic|~/.config/baloofilerc}} (KF5) file ([https://community.kde.org/Baloo/Configuration info]). Additionally the {{ic|balooctl}} process can also be used. In order to disable Baloo run {{ic|balooctl disable}}.<br />
<br />
Once you added additional folders to the blacklist or disabled Baloo entirely, a process named {{ic|baloo_file_cleaner}} removes all unneeded index files automatically. They are stored under {{ic|~/.local/share/baloo/}}.<br />
<br />
More advanced configuration options are available through {{AUR|kcm_baloo_advanced}}.<br />
<br />
==== How do I index a removable device? ====<br />
<br />
By default every removable device is blacklisted. You just have to remove your device from the blacklist in the KCM panel.<br />
<br />
=== Akonadi ===<br />
<br />
Akonadi is a system meant to act as a local cache for PIM data, regardless of its origin, which can be then used by other applications. This includes the user's emails, contacts, calendars, events, journals, alarms, notes, and so on.<br />
<br />
Akonadi does not store any data by itself: the storage format depends on the nature of the data (for example, contacts may be stored in vCard format).<br />
<br />
==== Disabling Akonadi ====<br />
<br />
See this [http://userbase.kde.org/Akonadi#Disabling_the_Akonadi_subsystem section in the KDE userbase]. Alternatively, install {{AUR|akonadi-fake}} from the [[AUR]].<br />
<br />
==== Database configuration ====<br />
<br />
Start {{ic|akonaditray}} from package {{Pkg|kdepim-runtime}}. Right click on it and select '''configure'''. In the Akonadi server configure tab, you can:<br />
* Configuring Akonadi to use MySQL/MariaDB Server<br />
** If your home directory is on a ZFS pool, you will need to create {{ic|~/.config/akonadi/mysql-local.conf}} with the following contents:<br />
<br />
[mysqld]<br />
innodb_use_native_aio = 0<br />
<br />
Otherwise you will get the [[MySQL#OS error 22 when running on ZFS|OS error 22]]<br />
* Configuring Akonadi to use PostgreSQL Server<br />
* Configuring Akonadi to use SQLite<br />
** Edit {{ic|~/.config/akonadi/akonadiserverrc}} to match the below<br />
<br />
[General]<br />
Driver=QSQLITE3<br />
<br />
[QSQLITE3]<br />
Name=/home/username/.local/akonadi/akonadi.db<br />
<br />
== Phonon ==<br />
<br />
From [[Wikipedia:Phonon|Wikipedia]]:<br />
<br />
:''"Phonon is the multimedia API for KDE 4. Phonon was created to allow KDE 4 to be independent of any single multimedia framework such as GStreamer or xine and to provide a stable API for KDE 4's lifetime. It was done for various reasons: to create a simple KDE/Qt style multimedia API, to better support native multimedia frameworks on Windows and Mac OS X, and to fix problems of frameworks becoming unmaintained or having API or ABI instability."''<br />
<br />
'''Phonon''' is being widely used within KDE, for both audio (e.g., the System notifications or KDE audio apps) and video (e.g., the Dolphin video thumbnails).<br />
<br />
=== Which backend should I choose? ===<br />
<br />
You can choose between various backends like [[GStreamer]] ({{Pkg|phonon-qt4-gstreamer}}, {{Pkg|phonon-qt5-gstreamer}}) or [[VLC]] ({{Pkg|phonon-qt4-vlc}}, {{Pkg|phonon-qt5-vlc}}), available in the [[official repositories]], and [[MPlayer]] ({{AUR|phonon-qt4-mplayer-git}}), QuickTime ({{AUR|phonon-quicktime-git}}) or [http://martinsandsmark.wordpress.com/2012/07/07/akademy/ AVKode] ({{AUR|phonon-avkode-git}}), available in the [[AUR]].<br />
<br />
Most users will want VLC which has the best upstream support. GStreamer is currently not well maintained. Note that multiple backends can be installed at once and chosen at ''System Settings > Multimedia > Phonon > Backend''.<br />
<br />
{{Note|<br />
* According to the [http://community.kde.org/Phonon/FeatureMatrix Feature Matrix], the GStreamer backend has some more features that the VLC backend.<br />
* According to the [http://userbase.kde.org/Phonon#Backend_libraries KDE UserBase], Phonon-MPlayer is currently unmaintained.}}<br />
<br />
== Useful applications ==<br />
<br />
The official set of KDE applications may be found [http://www.kde.org/applications/ here].<br />
<br />
=== Yakuake ===<br />
<br />
[[Yakuake]] provides a Quake-like terminal emulator whose visibility is toggled by the F12 key. It also has support for multiple tabs. Yakuake is available in the package {{Pkg|yakuake}}.<br />
<br />
=== KDE Telepathy ===<br />
<br />
[http://community.kde.org/KTp KDE Telepathy] is a project with the goal to closely integrate Instant Messaging with the KDE desktop. It utilizes the Telepathy framework as a backend and is intended to replace Kopete.<br />
<br />
To install all Telepathy protocols, install the {{Grp|telepathy}} group.<br />
To use the KDE Telepathy client, install the {{Pkg|telepathy-kde-meta}} package that includes all the packages contained in the {{Grp|kde-telepathy}}{{Broken package link|package not found}} group.<br />
<br />
==== Use Telegram with KDE Telepathy ====<br />
<br />
Telegram protocol is avaible using {{pkg|telepathy-haze}}, installing {{aur|telegram-purple}} or {{aur|telegram-purple-git}}. The username is the Telegram account telephone number (complete with the national prefix '+xx', e.g. '+39' for Germany). The configuration though the GUI may be tricky: if the phone number is not accepted when configuring a new account in the KDE Telepathy client (with an error message complaining about an invalid parameter which prevents the account creation), insert it between single quotes and then remove the quotes manually from the configuration file (<code>~/.local/share/telepathy/mission-control/accounts.cfg</code>) after the account creation (if the quotes are not removed after, an authentication error should rise). Note that the configuration file should be edited manually when KDE Telepathy is not running, e.g. when there is no KDE desktop session active, otherwise manual changes may be overwritten by the software.<br />
<br />
== Tips and tricks ==<br />
<br />
=== Using an alternative window manager in KDE ===<br />
<br />
To use an alternative [[window manager]] with KDE open the ''System Settings'' panel, navigate to ''Default Applications > Window Manager > Use a different window manager'' and select the window manager you wish to use from the list.<br />
<br />
==== KDE/Openbox Session ====<br />
<br />
The {{Pkg|openbox}} package provides a session for using KDE with [[Openbox]]. To make use of this session, select ''KDE/Openbox'' from the [[display manager]] menu.<br />
<br />
For those starting the session manually, add the following line to your {{ic|.xinitrc}} file:<br />
exec openbox-kde-session<br />
<br />
==== Compiz custom ====<br />
<br />
If you need to run Compiz with custom options and switches select ''Compiz custom'' and then create a script called {{ic|compiz-kde-launcher}} and add to it the commands you wish to use to start Compiz. See the example below:<br />
<br />
{{hc|/usr/local/bin/compiz-kde-launcher|<nowiki><br />
#!/bin/bash<br />
LIBGL_ALWAYS_INDIRECT=1<br />
compiz --replace &<br />
wait<br />
</nowiki>}}<br />
<br />
Then make it executable:<br />
$ chmod +x /usr/local/bin/compiz-kde-launcher<br />
<br />
==== Re-enabling compositing effects ====<br />
<br />
When replacing Kwin with a window manager which does not provide a Compositor (such as Openbox), any desktop compositing effects e.g. transparency will be lost. In this case, install and run a separate Composite manager to provide the effects such as [[Xcompmgr]] or [[Compton]].<br />
<br />
=== Integrate Android with the KDE Desktop ===<br />
<br />
KDE connect provides several features for you:<br />
* Share files and URLs to/from KDE from/to any app, without wires.<br />
* Touchpad emulation: Use your phone screen as your computer's touchpad.<br />
* Notifications sync (4.3+): Read your Android notifications from the desktop.<br />
* Shared clipboard: copy and paste between your phone and your computer.<br />
* Multimedia remote control: Use your phone as a remote for Linux media players.<br />
* WiFi connection: no usb wire or bluetooth needed.<br />
* RSA Encryption: your information is safe.<br />
<br />
You will need to install KDE Connect both on your computer and on your Android. For PC side, install {{Pkg|kdeconnect}} if you are using KDE4 or if you are using Plasma 5, then you should install {{AUR|kdeconnect-git}} instead. For Android side, install {{ic|KDE Connect}} from the [https://play.google.com/store/apps/details?id=org.kde.kdeconnect_tp&hl=en Google Play Store] or from [https://f-droid.org/repository/browse/?fdid=org.kde.kdeconnect_tp F-Droid].<br />
<br />
=== Configure KWin to use OpenGL ES ===<br />
<br />
Beginning with KWin version 4.8 it is possible to use the separately built binary '''kwin_gles''' as a replacement for kwin. It behaves almost the same as the kwin executable in OpenGL2 mode with the slight difference that it uses ''egl'' instead of ''glx'' as the native platform interface. To test kwin_gles you just have to run {{ic|kwin_gles --replace}} in Konsole.<br />
If you want to make this change permanent you have to create a script in {{ic|$(kde4-config --localprefix)/env/}} which exports {{ic|1=KDEWM=kwin_gles}}.<br />
<br />
=== Enabling audio/video thumbnails under Konqueror/Dolphin file managers ===<br />
<br />
For thumbnails of videos in konqueror and dolphin install {{Pkg|kdemultimedia-mplayerthumbs}} or {{Pkg|kdemultimedia-ffmpegthumbs}} and activate the installed package in ''Settings> Configure Konqueror> General> Previews> Video Files''.<br />
For thumbnails of audio files in Konqueror and Dolphin install {{AUR|audiothumbs}} from AUR.<br />
<br />
=== Speed up application startup ===<br />
<br />
User Rob wrote on his blog this "[http://kdemonkey.blogspot.nl/2008/04/magic-trick.html magic trick]" to improve application start-up time by 50-150ms.<br />
To enable it, create this folder in your home:<br />
$ mkdir ~/.compose-cache/<br />
But it can produce freezes on heavy io, can be avoided by:<br />
$ ln -sfv /run/user/$UID/ /home/$USER/.compose-cache<br />
<br />
{{Note|For those curious about what is going on here, this enables an optimization which Lubos (of general KDE speediness fame) came up with some time ago and was then rewritten and integrated into libx11. Ordinarily, on startup, applications read input method information from {{ic|/usr/share/X11/locale/''your locale''/Compose}}. This file is quite long (>5000 lines for the en_US.UTF-8 one) and takes some time to process. libX11 can create a cache of the parsed information which is much quicker to read subsequently, but it will only re-use an existing cache or create a new one in {{ic|~/.compose-cache}} if the directory already exists.}}<br />
<br />
=== Hiding partitions ===<br />
<br />
In Dolphin, it is as simple as right-clicking on the partition in the {{ic|Places}} sidebar and selecting {{ic|Hide ''partition''}}. Otherwise...<br />
<br />
If you wish to prevent your internal partitions from appearing in your file manager, you can create an udev rule, e.g:<br />
<br />
{{hc|/etc/udev/rules.d/10-local.rules|2=<br />
KERNEL=="sda[0-9]", ENV{UDISKS_IGNORE}="1"<br />
}}<br />
<br />
The same thing for a certain partition:<br />
<br />
KERNEL=="sda1", ENV{UDISKS_IGNORE}="1"<br />
KERNEL=="sda2", ENV{UDISKS_IGNORE}="1"<br />
<br />
=== Konqueror tips ===<br />
<br />
==== Disabling Access Keys ====<br />
<br />
Every time you pressing the Ctrl key while browsing, small square tooltips appear for each of the active areas (hyperlinks) on a webpage. This is useful when you browsing with only a keyboard.<br />
<br />
To disable Access Keys, go to ''Settings > Configure Konqueror > Web Browsing'' and uncheck ''Enable Access Key activation with Ctrl key''.<br />
<br />
==== Using WebKit ====<br />
<br />
WebKit is an open source browser engine developed by Apple Inc. It is a derivative from the KHTML and KJS libraries and contains many improvements. WebKit is used by Safari, Google Chrome and rekonq.<br />
<br />
It is possible to use WebKit in Konqueror instead of KHTML. First install the {{Pkg|kwebkitpart}} package.<br />
<br />
Then, after executing Konqueror, navigate to ''Settings > Configure Konqueror > General > Default web browser engine'' and set it as {{ic|WebKit}}.<br />
<br />
=== Firefox integration ===<br />
<br />
See [[Firefox#KDE_integration|Firefox]].<br />
<br />
=== Setting the background for lock screen ===<br />
<br />
In Plasma 5, you can set a custom wallpaper for the lock screen. This is [https://bugs.kde.org/show_bug.cgi?id=312828 not possible] in KDE 4, but here a workaround from OpenSUSE mailing lists: http://lists.opensuse.org/opensuse-kde/2013-02/msg00082.html<br />
<br />
For this you should modify the file {{ic|/usr/share/kde4/apps/ksmserver/screenlocker/org.kde.passworddialog/contents/ui/main.qml}}, replacing a line<br />
<br />
source: theme.wallpaperPathForSize(parent.width, parent.height)<br />
<br />
with something like<br />
<br />
source: "1920x1080.jpg"<br />
<br />
Now you simply put a wallpaper image {{ic|1920x1080.jpg}} to the {{ic|/usr/share/kde4/apps/ksmserver/screenlocker/org.kde.passworddialog/contents/ui}} directory.<br />
<br />
{{Note|You have to redo this for each update of the package {{Pkg|kdebase-workspace}}.}}<br />
<br />
=== Setting lockscreen wallpaper to arbitrary image ===<br />
<br />
Copy an existing wallpaper profile as a template:<br />
$ cp -r /usr/share/wallpapers/''ExistingWallpaper'' ~/.kde4/share/wallpapers/<br />
<br />
Change the name of the directory, and edit {{ic|metadata.desktop}}:<br />
<br />
{{hc|~/.kde4/share/wallpapers/''MyWallpaper''/metadata.desktop|2=<br />
[Desktop Entry]<br />
Name=MyWallpaper<br />
X-KDE-PluginInfo-Name=MyWallpaper<br />
}}<br />
<br />
Remove existing images ({{ic|contents/screenshot.png}} and {{ic|images/*}}):<br />
$ rm ~/.kde4/share/wallpapers/MyWallpaper/contents/screenshot.png<br />
$ rm ~/.kde4/share/wallpapers/MyWallpaper/contents/images/*<br />
<br />
Copy new image in:<br />
$ cp ''path/to/MyWallpaper.png'' MyWallpaper/contents/images/1920x1080.png<br />
<br />
Edit the metadata profile for the current theme:<br />
{{hc|~/.kde4/share/apps/desktoptheme/MyTheme/metadata.desktop|2=<br />
[Wallpaper]<br />
defaultWallpaperTheme=MyWallpaper<br />
defaultFileSuffix=.png<br />
defaultWidth=1920<br />
defaultHeight=1080<br />
}}<br />
<br />
Lock the screen to check that it worked.<br />
<br />
{{Note|This method sets the lockscreen background without changing any system-wide settings. For a system-wide change, create the new wallpaper profile in {{ic|/usr/share/wallpapers}}.}}<br />
<br />
=== Configuring monitor resolution / multiple monitors ===<br />
<br />
To enable display resolution management and multiple monitors in Plasma 5, install {{Pkg|kscreen}}. This adds the additional options to System Settings/Display and Monitor.<br />
<br />
== Troubleshooting ==<br />
<br />
=== Configuration related ===<br />
<br />
Many problems in KDE are related to configuration. One way to resolve upgrade problems is to start over with a fresh KDE config.<br />
<br />
==== Reset all KDE configuration ====<br />
<br />
To test whether your config is the problem try quitting your KDE session by logging out and, in a tty, run<br />
$ cp -r ~/.kde4 ~/.kde4.safekeeping<br />
$ rm .kde4/{cache,socket,tmp}-$(hostname)<br />
<br />
The ''rm'' command just removes symbolic links which will be recreated by KDE automatically. Now start a new KDE session to see the results.<br />
<br />
If the problem is resolved, you will have a fresh, problem-free {{ic|~/.kde4/}}. You can gradually move parts of your saved configuration back, restarting your session regularly to test, to identify the problematic parts of your config. Some files here are named after applications so you will probably be able to test these without needing to restart KDE.<br />
<br />
==== Plasma desktop behaves strangely ====<br />
<br />
Plasma problems are usually caused by unstable '''plasmoids''' or '''plasma themes'''. First, find which was the last plasmoid or plasma theme you had installed and disable it or uninstall it.<br />
<br />
So, if your desktop suddenly exhibits "locking up", this is likely caused by a faulty installed widget. If you cannot remember which widget you installed before the problem began (sometimes it can be an irregular problem), try to track it down by removing each widget until the problem ceases. Then you can uninstall the widget, and file a bug report (bugs.kde.org) '''only if it is an official widget'''. If it is not, it is recommended you find the entry on kde-look.org and inform the developer of that widget about the problem (detailing steps to reproduce, etc).<br />
<br />
If you cannot find the problem, but you do not want ''all'' the KDE settings to be lost, do:<br />
<br />
$ rm -r ~/.kde4/share/config/plasma*<br />
<br />
This command will '''delete all plasma related configs''' of your user and when you will relogin into KDE, you will have the '''default''' settings back. You should know that this action '''cannot be undone'''. You should create a backup folder and copy all the plasma related configs in it.<br />
<br />
==== Clean cache to resolve upgrade problems ====<br />
<br />
The [https://bbs.archlinux.org/viewtopic.php?id=135301 problem] may be caused by old cache. Sometimes after an upgrade, the old cache might introduce strange, hard to debug behaviour such as unkillable shells, hangs when changing various settings and several other problems such as ark being unable to unrar or unzip or amarok not recognizing any of your musics. This solution can also resolve problems with KDE and QT programmes looking bad following upgrade.<br />
<br />
Rebuild your cache with the following commands:<br />
<br />
$ rm ~/.config/Trolltech.conf<br />
$ kbuildsycoca4 --noincremental<br />
<br />
Hopefully, your problems are now fixed.<br />
<br />
=== Clean akonadi configuration to fix KMail ===<br />
<br />
First, make sure that KMail is not running. Then backup configuration:<br />
$ mv ~/.local/share/akonadi ~/.local/share/akonadi-old<br />
$ mv ~/.config/akonadi ~/.config/akonadi-old<br />
<br />
Start ''SystemSettings > Personal'' and remove all the resources. Go back to Dolphin and remove the original {{ic|~/.local/share/akonadi}} and<br />
{{ic|~/.config/akonadi}} - the copies you made ensure that you can back-track if necessary.<br />
<br />
Now go back to the System Settings page and carefully add the necessary resources. You should see the resource reading in your mail folders. Then start Kontact/KMail to see if it work properly.<br />
<br />
=== Getting current state of KWin for support and debug purposes ===<br />
<br />
This command prints out a wonderful summary of the current state of KWin including used options, used compositing backend and relevant OpenGL driver capabilities. See more on [http://blog.martin-graesslin.com/blog/2012/03/on-getting-help-for-kwin-and-helping-kwin/ Martin's blog].<br />
<br />
$ qdbus org.kde.kwin /KWin supportInformation<br />
<br />
=== KDE4 does not finish loading ===<br />
<br />
There might be a situation in which the graphic driver might create a conflict when starting KDE4. This situation happens after the login but before finishing loading the desktop, making the user wait indefinitely at the loading screen. Until now the only users confirmed to be affected by this are the ones that use [[NVIDIA|Nvidia drivers]] and KDE4.<br />
<br />
A solution for Nvidia users:<br />
<br />
{{hc|~/.kde4/share/config/kwinrc|2=<br />
[Compositing]<br />
Enabled=false<br />
}}<br />
For more information, see [https://bbs.archlinux.org/viewtopic.php?pid=932598 this] thread.<br />
<br />
If a minimal install was done, make sure you installed the required font by your phonon backend listed here: [[#Minimal install]]<br />
<br />
=== KDE and Qt programs look bad when in a different window manager ===<br />
<br />
If you are using KDE or Qt programs but not in a full KDE session (specifically, you did not run {{ic|startkde}}), then as of KDE 4.6.1 you will need to tell Qt how to find KDE's styles (Oxygen, QtCurve etc.)<br />
<br />
You just need to set the environment variable {{ic|QT_PLUGIN_PATH}}. E.g. put:<br />
<br />
export QT_PLUGIN_PATH=$HOME/.kde4/lib/kde4/plugins/:/usr/lib/kde4/plugins/<br />
<br />
into your {{ic|/etc/profile}} (or {{ic|~/.profile}} if you do not have root access). {{ic|qtconfig-qt4}}should then be able to find your KDE styles and everything should look nice again!<br />
<br />
Alternatively, you can symlink the Qt styles directory to the KDE styles one:<br />
# ln -s /usr/lib/kde4/plugins/styles/ /usr/lib/qt4/pluginlib32-libdbusmenu-glibs/styles<br />
<br />
Under Gnome you can try to install the package libgnomeui.<br />
<br />
=== Graphical related problems ===<br />
<br />
==== Low 2D desktop performance (or) artifacts appear when on 2D ====<br />
<br />
===== GPU driver problem =====<br />
<br />
Make sure you have the proper driver for your card installed, so that your desktop is at least 2D accelerated. Follow these articles for more information: [[ATI]], [[NVIDIA]], [[Intel]] for more information, in order to make sure that everything is all right.<br />
The open-source ATI and Intel drivers and the proprietary (binary) Nvidia driver should theoretically provide the best 2D and 3D acceleration.<br />
<br />
===== The Raster engine workaround =====<br />
<br />
If this does not solve your problems, your driver may not provide a good '''XRender''' acceleration which the current Qt painter engine relies on by default.<br />
<br />
You can change the painter engine to software based only by invoking the application with the {{ic|-graphicssystem raster}} command line. This rendering engine can be set as the default one by recompiling Qt with the same as configure option, {{ic|-graphicssystem raster}}.<br />
<br />
The raster paint engine enables the CPU to do the majority of the painting, as opposed to the GPU. You may get better performance, depending on your system. This is basically a work-around for the terrible Linux driver stack, since the CPU should obviously not be doing graphical computations since it is designed for fewer threads of greater complexity, as opposed to the GPU which is many threads but lesser computational strength. So, only use Raster engine if you are having problems or your GPU is much slower than you CPU, otherwise is better to use XRender.<br />
<br />
Since Qt 4.7+, recompiling Qt is not needed. Simply export {{ic|1=QT_GRAPHICSSYSTEM=raster}}, or {{ic|opengl}}, or {{ic|native}} (for the default). Raster depends on the CPU, OpenGL depends on the GPU and high driver support, and Native is just using the X11 rendering (mixture, usually).<br />
<br />
'''The best and automatic way to do that''' is to install {{AUR|kcm-qt-graphicssystem}} from AUR and configure this particular Qt setting through:<br />
<br />
System Settings > Qt Graphics System<br />
<br />
For more information, consult this [http://apachelog.wordpress.com/2010/09/05/qt-graphics-system-kcm/ KDE Developer blog entry] and/or this [http://labs.trolltech.com/blogs/2009/12/18/qt-graphics-and-performance-the-raster-engine/ Qt Developer blog entry].<br />
<br />
==== Low 3D desktop performance====<br />
<br />
KDE begins with desktop effects enabled. Older cards may be insufficient for 3D desktop acceleration. You can disable desktop effects in:<br />
System Settings > Desktop Effects<br />
and you can toggle desktop effects with {{ic|Alt+Shift+F12}}.<br />
<br />
{{Note| You may encounter such problems with 3D desktop performance even when using a more powerful graphics card, especially the catalyst proprietary driver ({{ic|fglrx}}). This driver is known for having problems with 3D acceleration. Visit [[ATI|the ATI Wiki page]] for more troubleshooting.}}<br />
<br />
==== Desktop compositing is disabled on my system with a modern Nvidia GPU ====<br />
<br />
Sometimes, KWin may have settings in its configuration file ({{ic|kwinrc}}) that ''may'' cause a problem on re-activating the 3D desktop {{ic|OpenGL}} compositing. That could be caused randomly (for example, due to a sudden Xorg crash or restart, and it gets corrupted), so, in case that happens, delete your {{ic|~/.kde4/share/config/kwinrc}} file and relogin. The KWin settings will turn to the KDE default ones and the problem should be probably gone.<br />
<br />
==== Flickering in fullscreen when compositing is enabled ====<br />
<br />
As of KDE SC 4.6.0, there is an option in ''Sytem Settings > Desktop Effect > Advanced > Suspend desktop effects for fullscreen windows''. Uncheck it would tell kwin to disable unredirect fullscren.<br />
<br />
==== Screen Tearing with desktop compositing enabled ====<br />
<br />
KWin may suffer from [[Wikipedia:Screen tearing|screen tearing]] while desktop effects are enabled. Uncheck the VSync option under ''System Settings > Desktop Effects > Advanced > Use Vsync''.<br />
<br />
{{Note|With the release of KDE 4.11, several new Vsync options have been added, which may help with screen tearing.}}<br />
<br />
For proprietary driver users, ensure that the driver's VSync option is enabled (''amdccle'' for [[Catalyst]] users, and ''nvidia-settings'' for [[NVIDIA]] users).<br />
<br />
==== Display settings lost on reboot (multiple monitors) ====<br />
There is a [https://bugs.kde.org/show_bug.cgi?id=346961 bug] in kscreen that makes it forget dual screen settings after reboot with certain displays.<br />
A possible workaround is to delete kscreen and make sure that your screen resolution is specified in a xorg.conf file:<br />
* For Nouveau you can use the template at [[Nouveau#Dual_Head]], just edit it to suit your setup.<br />
* For the proprietary nvidia driver you can use the [[NVIDIA#Using_NVIDIA_Settings|nvidia-settings]] utility as root to write the config file.<br />
<br />
''' Other suggestion '''<br />
<br />
Installing {{Pkg|kscreen4}} might fix the problem unless your screens share the same EDID. Kscreen is the improved screen management software for KDE, more information can be found [https://fedoraproject.org/wiki/Changes/KScreen?rd=Features/KScreen here].<br />
<br />
=== Sound problems under KDE ===<br />
<br />
==== ALSA related problems ====<br />
<br />
{{Note|First make sure you have {{Pkg|alsa-lib}} and {{Pkg|alsa-utils}} installed.}}<br />
<br />
===== "Falling back to default" messages when trying to listen to any sound in KDE =====<br />
<br />
When you encounter such messages:<br />
The audio playback device ''name_of_the_sound_device'' does not work.<br />
Falling back to default<br />
Go to:<br />
System Settings > Multimedia > Phonon<br />
and set the device named {{ic|default}} above all the other devices in each box you see.<br />
<br />
===== MP3 files cannot be played when using the GStreamer Phonon backend =====<br />
<br />
This can be solved by installing the GStreamer libav plugin (package {{Pkg|gst-libav}}). If you still encounter problems, you can try changing the Phonon backend used by installing another such as {{Pkg|phonon-qt4-vlc}} or {{Pkg|phonon-qt5-vlc}}.<br />
Then, make sure the backend is preferred via:<br />
<br />
System Settings > Multimedia > Phonon > Backend (tab)<br />
<br />
=== Konsole does not save commands' history ===<br />
<br />
By default console command history is saved only when you type 'exit' in console. When you close Konsole with 'x' in the corner it does not happen.<br />
To enable autosaving after every command execution:<br />
<br />
{{hc|~/.bashrc|<nowiki><br />
shopt -s histappend<br />
[[ "${PROMPT_COMMAND}" ]] && PROMPT_COMMAND="$PROMPT_COMMAND;history -a" || PROMPT_COMMAND="history -a"<br />
</nowiki>}}<br />
<br />
=== KDE password prompts display three bullets per char ===<br />
<br />
This setting can be changed at ''System Settings > Account Details > Password & User Account'':<br />
* Show one bullet for each letter<br />
* Show three bullets for each letter<br />
* Show nothing<br />
<br />
=== Dolphin and File Dialogs are extremely slow to start ===<br />
<br />
This may be caused by the upower service. If the upower service is not needed on your system, it can be disabled:<br />
<br />
# systemctl disable upower<br />
# systemctl mask upower<br />
<br />
Obviously this will not have any side effect on a desktop system.<br />
<br />
=== Default PDF viewer in GTK applications under KDE ===<br />
<br />
In some cases when you have installed [[Inkscape]], [[Gimp]] or other graphic programs, GTK applications ([[Firefox]] among all) might not select Okular as the default PDF application, and they are not going to follow the KDE settings on default applications. You can use the following user command to make Okular the default application again.<br />
<br />
$ xdg-mime default kde4-okularApplication_pdf.desktop application/pdf<br />
<br />
If you are using a different PDF viewer application, or a different mime-type is misbehaving, you should change {{ic|kde4-okularApplication_pdf.desktop}} and {{ic|application/pdf}} respectively according to your needs.<br />
<br />
For more information, consult [[Default applications]] wiki page.<br />
<br />
=== Inotify folder watch limit ===<br />
<br />
If you get the following error:<br />
<br />
KDE Baloo Filewatch service reached the inotify folder watch limit. File changes may be ignored.<br />
<br />
Then you will need to increase the inotify folder watch limit:<br />
<br />
# echo 10000 > /proc/sys/fs/inotify/max_user_watches<br />
<br />
To make changes permanent, create {{ic|/etc/sysctl.d/90-inotify.conf}} with<br />
<br />
#increase inotify watch limit<br />
fs.inotify.max_user_watches = 10000<br />
<br />
== Unstable releases ==<br />
<br />
When KDE is reaching beta or RC milestone, KDE "unstable" packages are uploaded to the ''kde-unstable'' repository. They stay there until KDE is declared stable and passes to the ''extra'' repository.<br />
<br />
You can add ''kde-unstable'' with:<br />
<br />
{{hc|/etc/pacman.conf|2=<br />
[kde-unstable]<br />
Include = /etc/pacman.d/mirrorlist<br />
}}<br />
<br />
{{Warning|Make sure to add these lines '''before''' the ''extra'' repository. Adding the section after ''extra'' will cause [[pacman]] to prefer the older packages in the extra repository. {{ic|pacman -Syu}} will not install them, and will warn that they are "too new" if installed manually. Also, some of the libraries will stay at the older versions, which may cause file conflicts and/or instability!}}<br />
<br />
# ''kde-unstable'' is based upon ''testing''. Therefore, you need to enable the repositories in the following order: ''kde-unstable'', ''testing'', ''core'', ''extra'', ''community-testing'', ''community''.<br />
# To update from a previous KDE installation, run: {{ic|# pacman -Syu}} or {{ic|# pacman -S kde-unstable/kde}}<br />
# If you do not have KDE installed, you might have difficulties to install it by using groups (limitation of pacman)<br />
# '''Subscribe and read the [https://mailman.archlinux.org/pipermail/arch-dev-public/ arch-dev-public] mailing list'''<br />
# Make sure [[#Distro_and_Upstream_bug_report|you make bug reports]] if you find any problems.<br />
<br />
== KDE forks ==<br />
<br />
=== Trinity ===<br />
<br />
From the release of KDE 4.x, the developers dropped support for KDE 3.5.x. Trinity Desktop Environment is a fork of KDE3 developed by Timothy Pearson ([http://trinitydesktop.org/ trinitydesktop.org]). This project aims to keep the KDE3.5 computing style alive, as well as polish off any rough edges that were present as of KDE 3.5.10. See [[Trinity]] for more info.<br />
<br />
== Bugs ==<br />
<br />
It is preferrable that if you find a minor or serious bug, you should visit [https://bugs.archlinux.org the Arch Bug Tracker] or/and [http://bugs.kde.org KDE Bug Tracker] in order to report that. Make sure that you are clear about what you want to report.<br />
<br />
If you have any problem and you write about in on the Arch forums, first make sure that you have '''fully''' updated your system using a good sync mirror (check [https://www.archlinux.de/?page=MirrorStatus here]) or try [[Reflector]].<br />
<br />
== See also ==<br />
<br />
* [http://www.kde.org KDE homepage]<br />
* [https://bugs.kde.org KDE bug tracker]<br />
* [https://projects.kde.org KDE Projects]<br />
* [http://blog.martin-graesslin.com/blog/kategorien/kde/ Martin Graesslin's blog]</div>JKAbramshttps://wiki.archlinux.org/index.php?title=KDE&diff=373306KDE2015-05-10T21:32:49Z<p>JKAbrams: Added a workaround that I've personally tested with both nvidia and nouveau drivers (not sure if ATI ever has this issue). I tried but the other workaround did not work for me. Perhaps it's no good anymore and should be deleted but I don't know for sure.</p>
<hr />
<div>[[Category:KDE]]<br />
[[cs:KDE]]<br />
[[de:KDE]]<br />
[[es:KDE]]<br />
[[fr:KDE]]<br />
[[it:KDE]]<br />
[[ja:KDE]]<br />
[[pl:KDE]]<br />
[[ru:KDE]]<br />
[[tr:KDE_Masaüstü_Ortamı]]<br />
[[zh-CN:KDE]]<br />
[[zh-TW:KDE]]<br />
{{Related articles start}}<br />
{{Related|Desktop environment}}<br />
{{Related|Display manager}}<br />
{{Related|Window manager}}<br />
{{Related|Plasma}}<br />
{{Related|Qt}}<br />
{{Related|KDM}}<br />
{{Related|KDevelop 4}}<br />
{{Related|Uniform Look for Qt and GTK Applications}}<br />
{{Related articles end}}<br />
<br />
From [http://www.kde.org/community/whatiskde/softwarecompilation.php KDE Software Compilation] and [http://www.kde.org/download/ Getting KDE Software]:<br />
<br />
:The KDE Software Compilation is the set of frameworks, workspaces, and applications produced by KDE to create a beautiful, functional and free desktop computing environment for Linux and similar operating systems. It consists of a large number of individual applications and a desktop workspace as a shell to run these applications.<br />
<br />
The KDE upstream has a well maintained [http://userbase.kde.org/ UserBase wiki]. Users can get detailed information about most KDE applications there.<br />
<br />
{{note| The term "KDE Software Compilation" is now outdated. KDE is moving to a new way of organizing itself, see: [[Plasma]].}}<br />
== Installation ==<br />
<br />
Before installing KDE, make sure you have a working [[Xorg]] installation on your system.<br />
<br />
Starting in 2014, the KDE project has changed the way it names and organizes itself. There is no KDE Software Compilation anymore, the project is now split into different products with their own names, version numbering and development cycles including: Frameworks (KDE libraries), Plasma (the workspace) and Applications (built on top of KDE libraries). <br />
<br />
=== Plasma 5 ===<br />
<br />
See [[Plasma]].<br />
<br />
=== KDE 4 Workspace ===<br />
<br />
To get the KDE4 version of the Plasma Desktop, install the {{Pkg|kdebase-workspace}} package and, optionally, the {{Pkg|kdebase-plasma}} package (folder view applet) and the {{Grp|kdeplasma4-addons}} and {{Grp|kdeartwork}} groups for additional plasmoids and artwork. Note that the KDE4 Plasma Desktop is currently in maintenance mode, and is expected to reach EOL in August 2015.<br />
<br />
=== KDE Applications ===<br />
<br />
To install the full set of KDE Applications, use the {{Grp|kde-applications}} group, or the {{Grp|kde-applications-meta}} meta-packages to install specific modules. Note that this will only install Applications, it will not install any version of the Plasma Desktop.<br />
<br />
==== Language pack ====<br />
<br />
If you need language files, install {{ic|kde-l10n-yourlanguagehere}} (e.g. {{Pkg|kde-l10n-de}} for the German language).<br />
<br />
For a full list of available languages see [https://www.archlinux.org/packages/extra/any/kde-l10n/ this link].<br />
<br />
== Starting Plasma ==<br />
See [[Plasma#Starting Plasma]].<br />
<br />
== Configuration ==<br />
<br />
All KDE 4 configurations are saved in the {{ic|~/.kde4}} folder, otherwise {{ic|~/.config}} is used. If KDE is giving you a lot of trouble or if you ever want a fresh installation of KDE, just backup and rename this folder and restart your X session. KDE will re-create it with all the default configuration files. If you want very fine-grained control over KDE programs, you may want to edit the files in this folder.<br />
<br />
However, configuring KDE is primarily done in '''System Settings'''. A few other options for the desktop are available in '''Default Desktop Settings''' in the desktop's context menu.<br />
<br />
For other personalization options not covered below such as activities, different wallpapers on one cube, etc., please refer to the [[Plasma]] wiki page.<br />
<br />
=== Personalization ===<br />
<br />
How to set up the KDE desktop to your personal style: use different Plasma themes, window decorations and icon themes.<br />
{{tip|1=Applications using the new frameworks 5 use the same configurations as under the old kdebase-workspace 4 but read from new locations. To allow frameworks 5 applications running in kdebase-workspace 4 to share the same configurations they may be moved to the new locations and symlinked back to the old. Examples are:<br />
*Konsole profiles from ~/.kde4/share/apps/konsole to ~/.local/share/konsole/<br />
*Application appearance from ~/.kde4/share/config/kdeglobals to ~/.config/kdeglobals<br />
This information was gathered from the [https://bbs.archlinux.org/viewforum.php?id=18 Applications & Desktop Environments] section of the forums. }}<br />
<br />
==== Plasma desktop ====<br />
<br />
===== Themes =====<br />
See [[Plasma#Themes]]<br />
<br />
===== Widgets =====<br />
<br />
Plasmoids are little scripted (plasmoid scripts) or coded (plasmoid binaries) KDE applications designed to enhance the functionality of your desktop.<br />
<br />
Plasmoid binaries can be installed using PKGBUILDs from [https://aur.archlinux.org/packages.php?O=0&K=plasmoid&do_Search=Go&PP=25&SO=d&SB=v AUR], or you can write your own PKGBUILD.<br />
<br />
The easiest way to install plasmoid scripts is by right-clicking onto a panel or the desktop:<br />
<br />
Add Widgets > Get new Widgets > Download Widgets<br />
<br />
This will present a nice frontend for [http://www.kde-look.org/ kde-look.org] that allows you to install, uninstall, or update third-party plasmoid scripts with literally just one click.<br />
<br />
Most plasmoids are not created officially by KDE developers. You can also try installing Mac OS X widgets, Microsoft Windows Vista/7 widgets, Google Widgets, and even SuperKaramba widgets.<br />
<br />
===== Sound applet in the system tray =====<br />
<br />
Install Kmix ({{Pkg|kdemultimedia-kmix}} for KDE 4, or {{Pkg|kmix}} for Plasma 5) from the official repositories and start it from the application launcher. Since KDE, by default, autostarts programs from the previous session, it does not need to be started manually upon every login.<br />
<br />
{{Note|1=To adjust the [https://bugs.kde.org/show_bug.cgi?id=313579#c28 step size of volume increments/decrements], add e.g. {{ic|1=VolumePercentageStep=1}} in the {{ic|[Global]}} section of {{ic|~/.kde4/share/config/kmixrc}}}}<br />
<br />
===== Adding a Global Menu to the desktop =====<br />
<br />
Install {{Pkg|appmenu-qt}} from the official repositories and {{AUR|appmenu-gtk}} and {{AUR|appmenu-qt5}} from the AUR in order to complete the preliminaries for a Mac OS X style always-on global menu. To get Firefox and LibreOffice to use the global menu as well, install {{AUR|firefox-extension-globalmenu}}{{Broken package link|package not found}} and {{AUR|libreoffice-extension-menubar}} from the AUR.<br />
<br />
{{Note|<br />
* {{AUR|appmenu-gtk}} is orphaned and Canonical has abandoned appmenu-gtk in favor of unity-gtk-module that is depending on Unity desktop. As of October 2014 there is no way of exporting gtk2,3 menus in KDE.<br />
* Install {{AUR|firefox-ubuntu}}, available in the AUR, which has Canonical's patch for getting the global menu to work with the current version of Firefox (as of November 2013).<br />
}}<br />
<br />
To actually get the global menu, install {{AUR|kdeplasma-applets-menubar}} from the AUR. Create a plasma-panel on top of your screen and add the window menubar applet to the panel. To export the menus to your global menu, go to ''System Settings > Application Appearance > Style''. Now click the fine-tuning tab and use the drop-down list to select ''only export'' as your menubar style.<br />
<br />
===== Disable panel shadow =====<br />
<br />
As the plasma panel is on top of other windows, its shadow is drawn over them. [https://bbs.archlinux.org/viewtopic.php?pid=1228394#p1228394] To disable this behaviour without impacting other shadows, [[install]] {{Pkg|xorg-xprop}} and run:<br />
<br />
$ xprop -remove _KDE_NET_WM_SHADOW<br />
<br />
then select the panel with the plus-sized cursor. [https://forum.kde.org/viewtopic.php?f=285&t=121592] For automation, install {{Pkg|xorg-xwininfo}} and create the following script:<br />
<br />
{{hc|/usr/local/bin/kde-no-shadow|<nowiki><br />
#!/bin/bash<br />
for WID in $(xwininfo -root -tree | sed '/"plasma-desktop": ("Plasma" "Plasma")/!d; s/^ *\([^ ]*\) .*/\1/g'); do<br />
xprop -id $WID -remove _KDE_NET_WM_SHADOW<br />
done<br />
</nowiki>}}<br />
<br />
The script can be run on login with ''Add Script'' in ''Autostart'':<br />
<br />
$ kcmshell4 autostart<br />
<br />
==== Window decorations ====<br />
<br />
[http://kde-look.org/index.php?xcontentmode=75 Window decorations] can be changed in:<br />
System Settings > Workspace Appearance > Window Decorations<br />
There you can also directly download and install more themes with one click, and some are available in the [https://aur.archlinux.org/packages.php?O=0&K=kdestyle&do_Search=Go&PP=25&SO=d&SB=v AUR].<br />
<br />
==== Icon themes ====<br />
<br />
Not many full system icons themes are available for KDE 4. You can open up ''System Settings > Application Appearance > Icons'' and browse for new ones or install them manually. Many of them can be found on [http://www.kde-look.org/ kde-look.org].<br />
<br />
Official logos, icons, CD labels and other artwork for Arch Linux are provided in the {{AUR|archlinux-artwork}} package. After installing you can find such artwork at {{ic|/usr/share/archlinux/}}.<br />
<br />
===== Qt 5 icons theme =====<br />
<br />
If you are on Plasma 5, use ''System Settings > Icons''.<br />
While if you are on KDE 4 use {{ic|kcmshell5 icons}} to set the icons theme.<br />
<br />
==== Fonts ====<br />
<br />
===== Fonts in KDE look poor =====<br />
<br />
Try installing the {{Pkg|ttf-dejavu}} and {{Pkg|ttf-liberation}} packages.<br />
<br />
After the installation, be sure to log out and back in. You should not have to modify anything in ''System Settings > Fonts''.<br />
<br />
If you have personally set up how your [[Fonts]] render, be aware that System Settings may alter their appearance. When you go ''System Settings > Appearance > Fonts'', System Settings will likely alter your font configuration file ({{ic|fonts.conf}}).<br />
<br />
There is no way to prevent this, but, if you set the values to match your {{ic|fonts.conf}} file, the expected font rendering will return (it will require you to restart your application or in a few cases restart your desktop). Note that Gnome's Font Preferences also does this.<br />
<br />
===== Fonts are huge or seem disproportional =====<br />
<br />
Try to force font DPI to '''96''' in ''System Settings > Application Appearance > Fonts''.<br />
<br />
If that does not work, try setting the DPI directly in your Xorg configuration as documented [[Xorg#Setting_DPI_manually|here]].<br />
<br />
==== Space efficiency ====<br />
<br />
Users with small screens (e.g. netbooks) can change some setting to make KDE more space efficient. See the [http://userbase.kde.org/KWin#Using_with_small_screens_(eg_Netbooks) upstream wiki] for more information. Also, you can use [http://www.kde.org/workspaces/plasmanetbook/ KDE's Plasma Netbook] which is a workspace made specifically for small, lightweight netbook devices.<br />
<br />
=== Networking ===<br />
<br />
You can choose from the following tools:<br />
* NetworkManager. See [[NetworkManager#KDE|NetworkManager]] for more information.<br />
* Wicd. See [[Wicd]] for more information.<br />
<br />
=== Printing ===<br />
<br />
{{Tip|Use the [[CUPS]] web interface for faster configuration. Printers configured in this way can be used in KDE applications. }}<br />
<br />
You can also configure printers in ''System Settings > Printer Configuration''. To use this method, you must first install {{Pkg|print-manager}} and {{Pkg|cups}}.<br />
<br />
The {{ic|avahi-daemon}} and {{ic|cupsd}} daemons must be started first; otherwise, you will get the following error:<br />
The service 'Printer Configuration' does not provide an interface 'KCModule'<br />
with keyword 'system-config- printer-kde/system-config-printer-kde.py'<br />
The factory does not support creating components of the specified type.<br />
<br />
If you are getting the following error, you need to give your user the right to manage printers.<br />
There was an error during CUPS operation: 'cups-authorization-canceled'<br />
<br />
For CUPS, this is set in {{ic|/etc/cups/cups-files.conf}}.<br />
<br />
Adding {{ic|lpadmin}} to {{ic|/etc/group}} and then to the {{ic|SystemGroup}} directive in {{ic|/etc/cups/cups-files.conf}} allows anyone in the {{ic|lpadmin}} group to configure printers. Do ''not'' add the {{ic|lp}} group to the {{ic|SystemGroup}} directive, or printing will fail.<br />
<br />
# groupadd -g107 lpadmin<br />
<br />
{{hc|/etc/cups/cups-files.conf|# Administrator user group...<br />
SystemGroup sys root lpadmin}}<br />
<br />
{{Tip|Read [[CUPS#CUPS administration]] to get more details on how to configure CUPS.}}<br />
<br />
=== Samba/Windows support ===<br />
<br />
If you want to have access to Windows services, install [[Samba]] (package {{Pkg|samba}}).<br />
<br />
The Dolphin share functionality requires usershares, which the stock smb.conf does not have enabled. Instructions to add them are in [[Samba#Creating_user_share_path|the Samba article]], after which sharing in Dolphin should work out of the box after restarting Samba.<br />
<br />
=== KDE Desktop activities ===<br />
<br />
KDE Desktop Activities are Plasma-based virtual-desktop-like sets of Plasma Widgets where you can independently configure widgets as if you have more than one screen or desktop.<br />
<br />
On your desktop, click the Cashew Plasmoid and, on the pop-up window, press "Activities".<br />
<br />
A plasma bar presenting you the current existing Plasma Desktop Activities will appear at the bottom of the screen. You can navigate between them by pressing the correspondent icons.<br />
<br />
=== Power saving ===<br />
<br />
KDE has an integrated power saving service called "'''Powerdevil Power Management'''" that may adjust the power saving profile of the system and/or the brightness of the screen (if supported).<br />
<br />
Since KDE 4.6, CPU frequency scaling is no longer managed by KDE. Instead it is assumed to be handled automatically by the the hardware and/or kernel. Arch has used {{ic|ondemand}} as the default CPU frequency governor since kernel version 3.3, so no additional configuration is needed in most cases. For details on fine-tuning the governor, see [[CPU frequency scaling]].<br />
<br />
=== Monitoring changes on local files and directories ===<br />
<br />
KDE now uses '''inotify''' directly from the kernel with '''kdirwatch''' (included in kdelibs), so Gamin or FAM are no longer needed. You may want to install this {{AUR|kdirwatch}} from AUR which is a GUI frontend for kdirwatch.<br />
<br />
== System administration ==<br />
<br />
=== Set keyboard ===<br />
<br />
Navigate to:<br />
System Settings > Hardware > Input Devices > Keyboard<br />
In the first tab, you can choose your keyboard model.<br />
<br />
In the "'''Layouts'''" tab, you can choose the languages you may want to use by pressing the "Add Layout" button and subsequently choosing the variant and the language.<br />
<br />
In the "'''Advanced'''" tab, you can choose the keyboard combination you want in order to change the layouts in the "Key(s) to change layout" sub-menu.<br />
<br />
=== Terminate Xorg server through KDE system settings ===<br />
<br />
Navigate to the submenu:<br />
System Settings > Input Devices > Keyboard > Advanced (tab) > "Key Sequence to kill the X server"<br />
and tick the checkbox.<br />
<br />
=== KCM ===<br />
<br />
KCM stands for '''KC'''onfig '''M'''odule. KCMs can help you configure your system by providing interfaces in System Settings.<br />
<br />
'''Configuration for look and feel of GTK applications.'''<br />
* {{Pkg|kde-gtk-config}}<br />
* {{AUR|kcm-gtk}}<br />
* {{AUR|kcm-qt-graphicssystem}}<br />
<br />
'''Configuration for the GRUB bootloader.'''<br />
* {{AUR|grub2-editor}}<br />
<br />
'''Configuration for Synaptics touchpads.'''<br />
* {{Pkg|kcm-touchpad}}<br />
* {{Pkg|kcm-touchpad-frameworks}}{{Broken package link|replaced by {{Pkg|plasma-desktop}}}} (Plasma 5)<br />
* {{AUR|synaptiks}}{{Broken package link|package not found}}<br />
* {{AUR|kcm_touchpad}}<br />
* {{AUR|kcm-touchpad-git}}{{Broken package link|package not found}}<br />
<br />
'''Configuration for the [[Uncomplicated Firewall]] (UFW)'''<br />
* {{AUR|kcm-ufw}}<br />
<br />
'''Configuration for [[PolicyKit]]'''<br />
* {{AUR|kcm-polkit-kde-git}}<br />
<br />
'''Configuration for Wacom tablets'''<br />
* {{AUR|kcm-wacomtablet}}<br />
<br />
'''Configuration for systemd'''<br />
* {{Pkg|kcmsystemd}} (Plasma 5)<br />
<br />
More KCMs can be found at [http://kde-apps.org/index.php?xcontentmode=273 kde-apps.org].<br />
<br />
===Auto Login===<br />
Go to ''System Settings > System Administration > Login Screen > Convenience'', check ''Enable Auto-Login'' box and select user.<br />
<br />
== Desktop search and semantic desktop ==<br />
<br />
According to [[wikipedia:Semantic_desktop|Wikipedia]]:<br />
:''"the Semantic Desktop is a collective term for ideas related to changing a computer's user interface and data handling capabilities so that data is more easily shared between different applications or tasks and so that data that once could not be automatically processed by a computer can be (automatically processed)."''<br />
<br />
The KDE implementation of this concept is tied to (as of KDE Applications 4.13) two major pieces of software: Akonadi and Baloo. Between the two of them, these programs look at your data and make an easily searchable index of it. The idea behind these pieces of software is to make your system "aware" of your data and give it context using meta-data and user-supplied tags. Baloo uses Xapian to store its data.<br />
<br />
=== Baloo ===<br />
<br />
==== Using and configuring Baloo ====<br />
<br />
In order to search using Baloo on the KDE Plasma Desktop, press {{ic|ALT+F2}} and type in your query. Within Dophin press {{ic|CTRL+F}}.<br />
<br />
By default the Desktop Search KCM exposes only two options: A panel to blacklist folders and, as of 4.13.1, a way to disable it with one click.<br />
<br />
Alternatively you can edit your {{ic|~/.kde4/share/config/baloofilerc}} (KDE4) or {{ic|~/.config/baloofilerc}} (KF5) file ([https://community.kde.org/Baloo/Configuration info]). Additionally the {{ic|balooctl}} process can also be used. In order to disable Baloo run {{ic|balooctl disable}}.<br />
<br />
Once you added additional folders to the blacklist or disabled Baloo entirely, a process named {{ic|baloo_file_cleaner}} removes all unneeded index files automatically. They are stored under {{ic|~/.local/share/baloo/}}.<br />
<br />
More advanced configuration options are available through {{AUR|kcm_baloo_advanced}}.<br />
<br />
==== How do I index a removable device? ====<br />
<br />
By default every removable device is blacklisted. You just have to remove your device from the blacklist in the KCM panel.<br />
<br />
=== Akonadi ===<br />
<br />
Akonadi is a system meant to act as a local cache for PIM data, regardless of its origin, which can be then used by other applications. This includes the user's emails, contacts, calendars, events, journals, alarms, notes, and so on.<br />
<br />
Akonadi does not store any data by itself: the storage format depends on the nature of the data (for example, contacts may be stored in vCard format).<br />
<br />
==== Disabling Akonadi ====<br />
<br />
See this [http://userbase.kde.org/Akonadi#Disabling_the_Akonadi_subsystem section in the KDE userbase]. Alternatively, install {{AUR|akonadi-fake}} from the [[AUR]].<br />
<br />
==== Database configuration ====<br />
<br />
Start {{ic|akonaditray}} from package {{Pkg|kdepim-runtime}}. Right click on it and select '''configure'''. In the Akonadi server configure tab, you can:<br />
* Configuring Akonadi to use MySQL/MariaDB Server<br />
** If your home directory is on a ZFS pool, you will need to create {{ic|~/.config/akonadi/mysql-local.conf}} with the following contents:<br />
<br />
[mysqld]<br />
innodb_use_native_aio = 0<br />
<br />
Otherwise you will get the [[MySQL#OS error 22 when running on ZFS|OS error 22]]<br />
* Configuring Akonadi to use PostgreSQL Server<br />
* Configuring Akonadi to use SQLite<br />
** Edit {{ic|~/.config/akonadi/akonadiserverrc}} to match the below<br />
<br />
[General]<br />
Driver=QSQLITE3<br />
<br />
[QSQLITE3]<br />
Name=/home/username/.local/akonadi/akonadi.db<br />
<br />
== Phonon ==<br />
<br />
From [[Wikipedia:Phonon|Wikipedia]]:<br />
<br />
:''"Phonon is the multimedia API for KDE 4. Phonon was created to allow KDE 4 to be independent of any single multimedia framework such as GStreamer or xine and to provide a stable API for KDE 4's lifetime. It was done for various reasons: to create a simple KDE/Qt style multimedia API, to better support native multimedia frameworks on Windows and Mac OS X, and to fix problems of frameworks becoming unmaintained or having API or ABI instability."''<br />
<br />
'''Phonon''' is being widely used within KDE, for both audio (e.g., the System notifications or KDE audio apps) and video (e.g., the Dolphin video thumbnails).<br />
<br />
=== Which backend should I choose? ===<br />
<br />
You can choose between various backends like [[GStreamer]] ({{Pkg|phonon-qt4-gstreamer}}, {{Pkg|phonon-qt5-gstreamer}}) or [[VLC]] ({{Pkg|phonon-qt4-vlc}}, {{Pkg|phonon-qt5-vlc}}), available in the [[official repositories]], and [[MPlayer]] ({{AUR|phonon-qt4-mplayer-git}}), QuickTime ({{AUR|phonon-quicktime-git}}) or [http://martinsandsmark.wordpress.com/2012/07/07/akademy/ AVKode] ({{AUR|phonon-avkode-git}}), available in the [[AUR]].<br />
<br />
Most users will want VLC which has the best upstream support. GStreamer is currently not well maintained. Note that multiple backends can be installed at once and chosen at ''System Settings > Multimedia > Phonon > Backend''.<br />
<br />
{{Note|<br />
* According to the [http://community.kde.org/Phonon/FeatureMatrix Feature Matrix], the GStreamer backend has some more features that the VLC backend.<br />
* According to the [http://userbase.kde.org/Phonon#Backend_libraries KDE UserBase], Phonon-MPlayer is currently unmaintained.}}<br />
<br />
== Useful applications ==<br />
<br />
The official set of KDE applications may be found [http://www.kde.org/applications/ here].<br />
<br />
=== Yakuake ===<br />
<br />
[[Yakuake]] provides a Quake-like terminal emulator whose visibility is toggled by the F12 key. It also has support for multiple tabs. Yakuake is available in the package {{Pkg|yakuake}}.<br />
<br />
=== KDE Telepathy ===<br />
<br />
[http://community.kde.org/KTp KDE Telepathy] is a project with the goal to closely integrate Instant Messaging with the KDE desktop. It utilizes the Telepathy framework as a backend and is intended to replace Kopete.<br />
<br />
To install all Telepathy protocols, install the {{Grp|telepathy}} group.<br />
To use the KDE Telepathy client, install the {{Pkg|telepathy-kde-meta}} package that includes all the packages contained in the {{Grp|kde-telepathy}}{{Broken package link|package not found}} group.<br />
<br />
==== Use Telegram with KDE Telepathy ====<br />
<br />
Telegram protocol is avaible using {{pkg|telepathy-haze}}, installing {{aur|telegram-purple}} or {{aur|telegram-purple-git}}. The username is the Telegram account telephone number (complete with the national prefix '+xx', e.g. '+39' for Germany). The configuration though the GUI may be tricky: if the phone number is not accepted when configuring a new account in the KDE Telepathy client (with an error message complaining about an invalid parameter which prevents the account creation), insert it between single quotes and then remove the quotes manually from the configuration file (<code>~/.local/share/telepathy/mission-control/accounts.cfg</code>) after the account creation (if the quotes are not removed after, an authentication error should rise). Note that the configuration file should be edited manually when KDE Telepathy is not running, e.g. when there is no KDE desktop session active, otherwise manual changes may be overwritten by the software.<br />
<br />
== Tips and tricks ==<br />
<br />
=== Using an alternative window manager in KDE ===<br />
<br />
To use an alternative [[window manager]] with KDE open the ''System Settings'' panel, navigate to ''Default Applications > Window Manager > Use a different window manager'' and select the window manager you wish to use from the list.<br />
<br />
==== KDE/Openbox Session ====<br />
<br />
The {{Pkg|openbox}} package provides a session for using KDE with [[Openbox]]. To make use of this session, select ''KDE/Openbox'' from the [[display manager]] menu.<br />
<br />
For those starting the session manually, add the following line to your {{ic|.xinitrc}} file:<br />
exec openbox-kde-session<br />
<br />
==== Compiz custom ====<br />
<br />
If you need to run Compiz with custom options and switches select ''Compiz custom'' and then create a script called {{ic|compiz-kde-launcher}} and add to it the commands you wish to use to start Compiz. See the example below:<br />
<br />
{{hc|/usr/local/bin/compiz-kde-launcher|<nowiki><br />
#!/bin/bash<br />
LIBGL_ALWAYS_INDIRECT=1<br />
compiz --replace &<br />
wait<br />
</nowiki>}}<br />
<br />
Then make it executable:<br />
$ chmod +x /usr/local/bin/compiz-kde-launcher<br />
<br />
==== Re-enabling compositing effects ====<br />
<br />
When replacing Kwin with a window manager which does not provide a Compositor (such as Openbox), any desktop compositing effects e.g. transparency will be lost. In this case, install and run a separate Composite manager to provide the effects such as [[Xcompmgr]] or [[Compton]].<br />
<br />
=== Integrate Android with the KDE Desktop ===<br />
<br />
KDE connect provides several features for you:<br />
* Share files and URLs to/from KDE from/to any app, without wires.<br />
* Touchpad emulation: Use your phone screen as your computer's touchpad.<br />
* Notifications sync (4.3+): Read your Android notifications from the desktop.<br />
* Shared clipboard: copy and paste between your phone and your computer.<br />
* Multimedia remote control: Use your phone as a remote for Linux media players.<br />
* WiFi connection: no usb wire or bluetooth needed.<br />
* RSA Encryption: your information is safe.<br />
<br />
You will need to install KDE Connect both on your computer and on your Android. For PC side, install {{Pkg|kdeconnect}} if you are using KDE4 or if you are using Plasma 5, then you should install {{AUR|kdeconnect-git}} instead. For Android side, install {{ic|KDE Connect}} from the [https://play.google.com/store/apps/details?id=org.kde.kdeconnect_tp&hl=en Google Play Store] or from [https://f-droid.org/repository/browse/?fdid=org.kde.kdeconnect_tp F-Droid].<br />
<br />
=== Configure KWin to use OpenGL ES ===<br />
<br />
Beginning with KWin version 4.8 it is possible to use the separately built binary '''kwin_gles''' as a replacement for kwin. It behaves almost the same as the kwin executable in OpenGL2 mode with the slight difference that it uses ''egl'' instead of ''glx'' as the native platform interface. To test kwin_gles you just have to run {{ic|kwin_gles --replace}} in Konsole.<br />
If you want to make this change permanent you have to create a script in {{ic|$(kde4-config --localprefix)/env/}} which exports {{ic|1=KDEWM=kwin_gles}}.<br />
<br />
=== Enabling audio/video thumbnails under Konqueror/Dolphin file managers ===<br />
<br />
For thumbnails of videos in konqueror and dolphin install {{Pkg|kdemultimedia-mplayerthumbs}} or {{Pkg|kdemultimedia-ffmpegthumbs}} and activate the installed package in ''Settings> Configure Konqueror> General> Previews> Video Files''.<br />
For thumbnails of audio files in Konqueror and Dolphin install {{AUR|audiothumbs}} from AUR.<br />
<br />
=== Speed up application startup ===<br />
<br />
User Rob wrote on his blog this "[http://kdemonkey.blogspot.nl/2008/04/magic-trick.html magic trick]" to improve application start-up time by 50-150ms.<br />
To enable it, create this folder in your home:<br />
$ mkdir ~/.compose-cache/<br />
But it can produce freezes on heavy io, can be avoided by:<br />
$ ln -sfv /run/user/$UID/ /home/$USER/.compose-cache<br />
<br />
{{Note|For those curious about what is going on here, this enables an optimization which Lubos (of general KDE speediness fame) came up with some time ago and was then rewritten and integrated into libx11. Ordinarily, on startup, applications read input method information from {{ic|/usr/share/X11/locale/''your locale''/Compose}}. This file is quite long (>5000 lines for the en_US.UTF-8 one) and takes some time to process. libX11 can create a cache of the parsed information which is much quicker to read subsequently, but it will only re-use an existing cache or create a new one in {{ic|~/.compose-cache}} if the directory already exists.}}<br />
<br />
=== Hiding partitions ===<br />
<br />
In Dolphin, it is as simple as right-clicking on the partition in the {{ic|Places}} sidebar and selecting {{ic|Hide ''partition''}}. Otherwise...<br />
<br />
If you wish to prevent your internal partitions from appearing in your file manager, you can create an udev rule, e.g:<br />
<br />
{{hc|/etc/udev/rules.d/10-local.rules|2=<br />
KERNEL=="sda[0-9]", ENV{UDISKS_IGNORE}="1"<br />
}}<br />
<br />
The same thing for a certain partition:<br />
<br />
KERNEL=="sda1", ENV{UDISKS_IGNORE}="1"<br />
KERNEL=="sda2", ENV{UDISKS_IGNORE}="1"<br />
<br />
=== Konqueror tips ===<br />
<br />
==== Disabling Access Keys ====<br />
<br />
Every time you pressing the Ctrl key while browsing, small square tooltips appear for each of the active areas (hyperlinks) on a webpage. This is useful when you browsing with only a keyboard.<br />
<br />
To disable Access Keys, go to ''Settings > Configure Konqueror > Web Browsing'' and uncheck ''Enable Access Key activation with Ctrl key''.<br />
<br />
==== Using WebKit ====<br />
<br />
WebKit is an open source browser engine developed by Apple Inc. It is a derivative from the KHTML and KJS libraries and contains many improvements. WebKit is used by Safari, Google Chrome and rekonq.<br />
<br />
It is possible to use WebKit in Konqueror instead of KHTML. First install the {{Pkg|kwebkitpart}} package.<br />
<br />
Then, after executing Konqueror, navigate to ''Settings > Configure Konqueror > General > Default web browser engine'' and set it as {{ic|WebKit}}.<br />
<br />
=== Firefox integration ===<br />
<br />
See [[Firefox#KDE_integration|Firefox]].<br />
<br />
=== Setting the background for lock screen ===<br />
<br />
In Plasma 5, you can set a custom wallpaper for the lock screen. This is [https://bugs.kde.org/show_bug.cgi?id=312828 not possible] in KDE 4, but here a workaround from OpenSUSE mailing lists: http://lists.opensuse.org/opensuse-kde/2013-02/msg00082.html<br />
<br />
For this you should modify the file {{ic|/usr/share/kde4/apps/ksmserver/screenlocker/org.kde.passworddialog/contents/ui/main.qml}}, replacing a line<br />
<br />
source: theme.wallpaperPathForSize(parent.width, parent.height)<br />
<br />
with something like<br />
<br />
source: "1920x1080.jpg"<br />
<br />
Now you simply put a wallpaper image {{ic|1920x1080.jpg}} to the {{ic|/usr/share/kde4/apps/ksmserver/screenlocker/org.kde.passworddialog/contents/ui}} directory.<br />
<br />
{{Note|You have to redo this for each update of the package {{Pkg|kdebase-workspace}}.}}<br />
<br />
=== Setting lockscreen wallpaper to arbitrary image ===<br />
<br />
Copy an existing wallpaper profile as a template:<br />
$ cp -r /usr/share/wallpapers/''ExistingWallpaper'' ~/.kde4/share/wallpapers/<br />
<br />
Change the name of the directory, and edit {{ic|metadata.desktop}}:<br />
<br />
{{hc|~/.kde4/share/wallpapers/''MyWallpaper''/metadata.desktop|2=<br />
[Desktop Entry]<br />
Name=MyWallpaper<br />
X-KDE-PluginInfo-Name=MyWallpaper<br />
}}<br />
<br />
Remove existing images ({{ic|contents/screenshot.png}} and {{ic|images/*}}):<br />
$ rm ~/.kde4/share/wallpapers/MyWallpaper/contents/screenshot.png<br />
$ rm ~/.kde4/share/wallpapers/MyWallpaper/contents/images/*<br />
<br />
Copy new image in:<br />
$ cp ''path/to/MyWallpaper.png'' MyWallpaper/contents/images/1920x1080.png<br />
<br />
Edit the metadata profile for the current theme:<br />
{{hc|~/.kde4/share/apps/desktoptheme/MyTheme/metadata.desktop|2=<br />
[Wallpaper]<br />
defaultWallpaperTheme=MyWallpaper<br />
defaultFileSuffix=.png<br />
defaultWidth=1920<br />
defaultHeight=1080<br />
}}<br />
<br />
Lock the screen to check that it worked.<br />
<br />
{{Note|This method sets the lockscreen background without changing any system-wide settings. For a system-wide change, create the new wallpaper profile in {{ic|/usr/share/wallpapers}}.}}<br />
<br />
=== Configuring monitor resolution / multiple monitors ===<br />
<br />
To enable display resolution management and multiple monitors in Plasma 5, install {{Pkg|kscreen}}. This adds the additional options to System Settings/Display and Monitor.<br />
<br />
== Troubleshooting ==<br />
<br />
=== Configuration related ===<br />
<br />
Many problems in KDE are related to configuration. One way to resolve upgrade problems is to start over with a fresh KDE config.<br />
<br />
==== Reset all KDE configuration ====<br />
<br />
To test whether your config is the problem try quitting your KDE session by logging out and, in a tty, run<br />
$ cp -r ~/.kde4 ~/.kde4.safekeeping<br />
$ rm .kde4/{cache,socket,tmp}-$(hostname)<br />
<br />
The ''rm'' command just removes symbolic links which will be recreated by KDE automatically. Now start a new KDE session to see the results.<br />
<br />
If the problem is resolved, you will have a fresh, problem-free {{ic|~/.kde4/}}. You can gradually move parts of your saved configuration back, restarting your session regularly to test, to identify the problematic parts of your config. Some files here are named after applications so you will probably be able to test these without needing to restart KDE.<br />
<br />
==== Plasma desktop behaves strangely ====<br />
<br />
Plasma problems are usually caused by unstable '''plasmoids''' or '''plasma themes'''. First, find which was the last plasmoid or plasma theme you had installed and disable it or uninstall it.<br />
<br />
So, if your desktop suddenly exhibits "locking up", this is likely caused by a faulty installed widget. If you cannot remember which widget you installed before the problem began (sometimes it can be an irregular problem), try to track it down by removing each widget until the problem ceases. Then you can uninstall the widget, and file a bug report (bugs.kde.org) '''only if it is an official widget'''. If it is not, it is recommended you find the entry on kde-look.org and inform the developer of that widget about the problem (detailing steps to reproduce, etc).<br />
<br />
If you cannot find the problem, but you do not want ''all'' the KDE settings to be lost, do:<br />
<br />
$ rm -r ~/.kde4/share/config/plasma*<br />
<br />
This command will '''delete all plasma related configs''' of your user and when you will relogin into KDE, you will have the '''default''' settings back. You should know that this action '''cannot be undone'''. You should create a backup folder and copy all the plasma related configs in it.<br />
<br />
==== Clean cache to resolve upgrade problems ====<br />
<br />
The [https://bbs.archlinux.org/viewtopic.php?id=135301 problem] may be caused by old cache. Sometimes after an upgrade, the old cache might introduce strange, hard to debug behaviour such as unkillable shells, hangs when changing various settings and several other problems such as ark being unable to unrar or unzip or amarok not recognizing any of your musics. This solution can also resolve problems with KDE and QT programmes looking bad following upgrade.<br />
<br />
Rebuild your cache with the following commands:<br />
<br />
$ rm ~/.config/Trolltech.conf<br />
$ kbuildsycoca4 --noincremental<br />
<br />
Hopefully, your problems are now fixed.<br />
<br />
=== Clean akonadi configuration to fix KMail ===<br />
<br />
First, make sure that KMail is not running. Then backup configuration:<br />
$ mv ~/.local/share/akonadi ~/.local/share/akonadi-old<br />
$ mv ~/.config/akonadi ~/.config/akonadi-old<br />
<br />
Start ''SystemSettings > Personal'' and remove all the resources. Go back to Dolphin and remove the original {{ic|~/.local/share/akonadi}} and<br />
{{ic|~/.config/akonadi}} - the copies you made ensure that you can back-track if necessary.<br />
<br />
Now go back to the System Settings page and carefully add the necessary resources. You should see the resource reading in your mail folders. Then start Kontact/KMail to see if it work properly.<br />
<br />
=== Getting current state of KWin for support and debug purposes ===<br />
<br />
This command prints out a wonderful summary of the current state of KWin including used options, used compositing backend and relevant OpenGL driver capabilities. See more on [http://blog.martin-graesslin.com/blog/2012/03/on-getting-help-for-kwin-and-helping-kwin/ Martin's blog].<br />
<br />
$ qdbus org.kde.kwin /KWin supportInformation<br />
<br />
=== KDE4 does not finish loading ===<br />
<br />
There might be a situation in which the graphic driver might create a conflict when starting KDE4. This situation happens after the login but before finishing loading the desktop, making the user wait indefinitely at the loading screen. Until now the only users confirmed to be affected by this are the ones that use [[NVIDIA|Nvidia drivers]] and KDE4.<br />
<br />
A solution for Nvidia users:<br />
<br />
{{hc|~/.kde4/share/config/kwinrc|2=<br />
[Compositing]<br />
Enabled=false<br />
}}<br />
For more information, see [https://bbs.archlinux.org/viewtopic.php?pid=932598 this] thread.<br />
<br />
If a minimal install was done, make sure you installed the required font by your phonon backend listed here: [[#Minimal install]]<br />
<br />
=== KDE and Qt programs look bad when in a different window manager ===<br />
<br />
If you are using KDE or Qt programs but not in a full KDE session (specifically, you did not run {{ic|startkde}}), then as of KDE 4.6.1 you will need to tell Qt how to find KDE's styles (Oxygen, QtCurve etc.)<br />
<br />
You just need to set the environment variable {{ic|QT_PLUGIN_PATH}}. E.g. put:<br />
<br />
export QT_PLUGIN_PATH=$HOME/.kde4/lib/kde4/plugins/:/usr/lib/kde4/plugins/<br />
<br />
into your {{ic|/etc/profile}} (or {{ic|~/.profile}} if you do not have root access). {{ic|qtconfig-qt4}}should then be able to find your KDE styles and everything should look nice again!<br />
<br />
Alternatively, you can symlink the Qt styles directory to the KDE styles one:<br />
# ln -s /usr/lib/kde4/plugins/styles/ /usr/lib/qt4/pluginlib32-libdbusmenu-glibs/styles<br />
<br />
Under Gnome you can try to install the package libgnomeui.<br />
<br />
=== Graphical related problems ===<br />
<br />
==== Low 2D desktop performance (or) artifacts appear when on 2D ====<br />
<br />
===== GPU driver problem =====<br />
<br />
Make sure you have the proper driver for your card installed, so that your desktop is at least 2D accelerated. Follow these articles for more information: [[ATI]], [[NVIDIA]], [[Intel]] for more information, in order to make sure that everything is all right.<br />
The open-source ATI and Intel drivers and the proprietary (binary) Nvidia driver should theoretically provide the best 2D and 3D acceleration.<br />
<br />
===== The Raster engine workaround =====<br />
<br />
If this does not solve your problems, your driver may not provide a good '''XRender''' acceleration which the current Qt painter engine relies on by default.<br />
<br />
You can change the painter engine to software based only by invoking the application with the {{ic|-graphicssystem raster}} command line. This rendering engine can be set as the default one by recompiling Qt with the same as configure option, {{ic|-graphicssystem raster}}.<br />
<br />
The raster paint engine enables the CPU to do the majority of the painting, as opposed to the GPU. You may get better performance, depending on your system. This is basically a work-around for the terrible Linux driver stack, since the CPU should obviously not be doing graphical computations since it is designed for fewer threads of greater complexity, as opposed to the GPU which is many threads but lesser computational strength. So, only use Raster engine if you are having problems or your GPU is much slower than you CPU, otherwise is better to use XRender.<br />
<br />
Since Qt 4.7+, recompiling Qt is not needed. Simply export {{ic|1=QT_GRAPHICSSYSTEM=raster}}, or {{ic|opengl}}, or {{ic|native}} (for the default). Raster depends on the CPU, OpenGL depends on the GPU and high driver support, and Native is just using the X11 rendering (mixture, usually).<br />
<br />
'''The best and automatic way to do that''' is to install {{AUR|kcm-qt-graphicssystem}} from AUR and configure this particular Qt setting through:<br />
<br />
System Settings > Qt Graphics System<br />
<br />
For more information, consult this [http://apachelog.wordpress.com/2010/09/05/qt-graphics-system-kcm/ KDE Developer blog entry] and/or this [http://labs.trolltech.com/blogs/2009/12/18/qt-graphics-and-performance-the-raster-engine/ Qt Developer blog entry].<br />
<br />
==== Low 3D desktop performance====<br />
<br />
KDE begins with desktop effects enabled. Older cards may be insufficient for 3D desktop acceleration. You can disable desktop effects in:<br />
System Settings > Desktop Effects<br />
and you can toggle desktop effects with {{ic|Alt+Shift+F12}}.<br />
<br />
{{Note| You may encounter such problems with 3D desktop performance even when using a more powerful graphics card, especially the catalyst proprietary driver ({{ic|fglrx}}). This driver is known for having problems with 3D acceleration. Visit [[ATI|the ATI Wiki page]] for more troubleshooting.}}<br />
<br />
==== Desktop compositing is disabled on my system with a modern Nvidia GPU ====<br />
<br />
Sometimes, KWin may have settings in its configuration file ({{ic|kwinrc}}) that ''may'' cause a problem on re-activating the 3D desktop {{ic|OpenGL}} compositing. That could be caused randomly (for example, due to a sudden Xorg crash or restart, and it gets corrupted), so, in case that happens, delete your {{ic|~/.kde4/share/config/kwinrc}} file and relogin. The KWin settings will turn to the KDE default ones and the problem should be probably gone.<br />
<br />
==== Flickering in fullscreen when compositing is enabled ====<br />
<br />
As of KDE SC 4.6.0, there is an option in ''Sytem Settings > Desktop Effect > Advanced > Suspend desktop effects for fullscreen windows''. Uncheck it would tell kwin to disable unredirect fullscren.<br />
<br />
==== Screen Tearing with desktop compositing enabled ====<br />
<br />
KWin may suffer from [[Wikipedia:Screen tearing|screen tearing]] while desktop effects are enabled. Uncheck the VSync option under ''System Settings > Desktop Effects > Advanced > Use Vsync''.<br />
<br />
{{Note|With the release of KDE 4.11, several new Vsync options have been added, which may help with screen tearing.}}<br />
<br />
For proprietary driver users, ensure that the driver's VSync option is enabled (''amdccle'' for [[Catalyst]] users, and ''nvidia-settings'' for [[NVIDIA]] users).<br />
<br />
==== Display settings lost on reboot (multiple monitors) ====<br />
There is a [https://bugs.kde.org/show_bug.cgi?id=346961 bug] in kscreen that makes it forgets dual screen settings after reboot with certain displays.<br />
A possible workaround is to delete kscreen and make sure that your screen resolution is specified in a xorg.conf file:<br />
* For Nouveau you can use the template at [[Nouveau#Dual_Head]], just edit it to suit your setup.<br />
* For the proprietary nvidia driver you can use the [[NVIDIA#Using_NVIDIA_Settings|nvidia-settings]] utility as root to write the config file.<br />
<br />
''' Other suggestion '''<br />
<br />
Installing {{Pkg|kscreen4}} might fix the problem unless your screens share the same EDID. Kscreen is the improved screen management software for KDE, more information can be found [https://fedoraproject.org/wiki/Changes/KScreen?rd=Features/KScreen here].<br />
<br />
=== Sound problems under KDE ===<br />
<br />
==== ALSA related problems ====<br />
<br />
{{Note|First make sure you have {{Pkg|alsa-lib}} and {{Pkg|alsa-utils}} installed.}}<br />
<br />
===== "Falling back to default" messages when trying to listen to any sound in KDE =====<br />
<br />
When you encounter such messages:<br />
The audio playback device ''name_of_the_sound_device'' does not work.<br />
Falling back to default<br />
Go to:<br />
System Settings > Multimedia > Phonon<br />
and set the device named {{ic|default}} above all the other devices in each box you see.<br />
<br />
===== MP3 files cannot be played when using the GStreamer Phonon backend =====<br />
<br />
This can be solved by installing the GStreamer libav plugin (package {{Pkg|gst-libav}}). If you still encounter problems, you can try changing the Phonon backend used by installing another such as {{Pkg|phonon-qt4-vlc}} or {{Pkg|phonon-qt5-vlc}}.<br />
Then, make sure the backend is preferred via:<br />
<br />
System Settings > Multimedia > Phonon > Backend (tab)<br />
<br />
=== Konsole does not save commands' history ===<br />
<br />
By default console command history is saved only when you type 'exit' in console. When you close Konsole with 'x' in the corner it does not happen.<br />
To enable autosaving after every command execution:<br />
<br />
{{hc|~/.bashrc|<nowiki><br />
shopt -s histappend<br />
[[ "${PROMPT_COMMAND}" ]] && PROMPT_COMMAND="$PROMPT_COMMAND;history -a" || PROMPT_COMMAND="history -a"<br />
</nowiki>}}<br />
<br />
=== KDE password prompts display three bullets per char ===<br />
<br />
This setting can be changed at ''System Settings > Account Details > Password & User Account'':<br />
* Show one bullet for each letter<br />
* Show three bullets for each letter<br />
* Show nothing<br />
<br />
=== Dolphin and File Dialogs are extremely slow to start ===<br />
<br />
This may be caused by the upower service. If the upower service is not needed on your system, it can be disabled:<br />
<br />
# systemctl disable upower<br />
# systemctl mask upower<br />
<br />
Obviously this will not have any side effect on a desktop system.<br />
<br />
=== Default PDF viewer in GTK applications under KDE ===<br />
<br />
In some cases when you have installed [[Inkscape]], [[Gimp]] or other graphic programs, GTK applications ([[Firefox]] among all) might not select Okular as the default PDF application, and they are not going to follow the KDE settings on default applications. You can use the following user command to make Okular the default application again.<br />
<br />
$ xdg-mime default kde4-okularApplication_pdf.desktop application/pdf<br />
<br />
If you are using a different PDF viewer application, or a different mime-type is misbehaving, you should change {{ic|kde4-okularApplication_pdf.desktop}} and {{ic|application/pdf}} respectively according to your needs.<br />
<br />
For more information, consult [[Default applications]] wiki page.<br />
<br />
=== Inotify folder watch limit ===<br />
<br />
If you get the following error:<br />
<br />
KDE Baloo Filewatch service reached the inotify folder watch limit. File changes may be ignored.<br />
<br />
Then you will need to increase the inotify folder watch limit:<br />
<br />
# echo 10000 > /proc/sys/fs/inotify/max_user_watches<br />
<br />
To make changes permanent, create {{ic|/etc/sysctl.d/90-inotify.conf}} with<br />
<br />
#increase inotify watch limit<br />
fs.inotify.max_user_watches = 10000<br />
<br />
== Unstable releases ==<br />
<br />
When KDE is reaching beta or RC milestone, KDE "unstable" packages are uploaded to the ''kde-unstable'' repository. They stay there until KDE is declared stable and passes to the ''extra'' repository.<br />
<br />
You can add ''kde-unstable'' with:<br />
<br />
{{hc|/etc/pacman.conf|2=<br />
[kde-unstable]<br />
Include = /etc/pacman.d/mirrorlist<br />
}}<br />
<br />
{{Warning|Make sure to add these lines '''before''' the ''extra'' repository. Adding the section after ''extra'' will cause [[pacman]] to prefer the older packages in the extra repository. {{ic|pacman -Syu}} will not install them, and will warn that they are "too new" if installed manually. Also, some of the libraries will stay at the older versions, which may cause file conflicts and/or instability!}}<br />
<br />
# ''kde-unstable'' is based upon ''testing''. Therefore, you need to enable the repositories in the following order: ''kde-unstable'', ''testing'', ''core'', ''extra'', ''community-testing'', ''community''.<br />
# To update from a previous KDE installation, run: {{ic|# pacman -Syu}} or {{ic|# pacman -S kde-unstable/kde}}<br />
# If you do not have KDE installed, you might have difficulties to install it by using groups (limitation of pacman)<br />
# '''Subscribe and read the [https://mailman.archlinux.org/pipermail/arch-dev-public/ arch-dev-public] mailing list'''<br />
# Make sure [[#Distro_and_Upstream_bug_report|you make bug reports]] if you find any problems.<br />
<br />
== KDE forks ==<br />
<br />
=== Trinity ===<br />
<br />
From the release of KDE 4.x, the developers dropped support for KDE 3.5.x. Trinity Desktop Environment is a fork of KDE3 developed by Timothy Pearson ([http://trinitydesktop.org/ trinitydesktop.org]). This project aims to keep the KDE3.5 computing style alive, as well as polish off any rough edges that were present as of KDE 3.5.10. See [[Trinity]] for more info.<br />
<br />
== Bugs ==<br />
<br />
It is preferrable that if you find a minor or serious bug, you should visit [https://bugs.archlinux.org the Arch Bug Tracker] or/and [http://bugs.kde.org KDE Bug Tracker] in order to report that. Make sure that you are clear about what you want to report.<br />
<br />
If you have any problem and you write about in on the Arch forums, first make sure that you have '''fully''' updated your system using a good sync mirror (check [https://www.archlinux.de/?page=MirrorStatus here]) or try [[Reflector]].<br />
<br />
== See also ==<br />
<br />
* [http://www.kde.org KDE homepage]<br />
* [https://bugs.kde.org KDE bug tracker]<br />
* [https://projects.kde.org KDE Projects]<br />
* [http://blog.martin-graesslin.com/blog/kategorien/kde/ Martin Graesslin's blog]</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Inkscape&diff=367944Inkscape2015-03-30T21:53:55Z<p>JKAbrams: </p>
<hr />
<div>[[Category:Graphics and desktop publishing]]<br />
[[de:Inkscape]]<br />
{{stub}}<br />
[http://inkscape.org/ Inkscape] is a vector graphics editor application. It is distributed under a free software license, the GNU GPL. Its stated goal is to become a powerful graphics tool while being fully compliant with the XML, SVG, and CSS standards.[https://en.wikipedia.org/wiki/Inkscape]<br />
<br />
== Installation ==<br />
{{pkg|inkscape}} can be installed from the [[official repositories]].<br />
<br />
=== Without GNOME dependencies ===<br />
Inkscape has quite a few [[GNOME]] dependencies, which can be annoying to users of other environments. If you do not want these, you can compile {{AUR|inkscape-bzr}} from the [[Arch User Repository|AUR]].<br />
<br />
==Troubleshooting==<br />
<br />
=== Build error with libpng 1.2.x ===<br />
If inkscape fails to build with the following error:<br />
In file included from /usr/include/libpng12/png.h:474,<br />
from sp-image.cpp:44:<br />
/usr/include/libpng12/pngconf.h:328: error: expected constructor, destructor, or type conversion before '.' token<br />
/usr/include/libpng12/pngconf.h:329: error: '__dont__' does not name a type<br />
<br />
You should be able to solve that by simply commenting the two mentioned Lines in {{ic|/usr/include/libpng12/pngconf.h}} out:<br />
<br />
//__pngconf.h__ already includes setjmp.h;<br />
//__dont__ include it again.;<br />
<br />
(I have got no idea what else those changes influence, so you might want to undo them after inkscape is built. This could be related to Debian Bug#522477 and might get fixed in libpng 1.4)<br />
<br />
=== Segfaults with qtcurve-gtk2 ===<br />
There is a problem with qtcurve-gtk2 1.8.18-3 that makes inkscape segfault shortly after launch. The bug is fixed upstream ([https://bugs.kde.org/show_bug.cgi?id=343704#c3 Bug 343704]) but no release is yet available and the AUR package qtcurve-git is not compatible with KDE Frameworks 5. Best option today to use qtcurve and inkscape is to use speps patched packages from [https://bugs.archlinux.org/task/43631#comment132113 FS#43631].<br />
<br />
== See also ==<br />
* [[Multimedia in Arch Linux]]<br />
* [http://inkscape.org/ Inkscape Homepage]<br />
* [[Wikipedia:Inkscape|Inkscape at Wikipedia]]</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Quassel&diff=343323Quassel2014-11-05T15:37:10Z<p>JKAbrams: </p>
<hr />
<div>[[Category:Internet Relay Chat]]<br />
Quassel (sometimes referred to as Quassel IRC) is a cross-platform IRC client introduced in 2008. It is dual-licensed under GPLv2 and GPLv3, while most graphical data is licensed under the LGPL and provided by the [http://www.oxygen-icons.org/ Oxygen Team]. The client part of Quassel uses the Qt framework for its user interface.<br />
<br />
== Structure ==<br />
<br />
Quassel is split up into two parts by a server-client model; a client and a core. There is also a monolithic version of the official client that does not require a core. The core(server) is the application that actually does the communication with IRC networks, while the client(s) only communicates with the core. This gives the user a flexibility of having the same instance to IRC networks on different clients (e.g. mobile, desktop at the same time).<br />
<br />
{{Note|Arch Linux used to have two packages, where quassel-monolighic was part of quassel-client, this was fixed in {{Bug|39756}} but if you used to run the monolithic version, you might run into problems after the update. You could try by just installing quassel-monolithic or if that doesn't help see troubleshooting below.}}<br />
<br />
== Installation ==<br />
<br />
=== Basic usage ===<br />
<br />
Just install the {{Pkg|quassel-monolithic}} package if you only want to use Quassel from a single computer.<br />
<br />
=== Setting up multiple clients to connect through the same core ===<br />
<br />
Install {{Pkg|quassel-core}} and {{Pkg|quassel-client}}.<br />
<br />
Generate a certificate (this will be valid for 4 years, after which it needs to be reissued, just change the -days to another value if you so desire):<br />
{{bc|# openssl req -x509 -nodes -days 365 -newkey rsa:4096 -keyout /var/lib/quassel/quasselCert.pem -out /var/lib/quassel/quasselCert.pem}}<br />
As this is a self-signed certificate, you can type whatever you want in the fields.<br />
<br />
Open port 4242 in your firewall.<br />
<br />
Start core:<br />
{{bc|# systemctl start quassel}}<br />
<br />
Start the client and connect to core:<br />
{{bc|$ quasselclient}}<br />
<br />
Accept your self-created certificate.<br />
<br />
Now set up your IRC-servers and IRC-nicknames on the core.<br />
<br />
{{Note|As this is the first time you connected to the core, you should see a wizard where you can set up the first user-account. If you don't get this wizard, your settings might be messed up, see troubleshooting below.}}<br />
<br />
Once it all works, you can set it up to start automatically through on system boot:<br />
<br />
{{bc|# systemctl enable quassel}}<br />
<br />
This is supposed to work but doesn't because of a bug {{Bug|38950}} but it's easy to work around:<br />
<br />
Copy the system service file to make a override in /etc/systemd/system/ (then when the bug is fixed you can just remove this file)<br />
{{bc|# cp /usr/lib/systemd/system/quassel.service /etc/systemd/system/}}<br />
<br />
Then edit the file /etc/systemd/system/quassel.service and remove --listen=${LISTEN} from ExecStart.<br />
<br />
== Troubleshooting ==<br />
<br />
If you were previously using quassel-monolithic, your settings might be messed up.<br />
Close qasselcore.<br />
Move your settings database to a bakup copy:<br />
{{bc|$ mv /~/.config/quassel-irc.org/quassel-storage.sqlite /~/.config/quassel-irc.org/quassel-storage.sqlite.bak}}<br />
<br />
Then start quasselcore again and connect from your client, you should now get the wizard to show, however, all settings will have to be re-entered.</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Quassel&diff=343322Quassel2014-11-05T15:33:31Z<p>JKAbrams: </p>
<hr />
<div>[[Category:Internet Relay Chat]]<br />
Quassel (sometimes referred to as Quassel IRC) is a cross-platform IRC client introduced in 2008. It is dual-licensed under GPLv2 and GPLv3, while most graphical data is licensed under the LGPL and provided by the [http://www.oxygen-icons.org/ Oxygen Team]. The client part of Quassel uses the Qt framework for its user interface.<br />
<br />
== Structure ==<br />
<br />
Quassel is split up into two parts by a server-client model; a client and a core. There is also a monolithic version of the official client that does not require a core. The core(server) is the application that actually does the communication with IRC networks, while the client(s) only communicates with the core. This gives the user a flexibility of having the same instance to IRC networks on different clients (e.g. mobile, desktop at the same time).<br />
<br />
{{Note|Arch Linux used to have two packages, where quassel-monolighic was part of quassel-client, this was fixed in {{Bug|39756}} but if you used to run the monolithic version, you might run into problems after the update. You could try by just installing quassel-monolithic or if that doesn't help see troubleshooting below.}}<br />
<br />
== Installation ==<br />
<br />
=== Basic usage ===<br />
<br />
Just install the {{Pkg|quassel-monolithic}} package if you only want to use Quassel from a single computer.<br />
<br />
=== Setting up multiple clients to connect through the same core ===<br />
<br />
Install {{Pkg|quassel-core}} and {{Pkg|quassel-client}}.<br />
<br />
Generate a certificate (this will be valid for 4 years, after which it needs to be reissued, just change the -days to another value if you so desire):<br />
{{bc|# openssl req -x509 -nodes -days 365 -newkey rsa:4096 -keyout /var/lib/quassel/quasselCert.pem -out /var/lib/quassel/quasselCert.pem}}<br />
As this is a self-signed certificate, you can type whatever you want in the fields.<br />
<br />
Open port 4242 in your firewall.<br />
<br />
Start core:<br />
{{bc|# systemctl start quassel}}<br />
<br />
Start the client and connect to core:<br />
{{bc|$ quasselclient}}<br />
<br />
Accept your self-created certificate.<br />
<br />
Now set up your IRC-servers and IRC-nicknames on the core.<br />
<br />
{{Note|As this is the first time you connected to the core, you should see a wizard where you can set up the first user-account. If you don't get this wizard, your settings might be messed up, see troubleshooting below.}}<br />
<br />
Once it all works, you can set it up to start automatically through on system boot:<br />
<br />
{{bc|# systemctl enable quassel}}<br />
<br />
This is supposed to work but doesn't because of a bug {{Bug|38950}} but it's easy to work around:<br />
<br />
Copy the system service file to make a override in /etc/systemd/system/<br />
{{bc|# cp /usr/lib/systemd/system/quassel.service /etc/systemd/system/}}<br />
<br />
Then edit the file /etc/systemd/system/quassel.service and remove --listen=${LISTEN} from ExecStart.<br />
<br />
== Troubleshooting ==<br />
<br />
If you were previously using quassel-monolithic, your settings might be messed up.<br />
Close qasselcore.<br />
Move your settings database to a bakup copy:<br />
{{bc|$ mv /~/.config/quassel-irc.org/quassel-storage.sqlite /~/.config/quassel-irc.org/quassel-storage.sqlite.bak}}<br />
<br />
Then start quasselcore again and connect from your client, you should now get the wizard to show, however, all settings will have to be re-entered.</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Quassel&diff=340790Quassel2014-10-19T18:43:18Z<p>JKAbrams: This is better.</p>
<hr />
<div>[[Category:Internet Relay Chat]]<br />
Quassel (sometimes referred to as Quassel IRC) is a cross-platform IRC client introduced in 2008. It is dual-licensed under GPLv2 and GPLv3, while most graphical data is licensed under the LGPL and provided by the [http://www.oxygen-icons.org/ Oxygen Team]. The client part of Quassel uses the Qt framework for its user interface.<br />
<br />
== Structure ==<br />
<br />
Quassel is split up into two parts by a server-client model; a client and a core. There is also a monolithic version of the official client that does not require a core. The core(server) is the application that actually does the communication with IRC networks, while the client(s) only communicates with the core. This gives the user a flexibility of having the same instance to IRC networks on different clients (e.g. mobile, desktop at the same time).<br />
<br />
{{Note|Arch Linux used to have two packages, where quassel-monolighic was part of quassel-client, this was fixed in {{Bug|39756}} but if you used to run the monolithic version, you might run into problems after the update. You could try by just installing quassel-monolithic or if that doesn't help see troubleshooting below.}}<br />
<br />
== Installation ==<br />
<br />
=== Basic usage ===<br />
<br />
Just install the {{Pkg|quassel-monolighic}} package if you only want to use Quassel from a single computer.<br />
<br />
=== Setting up multiple clients to connect through the same core ===<br />
<br />
Install {{Pkg|quassel-core}} and {{Pkg|quassel-client}}.<br />
<br />
Generate a certificate (this will be valid for 4 years, after which it needs to be reissued, just change the -days to another value if you so desire):<br />
{{bc|# openssl req -x509 -nodes -days 365 -newkey rsa:4096 -keyout /var/lib/quassel/quasselCert.pem -out /var/lib/quassel/quasselCert.pem}}<br />
As this is a self-signed certificate, you can type whatever you want in the fields.<br />
<br />
Open port 4242 in your firewall.<br />
<br />
Start core:<br />
{{bc|# systemctl start quassel}}<br />
<br />
Start the client and connect to core:<br />
{{bc|$ quasselclient}}<br />
<br />
Accept your self-created certificate.<br />
<br />
Now set up your IRC-servers and IRC-nicknames on the core.<br />
<br />
{{Note|As this is the first time you connected to the core, you should see a wizard where you can set up the first user-account. If you don't get this wizard, your settings might be messed up, see troubleshooting below.}}<br />
<br />
Once it all works, you can set it up to start automatically through on system boot:<br />
<br />
{{bc|# systemctl enable quassel}}<br />
<br />
== Troubleshooting ==<br />
<br />
If you were previously using quassel-monolithic, your settings might be messed up.<br />
Close qasselcore.<br />
Move your settings database to a bakup copy:<br />
{{bc|$ mv /~/.config/quassel-irc.org/quassel-storage.sqlite /~/.config/quassel-irc.org/quassel-storage.sqlite.bak}}<br />
<br />
Then start quasselcore again and connect from your client, you should now get the wizard to show, however, all settings will have to be re-entered.</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Quassel&diff=340788Quassel2014-10-19T18:31:59Z<p>JKAbrams: </p>
<hr />
<div>[[Category:Internet Relay Chat]]<br />
Quassel (sometimes referred to as Quassel IRC) is a cross-platform IRC client introduced in 2008. It is dual-licensed under GPLv2 and GPLv3, while most graphical data is licensed under the LGPL and provided by the [http://www.oxygen-icons.org/ Oxygen Team]. The client part of Quassel uses the Qt framework for its user interface.<br />
<br />
== Structure ==<br />
<br />
Quassel is split up into two parts by a server-client model; a client and a core. There is also a monolithic version of the official client that does not require a core. The core(server) is the application that actually does the communication with IRC networks, while the client(s) only communicates with the core. This gives the user a flexibility of having the same instance to IRC networks on different clients (e.g. mobile, desktop at the same time).<br />
<br />
{{Note|Arch Linux used to have two packages, where quassel-monolighic was part of quassel-client, this was fixed in {{Bug|39756}} but if you used to run the monolithic version, you might run into problems after the update. You could try by just installing quassel-monolithic or if that doesn't help see troubleshooting below.}}<br />
<br />
== Installation ==<br />
<br />
=== Basic usage ===<br />
<br />
Just install the {{Pkg|quassel-monolighic}} package if you only want to use Quassel from a single computer.<br />
<br />
=== Setting up multiple clients to connect through the same core ===<br />
<br />
Install {{Pkg|quassel-core}} and {{Pkg|quassel-client}}.<br />
<br />
Generate a certificate (this will be valid for 4 years, after which it needs to be reissued, just change the -days to another value if you so desire):<br />
{{bc|# openssl req -x509 -nodes -days 365 -newkey rsa:4096 -keyout /var/lib/quassel/quasselCert.pem -out /var/lib/quassel/quasselCert.pem}}<br />
As this is a self-signed certificate, you can type whatever you want in the fields.<br />
<br />
Start core (running from the command line will display any errors right away):<br />
{{bc|# quasselcore}}<br />
<br />
Open port 4242 in your firewall.<br />
<br />
Start the client and connect to core:<br />
{{bc|$ quasselclient}}<br />
<br />
Accept your self-created certificate.<br />
<br />
Now set up your IRC-servers and IRC-nicknames on the core.<br />
<br />
{{Note|As this is the first time you connected to the core, you should see a wizard where you can set up the first user-account. If you don't get this wizard, your settings might be messed up, see troubleshooting below.}}<br />
<br />
Once it all works, you can close quasselcore and set it up to start automatically through systemd:<br />
<br />
{{bc|# systemctl enable quassel<br />
# systemctl start quassel}}<br />
<br />
== Troubleshooting ==<br />
<br />
If you were previously using quassel-monolithic, your settings might be messed up.<br />
Close qasselcore.<br />
Move your settings database to a bakup copy:<br />
{{bc|$ mv /~/.config/quassel-irc.org/quassel-storage.sqlite /~/.config/quassel-irc.org/quassel-storage.sqlite.bak}}<br />
<br />
Then start quasselcore again and connect from your client, you should now get the wizard to show, however, all settings will have to be re-entered.</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Quassel&diff=340787Quassel2014-10-19T18:31:41Z<p>JKAbrams: Changed to issuing the cert as root and as it didn't work if you start it from systemd later.</p>
<hr />
<div>[[Category:Internet Relay Chat]]<br />
Quassel (sometimes referred to as Quassel IRC) is a cross-platform IRC client introduced in 2008. It is dual-licensed under GPLv2 and GPLv3, while most graphical data is licensed under the LGPL and provided by the [http://www.oxygen-icons.org/ Oxygen Team]. The client part of Quassel uses the Qt framework for its user interface.<br />
<br />
== Structure ==<br />
<br />
Quassel is split up into two parts by a server-client model; a client and a core. There is also a monolithic version of the official client that does not require a core. The core(server) is the application that actually does the communication with IRC networks, while the client(s) only communicates with the core. This gives the user a flexibility of having the same instance to IRC networks on different clients (e.g. mobile, desktop at the same time).<br />
<br />
{{Note|Arch Linux used to have two packages, where quassel-monolighic was part of quassel-client, this was fixed in {{Bug|39756}} but if you used to run the monolithic version, you might run into problems after the update. You could try by just installing quassel-monolithic or if that doesn't help see troubleshooting below.}}<br />
<br />
== Installation ==<br />
<br />
=== Basic usage ===<br />
<br />
Just install the {{Pkg|quassel-monolighic}} package if you only want to use Quassel from a single computer.<br />
<br />
=== Setting up multiple clients to connect through the same core ===<br />
<br />
Install {{Pkg|quassel-core}} and {{Pkg|quassel-client}}.<br />
<br />
Generate a certificate (this will be valid for 4 years, after which it needs to be reissued, just change the -days to another value if you so desire):<br />
{{bc|$ openssl req -x509 -nodes -days 365 -newkey rsa:4096 -keyout /var/lib/quassel/quasselCert.pem -out /var/lib/quassel/quasselCert.pem}}<br />
As this is a self-signed certificate, you can type whatever you want in the fields.<br />
<br />
Start core (running from the command line will display any errors right away):<br />
{{bc|# quasselcore}}<br />
<br />
Open port 4242 in your firewall.<br />
<br />
Start the client and connect to core:<br />
{{bc|$ quasselclient}}<br />
<br />
Accept your self-created certificate.<br />
<br />
Now set up your IRC-servers and IRC-nicknames on the core.<br />
<br />
{{Note|As this is the first time you connected to the core, you should see a wizard where you can set up the first user-account. If you don't get this wizard, your settings might be messed up, see troubleshooting below.}}<br />
<br />
Once it all works, you can close quasselcore and set it up to start automatically through systemd:<br />
<br />
{{bc|# systemctl enable quassel<br />
# systemctl start quassel}}<br />
<br />
== Troubleshooting ==<br />
<br />
If you were previously using quassel-monolithic, your settings might be messed up.<br />
Close qasselcore.<br />
Move your settings database to a bakup copy:<br />
{{bc|$ mv /~/.config/quassel-irc.org/quassel-storage.sqlite /~/.config/quassel-irc.org/quassel-storage.sqlite.bak}}<br />
<br />
Then start quasselcore again and connect from your client, you should now get the wizard to show, however, all settings will have to be re-entered.</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Quassel&diff=340786Quassel2014-10-19T18:17:38Z<p>JKAbrams: </p>
<hr />
<div>[[Category:Internet Relay Chat]]<br />
Quassel (sometimes referred to as Quassel IRC) is a cross-platform IRC client introduced in 2008. It is dual-licensed under GPLv2 and GPLv3, while most graphical data is licensed under the LGPL and provided by the [http://www.oxygen-icons.org/ Oxygen Team]. The client part of Quassel uses the Qt framework for its user interface.<br />
<br />
== Structure ==<br />
<br />
Quassel is split up into two parts by a server-client model; a client and a core. There is also a monolithic version of the official client that does not require a core. The core(server) is the application that actually does the communication with IRC networks, while the client(s) only communicates with the core. This gives the user a flexibility of having the same instance to IRC networks on different clients (e.g. mobile, desktop at the same time).<br />
<br />
{{Note|Arch Linux used to have two packages, where quassel-monolighic was part of quassel-client, this was fixed in {{Bug|39756}} but if you used to run the monolithic version, you might run into problems after the update. You could try by just installing quassel-monolithic or if that doesn't help see troubleshooting below.}}<br />
<br />
== Installation ==<br />
<br />
=== Basic usage ===<br />
<br />
Just install the {{Pkg|quassel-monolighic}} package if you only want to use Quassel from a single computer.<br />
<br />
=== Setting up multiple clients to connect through the same core ===<br />
<br />
Install {{Pkg|quassel-core}} and {{Pkg|quassel-client}}.<br />
<br />
Generate a certificate:<br />
{{bc|$ openssl req -x509 -nodes -days 365 -newkey rsa:4096 -keyout ~/.config/quassel-irc.org/quasselCert.pem -out ~/.config/quassel-irc.org/quasselCert.pem}}<br />
As this is a self-signed certificate, you can type whatever you want in the fields.<br />
<br />
Start core (running from the command line will display any errors right away):<br />
{{bc|$ quasselcore}}<br />
<br />
Open port 4242 in your firewall.<br />
<br />
Start the client and connect to core:<br />
{{bc|$ quasselclient}}<br />
<br />
Accept your self-created certificate.<br />
<br />
Now set up your IRC-servers and IRC-nicknames on the core.<br />
<br />
{{Note|As this is the first time you connected to the core, you should see a wizard where you can set up the first user-account. If you don't get this wizard, your settings might be messed up, see troubleshooting below.}}<br />
<br />
Once it all works, you can close quasselcore and set it up to start automatically through systemd:<br />
<br />
{{bc|# systemctl enable quassel<br />
# systemctl start quassel}}<br />
<br />
== Troubleshooting ==<br />
<br />
If you were previously using quassel-monolithic, your settings might be messed up.<br />
Close qasselcore.<br />
Move your settings database to a bakup copy:<br />
{{bc|$ mv /~/.config/quassel-irc.org/quassel-storage.sqlite /~/.config/quassel-irc.org/quassel-storage.sqlite.bak}}<br />
<br />
Then start quasselcore again and connect from your client, you should now get the wizard to show, however, all settings will have to be re-entered.</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Talk:Quassel&diff=340785Talk:Quassel2014-10-19T18:17:16Z<p>JKAbrams: </p>
<hr />
<div><br />
== Problems after upgrade ==<br />
Is there a better way to transfer settings from the previous quassel-client package to the new quassel-monolithic that does not mess up the settings? [[User:JKAbrams|JKAbrams]] ([[User talk:JKAbrams|talk]]) 18:16, 19 October 2014 (UTC)</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Talk:Quassel&diff=340784Talk:Quassel2014-10-19T18:16:03Z<p>JKAbrams: Created page with " == Problems after upgrade? == Is there a better way to transfer settings from the previous quassel-client package to the new quassel-monolithic that does not mess up the sett..."</p>
<hr />
<div><br />
== Problems after upgrade? ==<br />
Is there a better way to transfer settings from the previous quassel-client package to the new quassel-monolithic that does not mess up the settings? [[User:JKAbrams|JKAbrams]] ([[User talk:JKAbrams|talk]]) 18:16, 19 October 2014 (UTC)</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Quassel&diff=340783Quassel2014-10-19T18:14:04Z<p>JKAbrams: Final fix.</p>
<hr />
<div>[[Category:Internet Relay Chat]]<br />
Quassel (sometimes referred to as Quassel IRC) is a cross-platform IRC client introduced in 2008. It is dual-licensed under GPLv2 and GPLv3, while most graphical data is licensed under the LGPL and provided by the [http://www.oxygen-icons.org/ Oxygen Team]. The client part of Quassel uses the Qt framework for its user interface.<br />
<br />
== Structure ==<br />
<br />
Quassel is split up into two parts by a server-client model; a client and a core. There is also a monolithic version of the official client that does not require a core. The core(server) is the application that actually does the communication with IRC networks, while the client(s) only communicates with the core. This gives the user a flexibility of having the same instance to IRC networks on different clients (e.g. mobile, desktop at the same time).<br />
<br />
{{Note|Arch Linux used to have two packages, where quassel-monolighic was part of quassel-client, this was fixed in {{Bug|39756}} but if you used to run the monolithic version, you might run into problems after the update. You could try by just installing quassel-monolithic or if that doesn't help see troubleshooting below.}}<br />
<br />
== Installation ==<br />
<br />
=== Basic usage ===<br />
<br />
Just install the {{Pkg|quassel-monolighic}} package if you only want to use Quassel from a single computer.<br />
<br />
=== Setting up multiple clients to connect through the same core ===<br />
<br />
Install {{Pkg|quassel-core}} and {{Pkg|quassel-client}}.<br />
<br />
Generate a certificate:<br />
{{bc|$ openssl req -x509 -nodes -days 365 -newkey rsa:4096 -keyout ~/.config/quassel-irc.org/quasselCert.pem -out ~/.config/quassel-irc.org/quasselCert.pem}}<br />
As this is a self-signed certificate, you can type whatever you want in the fields.<br />
<br />
Start core (running from the command line will display any errors right away):<br />
{{bc|$ quasselcore}}<br />
<br />
Open port 4242 in your firewall.<br />
<br />
Start the client and connect to core:<br />
{{bc|$ quasselclient}}<br />
<br />
Accept the your self-created certificate.<br />
<br />
Now set up your IRC-servers and IRC-nicknames on the core.<br />
<br />
{{Note|As this is the first time you connected to the core, you should see a wizard where you can set up the first user-account. If you don't get this wizard, your settings might be messed up, see troubleshooting below.}}<br />
<br />
Once it all works, you can close quasselcore and set it up to start automatically through systemd:<br />
<br />
{{bc|# systemctl enable quassel<br />
# systemctl start quassel}}<br />
<br />
== Troubleshooting ==<br />
<br />
If you were previously using quassel-monolithic, your settings might be messed up.<br />
Close qasselcore.<br />
Move your settings database to a bakup copy:<br />
{{bc|$ mv /~/.config/quassel-irc.org/quassel-storage.sqlite /~/.config/quassel-irc.org/quassel-storage.sqlite.bak}}<br />
<br />
Then start quasselcore again and connect from your client, you should now get the wizard to show, however, all settings will have to be re-entered.</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Quassel&diff=340782Quassel2014-10-19T18:11:25Z<p>JKAbrams: I think that would be it.</p>
<hr />
<div>[[Category:Internet Relay Chat]]<br />
Quassel (sometimes referred to as Quassel IRC) is a cross-platform IRC client introduced in 2008. It is dual-licensed under GPLv2 and GPLv3, while most graphical data is licensed under the LGPL and provided by the [http://www.oxygen-icons.org/ Oxygen Team]. The client part of Quassel uses the Qt framework for its user interface.<br />
<br />
== Structure ==<br />
<br />
Quassel is split up into two parts by a server-client model; a client and a core. There is also a monolithic version of the official client that does not require a core. The core(server) is the application that actually does the communication with IRC networks, while the client(s) only communicates with the core. This gives the user a flexibility of having the same instance to IRC networks on different clients (e.g. mobile, desktop at the same time).<br />
<br />
Arch Linux used to have two packages, where the quassel-monolighic was part of the quassel-client, this was fixed but if you used to run the monolithic version, you might run into problems after the update. See troubleshooting below.<br />
<br />
== Installation ==<br />
<br />
=== Basic usage ===<br />
<br />
Just install the {{Pkg|quassel-monolighic}} package if you only want to use Quassel from a single computer.<br />
<br />
=== Setting up multiple clients to connect through the same core ===<br />
<br />
Install {{Pkg|quassel-core}} and {{Pkg|quassel-client}}.<br />
<br />
Generate a certificate:<br />
{{bc|$ openssl req -x509 -nodes -days 365 -newkey rsa:4096 -keyout ~/.config/quassel-irc.org/quasselCert.pem -out ~/.config/quassel-irc.org/quasselCert.pem}}<br />
As this is a self-signed certificate, you can type whatever you want in the fields.<br />
<br />
Start core (running from the command line will display any errors right away):<br />
{{bc|$ quasselcore}}<br />
<br />
Open port 4242 in your firewall.<br />
<br />
Start the client and connect to core:<br />
{{bc|$ quasselclient}}<br />
<br />
Accept the your self-created certificate.<br />
<br />
Now set up your IRC-servers and IRC-nicknames on the core.<br />
<br />
{{Note|As this is the first time you connected to the core, you should see a wizard where you can set up the first user-account. If you don't get this wizard, your settings might be messed up, see troubleshooting below.}}<br />
<br />
Once it all works, you can close quasselcore and set it up to start automatically through systemd:<br />
<br />
{{bc|# systemctl enable quassel<br />
# systemctl start quassel}}<br />
<br />
== Troubleshooting ==<br />
<br />
If you were previously using quassel-monolithic, your settings might be messed up.<br />
Close qasselcore.<br />
Move your settings database to a bakup copy:<br />
{{bc|$ mv /~/.config/quassel-irc.org/quassel-storage.sqlite /~/.config/quassel-irc.org/quassel-storage.sqlite.bak}}<br />
<br />
Then start quasselcore again and connect from your client, you should now get the wizard to show, however, all settings will have to be re-entered.</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Quassel&diff=340781Quassel2014-10-19T18:05:23Z<p>JKAbrams: </p>
<hr />
<div>[[Category:Internet Relay Chat]]<br />
Quassel (sometimes referred to as Quassel IRC) is a cross-platform IRC client introduced in 2008. It is dual-licensed under GPLv2 and GPLv3, while most graphical data is licensed under the LGPL and provided by the [http://www.oxygen-icons.org/ Oxygen Team]. The client part of Quassel uses the Qt framework for its user interface.<br />
<br />
== Structure ==<br />
<br />
Quassel is split up into two parts by a server-client model; a client and a core. There is also a monolithic version of the official client that does not require a core. The core(server) is the application that actually does the communication with IRC networks, while the client(s) only communicates with the core. This gives the user a flexibility of having the same instance to IRC networks on different clients (e.g. mobile, desktop at the same time).<br />
<br />
== Installation ==<br />
<br />
=== Basic usage ===<br />
<br />
Just install the {{Pkg|quassel-monolighic}} package if you only want to use quassel from a single computer.<br />
<br />
=== Setting up multiple clients to connect through the same core ===<br />
<br />
Install {{Pkg|quassel-core}} and {{Pkg|quassel-client}}.<br />
<br />
Generate a certificate:<br />
{{bc|openssl req -x509 -nodes -days 365 -newkey rsa:4096 -keyout ~/.config/quassel-irc.org/quasselCert.pem -out ~/.config/quassel-irc.org/quasselCert.pem}}<br />
As this is a self-signed certificate, you can type whatever you want in the fields.<br />
<br />
Start core (running from the command line will display any errors right away):<br />
{{bc|$ quasselcore}}<br />
<br />
Open port 4242 in your firewall.<br />
<br />
Start the client and connect to core:<br />
{{bc|$ quasselclient}}<br />
<br />
Accept the your self-created certificate.<br />
<br />
Now set up your IRC-servers and IRC-nicknames on the core.<br />
<br />
{{Note|As this is the first time you connected to the core, you should see a wizard where you can set up the first user-account. If you don't get this wizard, your settings might be messed up, see troubleshooting below.}}<br />
<br />
Once it all works, you can close quasselcore and set it up to start automatically through systemd:<br />
<br />
{{bc|# systemctl enable quassel<br />
# systemctl start quassel}}<br />
<br />
== Troubleshooting ==<br />
<br />
If you were previously using quassel-monolithic, your settings might be messed up.<br />
Close qasselcore.<br />
Move your settings database to a bakup copy:<br />
{{bc|$ mv /~/.config/quassel-irc.org/quassel-storage.sqlite /~/.config/quassel-irc.org/quassel-storage.sqlite.bak}}<br />
<br />
Then start quasselcore again and connect from your client, you should now get the wizard to show, however, all settings will have to be re-entered.</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Quassel&diff=340780Quassel2014-10-19T18:05:09Z<p>JKAbrams: </p>
<hr />
<div>[[Category:Internet Relay Chat]]<br />
<br />
Quassel (sometimes referred to as Quassel IRC) is a cross-platform IRC client introduced in 2008. It is dual-licensed under GPLv2 and GPLv3, while most graphical data is licensed under the LGPL and provided by the [http://www.oxygen-icons.org/ Oxygen Team]. The client part of Quassel uses the Qt framework for its user interface.<br />
<br />
== Structure ==<br />
<br />
Quassel is split up into two parts by a server-client model; a client and a core. There is also a monolithic version of the official client that does not require a core. The core(server) is the application that actually does the communication with IRC networks, while the client(s) only communicates with the core. This gives the user a flexibility of having the same instance to IRC networks on different clients (e.g. mobile, desktop at the same time).<br />
<br />
== Installation ==<br />
<br />
=== Basic usage ===<br />
<br />
Just install the {{Pkg|quassel-monolighic}} package if you only want to use quassel from a single computer.<br />
<br />
=== Setting up multiple clients to connect through the same core ===<br />
<br />
Install {{Pkg|quassel-core}} and {{Pkg|quassel-client}}.<br />
<br />
Generate a certificate:<br />
{{bc|openssl req -x509 -nodes -days 365 -newkey rsa:4096 -keyout ~/.config/quassel-irc.org/quasselCert.pem -out ~/.config/quassel-irc.org/quasselCert.pem}}<br />
As this is a self-signed certificate, you can type whatever you want in the fields.<br />
<br />
Start core (running from the command line will display any errors right away):<br />
{{bc|$ quasselcore}}<br />
<br />
Open port 4242 in your firewall.<br />
<br />
Start the client and connect to core:<br />
{{bc|$ quasselclient}}<br />
<br />
Accept the your self-created certificate.<br />
<br />
Now set up your IRC-servers and IRC-nicknames on the core.<br />
<br />
{{Note|As this is the first time you connected to the core, you should see a wizard where you can set up the first user-account. If you don't get this wizard, your settings might be messed up, see troubleshooting below.}}<br />
<br />
Once it all works, you can close quasselcore and set it up to start automatically through systemd:<br />
<br />
{{bc|# systemctl enable quassel<br />
# systemctl start quassel}}<br />
<br />
== Troubleshooting ==<br />
<br />
If you were previously using quassel-monolithic, your settings might be messed up.<br />
Close qasselcore.<br />
Move your settings database to a bakup copy:<br />
{{bc|$ mv /~/.config/quassel-irc.org/quassel-storage.sqlite /~/.config/quassel-irc.org/quassel-storage.sqlite.bak}}<br />
<br />
Then start quasselcore again and connect from your client, you should now get the wizard to show, however, all settings will have to be re-entered.</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Quassel&diff=340779Quassel2014-10-19T18:04:47Z<p>JKAbrams: </p>
<hr />
<div>[[Category:Internet Relay Chat]]<br />
{{Stub|This article certainly needs some work, I created this page as I saw a need for it but didn't at the time of writing have the time to finish it off.}}<br />
<br />
Quassel (sometimes referred to as Quassel IRC) is a cross-platform IRC client introduced in 2008. It is dual-licensed under GPLv2 and GPLv3, while most graphical data is licensed under the LGPL and provided by the [http://www.oxygen-icons.org/ Oxygen Team]. The client part of Quassel uses the Qt framework for its user interface.<br />
<br />
== Structure ==<br />
<br />
Quassel is split up into two parts by a server-client model; a client and a core. There is also a monolithic version of the official client that does not require a core. The core(server) is the application that actually does the communication with IRC networks, while the client(s) only communicates with the core. This gives the user a flexibility of having the same instance to IRC networks on different clients (e.g. mobile, desktop at the same time).<br />
<br />
== Installation ==<br />
<br />
=== Basic usage ===<br />
<br />
Just install the {{Pkg|quassel-monolighic}} package if you only want to use quassel from a single computer.<br />
<br />
=== Setting up multiple clients to connect through the same core ===<br />
<br />
Install {{Pkg|quassel-core}} and {{Pkg|quassel-client}}.<br />
<br />
Generate a certificate:<br />
{{bc|openssl req -x509 -nodes -days 365 -newkey rsa:4096 -keyout ~/.config/quassel-irc.org/quasselCert.pem -out ~/.config/quassel-irc.org/quasselCert.pem}}<br />
As this is a self-signed certificate, you can type whatever you want in the fields.<br />
<br />
Start core (running from the command line will display any errors right away):<br />
{{bc|$ quasselcore}}<br />
<br />
Open port 4242 in your firewall.<br />
<br />
Start the client and connect to core:<br />
{{bc|$ quasselclient}}<br />
<br />
Accept the your self-created certificate.<br />
<br />
Now set up your IRC-servers and IRC-nicknames on the core.<br />
<br />
{{Note|As this is the first time you connected to the core, you should see a wizard where you can set up the first user-account. If you don't get this wizard, your settings might be messed up, see troubleshooting below.}}<br />
<br />
Once it all works, you can close quasselcore and set it up to start automatically through systemd:<br />
<br />
{{bc|# systemctl enable quassel<br />
# systemctl start quassel}}<br />
<br />
== Troubleshooting ==<br />
<br />
If you were previously using quassel-monolithic, your settings might be messed up.<br />
Close qasselcore.<br />
Move your settings database to a bakup copy:<br />
{{bc|$ mv /~/.config/quassel-irc.org/quassel-storage.sqlite /~/.config/quassel-irc.org/quassel-storage.sqlite.bak}}<br />
<br />
Then start quasselcore again and connect from your client, you should now get the wizard to show, however, all settings will have to be re-entered.</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Quassel&diff=340778Quassel2014-10-19T18:02:24Z<p>JKAbrams: Fixup.</p>
<hr />
<div>[[Category:Internet Relay Chat]]<br />
{{Stub|This article certainly needs some work, I created this page as I saw a need for it but didn't at the time of writing have the time to finish it off.}}<br />
<br />
Quassel (sometimes referred to as Quassel IRC) is a cross-platform IRC client introduced in 2008. It is dual-licensed under GPLv2 and GPLv3, while most graphical data is licensed under the LGPL and provided by the [http://www.oxygen-icons.org/ Oxygen Team]. The client part of Quassel uses the Qt framework for its user interface.<br />
<br />
== Structure ==<br />
<br />
Quassel is split up into two parts by a server-client model; a client and a core. There is also a monolithic version of the official client that does not require a core. The core(server) is the application that actually does the communication with IRC networks, while the client(s) only communicates with the core. This gives the user a flexibility of having the same instance to IRC networks on different clients (e.g. mobile, desktop at the same time).<br />
<br />
== Installation ==<br />
<br />
=== Basic usage ===<br />
<br />
Just install the {{Pkg|quassel-monolighic}} package if you only want to use quassel from a single computer.<br />
<br />
=== Setting up multiple clients to connect through the same core ===<br />
<br />
Install {{Pkg|quassel-core}} and {{Pkg|quassel-client}}.<br />
<br />
Generate a certificate:<br />
{{bc|openssl req -x509 -nodes -days 365 -newkey rsa:4096 -keyout ~/.config/quassel-irc.org/quasselCert.pem -out ~/.config/quassel-irc.org/quasselCert.pem}}<br />
As this is a self-signed certificate, you can type whatever you want in the fields.<br />
<br />
Start core (running from the command line will display any errors right away):<br />
{{bc|$ quasselcore}}<br />
<br />
Open port 4242 in your firewall.<br />
<br />
Start the client and connect to core:<br />
{{bc|$ quasselclient}}<br />
<br />
Accept the your self-created certificate.<br />
<br />
Now set up your IRC-servers and IRC-nicknames on the core.<br />
<br />
{{Note|As this is the first time you connected to the core, you should see a wizard where you can set up the first user-account. If you don't get this wizard, your settings might be messed up, see troubleshooting below.}}<br />
<br />
Once it all works, you can close quasselcore and set it up to start automatically through systemd:<br />
<br />
{{bc|# systemctl enable quassel<br />
# systemctl start quassel}}<br />
<br />
== Troubleshooting ==<br />
<br />
If you were previously using quassel-monolithic, your settings might be messed up.<br />
Close qasselcore.<br />
Move your settings database to a bakup copy:<br />
{{bc|$ mv /~/.config/quassel-irc.org/quassel-storage.sqlite /~/.config/quassel-irc.org/quassel-storage.sqlite.bak}}<br />
<br />
The quasselcore and connect from your client, you should now get the wizard to show, however, all settings will have to be re-entered.<br />
<br />
{{Expansion|Fill me in.}}</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Quassel&diff=340760Quassel2014-10-19T13:59:30Z<p>JKAbrams: Quick statup guide, written in a hurry, might need some spell-fixes and the like, but at least a start.</p>
<hr />
<div>[[Category:Internet Relay Chat]]<br />
{{Stub|This article certainly needs some work, I created this page as I saw a need for it but didn't at the time of writing have the time to finish it off.}}<br />
<br />
Quassel (sometimes referred to as Quassel IRC) is a cross-platform IRC client introduced in 2008. It is dual-licensed under GPLv2 and GPLv3, while most graphical data is licensed under the LGPL and provided by the [http://www.oxygen-icons.org/ Oxygen Team]. The client part of Quassel uses the Qt framework for its user interface.<br />
<br />
== Structure ==<br />
<br />
Quassel is split up into two parts by a server-client model; a client and a core. There is also a monolithic version of the official client that does not require a core. The core(server) is the application that actually does the communication with IRC networks, while the client(s) only communicates with the core. This gives the user a flexibility of having the same instance to IRC networks on different clients (e.g. mobile, desktop at the same time).<br />
<br />
== Installation ==<br />
<br />
Currently Arch Linux offers two official packages; {{Pkg|quassel-core}} and {{Pkg|quassel-client}}, where the latter actually provides both the monolithic client as well as the stand-alone client (regardless of the description of the client-package, see {{Bug|39756}}).<br />
<br />
<br />
== Basic usage ==<br />
Just install the {{Pkg|quassel-monolighic}} package if you only want to use quassel from a single computer.<br />
<br />
== Setting up multiple clients to connect through the same core ==<br />
<br />
Install {{Pkg|quassel-core}} and {{Pkg|quassel-client}}<br />
<br />
Generate a certificate:<br />
openssl req -x509 -nodes -days 365 -newkey rsa:4096 -keyout ~/.config/quassel-irc.org/quasselCert.pem -out ~/.config/quassel-irc.org/quasselCert.pem<br />
<br />
Add user to core:<br />
{{bc|$ quasselcore --add-user}}<br />
<br />
{{Tip|1=Read here for more info on how to configure core users: http://bugs.quassel-irc.org/projects/quassel-irc/wiki/Manage_core_users}}<br />
<br />
Start core (running core from the command line will so any errors are displayed right away):<br />
{{bc|$ quasselcore}}<br />
<br />
Open port 4242 in your firewall.<br />
<br />
Start the client and connect to core:<br />
{{bc|$ quasselclient}}<br />
<br />
Accept the your self-created certificate.<br />
<br />
Now set up your IRC-servers and IRC-nicknames on the core.<br />
<br />
One it all works, you can close quasselcore and set it up to start automatically through systemd:<br />
<br />
{{bc|# systemctl enable quassel<br />
# systemctl start quassel}}<br />
<br />
<br />
== Troubleshooting ==<br />
<br />
If you was previously using quassel-monolithic, your settings might be messed up.<br />
Close qasselcore.<br />
Move your settings database to a bakup copy:<br />
{{bc|$ mv /~/.config/quassel-irc.org/quassel-storage.sqlite /~/.config/quassel-irc.org/quassel-storage.sqlite.bak}}<br />
<br />
The quasselcore and connect from your client, you should now get the wizard to show, however, all settings will have to be re-entered.<br />
<br />
{{Expansion|Fill me in.}}</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Apple_Keyboard&diff=334082Apple Keyboard2014-09-06T13:59:25Z<p>JKAbrams: extra t removed</p>
<hr />
<div>[[Category:Keyboards]]<br />
<br />
== More Information ==<br />
For background information see this page: https://help.ubuntu.com/community/AppleKeyboard<br />
<br />
{{Note|Some of the settings can be made permanent with a configuration file for a [[kernel module]]. For this to work, the file has to be added to FILES in [[mkinitcpio.conf]] cause the kernel module will be autoloaded while booting.}}<br />
<br />
{{Tip|If you want to use [[sudo]] to write into a system directory you can't use shell redirection. Use {{ic|tee}} like so<br />
$ echo 0 &#124; sudo tee /sys/module/hid_apple/parameters/iso_layout<br />
}}<br />
<br />
==Function keys do not work==<br />
<br />
If your {{ic|F<num>}} keys do not work, this is probably because the kernel driver for the keyboard has defaulted to using the media keys and requiring you to use the {{ic|Fn}} key to get to the {{ic|F<num>}} keys. To change this behaviour, you have to change the driver setting. Do the following as root:<br />
<br />
# echo 2 > /sys/module/hid_apple/parameters/fnmode<br />
<br />
If it tells you that the file doesn't exist, you probably have an older kernel and will have to do the following instead:<br />
<br />
# echo 2 > /sys/module/hid/parameters/pb_fnmode<br />
<br />
Place whatever option worked for you in {{ic|/etc/modprobe.d/hid_apple.conf}} to make the setting permanent:<br />
<br />
{{hc|/etc/modprobe.d/hid_apple.conf|<nowiki><br />
options hid_apple fnmode=2<br />
</nowiki>}}<br />
<br />
<br />
===If the above doesn't work for your wireless keyboard===<br />
<br />
If {{ic|hid_apple/parameters}} and/or {{ic|hid/parameters/pb_fnmode}} is missing in a recent Apple Bluetooth keyboard model and kernel 3.4.<br />
<br />
First thing: identify your keyboard. Execute as root ({{ic|hidd}} is part of package {{Pkg|bluez}} from the [[official repositories]]):<br />
# hidd --show<br />
<br />
You should see something like:<br />
40:CA:EC:32:85:AB Apple Wireless Keyboard [05ac:0255] connected <br />
<br />
So with the vendor (05ac) and device (0255) ID it's easier to find out if the current kernel has support for it.<br />
Actually, the above device is listed in the linux kernel 3.4. If you check {{ic|drivers/hid/hid-ids.h}} you should see the following line:<br />
<br />
#define USB_DEVICE_ID_APPLE_ALU_WIRELESS_2011_ANSI 0x0255<br />
<br />
But support for the Function Key is missing.<br />
<br />
In order to fix it rebuild your kernel from [[abs]] with the following patch:<br />
http://pastebin.com/CvFJz3Fn<br />
<br />
This bug is already reported upstream<br />
https://bugzilla.kernel.org/show_bug.cgi?id=43135<br />
and part of the vanilla kernel since 3.5<br />
<br />
==< and > have changed place with § and ½==<br />
<br />
If the '''<''' and '''>''' are switched with the '''§''' and '''½''' keys, run the following command in your graphical environment:<br />
<br />
$ setxkbmap -option apple:badmap<br />
<br />
Place that command into {{ic|~/.bashrc}} file to have it run automatically when you log in.<br />
<br />
You can also apply the change system-wide by creating (or editing) {{ic|/etc/X11/xorg.conf.d/10-keymap.conf}} as such:<br />
Section "InputClass"<br />
Identifier "keyboard catchall"<br />
MatchIsKeyboard "true"<br />
Driver "evdev"<br />
Option "XkbOptions" "apple:badmap"<br />
EndSection<br />
<br />
<br />
If the above approach doesn't seem to work, you can add these two lines to your {{ic|~/.Xmodmap}} file:<br />
<br />
keycode 49 = less greater less greater bar brokenbar<br />
keycode 94 = section degree section degree notsign notsign<br />
<br />
If you use a Canadian multilingual layout (where the "ù" and the "/" is switch) use this :<br />
<br />
keycode 94 = slash backslash slash backslash bar brokenbar<br />
keycode 49 = ugrave Ugrave ugrave Ugrave notsign notsign<br />
<br />
Then run {{Ic|xmodmap ~/.Xmodmap}}. This command can also go into {{ic|~/.bashrc}}.<br />
<br />
==< and > have changed place with ^ and °==<br />
With German layout, circumflex/degree symbol and 'smaller than'/'bigger than' are exchanged.<br />
<br />
'''The new way:'''<br />
<br />
First, try if the new method works for you (you have to be root)<br />
# echo 0 > /sys/module/hid_apple/parameters/iso_layout<br />
To make the changes permanent add the following line to {{ic|/etc/modprobe.d/hid_apple.conf}}:<br />
options hid_apple iso_layout=0<br />
<br />
'''To fix this the old way, do the following:'''<br />
$ xmodmap -e 'keycode 49 = less greater less greater bar brokenbar bar' -e 'keycode 94 = dead_circumflex degree dead_circumflex degree U2032 U2033 U2032'<br />
<br />
Now try your keys. When it works, you may want the change permanently. So execute this:<br />
$ xmodmap -pke | grep " 49" >> ~/.Xmodmap<br />
$ xmodmap -pke | grep " 94" >> ~/.Xmodmap<br />
<br />
==Media Keys==<br />
<br />
The evdev driver should produce keycodes that map to the appropriate keysyms for your media keys by default. You can confirm that by running {{Ic|xev}} in a console window and watching the console output as you press your media keys.<br />
<br />
For these keys to have any effect, you will have to assign actions to them. Refer to [[Extra keyboard keys in Xorg]] for more about that.<br />
<br />
<br />
If you have confirmed that your media keys are ''not'' producing the correct keycodes, create or edit the {{ic|~/.Xmodmap}} file so that it includes these lines:<br />
{{bc|1=keycode 160 = XF86AudioMute<br />
keycode 176 = XF86AudioRaiseVolume<br />
keycode 174 = XF86AudioLowerVolume<br />
<br />
keycode 144 = XF86AudioPrev<br />
keycode 162 = XF86AudioPlay<br />
keycode 153 = XF86AudioNext<br />
<br />
keycode 101 = XF86MonBrightnessDown<br />
keycode 212 = XF86MonBrightnessUp<br />
<br />
keycode 204 = XF86Eject}}<br />
and then run {{Ic|xmodmap ~/.Xmodmap}}. Place that command in the {{ic|~/.bashrc}} file to have it run automatically when you log in.<br />
<br />
==PrintScreen and SysRq==<br />
<br />
Apple Keyboards have an {{ic|F13}} key instead of a {{ic|PrintScreen}}/{{ic|SysRq}} key. This means that [[Keyboard shortcuts#Kernel | Alt+SysRq sequences]] do not work, and application actions associated with {{ic|PrintScreen}} (such as taking screenshots in many games that work under [[Wine]]) do not work.<br />
Both issues can be addressed by installing {{AUR|keyfuzz}} from the [[Arch User Repository]].<br />
<br />
With keyfuzz installed, run the following command:<br />
echo "458856 99" | /usr/sbin/keyfuzz -s -d /dev/input/by-id/usb-Apple__Inc_Apple_keyboard-event-kbd<br />
458856 (0x070068) is the scancode of {{ic|F13}}, and 99 is the keycode of {{ic|PrintScreen}}/{{ic|SysRq}}. You can determine the scancode of a particular key with {{AUR|getscancodes}} from the [[AUR]], and the keycode from {{ic|/usr/include/linux/input.h}}.<br />
<br />
Other versions of the Apple Aluminum Keyboard may require a slightly different device path, so adjust it as needed. You can make this change permanent by putting the command in {{ic|/etc/rc.local}}.<br />
<br />
==Treating Apple Keyboards Like Regular Keyboards==<br />
<br />
If you want to use your Apple keyboard like a regular US-layout keyboard, with {{ic|Alt}} on the left side of {{ic|Meta}}, you can use the [[AUR]] package {{AUR|un-apple-keyboard}}. Currently it only works for the aluminium USB model. The package does the following things:<br />
<br />
*Adds a {{ic|/etc/modprobe.d/hid_apple.conf}} file which enables the {{ic|F}} keys by default, as above.<br />
*Uses keyfuzz to remap {{ic|F13-15}} to {{ic|PrintScreen}}/{{ic|SysRq}}, {{ic|Scroll Lock}}, and {{ic|Pause}}, respectively<br />
*Swaps the ordering of the {{ic|Alt}} and {{ic|Meta}} ({{ic|Command}}) keys to match all other keyboards, again using {{ic|/etc/modprobe.d/hid_apple.conf}}.<br />
*Applies these changes automatically when you plug in your keyboard, with a [[udev]] rule.<br />
<br />
You will need to add {{ic|/etc/modprobe.d/hid_apple.conf}} to FILES in [[mkinitcpio.conf]]. Otherwise if you boot your computer with the Apple keyboard plugged in, the F keys will not be the default.</div>JKAbramshttps://wiki.archlinux.org/index.php?title=PhpMyAdmin&diff=333954PhpMyAdmin2014-09-05T15:05:00Z<p>JKAbrams: Undo revision 333952 by JKAbrams (talk) Oops!</p>
<hr />
<div>[[Category:Web Server]]<br />
{{lowercase title}}<br />
[[cs:PhpMyAdmin]]<br />
[[es:PhpMyAdmin]]<br />
[[fr:phpmyadmin]]<br />
[[ru:PhpMyAdmin]]<br />
[[tr:PhpMyAdmin]]<br />
[[zh-CN:PhpMyAdmin]]<br />
[http://www.phpmyadmin.net/ phpMyAdmin] is a web-based tool to help manage MySQL databases using an Apache/PHP frontend. It requires a working [[LAMP]] setup.<br />
<br />
== Installation ==<br />
<br />
Install the {{Pkg|phpmyadmin}} and {{Pkg|php-mcrypt}} packages from the [[official repositories]].<br />
<br />
== Configuration ==<br />
<br />
===Apache===<br />
{{Note|The following works (at least no obvious problems) with Apache 2.4 and php-apache/mod_mpm_prefork or php-fpm/mod_proxy_handler}}<br />
<br />
Set up Apache to use php as outlined in the [[LAMP#PHP|LAMP]] article.<br />
<br />
Create the Apache configuration file:<br />
{{hc|/etc/httpd/conf/extra/httpd-phpmyadmin.conf|<nowiki><br />
Alias /phpmyadmin "/usr/share/webapps/phpMyAdmin"<br />
<Directory "/usr/share/webapps/phpMyAdmin"><br />
DirectoryIndex index.html index.php<br />
AllowOverride All<br />
Options FollowSymlinks<br />
Require all granted<br />
</Directory><br />
</nowiki>}}<br />
<br />
And include it in {{ic|/etc/httpd/conf/httpd.conf}}:<br />
# phpMyAdmin configuration<br />
Include conf/extra/httpd-phpmyadmin.conf<br />
<br />
By default, everyone can see the phpMyAdmin page, to change this, edit {{ic|/etc/httpd/conf/extra/httpd-phpmyadmin.conf}} to your liking. For example, if you only want to be able to access it from the same machine, replace {{ic|Require all granted}} by {{ic|Require local}}.<br />
<br />
===Lighttpd===<br />
Configurating Lighttpd is similar to Apache. Make sure Lighttpd is setup to serve PHP files (see [[Lighttpd]]).<br />
<br />
Make an alias for phpmyadmin in your Lighttpd config.<br />
alias.url = ( "/phpmyadmin" => "/usr/share/webapps/phpMyAdmin/")<br />
Then enable mod_alias, mod_fastcgi and mod_cgi in your config ( server.modules section )<br />
<br />
Update open_basedir in /etc/php/php.ini and add "/usr/share/webapps/".<br />
open_basedir = /srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/webapps/:/etc/webapps/<br />
<br />
Restart Lighttpd and go to [http://localhost/phpmyadmin/].<br />
<br />
===Nginx===<br />
<br />
==== Option 1: subdomain ====<br />
<br />
Using this method, you'll access PhpMyAdmin as {{ic|phpmyadmin.<domain>}}.<br />
<br />
Configurating Nginx is similar to Apache (and Lighttpd, for that matter). Make sure Nginx is setup to serve PHP files (see [[Nginx]]).<br />
<br />
You can setup a sub domain (or domain) with a server block like so (if using php-fpm):<br />
<br />
server {<br />
server_name phpmyadmin.<domain.tld>;<br />
<br />
root /usr/share/webapps/phpMyAdmin;<br />
index index.php;<br />
<br />
location ~ \.php$ {<br />
try_files $uri =404;<br />
fastcgi_pass unix:/run/php-fpm/php-fpm.sock;<br />
fastcgi_index index.php;<br />
include fastcgi.conf;<br />
}<br />
}<br />
<br />
To access this url on your localhost, you can simply add an entry in /etc/hosts:<br />
127.0.0.1 phpmyadmin.<domain.tld><br />
<br />
You need to update PHP's open_basedir option to add the appropriate directories. <br />
Either in /etc/php/php.ini:<br />
open_basedir = /srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/webapps/:/etc/webapps/<br />
<br />
Or if running php-fpm with a separate entry for phpmyadmin, you can overwrite this value in your pool definition (in /etc/php/fpm.d/<pool file>):<br />
php_admin_value[open_basedir] = /tmp/:/usr/share/webapps/:/etc/webapps/<br />
<br />
If the above doesn't fix it try adding the following to your NGINX Configuration below the other fastcgi_param (I think its something to do with the Suhosin-Patch)<br />
fastcgi_param PHP_ADMIN_VALUE open_basedir="/srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/webapps/:/etc/webapps/";<br />
<br />
While you can enter anything for the blowfish password, you may want to choose a randomly generated string of characters (most likely for security reasons). Here's a handy tool that will do that for you on the web[http://www.question-defense.com/tools/phpmyadmin-blowfish-secret-generator].<br />
<br />
When using SSL, you might run into the problem that the links on the pages generated by phpMyAdmin incorrectly start with "http" instead of "https" which may cause errors. To fix this, you can add the following fcgi_param to your SSL-enabled server section (in addition to your usual fastcgi params):<br />
fastcgi_param HTTPS on;<br />
<br />
==== Option 2: subdirectory ====<br />
<br />
Using this method, you'll access PhpMyAdmin as {{ic|localhost/phpmyadmin}}, similarly to Apache.<br />
<br />
To get PhpMyAdmin working with your [[nginx]] setup, first take note of the root of the server you want to use. Supposing it is {{ic|/srv/http}}, now create a symlink:<br />
<br />
# ln -s /usr/share/webapps/phpMyAdmin/ /srv/http/phpmyadmin<br />
<br />
===PHP===<br />
You need to enable the {{ic|mysqli}} and {{ic|mcrypt}} (if you want phpMyAdmin internal authentication) extensions in PHP by editing {{ic|/etc/php/php.ini}} and uncommenting the following lines:<br />
extension=mysqli.so<br />
extension=mcrypt.so<br />
<br />
Optionally you can enable {{ic|bz2.so}} and {{ic|zip.so}} for compression support.<br />
<br />
You need to make sure that PHP can access {{ic|/etc/webapps}}. Add it to {{ic|open_basedir}} in {{ic|/etc/php/php.ini}} if necessary:<br />
open_basedir = /srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/webapps/:/etc/webapps/<br />
<br />
==phpMyAdmin configuration==<br />
phpMyAdmin's configuration file is located at {{ic|/etc/webapps/phpmyadmin/config.inc.php}}. If you have a local MySQL server, it should be usable without making any modifications.<br />
<br />
If your MySQL server is not on the localhost, uncomment and edit the following line:<br />
$cfg['Servers'][$i]['host'] = 'localhost';<br />
<br />
If you would like to use phpMyAdmin setup script by calling http://localhost/phpmyadmin/setup you will need to create a config directory that's writeable by the ''httpd'' user in {{ic|/usr/share/webapps/phpMyAdmin}} as follows:<br />
# cd /usr/share/webapps/phpMyAdmin<br />
# mkdir config<br />
# chgrp http config<br />
# chmod g+w config<br />
<br />
=== Add blowfish_secret passphrase ===<br />
If you see the following error message at the bottom of the page when you first log in to /phpmyadmin (using a previously setup MySQL username and password) :<br />
<br />
ERROR: The configuration file now needs a secret passphrase (blowfish_secret)<br />
<br />
You need to add a blowfish password to the phpMyAdmin's config file. Edit {{ic|/etc/webapps/phpmyadmin/config.inc.php}} and insert a random blowfish "password" in the line <br />
<br />
$cfg['blowfish_secret'] = ''; /* YOU MUST FILL IN THIS FOR COOKIE AUTH! */<br />
<br />
Go [http://www.question-defense.com/tools/phpmyadmin-blowfish-secret-generator here] to get a nicely generated blowfish_secret and paste it between the '' marks. It should now look something like this:<br />
<br />
$cfg['blowfish_secret'] = 'qtdRoGmbc9{8IZr323xYcSN]0s)r$9b_JUnb{~Xz'; /* YOU MUST FILL IN THIS FOR COOKIE AUTH! */<br />
<br />
The error should go away if you refresh the phpmyadmin page.<br />
<br />
=== Enabling Configuration Storage (optional) ===<br />
Now that the basic database server has been setup, it ''is'' functional, however by default, extra options such as table linking, change tracking, PDF creation, and bookmarking queries are disabled. You will see a message at the bottom of the main phpMyAdmin page, "The phpMyAdmin configuration storage is not completely configured, some extended features have been deactivated. To find out why...", This section addresses how to to enable these extra features.<br />
<br />
{{note|This example assumes you want to use the username '''pma''' as the controluser, and '''pmapass''' as the controlpass. These should be changed (the ''very'' least, you should change the password!) to something more secure.}}<br />
<br />
In {{ic|/etc/webapps/phpmyadmin/config.inc.php}}, uncomment (remove the leading "//"s on) these two lines, and change them to your desired credentials:<br />
{{bc|1=<br />
// $cfg['Servers'][$i]['controluser'] = 'pma';<br />
// $cfg['Servers'][$i]['controlpass'] = 'pmapass';<br />
}}<br />
<br />
You will need this information later, so keep it in mind.<br />
<br />
Beneath the controluser setup section, uncomment these lines:<br />
{{bc|1=<br />
/* Storage database and tables */<br />
// $cfg['Servers'][$i]['pmadb'] = 'phpmyadmin';<br />
// $cfg['Servers'][$i]['bookmarktable'] = 'pma__bookmark';<br />
// $cfg['Servers'][$i]['relation'] = 'pma__relation';<br />
// $cfg['Servers'][$i]['table_info'] = 'pma__table_info';<br />
// $cfg['Servers'][$i]['table_coords'] = 'pma__table_coords';<br />
// $cfg['Servers'][$i]['pdf_pages'] = 'pma__pdf_pages';<br />
// $cfg['Servers'][$i]['column_info'] = 'pma__column_info';<br />
// $cfg['Servers'][$i]['history'] = 'pma__history';<br />
// $cfg['Servers'][$i]['table_uiprefs'] = 'pma__table_uiprefs';<br />
// $cfg['Servers'][$i]['tracking'] = 'pma__tracking';<br />
// $cfg['Servers'][$i]['designer_coords'] = 'pma__designer_coords';<br />
// $cfg['Servers'][$i]['userconfig'] = 'pma__userconfig';<br />
// $cfg['Servers'][$i]['recent'] = 'pma__recent';<br />
// $cfg['Servers'][$i]['users'] = 'pma__users';<br />
// $cfg['Servers'][$i]['usergroups'] = 'pma__usergroups';<br />
// $cfg['Servers'][$i]['navigationhiding'] = 'pma__navigationhiding';<br />
}}<br />
<br />
Next, create the user with the above details. Don't set any permissions for it just yet.<br />
{{note|If you can't login to phpmyadmin, make sure that your mysql server is started.}}<br />
<br />
===== creating phpMyAdmin database =====<br />
Using the phpMyAdmin web interface:<br />
Import {{ic|/usr/share/webapps/phpMyAdmin/examples/create_tables.sql}} from phpMyAdmin -> Import.<br />
'''or'''<br />
Using command line: {{ic|mysql -u root -p < /usr/share/webapps/phpMyAdmin/examples/create_tables.sql}}.<br />
<br />
===== creating phpMyAdmin database user =====<br />
Now to apply the permissions to your controluser, in the SQL tab, make sure to replace all instances of 'pma' and 'pmapass' to the values set in config.inc.php. If you are setting this up for a remote database, then you must also change 'localhost' to the proper host:<br />
{{bc|<br />
GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';<br />
GRANT SELECT (<br />
Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,<br />
Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,<br />
File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,<br />
Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,<br />
Execute_priv, Repl_slave_priv, Repl_client_priv<br />
) ON mysql.user TO 'pma'@'localhost';<br />
GRANT SELECT ON mysql.db TO 'pma'@'localhost';<br />
GRANT SELECT ON mysql.host TO 'pma'@'localhost';<br />
GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)<br />
ON mysql.tables_priv TO 'pma'@'localhost';<br />
}}<br />
<br />
In order to take advantage of the bookmark and relation features, you will also need to give '''pma''' some additional permissions:<br />
{{Note|as long as you did not change the value of '''$cfg['Servers'][$i]['pmadb']''' in {{ic|/etc/webapps/phpmyadmin/config.inc.php}}, then '''<pma_db>''' should be '''phpmyadmin'''}}<br />
{{bc|GRANT SELECT, INSERT, UPDATE, DELETE ON <pma_db>.* TO 'pma'@'localhost';}}<br />
<br />
Log out, and back in to ensure the new features are activated. The message at the bottom of the main screen should now be gone.<br />
<br />
==Accessing your phpMyAdmin installation==<br />
Your phpMyAdmin installation is now complete. Before you start using it you need to restart Apache.<br />
<br />
You can access your phpMyAdmin installation by going to http://localhost/phpmyadmin/</div>JKAbramshttps://wiki.archlinux.org/index.php?title=PhpMyAdmin&diff=333952PhpMyAdmin2014-09-05T15:00:04Z<p>JKAbrams: changed /usr/share/webapps/phpMyAdmin to /usr/share/webapps/phpmyadmin</p>
<hr />
<div>[[Category:Web Server]]<br />
{{lowercase title}}<br />
[[cs:PhpMyAdmin]]<br />
[[es:PhpMyAdmin]]<br />
[[fr:phpmyadmin]]<br />
[[ru:PhpMyAdmin]]<br />
[[tr:PhpMyAdmin]]<br />
[[zh-CN:PhpMyAdmin]]<br />
[http://www.phpmyadmin.net/ phpMyAdmin] is a web-based tool to help manage MySQL databases using an Apache/PHP frontend. It requires a working [[LAMP]] setup.<br />
<br />
== Installation ==<br />
<br />
Install the {{Pkg|phpmyadmin}} and {{Pkg|php-mcrypt}} packages from the [[official repositories]].<br />
<br />
== Configuration ==<br />
<br />
===Apache===<br />
{{Note|The following works (at least no obvious problems) with Apache 2.4 and php-apache/mod_mpm_prefork or php-fpm/mod_proxy_handler}}<br />
<br />
Set up Apache to use php as outlined in the [[LAMP#PHP|LAMP]] article.<br />
<br />
Create the Apache configuration file:<br />
{{hc|/etc/httpd/conf/extra/httpd-phpmyadmin.conf|<nowiki><br />
Alias /phpmyadmin "/usr/share/webapps/phpMyAdmin"<br />
<Directory "/usr/share/webapps/phpMyAdmin"><br />
DirectoryIndex index.html index.php<br />
AllowOverride All<br />
Options FollowSymlinks<br />
Require all granted<br />
</Directory><br />
</nowiki>}}<br />
<br />
And include it in {{ic|/etc/httpd/conf/httpd.conf}}:<br />
# phpMyAdmin configuration<br />
Include conf/extra/httpd-phpmyadmin.conf<br />
<br />
By default, everyone can see the phpMyAdmin page, to change this, edit {{ic|/etc/httpd/conf/extra/httpd-phpmyadmin.conf}} to your liking. For example, if you only want to be able to access it from the same machine, replace {{ic|Require all granted}} by {{ic|Require local}}.<br />
<br />
===Lighttpd===<br />
Configurating Lighttpd is similar to Apache. Make sure Lighttpd is setup to serve PHP files (see [[Lighttpd]]).<br />
<br />
Make an alias for phpmyadmin in your Lighttpd config.<br />
alias.url = ( "/phpmyadmin" => "/usr/share/webapps/phpMyAdmin/")<br />
Then enable mod_alias, mod_fastcgi and mod_cgi in your config ( server.modules section )<br />
<br />
Update open_basedir in /etc/php/php.ini and add "/usr/share/webapps/".<br />
open_basedir = /srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/webapps/:/etc/webapps/<br />
<br />
Restart Lighttpd and go to [http://localhost/phpmyadmin/].<br />
<br />
===Nginx===<br />
<br />
==== Option 1: subdomain ====<br />
<br />
Using this method, you'll access PhpMyAdmin as {{ic|phpmyadmin.<domain>}}.<br />
<br />
Configurating Nginx is similar to Apache (and Lighttpd, for that matter). Make sure Nginx is setup to serve PHP files (see [[Nginx]]).<br />
<br />
You can setup a sub domain (or domain) with a server block like so (if using php-fpm):<br />
<br />
server {<br />
server_name phpmyadmin.<domain.tld>;<br />
<br />
root /usr/share/webapps/phpMyAdmin;<br />
index index.php;<br />
<br />
location ~ \.php$ {<br />
try_files $uri =404;<br />
fastcgi_pass unix:/run/php-fpm/php-fpm.sock;<br />
fastcgi_index index.php;<br />
include fastcgi.conf;<br />
}<br />
}<br />
<br />
To access this url on your localhost, you can simply add an entry in /etc/hosts:<br />
127.0.0.1 phpmyadmin.<domain.tld><br />
<br />
You need to update PHP's open_basedir option to add the appropriate directories. <br />
Either in /etc/php/php.ini:<br />
open_basedir = /srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/webapps/:/etc/webapps/<br />
<br />
Or if running php-fpm with a separate entry for phpmyadmin, you can overwrite this value in your pool definition (in /etc/php/fpm.d/<pool file>):<br />
php_admin_value[open_basedir] = /tmp/:/usr/share/webapps/:/etc/webapps/<br />
<br />
If the above doesn't fix it try adding the following to your NGINX Configuration below the other fastcgi_param (I think its something to do with the Suhosin-Patch)<br />
fastcgi_param PHP_ADMIN_VALUE open_basedir="/srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/webapps/:/etc/webapps/";<br />
<br />
While you can enter anything for the blowfish password, you may want to choose a randomly generated string of characters (most likely for security reasons). Here's a handy tool that will do that for you on the web[http://www.question-defense.com/tools/phpmyadmin-blowfish-secret-generator].<br />
<br />
When using SSL, you might run into the problem that the links on the pages generated by phpMyAdmin incorrectly start with "http" instead of "https" which may cause errors. To fix this, you can add the following fcgi_param to your SSL-enabled server section (in addition to your usual fastcgi params):<br />
fastcgi_param HTTPS on;<br />
<br />
==== Option 2: subdirectory ====<br />
<br />
Using this method, you'll access PhpMyAdmin as {{ic|localhost/phpmyadmin}}, similarly to Apache.<br />
<br />
To get PhpMyAdmin working with your [[nginx]] setup, first take note of the root of the server you want to use. Supposing it is {{ic|/srv/http}}, now create a symlink:<br />
<br />
# ln -s /usr/share/webapps/phpMyAdmin/ /srv/http/phpmyadmin<br />
<br />
===PHP===<br />
You need to enable the {{ic|mysqli}} and {{ic|mcrypt}} (if you want phpMyAdmin internal authentication) extensions in PHP by editing {{ic|/etc/php/php.ini}} and uncommenting the following lines:<br />
extension=mysqli.so<br />
extension=mcrypt.so<br />
<br />
Optionally you can enable {{ic|bz2.so}} and {{ic|zip.so}} for compression support.<br />
<br />
You need to make sure that PHP can access {{ic|/etc/webapps}}. Add it to {{ic|open_basedir}} in {{ic|/etc/php/php.ini}} if necessary:<br />
open_basedir = /srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/webapps/:/etc/webapps/<br />
<br />
==phpMyAdmin configuration==<br />
phpMyAdmin's configuration file is located at {{ic|/etc/webapps/phpmyadmin/config.inc.php}}. If you have a local MySQL server, it should be usable without making any modifications.<br />
<br />
If your MySQL server is not on the localhost, uncomment and edit the following line:<br />
$cfg['Servers'][$i]['host'] = 'localhost';<br />
<br />
If you would like to use phpMyAdmin setup script by calling http://localhost/phpmyadmin/setup you will need to create a config directory that's writeable by the ''httpd'' user in {{ic|/usr/share/webapps/phpmyadmin}} as follows:<br />
# cd /usr/share/webapps/phpmyadmin<br />
# mkdir config<br />
# chgrp http config<br />
# chmod g+w config<br />
<br />
=== Add blowfish_secret passphrase ===<br />
If you see the following error message at the bottom of the page when you first log in to /phpmyadmin (using a previously setup MySQL username and password) :<br />
<br />
ERROR: The configuration file now needs a secret passphrase (blowfish_secret)<br />
<br />
You need to add a blowfish password to the phpMyAdmin's config file. Edit {{ic|/etc/webapps/phpmyadmin/config.inc.php}} and insert a random blowfish "password" in the line <br />
<br />
$cfg['blowfish_secret'] = ''; /* YOU MUST FILL IN THIS FOR COOKIE AUTH! */<br />
<br />
Go [http://www.question-defense.com/tools/phpmyadmin-blowfish-secret-generator here] to get a nicely generated blowfish_secret and paste it between the '' marks. It should now look something like this:<br />
<br />
$cfg['blowfish_secret'] = 'qtdRoGmbc9{8IZr323xYcSN]0s)r$9b_JUnb{~Xz'; /* YOU MUST FILL IN THIS FOR COOKIE AUTH! */<br />
<br />
The error should go away if you refresh the phpmyadmin page.<br />
<br />
=== Enabling Configuration Storage (optional) ===<br />
Now that the basic database server has been setup, it ''is'' functional, however by default, extra options such as table linking, change tracking, PDF creation, and bookmarking queries are disabled. You will see a message at the bottom of the main phpMyAdmin page, "The phpMyAdmin configuration storage is not completely configured, some extended features have been deactivated. To find out why...", This section addresses how to to enable these extra features.<br />
<br />
{{note|This example assumes you want to use the username '''pma''' as the controluser, and '''pmapass''' as the controlpass. These should be changed (the ''very'' least, you should change the password!) to something more secure.}}<br />
<br />
In {{ic|/etc/webapps/phpmyadmin/config.inc.php}}, uncomment (remove the leading "//"s on) these two lines, and change them to your desired credentials:<br />
{{bc|1=<br />
// $cfg['Servers'][$i]['controluser'] = 'pma';<br />
// $cfg['Servers'][$i]['controlpass'] = 'pmapass';<br />
}}<br />
<br />
You will need this information later, so keep it in mind.<br />
<br />
Beneath the controluser setup section, uncomment these lines:<br />
{{bc|1=<br />
/* Storage database and tables */<br />
// $cfg['Servers'][$i]['pmadb'] = 'phpmyadmin';<br />
// $cfg['Servers'][$i]['bookmarktable'] = 'pma__bookmark';<br />
// $cfg['Servers'][$i]['relation'] = 'pma__relation';<br />
// $cfg['Servers'][$i]['table_info'] = 'pma__table_info';<br />
// $cfg['Servers'][$i]['table_coords'] = 'pma__table_coords';<br />
// $cfg['Servers'][$i]['pdf_pages'] = 'pma__pdf_pages';<br />
// $cfg['Servers'][$i]['column_info'] = 'pma__column_info';<br />
// $cfg['Servers'][$i]['history'] = 'pma__history';<br />
// $cfg['Servers'][$i]['table_uiprefs'] = 'pma__table_uiprefs';<br />
// $cfg['Servers'][$i]['tracking'] = 'pma__tracking';<br />
// $cfg['Servers'][$i]['designer_coords'] = 'pma__designer_coords';<br />
// $cfg['Servers'][$i]['userconfig'] = 'pma__userconfig';<br />
// $cfg['Servers'][$i]['recent'] = 'pma__recent';<br />
// $cfg['Servers'][$i]['users'] = 'pma__users';<br />
// $cfg['Servers'][$i]['usergroups'] = 'pma__usergroups';<br />
// $cfg['Servers'][$i]['navigationhiding'] = 'pma__navigationhiding';<br />
}}<br />
<br />
Next, create the user with the above details. Don't set any permissions for it just yet.<br />
{{note|If you can't login to phpmyadmin, make sure that your mysql server is started.}}<br />
<br />
===== creating phpMyAdmin database =====<br />
Using the phpMyAdmin web interface:<br />
Import {{ic|/usr/share/webapps/phpMyAdmin/examples/create_tables.sql}} from phpMyAdmin -> Import.<br />
'''or'''<br />
Using command line: {{ic|mysql -u root -p < /usr/share/webapps/phpMyAdmin/examples/create_tables.sql}}.<br />
<br />
===== creating phpMyAdmin database user =====<br />
Now to apply the permissions to your controluser, in the SQL tab, make sure to replace all instances of 'pma' and 'pmapass' to the values set in config.inc.php. If you are setting this up for a remote database, then you must also change 'localhost' to the proper host:<br />
{{bc|<br />
GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';<br />
GRANT SELECT (<br />
Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,<br />
Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,<br />
File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,<br />
Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,<br />
Execute_priv, Repl_slave_priv, Repl_client_priv<br />
) ON mysql.user TO 'pma'@'localhost';<br />
GRANT SELECT ON mysql.db TO 'pma'@'localhost';<br />
GRANT SELECT ON mysql.host TO 'pma'@'localhost';<br />
GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)<br />
ON mysql.tables_priv TO 'pma'@'localhost';<br />
}}<br />
<br />
In order to take advantage of the bookmark and relation features, you will also need to give '''pma''' some additional permissions:<br />
{{Note|as long as you did not change the value of '''$cfg['Servers'][$i]['pmadb']''' in {{ic|/etc/webapps/phpmyadmin/config.inc.php}}, then '''<pma_db>''' should be '''phpmyadmin'''}}<br />
{{bc|GRANT SELECT, INSERT, UPDATE, DELETE ON <pma_db>.* TO 'pma'@'localhost';}}<br />
<br />
Log out, and back in to ensure the new features are activated. The message at the bottom of the main screen should now be gone.<br />
<br />
==Accessing your phpMyAdmin installation==<br />
Your phpMyAdmin installation is now complete. Before you start using it you need to restart Apache.<br />
<br />
You can access your phpMyAdmin installation by going to http://localhost/phpmyadmin/</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Talk:Configure_virtual_console_colors&diff=328548Talk:Configure virtual console colors2014-08-05T01:55:08Z<p>JKAbrams: never mind</p>
<hr />
<div></div>JKAbramshttps://wiki.archlinux.org/index.php?title=Talk:Configure_virtual_console_colors&diff=328547Talk:Configure virtual console colors2014-08-05T01:52:57Z<p>JKAbrams: </p>
<hr />
<div>Them image i got was a bit mangled, here's what worked for me:<br />
<br />
echo -e '^[[H^[[2J' >> issue<br />
echo -e ' ^[[1;30m| ^[[34m\s \r' >> issue<br />
echo -e ' ^[[36;1m/\\ ^[[37m|| ^[[36m| | ^[[30m|' >> issue<br />
echo -e ' ^[[36m/ \\ ^[[37m|| ^[[36m| _ ^[[30m| ^[[32m\t' >> issue<br />
echo -e ' ^[[1;36m/ ^[[0;36m.. ^[[1m\\ ^[[37m//==\\\\ ||/= /==\\ ||/=\\ ^[[36m| | |/ \ | | \ / ^[[30m| ^[[32m\d' >> issue<br />
echo -e ' ^[[0;36m/ . . \\ ^[[37m|| || || | || || ^[[36m| | | | | | X ^[[1;30m|' >> issue<br />
echo -e ' ^[[0;36m/ . . \\ ^[[37m\\\\==/| || \\==/ || || ^[[36m| | | | \_/| / \ ^[[1;30m| ^[[31m\U' >> issue<br />
echo -e ' ^[[0;36m/ .. .. \\ ^[[0;37mA simple, lightweight linux distribution. ^[[1;30m|' >> issue<br />
echo -e ' ^[[0;36m/_' `_\\ ^[[1;30m| ^[[35m\l ^[[0mon ^[[1;33m\n' >> issue<br />
echo -e ' ^[[0m' >> issue</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Talk:Configure_virtual_console_colors&diff=328546Talk:Configure virtual console colors2014-08-05T01:52:46Z<p>JKAbrams: </p>
<hr />
<div>Them image i got was a bit mangled, here's what worked for me:<br />
<br />
echo -e '^[[H^[[2J' >> issue<br />
echo -e ' ^[[1;30m| ^[[34m\s \r' >> issue<br />
echo -e ' ^[[36;1m/\\ ^[[37m|| ^[[36m| | ^[[30m|' >> issue<br />
echo -e ' ^[[36m/ \\ ^[[37m|| ^[[36m| _ ^[[30m| ^[[32m\t' >> issue<br />
echo -e ' ^[[1;36m/ ^[[0;36m.. ^[[1m\\ ^[[37m//==\\\\ ||/= /==\\ ||/=\\ ^[[36m| | |/ \ | | \ / ^[[30m| ^[[32m\d' >> issue<br />
echo -e ' ^[[0;36m/ . . \\ ^[[37m|| || || | || || ^[[36m| | | | | | X ^[[1;30m|' >> issue<br />
echo -e ' ^[[0;36m/ . . \\ ^[[37m\\\\==/| || \\==/ || || ^[[36m| | | | \_/| / \ ^[[1;30m| ^[[31m\U' >> issue<br />
echo -e ' ^[[0;36m/ .. .. \\ ^[[0;37mA simple, lightweight linux distribution. ^[[1;30m|' >> issue<br />
echo -e ' ^[[0;36m/_' `_\\ ^[[1;30m| ^[[35m\l ^[[0mon ^[[1;33m\n' >> issue<br />
echo -e ' ^[[0m' >> issue</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Talk:Configure_virtual_console_colors&diff=328545Talk:Configure virtual console colors2014-08-05T01:51:35Z<p>JKAbrams: </p>
<hr />
<div>Them image i got was a bit mangled, here's a corrected one:<br />
<br />
^[[H^[[2J<br />
^[[1;30m| ^[[34m\s \r<br />
^[[36;1m/\\ ^[[37m|| ^[[36m| | ^[[30m|<br />
^[[36m/ \\ ^[[37m|| ^[[36m| _ ^[[30m| ^[[32m\t<br />
^[[1;36m/ ^[[0;36m.. ^[[1m\\ ^[[37m//==\\\\ ||/= /==\\ ||/=\\ ^[[36m| | |/ \ | | \ / ^[[30m| ^[[32m\d<br />
^[[0;36m/ . . \\ ^[[37m|| || || | || || ^[[36m| | | | | | X ^[[1;30m|<br />
^[[0;36m/ . . \\ ^[[37m\\\\==/| || \\==/ || || ^[[36m| | | | \_/| / \ ^[[1;30m| ^[[31m\U<br />
^[[0;36m/ .. .. \\ ^[[0;37mA simple, lightweight linux distribution. ^[[1;30m|<br />
^[[0;36m/_' `_\\ ^[[1;30m| ^[[35m\l ^[[0mon ^[[1;33m\n<br />
^[[0m</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Talk:Configure_virtual_console_colors&diff=328544Talk:Configure virtual console colors2014-08-05T01:51:06Z<p>JKAbrams: Created page with "Them image i got was a bit mangled, here's a corrected one: ^H^[[2J ^[[1;30m| ^[[34m\s \r ^[[36;1m/\\ ..."</p>
<hr />
<div>Them image i got was a bit mangled, here's a corrected one:<br />
<br />
^[[H^[[2J<br />
^[[1;30m| ^[[34m\s \r<br />
^[[36;1m/\\ ^[[37m|| ^[[36m| | ^[[30m|<br />
^[[36m/ \\ ^[[37m|| ^[[36m| _ ^[[30m| ^[[32m\t<br />
^[[1;36m/ ^[[0;36m.. ^[[1m\\ ^[[37m//==\\\\ ||/= /==\\ ||/=\\ ^[[36m| | |/ \ | | \ / ^[[30m| ^[[32m\d<br />
^[[0;36m/ . . \\ ^[[37m|| || || | || || ^[[36m| | | | | | X ^[[1;30m|<br />
^[[0;36m/ . . \\ ^[[37m\\\\==/| || \\==/ || || ^[[36m| | | | \_/| / \ ^[[1;30m| ^[[31m\U<br />
^[[0;36m/ .. .. \\ ^[[0;37mA simple, lightweight linux distribution. ^[[1;30m|<br />
^[[0;36m/_' `_\\ ^[[1;30m| ^[[35m\l ^[[0mon ^[[1;33m\n<br />
^[[0m</div>JKAbramshttps://wiki.archlinux.org/index.php?title=KDE&diff=283467KDE2013-11-17T22:50:35Z<p>JKAbrams: /* Graphical related issues */</p>
<hr />
<div>[[Category:KDE]]<br />
[[cs:KDE]]<br />
[[de:KDE]]<br />
[[es:KDE]]<br />
[[fr:KDE]]<br />
[[it:KDE]]<br />
[[ja:KDE]]<br />
[[pl:KDE]]<br />
[[ru:KDE]]<br />
[[tr:KDE_Masaüstü_Ortamı]]<br />
[[zh-CN:KDE]]<br />
[[zh-TW:KDE]]<br />
{{Article summary start}}<br />
{{Article summary text|This article covers installation, configuration, and troubleshooting of KDE.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Graphical user interface overview}}}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Plasma}}<br />
{{Article summary wiki|Qt}} - KDE uses the Qt toolkit<br />
{{Article summary wiki|KDM}}<br />
{{Article summary wiki|KDevelop 4}}<br />
{{Article summary wiki|Uniform Look for Qt and GTK Applications}}<br />
{{Article summary end}}<br />
<br />
From [http://www.kde.org/community/whatiskde/softwarecompilation.php KDE Software Compilation] and [http://www.kde.org/download/ Getting KDE Software]:<br />
<br />
:''The KDE Software Compilation is the set of frameworks, workspaces, and applications produced by KDE to create a beautiful, functional and free desktop computing environment for Linux and similar operating systems. It consists of a large number of individual applications and a desktop workspace as a shell to run these applications. ''<br />
<br />
The KDE upstream has a well maintained [http://userbase.kde.org/ UserBase wiki]. Users can get detailed information about most KDE applications there.<br />
<br />
== Installation ==<br />
<br />
KDE 4.x is '''modular'''. You can install an entire set of packages or only install your preferred KDE applications.<br />
<br />
{{Note|If you do not have [[Xorg#Installation|Xorg]] installed on your system, be sure to install it before KDE.}}<br />
<br />
=== Full install ===<br />
<br />
[[pacman|Install]] {{Grp|kde}} or {{Grp|kde-meta}} available in the [[official repositories]]. For differences between {{Grp|kde}} and {{Grp|kde-meta}} see the [[KDE Packages]] article.<br />
<br />
=== Minimal install ===<br />
<br />
If you want to have a minimal installation of the KDE SC, install:<br />
* {{Grp|kdebase}}<br />
<br />
=== Language pack ===<br />
<br />
If you need language files, install {{ic|kde-l10n-yourlanguagehere}} (e.g. {{Pkg|kde-l10n-de}} for the German language).<br />
<br />
For a full list of available languages see [https://www.archlinux.org/packages/extra/any/kde-l10n/ this link].<br />
<br />
== Upgrading ==<br />
<br />
'''KDE 4.11''' Software Compilation is the current major [http://kde.org/announcements/ release of KDE]. Important hints for upgraders:<br />
* Always check if your mirror is '''up to date'''.<br />
* '''Do not force an update using {{ic|# pacman --force}}'''. If pacman complains about conflicts please '''file a bug report'''.<br />
* You can remove the meta packages and the sub packages you do not need after the update.<br />
* If you do not like split packages just keep using the kde-meta packages.<br />
<br />
== Starting KDE ==<br />
<br />
Starting KDE depends on your preferences. Basically there are two ways of starting KDE. Using '''KDM''' or '''xinitrc'''.<br />
<br />
=== Using a Display Manager ===<br />
''It is highly recommended to get familiar with the [[Display Manager|full article]] concerning display managers, before you make any changes.''<br />
<br />
==== KDM (KDE Display Manager) ====<br />
<br />
''See also [[KDM]] Wiki page.''<br />
<br />
[[Daemons|Enable/start]] {{ic|kdm.service}}.<br />
<br />
=== Using xinitrc ===<br />
<br />
''The meaning and usage of '''xinitrc''' is very well described [[Xinitrc|here]].<br />
<br />
{{Pkg|kdebase-workspace}} provides startkde. Make sure it is installed then use:<br />
<br />
{{hc|~/.xinitrc|<br />
exec startkde<br />
}}<br />
<br />
After a reboot and/or log-in, each execution of Xorg ({{ic|startx}} or {{ic|xinit}}) will start KDE automatically.<br />
<br />
{{Note|If you want to start Xorg at boot, please read [[Start X at Login]] article.}}<br />
<br />
== Configuration ==<br />
<br />
All KDE configuration is saved in the {{ic|~/.kde4}} folder. If your KDE is giving you a lot of trouble or if you ever want a fresh installation of KDE, just back this folder up and restart your X session. KDE will re-create this folder with all the default config files. If you want very fine-grained control over your KDE programs, then you may want to edit the files in this folder.<br />
<br />
However, configuring KDE is primarily done in '''System Settings'''. There are also a few other options available for the desktop with '''Default Desktop Settings''' when you right click the desktop.<br />
<br />
For other personalization options not covered below such as activities, different wallpapers on one cube, etc please refer to the [[Plasma]] wiki page.<br />
<br />
=== Personalization ===<br />
<br />
How to set up the KDE desktop to your personal style; use different Plasma themes, window decorations and icon themes. <br />
<br />
==== Plasma desktop ====<br />
<br />
[[Plasma]] is a desktop integration technology that provides many functions from displaying the wallpaper, adding widgets to the desktop, and handling the panels or "taskbar".<br />
<br />
===== Themes =====<br />
<br />
[http://kde-look.org/index.php?xcontentmode=76 Plasma themes] can be installed through the Desktop Settings control panel. Plasma themes define how your panels and plasmoids look like. If you like to have them installed system-wide, themes can be found in both the official repositories and [https://aur.archlinux.org/packages.php?O=0&K=plasmatheme&do_Search=Go AUR].<br />
<br />
===== Widgets =====<br />
<br />
Plasmoids are little scripted or coded KDE apps that enhance the functionality of your desktop. There are two kinds, plasmoid scripts and plasmoid binaries.<br />
<br />
Plasmoid binaries must be installed using PKGBUILDS from [https://aur.archlinux.org/packages.php?O=0&K=plasmoid&do_Search=Go&PP=25&SO=d&SB=v AUR]. Or write your own PKGBUILD.<br />
<br />
The easiest way to install plasmoid scripts is by right-clicking onto a panel or the desktop:<br />
<br />
Add Widgets > Get new Widgets > Download Widgets<br />
<br />
This will present a nice frontend for [http://www.kde-look.org/ kde-look.org] and allows you to (un)install or update third-party plasmoid scripts with just one click.<br />
<br />
Most plasmoids are not created officially by KDE developers. You can also try installing Mac OS X widgets, Microsoft Windows Vista/7 widgets, Google Widgets, and even SuperKaramba widgets.<br />
<br />
===== Sound applet in the system tray =====<br />
<br />
Install Kmix ({{Pkg|kdemultimedia-kmix}}) from the official repositories and start it from the application launcher. Since KDE autostarts programs from the previous session, the program need not be started manually every time one logs in.<br />
<br />
===== Adding a Global Menu to the desktop =====<br />
<br />
Install {{Pkg|appmenu-qt}} from the official repos and {{aur|appmenu-gtk}} and {{aur|appmenu-qt5}} from the AUR in order to complete the preliminaries for an always-on globalmenu (mac-style). To get firefox and libreoffice support as well, install {{aur|firefox-extension-globalmenu}} and {{aur|libreoffice-extension-menubar}} from the AUR.<br />
<br />
{{Warning|{{aur|firefox-extension-globalmenu}} has been deprecated as of Firefox 25 and there is no other recommended method for getting the global menu. However, there is a patched package, namely {{aur|firefox-ubuntu}} available in the AUR which has canonical's patch for getting the globalmenu to work with the current version of Firefox (as of this writing).}}<br />
<br />
To actually get the globalmenu, install {{aur|kdeplasma-applets-menubar}} from the AUR. Create a plasma-panel on top of your screen and add the window menubar applet to the panel. To export the menus to your globalmenu, go to ''System Settings > Application Appearance > Style''. Now click the fine-tuning tab and use the drop-down list to select ''only export'' as your menubar style.<br />
<br />
==== Window decorations ====<br />
<br />
[http://kde-look.org/index.php?xcontentmode=75 Window decorations] can be changed in:<br />
System Settings > Workspace Appearance > Window Decorations<br />
There you can also directly download and install more themes with one click and some are available on [https://aur.archlinux.org/packages.php?O=0&K=kdestyle&do_Search=Go&PP=25&SO=d&SB=v AUR].<br />
<br />
==== Icon themes ====<br />
<br />
Not many full system icons themes are available for KDE 4. You can open up ''System Settings > Application Appearance > Icons'' and browse for new ones or install them manually. Many of them can be found on [http://www.kde-look.org/ kde-look.org].<br />
<br />
Official logos, icons, CD labels and other artwork for Arch Linux are provided in the {{AUR|archlinux-artwork}} package. After installing you can find such artwork at {{ic|/usr/share/archlinux/}}.<br />
<br />
==== Fonts ====<br />
<br />
===== Fonts in KDE look poor =====<br />
<br />
Try installing the {{Pkg|ttf-dejavu}} and {{Pkg|ttf-liberation}} packages. <br />
<br />
After the installation, be sure to log out and back in. You should not have to modify anything in ''System Settings > Fonts''.<br />
<br />
If you have personally set up how your [[Fonts]] render, be aware that System Settings may alter their appearance. When you go ''System Settings > Appearance > Fonts'', System Settings will likely alter your font configuration file ({{ic|fonts.conf}}). <br />
<br />
There is no way to prevent this but if you set the values to match your {{ic|fonts.conf}} file the expected font rendering will return (it will require you to restart your application or in a few cases for you to have to restart your desktop). <br />
<br />
Note too that Gnomes' Font Preferences will also do this if you use both desktop environments.<br />
<br />
===== Fonts are huge or seems disproportional =====<br />
<br />
Try to force fonts DPI to '''96''' on ''System Settings > Application Appearance > Fonts''.<br />
<br />
If it does not work try set DPI directly on Xorg configuration [[Xorg#Setting_DPI_manually|here]].<br />
<br />
==== Space efficiency ====<br />
<br />
Users with small screens (eg Netbooks) can change some setting to make KDE more space efficient. See [http://userbase.kde.org/KWin#Using_with_small_screens_(eg_Netbooks) upstream wiki] for more info. Also you can use [http://www.kde.org/workspaces/plasmanetbook/ KDE's Plasma Netbook] which is a workspace made specifically for small, lightweight netbook devices.<br />
<br />
=== Networking ===<br />
<br />
You can choose from the following tools:<br />
* NetworkManager. See [[NetworkManager#KDE4|NetworkManager]] for more information.<br />
* Wicd. See [[Wicd]] for more information.<br />
<br />
=== Printing ===<br />
<br />
{{Tip|Use the [[CUPS]] web interface for faster configuration.}}<br />
<br />
The printers are configured in this way can be found in applications KDE. <br />
<br />
You can also choose the printer configuration through ''System Settings > Printer Configuration''. To use this method, you must first install the packages {{Pkg|kdeutils-print-manager}} and {{Pkg|cups}}.<br />
<br />
You need to start the {{ic|avahi-daemon}} and {{ic|cupsd}} daemons first or you will get the following error: <br />
The service 'Printer Configuration' does not provide an interface 'KCModule' <br />
with keyword 'system-config- printer-kde/system-config-printer-kde.py' <br />
The factory does not support creating components of the specified type.<br />
<br />
If you are getting the following error, you need to give the user rights to manage printers: <br />
There was an error during CUPS operation: 'cups-authorization-canceled'<br />
<br />
For CUPS, this is set in {{ic|/etc/cups/cupsd.conf}}.<br />
<br />
Adding {{ic|lp}} to {{ic|SystemGroup}} allows anyone who can print to configure printers. You can, of course, add another group instead of {{ic|lp}}.<br />
{{hc|/etc/cups/cupsd.conf|# Administrator user group...<br />
SystemGroup sys root lp}}<br />
<br />
=== Samba/Windows support ===<br />
<br />
If you want to have access to Windows services install [[Samba]] (package {{Pkg|samba}}).<br />
<br />
You may then configure your Samba shares through:<br />
<br />
System Settings > Sharing > Samba<br />
<br />
=== KDE Desktop activities ===<br />
<br />
KDE Desktop Activities are Plasma based "virtual desktop"-like set of Plasma Widgets where you can independently configure widgets as if you had more than one screens/desktops. <br />
<br />
On your desktop, click the Cashew Plasmoid and on the pop-up window press "Activities".<br />
<br />
A plasma bar will appear at the bottom of the screen which presents you the current Plasma Desktop Activities which exist. You can then navigate between them by pressing their correspondent icon.<br />
<br />
=== Power saving ===<br />
<br />
KDE has an integrated power saving service called "'''Powerdevil Power Management'''" that may adjust the power saving profile of the system and/or the brightness of the screen (if supported).<br />
<br />
Since KDE 4.6, CPU frequency scaling is no longer managed by KDE. Instead it is assumed to be handled automatically by the the hardware and/or kernel. Arch uses {{ic|ondemand}} as default CPU Frequency governor from kernel vesion 3.3. So nothing need to be done for most cases. For detaild fine tune of the governor, please see [[CPU Frequency Scaling]].<br />
<br />
=== Monitoring changes on local files and directories ===<br />
<br />
KDE now uses '''inotify''' directly from the kernel with '''kdirwatch''' (included in kdelibs), so Gamin or FAM are no longer needed. You may want to install this {{AUR|kdirwatch}} from AUR which is a GUI frontend for kdirwatch.<br />
<br />
== System administration ==<br />
<br />
=== Set keyboard ===<br />
<br />
Navigate to:<br />
System Settings > Hardware > Input Devices > Keyboard<br />
There you may choose your keyboard model at first.<br />
<br />
In the "'''Layouts'''" tab, you choose the languages you may want to use by pressing the "Add Layout" button and therefore the variant and the language.<br />
<br />
In the "'''Advanced'''" tab, you can choose the keyboard combination you want in order to change the layouts in the "Key(s) to change layout" sub-menu.<br />
<br />
=== Terminate Xorg-server through KDE system settings ===<br />
<br />
Navigate to:<br />
System Settings > Input Devices > Keyboard > Advanced (tab) > "Key Sequence to kill the X server" submenu<br />
and tick the checkbox.<br />
<br />
=== Useful KCM ===<br />
<br />
KCM means KConfig Module. This modules help you to configure you system providing a interface on System Settings.<br />
<br />
'''Configuration for look&feel of your GTK apps.'''<br />
* {{Pkg|kde-gtk-config}}<br />
* {{AUR|kcm-gtk}}<br />
* {{AUR|kcm-qt-graphicssystem}}<br />
<br />
'''Configuration for the GRUB bootloader.'''<br />
* {{AUR|grub2-editor}}<br />
* {{AUR|kcm-grub2}}<br />
<br />
'''Configuration for Synaptics driver based touchpads.'''<br />
* {{AUR|synaptiks}}<br />
* {{AUR|kcm_touchpad}}<br />
<br />
'''Configuration for the [[Uncomplicated Firewall]] (UFW)''' <br />
* {{AUR|kcm-ufw}}<br />
<br />
'''Configuration for [[PolicyKit]]'''<br />
* {{AUR|kcm-polkit-kde-git}}<br />
<br />
'''Configuration for Wacom Tablet'''<br />
* {{AUR|kcm-wacomtablet}}<br />
<br />
More KCM can be found [http://kde-apps.org/index.php?xcontentmode=273 here].<br />
<br />
== Desktop search and semantic desktop ==<br />
<br />
According to [[wikipedia:Semantic_desktop|Wikipedia]], ''"the Semantic Desktop is a collective term for ideas related to changing a computer's user interface and data handling capabilities so that data is more easily shared between different applications or tasks and so that data that once could not be automatically processed by a computer can be (automatically processed)."''<br />
<br />
The KDE implementation of this concept is tied to (as of KDE 4.10) two major pieces of software, Akonadi and Nepomuk. Between the two of them, these programs look at your data and make an easily searchable index of it. The idea behind these pieces of software is to make your system "aware" of your data and give it context using meta-data and user-supplied tags.<br />
<br />
Soprano and Virtuoso are two dependencies of the Nepomuk Semantic Desktop. Since the relationship between the two major components and their dependencies is not very clear, the following sections try to shed some light on their inner workings.<br />
<br />
=== Virtuoso and Soprano ===<br />
<br />
The database used to store all the metadata used by the semantic desktop is a ''[[wikipedia:Resource_Description_Framework|Resource Description Framework (RDF)]]'' database called Virtuoso. Internally, Virtuoso may be looked as a relational database. (A [[wikipedia:Relational_model|relational database]] is different from a traditional single-table based database in the sense that it uses multiple tables related by a single key in order to store data.) It is currently controlled by OpenLink, and is available under commercial and an open source license.<br />
<br />
From the [http://techbase.kde.org/Projects/Nepomuk/ComponentOverview#Soprano KDE Techbase], ''Soprano is a Qt abstraction over databases. It provides a friendly Qt-based API for accessing different RDF stores. It currently supports 3 database backends - Sesame, Redland and Virtuoso. The KDE Semantic Stack only works with Virtuoso. Soprano also provides additional features such as serializing, parsing RDF data, and a client server architecture that is heavily used in Nepomuk.''<br />
<br />
=== Nepomuk ===<br />
<br />
Nepomuk stands for "Networked Environment for Personal, Ontology-based Management of Unified Knowledge". It is what allows all the tagging and labeling of files as well to take place and also serves as the way to actually read the Virtuoso databases. It provides an API to application developers which allows them to read the data collected by it.<br />
<br />
In the past, the "Strigi" service was used to collect data about the various files present on the system. However, due to many reasons, the most important of them being CPU and Memory usage, Strigi was replaced by a homegrown indexing service which is integrated with Nepomuk-Core.<br />
<br />
For further information about Nepomuk, [http://techbase.kde.org/Projects/Nepomuk/ComponentOverview#Nepomuk_Components this page] is a good resource. However, some of the information in the previous page has been rendered outdated according to [http://vhanda.in/blog/2012/11/nepomuk-without-strigi/ this blog post].<br />
<br />
==== Using and configuring Nepomuk ====<br />
<br />
In order to search using Nepouk on the KDE desktop, press {{ic|ALT+F2}} and type in your query. Nepomuk is enabled by default. It can be turned on and off in:<br />
System Settings > Desktop Search<br />
<br />
Nepomuk has to keep track of a lot of files. It is for this reason that it is recommended to increase the number of files that can be watched with inotify. In order to do that this command is a good option.<br />
# sysctl fs.inotify.max_user_watches=524288<br />
<br />
To do it persistently:<br />
# echo "fs.inotify.max_user_watches = 524288" >> /etc/sysctl.d/99-inotify.conf<br />
<br />
Restart Nepomuk to see the changes.<br />
<br />
==== KDE without Nepomuk ====<br />
<br />
If you wish to run KDE without Nepomuk, there exists a {{AUR|nepomuk-core-fake}} package in the AUR.<br />
{{Warning|As of now, Dolphin depends on {{Pkg|nepomuk-widgets}} and hence will break if used with the fake Nepomuk package.}}<br />
<br />
=== Akonadi ===<br />
<br />
Akonadi is a system meant to act as a local cache for PIM data, regardless of its origin, which can be then used by other applications. This includes the user's emails, contacts, calendars, events, journals, alarms, notes, and so on. It interfaces with the Nepomuk libraries to provide searching capabilities.<br />
<br />
Akonadi does not store any data by itself: the storage format depends on the nature of the data (for example, contacts may be stored in vCard format).<br />
<br />
For more information on Akonadi and its relationship with Nepomuk, see [http://blogs.kde.org/node/4503] and [http://cmollekopf.wordpress.com/2013/02/13/kontact-nepomuk-integration-why-data-from-akonadi-is-indexed-in-nepomuk/].<br />
<br />
==== Disabling Akonadi ====<br />
<br />
See this [http://userbase.kde.org/Akonadi#Disabling_the_Akonadi_subsystem section in the KDE userbase].<br />
<br />
==== Database configuration ====<br />
<br />
Start {{ic|akonaditray}} from package {{Pkg|kdepim-runtime}}. Right click on it and select '''configure'''. In the Akonadi server configure tab, you can:<br />
* Configuring Akonadi to use MySQL/MariaDB Server<br />
* Configuring Akonadi to use PostgreSQL Server<br />
* Configuring Akonadi to use SQLite<br />
<br />
==== Running KDE without Akonadi ====<br />
<br />
The package {{AUR|akonadi-fake}} is a good option for those who wish to run KDE without Akonadi.<br />
<br />
== Phonon ==<br />
<br />
=== What is Phonon? ===<br />
<br />
From [[Wikipedia:Phonon|Wikipedia]]:<br />
''Phonon is the multimedia API for KDE 4. Phonon was created to allow KDE 4 to be independent of any single multimedia framework such as GStreamer or xine and to provide a stable API for KDE 4's lifetime. It was done for various reasons: to create a simple KDE/Qt style multimedia API, to better support native multimedia frameworks on Windows and Mac OS X, and to fix problems of frameworks becoming unmaintained or having API or ABI instability.<br />
''<br />
<br />
'''Phonon''' is being widely used within KDE, for both audio (e.g., the System notifications or KDE audio apps) and video (e.g., the Dolphin video thumbnails).<br />
<br />
=== Which backend should I choose? ===<br />
<br />
You can choose between various backends, like GStreamer ({{Pkg|phonon-gstreamer}}) or VLC ({{Pkg|phonon-vlc}}) available in the [[official repositories]] and MPlayer ({{AUR|phonon-mplayer-git}}), ({{AUR|phonon-quicktime-git}}) and ({{AUR|phonon-avkode-git}}) available on [[AUR]]. Most users will want GStreamer or VLC which have the best upstream support. Note that multiple backends can be installed at once and you can switch between them via ''System Settings > Multimedia > Phonon > Backend''.<br />
<br />
{{Note|According to the [http://userbase.kde.org/Phonon#Backend_libraries KDE UserBase], Phonon-MPlayer is currently unmaintained}}<br />
<br />
According to [http://lists.kde.org/?l=kde-multimedia&m=137994906723790&w=2 this mail in the KDE-Multimedia mailing list], users should prefer VLC over GStreamer.<br />
<br />
== Useful applications ==<br />
<br />
The official set of KDE applications may be found [http://www.kde.org/applications/ here].<br />
<br />
=== Yakuake ===<br />
<br />
[http://yakuake.kde.org/ This] application provides a Quake-like terminal emulator, which is toggled visible using the F12 key. It also has support for multiple tabs. Yakuake can be installed by package {{Pkg|yakuake}}.<br />
<br />
=== KDE Telepathy ===<br />
<br />
[http://community.kde.org/KTp KDE Telepathy] is a project with the goal to closely integrate Instant Messaging with the KDE desktop. It utilizes the Telepathy framework as a backend, and is intended to replace Kopete.<br />
<br />
To install all Telepathy protocols install the {{Grp|telepathy}} group.<br />
To use the KDE Telepathy client, install the {{Pkg|kde-telepathy-meta}} package that includes all the packages contained in the {{Grp|kde-telepathy}} group .<br />
<br />
== Tips and tricks ==<br />
<br />
=== Configure KWin to use OpenGL ES ===<br />
<br />
Beginning with KWin version 4.8 it is possible to use the separately built binary '''kwin_gles''' as a replacement for kwin. It behaves almost the same as the kwin executable in OpenGL2 mode with the slight difference that it uses ''egl'' instead of ''glx'' as the native platform interface. To test kwin_gles you just have to run {{ic|kwin_gles --replace}} in Konsole.<br />
If you want to make this change permanent you have to create a script in {{ic|$(kde4-config --localprefix)/env/}} which exports {{ic|1=KDEWM=kwin_gles}}.<br />
<br />
=== Enabling audio thumbnails under Konqueror/Dolphin file managers ===<br />
<br />
For thumbnails of audio files in Konqueror and Dolphin install {{AUR|audiothumbs}} from AUR.<br />
<br />
=== Enabling video thumbnails under Konqueror/Dolphin file managers ===<br />
<br />
For thumbnails of videos in konqueror and dolphin install {{Pkg|kdemultimedia-mplayerthumbs}} or {{Pkg|kdemultimedia-ffmpegthumbs}}.<br />
<br />
=== Speed up application startup ===<br />
<br />
User Rob wrote on his blog this "[http://kdemonkey.blogspot.nl/2008/04/magic-trick.html magic trick]" to improve applications start up by 50-150ms.<br />
To enable it, create this folder in your home:<br />
$ mkdir -p ~/.compose-cache/<br />
<br />
''For those curious about what is going on here, this enables an optimization which Lubos (of general KDE speediness fame) came up with some time ago and was then rewritten and integrated into libx11. Ordinarily on startup applications read input method information from {{ic|/usr/share/X11/locale/''your locale''/Compose}}. This Compose file is quite long (>5000 lines for the en_US.UTF-8 one) and takes some time to process. libX11 can create a cache of the parsed information which is much quicker to read subsequently, but it will only re-use an existing cache or create a new one in {{ic|~/.compose-cache}} if the directory already exists.''<br />
<br />
=== Hiding partitions ===<br />
<br />
In Dolphin, it is as simple as right-clicking on the partition in the {{ic|Places}} sidebar and selecting {{ic|Hide ''partition''}}. Otherwise...<br />
<br />
If you wish to prevent your internal partitions from appearing in your file manager, you can create an udev rule, e.g:<br />
<br />
{{hc|/etc/udev/rules.d/10-local.rules|2=<br />
KERNEL=="sda[0-9]", ENV{UDISKS_IGNORE}="1"<br />
}}<br />
<br />
The same thing for a certain partition:<br />
<br />
KERNEL=="sda1", ENV{UDISKS_IGNORE}="1"<br />
KERNEL=="sda2", ENV{UDISKS_IGNORE}="1"<br />
<br />
=== Konqueror tips ===<br />
<br />
==== Disabling smart key tooltips (browser) ====<br />
<br />
To disable those smart key tooltips in Konqueror (pressing {{ic|Ctrl}} on a web page), use ''Settings > Configure Konqueror > Web Browsing'' and uncheck ''Enable Access Key activation with Ctrl key'' o<br />
<br />
{{hc|~/.kde4/share/config/konquerorrc|2=<br />
[Access Keys]<br />
Enabled=false<br />
}}<br />
<br />
==== Using WebKit ====<br />
<br />
WebKit is an open source browser engine developed by Apple Inc. It is a derivative from the KHTML and KJS libraries and contains many improvements. WebKit is used by Safari, Google Chrome and rekonq.<br />
<br />
It is possible to use WebKit in Konqueror instead of KHTML. First install the {{Pkg|kwebkitpart}} package.<br />
<br />
Then, after executing Konqueror, navigate to ''Settings > Configure Konqueror > General > Default web browser engine'' and set it as {{ic|WebKit}}.<br />
<br />
=== Firefox integration ===<br />
<br />
See [[Firefox#KDE_integration|Firefox]].<br />
<br />
=== Setting the screensaver background to the same as the current one ===<br />
<br />
For the beauty of a system you can placed your current background for your Kscreensaver instead of the default.<br />
<br />
KDE by default is [https://bugs.kde.org/show_bug.cgi?id=312828 not able] to change this for the 'Simple Lock', but a [http://lists.opensuse.org/opensuse-kde/2013-02/msg00082.html workaround] [http://forum.kde.org/viewtopic.php?f=66&t=110039 exists]:<br />
<br />
{{hc|/usr/share/apps/ksmserver/screenlocker/org.kde.passworddialog/contents/ui/|<br />
[...]<br />
''#source: theme.wallpaperPathForSize(parent.width, parent.height)''<br />
source: "1920x1080.jpg"<br />
[...]<br />
}}<br />
<br />
Now you copy your current background image to {{ic|"1920x1080.jpg"}}. <br />
<br />
Note you have to redo this for each update of the package {{Pkg|kdebase-workspace}}.<br />
<br />
=== Setting lockscreen wallpaper to arbitrary image ===<br />
<br />
Copy an existing wallpaper profile as a template:<br />
$ cp -r /usr/share/wallpapers/''ExistingWallpaper'' ~/.kde4/share/wallpapers/<br />
<br />
Change the name of the directory, and edit {{ic|metadata.desktop}}:<br />
<br />
{{hc|~/.kde4/share/wallpapers/''MyWallpaper''/metadata.desktop|2=<br />
[Desktop Entry]<br />
Name=MyWallpaper<br />
X-KDE-PluginInfo-Name=MyWallpaper<br />
}}<br />
<br />
Remove existing images ({{ic|contents/screenshot.png}} and {{ic|images/*}}):<br />
$ rm ~/.kde4/share/wallpapers/MyWallpaper/contents/screenshot.png<br />
$ rm ~/.kde4/share/wallpapers/MyWallpaper/contents/images/*<br />
<br />
Copy new image in:<br />
$ cp ''path/to/MyWallpaper.png'' MyWallpaper/contents/images/1920x1080.png<br />
<br />
Edit the metadata profile for the current theme:<br />
{{hc|~/.kde4/share/apps/desktoptheme/MyTheme/metadata.desktop|2=<br />
[Wallpaper]<br />
defaultWallpaperTheme=NewWallpaper<br />
defaultFileSuffix=.png<br />
defaultWidth=1920<br />
defaultHeight=1080<br />
}}<br />
<br />
Lock the screen to check that it worked.<br />
<br />
{{Note|This method allows you to set the lockscreen background, without changing any system-wide settings. For the change to be system-wide, create the new wallpaper profile in {{ic|/usr/share/wallpapers}}.}}<br />
<br />
== Troubleshooting ==<br />
<br />
=== Configuration related ===<br />
<br />
Many issues in KDE are related to configuration. One way to resolve upgrade problems is to start over with a fresh KDE config. <br />
<br />
==== Reset all KDE configuration ====<br />
<br />
To test whether your config is the problem try quitting your KDE session by logging out and, in a tty, run<br />
$ cp ~/.kde4 ~/.kde4.safekeeping<br />
$ rm .kde4/{cache,socket,tmp}-$(hostname)<br />
<br />
The ''rm'' command just removes symbolic links which will be recreated by KDE automatically. Now start a new KDE session to see the results.<br />
<br />
If the problem is resolved, you will have a fresh, problem-free {{ic|~/.kde4/}}. You can gradually move parts of your saved configuration back, restarting your session regularly to test, to identify the problematic parts of your config. Some files here are named after applications so you will probably be able to test these without needing to restart KDE.<br />
<br />
==== File Indexer Service not working even after enabling everything properly ====<br />
<br />
This is caused due to a corrupted Nepomuk database. It may be remedied by moving the database or deleting it all together. Log out of KDE and issue this command from a virtual console:<br />
<br />
$ mv ~/.kde4/share/apps/nepomuk ~/.kde4/share/apps/nepomuk_backup<br />
<br />
to move your existing (and corrupt) nepomuk database. It will be recreated when you log in again.<br />
<br />
==== Plasma desktop behaves strangely ====<br />
<br />
Plasma issues are usually caused by unstable '''plasmoids''' or '''plasma themes'''. First, find which was the last plasmoid or plasma theme you had installed and disable it or uninstall it. <br />
<br />
So, if your desktop suddenly exhibits "locking up", this is likely caused by a faulty installed widget. If you cannot remember which widget you installed before the problem began (sometimes it can be an irregular problem), try to track it down by removing each widget until the problem ceases. Then you can uninstall the widget, and file a bug report (bugs.kde.org) '''only if it is an official widget'''. If it is not, it is recommended you find the entry on kde-look.org and inform the developer of that widget about the issue (detailing steps to reproduce, etc).<br />
<br />
If you cannot find the problem, but you do not want ''all'' the KDE settings to be lost, do:<br />
<br />
$ rm -r ~/.kde4/share/config/plasma*<br />
<br />
This command will '''delete all plasma related configs''' of your user and when you will relogin into KDE, you will have the '''default''' settings back. You should know that this action '''cannot be undone'''. You ought to create a backup folder and copy all the plasma related configs in it.<br />
<br />
==== Clean cache to resolve upgrade problems ====<br />
<br />
The [https://bbs.archlinux.org/viewtopic.php?id=135301 problem] may be caused by old cache. Sometimes after an upgrade, the old cache might introduce strange, hard to debug behaviour such as unkillable shells, hangs when changing various settings and several other problems such as ark being unable to unrar or unzip or amarok not recognizing any of your musics. This solution can also resolve problems with KDE and QT programmes looking bad following upgrade.<br />
<br />
Rebuild your cache with the following commands:<br />
<br />
$ rm ~/.config/Trolltech.conf<br />
$ kbuildsycoca4 --noincremental<br />
<br />
Hopefully, your problems are now fixed.<br />
<br />
=== Clean akonadi configuration to fix KMail ===<br />
<br />
First, make sure that KMail is not running. Then backup configuration:<br />
$ mv ~/.local/share/akonadi ~/.local/share/akonadi-old<br />
$ mv ~/.config/akonadi ~/.config/akonadi-old<br />
<br />
Start ''SystemSettings > Personal'' and remove all the resources. Go back to Dolphin and remove the original {{ic|~/.local/share/akonadi}} and<br />
{{ic|~/.config/akonadi}} - the copies you made ensure that you can back-track if necessary.<br />
<br />
Now go back to the System Settings page and carefully add the necessary resources. You should see the resource reading in your mail folders. Then start Kontact/KMail to see if it work properly.<br />
<br />
=== Getting current state of KWin for support and debug purposes ===<br />
<br />
This command prints out a wonderful summary of the current state of KWin including used options, used compositing backend and relevant OpenGL driver capabilities. [http://blog.martin-graesslin.com/blog/2012/03/on-getting-help-for-kwin-and-helping-kwin/ See more at Martin's blog]<br />
<br />
$ qdbus org.kde.kwin /KWin supportInformation<br />
<br />
=== KDE4 does not finish loading ===<br />
<br />
There might be a situation in which the graphic driver might create a conflict when starting KDE4. This situation happens after the login but before finishing loading the desktop, making the user wait indefinitely at the loading screen. Until now the only users confirmed to be affected by this are the ones that use Nvidia drivers and KDE4.<br />
<br />
A solution for Nvidia users:<br />
<br />
{{hc|~/.kde4/share/config/kwinrc|2=<br />
[Compositing]<br />
Enabled=false<br />
}}<br />
For more information look at this [https://bbs.archlinux.org/viewtopic.php?pid=932598 thread].<br />
<br />
If a minimal install was done, make sure you installed the required font by your phonon backend listed here: [[#Minimal install]]<br />
<br />
=== KDE and Qt programs look bad when in a different window manager ===<br />
<br />
If you are using KDE or Qt programs but not in a full KDE session (specifically, you did not run {{ic|startkde}}), then as of KDE 4.6.1 you will need to tell Qt how to find KDE's styles (Oxygen, QtCurve etc.)<br />
<br />
You just need to set the environment variable {{ic|QT_PLUGIN_PATH}}. E.g. put:<br />
<br />
export QT_PLUGIN_PATH=$HOME/.kde4/lib/kde4/plugins/:/usr/lib/kde4/plugins/<br />
<br />
into your {{ic|/etc/profile}} (or {{ic|~/.profile}} if you do not have root access). qtconfig should then be able to find your KDE styles and everything should look nice again!<br />
<br />
Alternatively, you can symlink the Qt styles directory to the KDE styles one:<br />
# ln -s /usr/lib/kde4/plugins/styles/ /usr/lib/qt/plugins/styles<br />
<br />
Under Gnome you can try to install the package libgnomeui.<br />
<br />
=== Graphical related issues ===<br />
<br />
==== Low 2D desktop performance (or) artifacts appear when on 2D ====<br />
<br />
===== GPU driver problem =====<br />
<br />
Make sure you have the proper driver for your card installed, so that your desktop is at least 2D accelerated. Follow these articles for more information: [[ATI]], [[NVIDIA]], [[Intel]] for more information, in order to make sure that everything is all right.<br />
The open-source ATI and Intel drivers and the proprietary (binary) Nvidia driver should theoretically provide the best 2D and 3D acceleration.<br />
<br />
===== The Raster engine workaround =====<br />
<br />
If this does not solve your problems, maybe your driver does not provide a good '''XRender''' acceleration which the current Qt painter engine relies on by default. <br />
<br />
You can change the painter engine to software based only by invoking the application with the {{ic|-graphicssystem raster}} command line. This rendering engine can be set as the default one by recompiling Qt with the same as configure option, {{ic|-graphicssystem raster}}. <br />
<br />
The raster paint engine enables the CPU to do the majority of the painting, as opposed to the GPU. You may get better performance, depending on your system. This is basically a work-around for the terrible Linux driver stack, since the CPU should obviously not be doing graphical computations since it is designed for fewer threads of greater complexity, as opposed to the GPU which is many threads but lesser computational strength. So, only use Raster engine if you are having problems or your GPU is much slower than you CPU, otherwise is better to use XRender.<br />
<br />
Since Qt 4.7+, recompiling Qt is not needed. Simply export {{ic|1=QT_GRAPHICSSYSTEM=raster}}, or {{ic|opengl}}, or {{ic|native}} (for the default). Raster depends on the CPU, OpenGL depends on the GPU and high driver support, and Native is just using the X11 rendering (mixture, usually).<br />
<br />
'''The best and automatic way to do that''' is to install {{AUR|kcm-qt-graphicssystem}} from AUR and configure this particular Qt setting through:<br />
<br />
System Settings > Qt Graphics System<br />
<br />
For more information, consult this [http://apachelog.wordpress.com/2010/09/05/qt-graphics-system-kcm/ KDE Developer blog entry] and/or this [http://labs.trolltech.com/blogs/2009/12/18/qt-graphics-and-performance-the-raster-engine/ Qt Developer blog entry].<br />
<br />
==== Low 3D desktop performance====<br />
<br />
KDE begins with desktop effects enabled. Older cards may be insufficient for 3D desktop acceleration. You can disable desktop effects in:<br />
System Settings > Desktop Effects<br />
or you can toggle desktop effects with {{ic|Alt+Shift+F12}}.<br />
<br />
{{Note| You may encounter such problems with 3D desktop performance even when using a more powerful graphics card, especially the catalyst proprietary driver ({{ic|fglrx}}). This driver is known for having issues with 3D acceleration. Visit [[ATI|the ATi Wiki page]] for more troubleshooting.}}<br />
<br />
==== Desktop compositing is disabled on my system with a modern Nvidia GPU ====<br />
<br />
Sometimes, KWin may have settings in its configuration file ({{ic|kwinrc}}) that ''may'' cause a problem on re-activating the 3D desktop {{ic|OpenGL}} compositing. That could be caused randomly (for example, due to a sudden Xorg crash or restart, and it gets corrupted), so, in case that happens, delete your {{ic|~/.kde4/share/config/kwinrc}} file and relogin. The KWin settings will turn to the KDE default ones and the problem should be probably gone.<br />
<br />
==== Flickering in fullscreen when compositing is enabled ====<br />
<br />
As of KDE SC 4.6.0, there is an option in ''Sytem Settings > Desktop Effect > Advanced > Suspend desktop effects for fullscreen windows''. Uncheck it would tell kwin to disable unredirect fullscren.<br />
<br />
==== Screen Tearing with desktop compositing enabled ====<br />
<br />
{{Note|With the recent update of KDE to 4.11, several new Vsync options have been added, which may help with screen tearing.}}<br />
<br />
KWin may suffer from screen tearing while desktop effects are enabled. Uncheck the VSync option under ''System Settings > Desktop Effects > Advanced > Use Vsync''.<br />
<br />
For proprietary driver users, ensure that the driver's VSync option is enabled ({{ic|amdccle}} for [[Catalyst]] users, and nvidia-settings for [[NVIDIA]] users).<br />
<br />
==== Display settings lost on reboot (multiple monitors) ====<br />
Installing {{Pkg|kscreen}} might fix the problem unless your screens share the same EDID. Kscreen is the improved screen management software for KDE, more information can be found [https://fedoraproject.org/wiki/Changes/KScreen?rd=Features/KScreen here].<br />
<br />
=== Sound problems under KDE ===<br />
<br />
==== ALSA related problems ====<br />
<br />
{{Note|First make sure you have {{Pkg|alsa-lib}} and {{Pkg|alsa-utils}} installed.}}<br />
<br />
===== "Falling back to default" messages when trying to listen to any sound in KDE =====<br />
<br />
When you encounter such messages:<br />
The audio playback device ''name_of_the_sound_device'' does not work.<br />
Falling back to default<br />
Go to:<br />
System Settings > Multimedia > Phonon<br />
and set the device named {{ic|default}} above all the other devices in each box you see.<br />
<br />
===== I cannot play MP3 files when using the GStreamer Phonon backend =====<br />
<br />
That can be solved by installing the GStreamer plugins (package group {{Grp|gstreamer0.10-plugins}}). If you still encounter problems, you can try changing the Phonon backend used by installing another such as {{Pkg|phonon-vlc}}.<br />
Then make sure the backend is preferred via:<br />
<br />
System Settings > Multimedia > Phonon > Backend (tab)<br />
<br />
=== Konsole does not save commands' history ===<br />
<br />
By default console commands' history is saved only when you type 'exit' in console. When you close Konsole with 'x' in the corner it does not happen.<br />
To enable autosaving after every command execution:<br />
<br />
{{hc|~/.bashrc|<nowiki><br />
shopt -s histappend<br />
[[ "${PROMPT_COMMAND}" ]] && PROMPT_COMMAND="$PROMPT_COMMAND;history -a" || PROMPT_COMMAND="history -a"<br />
</nowiki>}}<br />
<br />
=== KDE password prompts display three bullets per char ===<br />
<br />
You can change it under ''System Settings > Account Details > Password & User Account'':<br />
* Show one bullet for each letter<br />
* Show three bullets for each letter<br />
* Show nothing<br />
<br />
=== Nepomukserver process still autostart even with semantic desktop disabled ===<br />
<br />
Go to ''System Settings > Startup and Shutdown > Service Manager > Startup Services'' and uncheck the Nepomuk Search Module.<br />
<br />
=== Dolphin and File Dialogs are extremely slow to start everytime ===<br />
<br />
May be caused by the upower service. If the upower service is not needed on your system, it can be disabled:<br />
<br />
# systemctl disable upower<br />
# systemctl mask upower<br />
<br />
Obviously this will not have any side effect on a desktop system.<br />
<br />
=== Default PDF viewer in GTK applications under KDE ===<br />
<br />
In some cases when you have installed [[Inkscape]], [[Gimp]] or other graphic programs, GTK applications ([[Firefox]] among all) might not select Okular as the default PDF application, and they are not going to follow the KDE settings on default applications. You can use the following user command to make Okular the default application again.<br />
<br />
$ xdg-mime default kde4-okularApplication_pdf.desktop application/pdf<br />
<br />
If you are using a different PDF viewer application, or a different mime-type is misbehaving, you should change {{ic|kde4-okularApplication_pdf.desktop}} and {{ic|application/pdf}} respectively according to your needs.<br />
<br />
For more information, consult [[Default Applications]] wiki page.<br />
<br />
== Unstable releases ==<br />
<br />
When KDE is reaching beta or RC milestone, KDE "unstable" packages are uploaded to the [kde-unstable] repo. They stay there until KDE is declared stable and passes to [extra].<br />
<br />
You may add it with:<br />
<br />
{{hc|/etc/pacman.conf|2=<br />
[kde-unstable]<br />
Include = /etc/pacman.d/mirrorlist<br />
}}<br />
<br />
# [kde-unstable] is based upon testing. Therefore, you need to enable the repositories in the following order: [kde-unstable], [testing], [core], [extra], [community-testing], [community]. <br />
# To update from a previous KDE installation, run: {{ic|# pacman -Syu}} or {{ic|# pacman -S kde-unstable/kde}}<br />
# If you do not have KDE installed, you might have difficulties to install it by using groups (limitation of pacman)<br />
# '''Subscribe and read the [https://mailman.archlinux.org/pipermail/arch-dev-public/ arch-dev-public] mailing list'''<br />
# Make sure [[#Distro_and_Upstream_bug_report|you make bug reports]] if you find any issues.<br />
<br />
== Other KDE projects ==<br />
<br />
=== Trinity ===<br />
<br />
From the release of KDE 4.x, the developers dropped support for KDE 3.5.x. Trinity Desktop Environment is a fork of KDE3 developed by Timothy Pearson ([http://trinitydesktop.org/ trinitydesktop.org]). This project aims to keep the KDE3.5 computing style alive, as well as polish off any rough edges that were present as of KDE 3.5.10. See [[Trinity]] for more info.<br />
<br />
{{Warning|KDE 3 is no longer maintained and supported by the KDE developers. The "Trinity KDE" is maintained by the Trinity project commmunity. Use KDE 3 on your own risk, regarding any bugs, performance issues or security risks.}}<br />
<br />
== Bugs ==<br />
<br />
It is preferrable that if you find a minor or serious bug, you should visit [https://bugs.archlinux.org the Arch Bug Tracker] or/and [http://bugs.kde.org KDE Bug Tracker] in order to report that. Make sure that you be clear on what you want to report.<br />
<br />
If you have any issue and you write about in on the Arch forums, first make sure that you have '''fully''' updated your system using a good sync mirror (check [https://www.archlinux.de/?page=MirrorStatus here]) or try [[Reflector]].<br />
<br />
== See also ==<br />
<br />
* [http://www.kde.org] - KDE homepage<br />
* [https://bugs.kde.org] - KDE bug tracker<br />
* [https://bugs.archlinux.org] - Arch Linux bug tracker<br />
* [https://projects.kde.org] - KDE Projects</div>JKAbramshttps://wiki.archlinux.org/index.php?title=User:Chrisl/Installing_Arch_Using_Old_Installation_Media&diff=263928User:Chrisl/Installing Arch Using Old Installation Media2013-06-23T06:33:21Z<p>JKAbrams: fixed sentence</p>
<hr />
<div>[[Category:Getting and installing Arch]]<br />
{{Article summary start}}<br />
{{Article summary text|This article give additional steps to the official installation guide, to allow installing Arch using an old media cd using the [https://github.com/falconindy/arch-install-scripts Arch Install Scripts] instead of AIF.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Installation Guide}}: You should still follow the official guide steps.<br />
{{Article summary end}}<br />
{{Note|This guide is only for installation media version 2011.08.19 and older. For more recent versions, just follow the regular [[Installation Guide]]}}<br />
In the past, it didn't really matter what version of the installation media was used to install arch, as long remote repos were used, the result was an updated arch installation.<br />
<br />
That is still true, but several changes have occurred in arch, including [[pacman|pacman4]] and the [[systemd]] adoption, that may make the installation difficult using the media iso 2011.08.19 and older.<br />
<br />
The goal of this article is to provide few additional steps to the [[Installation Guide]], in order to allow you to use an old installation media to install arch, using the new [https://github.com/falconindy/arch-install-scripts Arch Install Scripts] instead of AIF.<br />
<br />
This is useful in situations like this:<br />
<br />
* Some VPS providers only provide iso files of old media versions.<br />
* Installation on older computers. While the 2011.08.19 i686 iso was able to boot with only 64M RAM and install arch (activating swap), more recent versions can't.<br />
* Maybe an old media cd is the only media you have at hand to install arch at any given moment.<br />
<br />
Again, this are only additional steps. You should still follow the [[Installation Guide]].<br />
<br />
This steps have been tested using 2010.05 and 2011.08.19 installation media cds.<br />
<br />
==Install the Arch Install Scripts==<br />
* Follow the guide until you get internet access.<br />
<br />
* Install {{Pkg|arch-install-scripts}} from the [[Official Repositories|official repositories]], making sure you update the database; do it like this:<br />
<br />
{{bc|# pacman -Sy arch-install-scripts}}<br />
<br />
{{Note|Say '''no''' to the question about updating pacman.}}<br />
<br />
* If you are using a media '''older''' than 2011.08.19, edit both {{ic|/usr/bin/pacstrap}} and {{ic|/usr/bin/arch-chroot}}. Look for a line like this:<br />
<br />
{{bc|1=mount -t devtmpfs udev "$1/dev" -o mode=0755,nosuid &&}}<br />
<br />
And change it to this:<br />
<br />
{{bc|1=mount /dev "$1/dev" -o bind,mode=0755,nosuid &&}}<br />
<br />
on both files.<br />
<br />
Again, that is '''not''' necessary for 2011.08.19 media.<br />
<br />
==Install haveged==<br />
* Continue the steps, and after you have done {{ic|pacstrap /mnt base base-devel}}, do: <br />
<br />
{{bc|# pacstrap /mnt haveged}}<br />
<br />
==Edit the fstab file==<br />
* Omit using genfstab. That script does not work on older media. You'll need to edit the {{ic|/mnt/etc/fstab}} file by hand.<br />
You can use the content of {{ic|/etc/mtab}} as reference.<br />
<br />
==Fixing Pacman==<br />
Once you are inside the {{ic|arch-choot /mnt}}:<br />
<br />
* If you are using an installation media '''older''' than 2011.08.19, you'll need to update pacman's database. Do it like this:<br />
<br />
{{bc|# pacman-db-upgrade}}<br />
<br />
That is '''not''' necessary for 2011.08.19 media.<br />
<br />
* This steps will fix the arch signatures keyring:<br />
{{bc|<br />
# /usr/sbin/haveged -w 1024 -v 1<br />
# pacman-key --init<br />
# pacman -U /var/cache/pacman/pkg/archlinux-keyring*<br />
}}<br />
<br />
* Do the rest of the steps normally.</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Talk:Systemd&diff=233968Talk:Systemd2012-11-05T22:24:05Z<p>JKAbrams: </p>
<hr />
<div>== Display manager fails to load with fast SSD ==<br />
<br />
I was having a problem with my display manager (LXDM) not loading on my laptop, which has a Sandisk Extreme SSD.<br />
Xorg.log would show errors like "No screens found."<br />
<br />
I eventually figured out that the problem was that my computer was booting so fast that KMS didn't have enough time to kick in before X was started. I solved by adding the KMS driver (i915 in my case) to the initramfs.<br />
<br />
Just a tip for SSD users, not sure if it should be added to the page or not.<br> --[[User:Steev|Steev]] ([[User talk:Steev|talk]]) 16:59, 2 September 2012 (UTC)<br />
:This is a general problem that needs to be solved in the display manager. GDM already implements the bits for the [http://cgit.freedesktop.org/systemd/systemd/commit/?id=f1a8e221ecacea23 CanGraphical] flag.<br />
:-- [[User:Falconindy|Falconindy]] ([[User talk:Falconindy|talk]]) 21:34, 2 September 2012 (UTC)<br />
<br />
== Hibernation with systemd ==<br />
<br />
The hibernation section should be considered a hack since systemd does not directly handle the backend that handles power management. Systemd uses the Upower interface to handle such requests<br>-- [[User:Yungtrizzle|Yungtrizzle]] ([[User talk:Yungtrizzle|talk]]) 06:25, 10 October 2012<br />
<br />
:I talked about hibernation process with Lennart Poettering and he said that systemd-hibernate does only "echo disk > /sys/power/state" . As far as i can see, it works perfectly with tuxonice, since it seems it is now using the same userspace API as kernel hibernation; so it works even without hibernate-script installed (i use it without that package). <br />
:-- [[User:Nierro|Nierro]] ([[User talk:Nierro|talk]]) 13:54, 24 October 2012<br />
<br />
:: what is the #Hibernation section all about anyway? It makes it sound like you need to use uswsusp to hibernate while it should work out of the box just fine. It doesn't explain at all why you would want to use uswsusp instead of the default command. I don't use hibernate nor do I know what uswsusp actually does, so what am I missing here? ::-- [[User:65kid|65kid]] ([[User talk:65kid|talk]]) 15:12, 25 October 2012 (UTC)<br />
<br />
:::I agree with 65kid. In fact, systemctl hibernate works out of the box (it only does an "echo disk...", nothing else). We don't need uswsusp at all. I tried with stock arch kernel and it works.<br />
:::-- [[User:Nierro|Nierro]] ([[User talk:Nierro|talk]]) 11:24, 26 October 2012<br />
<br />
::::Then I suggest that - unless someone explains why you would want to use uswsusp - we remove this whole section because it is nothing but confusing. This article is already way too big to waste text on something that doesn't seem to make any sense.<br />
::::-- [[User:65kid|65kid]] ([[User talk:65kid|talk]]) 10:10, 26 October 2012 (UTC)<br />
<br />
::::: I went ahead and removed the irrelevant information from the page, moving it to [[Uswsusp]]. I also added a note pointing readers there if they want to use another backend for suspending or hibernating.<br />
:::::-- [[User:Ifaigios|Ifaigios]] ([[User talk:Ifaigios|talk]]) 18:16, 26 October 2012 (UTC)<br />
<br />
:::::: Hey [[User:Nierro|Nierro]], do {{ic|systemctl hibernate}} and {{ic|systemctl suspend}} really do different things on your box? In my setup (linux-pf, systemd 195-2), if I do the latter, my box is also in suspend mode, meaning that my power button is glowing on and off and I don't see grub after pressing the power button again but are back to my desktop almost immediately. To me, it rather seems as if {{ic|systemctl hibernate}} goes into hybrid mode?<br />
::::::-- [[User:Jakobh|jakobh]] [[User talk:Jakobh|✉]] 10:07, 29 October 2012 (UTC)<br />
<br />
:::::: Got an answer to the question on the systemd mailing list now: [http://lists.freedesktop.org/archives/systemd-devel/2012-October/007245.html Link] <br />
::::::-- [[User:Jakobh|jakobh]] [[User talk:Jakobh|✉]] 17:56, 30 October 2012 (UTC)<br />
<br />
== <s>Removing rc.local</s> ==<br />
<br />
It isn't clear how to get rid of rc.local. It would be useful to include this statement from the forum discussion in moving from a mixed system to a pure system:<br />
<br />
Go through {{ic|/etc/rc.local}} and {{ic|/etc/rc.local.shutdown}} and turn them into service files (or, if you intend to keep them as they are, copy {{ic|/usr/lib/systemd/system/rc-local{,.shutdown}.service}} to {{ic|/etc/systemd/system/}}).<br>-- [[User:Myshkin|Myshkin]] ([[User talk:Myshkin|talk]]) 00:21, 13 Oct 2012<br />
* I added a new section [[Systemd#.2Fetc.2Frc.local_emulation_for_systemd]] that covers how to emulate {{ic|/etc/rc.local}} in a pure systemd environment. Closing.<br />
:-- [[User:Jstjohn|Jstjohn]] ([[User talk:Jstjohn|talk]]) 21:04, 30 October 2012 (UTC)<br />
<br />
== <s>Replacing ConsoleKit with systemd-logind -> networkmanager</s> ==<br />
<br />
As of {{pkg|networkmanager}} 0.9.6.0-2 in [extra] we do no more have to recompile it with systemd support from [[ABS]], is this right? So the note should be upgraded.<br />
Am i missing anything?<br> -- [[User:Nierro|Nierro]] ([[User talk:Nierro|talk]]) 09:31, 15 October 2012<br />
<br />
: 0.9.6.0-2 in [extra] was compiled on 2012-09-19 and the change to systemd was on 2012-09-29, so as far as I can see, it still needs to be recompiled. https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/networkmanager&id=c34580e6e35b9e87f7dc27f360507143d4fd9106<br />
:-- [[User:65kid|65kid]] ([[User talk:65kid|talk]]) 20:00, 15 October 2012 (UTC)<br />
<br />
::Damn, you're right. I did not see that pkgrel=3 while we are still using -2. Sorry, it means i'm still using my recompiled package, while i thought i was using the [extra] one.<br />
::-- [[User:Nierro|Nierro]] ([[User talk:Nierro|talk]]) 16:35, 15 October 2012<br />
<br />
:::{{pkg|networkmanager}} 0.9.6.4-1 was just pushed to [extra]. NetworkManager does not have to be recompiled anymore. Closing.<br />
:::-- [[User:Jstjohn|Jstjohn]] ([[User talk:Jstjohn|talk]]) 00:13, 31 October 2012 (UTC)<br />
<br />
== video group is still needed! ==<br />
<br />
"Adding your user to groups (optical, audio, scanner, ...) is not necessary for most use cases with systemd. The groups can even cause some functionality to break." ([[Systemd#Supplementary_information]])<br />
<br />
This statement might be too generic. For example, without the video group, mesa will use the llvm driver instead of the Gallium AMD driver in my laptop.<br><br />
-- [[User:MSal|MSal]] ([[User_talk:MSal|talk]]) 22:07, 30 October 2012 (UTC)<br />
<br />
: No, the statement is correct and you don't need the video group. see https://bbs.archlinux.org/viewtopic.php?pid=1183090#p1183090 [[User:65kid|65kid]] ([[User talk:65kid|talk]]) 14:05, 31 October 2012 (UTC)<br />
<br />
== GNOME 3.6 issues inhibited commands ==<br />
It seems that GNOME 3.6 now issues the necessary "inhibited" commands, at my system now doesn't suspend twice with the standard configuration anymore. However I'm not familiar enough with the whole concept to be absolutely sure, so I won't update the page itself. Maybe someone with more competence regarding the inhibited commands can confirm this and edit the page?<br><br />
-- [[User:Johnpatcher|Johnpatcher]] ([[User_talk:Johnpatcher|talk]]) 00:34, 31 October 2012 (UTC)<br />
<br />
<br />
== Should we add a note about cups under 'Transitioning from initscripts to systemd'? ==<br />
Are there any more sockets that change?<br />
<br />
Copied from the Cups wiki:<br />
<br />
...<br />
<br />
Systemd uses a different cups socket file located at:<br />
<br />
'''/usr/lib/systemd/system/cups.socket'''<br />
<br />
The default cups socket file is located at:<br />
<br />
'''/var/run/cups/cups.sock'''<br />
<br />
Edit '''/etc/cups/cupsd.conf''' and '''/etc/cups/client.conf''' as root to use the Systemd socket instead of the default. Make sure to restart CUPS when you are done:<br />
<br />
# systemctl restart cups<br />
<br />
...<br />
<br />
[[User:JKAbrams|JKAbrams]] 5 November 2012</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Talk:Systemd&diff=233961Talk:Systemd2012-11-05T22:09:15Z<p>JKAbrams: </p>
<hr />
<div>== Display manager fails to load with fast SSD ==<br />
<br />
I was having a problem with my display manager (LXDM) not loading on my laptop, which has a Sandisk Extreme SSD.<br />
Xorg.log would show errors like "No screens found."<br />
<br />
I eventually figured out that the problem was that my computer was booting so fast that KMS didn't have enough time to kick in before X was started. I solved by adding the KMS driver (i915 in my case) to the initramfs.<br />
<br />
Just a tip for SSD users, not sure if it should be added to the page or not.<br> --[[User:Steev|Steev]] ([[User talk:Steev|talk]]) 16:59, 2 September 2012 (UTC)<br />
:This is a general problem that needs to be solved in the display manager. GDM already implements the bits for the [http://cgit.freedesktop.org/systemd/systemd/commit/?id=f1a8e221ecacea23 CanGraphical] flag.<br />
:-- [[User:Falconindy|Falconindy]] ([[User talk:Falconindy|talk]]) 21:34, 2 September 2012 (UTC)<br />
<br />
== Hibernation with systemd ==<br />
<br />
The hibernation section should be considered a hack since systemd does not directly handle the backend that handles power management. Systemd uses the Upower interface to handle such requests<br>-- [[User:Yungtrizzle|Yungtrizzle]] ([[User talk:Yungtrizzle|talk]]) 06:25, 10 October 2012<br />
<br />
:I talked about hibernation process with Lennart Poettering and he said that systemd-hibernate does only "echo disk > /sys/power/state" . As far as i can see, it works perfectly with tuxonice, since it seems it is now using the same userspace API as kernel hibernation; so it works even without hibernate-script installed (i use it without that package). <br />
:-- [[User:Nierro|Nierro]] ([[User talk:Nierro|talk]]) 13:54, 24 October 2012<br />
<br />
:: what is the #Hibernation section all about anyway? It makes it sound like you need to use uswsusp to hibernate while it should work out of the box just fine. It doesn't explain at all why you would want to use uswsusp instead of the default command. I don't use hibernate nor do I know what uswsusp actually does, so what am I missing here? ::-- [[User:65kid|65kid]] ([[User talk:65kid|talk]]) 15:12, 25 October 2012 (UTC)<br />
<br />
:::I agree with 65kid. In fact, systemctl hibernate works out of the box (it only does an "echo disk...", nothing else). We don't need uswsusp at all. I tried with stock arch kernel and it works.<br />
:::-- [[User:Nierro|Nierro]] ([[User talk:Nierro|talk]]) 11:24, 26 October 2012<br />
<br />
::::Then I suggest that - unless someone explains why you would want to use uswsusp - we remove this whole section because it is nothing but confusing. This article is already way too big to waste text on something that doesn't seem to make any sense.<br />
::::-- [[User:65kid|65kid]] ([[User talk:65kid|talk]]) 10:10, 26 October 2012 (UTC)<br />
<br />
::::: I went ahead and removed the irrelevant information from the page, moving it to [[Uswsusp]]. I also added a note pointing readers there if they want to use another backend for suspending or hibernating.<br />
:::::-- [[User:Ifaigios|Ifaigios]] ([[User talk:Ifaigios|talk]]) 18:16, 26 October 2012 (UTC)<br />
<br />
:::::: Hey [[User:Nierro|Nierro]], do {{ic|systemctl hibernate}} and {{ic|systemctl suspend}} really do different things on your box? In my setup (linux-pf, systemd 195-2), if I do the latter, my box is also in suspend mode, meaning that my power button is glowing on and off and I don't see grub after pressing the power button again but are back to my desktop almost immediately. To me, it rather seems as if {{ic|systemctl hibernate}} goes into hybrid mode?<br />
::::::-- [[User:Jakobh|jakobh]] [[User talk:Jakobh|✉]] 10:07, 29 October 2012 (UTC)<br />
<br />
:::::: Got an answer to the question on the systemd mailing list now: [http://lists.freedesktop.org/archives/systemd-devel/2012-October/007245.html Link] <br />
::::::-- [[User:Jakobh|jakobh]] [[User talk:Jakobh|✉]] 17:56, 30 October 2012 (UTC)<br />
<br />
== <s>Removing rc.local</s> ==<br />
<br />
It isn't clear how to get rid of rc.local. It would be useful to include this statement from the forum discussion in moving from a mixed system to a pure system:<br />
<br />
Go through {{ic|/etc/rc.local}} and {{ic|/etc/rc.local.shutdown}} and turn them into service files (or, if you intend to keep them as they are, copy {{ic|/usr/lib/systemd/system/rc-local{,.shutdown}.service}} to {{ic|/etc/systemd/system/}}).<br>-- [[User:Myshkin|Myshkin]] ([[User talk:Myshkin|talk]]) 00:21, 13 Oct 2012<br />
* I added a new section [[Systemd#.2Fetc.2Frc.local_emulation_for_systemd]] that covers how to emulate {{ic|/etc/rc.local}} in a pure systemd environment. Closing.<br />
:-- [[User:Jstjohn|Jstjohn]] ([[User talk:Jstjohn|talk]]) 21:04, 30 October 2012 (UTC)<br />
<br />
== <s>Replacing ConsoleKit with systemd-logind -> networkmanager</s> ==<br />
<br />
As of {{pkg|networkmanager}} 0.9.6.0-2 in [extra] we do no more have to recompile it with systemd support from [[ABS]], is this right? So the note should be upgraded.<br />
Am i missing anything?<br> -- [[User:Nierro|Nierro]] ([[User talk:Nierro|talk]]) 09:31, 15 October 2012<br />
<br />
: 0.9.6.0-2 in [extra] was compiled on 2012-09-19 and the change to systemd was on 2012-09-29, so as far as I can see, it still needs to be recompiled. https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/networkmanager&id=c34580e6e35b9e87f7dc27f360507143d4fd9106<br />
:-- [[User:65kid|65kid]] ([[User talk:65kid|talk]]) 20:00, 15 October 2012 (UTC)<br />
<br />
::Damn, you're right. I did not see that pkgrel=3 while we are still using -2. Sorry, it means i'm still using my recompiled package, while i thought i was using the [extra] one.<br />
::-- [[User:Nierro|Nierro]] ([[User talk:Nierro|talk]]) 16:35, 15 October 2012<br />
<br />
:::{{pkg|networkmanager}} 0.9.6.4-1 was just pushed to [extra]. NetworkManager does not have to be recompiled anymore. Closing.<br />
:::-- [[User:Jstjohn|Jstjohn]] ([[User talk:Jstjohn|talk]]) 00:13, 31 October 2012 (UTC)<br />
<br />
== video group is still needed! ==<br />
<br />
"Adding your user to groups (optical, audio, scanner, ...) is not necessary for most use cases with systemd. The groups can even cause some functionality to break." ([[Systemd#Supplementary_information]])<br />
<br />
This statement might be too generic. For example, without the video group, mesa will use the llvm driver instead of the Gallium AMD driver in my laptop.<br><br />
-- [[User:MSal|MSal]] ([[User_talk:MSal|talk]]) 22:07, 30 October 2012 (UTC)<br />
<br />
: No, the statement is correct and you don't need the video group. see https://bbs.archlinux.org/viewtopic.php?pid=1183090#p1183090 [[User:65kid|65kid]] ([[User talk:65kid|talk]]) 14:05, 31 October 2012 (UTC)<br />
<br />
== GNOME 3.6 issues inhibited commands ==<br />
It seems that GNOME 3.6 now issues the necessary "inhibited" commands, at my system now doesn't suspend twice with the standard configuration anymore. However I'm not familiar enough with the whole concept to be absolutely sure, so I won't update the page itself. Maybe someone with more competence regarding the inhibited commands can confirm this and edit the page?<br><br />
-- [[User:Johnpatcher|Johnpatcher]] ([[User_talk:Johnpatcher|talk]]) 00:34, 31 October 2012 (UTC)<br />
<br />
<br />
== I think we should add a note about cups under 'Transitioning from initscripts to systemd' ==<br />
Cups stops working after upgrading to systemd because the sockets are changed. Are there any more sockets that change?<br />
<br />
Copied from the Cups wiki:<br />
<br />
...<br />
<br />
Systemd uses a different cups socket file located at:<br />
<br />
'''/usr/lib/systemd/system/cups.socket'''<br />
<br />
The default cups socket file is located at:<br />
<br />
'''/var/run/cups/cups.sock'''<br />
<br />
Edit '''/etc/cups/cupsd.conf''' and '''/etc/cups/client.conf''' as root to use the Systemd socket instead of the default. Make sure to restart CUPS when you are done:<br />
<br />
# systemctl restart cups<br />
<br />
...<br />
<br />
[[User:JKAbrams|JKAbrams]] 5 November 2012</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Talk:Network_configuration/Wireless&diff=233275Talk:Network configuration/Wireless2012-11-02T19:52:23Z<p>JKAbrams: </p>
<hr />
<div>==Encrypting example==<br />
It would be good to place a further example for encrypting.<br />
<br />
# /etc/conf.d/wireless<br />
wlan_wlan0="wlan0 essid MyEssid"<br />
#wlan_wlan0="wlan0 essid MyEssid key 625341627"<br />
#wlan_wlan0="wlan0 essid MyEssid key s:masterpassword"<br />
<br />
If you have eth0 as wireless card, you replace wlan0 with eth0<br />
<br />
wlan_et0="eth0 essid MyEssid key s:masterpassword""<br />
<br />
==Mention modprobe -l==<br />
Does anybody else besides me think that it would be helpful to mention modprobe -l to get a list of loaded modules/drivers and that ath9k is already included in the kernel at the beginning of ''First steps'' or ''Drivers and Firmware'' section? In my case (I have a Thinkpad x61) I didn't have to install any additional drivers, so I could proceed immediately to Manual setup and everything worked perfectly. --[[User:Bhobbit|Bhobbit]] 01:03, 7 June 2009 (EDT)<br />
<br />
== Overall article readability (notes and split) ==<br />
There is no doubt this article is very rich, but I find it a bit messy overall.<br />
At first sight, the newcomer may think managing wireless is a real odyssey, whereas it may be 2 simple steps for most users.<br />
* More than 50% of the article is dedicated to specific drivers installation. Perhaps it would be worth moving the whole section to a dedicated page, leaving only generic install guidelines here.<br />
* I've found 21 ''Note'' templates. Too much imho, it makes different sections and code lines harder to distinguish, and thus diminishes article's overall readbility. Some of them definitely do not deserve a template, they should be written as is.<br />
<br />
Still I won't say there is no doubt these 2 changes would make the article really better. So feel free to discuss!<br />
<br />
[[User:Ambrevar|Ambrevar]] ([[User talk:Ambrevar|talk]]) 10:27, 6 July 2012 (UTC)<br />
<br />
== auto connect if dropped or changed location WICD ==<br />
<br />
I tested this with wicd and this didn't work (with my raspberry pi and an ASUS USB-N10 adaptor). Once the connection was dropped the device didn't even search for other networks (the light at the adaptor didn't blink).<br />
<br />
I now tried again with netcfg and that works like a charm, so it has nothing to do with my hardware. Are there others who are experiencing the same problem? - [[User:Warddr|Warddr]] ([[User talk:Warddr|talk]]) 15:17, 22 August 2012 (UTC)<br />
<br />
== systemd, rc.conf ==<br />
The section about Management methods needs to be updated with info how to do this on a pure systemd system. - [[User:JKAbrams|JKAbrams]] 20:51, 02 November 2012</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Talk:Network_configuration/Wireless&diff=233257Talk:Network configuration/Wireless2012-11-02T19:05:59Z<p>JKAbrams: </p>
<hr />
<div>==Encrypting example==<br />
It would be good to place a further example for encrypting.<br />
<br />
# /etc/conf.d/wireless<br />
wlan_wlan0="wlan0 essid MyEssid"<br />
#wlan_wlan0="wlan0 essid MyEssid key 625341627"<br />
#wlan_wlan0="wlan0 essid MyEssid key s:masterpassword"<br />
<br />
If you have eth0 as wireless card, you replace wlan0 with eth0<br />
<br />
wlan_et0="eth0 essid MyEssid key s:masterpassword""<br />
<br />
==Mention modprobe -l==<br />
Does anybody else besides me think that it would be helpful to mention modprobe -l to get a list of loaded modules/drivers and that ath9k is already included in the kernel at the beginning of ''First steps'' or ''Drivers and Firmware'' section? In my case (I have a Thinkpad x61) I didn't have to install any additional drivers, so I could proceed immediately to Manual setup and everything worked perfectly. --[[User:Bhobbit|Bhobbit]] 01:03, 7 June 2009 (EDT)<br />
<br />
== Overall article readability (notes and split) ==<br />
There is no doubt this article is very rich, but I find it a bit messy overall.<br />
At first sight, the newcomer may think managing wireless is a real odyssey, whereas it may be 2 simple steps for most users.<br />
* More than 50% of the article is dedicated to specific drivers installation. Perhaps it would be worth moving the whole section to a dedicated page, leaving only generic install guidelines here.<br />
* I've found 21 ''Note'' templates. Too much imho, it makes different sections and code lines harder to distinguish, and thus diminishes article's overall readbility. Some of them definitely do not deserve a template, they should be written as is.<br />
<br />
Still I won't say there is no doubt these 2 changes would make the article really better. So feel free to discuss!<br />
<br />
[[User:Ambrevar|Ambrevar]] ([[User talk:Ambrevar|talk]]) 10:27, 6 July 2012 (UTC)<br />
<br />
== auto connect if dropped or changed location WICD ==<br />
<br />
I tested this with wicd and this didn't work (with my raspberry pi and an ASUS USB-N10 adaptor). Once the connection was dropped the device didn't even search for other networks (the light at the adaptor didn't blink).<br />
<br />
I now tried again with netcfg and that works like a charm, so it has nothing to do with my hardware. Are there others who are experiencing the same problem? - [[User:Warddr|Warddr]] ([[User talk:Warddr|talk]]) 15:17, 22 August 2012 (UTC)<br />
<br />
== systemd, rc.conf ==<br />
The section about Management methods needs to be updated with info how to do this on a pure systemd system.</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Media_Transfer_Protocol&diff=233230Media Transfer Protocol2012-11-02T17:31:53Z<p>JKAbrams: </p>
<hr />
<div>[[Category:Sound]]<br />
MTP is the "Media Transfer Protocol" and is used by many MP3 players such as the Creative Zen and some Walkmans. In addition, Android phones and tablets use it since version 3.0. It is part of the "Windows Media" Framework and has close relationship with Windows Media Player.<br />
<br />
==Installation==<br />
MTP support is provided by the [http://libmtp.sourceforge.net/ libmtp] package, to install:<br />
pacman -S libmtp<br />
==Usage==<br />
After installation, you have several mtp tools available.<br />
Upon connecting your MTP device, you use:<br />
mtp-detect<br />
to see if your MTP device is detected.<br />
<br />
To connect to your MTP device, you use:<br />
mtp-connect<br />
<br />
If connection is successful, you will be given several switch options in conjunction with mtp-connect to access data on the device.<br />
<br />
There are also several stand alone commands you can use to access your MTP device such as,<br />
{{Note | Some commands may be harmful to your MTP device!!! }}<br />
<br />
mtp-albumart mtp-emptyfolders mtp-getplaylist mtp-reset mtp-trexist<br />
mtp-albums mtp-files mtp-hotplug mtp-sendfile<br />
mtp-connect mtp-folders mtp-newfolder mtp-sendtr<br />
mtp-delfile mtp-format mtp-newplaylist mtp-thumb<br />
mtp-detect mtp-getfile mtp-playlists mtp-tracks<br />
<br />
==Using media players==<br />
You can also use your mtp device in music players such as Amarok. To do this you may have to edit "/etc/udev/rules.d/51-android.rules" (The MTP device used in the following example is a Galaxy Nexus):<br />
To do this run:<br />
$ lsusb<br />
and look for your device, it will be something like:<br />
Bus 003 Device 011: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II], GT-P7500 [Galaxy Tab 10.1]<br />
in which case the entry would be:<br />
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0666"<br />
Then, reload udev rules:<br />
# udevadm control --reload<br />
<br />
{{Note | After installing MTP you may have to reboot for your device to be recognised''}}<br />
<br />
==mtpfs==<br />
Mtpfs is FUSE filesystem that supports reading and writing from any MTP device. Basically it allows you to mount your device as an external drive.<br> It's available in the community repository; you can install it by running {{ic|pacman -S mtpfs}}.<br />
*First edit your {{ic|/etc/fuse.conf}} and uncomment the following line:<br />
user_allow_other<br />
*To mount your device <br />
# mtpfs -o allow_other /media/YOURMOUNTPOINT<br />
*To unmount your device<br />
$ umount /media/YOURMOUNTPOINT<br />
Also, you can put them into your ~/.bashrc:<br />
alias android-connect="mtpfs -o allow_other /media/YOURMOUNTPOINT"<br />
alias android-disconnect="sudo umount /media/YOURMOUNTPOINT"<br />
{{Note|if you want not be asked for password when using sudo, please refer to [[USB Storage Devices#Mounting USB devices]]}}<br />
<br />
==go-mtpfs==<br />
{{Note|Go-mtpfs gives a better performance while writing files to some devices than mtpfs/jmtpfs. Try it if you have slow speeds.}}<br />
If the above instructions don't show any positiv results one should try {{aur|go-mtpfs-git}} from the [[AUR]].<br />
The following has been tested on a Samsung Galaxy Nexus GSM.<br />
<br />
As in the section above install {{aur|android-udev}} which will provide you with "/etc/udev/rules.d/51-android.rules" edit it to apply to <br />
your vendorID and productID, which you can see after running mtp-detect. To the end of the line add with a comma OWNER="yourusername". Save the file.<br />
<br />
*Add yourself to the "fuse" group:<br />
gpasswd -a [user] fuse<br />
<br />
*If the group "fuse" doesn't exist create it with:<br />
groupadd fuse<br />
<br />
Logout or reboot to apply these changes. <br />
<br />
*To create a mount point called "Android" issue the following commands:<br />
mkdir Android<br />
<br />
*To mount your phone use:<br />
go-mtpfs Android<br />
<br />
*To unmount your phone:<br />
fusermount -u Android<br />
<br />
You can create a .bashrc alias as in the example above for easier use.<br />
<br />
==gvfs-mtp==<br />
<br />
Philip Langdale is working on native MTP support for gvfs. Currently gvfs uses gphoto2 for mounting MTP volumes. The weaknesses of gphoto2 and mtpfs are listed in his [http://intr.overt.org/blog/?p=153 blog post]. <br />
*You can test his native mtp implementation for gvfs before it gets upstream with the AUR package [https://aur.archlinux.org/packages.php?ID=62664 gvfs-mtp-git].<br />
<br />
*Devices will have gvfs paths like this<br />
gvfs-ls mtp://[usb:002,013]/<br />
<br />
==KDE MTP KIO Slave==<br />
There is a MTP KIO Slave built upon libmtp under development by Philipp Schmidt, availiable as AUR package [https://aur.archlinux.org/packages.php?ID=63140 kio-mtp-git].<br />
Using KIO makes file access in KDE seamless, in principle any KDE application would be able read/write files on the device.<br />
<br />
===Usage===<br />
The device will be available under the path mtp:/<br />
<br />
===Workaround if the KDE device actions doesn't work===<br />
If you are not able to use the action "Open with File Manager", you may work around this problem by editing the file /usr/share/apps/solid/actions/solid_mtp.desktop<br />
<br />
Change the line<br />
Exec=kioclient exec mtp:udi=%i/<br />
To<br />
Exec=dolphin "mtp:/"</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Talk:Locale&diff=232898Talk:Locale2012-11-01T03:08:51Z<p>JKAbrams: </p>
<hr />
<div>== <s> "invalid charset name" </s> ==<br />
<br />
hello ppl, I was having this error message while trying to access man pages and running less, it turns out that the LESSCHARSET environment variable does not recongnize utf if it is written like 'utf8' it will only work if you write it like 'UTF-8' hope it helps!<br />
: Fixed. Close. -- [[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 05:12, 14 October 2012 (UTC)<br />
<br />
== .bashrc ==<br />
<br />
.bashrc is only used by interactive bash sessions, right? So that if you login with KDM in KDE (or GDM gnome), the whole KDE session will inherit the locale set by init->KDM and will not use the one set in .bashrc! <br />
<br />
I guess a "source ~/.bashrc" in ~/.xprofile would solve this.<br />
<br />
--[[User:Luetti|Luetti]] 17:56, 8 July 2008 (EDT): I don't think so. I tried almost the whole day to set only LC_PAPER="de_DE.utf8". Trying this in almost every file possible (/etc/profile, .xprofile, .bashrc, /etc/rc.local) seemed to work, as I used "locale" in terminal to verify it. But this only worked for applications I started from terminal, but not for applications started from the gnome-menu. So I came to the conclusion it has something to do with gdm. After having a closer look to /etc/gdm/xsession the problem was clear. GDM probably always sets $GDM_LANG on login. When $GDM_LANG is set, xsession will unset all other LC-variables. Just commented out this part and now everything works as desired. <br />
If this is a common and/or important problem, I will add this to the article. What do you think?<br />
<br />
== <s> setting LC_ALL a bad idea? </s>==<br />
<br />
At the end, this wiki suggests setting LC_ALL in /etc/environment<br />
<br />
https://wiki.archlinux.org/index.php/Locale#gnome-terminal_doesn.27t_support_UTF-8_characters_for_me<br />
<br />
but the Gentoo localization page says about LC_ALL that you should "never set it in a startup file". <br />
<br />
http://www.gentoo.org/doc/en/guide-localization.xml<br />
<br />
Who is correct?<br />
<br />
Is it sufficient just to set LANG in /etc/environment, and not set LC_ALL?<br />
<br />
<br />
-Yeap, lang is sufficient, it worked even on gentoo. I removed it --[[User:Maevius|Maevius]] 08:30, 19 January 2012 (EST)<br />
<br />
== LC_MESSAGES ==<br />
<br />
Setting LC_MESSAGES to "C" or "POSIX" (as opposed to "en_US.UTF-8" for example), can save tens of syscalls in a simple program without any loss (since all you need is plain English anyway). It's 29 less syscalls (on my system) for a simple "ls /no/such/dir". Add this info inside? --[[User:Philomath|Philomath]] ([[User talk:Philomath|talk]]) 07:55, 2 July 2012 (UTC)<br />
<br />
<br />
== locale.sh ==<br />
If setting locale.conf doesn't work (symptom: everything is set to POSIX no matter whats in locale.conf), reinstall filesystem.<br />
(locale.sh somehow gets lost, see comment here https://plus.google.com/114015603831160344127/posts/2zKCcnTWDpa happens after the switch to systemd)<br />
<br />
JKAbrams 01 December 2012</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Talk:Daemons_list&diff=232876Talk:Daemons list2012-11-01T00:27:55Z<p>JKAbrams: Created page with "'''Should dbus be labeled as automatically handled?''' systemctl enable dbus.service The unit files have no [Install] section. They are not meant to be enabled using systemc..."</p>
<hr />
<div>'''Should dbus be labeled as automatically handled?'''<br />
<br />
systemctl enable dbus.service<br />
<br />
The unit files have no [Install] section. They are not meant to be enabled using systemctl.<br />
<br />
''JKAbrams 2012-11-01''</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Debugging/Getting_traces&diff=187898Debugging/Getting traces2012-03-05T21:22:18Z<p>JKAbrams: /* Getting the trace */</p>
<hr />
<div>[[Category:Package development (English)]]<br />
{{i18n|Debug - Getting Traces}}<br />
<br />
This article will try to give you an idea how to create Arch package. This provides debug and traces information for reporting software bugs (for example after use of [http://www.archlinux.org/packages/search/?q=bug-buddy Bug-Buddy]).<br />
<br />
==Discovering name of package(s)==<br />
===A few facts of debug messages===<br />
When looking at debug message, such as (''stripped''):<br />
<br />
...<br />
Backtrace was generated from '/usr/bin/epiphany'<br />
<br />
'''(no debugging symbols found)'''<br />
Using host libthread_db library "/lib/libthread_db.so.1".<br />
'''(no debugging symbols found)'''<br />
[Thread debugging using libthread_db enabled]<br />
[New Thread -1241265952 (LWP 12630)]<br />
(no debugging symbols found)<br />
0xb7f25410 in __kernel_vsyscall ()<br />
#0 0xb7f25410 in __kernel_vsyscall ()<br />
#1 0xb741b45b in '''??''' () from /lib/libpthread.so.0<br />
...<br />
<br />
you can see '''??''' at the place where debugging info is missing and also the name of library or executable which called the function. Similarly, when the line '''(no debugging symbols found)''' appears in a message, it means that you have to look for a file whose name is stated. <br />
<br />
===Finding package===<br />
Use [[Pacman]] to retrieve name of package:<br />
<br />
# pacman -Qo /lib/libthread_db.so.1<br />
/lib/libthread_db.so.1 is owned by ''glibc'' 2.5-8<br />
<br />
We have found that package is called ''glibc'' in version 2.5-8. By repeating this step, we are able to create a list of packages which we have to compile ourselves to get full stack trace. <br />
<br />
==Obtaining PKGBUILD==<br />
In order to build a package from source, the PKGBUILD file is required. The location from which you can obtain PKGBUILDs is, in general:<br />
#[[AUR]] or<br />
#[[ABS]]<br />
<br />
===Using AUR===<br />
Use [http://aur.archlinux.org/packages.php AUR search page] to find the package. If it is not present, the package is stored in one of the official repository trees of Arch Linux. If found, click on its name and download the '''Tarball'''. Store it in location of your choice. Use <code>tar</code> to extract it and change directory:<br />
<br />
$ tar xvzf name_of_tarball.tar.gz<br />
$ cd name_of_tarball<br />
<br />
===Using ABS===<br />
If the package is a part of official tree, install [[ABS]], fetch the source for the package and then build it:<br />
<br />
$ ABSROOT=. abs core/glibc<br />
$ cd core/glibc<br />
$ makepkg -s<br />
<br />
==Compilation settings==<br />
At this stage, you can modify the global configuration file of <code>makepkg</code> if you will be using it only for debug purposes. In other cases, you should modify package's PKGBUILD file only for each package you would like to rebuild.<br />
===Global settings===<br />
Modify <code>makepkg</code>'s configuration file <code>/etc/makepkg.conf</code> to contain following lines:<br />
<br />
CFLAGS="'''-g''' -march=i686 '''-O1''' -pipe"<br />
CXXFLAGS="'''-g''' -march=i686 '''-O1''' -pipe"<br />
<br />
and<br />
<br />
OPTIONS=('''!strip''' !docs libtool emptydirs)<br />
<br />
These settings (in bold) will force compilation with debugging information and will disable stripping of executable.<br />
<br />
===One package settings only===<br />
Modify <code>foo</code>'s PKGBUILD file to contain the following lines:<br />
<br />
options=(!strip)<br />
<br />
Into the <code>build()</code> function, add following lines at the very beginning:<br />
<br />
export CFLAGS="$CFLAGS -g -O1"<br />
export CXXFLAGS="$CXXFLAGS -g -O1"<br />
<br />
{{Note|A change in optimization level below {{Ic|-O1}} cannot be generally recommended as ''gcc'' then uses implementations of functions in the GNU C library that can be considered too different from the optimized ones. Also, changes in headers' includes and disabled functions may prevent successful compilation.}}<br />
<br />
==Building and installing the package==<br />
Build the package from source using <code>makepkg</code> while in the PKGBUILD's directory. This could take some time:<br />
<br />
# makepkg<br />
<br />
Then install the built package:<br />
<br />
# pacman -U glibc-2.5-8-i686.pkg.tar.gz<br />
<br />
==Getting the trace==<br />
<br />
The actual backtrace resp. stack trace can now be obtained via e. g. {{Ic|gdb}}, the GNU Debugger. Run it either via<br />
<br />
# gdb /path/to/file<br />
<br />
or<br />
<br />
# gdb<br />
(gdb) exec /path/to/file<br />
<br />
The path is optional if it is already in the {{Ic|$PATH}} variable.<br />
<br />
Then, within {{Ic|gdb}}, type {{Ic|run}} followed by any arguments you wish the program to start with, e. g.<br />
<br />
(gdb) run --no-daemon --verbose<br />
<br />
to start execution of the file. Do whatever necessary to evoke the bug. For the actual log, type the lines<br />
<br />
(gdb) set logging file trace.log<br />
(gdb) set logging on<br />
<br />
and then<br />
<br />
(gdb) bt<br />
<br />
to output the trace to {{Ic|trace.log}} into the directory {{Ic|gdb}} was started in. To exit, enter:<br />
<br />
(gdb) set logging off<br />
(gdb) quit<br />
<br />
{{Tip| To debug an application written in python<br />
# gdb /usr/bin/python<br />
(gdb) run <python application><br />
}}<br />
<br />
==Conclusion==<br />
Use the completed stack trace to inform developers of the bug you have discovered before. This will be highly appreciated by them and will help to improve your favorite program.<br />
<br />
== See also ==<br />
*[[Reporting Bug Guidelines]]<br />
*[[Step By Step Debugging Guide]]<br />
*[http://www.gentoo.org/proj/en/qa/backtraces.xml Gentoo Linux Documentation — How to get meaningful backtraces in Gentoo]</div>JKAbramshttps://wiki.archlinux.org/index.php?title=IPhone_tethering&diff=184928IPhone tethering2012-02-16T06:51:12Z<p>JKAbrams: /* Install ipheth */</p>
<hr />
<div>{{Lowercase_title}}<br />
[[Category:Other hardware (English)]]<br />
{{i18n|IPhone Tethering}}<br />
{{out of date}}<br />
With the release of iPhone OS 3.0 it is possible to use the device as a 3G data modem over either USB or Bluetooth on Windows and OS X systems, without the need for jailbreaking. There is no official support for tethering on Linux systems and by the time of writing no working USB driver has been developed. However, tethering over Bluetooth is still an option.<br />
<br />
== Tethering over Bluetooth ==<br />
Tethering over Bluetooth will drain the batteries relatively quickly, but simultaneous charging from an USB port works well.<br />
<br />
=== Hardware Requirements ===<br />
* iPhone running OS 3.0 with tethering enabled. See Settings > General > Network and turn on the tethering option.<br />
* Bluetooth Adapter or similar, preferably with EDR(Enhanced Data Rate) for acceptable speeds. Tested with a Belkin F8T016NE.<br />
<br />
=== Setup ===<br />
From the article entitled [[Bluetooth]]:<br />
<br />
To use Bluetooth, the [http://www.bluez.org bluez] package for the Linux Bluetooth protocol stack must be installed:<br />
# pacman -S bluez<br />
<br />
Once bluez is installed, both the dbus daemon and the bluetooth daemon must be running:<br />
# /etc/rc.d/dbus start<br />
<br />
# /etc/rc.d/bluetooth start<br />
<br />
The dbus daemon is used to read settings and for pin pairing, while the bluetooth daemon is required for the Bluetooth protocol. It is important that dbus is started '''before''' bluetooth. If dbus was not running when bluetooth was started, then try (after dbus is running):<br />
<br />
# /etc/rc.d/bluetooth restart<br />
<br />
To start bluetooth automatically on boot, add bluetooth to your daemons array in rc.conf:<br />
DAEMONS=(... bluetooth)<br />
<br />
No further configuration seems to be necessary on Arch systems. If problems arise, see the first sources link for possible config file edits.<br />
<br />
==== Gnome/Xfce4 ====<br />
Install the [[Blueman]] GTK+ Bluetooth manager<br />
<br />
# pacman -S blueman<br />
<br />
A Bluetooth icon should appear in your notification area. Note: the icon may not appear if bluetooth was not turned on at startup. Click it, and search for nearby devices, adding your iPhone (note, you may need to have the Bluetooth setting screen up on your iPhone for discovery to work).<br />
<br />
Once the iPhone has been added to the devices list, open the Device menu and select pair. This will require the usual entering of a PIN on the computer then the iPhone. Now open the Device menu again, and choose Network Access > Network Access Point. If everything goes well, blueman reports a success and the status bar on your iPhone should glow blue, indicating a successful tether.<br />
<br />
Blueman will have created a new network interface, typically bnep0. To connect to it, run the following as root.<br />
<br />
# dhcpcd bnep0<br />
<br />
Optionally, if you have [[NetworkManager]] installed and want it to automatically connect to the bnep0 interface, '''blacklist''' the interface in your rc.conf just as with the other interfaces you want to be automatically handled:<br />
INTERFACES=(!eth0 !wlan0 '''!bnep0''' ...)<br />
<br />
NetworkManager might still automatically connect to the new interface initially, but on subsequent boots the above action is necessary.<br />
<br />
==== KDE ====<br />
To be added...<br />
<br />
==== netcfg ====<br />
<br />
Alternatively, you can create a [[netcfg]] network profile to allow easy tethering from the command line, without requiring [[Blueman]] or Gnome. Assuming an already paired iPhone with address '00:00:DE:AD:BE:EF', simply create a profile in /etc/network.d called - for example - 'tether':<br />
<br />
CONNECTION="ethernet"<br />
DESCRIPTION="Ethernet via pand tethering to iPhone"<br />
INTERFACE="bnep0"<br />
IPHONE="00:00:DE:AD:BE:EF"<br />
PRE_UP="pand -E -S -c ${IPHONE} -e ${INTERFACE} -n 2>/dev/null"<br />
POST_DOWN="pand -k ${IPHONE}"<br />
IP="dhcp"<br />
<br />
Then, either as root or using sudo, execute:<br />
<br />
netcfg tether<br />
<br />
To bring the interface down and un-tether:<br />
<br />
netcfg down tether<br />
<br />
== Tethering over USB ==<br />
You need '''aur/itunnel''' and '''aur/ifuse''' to do so.<br />
<br />
Then follow up http://dev.squarecows.com/2009/05/06/iphone-linux-tethering-via-usb-cable/<br />
<br />
=== USB tethering from within Windows guest in Virtualbox ===<br />
One potential way to accomplish this is to use a Windows guest in [[VirtualBox]], and present the host Arch system with a network interface (Host Only?). The working iPhone network device in Windows might then be bridged to the host only interface device within Windows. The iPhone USB network driver is installed together with iTunes. However, this has yet to be tested successfully. More info to come.<br />
<br />
== Tethering via USB with libimobiledevice: Native Support==<br />
{{Note|This section needs to be reviewed for style}}<br />
<br />
With the release of libimobiledevice it's now possible to natively tether the iPhone 3G and 3GS with firmware 3.0 or superior (Not tested with 4.0, now in developer release).<br />
<br />
=== Requirements ===<br />
*'''In the iPhone:''' Enable tethering<br />
*'''In your computer:''' Install usbmuxd<br />
*'''In your computer:''' Install libimobiledevice (previously libiphone)<br />
*'''In your computer:''' Install The iPhone Ethernet Driver (ipheth)<br />
<br />
Though there are packages for all of these, the usbmuxd is the only requirement recommended to install from arch. Both libimobiledevice and ipheth are recommended to install from the [[git]].<br />
<br />
==== Enable tethering in the iPhone ====<br />
If your carrier hasn't already enabled tethering you can do it by:<br />
*Using blackra1n tu unlock your iPhone http://blackra1n.com/<br />
*Installing a carrier update (a new .ipcc) more instructions in http://gizmodo.com/5175391/how-to-enable-3g-tethering-in-your-iphone-30-now<br />
All of these methods are really easy to find in google. Notice that the 3rd method will just work in fw inferior to 3.1.2, following that you'll first need to use Blackra1n<br />
<br />
==== Installing usbmuxd ====<br />
You can install [http://aur.archlinux.org/packages.php?ID=26970 usbmuxd] from the [[AUR]]<br />
<br />
==== Installing libimobiledevice ====<br />
You can get libimobile device from MCoyler site at github http://github.com/mcolyer<br />
<br />
To get the source and install run the following commands. This should be pretty much straight forward<br />
<br />
# git clone git://github.com/mcolyer/libiphone.git<br />
# cd libiphone<br />
# ./autogen.sh<br />
# make<br />
<br />
As always check there are no errors so far; if everything looks good you are ready to install<br />
<br />
# sudo make install<br />
<br />
==== Install ipheth ==== <br />
<br />
The following section is based in the tutorial available here http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver<br />
<br />
Again we will be getting a git repository, but this install is divided in two sections. Install the kernel module, and installing the pairing program.<br />
<br />
Remember that this depends on libimobiledevice and usbmuxd, so install those first.<br />
<br />
'''Since 2.6.34 kernel (available in testing repo) ipheth module is already in kernel, so everything you need is [http://aur.archlinux.org/packages.php?ID=37584 ipheth-utils] pkg from AUR.'''<br />
<br />
If you are using 2.6.33 kernel or earlier the right way is described below:<br />
<br />
# git clone git://github.com/dgiagio/ipheth.git<br />
<br />
Now we are good to install the Kernel Module.<br />
<br />
# cd ipheth/ipheth-driver<br />
# make<br />
<br />
If there are no errors you can load the module<br />
# sudo insmod ipheth.ko<br />
<br />
Now plug your iPhone and run dmesg. It should give you something like the following:<br />
# ...<br />
# [ 8181.461000] ipheth 1-6:4.2: Apple iPhone USB Ethernet device attached<br />
# [ 8181.463067] usbcore: registered new interface driver ipheth<br />
# ...<br />
<br />
If you have a hard time finding these lines run<br />
<br />
# dmesg | grep ipheth<br />
<br />
Now you should have a new network device, mine is called eth1 but it can be different. If you are ussing the NetworkManager Applet you should see a wired network device called Apple iPhone.<br />
<br />
Just one step to go. Installing the pairing program. You will have to run this program every time you plug your iPhone, I really do not know why but otherwise it won't work.<br />
<br />
# cd ipheth/ipheth-pair<br />
# make<br />
# sudo make install<br />
<br />
{{Note|If you get an error that it can't find /sbin/udevadm run this command to reload the udev rules: sudo /usr/bin/udevadm control --reload-rules}}<br />
<br />
This will install '''ipheth-pair''' (the pairing program) in /lib/udev/ipheth-pair Not the most practical location since it's not in your PATH. With you iPhone plugged rud<br />
<br />
# /lib/udev/ipheth-pair<br />
<br />
If you do not get any errors you should now be able to connect to tether your iPhone with NetworkManager<br />
<br />
You can also use [http://aur.archlinux.org/packages.php?ID=34953 ipheth-git] from AUR.<br />
<br />
=== Troubleshooting ===<br />
<br />
==== iPhone not appearing in the devices list ====<br />
If you can't see the device in dmesg or in the NetworkManager device list you probably didn't reload the module. Just run:<br />
<br />
# sudo insmod ipheth.ko<br />
<br />
You can also add the module to rc.conf just <br />
<br />
# cd ipheth/ipheth-driver<br />
# make clean<br />
# make<br />
# sudo make install<br />
<br />
and then edit the [b]rc.conf[/b] since it's still in a beta stage I do not recommend this, but if it works for you there shouldn't be trouble.<br />
<br />
==== The iPhone appears in the device list but it doesn't connect ====<br />
Did you pair the iPhone? run<br />
<br />
# /lib/udev/ipheth-pair<br />
<br />
Now you should be able to connect<br />
<br />
==== You run ipheth-pair but it returns there's no libimobiledevice ====<br />
<br />
If you get this error<br />
<br />
# ./ipheth-pair: error while loading shared libraries: libimobiledevice.so.1: cannot open shared object file: No such file or directory<br />
<br />
You can solve it by running<br />
<br />
# sudo ln -s /usr/local/lib/libimobiledevice.so.1.0.0 /usr/lib/libimobiledevice.so.1<br />
<br />
== Sources ==<br />
# [http://jkeating.livejournal.com/75270.html jkeating: Tethering iPhone 3.0 with Linux (Fedora 11) over bluetooth]<br />
# http://www.libimobiledevice.org/<br />
# http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver<br />
# http://github.com/mcolyer/libiphone<br />
<br />
== Troubleshooting ==<br />
* If you get "interface bnep0 does not exist" when trying tethering, you must enable "tethering" in the iPhone :<br><br />
See http://informationmadness.com/cms/blog/25-blog/1531-iphone-3g-s-tethering-without-installing-anything.html if you are stuck.<br><br />
sputnick, Thu apr 1 2010.<br />
<br />
* If your iPhone stopped showing in NetworkManager after installing 2.6.34 kernel remove ipheth from kernel<br />
<br />
# sudo rmmod ipheth<br />
<br />
and than install ipheth-git from AUR.<br />
This will compile old kernel module, which is detected fine.</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Omnikey_Cardman_5321&diff=180176Omnikey Cardman 53212012-01-25T11:23:07Z<p>JKAbrams: /* pscslite */</p>
<hr />
<div>[[Category:Other hardware (English)]]<br />
{{i18n|Omnikey Cardman 5321}}<br />
This page will explain how to get the Omnikey Cardman 5321 SmartCard Reader up and running under Archlinux. This guide may work for other models to, but this has not been tested.<br />
<br />
= Installation =<br />
<br />
== Packages ==<br />
<br />
=== pscslite ===<br />
You need to install pcsclite, a middleware to access a smart card using the SCard API. {{Package Official|pcsclite}} availible in [community].<br />
<br />
=== pcsc-tools ===<br />
In addition you can install pcsc-tools which provide you some tools that you can use with smart cards and PC/SC: [http://www.archlinux.org/packages/community/i686/pcsc-tools/ pcsc-tools].<br />
<br />
=== Driver ===<br />
At least you have to install the driver, that is now also available through the AUR: [http://aur.archlinux.org/packages.php?ID=34887 omnikey_cardman_5x2x].<br />
<br />
= Usage =<br />
<br />
== Start pcscd ==<br />
To start pcscd you have to run the following command:<br />
<pre><br />
/etc/rc.d/pcscd start<br />
</pre><br />
<br />
== Test with pcsc_scan ==<br />
You can test the installation by running pcsc_scan. If everything worked fine, you should get something like that:<br />
<pre><br />
PC/SC device scanner<br />
V 1.4.16 (c) 2001-2009, Ludovic Rousseau <ludovic.rousseau@free.fr><br />
Compiled with PC/SC lite version: 1.5.5<br />
Scanning present readers...<br />
0: OMNIKEY CardMan 5x21 00 00<br />
1: OMNIKEY CardMan 5x21 00 01<br />
<br />
Sun Feb 21 18:21:05 2010<br />
Reader 0: OMNIKEY CardMan 5x21 00 00<br />
Card state: Card removed, <br />
<br />
Sun Feb 21 18:21:05 2010<br />
Reader 1: OMNIKEY CardMan 5x21 00 01<br />
Card state: Card removed, <br />
<br />
Sun Feb 21 18:21:11 2010<br />
Reader 1: OMNIKEY CardMan 5x21 00 01<br />
Card state: Card inserted, <br />
ATR: 3B 89 80 01 4A 43 4F 50 34 31 56 32 32 4D<br />
<br />
ATR: 3B 89 80 01 4A 43 4F 50 34 31 56 32 32 4D<br />
+ TS = 3B --> Direct Convention<br />
+ T0 = 89, Y(1): 1000, K: 9 (historical bytes)<br />
TD(1) = 80 --> Y(i+1) = 1000, Protocol T = 0 <br />
-----<br />
TD(2) = 01 --> Y(i+1) = 0000, Protocol T = 1 <br />
-----<br />
+ Historical bytes: 4A 43 4F 50 34 31 56 32 32<br />
Category indicator byte: 4A (proprietary format)<br />
+ TCK = 4D (correct checksum)<br />
<br />
Possibly identified card (using /usr/share/pcsc/smartcard_list.txt):<br />
3B 89 80 01 4A 43 4F 50 34 31 56 32 32 4D<br />
New Zealand e-Passport<br />
</pre></div>JKAbramshttps://wiki.archlinux.org/index.php?title=Omnikey_Cardman_5321&diff=180175Omnikey Cardman 53212012-01-25T11:22:32Z<p>JKAbrams: /* Packages */</p>
<hr />
<div>[[Category:Other hardware (English)]]<br />
{{i18n|Omnikey Cardman 5321}}<br />
This page will explain how to get the Omnikey Cardman 5321 SmartCard Reader up and running under Archlinux. This guide may work for other models to, but this has not been tested.<br />
<br />
= Installation =<br />
<br />
== Packages ==<br />
<br />
=== pscslite ===<br />
You need to install pcsclite, a middleware to access a smart card using the SCard API {{Package Official|pcsclite}} availible in [community].<br />
<br />
=== pcsc-tools ===<br />
In addition you can install pcsc-tools which provide you some tools that you can use with smart cards and PC/SC: [http://www.archlinux.org/packages/community/i686/pcsc-tools/ pcsc-tools].<br />
<br />
=== Driver ===<br />
At least you have to install the driver, that is now also available through the AUR: [http://aur.archlinux.org/packages.php?ID=34887 omnikey_cardman_5x2x].<br />
<br />
= Usage =<br />
<br />
== Start pcscd ==<br />
To start pcscd you have to run the following command:<br />
<pre><br />
/etc/rc.d/pcscd start<br />
</pre><br />
<br />
== Test with pcsc_scan ==<br />
You can test the installation by running pcsc_scan. If everything worked fine, you should get something like that:<br />
<pre><br />
PC/SC device scanner<br />
V 1.4.16 (c) 2001-2009, Ludovic Rousseau <ludovic.rousseau@free.fr><br />
Compiled with PC/SC lite version: 1.5.5<br />
Scanning present readers...<br />
0: OMNIKEY CardMan 5x21 00 00<br />
1: OMNIKEY CardMan 5x21 00 01<br />
<br />
Sun Feb 21 18:21:05 2010<br />
Reader 0: OMNIKEY CardMan 5x21 00 00<br />
Card state: Card removed, <br />
<br />
Sun Feb 21 18:21:05 2010<br />
Reader 1: OMNIKEY CardMan 5x21 00 01<br />
Card state: Card removed, <br />
<br />
Sun Feb 21 18:21:11 2010<br />
Reader 1: OMNIKEY CardMan 5x21 00 01<br />
Card state: Card inserted, <br />
ATR: 3B 89 80 01 4A 43 4F 50 34 31 56 32 32 4D<br />
<br />
ATR: 3B 89 80 01 4A 43 4F 50 34 31 56 32 32 4D<br />
+ TS = 3B --> Direct Convention<br />
+ T0 = 89, Y(1): 1000, K: 9 (historical bytes)<br />
TD(1) = 80 --> Y(i+1) = 1000, Protocol T = 0 <br />
-----<br />
TD(2) = 01 --> Y(i+1) = 0000, Protocol T = 1 <br />
-----<br />
+ Historical bytes: 4A 43 4F 50 34 31 56 32 32<br />
Category indicator byte: 4A (proprietary format)<br />
+ TCK = 4D (correct checksum)<br />
<br />
Possibly identified card (using /usr/share/pcsc/smartcard_list.txt):<br />
3B 89 80 01 4A 43 4F 50 34 31 56 32 32 4D<br />
New Zealand e-Passport<br />
</pre></div>JKAbramshttps://wiki.archlinux.org/index.php?title=Wine&diff=179820Wine2012-01-23T09:45:49Z<p>JKAbrams: /* Using WINEARCH */</p>
<hr />
<div>[[Category:Wine (English)]]<br />
[[fr:Wine]]<br />
{{i18n|Wine}}<br />
<br />
[[Wikipedia:Wine (software)|Wine]] is a compatibility layer capable of running Microsoft Windows applications on Unix-like operating systems. Windows programs running in Wine act as native programs would, running without the performance or memory usage penalties of an emulator, with a similar look and feel to other applications on your desktop environment.<br />
<br />
== Installation ==<br />
Wine is constantly updated and available in the [community] repository for i686 and in [multilib] for x86_64.<br />
{{Note|If you are on x86_64, you will need to enable the [multilib] repository (disabled by default) in {{ic|/etc/pacman.conf}} or you will get an error because [[pacman]] can not find the wine package without it.}}<br />
# pacman -S wine<br />
<br />
You may also require wine_gecko if your applications make use of Internet Explorer<br />
<br />
# pacman -S wine_gecko<br />
<br />
=== Architectural differences ===<br />
Wine in Arch Linux on i686 is packaged just like expected. It includes a standard 32-bit Wine installation and is unable to execute any 64-bit Windows applications. However, the x86_64 Wine package includes both, a 32-bit and a 64-bit Windows compatibility layer in one. <br />
<br />
This so called [[Wikipedia:WoW64|WoW64]] allows the user to use 32-bit and 64-bit Windows programs concurrently and even in the same WINEPREFIX with a win64 WINEARCH. The current support for this in Wine itself is limited and users are recommended to use a win32 WINEPREFIX. See [[Wine#Using_WINEARCH]] for more information on this.<br />
<br />
To clarify the above, the i686 package Wine will work exactly like a x86_64 package Wine with a win32 WINEPREFIX with no ill effects.<br />
<br />
== Configuration ==<br />
By default, Wine stores its configuration files and installed Windows programs in {{ic|~/.wine}}. This directory is commonly called a "Wine prefix" or "Wine bottle." It is created/updated automatically whenever you run a Windows program or one of Wine's bundled programs such as winecfg. The prefix directory also contains a tree which your Windows programs will see as "C: drive."<br />
<br />
You can override the location Wine uses for a prefix with the WINEPREFIX environment variable. This is useful if you want to use separate configurations for different Windows programs. For example if you run one program with<br />
$ env WINEPREFIX=~/.win-a wine program-a.exe<br />
and another with<br />
$ env WINEPREFIX=~/.win-b wine program-b.exe<br />
the two programs will each have separate "C: drives" and registries.<br />
<br />
To create a default prefix without running a Windows program or other GUI tool you can use<br />
$ env WINEPREFIX=~/.customprefix wineboot -u<br />
<br />
{{Note|Wine prefixes should not be confused with the same kind of "containment" found with other "virtual" environments. Generally speaking, if you can access a file or resource with your user account, programs running with Wine can too. Wine is not a jail.}}<br />
<br />
Configuring Wine is typically accomplished using winecfg, Wine's control panel, and regedit.<br />
* [http://wiki.winehq.org/winecfg winecfg] is a GUI configuration tool for Wine. You can run it from a console window with {{bc|$ winecfg}} or {{bc|1=$ WINEPREFIX=~/.some_prefix winecfg}}<br />
* [http://wiki.winehq.org/control control.exe] is Wine's implementation of Windows' Control Panel which can be accessed with {{bc|$ wine control}}<br />
* [http://wiki.winehq.org/regedit regedit] is Wine's registry editing tool. If winecfg and the Control Panel were not enough, see [http://wiki.winehq.org/UsefulRegistryKeys WineHQ's article on Useful Registry Keys]<br />
<br />
=== Using WINEARCH ===<br />
If you are using wine from [multilib], you will notice that '''winecfg''' will get you a 64-bit wine environment by default. You can change this behavior using the WINEARCH environment variable. Rename your ~/.wine directory and create a new wine environment by running: <br />
$ WINEARCH=win32 winecfg <br />
This will get you a 32-bit wine environment. Not setting WINEARCH will get you a 64-bit one.<br />
<br />
You can combine this with WINEPREFIX to make a separate win32 and win64 environment:<br />
$ WINEARCH=win32 WINEPREFIX=~/win32 winecfg <br />
$ WINEPREFIX=~/win64 winecfg<br />
<br />
Note that a win64 WINEARCH is meant to be able to run 32-bit Windows applications as well as 64-bit ones. However, support for this is limited in Wine and users are encouraged to use a win32 WINEPREFIX for the time being until support improves.<br />
<br />
{{Note|During prefix creation, the 64-bit version of wine treats all folders as 64-bit prefixs and will not create a 32-bit in any existing folder. To create a 32-bit prefix you have to let wine create the folder specified in WINEPREFIX.}}<br />
<br />
You can also use winetricks and WINEARCH in one command for installing something from winetricks like this (using Steam as an example):<br />
env WINEARCH=win32 WINEPREFIX=~/.local/share/wineprefixes/steam winetricks steam<br />
Note: you do not have create the steam subdirectory in the wineprefixes directory, it will create for you. See the Bottles section below for more information.<br />
<br />
=== Graphics Drivers ===<br />
For most games, Wine requires high performance accelerated graphics drivers. This likely means using proprietary binary drivers from [[Nvidia]] or [[ATI|Amd/ATI]]. [[Intel]] drivers should mostly work as well as they are going to out of the box.<br />
<br />
A good sign that your drivers are inadequate or not properly configured is when Wine reports the following in your terminal window:<br />
Direct rendering is disabled, most likely your OpenGL drivers haven't been installed correctly<br />
<br />
For x86-64 systems, additional 32-bit [multilib] or [[AUR]] packages are required:<br />
* '''NVIDIA''': {{bc|# pacman -S lib32-nvidia-utils}} For older lib32-nvidia-utils (e.g. nvidia-96xx drivers), see [http://aur.archlinux.org/packages.php?K=lib32-nvidia-utils here].<br />
* '''Intel''': {{bc|# pacman -S lib32-intel-dri}} Run Wine with {{bc|1=LIBGL_DRIVERS_PATH=/usr/lib32/xorg/modules/dri}}<br />
* '''AMD/ATI''': {{bc|# pacman -S lib32-ati-dri}} For ATI's proprietary drivers, install {{AUR|lib32-catalyst-utils}} from AUR<br />
<br />
{{Note|You might need to restart after having installed the correct library!}}<br />
<br />
=== Sound ===<br />
<br />
By default sound issues may arise when running Wine applications. Ensure only one sound device is selected in ''winecfg''. Currently, the [[Alsa]] driver is the most supported.<br />
<br />
If you want to use [[OSS]] in Wine, you will need to install the '''oss''' package. The OSS driver in the kernel will not suffice.<br />
<br />
===Fonts===<br />
<br />
If Wine applications are not showing easily readable fonts, you may not have Microsoft's Truetype fonts installed. See [[MS Fonts]]. If this does not help, try running {{ic|winetricks allfonts}}. (See [[#Winetricks]] below.)<br />
<br />
After running such programs, kill all wine servers and run winecfg. Fonts should be legible now.<br />
<br />
If the fonts look somehow smeared, import the following text file into the Wine registry with [http://wiki.winehq.org/regedit regedit]:<br />
[HKEY_CURRENT_USER\Software\Wine\X11 Driver]<br />
"ClientSideWithRender"="N"<br />
<br />
=== Desktop Launcher Menus ===<br />
By default, installation of Wine does not create desktop menus/icons for the software which comes with Wine (e.g. for winecfg, winebrowser, etc). However, installing Windows programs with Wine, in most cases, should result in the appropriate menu/desktop icons being created. For example, if the installation program (e.g. setup.exe) would normally add an icon to your Desktop or "Start Menu" on Windows, then Wine should create corresponding freedesktop.org style .desktop files for launching your programs with Wine.<br />
<br />
{{Tip|If menu items were ''not'' created while installing software or have been lost, [http://wiki.winehq.org/winemenubuilder winemenubuilder] may be of some use.}}<br />
<br />
If you wish to add on to the menu to create an Ubuntu-like Wine sub-menu, then follow these instructions:<br />
<br />
==== Creating Menu Entries ====<br />
First, install a Windows program using Wine to create the base menu. After the base menu is created, you can start to add the menu entries. In GNOME, right-click on the desktop and select "Create Launcher...". The steps might be different for KDE/Xfce. Make three launchers using these settings:<br />
'''Type''': Application<br />
'''Name''': Configuration<br />
'''Command''': winecfg<br />
'''Comment''': Configure the general settings for Wine<br />
<br />
'''Type''': Application<br />
'''Name''': Uninstall Programs<br />
'''Command''': wine uninstaller<br />
'''Comment''': Uninstall Windows programs under Wine properly<br />
<br />
'''Type''': Application<br />
'''Name''': Browse C:\ Drive<br />
'''Command''': wine winebrowser c:\\<br />
'''Comment''': Browse the files in the virtual Wine C:\ drive<br />
Now that you have these three launchers on your desktop, it is time to put them into the menu. But, first you should change the launchers to dynamically change icons when a new icon set is installed. To do this, open the launchers that you just made in your favorite text editor. Change the following settings to these new values:<br />
''Configuration'' launcher:<br />
Icon[en_US]=wine-winecfg<br />
Icon=wine-winecfg<br />
''Uninstall Programs'' launcher:<br />
Icon[en_US]=wine-uninstaller<br />
Icon=wine-uninstaller<br />
''Browse C:\ Drive'' launcher:<br />
Icon[en_US]=wine-winefile<br />
Icon=wine-winefile<br />
If these settings produce a ugly/non-existent icon, it means that there are no icons for these launchers in the icon set that you have enabled. You should replace the icon settings with the explicit location of the icon that you want. Clicking the icon in the launcher's properties menu will have the same effect. A great icon set that supports these shortcuts is [http://www.gnome-look.org/content/show.php/GNOME-colors?content=82562 GNOME-colors].<br />
<br />
Now that you have the launchers fully configured, now it is time to put them in the menu. Copy them into {{ic|~/.local/share/applications/wine/}}.<br />
<br />
Wait a second, they aren't in the menu yet! There is one last step. Create the following text file {{hc|~/.config/menus/applications-merged/wine-utilities.menu|<nowiki><br />
<!DOCTYPE Menu PUBLIC "-//freedesktop//DTD Menu 1.0//EN"<br />
"http://www.freedesktop.org/standards/menu-spec/menu-1.0.dtd"><br />
<Menu><br />
<Name>Applications</Name><br />
<Menu><br />
<Name>wine-wine</Name><br />
<Directory>wine-wine.directory</Directory><br />
<Include><br />
<Filename>wine-Configuration.desktop</Filename><br />
</Include><br />
<Include><br />
<Filename>wine-Browse C:\ Drive.desktop</Filename><br />
</Include><br />
<Include><br />
<Filename>wine-Uninstall Programs.desktop</Filename><br />
</Include><br />
</Menu><br />
</Menu><br />
</nowiki>}}<br />
Go check in the menu and there should be the minty fresh options waiting to be used!<br />
<br />
==== KDE 4 Menu Fix[https://bugs.launchpad.net/ubuntu/+source/wine/+bug/263041] ====<br />
The Wine menu items may appear in "Lost & Found" instead of the Wine menu in KDE 4. This is because kde-applications.menu is missing the MergeDir option.<br />
<br />
Edit {{ic|/etc/xdg/menus/kde-applications.menu}}<br />
<br />
At the end of the file add {{ic|<MergeDir>applications-merged</MergeDir>}} after {{ic|<DefaultMergeDirs/>}}, it should look like this:<br />
<Include><br />
<And><br />
<Category>KDE</Category><br />
<Category>Core</Category><br />
</And><br />
</Include><br />
<DefaultMergeDirs/><br />
'''<MergeDir>applications-merged</MergeDir>'''<br />
<MergeFile>applications-kmenuedit.menu</MergeFile><br />
</Menu><br />
<br />
Alternatively you can create a symlink to a folder that KDE does see:<br />
ln -s ~/.config/menus/applications-merged ~/.config/menus/kde-applications-merged<br />
<br />
This has the added bonus that an update to KDE won't change it, but is per user instead of system wide.<br />
<br />
== Running Windows Applications ==<br />
{{Warning|Do not run or install Wine applications as root! See http://wiki.winehq.org/FAQ#run_as_root for more details.}}<br />
To run a 32-bit windows application:<br />
$ wine <path to exe><br />
<br />
To run a 64-bit windows application on a x86-64 system:<br />
$ wine64 <path to exe><br />
<br />
To install using an MSI installer, use the included msiexec utility:<br />
$ msiexec installername.msi<br />
<br />
{{Tip|The [http://www.winehq.org official Wine site] contains a wealth of information about running Windows applications with Wine. Of particular interest are:<br />
* [http://wiki.winehq.org/FAQ The official FAQ] - General information about Wine and Frequently Asked Questions<br />
* [http://appdb.winehq.org/ The Wine Application Database (AppDB)] - Information about running specific Windows applications (Known issues, ratings, guides, etc tailored to specific applications)<br />
* [http://forum.winehq.org/ The WineHQ Forums] - A great place to ask questions ''after'' you have looked through the FAQ and AppDB<br />
<br />
If it does not "just work," these resources will often be your first stops toward getting your Windows software working.<br />
}}<br />
<br />
== Tips and Tricks ==<br />
These tools will assist in the installation of typical Windows components. In most cases they should be used as a last effort, as it may severely alter your wine configuration.<br />
<br />
=== Installing Microsoft Office 2007 ===<br />
<br />
A small tweak is needed to install the office suite. Follow these steps to accomplish it:<br />
<br />
$ WINEARCH=win32 WINEPREFIX=/path/to/wineprefix winecfg<br />
# pacman -S winetricks<br />
$ winetricks msxml3<br />
$ wine /path/to/office_cd/setup.exe<br />
<br />
For additional info, see the [http://appdb.winehq.org/appview.php?iVersionId=4992 WineHQ] article.<br />
<br />
=== OpenGL Modes ===<br />
Many games have an OpenGL mode which ''may'' preform better than their default DirectX mode. While the steps to enable OpenGL rendering is ''application specific'', many games accept the {{Ic|-opengl}} parameter.<br />
$ wine /path/to/3d_game.exe -opengl<br />
<br />
You should of course refer to your application's documentation and Wine's [http://appdb.winehq.org AppDB] for such application specific information.<br />
<br />
=== PlayOnLinux ===<br />
[http://www.playonlinux.com/ PlayOnLinux] is a graphical Windows and DOS program manager. It contains many scripts to assist the configuration and running of progams. You can find the [http://aur.archlinux.org/packages.php?ID=14986 PKGBUILD] in AUR.<br />
<br />
PlayOnLinux can also manage multiple Wine versions and use a specific version for each executable because of regressions. If you need to know what Wine version works best for a certain game, try the [http://appdb.winehq.org/ Wine Application Database].<br />
<br />
=== PyWinery ===<br />
[http://code.google.com/p/pywinery/ PyWinery] is a graphical and simple wine-prefix manager which allows you to launch apps and manage configuration of separate prefixes, also have a button to open winetricks in the same prefix, to open prefix dir, winecfg, application uninstaller and wineDOS. You can install [https://aur.archlinux.org/packages.php?ID=48382 PyWinery from AUR]. It is especially useful for having differents settings like DirectX games, office, programming, etc, and choose which prefix to use before you open an application or file.<br />
<br />
It's recommended using winetricks by default to open. exe files, so you can choose between any wine configuration you have.<br />
<br />
=== Sidenet Wine Configuration Utility ===<br />
{{Note|The link appears to be broken.}}<br />
<br />
[http://sidenet.ddo.jp/winetips/config.html Sidenet's wine-config]<br />
<br />
* Download the latest version<br />
* unpack it<br />
* READ THE README<br />
* execute<br />
./setup<br />
* Follow the instructions<br />
<br />
'''Keep in mind''': Like stated on the [http://sidenet.ddo.jp/winetips/config.html site], you're only allowed to install DCOM98 if you possess a valid License for Windows98.<br />
<br />
<br />
=== Using Wine as an interpreter for Win16/Win32 binaries ===<br />
It is also possible to tell the kernel to use wine as an interpreter for all Win16/Win32 binaries. First mount the binfmt_misc filesystem:<br />
# mount -t binfmt_misc none /proc/sys/fs/binfmt_misc<br />
Or you can add this line to your {{ic|/etc/fstab}}:<br />
none /proc/sys/fs/binfmt_misc binfmt_misc defaults 0 0<br />
Then, tell the kernel how to interpret Win16 and Win32 binaries:<br />
echo ':DOSWin:M::MZ::/usr/bin/wine:' > /proc/sys/fs/binfmt_misc/register<br />
You can add this line to {{ic|/etc/rc.local}} to make this setting permanent. In this case you may want to ignore stderr to avoid error messages when changing runlevels:<br />
{ echo ':DOSWin:M::MZ::/usr/bin/wine:' > /proc/sys/fs/binfmt_misc/register; } 2>/dev/null<br />
Now try to run a Windows program:<br />
chmod 755 exefile.exe<br />
./exefile.exe<br />
<br />
=== Wineconsole ===<br />
<br />
Often you may need to run .exes to patch game files, for example a widescreen mod for an old game, and running the .exe normally through wine might yield nothing happening. In this case, you can open a terminal and run the following command:<br />
<br />
$ wineconsole cmd<br />
<br />
Then navigate to the directory and run the .exe file from there.<br />
<br />
=== Wine-doors ===<br />
<br />
[http://www.wine-doors.org/ Wine-doors]<br />
<br />
Wine-doors is a WineTools replacement. It features a GNOME GUI and works like a package manager. Works fine in 64bit. [No longer available in the AUR].<br />
<br />
=== WineTools assistant ===<br />
{{Note|This tool is currently slightly outdated, but working.}}<br />
<br />
[http://www.von-thadden.de/Joachim/WineTools Winetools] is a script that facilitates in the installation of some core components for wine in order to install other programs. Note this is not necessary for wine, but does help if you want to get Internet Explorer running.<br />
<br />
{{Note|Microsoft policy is that you must have a license for IE6 in order to install DCOM98 or Internet Explorer 6. If you've ever owned a copy of Windows, you should be fine.}}<br />
<br />
You can download the [http://aur.archlinux.org/packages.php?ID=8913 PKGBUILD] script and see [[AUR]] for instructions to build and install.<br />
<!--<br />
<br />
=== Winetricks ===<br />
[http://wiki.winehq.org/winetricks Winetricks] is a quick script that allows one to install base requirements needed to run some Windows programs. Installable components includes DirectX 9.x, msxml (required by Microsoft Office 2007 and Internet Explorer), visual runtime libraries and many more.<br />
<br />
You can install winetricks via pacman.<br />
# pacman -S winetricks<br />
Then run winetricks '''as a normal user''':<br />
$ winetricks<br />
<br />
== Alternatives to Win16 / Win32 binaries ==<br />
<br />
* [[Codeweavers]] - Codeweavers' Crossover Office; Aimed at Office Users<br />
<br />
== External Resources ==<br />
* [http://www.winehq.com/ Official Wine Website]<br />
* [http://appdb.winehq.org/ Wine Application Database]<br />
* [http://linuxgamingtoday.wordpress.com/2008/02/16/quick-tips-to-speed-up-your-gaming-in-wine/ Advanced configuring your gfx card and OpenGL settings on wine; Speed up wine]<br />
* [http://wiki.gotux.net/code:perl:fileinfo FileInfo] - Find Win32 PE/COFF headers in EXE/DLL/OCX files under linux/unix environment.</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Talk:Wine&diff=179281Talk:Wine2012-01-20T13:43:11Z<p>JKAbrams: </p>
<hr />
<div>== bin32-wine vs. bin32-wine-suse? ==<br />
<br />
Is there any noteworthy difference between these two, e. g. speed or stability? I couldn't find an answer to that. -- [[User:Misc|Misc]] 16:27, 9 May 2010 (EDT)<br />
<br />
== WINEARCH=win32 ==<br />
<br />
Wine seems to treat empty folders as win64 prefix folders, making it confusing to create win32 prefixes in empty folders. It gives the error [wine: WINEARCH set to win32 but '/home/wine/photoshop' is a 64-bit installation].<br />
Perhaps we should add a note about this? See this bugreport http://bugs.winehq.org/show_bug.cgi?id=29661 -- [[User:JKAbrams|JKAbrams]] 14:35, 20 Jan 2012 (EDT)</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Talk:Wine&diff=179280Talk:Wine2012-01-20T13:42:23Z<p>JKAbrams: /* WINEARCH=win32 */</p>
<hr />
<div>== bin32-wine vs. bin32-wine-suse? ==<br />
<br />
Is there any noteworthy difference between these two, e. g. speed or stability? I couldn't find an answer to that. -- [[User:Misc|Misc]] 16:27, 9 May 2010 (EDT)<br />
<br />
== WINEARCH=win32 ==<br />
<br />
Wine seems to treat empty folders as win64 prefix folders, making it confusing to create win32 prefixes in empty folders. It gives the error [wine: WINEARCH set to win32 but '/home/wine/photoshop' is a 64-bit installation].<br />
Perhaps we should add a note about this? See this bugreport http://bugs.winehq.org/show_bug.cgi?id=29661 -- [[User:JKAbrams]] 14:35, 20 Jan 2012 (EDT)</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Talk:Wine&diff=179278Talk:Wine2012-01-20T13:39:07Z<p>JKAbrams: </p>
<hr />
<div>== bin32-wine vs. bin32-wine-suse? ==<br />
<br />
Is there any noteworthy difference between these two, e. g. speed or stability? I couldn't find an answer to that. -- [[User:Misc|Misc]] 16:27, 9 May 2010 (EDT)<br />
<br />
== WINEARCH=win32 ==<br />
<br />
Wine seems to treat empty folders as win64 prefix folders, making it confusing to create win32 prefixes in empty folders, perhaps we should add a note about this? See this bugreport http://bugs.winehq.org/show_bug.cgi?id=29661 -- [[User:JKAbrams]] 14:35, 20 Jan 2012 (EDT)</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Starcraft2&diff=172583Starcraft22011-12-07T10:29:56Z<p>JKAbrams: /* Installing from DVD */</p>
<hr />
<div>{{out of date}}<br />
==Environment==<br />
<br />
<br />
====You need Kernel <= 2.6.32 or kernel>=2.6.35====<br />
Without such a kernel, you will get one of these errors at the start most of the time:<br />
PRIV_INSTRUCTION, ACCESS_VIOLATION or Internal Battle.net Error<br />
<br />
====Wine >= 1.2====<br />
You need wine >= 1.2. community/wine is recent enough.<br />
$ pacman -S wine<br />
<br />
====Configure Wine====<br />
The sound in Starcraft 2 in Wine versions 1.3.25 and later works out of the box. For older versions of Wine, you must either disable the mmdevapi library, or use openal. <br />
{{Warning|If you disabled mmdevapi previously, you won't get any sound on new versions of Wine until you remove the exception.}}<br />
<br />
*For normal sound output (versions before 1.3.25)<br />
$ winecfg<br />
Go to Libraries, add "mmdevapi" and set it to "disabled".<br />
*Or you can install openal, in which case the mmdevapi setting isn't required:<br />
# pacman -S openal<br />
# pacman -S lib32-openal (this line is only necessary for x86_64)<br />
*Install libjpeg, libpng and libldap:<br />
# pacman -S libjpeg libpng libldap <br />
# pacman -S lib32-libjpeg lib32-libpng lib32-libldap (this line is only necessary for x86_64)<br />
*Edit the registry<br />
$ regedit<br />
Go to HKEY_CURRENT_USER/Software/Wine/Direct3D<br />
To create new entries: Right-click on Direct3D, select New -> String Value<br />
DirectDrawRenderer opengl<br />
Multisampling disabled<br />
OffscreenRenderingMode pbuffer<br />
PixelShaderMode enabled<br />
RenderTargetLockMode readtex<br />
StrictDrawOrdering disabled<br />
UseGLSL disabled<br />
VertexShaderMode hardware<br />
VideoMemorySize 1536 (Change this to however much memory your card has)<br />
*For Map-Editor: <br />
**The latest winetricks can be found at [http://winetricks.org/winetricks http://winetricks.org/winetricks], download and start:<br />
$ sh winetricks vcrun2005 vcrun2008<br />
*To get rid of some warnings that may or may not matter, you may want to install the following on x86_64:<br />
# pacman -S lib32-esound lib32-mpg123 lib32-jack<br />
*Don't emulate a virtual desktop for the installer.<br />
*If the installer doesn't work, backup and remove your .wine directory.<br />
*If you are asked to install Gecko, then click install to do so.<br />
*If the installer hangs while downloading patch 1.03, install ie6, and set the wine version to windows XP:<br />
$ sh winetricks ie6<br />
$ winecfg<br />
Go to Applications, set Windows Version to "Windows XP"<br />
*If your game says "Your StarCraft II installation is corrupt" do not fret, you've just forgotten to install lib32-libldap:<br />
# pacman -S lib32-libldap<br />
<br />
==Installing StarCraft II==<br />
<br />
<br />
====Installing from DVD====<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 />
====Blizzard Downloader====<br />
*Get the downloader from your [http://battle.net battle.net] account (you need to log in).<br />
*You may want to go to View -> Preferences and check "Don't throttle background download".<br />
*During the install, you will need about twice the space of the installed game, since it downloads to a temporary directory (of your choice) before installing. This directory can be deleted after install.<br />
<br />
====Starcraft 2 demo====<br />
https://us.battle.net/account/sc2-demo.html<br />
The download is 1.56 GB. You need to have a battle.net account.<br />
<br />
The demo got replaced by [http://us.battle.net/sc2/en/blog/3250656 StarCraft II: Starter Edition].<br />
<br />
==Playing StarCraft II==<br />
$ cd .wine/drive_c/Program\ Files/StarCraft\ II/<br />
$ wine start StarCraft\ II.exe<br />
(Or use the Starcraft II icon, but that'll make it more difficult to troubleshoot in case you have problems.)<br />
<br />
==Hints for Performance Tuning==<br />
* CTRL+ALT+F shows FPS<br />
* Launching the game with the -opengl flag has been reported to increase performance. (This may be specific to the mac version.)<br />
* Disabling Shader in wine could help, if FPS is too low. (It may also cause the game to not work at all. Again, possibly only mac.)<br />
* Make sure that you are not using old graphics drivers. Nvidia drivers should be 256.35 or later (extra/nvidia is 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 />
<br />
==x86_64==<br />
If you are running a 64bit version of Arch Linux, you may have trouble getting the updating done. Since StarCraft 2 uses Internet Explorer to render all the HTML pages, you need to have Internet Explorer installed. However, by the installer of IE6 will warn you that 64bit is not supported. By default, if you have created your wine configuration directory (~/.wine), it will be set to 64 bit. To overcome this problem, you can either recreate your ~/.wine configuration, or if you wish to keep your current ~/.wine configuration see the alternative method below. If you wish to recreate your ~/.wine configuration simply remove the ~/.wine directory, add export WINEARCH="win32" to your ~/.bashrc, logout of X, login once again and launch wine. It should create a ~/.wine folder. Next install ie6 with<br />
$ winetricks ie6<br />
<br />
[https://bbs.archlinux.org/viewtopic.php?pid=806725#p806725 More information can be found here]<br />
<br />
<br />
'''Alternative Method: Updating while keeping your 64bit ~/.wine directory'''<br />
<br />
This method uses a separate wine directory installed as 32bit. So the first step is to setup this alternate wine configuratoin. The easiest way to do this is to install a wine configuration for a separate user. You do not need to logout for this, just open up your terminal of choice and:<br />
<pre>$ login alternateuser</pre><br />
or if you're going to use root:<br />
<pre>$ su</pre><br />
Enter password, remove any already existing wine configuration supposing you do not use wine from this user, then set wine to use 32bit architecture and generate the configuration:<br />
<pre>$ export WINEARCH="win32"</pre><br />
<pre>$ winecfg</pre><br />
Install/update the wine configuration. No other settings need to be set after updating so you can just close the wine configuration window. Then use winetricks to install ie6:<br />
<pre>$ winetricks ie6</pre><br />
When that's done, use the new configuration to run Starcraft II.exe from your user's 64bit /home/user/.wine directory where Starcraft 2 is installed:<br />
<pre>$ wine /home/user/.wine/drive_c/Program\ Files\ \(x86\)/Starcraft\ II/Starcraft\ II.exe</pre><br />
This will run the updater/patcher installing all the patch files to your 64bit ~/.wine directory using the alternate user's 32bit .wine directory containing ie6. Close the updater when it's finished and you can then remove the new 32bit .wine configuration or keep it for later updates. Now you can go back to playing from your regular user using 64bit wine.<br />
<br />
==Other Problems==<br />
<br />
* For some, the game crashes upon exit.<br />
* If you want to use pulseaudio, compile it from [http://aur.archlinux.org/packages.php?O=0&K=wine-pulse&do_Search=Go AUR]. Pulseaudio may have a big performance impact, see [http://wiki.archlinux.org/index.php/Pulseaudio#Troubleshooting Pulseaudio Troubleshooting]<br />
* (There seems to be more issues with ati cards than nvidia.)<br />
* For some, in-gamechange of resolution 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 />
<br />
==References and Resources==<br />
<br />
*[http://appdb.winehq.org/objectManager.php?sClass=version&iId=20882 StarCraft II: Wings of Liberty (Retail)] (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] (archlinux forums)<br />
*[https://bbs.archlinux.org/viewtopic.php?id=103354 starcraft2 fails to update to patch 1.03] (archlinux forums)<br />
*[http://eu.battle.net/sc2/en/forum/topic/76237660 Known Issues] (battle.net EU forums)<br />
*[http://eu.battle.net/sc2/en/forum/topic/283440977 Patch News] (battle.net EU forums)<br />
*There used to be a link here about hotkey customization. Instead, [http://eu.battle.net/sc2/en/forum/topic/443018939#15 here is a link telling us that's not allowed.] (battle.net EU forums)<br />
<br />
[[Category:Gaming (English)]]<br />
[[Category:Wine (English)]]</div>JKAbramshttps://wiki.archlinux.org/index.php?title=Talk:Starcraft2&diff=172582Talk:Starcraft22011-12-07T10:29:34Z<p>JKAbrams: /* Performance Optimizing */</p>
<hr />
<div>===Performance Optimizing===<br />
Actually SC II does not run with this setting: * disable Shader in wine could help, if FPS is too low<br />
--[[User:Doddo|Doddo]] 07:53, 1 August 2010 (EDT)<br />
<br />
Well Shadersetting higher then medium is not playable, even on mac. But I think this is depend on graphic card. --Unknown<br />
<br />
Huh? Medium? I can select Hardware or None. Are we talking about winecfg -> Graphics -> Direct3D -> Vertex Shader Support? --[[User:Montschok|Montschok]] 20:54, 11 August 2010 (EDT)<br />
<br />
<br />
===Staring Installer===<br />
"wine start /media/dvd/Installer.exe" gives: err:start:wmain Option 'L"/dvd/Installer.exe"' not recognized'<br />
Use<br />
"wine start /unix /media/dvd/Installer.exe"<br />
or simply:<br />
"wine /media/dvd/Installer.exe"<br />
Why is start needed at all? Added the /unix switch to wiki.</div>JKAbrams