Difference between revisions of "KDE"

From ArchWiki
Jump to: navigation, search
(Full install)
(update interlanguage links)
(Tag: wiki-scripts)
 
(960 intermediate revisions by more than 100 users not shown)
Line 1: Line 1:
[[Category:Desktop environments (English)]]
+
[[Category:KDE]]
[[Category:HOWTOs (English)]]
+
[[ar:KDE]]
{{i18n|KDE}}
+
[[cs:KDE]]
[[de:KDE]]
+
[[de:Plasma]]
 +
[[es:KDE]]
 +
[[fa:KDE]]
 
[[fr:KDE]]
 
[[fr:KDE]]
 +
[[it:KDE]]
 +
[[ja:KDE]]
 +
[[pl:KDE]]
 +
[[ru:KDE]]
 +
[[zh-hans:KDE]]
 +
[[zh-hant:KDE]]
 +
{{Related articles start}}
 +
{{Related|Desktop environment}}
 +
{{Related|Display manager}}
 +
{{Related|Dolphin}}
 +
{{Related|Window manager}}
 +
{{Related|Qt}}
 +
{{Related|KDevelop}}
 +
{{Related|Trinity}}
 +
{{Related|Uniform Look for Qt and GTK Applications}}
 +
{{Related articles end}}
  
{{Article summary start}}
+
KDE is a software project currently comprising of a [[desktop environment]] known as Plasma, a collection of libraries and frameworks (KDE Frameworks) and several applications (KDE Applications) as well. KDE upstream has a well maintained [https://userbase.kde.org/ UserBase wiki]. Detailed information about most KDE applications can be found there.
{{Article summary text|For users on Linux and Unix, KDE offers a full suite of user workspace applications which allow interaction with these operating systems in a modern, graphical user interface. This article covers its installation, configuration, and troubleshooting.}}
 
{{Article summary text|KDE uses the [[Qt]] toolkit.}}
 
{{Article summary heading|Overview}}
 
{{Article summary text|{{Graphical user interface overview}}}}
 
{{Article summary heading|Related}}
 
{{Article summary wiki|Plasma}}
 
{{Article summary end}}
 
  
From [http://www.kde.org/community/whatiskde/softwarecompilation.php KDE - KDE Software Compilation]:
+
== Installation ==
  
:''The KDE Software Compilation grew out of the history of the KDE Project. In its inception, KDE was formed to create a beautiful, functional and free desktop computing environment for Linux and similar operating system. At the time, these systems lacked a graphical user environment that could rival the offerings from the larger proprietary operating system vendors. KDE was created to fill this gap.''
+
=== Plasma ===
  
:''The KDE Software Compilation is the set of libraries, workspaces, and applications produced by KDE that share this common heritage, and continue to use the synchronized release cycle. Software may move in and out of this semi-formally defined collection depending on the particular needs of the contributors who are working on that software, with exceptions made to ensure that binary compatibility remains at the library level throughout any major release of the compilation.''
+
Before installing Plasma, make sure you have a working [[Xorg]] installation on your system.
  
From [http://www.kde.org/download/ KDE - Getting KDE Software]:
+
[[Install]] the {{Pkg|plasma-meta}} meta-package or the {{Grp|plasma}} group. For differences between {{Pkg|plasma-meta}} and {{Grp|plasma}} reference [[Creating packages#Meta packages and groups]]. Alternatively, for a more minimal Plasma installation, install the {{Pkg|plasma-desktop}} package.
  
:''KDE software consists of a large number of individual applications and a desktop workspace as a shell to run these applications. You can run KDE applications just fine on any desktop environment. KDE applications are built to integrate well with your system's components. By using also KDE workspace, you get even better integration of your applications with the working environment while lowering system resource needs.''
+
To enable support for [[Wayland]] in Plasma, also install the {{Pkg|plasma-wayland-session}} package.
  
==Overview==
+
=== KDE applications and language packs ===
  
'''KDE 4.6''' Software Compilation is the current major release of KDE that includes a number of improvements and bug fixes.  The new Arch package set for KDE makes it possible to only install those applications you like.''
+
To install the full set of KDE Applications, install the {{Grp|kde-applications}} group or the {{Pkg|kde-applications-meta}} meta-package. Note that this will only install applications, it will not install any version of Plasma.
  
Important features of the Arch Linux KDE SC in short:
+
Most KDE packages ship their own translations. The exception is KDE4-based packages from kde-applications. If you need language files for these packages, install {{ic|kde-l10n-'''''yourlanguagehere'''''}} (e.g. {{Pkg|kde-l10n-de}} for the German language). For a full list of available languages see the [https://www.archlinux.org/packages/extra/any/kde-l10n/ kde-l10n split package].
* '''Split packages'''; for more Information see [[KDE_Packages|KDE Packages]] and [[DeveloperWiki:Splitting_KDE|Splitting KDE]].
 
* You can use different Phonon backends, like Gstreamer, Xine or VLC
 
* Meta packages ensure a smooth upgrade and emulate the old monolith packages for those who prefer them.
 
  
Important hints for upgraders:
+
=== Unstable releases ===
* Always check if your mirror is '''up to date'''.
 
* pacman will ask you to replace '''all''' kde packages with kde-meta packages.
 
* '''Do not force an update'''.  If pacman complains about conflicts please '''file a bug report'''.
 
* You can remove the meta packages and the sub packages you do not need after the update.
 
* If you do not like split packages just keep using the kde-meta packages.
 
  
:Information about upstream changes are be available [http://kde.org/announcements/4.6 here]
+
See [[Official repositories#kde-unstable]]
  
===Arch Linux notes (KDE SC 4.6) ===
+
== Starting Plasma ==
 +
{{Note|Although it is possible to launch Plasma under [[Wayland]], there are some missing features and known problems as of Plasma 5.11. See the [https://community.kde.org/Plasma/5.11_Errata#Wayland Plasma 5.11 Errata] for a list of issues and the [https://phabricator.kde.org/project/board/99/ Plasma on Wayland workboard] for the current state of development. Use [[Xorg]] for the most complete and stable experience.}}
  
* This release offers '''UPower''', '''UDev''' and '''UDisks''' support that can be used instead of the deprecated HAL. For that, the hal package is no more a requirement of kdebase-workspace and can be removed from your system, unless it is needed by other packages.
+
Plasma can be started either using a [[display manager]], or from the console.
  
* KDE PIM 4.6 is yet '''not''' available, so we will continue with the 4.4 series.
+
=== Using a display manager ===
  
* Also, with the last Phonon update, the DEVs declared the Xine backend no longer maintained; you really should think to switch to the GStreamer or the VLC backend.
+
* Select ''Plasma'' to launch a new session in [[Xorg]].
 +
* [[Install]] {{Pkg|plasma-wayland-session}} and select ''Plasma (Wayland)'' to launch a new session in [[Wayland]].
  
* In case of any error, try using a new user account or (re)moving KDE's configuration which can be found at ~/.kde4 /tmp/kde- /var/tmp/kdecache-. Akonadi saves its data at ~/.config/akonadi and ~/.local/share/akonadi.
+
{{Note|The [[NVIDIA]] proprietary driver implementation for Wayland requires EGLStreams. KDE have not implemented EGLStreams in their Wayland [https://blog.martin-graesslin.com/blog/2016/09/to-eglstream-or-not implementation]. The following workarounds are available:
 +
*Using the [[Nouveau]] driver.
 +
*Using the (default) Xorg session.
 +
}}
  
* The removed packages are: kdegames-ksame, kdesdk-kbugbuster, kdeutils-okteta The new packages are: kdeaccessibility-kaccessible, kdegames-klickety, kdesdk-okteta, kdeutils-filelight, kdeplasma-addons-concontainments, kdeplasma-addons-runners-events
+
=== From the console ===
  
==Installation==
+
To start Plasma with [[xinit]]/''startx'', append {{ic|exec startkde}} to your {{ic|.xinitrc}} file. If you want to start Xorg at login, please see [[Start X at login]]. To start a Plasma on Wayland session from a console, run {{ic|startplasmacompositor}}.
  
=== Full install ===
+
== Configuration ==
  
To install the entire KDE set, first '''fully upgrade your system''':
+
Most settings for KDE applications are stored in {{ic|~/.config}}, but some older applications may use {{ic|~/.kde4}}. However, configuring KDE is primarily done through the '''System Settings''' application. It can be started from a terminal by executing {{ic|systemsettings5}}.
  
# pacman -Syu
+
Some Frameworks 5 applications can use KDElibs 4 configuration, after moving the configuration files to the new location. Examples are:
  
and then:
+
* Konsole profiles from {{ic|~/.kde4/share/apps/konsole}} to {{ic|~/.local/share/konsole/}}
 +
* Application appearance from {{ic|~/.kde4/share/config/kdeglobals}} to {{ic|~/.config/kdeglobals}}
  
# pacman -S kde
+
=== Personalization ===
  
or
+
==== Plasma desktop ====
  
# pacman -S kde-meta
+
===== Themes =====
  
{{Note|Learn about the difference between kde and kde-meta packages in the [[KDE Packages]] article.}}
+
[https://store.kde.org/browse/cat/104/ Plasma themes] define the look of panels and plasmoids. For easy system-wide installation, some themes are available in both the official repositories and the [https://aur.archlinux.org/packages.php?O=0&K=plasmatheme&do_Search=Go AUR].
  
If you need language files:
+
The easiest way to install themes is by going through the ''System Settings > Workspace Theme > Desktop Theme > Get new Themes''.
  
# pacman -S kde-l10n-yourlanguagehere
+
This will present a frontend for the [https://store.kde.org/ KDE-Store] that allows you to install, uninstall, or update third-party plasmoid scripts.
  
e.g. kde-l10n-'''de''', for the German language.
+
Splash and Lock screens are currently unavailable. To customize these screens, you have to modify the original theme found in {{ic|/usr/share/plasma/look-and-feel/}}.
 +
See [https://www.kubuntuforums.net/showthread.php?67599-Plasma-5-background-images&s=59832dc20e5bfc2948dbb591d8453f61 this thread] on the Kubuntu forums.
  
{{Note| KDE 4.x is '''modular'''; you can install your preferred KDE applications without having to install an entire set of packages.  See [[KDE Packages]] for more information.}}
+
Note that the [[SDDM]] login screen is not part of this theme.
  
{{Note| KDE 4.x not need Gamin or Fam packages for monitoring changes on local files and directories [https://wiki.archlinux.org/index.php/KDE#Monitoring_changes_on_local_files_and_directories see more] }}
+
====== Qt and GTK+ Applications Appearance ======
  
=== Minimal install ===
+
{{Tip|For Qt and GTK theme consistency, see [[Uniform look for Qt and GTK applications]].}}
  
If you want to have a minimal installation of the KDE SC, here is an example:
+
; Qt4
  
# pacman -S kdebase kde-l10n-yourlanguagehere phonon-vlc
+
For Qt4 applications to have a consistent appearance, there are two options:
  
== Starting KDE ==
+
Install {{Pkg|breeze-kde4}} and then pick Breeze as GUI Style in {{ic|qtconfig-qt4}}; or install {{Pkg|breeze-gtk}} and pick GTK+ as GUI Style.
  
Add dbus to your DAEMONS array, to invoke it on boot.
+
; GTK+
  
DAEMONS=(syslog-ng '''dbus''' networkmanager alsa crond)
+
The recommended theme for a pleasant appearance in GTK+ applications is {{Pkg|breeze-gtk}} or {{AUR|gnome-breeze-git}}, a GTK+ theme designed to mimic the appearance of Plasma's Breeze theme.
 +
Install {{Pkg|kde-gtk-config}} and select the installed GTK-theme for GTK2/GTK3-Theme in ''System Settings > Application Style > GNOME Application Style''.
  
If you need to start it without rebooting:
+
In some themes, tooltips in GTK+ applications have white text on white backgrounds making it difficult to read. To change the colors in GTK2 applications, find the section for tooltips in the {{ic|.gtkrc-2.0}} file and change it. For GTK3 application two files need to be changed, {{ic|gtk.css}} and {{ic|settings.ini}}.
 +
It might also help to uncheck the option to ''Apply colors to non-Qt applications'' under ''System Settings'' > ''Colors''.
  
# /etc/rc.d/dbus start
+
Some GTK2 programs like {{AUR|vuescan-bin}} still look hardly usable due to invisible checkboxes with the Breeze or Adwaita skin in a Plasma session. To workaround this, install and select e.g. the Numix-Frost-Light skin of the {{AUR|numix-frost-themes}} under ''System Settings'' > ''Application Style'' > ''GNOME Application Style (GTK)'' > ''Select a GTK2 Theme:''. Numix-Frost-Light looks similar to Breeze.
  
Starting KDE depends on your preferences. Basically there are two ways of starting KDE. Using '''KDM''' or '''xinitrc'''.
+
===== Widgets =====
  
=== Using KDM (KDE Display Manager)===
+
Plasmoids are little scripted (plasmoid scripts) or coded (plasmoid binaries) KDE applications designed to enhance the functionality of your desktop.
''It is highly recommended to get familiar with the [[Display Manager|full article]] concerning display managers, before you make any changes. See also [[KDM]] Wiki page.''
 
  
==== Starting KDM as a daemon ====
+
The easiest way to install plasmoid scripts is by right-clicking onto a panel or the desktop and choosing ''Add Widgets > Get new Widgets > Download Widgets''.
Add "'''kdm'''" (without the quotes) to daemons array in '''{{Filename|/etc/rc.conf}}'''
+
This will present a nice frontend for https://store.kde.org/ that allows you to install, uninstall, or update third-party plasmoid scripts with literally just one click.
  
DAEMONS=(syslog-ng dbus network crond ... '''kdm''')
+
Many Plasmoid binaries are available from the [https://aur.archlinux.org/packages.php?O=0&K=plasmoid&PP=50&SO=d&SB=v AUR].
  
==== Starting KDM through /etc/inittab [''preferable''] ====  
+
===== Sound applet in the system tray =====
  
Edit '''{{Filename|/etc/inittab}}''' and comment out:
+
[[Install]] {{Pkg|plasma-pa}} or {{Pkg|kmix}} (start Kmix from the Application Launcher). {{Pkg|plasma-pa}} is now installed by default with {{Grp|plasma}}, no further configuration needed.
#id:3:initdefault:
 
 
[...]
 
 
#x:5:respawn:/usr/bin/xdm -nodaemon
 
  
Then uncomment:
+
{{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|~/.config/kmixrc}}.}}
  
id:5:initdefault:
+
===== Disable panel shadow =====
 
[...]
 
 
x:5:respawn:/usr/bin/kdm -nodaemon
 
  
{{Note| In both methods KDM loads Xorg automatically.}}
+
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:
  
===Using xinitrc===
+
$ xprop -remove _KDE_NET_WM_SHADOW
''The meaning and usage of '''xinitrc''' is very well described [http://wiki.archlinux.org/index.php/Xinitrc here].
 
  
Edit '''{{Filename|/home/}}'''{{Filename|''your-username''}}'''{{Filename|/.xinitrc}}'''. Then uncomment:
+
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:
exec ck-launch-session startkde
 
After a reboot or/and login, each execution of Xorg ('''startx''' or '''xinit''') will start KDE automatically.
 
  
{{Warning| By doing this you may have restart/shutdown functions disabled in your KDE menu.}}
+
{{hc|/usr/local/bin/kde-no-shadow|<nowiki>
 +
#!/bin/bash
 +
for WID in $(xwininfo -root -tree | sed '/"Plasma": ("plasmashell" "plasmashell")/!d; s/^  *\([^ ]*\) .*/\1/g'); do
 +
  xprop -id $WID -remove _KDE_NET_WM_SHADOW
 +
done
 +
</nowiki>}}
  
{{Note| If you want to start Xorg at boot, please read [[Start X at boot]] article.}}
+
Set execution permissions for the script:
  
==Configuration==
+
# chmod 755 /usr/local/bin/kde-no-shadow
  
{{Note| Configuring KDE is primarily done in ''''System Settings''''. There are also a few other options available for the desktop with 'Desktop Settings' when you right click the desktop.}}
+
The script can be run on login with ''Add Script'' in ''Autostart'':
  
For other personalization options not covered below such as activities, different wallpapers on one cube, etc please refer to the [[Plasma]] wiki page.
+
$ kcmshell5 autostart
  
===Personalization===
+
==== Window decorations ====
  
How to set up the KDE desktop to your personal style; use different Plasma themes, window decorations and icon themes.  
+
[https://store.kde.org/browse/cat/114/ Window decorations] can be changed in ''System Settings > Application Style > Window Decorations''.
  
====Plasma Desktop====
+
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].
  
[[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".
+
==== Icon themes ====
  
=====Themes=====
+
Icon themes can be installed and changed on ''System Settings > Icons''.
  
[http://kde-look.org/index.php?xcontentmode=76&PHPSESSID=bba0ae5354c7818b519687ebf5badf0e 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 [http://aur.archlinux.org/packages.php?O=0&K=plasmatheme&do_Search=Go AUR].
+
{{Note|Although all modern Linux desktops share the same icon theme format, desktops like [[GNOME]] use fewer icons (esp. in menus and toolbars). Themes developed for such desktops usually lack icons required by Plasma and KDE apps. It is recommended to install Plasma compatible icon themes instead.}}
  
=====Widgets=====
+
==== Fonts ====
Plasmoids are little scripted or coded KDE apps that enhance the functionality of your desktop.  There are two kinds, plasmoid scripts and plasmoid binaries.
 
  
Plasmoid binaries must be installed using PKGBUILDS from [http://aur.archlinux.org/packages.php?O=0&K=plasmoid&do_Search=Go&PP=25&SO=d&SB=v AUR].  Or write your own PKGBUILD.
+
===== Fonts in a Plasma session look poor =====
  
The easiest way to install plasmoid scripts is by right-clicking onto a panel or the desktop:
+
Try installing the {{Pkg|ttf-dejavu}} and {{Pkg|ttf-liberation}} packages.
  
Add Widgets -> Get new Widgets -> Download Widgets
+
After the installation, be sure to log out and back in. You should not have to modify anything in ''System Settings > Fonts''. If you are using {{Pkg|qt5ct}}, the settings in Qt5 Configuration Tool may override the font settings in System Settings.
  
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.
+
If you have personally set up how your [[Fonts]] render, be aware that System Settings may alter their appearance. When you go ''System Settings > Fonts'' System Settings will likely alter your font configuration file ({{ic|fonts.conf}}).
  
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.
+
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.
  
====Window Decorations====
+
===== Fonts are huge or seem disproportional =====
  
[http://kde-look.org/index.php?xcontentmode=75 Window decorations] can be changed in
+
Try to force font DPI to {{ic|'''96'''}} in ''System Settings > Fonts''.
System Settings -> Workspace Appearance -> Window Decorations
 
There you can also directly download and install more themes with one click and some are available on [http://aur.archlinux.org/packages.php?O=0&K=kdestyle&do_Search=Go&PP=25&SO=d&SB=v AUR].
 
  
====KDE 4 Theme Integration with GTK Applications====
+
If that does not work, try setting the DPI directly in your Xorg configuration as documented in [[Xorg#Setting DPI manually]].
To better integrate GTK and KDE 4 themes, you can use '''QtCurve'''
 
  pacman -S qtcurve-gtk2 qtcurve-kde4 gtk-kde4
 
or '''oxygen-gtk'''
 
  pacman -S oxygen-gtk
 
or you can download a GTK theme that matches your version of KDE [http://kde-look.org/content/show.php?content=103741 here]. This theme comes closer to the original Oxygen and is updated frequently.
 
  
=====Automatic procedure=====
+
==== Space efficiency ====
To change the GTK theme to QtCurve or something else a few applications are available:
 
  pacman -S lxappearance
 
  pacman -S gtk-theme-switch2
 
  pacman -S gtk-chtheme
 
  
Then change the theme of your choice in the respective application:
+
The Plasma Netbook shell has been dropped from Plasma 5, see the following [https://forum.kde.org/viewtopic.php?f=289&t=126631&p=335947&hilit=plasma+netbook#p335899 KDE forum post]
lxappearance
+
However, you can achieve something similar by editing the file {{ic|~/.config/kwinrc}} adding
gtk-theme-switch2
+
{{ic|1=BorderlessMaximizedWindows=true}} in the {{ic|[Windows]}} section.
gtk-chtheme
 
  
=====Manual procedure=====
+
==== Thumbnail generation ====
To manually change the GTK theme to QtCurve, you need to create the file {{Filename|~/.gtkrc-2.0-kde4}} with the following content:
+
To allow thumbnail generation for media or document files on the desktop and in Dolphin, install {{Pkg|kdegraphics-thumbnailers}}, {{Pkg|ffmpegthumbs}} and {{AUR|kde-thumbnailer-odf}}.
include "/usr/share/themes/QtCurve/gtk-2.0/gtkrc"
 
include "/etc/gtk-2.0/gtkrc"
 
 
style "user-font"
 
{
 
    font_name="Sans Serif"
 
}
 
widget_class "*" style "user-font"
 
gtk-theme-name="QtCurve"
 
Then you need to create the symbolic link {{Filename|~/.gtkrc-2.0}}:
 
ln -s .gtkrc-2.0-kde4 .gtkrc-2.0
 
If you want also specify a font, you can add (and adapt) the following line to the file:
 
  gtk-font-name="Sans Serif 9"
 
  
=====Icons=====
+
Then enable the thumbnail categories for the desktop via ''right click'' on the ''desktop background'' > ''Configure Desktop'' > ''Icons'' > ''More Preview Options...''.
If you're using Oxygen icons and want a consistent look in GTK open/save dialogs, you can install an [http://aur.archlinux.org/packages.php?O=0&K=oxygenrefit2-icon-theme&do_Search=Go oxygenrefit2] icon theme from AUR and set it as your GTK icon theme.  Add the theme to the {{Filename|~/.gtkrc-2.0}} file or you can use lxappearance and set it.
 
gtk-icon-theme-name="OxygenRefit2"
 
There are also a couple GTK themes built on the [http://aur.archlinux.org/packages.php?ID=24329 gtk-kde42-oxygen-theme Oxygen style] that can also do this.
 
  
====Icon Themes====
+
In ''Dolphin'', navigate to ''Control'' > ''General'' > ''Previews''.
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].
 
  
====Arch Linux Logo Icon in Kicker menu====
+
=== Printing ===
Right click on the Kicker menu button, press '''Application launcher settings''' and then press the icon on the '''right'''. Then you may choose  Arch Linux icon or any other icon that will replace the default one.
 
  
Official Arch Linux artwork icons are in [http://www.archlinux.org/packages/extra/any/archlinux-artwork/ archlinux-artwork] package, available after installing at
+
{{Tip|Use the [[CUPS]] web interface for faster configuration. Printers configured in this way can be used in KDE applications. }}
/usr/share/archlinux/icons
 
  
====Fonts====
+
You can also configure printers in ''System Settings > Printers''. To use this method, you must first install {{Pkg|print-manager}} and {{Pkg|cups}}. See [[CUPS#Configuration]].
  
If by default, the fonts in KDE look poor, try installing the [http://www.archlinux.org/packages/extra/any/ttf-dejavu/ ttf-dejavu] and [http://www.archlinux.org/packages/community/any/ttf-liberation/ ttf-liberation] packages.
+
=== Samba/Windows support ===
  
After the installation, be sure to log out and back in. You should not have to modify any settings in the "Fonts" panel of the KDE System Settings application.
+
If you want to have access to Windows services, install [[Samba]] (package {{Pkg|samba}}).
  
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 ({{Filename|fonts.conf}}).  
+
The Dolphin share functionality requires the package {{Pkg|kdenetwork-filesharing}} and usershares, which the stock {{ic|smb.conf}} does not have enabled. Instructions to add them are in [[Samba#Creating usershare path]], after which sharing in Dolphin should work out of the box after restarting Samba.
  
There is no way to prevent this but if you set the values to match your {{Filename|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).  
+
Plasma's abilities to access SMB shares are limited, though. Writing to Windows shares is problematic and opening files from such shares, e.g. large videos, makes Plasma copying the whole file to the local system first.
 +
To workaround this, you can install a GTK based file browser like {{Pkg|thunar}} with {{Pkg|gvfs}} and {{Pkg|gvfs-smb}} (and {{Pkg|gnome-keyring}} for saving login credentials) to access SMB shares in a more able way.
 +
Another possible workaround is to [[mount]] a Samba share via {{Pkg|cifs-utils}} to make it look to Plasma like if the SMB share was just a normal local folder and thus can be accessed normally.
 +
The mount command could look like the following for write access to a public share:
 +
# mount -t cifs -o username=*,password=*,uid=1000,gid=1000,file_mode=0660,dir_mode=0770 //networkhost/share/ /home/user/localmountpoint/
 +
Make it permanent:
 +
{{hc|/etc/fstab|<nowiki>
 +
//networkhost/share/ /home/user/localmountpoint/ cifs defaults,username=*,password=*,uid=1000,gid=1000,file_mode=0660,dir_mode=0770 0 2
 +
</nowiki>}}
 +
It might be necessary to append {{ic|.local}} to the hostname. For some NAS devices it might also be necessary to append {{ic|1=vers=1.0}} to the argument line to enforce SMB 1.0 compatibility.
  
Note too that Gnomes' Font Preferences will also do this if you use both desktop environments.
+
An easier solution is to use {{AUR|samba-mounter-git}}, which offers basically the same functionality via an easy to use option located at ''System Settings'' > ''Network Drivers''.
  
====Space efficiency====
+
=== KDE Desktop activities ===
KDE is often '''criticized''' for being bloated.
 
  
The user might get this perception from seeing''' many toolbars and pretty big scaled icons in the applications'''. One thing that improved the situation was the new Kwin-Theme that came with KDE SC 4.4.* with the more elegant buttons that one can also resize. '''KDE Apps allows to hide many toolbars, menubars and statusbars'''.
+
[https://userbase.kde.org/Plasma#Activities KDE Desktop Activities] are special workspaces where you can select specific settings for each activity that apply only when you are using said activity.
  
=====All sorts of *bars=====
+
=== Power saving ===
Most toolbars of a program can be removed in the menubar-entry "'''Settings'''". There you often can hide the statusbar and often all toolbars. The last step should be to remove the menubar itself via '''Ctrl + M'''.
 
  
If you do not want to remove any bars you can still make them smaller or remove the text via:
+
[[Install]] {{Pkg|powerdevil}} for 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).
System Settings -> Application Appearance -> Style -> Fine Tuning ->  (Main toolbar text / Secondary toolbar text)
 
  
Since most aspect ratios of modern flat screens are wider than 4:3 it could be reasonable to put the toolbar '''at the left or right of a window''' to artificially stretch windows more to the monitors aspect ratio.
+
{{Accuracy|Regarding the note below, it might be that the problem is the logind setting ''LidSwitchIgnoreInhibited'' which defaults to ''yes''. [https://bbs.archlinux.org/viewtopic.php?pid&#61;1649022#p1649022]}}
  
=====Plasma=====
+
{{Note|Powerdevil may not [[Power management#Power managers|inhibit]] all logind settings (such as the lid close action for laptops). In these cases, the logind setting itself will need to be changed - see [[Power management#Power management with systemd]].}}
There are also some settings and modifications you can apply to your plasmoids to make KDE less space wasting.  
 
  
For example, the "Digital Clock" wastes more space than the "Analogue Clock". The little plasma icon ("Cashew") that one can see in the panel can be hidden by locking the widgets via rightklicking onto the panel.
+
=== Autostarting applications ===
  
If you have got many tasks in your task-manager you should consider using ''Smooth-tasks''.  
+
Plasma can autostart applications and run scripts on startup and shutdown. To autostart an application, navigate to ''System Settings > Startup and Shutdown > Autostart'' and add the program or shell script of your choice. For applications, a {{ic|.desktop}} file will be created, for shell scripts, a symlink will be created.
  
This alternative task-manager allows you to just display the icons of a task thus using less space but still maintaining the ability of the user to distinguish the different tasks.
+
{{Note|
 +
* Programs can be autostarted on login only, whilst shell scripts can also be run on shutdown or even before Plasma itself starts.
 +
* Shell scripts will only be run if they are marked executable.
 +
}}
  
Install [http://aur.archlinux.org/packages.php?ID=29410 smooth-tasks] from the [[AUR]].
+
Place [[Desktop entries]] (i.e. {{ic|.desktop}} files) here:
  
After installing and substituting it with the original task-manager you should have a deep look at the settings since they are much broader.
+
; {{ic|~/.config/autostart}}: for starting applications at login.
one way of using the features of smooth-tasks could be to only display the icons of tasks and move the panel to the left or right of the screen. This is most useful on widescreens.
 
  
On very small screens it could be reasonable to set the bottom-panel to auto-hide completely.
+
Place or symlink shell scripts in one of the following directories:
  
For netbooks there is a special workspace, called Plasma Netbook, that makes better use of the screen:
+
; {{ic|~/.config/plasma-workspace/env}}: for executing scripts at login before launching Plasma.
 +
; {{ic|~/.config/autostart-scripts}}: for executing scripts at login.
 +
; {{ic|~/.config/plasma-workspace/shutdown}}: for executing scripts on shutdown.
  
System Settings -> Workspace Behavior -> Workspace -> Workspace Type
+
=== Phonon ===
  
=====KWin=====
+
From [[Wikipedia:Phonon (software)|Wikipedia]]:
The windows decorations can also be resized by making the buttons in the decoration smaller thus making the whole top border smaller:
 
System Settings -> Workspace Appearance -> Window Decorations -> Configure Decoration... -> Button size
 
You could also remove the side-border of all windows via:
 
System Settings -> Workspace Appearance -> Window Decorations -> Configure Decoration... -> Border size
 
  
=== Networking ===
+
:''“Phonon is the multimedia API provided by KDE and is the standard abstraction for handling multimedia streams within KDE software and also used by several Qt applications.
  
NetworkManager support has been added in KDE SC.  See [[Networkmanager#KDE4|NetworkManager]] for more information.
+
Phonon was originally created to allow KDE and Qt software to be independent of any single multimedia framework such as GStreamer or xine and to provide a stable API for a major version's lifetime.”''
  
Also you can use [http://aur.archlinux.org/packages.php?ID=40666/ wicd-client-kde].
+
'''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).
  
=== Printing ===
+
==== Which backend should I choose? ====
  
{{Tip|Use the [[Cups]] web interface for faster configuration.}}
+
You can choose between backends based on [[GStreamer]] and [[VLC]] – each available in versions for Qt4 applications and Qt5 applications ({{Pkg|phonon-qt4-gstreamer}}, {{Pkg|phonon-qt5-gstreamer}} – {{Pkg|phonon-qt4-vlc}}, {{Pkg|phonon-qt5-vlc}}).
  
The printers are configured in this way can be found in applications KDE.  
+
[https://www.phoronix.com/scan.php?page=news_item&px=MTUwNDM Upstream prefers VLC] but prominent Linux distributions (Kubuntu and Fedora-KDE for example) prefer GStreamer because that allows them to easily leave out patented MPEG codecs from the default installation. Both backends have a slightly different [https://community.kde.org/Phonon/FeatureMatrix features set].
  
You can also choose the printer configuration through '''Systemsettings -> Printer Configuration'''. To use this method, you must first install the packages:
+
In the past other backends were developed as well but are no longer maintained and their AUR packages have been deleted.
  
# pacman -S kdeadmin-system-config-printer-kde cups
+
{{Note|1=<br>
 +
* Multiple backends can be installed at once and prioritized at ''System Settings > Multimedia > Backend''.
 +
* According to the [https://forum.kde.org/viewtopic.php?f=250&t=126476&p=335080 KDE forums], the VLC backend lacks support for [[wikipedia:ReplayGain|ReplayGain]].
 +
* If you choose the vlc backend, you may experience crashes every time kde wants to send you a audible warning (and in quite a number of other cases as well, see [https://forum.kde.org/viewtopic.php?f=289&t=135956])
 +
* A possible fix is to run
 +
{{bc|# /usr/lib/vlc/vlc-cache-gen -f /usr/lib/vlc/plugins}}
 +
}}
  
===Samba/Windows support===
+
== Applications ==
  
If you want to have access to Windows services:
+
The KDE project provides a suite of applications that integrate with the Plasma desktop. See the {{Grp|kde-applications}} group for a full listing of the available applications. Also see [[:Category:KDE]] for related KDE application pages.
  
pacman -S samba
+
Aside from the programs provided in KDE Applications, there are many other applications available that can complement the Plasma desktop. Some of these are discussed below.
  
You may then configure your Samba shares through
+
=== System administration ===
  
  System Settings -> Sharing -> Samba
+
==== Terminate Xorg server through KDE System Settings ====
  
=== KDE Desktop Activities ===
+
Navigate to the submenu ''System Settings > Input Devices > Keyboard > Advanced (tab) > "Key Sequence to kill the X server"'' and ensure that the checkbox is ticked.
  
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.
+
==== KCM ====
Since KDE 4.5, the feature of changing Desktop Activities has been simplified.
 
  
On your desktop, click the Cashew Plasmoid and on the pop-up window press "Activities".
+
KCM stands for '''KC'''onfig '''M'''odule. KCMs can help you configure your system by providing interfaces in System Settings, or through the command line with ''kcmshell5''.
  
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.
+
* {{App|kde-gtk-config|GTK2 and GTK3 Configurator for KDE.|https://cgit.kde.org/kde-gtk-config.git|{{Pkg|kde-gtk-config}}}}
 +
* {{App|KCM Qt Graphics System|This KCM allows you to easily configure the standard Qt graphics system.|https://www.linux-apps.com/p/1127857/|{{AUR|kcm-qt-graphicssystem}}}}
 +
* {{App|UFW KControl Module|KDE4 control module for UFW ([[Uncomplicated Firewall]]).|https://www.linux-apps.com/p/1127851/|{{AUR|kcm-ufw}}}}
 +
* {{App|System policies|Set of configuration modules which allows administrator to change [[PolicyKit]] settings.|https://cgit.kde.org/polkit-kde-kcmodules-1.git|{{AUR|kcm-polkit-kde-git}}}}
 +
* {{App|wacom tablet|KDE GUI for the Wacom Linux Drivers.|https://www.linux-apps.com/p/1127862/|{{AUR|kcm-wacomtablet}}}}
 +
* {{App|Kcmsystemd|systemd control module for KDE.|https://github.com/rthomsen/kcmsystemd|{{Pkg|systemd-kcm}}}}
  
===Powersaving===
+
More KCMs can be found at [https://www.linux-apps.com/search?projectSearchText=KCM linux-apps.com].
  
KDE has integrated Powersaving service called "'''Powerdevil Power Management'''" that may adjust the powersaving profile of the system or/and the brightness of the screen (if supported).
+
=== Desktop search ===
  
 +
KDE implements desktop search with a software called Baloo, a file indexing and searching solution.
  
==== How to enable Cpufreq based powersaving ====
+
==== Baloo ====
  
Since KDE 4.5, [http://lists.kde.org/?l=kde-devel&m=126800277431817&w=2 Powerdevil doesn't handle CPU power schemes through Cpufreq]. CPU scaling is defined by the hardware and/or kernel "'''ondemand'''" governor power scheme and that's the official way to have the system's power management handled, according to the guidelines by the kernel power-management devs.
+
===== Using and configuring Baloo =====
  
{{Note| Despite the claim in the link above, it seems that CPU does not scale without cpufreq. Also, in Arch the default governor is "'''performance'''" and not "'''ondemand'''", so the user still needs to install the cpufrequtils package and add the "'''cpufreq_ondemand'''" module in the modules array in rc.conf.}}
+
In order to search using Baloo on the Plasma desktop, start krunner (default keyboard shortcut {{ic|ALT+F2}}) and type in your query. Within Dolphin press {{ic|CTRL+F}}.
  
You can easily use the desired governors through the cpufreq commands.
+
By default the Desktop Search KCM exposes only two options: A panel to blacklist folders and a way to disable it with one click.
  
In order to do that, follow these steps:
+
Alternatively you can edit your {{ic|~/.config/baloofilerc}} 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 stop}} and {{ic|balooctl disable}}.
  
1. Install cpufrequtils
+
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/}}.
  
pacman -S cpufrequtils
+
===== How do I index a removable device? =====
  
and make sure you have your CPU's cpufreq module loaded. For more information on this, visit [[Cpufreq|this article]].
+
By default every removable device is blacklisted. You just have to remove your device from the blacklist in the KCM panel.
  
2. Then, in '''System Settings > Power Management''', go to "Power Profiles" menu.
+
=== Web browsers ===
  
You can now create a new profile or edit the previous ones.  
+
* {{App|[[Wikipedia:Konqueror|Konqueror]]|Part of the KDE project, supports two rendering engines – KHTML and the [[Chromium]]-based Qt WebEngine.|https://konqueror.org/|{{Pkg|konqueror}}}}
 +
* {{App|[[Wikipedia:QupZilla|QupZilla]]|A Qt web browser with Plasma integration features. It uses Qt WebEngine.|https://www.qupzilla.com/|{{Pkg|qupzilla}}}}
 +
* {{App|[[Chromium]]|Chromium and its proprietary variant Google Chrome have limited Plasma integration. [[KDE Wallet#KDE Wallet for Chrome and Chromium|They can use KWallet]] and KDE Open/Save windows.|https://www.chromium.org/|{{Pkg|chromium}}}}
 +
* {{App|[[Firefox]]|Firefox can be configured to better integrate with Plasma. See [[Firefox#KDE/GNOME integration|Firefox KDE integration]] for details.|https://mozilla.org/firefox|{{Pkg|firefox}}}}
  
If you would like to have cpufrequtils as the software that will manage the CPU's powersaving behavior, type the following command in the "Script" text box:
+
=== PIM ===
  
cpufreq-set -g ondemand
+
KDE offers its own stack for personal information management. This includes emails, contacts, calendar, etc. To install all the PIM packages, you could use the meta-package {{Pkg|kde-meta-kdepim}}.
  
3. Now select the "Performance" profile and type this command in the "Script" text box:
+
==== Akonadi ====
  
  cpufreq-set -g performance
+
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.
  
You don't have to enable the "Enable System power saving" check box for this profile.
+
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).
  
{{Note| KDE 4.6 introduced a new power management framework and "solid-powermanagement", that could be previously used, '''is no longer a valid comman'''d.  It appears there is no longer a KDE method to set the CPU frequency governor.  However, "cpufreq-set -g ondemand" has the same affect. You can enter that in the script text box as above. If that fails, and you are happy with using the ondemand governor all the time, you can have this command executed at startup by placing it in "/etc/rc.local".}}
+
===== Installation =====
  
===Monitoring changes on local files and directories===
+
Install {{Pkg|akonadi}}. For additional addons, install {{Pkg|kdepim-addons}}. For EWS support, install {{AUR|akonadi-ews-git}}.
KDE uses inotify directly from kernel using kdirwatch(inside in kdelibs), so Gamin or FAM aren't needed, if you want see if kdirwatch is working probably you are interested install gui for kdirwatch ([https://aur.archlinux.org/packages.php?ID=31274 kdirwatch] from aur)
 
  
==System Administration==
+
{{Note|If you wish to use a database engine other than MariaDB/MySQL, then when installing the {{Pkg|akonadi}} package, use the following command to skip installing the {{Pkg|mariadb}} dependencies:
  
===Set keyboard layout in order switch language inputs===
+
{{bc|# pacman -S akonadi --assume-installed mariadb}}
In order to do that, navigate to
 
    System Settings > Input Devices > Keyboard
 
There you may choose your keyboard model at first.
 
{{Note| It is preferable that, if you use Evdev, that means Xorg automatic configuration for keyboards, you should choose "Evdev-managed keyboard".}}
 
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.
 
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.
 
  
===Terminate Xorg-server through KDE system settings===
+
}}
Navigate to
 
    System Settings -> Input Devices -> Keyboard -> Advanced (tab) > "Key Sequence to kill the X server" submenu
 
and tick the checkbox.
 
  
==Desktop Search and Semantic Desktop==
+
===== Disabling Akonadi =====
Most users who freshly install KDE are wondering what functionality the following four pieces of software are able to offer. Most features are still somehow hidden under the hood and yet not many applications featured in the KDE SC are using these interfaces. This chapter intends to first explain the features and then convince the user of the power these tools offer once properly integrated into KDE. The following sections are more or less a roughly shortened version of [http://thomasmcguire.wordpress.com/2009/10/03/akonadi-nepomuk-and-strigi-explained/  this blogpost].
 
  
===Soprano===
+
See this [https://userbase.kde.org/Akonadi#Disabling_the_Akonadi_subsystem section in the KDE userbase].
Soprano is a library for QT that is able to process RDF data. This is semantic data. Semantic data is a special kind of metadata which is much more flexible than metadata you might know from MP3-Tags or Meta-Tags in HTML since RDF data more resembles the structure of a spoken sentence, thus allowing a much wider field of ways dealing with them. Soprano stores semantic data in a backend and allows low level access to this data.
 
  
===Nepomuk===
+
===== Database configuration =====
Nepomuk is somehow the glue between Soprano and the KDE Desktop and thus the user. Nepomuk allows to tag the files with various entries and offers an API for the applications featured in KDE SC. It is enabled by default. Nepomuk can be turned on and off in
 
System Settings -> Desktop Search
 
  
Nepomuk has to keep the trace of a lot of files, because of that is recommended to increase the number of files that can be watched with inotify, to do that:
+
====== MariaDB/MySQL (using ZFS) ======
sysctl fs.inotify.max_user_watches=524288
 
  
To do it persistant:
+
If your home directory is on a ZFS pool, you will need to create {{ic|~/.config/akonadi/mysql-local.conf}} with the following contents:
echo "fs.inotify.max_user_watches = 524288" >> /etc/sysctl.conf
 
  
And restart Nepomuk.
+
[mysqld]
 +
innodb_use_native_aio = 0
  
===Akonadi===
+
Otherwise you will get the [[MySQL#OS error 22 when running on ZFS|OS error 22]]
Akonadi is one of the ways of getting data into Nepomuk. Its intention is to gather all kinds of PIM data from KMail, KAdressbook or Kopete. It collects chat contacts, email addresses, email attachments and email contents. First of all it feeds Nepomuk with this data but moreover it provides a centralized access point for all this data.
 
  
==== Disabling Akonadi ====
+
====== PostgreSQL ======
  
If you don't want Akonadi to be ran in your system (for your own reasons), edit '''~/.config/akonadi/akonadiserverrc''' and turn
+
Install and setup [[PostgreSQL]]. Make sure {{ic|postgresql.service}} is [[started]].
  
  StartServer=true
+
Edit Akonadi configuration file so that it has the following contents:
  
to
+
{{hc|~/.config/akonadi/akonadiserverrc|<nowiki>
 +
[%General]
 +
Driver=QPSQL
  
  StartServer=false
+
[QPSQL]
 +
Host=/run/postgresql/
 +
InitDbPath=/usr/bin/initdb
 +
Name=akonadi
 +
Options=
 +
Password=
 +
Port=5432
 +
ServerPath=/usr/bin/pg_ctl
 +
StartServer=true
 +
User=postgres
 +
</nowiki>}}
  
And then relogin into your account.
+
{{Note|If your PostgreSQL database username, password, and port differ from {{ic|postgres}}, {{ic|}} (nothing), and {{ic|5432}}, then make sure you respectively change the configuration options, {{ic|1=User=}}, {{ic|1=Password=}}, and {{ic|1=Port=}}.}}
  
==== Configuring Akonadi to use MySQL Server running on the System ====
+
Start Akonadi with {{ic|akonadictl start}}, and check its status: {{ic|akonadictl status}}.
  
First, you need to set up the database using the following commands (replace password with the correct one):
+
====== SQLite ======
  
  CREATE DATABASE akonadi;
+
Edit Akonadi configuration file to match the configuration below:
  GRANT ALL PRIVILEGES ON akonadi.* TO 'akonadiuser' IDENTIFIED BY 'password';
 
  FLUSH PRIVILEGES;
 
  
If '''~/.config/akonadi/mysql-local.conf''' does not exist then
+
{{hc|~/.config/akonadi/akonadiserverrc|2=
 +
[%General]
 +
Driver=QSQLITE3
  
cp /usr/share/config/akonadi/mysql-global.conf ~/.config/akonadi/mysql-local.conf
+
[QSQLITE3]
 +
Name=/home/''username''/.local/share/akonadi/akonadi.db
 +
}}
  
and uncomment the following line
+
=== KDE Telepathy ===
  
sql_mode=strict_trans_tables
+
[https://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.
  
Then edit '''~/.config/akonadi/akonadiserverrc''':
+
To install all Telepathy protocols, install the {{Grp|telepathy}} group.
 +
To use the KDE Telepathy client, install the {{Pkg|telepathy-kde-meta}} package that includes all the packages contained in the {{Grp|telepathy-kde}} group.
  
[%General]
+
==== Use Telegram with KDE Telepathy ====
Driver=QMYSQL
 
 
[QMYSQL]
 
Name=akonadi
 
Host=localhost
 
ServerPath=/usr/bin/mysqld
 
StartServer=false
 
User=akonadiuser
 
Password=<password>
 
Options=
 
 
[Debug]
 
Tracer=null
 
  
Restart the Akonadi server with:
+
[[Telegram]] protocol is available using {{pkg|telepathy-haze}}, installing {{aur|telegram-purple}} or {{aur|telegram-purple-git}} and {{aur|telepathy-morse-git}}. The username is the Telegram account telephone number (complete with the national prefix {{ic|+''xx''}}, e.g. {{ic|+49}} for Germany).
  
akonadictl restart
+
The configuration through 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 ({{ic|~/.local/share/telepathy/mission-control/accounts.cfg}}) after the account creation (if the quotes are not removed after, an authentication error should rise).
  
===Strigi Search===
+
{{Note|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.}}
Strigi is another way of feeding data into Nepomuk. It preferably indexes the users home-folder. Indexing means that it not only gathers filenames but also information about your music collection or tagged downloads you did with Kget. The Strigi search is also integrated into KDEs launcher which can be accessed via:
 
{{Keypress|Alt}} + {{Keypress|F2}}
 
  
By default, Dolphin has a search bar on top-right where you may type what you want to be found from Strigi's index.
+
=== Integrate Android ===
  
{{Note | Strigi has implications for resource usage on your computer - CPU, memory, disk access, disk space, battery life. If Strigi is too resource-hungry for you, you can turn it off in "'''System Settings -> Desktop Search'''". }}
+
[https://community.kde.org/KDEConnect KDE Connect] provides several features for you:
  
Strigi folder indexing can be configured in:
+
* Share files and URLs to/from KDE from/to any app, without wires.
System Settings -> Desktop Search -> Desktop Query -> Customize index folders…
+
* Touchpad emulation: Use your phone screen as your computer's touchpad.
 +
* Notifications sync (4.3+): Read your Android notifications from the desktop.
 +
* Shared clipboard: copy and paste between your phone and your computer.
 +
* Multimedia remote control: Use your phone as a remote for Linux media players.
 +
* WiFi connection: no usb wire or bluetooth needed.
 +
* RSA Encryption: your information is safe.
  
==KDM (KDE Desktop Manager)==
+
You will need to install KDE Connect both on your computer and on your Android. For PC side, install {{Pkg|kdeconnect}} package. For Android side, install {{ic|KDE Connect}} from [https://play.google.com/store/apps/details?id=org.kde.kdeconnect_tp Google Play] or from [https://f-droid.org/repository/browse/?fdid=org.kde.kdeconnect_tp F-Droid].
  
===KDM Xserver file===
+
It is possible to use KDE Connect even if you do not use the Plasma desktop. For desktop environments that use AppIndicators, such as Unity, install {{AUR|indicator-kdeconnect}} package as well.
An example configuration for KDM can be found at '''/usr/share/config/kdm/kdmrc'''. See '''/usr/share/doc/HTML/en/kdm/kdmrc-ref.docbook''' for all options.
 
  
===Configuring KDM===
+
== Tips and tricks ==
  
You can visit '''System Settings > Login Screen''' and make your changes. Whenever you press "Apply", a '''KDE Polkit authorization''' window appears which will ask you to give your root password in order to finish the changes.
+
=== Using an alternative window manager ===
  
==== Problems while Configuring KDM as a user ====
+
The component chooser settings in Plasma does not allow changing the window manager anymore. [https://github.com/KDE/plasma-desktop/commit/2f83a4434a888cd17b03af1f9925cbb054256ade]
 +
In order to change the window manager used you need to set the {{ic|KDEWM}} [[environment variable]] before KDE startup. [https://wiki.haskell.org/Xmonad/Using_xmonad_in_KDE] To do that you can create a script called {{ic|set_window_manager.sh}} in {{ic|~/.config/plasma-workspace/env}} and export the {{ic|KDEWM}} variable there. For example to use the i3 window manager :
  
If you seem not to be able to KDM settings when launching System Settings as user, press
+
{{hc|~/.config/plasma-workspace/env/set_window_manager.sh|2=
 +
export KDEWM=/usr/bin/i3
 +
}}
  
{{Keypress|Alt}} + {{Keypress|F2}}
+
And then make it executable :
  
and type
+
{{bc|$ chmod +x ~/.config/plasma-workspace/env/set_window_manager.sh}}
  
  kdesu systemsettings
+
==== KDE/Openbox session ====
  
In the pop-up kdesu window, enter your root password and wait for System Settings to be launched.
+
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.
  
{{Note| Since you have launched it as root, be careful when changing your settings. All settings configuration in root-launched System Settings are saved under /root/.kde4 and not under ~/.kde4 (your home location).}}
+
For those starting the session manually, add the following line to your {{ic|.xinitrc}} file:
  
In the System Settings window, go to Login Screen.
+
exec openbox-kde-session
  
==Phonon==
+
==== Re-enabling compositing effects ====
  
===What is Phonon?===
+
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]].
  
''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.
+
=== Configuring monitor resolution / multiple monitors ===
''
 
  
from Wikipedia.
+
To enable display resolution management and multiple monitors in Plasma, install {{Pkg|kscreen}}. This adds the additional options to ''Sytem Settings > Display and Monitor''.
  
'''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).
+
=== Disable opening application launcher with Super key (Windows key) ===
  
===Which backend should I choose?===
+
To disable this feature you currently can run the following command:
  
You can choose between various backends, like GStreamer ([http://www.archlinux.org/packages/?q=phonon-gstreamer phonon-gstreamer]), VLC ([http://www.archlinux.org/packages/?q=phonon-vlc phonon-vlc]), Xine ([http://www.archlinux.org/packages/?q=phonon-xine phonon-xine]) or even MPlayer in [unsupported] ([http://aur.archlinux.org/packages.php?K=phonon-mplayer phonon-mplayer]).
+
$ kwriteconfig5 --file kwinrc --group ModifierOnlyShortcuts --key Meta ""
  
According to [http://www.archlinux.org/news/kde-sc-46-to-extra/ announce of KDE 4.6 in Arch] and [http://mail.kde.org/pipermail/phonon-backends/2011-February/000500.html mail in Phonon dev list]:
+
== Troubleshooting ==
  
<blockquote>Xine is not maintained and thus will not see releases.</blockquote>
+
=== Configuration related ===
<blockquote>This intial preference currently rates
 
GStreamer highest, followed by VLC as there is some feature
 
difference.</blockquote>
 
  
==Using WebKit in Konqueror==
+
Many problems in KDE are related to configuration.
  
===What is WebKit?===
+
==== Plasma desktop behaves strangely ====
  
WebKit is an open source browser engine developed by Apple Inc. It is used by Safari and Google Chrome. WebKit is a derivative from the KHTML and KJS libraries and contain many improvements.
+
Plasma problems are usually caused by unstable '''Plasma widgets''' (colloquially called ''plasmoids'')  or '''Plasma themes'''. First, find which was the last widget or theme you had installed and disable it or uninstall it.
  
===How to use in Konqueror===
+
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 (https://bugs.kde.org/) '''only if it is an official widget'''. If it is not, it is recommended you find the entry on https://store.kde.org/ and inform the developer of that widget about the problem (detailing steps to reproduce, etc).
  
It is possible to use WebKit in Konqueror instead of KHTML. First install the kwebkitpart package :
+
If you cannot find the problem, but you do not want ''all'' the settings to be lost, navigate to {{ic|~/.config}}:
  
  pacman -S kwebkitpart
+
$ for j in plasma*; do mv -- "$j" "${j%}.bak"; done
  
Then, after executing Konqueror, press '''Settings > Configure Konqueror'''.  
+
This command will '''rename all Plasma related configs''' to *.bak (e.g. {{ic|plasmarc.bak}}) of your user and when you will relogin into Plasma, you will have the '''default''' settings back. To undo that action, remove the .bak file extension. If you already have *.bak files, rename, move, or delete them first. It is highly recommended that you create regular backups anyway. See [[Synchronization and backup programs]] for a list of possible solutions.
  
On the "General" submenu, select the "WebKit" as the "Default web browser engine".
+
==== Clean cache to resolve upgrade problems ====
 
You can, of course, choose KHTML again, if you don't like WebKit as the rendering engine.
 
  
==Troubleshooting==
+
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 music. This solution can also resolve problems with KDE and Qt programmes looking bad following upgrade.
  
===KDE and Qt programs look bad when in a different window manager===
+
Rebuild your cache with the following commands:
If you're using KDE or Qt programs but not in a full KDE session (specifically, you didn't run "startkde"), then as of KDE 4.6.1 you will need to tell Qt how to find KDE's styles (Oxygen, QtCurve etc.)
 
  
You just need to set the environment variable QT_PLUGIN_PATH. E.g. put
+
$ rm ~/.config/Trolltech.conf
 +
$ kbuildsycoca5 --noincremental
  
export QT_PLUGIN_PATH=$HOME/.kde4/lib/kde4/plugins/:/usr/lib/kde4/plugins/
+
=== Clean akonadi configuration to fix KMail ===
  
into your /etc/profile (or ~/.profile if you don't have root access). qtconfig should then be able to find your kde styles and everything should look nice again!
+
First, make sure that KMail is not running. Then backup configuration:
  
===KHotkeys issue===
+
$ cp -a ~/.local/share/akonadi ~/.local/share/akonadi-old
Ιf '''khotkeys''' does not work, make sure you have a fully updated system first.
+
  $ cp -a ~/.config/akonadi ~/.config/akonadi-old
You can also create ~/.kde4/Autostart/reloadkhotkeys.sh with contents
 
#!/bin/bash
 
  (sleep 3 && qdbus org.kde.kded /modules/khotkeys reread_configuration) &
 
and then do a
 
chmod u+x ~/.kde4/Autostart/reloadkhotkeys.sh
 
then logout & login.
 
  
===Enabling back/forward mouse buttons in Konqueror and Dolphin file managers===
+
Start ''SystemSettings > Personal'' and remove all the resources. Go back to Dolphin and remove the original {{ic|~/.local/share/akonadi}} and
First, you must install xautomation which can be downloaded from [[http://aur.archlinux.org/packages.php?ID=7312 AUR]] and xbindkeys, which can be installed using Pacman.  
+
{{ic|~/.config/akonadi}} - the copies you made ensure that you can back-track if necessary.
  
Next, create a text file named .xbindkeysrc and save it to your home directory. The content of the file should be:
+
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.
  
{{file|name=xbindkeysrc|content= <nowiki>
+
=== Fix empty IMAP inbox ===
# For the benefit of emacs users: -*- shell-script -*-
 
###########################
 
# xbindkeys configuration #
 
###########################
 
#
 
# Version: 1.8.0
 
#
 
# If you edit this file, do not forget to uncomment any lines
 
# that you change.
 
# The pound(#) symbol may be used anywhere for comments.
 
#
 
# To specify a key, you can use 'xbindkeys --key' or
 
# 'xbindkeys --multikey' and put one of the two lines in this file.
 
#
 
# The format of a command line is:
 
# "command to start"
 
# associated key
 
#
 
#
 
# A list of keys is in /usr/include/X11/keysym.h and in
 
# /usr/include/X11/keysymdef.h
 
# The XK_ is not needed.
 
#
 
# List of modifier:
 
# Release, Control, Shift, Mod1 (Alt), Mod2 (NumLock),
 
# Mod3 (CapsLock), Mod4, Mod5 (Scroll).
 
#
 
 
# The release modifier is not a standard X modifier, but you can
 
# use it if you want to catch release events instead of press events
 
 
# By defaults, xbindkeys does not pay attention with the modifiers
 
# NumLock, CapsLock and ScrollLock.
 
# Uncomment the lines above if you want to pay attention to them.
 
 
#keystate_numlock = enable
 
#keystate_capslock = enable
 
#keystate_scrolllock= enable
 
 
# Examples of commands:
 
 
"xbindkeys_show"
 
control+shift + q
 
 
# set directly keycode (here control + f with my keyboard)
 
"xterm"
 
c:41 + m:0x4
 
 
# specify a mouse button
 
"xterm"
 
control + b:2
 
 
#"xterm -geom 50x20+20+20"
 
# Shift+Mod2+alt + s
 
#
 
## set directly keycode (here control+alt+mod2 + f with my keyboard)
 
#"xterm"
 
# alt + c:0x29 + m:4 + mod2
 
#
 
## Control+Shift+a release event starts rxvt
 
#"rxvt"
 
# release+control+shift + a
 
#
 
## Control + mouse button 2 release event starts rxvt
 
#"rxvt"
 
# Control + b:2 + Release
 
 
# dolphin go back
 
"xte 'keydown Alt_L' 'key Right' 'keyup Alt_L'"
 
b:9
 
 
# dolphin go forward
 
"xte 'keydown Alt_L' 'key Left' 'keyup Alt_L'"
 
b:8
 
 
 
##################################
 
# End of xbindkeys configuration #
 
##################################
 
</nowiki>}}
 
  
Now create an autostart entry in /home/user_name/.kde4/Autostart named xbindkeys.desktop containing the following code:
+
For some IMAP accounts, kmail will show the inbox as a container with all other folders of this account inside. Kmail does not show messages in the inbox container but in all other subfolders, see [https://bugs.kde.org/show_bug.cgi?id=284172 KDE Bug 284172]. To solve this problem simply disable the server side subscribition in the kmail account settings.
  
{{file|name=xbindkeys.desktop|content= <nowiki>
+
=== Getting current state of KWin for support and debug purposes ===
[Desktop Entry]
 
Comment[en_US]=
 
Comment=
 
Encoding=UTF-8
 
Exec=xbindkeys
 
GenericName[en_US]=
 
GenericName=
 
Icon=
 
MimeType=
 
Name[en_US]=
 
Name=
 
Path=
 
StartupNotify=false
 
Terminal=false
 
TerminalOptions=
 
Type=Application
 
Version=1.0
 
X-DBUS-ServiceName=
 
X-DBUS-StartupType=
 
X-DCOP-ServiceType=
 
X-KDE-SubstituteUID=false
 
X-KDE-Username=
 
X-KDE-autostart-after=kdesktop
 
</nowiki>}}
 
  
Now just reboot your computer and you should have back/forward mouse button functionality in Dolphin and Konqueror.
+
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 [https://blog.martin-graesslin.com/blog/2012/03/on-getting-help-for-kwin-and-helping-kwin/ Martin's blog].
  
===Enabling thumbnails under Konqueror and Dolphin file managers===
+
$ qdbus org.kde.KWin /KWin supportInformation
  
For thumbnails of videos in konqueror and dolphin:
+
=== KF5/Qt5 applications do not display icons in i3/fvwm/awesome ===
  
  # pacman -S kdemultimedia-mplayerthumbs
+
See [[Qt#Configuration of Qt5 apps under environments other than KDE Plasma]].
or
 
  
  # pacman -S kdemultimedia-ffmpegthumbs
+
=== Graphical related problems ===
  
=== Suspend to Disk/Ram not working ===
+
==== Plasma keeps crashing with legacy Nvidia ====
If you are starting KDE with startx try adding ck-launch-session to the .xinitrc,
 
as so:
 
#!/bin/sh
 
#
 
# ~/.xinitrc
 
#
 
# Executed by startx (run your window manager from here)
 
# exec gnome-session
 
exec ck-launch-session startkde
 
# exec startxfce4
 
# ...or the Window Manager of your choice
 
This is done '''automatically with KDM'''.
 
  
=== Graphical related issues ===
+
This is caused by a [https://bugs.kde.org/show_bug.cgi?id=348753 bug in Plasma] when using the Nvidia-304xx driver. Rather than disabling compositing, create a file {{ic|kwin.sh}} in {{ic|~/.config/plasma-workspace/env/}} with the following contents:
  
==== Low 2D desktop performance (or) Artifacts appear when on 2D ====
+
#!/bin/sh
===== GPU driver problem =====
+
export KWIN_EXPLICIT_SYNC=0
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.
 
The open-source ATI and Intel drivers and the proprietary (binary) Nvidia driver should theoretically provide the best 2D and 3D acceleration.
 
  
===== The Raster engine workaround =====
+
Then go to ''System Settings > Startup and Shutdown > Autostart'' and ''Check/Add'' the script as a pre-KDE startup file.
If this doesn't solve your problems, maybe your driver doesn't provide a good '''XRender''' acceleration which the current Qt painter engine relies on by default.  
 
  
You can change the painter engine to software based only by invoking the application with the "'''-graphicssystem raster'''" command line. This rendering engine can be set as the default one by recompiling Qt with the same as configure option, "'''-graphicssystem raster'''".
+
==== Applications do not refresh properly ====
  
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.
+
If you use 3D-accelerated composition with [[Intel]], you might find that the Plasma panel and other applications do not refresh properly (stay frozen). Some Intel drivers have [https://bugzilla.redhat.com/show_bug.cgi?id=1259475 problems with EGL]. Go to ''System Settings > Display and Monitor > Compositor''. Set ''OpenGL interface'' to OpenGL 3.1. If that does not work, see [[Intel graphics#SNA issues]] for alternative solutions.
  
Since Qt 4.7+, recompiling Qt is not needed. Simply export '''QT_GRAPHICSSYSTEM=raster''', or "opengl", or "native" (for the default). Raster depends on the CPU, OpenGL depends on the GPU and high driver support (it's buggy and highly in development, so I wouldn't expect it to work), and Native is just using the X11 rendering (mixture, usually).
+
==== Bad performance ====
  
'''The best and automatic way to do that''' is to install [http://aur.archlinux.org/packages.php?ID=40582 kcm-qt-graphicssystem] from AUR and configure this particular Qt setting through
+
Make sure you have the proper driver for your GPU installed. See [[Xorg#Driver installation]] for more information. If you have an older card, it might help to [[#Disable desktop effects manually or automatically for defined applications]] or [[#Disable compositing]].
  
  System Settings > Qt Graphics System
+
===== Disable desktop effects manually or automatically for defined applications =====
  
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].
+
Plasma has desktop effects enabled by default and e.g. not every game will disable them automatically. You can disable desktop effects in ''System Settings > Desktop Effects'' and you can toggle desktop effects with {{ic|Alt+Shift+F12}}. Additionally, you can create custom KWin rules to automatically disable/enable compositing when a certain application/window starts under ''System Settings > Window Management > Window Rules''.
  
==== Konsole is slow in applications like vim ====
+
===== Disable compositing =====
This is a problem that is caused by slow glyph rendering. You can solve this by switching to a scalable font like Bitstream Vera Sans Mono.
 
  
==== Low 3D desktop performance====
+
In ''Sytem Settings > Display and Monitor'', uncheck ''Enable compositor on startup'' and restart Plasma.
KDE begins with desktop effects enabled.  Older cards may be insufficient for 3D desktop acceleration.  You can disable desktop effects in
 
System Settings -> Desktop Effects
 
or you can toggle desktop effects with
 
{{Keypress|Alt}} + {{Keypress|Shift}} + {{Keypress|F12}}
 
 
 
{{Note| You may encounter such problems with 3D desktop performance even when using a more powerful graphics card, but using catalyst proprietary driver (fglrx). This driver is known for having issues with 3D acceleration. Visit [[ATI|the ATi Wiki page]] for more troubleshooting.}}
 
 
 
==== Desktop compositing is disabled on my system with a modern Nvidia GPU ====
 
 
 
Sometimes, KWin may have settings in it's configuration file ('''kwinrc''') that ''may'' cause a problem on re-activating the 3D desktop '''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 '''~/.kde4/share/config/kwinrc''' file and relogin. The KWin settings will turn to the KDE default ones and the problem should be probably gone.
 
  
 
==== Flickering in fullscreen when compositing is enabled ====
 
==== Flickering in fullscreen when compositing is enabled ====
According to https://fedoraproject.org/wiki/KDE/How_to_reduce_fullscreen_flicker :
 
  
Press Alt+F2 and run:
+
In ''Sytem Settings > Display and Monitor'', uncheck ''Allow applications to block compositing''. This may harm performance.
  
    kwriteconfig --file kwinrc --group Compositing --key UnredirectFullscreen --type bool false
+
==== Screen tearing with Nvidia ====
  
Apply the changes by pressing Alt+F2 and running:  
+
By default, KWin compositing suffers from tearing when used with the proprietary Nvidia driver. To work around this, run {{ic|kwin_x11 --replace}} with the environment variable {{ic|1=export __GL_YIELD="USLEEP"}} stated before:
  
    qdbus org.kde.kwin /KWin reconfigure
+
export __GL_YIELD="USLEEP" && kwin_x11 --replace
  
This forces KWin not to use window unredirection but can affect performance of fullscreen OpenGL applications when desktop effects are enabled. Desktop effects can be suspended to prevent performance issues (press Alt+Shift+F12) before running such applications.  
+
Unlike using the environment variable globally, this does only affect KWin and doesn't reduce CPU performance in other 3D applications. This can also be executed automatically when logging in by creating a simple script and put it into Plasma's {{ic|~/.config/autostart-scripts}} folder.
  
See https://bugs.kde.org/show_bug.cgi?id=177495
+
{{hc|~/.config/autostart-scripts/restartkwinusleep.sh|<nowiki>
 +
(sleep 2s &&
 +
export __GL_YIELD="USLEEP" && kwin_x11 --replace
 +
)
  
As of KDE SC 4.6.0, there is an option in systemsettings -> Desktop Effect -> Advanced -> "Suspend desktop effects for fullscreen windows"
+
</nowiki>}}
Uncheck it would tell kwin to disable unredirect fullscren. (icarus-c)
+
The {{ic|sleep}} argument helps to prevent issues when KWin is restarted too soon after logging in, you might want to adjust the time to your needs. Don't forget to mark the script as executable.
 
 
===Sound problems under KDE===
 
  
====ALSA related problems====
+
==== Plasma cursor sometimes shown incorrecty ====
{{Note| First make sure you have '''alsa-lib''' and '''alsa-utils''' installed.}}
 
  
====="Falling back to default" messages when trying to listen to any sound in KDE=====
+
Create the directory {{ic|~/.icons/default}} and inside a file named {{ic|index.theme}} with the following contents:
When you encounter such messages:
 
:The audio playback device ''<name-of-the-sound-device>'' does not work.
 
:Falling back to default
 
Go to
 
System Settings -> Multimedia -> Phonon
 
and set the device named "'''default'''" above all the other devices in each box you see.
 
  
=====I cannot play mp3 files when using the GStreamer Phonon backend=====
+
{{hc|/home/''archie''/.icons/default/index.theme|2=
That can be solved by installing the GStreamer plugins:
+
[Icon Theme]
  pacman -S gstreamer0.10-plugins
+
Inherits=breeze_cursors
If you still encounter problems, you can try changing the backend used by Phonon by installing phonon-vlc:
+
}}
  pacman -S phonon-vlc
 
A Xine backend is also available (phonon-xine), and it is usable when used with [[PulseAudio]], however it is no longer maintained upstream and is considered deprecated.
 
  
The backend order of preference can be changed in:
+
Execute the following command:
  System Settings -> Multimedia -> Phonon -> Backend (tab)
 
(The order may be changed automatically after installing phonon-vlc/phonon-xine)
 
  
=====No KDE system notifcations sounds with phonon-xine=====
+
$ ln -s /usr/share/icons/breeze_cursors/cursors ~/.icons/default/cursors
If you get no sounds with any system notifcation in general and you are using phonon-xine then you need to install the speex package, an optional dependence of xine-lib.
 
  pacman -S speex
 
  
=====Amarok "waits" before playing any track=====
+
=== Sound problems under Plasma 5 ===
If you have encountered this error, the problem is backend specific.  In order to solve this problem, change Amarok's backend from '''gstreamer''' to '''xine'''.
 
  
=====Phonon with Xine backend and ALSA devices=====
+
==== No sound after suspend ====
If using Phonon with the Xine backend, not all ALSA devices in /etc/asound.conf or ~/.asoundrc (or the default ALSA device) may show or be available.
 
  
Symptoms of the problem:
+
If there is no sound after suspending and if KMix doesn't show audio devices which should be there, restarting plasmeshell and pulseaudio may help:
* ALSA devices do not appear in System Settings > Multimedia > Phonon
 
* speaker-test yields Error -2, "No such file or directory"
 
* aplay yields a file or directory not found error
 
  
[http://phonon.kde.org/cms/1032 Problem and workaround documented on the KDE Phonon Wiki]
+
$ killall plasmashell
 +
$ systemctl --user restart pulseaudio.service
 +
$ plasmashell
  
====OSS4 related problems====
+
Some applications may also need to be restarted in order for sound to play from them again.
If you have OSS4 installed and encounter any problems you should be aware that developers of Kmix are still integrating OSSv4 support. There is an [http://aur.archlinux.org/packages.php?ID=29286 AUR package] that is still experimental.
 
Arch uses phonon with the Gstreamer backend that should work for most applications.  Alternately you could try [[KDE#I_can.27t_play_mp3_files_when_having_Gstreamer_backend_in_Qt_Phonon|phonon with Xine]].
 
  
=== Arch linux specific packaging issues ===
+
==== ALSA related problems ====
Due to some upgrades on the packages or a newer versioned pacman with bugs (pft, like there are any ;) there could be some problems during upgrading. Please read the sections below, if you have a problem.
 
  
===I wanted a minimal installation of KDE. After I installed some packages and logged in KDE, there are no panels===
+
{{Note|First make sure you have {{Pkg|alsa-lib}} and {{Pkg|alsa-utils}} installed.}}
If you wanted a minimal installation of KDE, logged in, heard the login sound but nothing else happened, you may not have installed the Plasma binaries. These are included in
 
  kdebase-workspace
 
Install this package and restart Xorg.
 
  
===I want a fresh installation of KDE for my system. What should I do?===
+
===== "Falling back to default" messages when trying to listen to any sound =====
Just rename the settings directory of KDE (just in case you'll want to go back to your original settings):
 
mv ~/.kde4 ~/.kde4-backup
 
  
===Plasma desktop behaves strangely===
+
When you encounter such messages:
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.
 
 
 
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, I recommend you find the entry on kde-look.org and inform the developer of that widget about the issue (detailing steps to reproduce, etc).
 
 
 
 
 
If you cannot find the problem, but you do not want ''all'' the KDE settings to be lost, do:
 
 
 
  rm -r ~/.kde4/share/config/plasma*
 
 
 
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.
 
 
 
===Hiding partitions===
 
If you wish to prevent your internal partitions from appearing in your file manager, you can create a udev rule, for example {{filename|/etc/udev/rules.d/10-local.rules}}:
 
 
 
KERNEL=="sda[0-9]", ENV{UDISKS_PRESENTATION_HIDE}="1"
 
 
 
The same thing for a certain partition:
 
 
 
KERNEL=="sda1", ENV{UDISKS_PRESENTATION_HIDE}="1"
 
 
 
===Konsole doesn't save commands' history===
 
By default console commands' history is saved only when you type 'exit' in console. When you close Konsole with 'x' in the corner it doesn't happen.
 
To enable autosaving after every command execution you should add following lines into your .bashrc
 
shopt -s histappend
 
[[ "${PROMPT_COMMAND}" ]] && PROMPT_COMMAND="$PROMPT_COMMAND;history -a" || PROMPT_COMMAND="history -a"
 
 
 
==Other KDE projects==
 
 
 
===KDE unstable (snapshot)===
 
 
 
===== Unofficial kde-unstable =====
 
 
 
The member '''ProgDan''' has created a repo where he uploads the testing KDE packages when a new '''upstream snapshot''' is out. You may visit [http://bbs.archlinux.org/viewtopic.php?id=76245 this topic] for more information.
 
 
 
===== Semi-official kde-unstable =====
 
 
 
When KDE is reaching beta or RC milestone, KDE "unstable" packages are uploaded to the [kde-unstable] repo.
 
 
 
You may add it by adding:
 
 
 
[kde-unstable]
 
Include = /etc/pacman.d/mirrorlist
 
 
 
in '''{{Filename|/etc/pacman.conf}}'''
 
 
 
They stay there until KDE is declared stable and passes to [extra].
 
 
 
Make sure [http://wiki.archlinux.org/index.php/KDE#Distro_and_Upstream_bug_report you make bug reports] if you find any issues.
 
 
 
Read [http://wiki.archlinux.org/index.php/DeveloperWiki:KDE#Users this section] in the wiki as well.
 
 
 
===KDE Legacy===
 
  
Along with the official KDE4, the KDE3 code "lives" under the fork project called "Trinity".  
+
The audio playback device ''name_of_the_sound_device'' does not work.
 +
Falling back to default
  
==== Unofficial community repository for KDE 3 ====
+
Go to ''System Settings > Multimedia > Phonon'' and set the device named {{ic|default}} above all the other devices in each box you see.
From the release of KDE 4.x, the developers dropped support for KDE 3.5.x. Nevertheless you can still use KDE 3.5.x through a project called '''kdemod3'''
 
[http://bbs.archlinux.org/viewtopic.php?id=97612 In this thread]. The current rebuild of the unsupported KDEmod3 is based on the Trinity project code (KDE 3.5.12). See Trinity on Arch Linux below.
 
  
{{Warning| KDE 3 is no longer maintained and supported by the KDE developers. The "Trinity KDE" is maintained by the Trinity project commmunity. KDEmod3 is no longer maintained by the Chakra Projects developers. Use KDE 3 on your own risk, regarding any bugs, performance issues or security risks.}}
+
===== MP3 files cannot be played when using the GStreamer Phonon backend =====
  
===Trinity on Arch Linux===
+
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}}.
Trinity SVN is currently KDE 3.5.13. An unofficial effort to provide a working set of PKGBUILDs for Trinity for Arch Linux is in the beginning stages and produces a working KDE 3.5.13 desktop for Arch Linux. Links for binary packages built from the Trinity SVN code as well as the PKGBUILDs are available. For details on this effort, see the Trinity Arch wiki:
+
Then, make sure the backend is preferred via ''System Settings > Multimedia > Backend''.
*'''[https://wiki.archlinux.org/index.php/Trinity Trinity on Arch]'''
 
  
Trinity Stable (KDE 3.5.12) packages are also available as an update to kdemod3. The following repository holds binary packages from the Trinity (3.5.12) code base:
+
=== Inotify folder watch limit ===
  
# Trinity 3.5.12 - i686
+
If you get the following error:
[kdemod3]
 
Server = http://rapinjam.com/beta/lefa/kdemod3/i686/
 
 
# Trinity 3.5.12 - x86_64
 
[kdemod3]
 
Server = http://rapinjam.com/beta/lefa/kdemod3/x86_64/
 
  
* After adding the repository, issue '''&lsquo;pacman -Syu&rsquo;'''. If that fails to trigger the update (or if you don't have kdemod3 installed), then use '''&lsquo;pacman -Sy kdemod3-complete&rsquo;'''
+
KDE Baloo Filewatch service reached the inotify folder watch limit. File changes may be ignored.
  
=== Chakra Project KDEmod ===
+
Then you will need to increase the inotify folder watch limit:
  
The Chakra Project KDEmod (for KDE4) is no longer active and the current Chakra Project's KDE is no longer compatible with Archlinux packages and repos.
+
# echo 524288 > /proc/sys/fs/inotify/max_user_watches
  
If you have installed KDEmod (for KDE4), please remove it and install KDE SC from the official Archlinux repos.
+
To make changes permanent, create {{ic|/etc/sysctl.d/40-max-user-watches.conf}} with:
  
==Bugs==
+
fs.inotify.max_user_watches=524288
  
===Distro and Upstream bug report===
+
=== Freezes when using Automount on a NFS volume  ===
It is preferrable that if you find a minor or serious bug, you should visit [http://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.
 
  
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]].
+
Using [[Fstab#Automount with systemd]] on a [[NFS]] volume may cause freezes, see [https://bugs.kde.org/show_bug.cgi?id=354137 bug report upstream].
  
KDE 4 config files are usually located at
+
=== No Suspend/Hibernate options ===
  
~/.kde4/share/config/
+
If your system is able to suspend or hibernate using systemd but do not have these options shown in KDE, make sure {{Pkg|powerdevil}} is installed.
  
and for app-specific configs
+
=== Problems with saving credentials and persistently occurring KWallet dialogs ===
 +
It is not recommended to turn off the KWallet password saving system in the user settings as it is required to save encrypted credentials like WiFi passphrases for each user. Persistently occuring KWallet dialogs can be the consequence of turning it off.
 +
In case you find the dialogs to unlock the wallet annoying when applications want to access it, you can let the login managers {{ic|SDDM}} and {{ic|LightDM}} unlock the wallet at login automatically, see [[KDE_Wallet#Unlock_KDE_Wallet_automatically_on_login|KDE Wallet]]. The first wallet needs to be generated by KWallet (and not user-generated) in order to be usable for system program credentials.
 +
In case you want the wallet credentials not to be opened in memory for every application, you can restrict applications from accessing it with {{Pkg|kwalletmanager}} in the KWallet settings.
 +
If you do not care for credential encryption at all, you can simply leave the password forms blank when KWallet asks for the password while creating a wallet. In this case, applications can access passwords without having to unlock the wallet first.
  
~/.kde4/share/apps/
+
== See also ==
  
==External Links==
+
* [https://www.kde.org/ KDE homepage]
* [http://www.kde.org KDE Homepage]
+
* [https://bugs.kde.org/ KDE bug tracker]
* [http://bugs.kde.org KDE Bug Tracker]
+
* [https://blog.martin-graesslin.com/blog/kategorien/kde/ Martin Graesslin's blog]
* [http://bugs.archlinux.org Arch Linux Bug Tracker]
 
* [http://websvn.kde.org KDE WebSVN]
 

Latest revision as of 21:41, 13 December 2017

KDE is a software project currently comprising of a desktop environment known as Plasma, a collection of libraries and frameworks (KDE Frameworks) and several applications (KDE Applications) as well. KDE upstream has a well maintained UserBase wiki. Detailed information about most KDE applications can be found there.

Contents

Installation

Plasma

Before installing Plasma, make sure you have a working Xorg installation on your system.

Install the plasma-meta meta-package or the plasma group. For differences between plasma-meta and plasma reference Creating packages#Meta packages and groups. Alternatively, for a more minimal Plasma installation, install the plasma-desktop package.

To enable support for Wayland in Plasma, also install the plasma-wayland-session package.

KDE applications and language packs

To install the full set of KDE Applications, install the kde-applications group or the kde-applications-meta meta-package. Note that this will only install applications, it will not install any version of Plasma.

Most KDE packages ship their own translations. The exception is KDE4-based packages from kde-applications. If you need language files for these packages, install kde-l10n-yourlanguagehere (e.g. kde-l10n-de for the German language). For a full list of available languages see the kde-l10n split package.

Unstable releases

See Official repositories#kde-unstable

Starting Plasma

Note: Although it is possible to launch Plasma under Wayland, there are some missing features and known problems as of Plasma 5.11. See the Plasma 5.11 Errata for a list of issues and the Plasma on Wayland workboard for the current state of development. Use Xorg for the most complete and stable experience.

Plasma can be started either using a display manager, or from the console.

Using a display manager

Note: The NVIDIA proprietary driver implementation for Wayland requires EGLStreams. KDE have not implemented EGLStreams in their Wayland implementation. The following workarounds are available:
  • Using the Nouveau driver.
  • Using the (default) Xorg session.

From the console

To start Plasma with xinit/startx, append exec startkde to your .xinitrc file. If you want to start Xorg at login, please see Start X at login. To start a Plasma on Wayland session from a console, run startplasmacompositor.

Configuration

Most settings for KDE applications are stored in ~/.config, but some older applications may use ~/.kde4. However, configuring KDE is primarily done through the System Settings application. It can be started from a terminal by executing systemsettings5.

Some Frameworks 5 applications can use KDElibs 4 configuration, after moving the configuration files to the new location. Examples are:

  • Konsole profiles from ~/.kde4/share/apps/konsole to ~/.local/share/konsole/
  • Application appearance from ~/.kde4/share/config/kdeglobals to ~/.config/kdeglobals

Personalization

Plasma desktop

Themes

Plasma themes define the look of panels and plasmoids. For easy system-wide installation, some themes are available in both the official repositories and the AUR.

The easiest way to install themes is by going through the System Settings > Workspace Theme > Desktop Theme > Get new Themes.

This will present a frontend for the KDE-Store that allows you to install, uninstall, or update third-party plasmoid scripts.

Splash and Lock screens are currently unavailable. To customize these screens, you have to modify the original theme found in /usr/share/plasma/look-and-feel/. See this thread on the Kubuntu forums.

Note that the SDDM login screen is not part of this theme.

Qt and GTK+ Applications Appearance
Tip: For Qt and GTK theme consistency, see Uniform look for Qt and GTK applications.
Qt4

For Qt4 applications to have a consistent appearance, there are two options:

Install breeze-kde4 and then pick Breeze as GUI Style in qtconfig-qt4; or install breeze-gtk and pick GTK+ as GUI Style.

GTK+

The recommended theme for a pleasant appearance in GTK+ applications is breeze-gtk or gnome-breeze-gitAUR, a GTK+ theme designed to mimic the appearance of Plasma's Breeze theme. Install kde-gtk-config and select the installed GTK-theme for GTK2/GTK3-Theme in System Settings > Application Style > GNOME Application Style.

In some themes, tooltips in GTK+ applications have white text on white backgrounds making it difficult to read. To change the colors in GTK2 applications, find the section for tooltips in the .gtkrc-2.0 file and change it. For GTK3 application two files need to be changed, gtk.css and settings.ini. It might also help to uncheck the option to Apply colors to non-Qt applications under System Settings > Colors.

Some GTK2 programs like vuescan-binAUR still look hardly usable due to invisible checkboxes with the Breeze or Adwaita skin in a Plasma session. To workaround this, install and select e.g. the Numix-Frost-Light skin of the numix-frost-themesAUR under System Settings > Application Style > GNOME Application Style (GTK) > Select a GTK2 Theme:. Numix-Frost-Light looks similar to Breeze.

Widgets

Plasmoids are little scripted (plasmoid scripts) or coded (plasmoid binaries) KDE applications designed to enhance the functionality of your desktop.

The easiest way to install plasmoid scripts is by right-clicking onto a panel or the desktop and choosing Add Widgets > Get new Widgets > Download Widgets. This will present a nice frontend for https://store.kde.org/ that allows you to install, uninstall, or update third-party plasmoid scripts with literally just one click.

Many Plasmoid binaries are available from the AUR.

Sound applet in the system tray

Install plasma-pa or kmix (start Kmix from the Application Launcher). plasma-pa is now installed by default with plasma, no further configuration needed.

Note: To adjust the step size of volume increments/decrements, add e.g. VolumePercentageStep=1 in the [Global] section of ~/.config/kmixrc.
Disable panel shadow

As the Plasma panel is on top of other windows, its shadow is drawn over them. [1] To disable this behaviour without impacting other shadows, install xorg-xprop and run:

$ xprop -remove _KDE_NET_WM_SHADOW

then select the panel with the plus-sized cursor. [2] For automation, install xorg-xwininfo and create the following script:

/usr/local/bin/kde-no-shadow
#!/bin/bash
for WID in $(xwininfo -root -tree | sed '/"Plasma": ("plasmashell" "plasmashell")/!d; s/^  *\([^ ]*\) .*/\1/g'); do
   xprop -id $WID -remove _KDE_NET_WM_SHADOW
done

Set execution permissions for the script:

# chmod 755 /usr/local/bin/kde-no-shadow

The script can be run on login with Add Script in Autostart:

$ kcmshell5 autostart

Window decorations

Window decorations can be changed in System Settings > Application Style > Window Decorations.

There you can also directly download and install more themes with one click, and some are available in the AUR.

Icon themes

Icon themes can be installed and changed on System Settings > Icons.

Note: Although all modern Linux desktops share the same icon theme format, desktops like GNOME use fewer icons (esp. in menus and toolbars). Themes developed for such desktops usually lack icons required by Plasma and KDE apps. It is recommended to install Plasma compatible icon themes instead.

Fonts

Fonts in a Plasma session look poor

Try installing the ttf-dejavu and ttf-liberation packages.

After the installation, be sure to log out and back in. You should not have to modify anything in System Settings > Fonts. If you are using qt5ct, the settings in Qt5 Configuration Tool may override the font settings in System Settings.

If you have personally set up how your Fonts render, be aware that System Settings may alter their appearance. When you go System Settings > Fonts System Settings will likely alter your font configuration file (fonts.conf).

There is no way to prevent this, but, if you set the values to match your 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.

Fonts are huge or seem disproportional

Try to force font DPI to 96 in System Settings > Fonts.

If that does not work, try setting the DPI directly in your Xorg configuration as documented in Xorg#Setting DPI manually.

Space efficiency

The Plasma Netbook shell has been dropped from Plasma 5, see the following KDE forum post However, you can achieve something similar by editing the file ~/.config/kwinrc adding BorderlessMaximizedWindows=true in the [Windows] section.

Thumbnail generation

To allow thumbnail generation for media or document files on the desktop and in Dolphin, install kdegraphics-thumbnailers, ffmpegthumbs and kde-thumbnailer-odfAUR.

Then enable the thumbnail categories for the desktop via right click on the desktop background > Configure Desktop > Icons > More Preview Options....

In Dolphin, navigate to Control > General > Previews.

Printing

Tip: Use the CUPS web interface for faster configuration. Printers configured in this way can be used in KDE applications.

You can also configure printers in System Settings > Printers. To use this method, you must first install print-manager and cups. See CUPS#Configuration.

Samba/Windows support

If you want to have access to Windows services, install Samba (package samba).

The Dolphin share functionality requires the package kdenetwork-filesharing and usershares, which the stock smb.conf does not have enabled. Instructions to add them are in Samba#Creating usershare path, after which sharing in Dolphin should work out of the box after restarting Samba.

Plasma's abilities to access SMB shares are limited, though. Writing to Windows shares is problematic and opening files from such shares, e.g. large videos, makes Plasma copying the whole file to the local system first. To workaround this, you can install a GTK based file browser like thunar with gvfs and gvfs-smb (and gnome-keyring for saving login credentials) to access SMB shares in a more able way. Another possible workaround is to mount a Samba share via cifs-utils to make it look to Plasma like if the SMB share was just a normal local folder and thus can be accessed normally. The mount command could look like the following for write access to a public share:

# mount -t cifs -o username=*,password=*,uid=1000,gid=1000,file_mode=0660,dir_mode=0770 //networkhost/share/ /home/user/localmountpoint/

Make it permanent:

/etc/fstab
//networkhost/share/ /home/user/localmountpoint/ cifs defaults,username=*,password=*,uid=1000,gid=1000,file_mode=0660,dir_mode=0770 0 2

It might be necessary to append .local to the hostname. For some NAS devices it might also be necessary to append vers=1.0 to the argument line to enforce SMB 1.0 compatibility.

An easier solution is to use samba-mounter-gitAUR, which offers basically the same functionality via an easy to use option located at System Settings > Network Drivers.

KDE Desktop activities

KDE Desktop Activities are special workspaces where you can select specific settings for each activity that apply only when you are using said activity.

Power saving

Install powerdevil for 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).

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: Regarding the note below, it might be that the problem is the logind setting LidSwitchIgnoreInhibited which defaults to yes. [3] (Discuss in Talk:KDE#)
Note: Powerdevil may not inhibit all logind settings (such as the lid close action for laptops). In these cases, the logind setting itself will need to be changed - see Power management#Power management with systemd.

Autostarting applications

Plasma can autostart applications and run scripts on startup and shutdown. To autostart an application, navigate to System Settings > Startup and Shutdown > Autostart and add the program or shell script of your choice. For applications, a .desktop file will be created, for shell scripts, a symlink will be created.

Note:
  • Programs can be autostarted on login only, whilst shell scripts can also be run on shutdown or even before Plasma itself starts.
  • Shell scripts will only be run if they are marked executable.

Place Desktop entries (i.e. .desktop files) here:

~/.config/autostart
for starting applications at login.

Place or symlink shell scripts in one of the following directories:

~/.config/plasma-workspace/env
for executing scripts at login before launching Plasma.
~/.config/autostart-scripts
for executing scripts at login.
~/.config/plasma-workspace/shutdown
for executing scripts on shutdown.

Phonon

From Wikipedia:

“Phonon is the multimedia API provided by KDE and is the standard abstraction for handling multimedia streams within KDE software and also used by several Qt applications.

Phonon was originally created to allow KDE and Qt software to be independent of any single multimedia framework such as GStreamer or xine and to provide a stable API for a major version's lifetime.”

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).

Which backend should I choose?

You can choose between backends based on GStreamer and VLC – each available in versions for Qt4 applications and Qt5 applications (phonon-qt4-gstreamer, phonon-qt5-gstreamerphonon-qt4-vlc, phonon-qt5-vlc).

Upstream prefers VLC but prominent Linux distributions (Kubuntu and Fedora-KDE for example) prefer GStreamer because that allows them to easily leave out patented MPEG codecs from the default installation. Both backends have a slightly different features set.

In the past other backends were developed as well but are no longer maintained and their AUR packages have been deleted.

Note:
  • Multiple backends can be installed at once and prioritized at System Settings > Multimedia > Backend.
  • According to the KDE forums, the VLC backend lacks support for ReplayGain.
  • If you choose the vlc backend, you may experience crashes every time kde wants to send you a audible warning (and in quite a number of other cases as well, see [4])
  • A possible fix is to run
# /usr/lib/vlc/vlc-cache-gen -f /usr/lib/vlc/plugins

Applications

The KDE project provides a suite of applications that integrate with the Plasma desktop. See the kde-applications group for a full listing of the available applications. Also see Category:KDE for related KDE application pages.

Aside from the programs provided in KDE Applications, there are many other applications available that can complement the Plasma desktop. Some of these are discussed below.

System administration

Terminate Xorg server through KDE System Settings

Navigate to the submenu System Settings > Input Devices > Keyboard > Advanced (tab) > "Key Sequence to kill the X server" and ensure that the checkbox is ticked.

KCM

KCM stands for KConfig Module. KCMs can help you configure your system by providing interfaces in System Settings, or through the command line with kcmshell5.

  • kde-gtk-config — GTK2 and GTK3 Configurator for KDE.
https://cgit.kde.org/kde-gtk-config.git || kde-gtk-config
  • KCM Qt Graphics System — This KCM allows you to easily configure the standard Qt graphics system.
https://www.linux-apps.com/p/1127857/ || kcm-qt-graphicssystemAUR
https://www.linux-apps.com/p/1127851/ || kcm-ufwAUR
  • System policies — Set of configuration modules which allows administrator to change PolicyKit settings.
https://cgit.kde.org/polkit-kde-kcmodules-1.git || kcm-polkit-kde-gitAUR
  • wacom tablet — KDE GUI for the Wacom Linux Drivers.
https://www.linux-apps.com/p/1127862/ || kcm-wacomtabletAUR
  • Kcmsystemd — systemd control module for KDE.
https://github.com/rthomsen/kcmsystemd || systemd-kcm

More KCMs can be found at linux-apps.com.

Desktop search

KDE implements desktop search with a software called Baloo, a file indexing and searching solution.

Baloo

Using and configuring Baloo

In order to search using Baloo on the Plasma desktop, start krunner (default keyboard shortcut ALT+F2) and type in your query. Within Dolphin press CTRL+F.

By default the Desktop Search KCM exposes only two options: A panel to blacklist folders and a way to disable it with one click.

Alternatively you can edit your ~/.config/baloofilerc file (info). Additionally the balooctl process can also be used. In order to disable Baloo run balooctl stop and balooctl disable.

Once you added additional folders to the blacklist or disabled Baloo entirely, a process named baloo_file_cleaner removes all unneeded index files automatically. They are stored under ~/.local/share/baloo/.

How do I index a removable device?

By default every removable device is blacklisted. You just have to remove your device from the blacklist in the KCM panel.

Web browsers

  • Konqueror — Part of the KDE project, supports two rendering engines – KHTML and the Chromium-based Qt WebEngine.
https://konqueror.org/ || konqueror
  • QupZilla — A Qt web browser with Plasma integration features. It uses Qt WebEngine.
https://www.qupzilla.com/ || qupzilla
  • Chromium — Chromium and its proprietary variant Google Chrome have limited Plasma integration. They can use KWallet and KDE Open/Save windows.
https://www.chromium.org/ || chromium
https://mozilla.org/firefox || firefox

PIM

KDE offers its own stack for personal information management. This includes emails, contacts, calendar, etc. To install all the PIM packages, you could use the meta-package kde-meta-kdepim.

Akonadi

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.

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).

Installation

Install akonadi. For additional addons, install kdepim-addons. For EWS support, install akonadi-ews-gitAUR.

Note: If you wish to use a database engine other than MariaDB/MySQL, then when installing the akonadi package, use the following command to skip installing the mariadb dependencies:
# pacman -S akonadi --assume-installed mariadb
Disabling Akonadi

See this section in the KDE userbase.

Database configuration
MariaDB/MySQL (using ZFS)

If your home directory is on a ZFS pool, you will need to create ~/.config/akonadi/mysql-local.conf with the following contents:

[mysqld]
innodb_use_native_aio = 0

Otherwise you will get the OS error 22

PostgreSQL

Install and setup PostgreSQL. Make sure postgresql.service is started.

Edit Akonadi configuration file so that it has the following contents:

~/.config/akonadi/akonadiserverrc
[%General]
Driver=QPSQL

[QPSQL]
Host=/run/postgresql/
InitDbPath=/usr/bin/initdb
Name=akonadi
Options=
Password=
Port=5432
ServerPath=/usr/bin/pg_ctl
StartServer=true
User=postgres
Note: If your PostgreSQL database username, password, and port differ from postgres, (nothing), and 5432, then make sure you respectively change the configuration options, User=, Password=, and Port=.

Start Akonadi with akonadictl start, and check its status: akonadictl status.

SQLite

Edit Akonadi configuration file to match the configuration below:

~/.config/akonadi/akonadiserverrc
[%General]
Driver=QSQLITE3

[QSQLITE3]
Name=/home/username/.local/share/akonadi/akonadi.db

KDE Telepathy

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.

To install all Telepathy protocols, install the telepathy group. To use the KDE Telepathy client, install the telepathy-kde-meta package that includes all the packages contained in the telepathy-kde group.

Use Telegram with KDE Telepathy

Telegram protocol is available using telepathy-haze, installing telegram-purpleAUR or telegram-purple-gitAUR and telepathy-morse-gitAUR. The username is the Telegram account telephone number (complete with the national prefix +xx, e.g. +49 for Germany).

The configuration through 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 (~/.local/share/telepathy/mission-control/accounts.cfg) after the account creation (if the quotes are not removed after, an authentication error should rise).

Note: 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.

Integrate Android

KDE Connect provides several features for you:

  • Share files and URLs to/from KDE from/to any app, without wires.
  • Touchpad emulation: Use your phone screen as your computer's touchpad.
  • Notifications sync (4.3+): Read your Android notifications from the desktop.
  • Shared clipboard: copy and paste between your phone and your computer.
  • Multimedia remote control: Use your phone as a remote for Linux media players.
  • WiFi connection: no usb wire or bluetooth needed.
  • RSA Encryption: your information is safe.

You will need to install KDE Connect both on your computer and on your Android. For PC side, install kdeconnect package. For Android side, install KDE Connect from Google Play or from F-Droid.

It is possible to use KDE Connect even if you do not use the Plasma desktop. For desktop environments that use AppIndicators, such as Unity, install indicator-kdeconnectAUR package as well.

Tips and tricks

Using an alternative window manager

The component chooser settings in Plasma does not allow changing the window manager anymore. [5] In order to change the window manager used you need to set the KDEWM environment variable before KDE startup. [6] To do that you can create a script called set_window_manager.sh in ~/.config/plasma-workspace/env and export the KDEWM variable there. For example to use the i3 window manager :

~/.config/plasma-workspace/env/set_window_manager.sh
export KDEWM=/usr/bin/i3

And then make it executable :

$ chmod +x ~/.config/plasma-workspace/env/set_window_manager.sh

KDE/Openbox session

The openbox package provides a session for using KDE with Openbox. To make use of this session, select KDE/Openbox from the display manager menu.

For those starting the session manually, add the following line to your .xinitrc file:

exec openbox-kde-session

Re-enabling compositing effects

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.

Configuring monitor resolution / multiple monitors

To enable display resolution management and multiple monitors in Plasma, install kscreen. This adds the additional options to Sytem Settings > Display and Monitor.

Disable opening application launcher with Super key (Windows key)

To disable this feature you currently can run the following command:

$ kwriteconfig5 --file kwinrc --group ModifierOnlyShortcuts --key Meta ""

Troubleshooting

Configuration related

Many problems in KDE are related to configuration.

Plasma desktop behaves strangely

Plasma problems are usually caused by unstable Plasma widgets (colloquially called plasmoids) or Plasma themes. First, find which was the last widget or theme you had installed and disable it or uninstall it.

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 (https://bugs.kde.org/) only if it is an official widget. If it is not, it is recommended you find the entry on https://store.kde.org/ and inform the developer of that widget about the problem (detailing steps to reproduce, etc).

If you cannot find the problem, but you do not want all the settings to be lost, navigate to ~/.config:

$ for j in plasma*; do mv -- "$j" "${j%}.bak"; done

This command will rename all Plasma related configs to *.bak (e.g. plasmarc.bak) of your user and when you will relogin into Plasma, you will have the default settings back. To undo that action, remove the .bak file extension. If you already have *.bak files, rename, move, or delete them first. It is highly recommended that you create regular backups anyway. See Synchronization and backup programs for a list of possible solutions.

Clean cache to resolve upgrade problems

The 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 music. This solution can also resolve problems with KDE and Qt programmes looking bad following upgrade.

Rebuild your cache with the following commands:

$ rm ~/.config/Trolltech.conf
$ kbuildsycoca5 --noincremental

Clean akonadi configuration to fix KMail

First, make sure that KMail is not running. Then backup configuration:

$ cp -a ~/.local/share/akonadi ~/.local/share/akonadi-old
$ cp -a ~/.config/akonadi ~/.config/akonadi-old

Start SystemSettings > Personal and remove all the resources. Go back to Dolphin and remove the original ~/.local/share/akonadi and ~/.config/akonadi - the copies you made ensure that you can back-track if necessary.

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.

Fix empty IMAP inbox

For some IMAP accounts, kmail will show the inbox as a container with all other folders of this account inside. Kmail does not show messages in the inbox container but in all other subfolders, see KDE Bug 284172. To solve this problem simply disable the server side subscribition in the kmail account settings.

Getting current state of KWin for support and debug purposes

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 Martin's blog.

$ qdbus org.kde.KWin /KWin supportInformation

KF5/Qt5 applications do not display icons in i3/fvwm/awesome

See Qt#Configuration of Qt5 apps under environments other than KDE Plasma.

Graphical related problems

Plasma keeps crashing with legacy Nvidia

This is caused by a bug in Plasma when using the Nvidia-304xx driver. Rather than disabling compositing, create a file kwin.sh in ~/.config/plasma-workspace/env/ with the following contents:

#!/bin/sh
export KWIN_EXPLICIT_SYNC=0

Then go to System Settings > Startup and Shutdown > Autostart and Check/Add the script as a pre-KDE startup file.

Applications do not refresh properly

If you use 3D-accelerated composition with Intel, you might find that the Plasma panel and other applications do not refresh properly (stay frozen). Some Intel drivers have problems with EGL. Go to System Settings > Display and Monitor > Compositor. Set OpenGL interface to OpenGL 3.1. If that does not work, see Intel graphics#SNA issues for alternative solutions.

Bad performance

Make sure you have the proper driver for your GPU installed. See Xorg#Driver installation for more information. If you have an older card, it might help to #Disable desktop effects manually or automatically for defined applications or #Disable compositing.

Disable desktop effects manually or automatically for defined applications

Plasma has desktop effects enabled by default and e.g. not every game will disable them automatically. You can disable desktop effects in System Settings > Desktop Effects and you can toggle desktop effects with Alt+Shift+F12. Additionally, you can create custom KWin rules to automatically disable/enable compositing when a certain application/window starts under System Settings > Window Management > Window Rules.

Disable compositing

In Sytem Settings > Display and Monitor, uncheck Enable compositor on startup and restart Plasma.

Flickering in fullscreen when compositing is enabled

In Sytem Settings > Display and Monitor, uncheck Allow applications to block compositing. This may harm performance.

Screen tearing with Nvidia

By default, KWin compositing suffers from tearing when used with the proprietary Nvidia driver. To work around this, run kwin_x11 --replace with the environment variable export __GL_YIELD="USLEEP" stated before:

export __GL_YIELD="USLEEP" && kwin_x11 --replace

Unlike using the environment variable globally, this does only affect KWin and doesn't reduce CPU performance in other 3D applications. This can also be executed automatically when logging in by creating a simple script and put it into Plasma's ~/.config/autostart-scripts folder.

~/.config/autostart-scripts/restartkwinusleep.sh
(sleep 2s &&
export __GL_YIELD="USLEEP" && kwin_x11 --replace
)

The sleep argument helps to prevent issues when KWin is restarted too soon after logging in, you might want to adjust the time to your needs. Don't forget to mark the script as executable.

Plasma cursor sometimes shown incorrecty

Create the directory ~/.icons/default and inside a file named index.theme with the following contents:

/home/archie/.icons/default/index.theme
[Icon Theme]
Inherits=breeze_cursors

Execute the following command:

$ ln -s /usr/share/icons/breeze_cursors/cursors ~/.icons/default/cursors

Sound problems under Plasma 5

No sound after suspend

If there is no sound after suspending and if KMix doesn't show audio devices which should be there, restarting plasmeshell and pulseaudio may help:

$ killall plasmashell
$ systemctl --user restart pulseaudio.service
$ plasmashell

Some applications may also need to be restarted in order for sound to play from them again.

ALSA related problems

Note: First make sure you have alsa-lib and alsa-utils installed.
"Falling back to default" messages when trying to listen to any sound

When you encounter such messages:

The audio playback device name_of_the_sound_device does not work.
Falling back to default

Go to System Settings > Multimedia > Phonon and set the device named default above all the other devices in each box you see.

MP3 files cannot be played when using the GStreamer Phonon backend

This can be solved by installing the GStreamer libav plugin (package gst-libav). If you still encounter problems, you can try changing the Phonon backend used by installing another such as phonon-qt4-vlc or phonon-qt5-vlc. Then, make sure the backend is preferred via System Settings > Multimedia > Backend.

Inotify folder watch limit

If you get the following error:

KDE Baloo Filewatch service reached the inotify folder watch limit. File changes may be ignored.

Then you will need to increase the inotify folder watch limit:

# echo 524288 > /proc/sys/fs/inotify/max_user_watches

To make changes permanent, create /etc/sysctl.d/40-max-user-watches.conf with:

fs.inotify.max_user_watches=524288

Freezes when using Automount on a NFS volume

Using Fstab#Automount with systemd on a NFS volume may cause freezes, see bug report upstream.

No Suspend/Hibernate options

If your system is able to suspend or hibernate using systemd but do not have these options shown in KDE, make sure powerdevil is installed.

Problems with saving credentials and persistently occurring KWallet dialogs

It is not recommended to turn off the KWallet password saving system in the user settings as it is required to save encrypted credentials like WiFi passphrases for each user. Persistently occuring KWallet dialogs can be the consequence of turning it off. In case you find the dialogs to unlock the wallet annoying when applications want to access it, you can let the login managers SDDM and LightDM unlock the wallet at login automatically, see KDE Wallet. The first wallet needs to be generated by KWallet (and not user-generated) in order to be usable for system program credentials. In case you want the wallet credentials not to be opened in memory for every application, you can restrict applications from accessing it with kwalletmanager in the KWallet settings. If you do not care for credential encryption at all, you can simply leave the password forms blank when KWallet asks for the password while creating a wallet. In this case, applications can access passwords without having to unlock the wallet first.

See also