Difference between revisions of "KDE"

From ArchWiki
Jump to navigation Jump to search
(tip about slow dolphin / file dialogs.)
m (Reverted edits by Lahwaacz.bot (talk) to last revision by SlavMetal)
Tag: Rollback
 
(862 intermediate revisions by more than 100 users not shown)
Line 1: Line 1:
[[Category:KDE| ]]
+
[[Category:KDE]]
 +
[[ar:KDE]]
 
[[cs:KDE]]
 
[[cs:KDE]]
[[de:KDE]]
+
[[de:Plasma]]
 
[[es:KDE]]
 
[[es:KDE]]
 +
[[fa:KDE]]
 
[[fr:KDE]]
 
[[fr:KDE]]
 
[[it:KDE]]
 
[[it:KDE]]
 
[[ja:KDE]]
 
[[ja:KDE]]
 
[[pl:KDE]]
 
[[pl:KDE]]
 +
[[pt:KDE]]
 
[[ru:KDE]]
 
[[ru:KDE]]
[[tr:KDE_Masaüstü_Ortamı]]
+
[[zh-hans:KDE]]
[[zh-CN:KDE]]
+
[[zh-hant:KDE]]
[[zh-TW:KDE]]
+
{{Related articles start}}
{{Article summary start}}
+
{{Related|Desktop environment}}
{{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.}}
+
{{Related|Display manager}}
{{Article summary text|KDE uses the [[Qt]] toolkit.}}
+
{{Related|Window manager}}
{{Article summary heading|Overview}}
+
{{Related|Qt}}
{{Article summary text|{{Graphical user interface overview}}}}
+
{{Related|SDDM}}
{{Article summary heading|Related}}
+
{{Related|Dolphin}}
{{Article summary wiki|Plasma}}
+
{{Related|KDE Wallet}}
{{Article summary wiki|Qt}}
+
{{Related|KDevelop}}
{{Article summary wiki|KDM}}
+
{{Related|Trinity}}
{{Article summary wiki|KDevelop 4}}
+
{{Related|Uniform Look for Qt and GTK Applications}}
{{Article summary wiki|Uniform Look for Qt and GTK Applications}}
+
{{Related articles end}}
{{Article summary end}}
 
  
From [http://www.kde.org/community/whatiskde/softwarecompilation.php KDE - KDE Software Compilation]:
+
KDE is a software project currently comprising 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.
  
:''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 systems. 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.''
+
== Installation ==
 +
 
 +
=== Plasma ===
 +
 
 +
Before installing Plasma, make sure you have a working [[Xorg]] installation on your system.
  
:''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.''
+
[[Install]] the {{Pkg|plasma-meta}} meta-package or the {{Grp|plasma}} group. For differences between {{Pkg|plasma-meta}} and {{Grp|plasma}} reference [[Package group]]. Alternatively, for a more minimal Plasma installation, install the {{Pkg|plasma-desktop}} package.
  
From [http://www.kde.org/download/ KDE - Getting KDE Software]:
+
To enable support for [[Wayland]] in Plasma, also install the {{Pkg|plasma-wayland-session}} 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.''
+
=== KDE applications ===
  
The KDE upstream has a well maintained [http://userbase.kde.org/ UserBase wiki]. Users can get detailed information about most KDE applications there.
+
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.
  
== Overview ==
+
=== Unstable releases ===
  
'''KDE 4.10''' Software Compilation is the current major [http://kde.org/announcements/ release of KDE]. Important hints for upgraders:
+
See [[Official repositories#kde-unstable]]
* Always check if your mirror is '''up to date'''.
 
* '''Do not force an update using pacman --force'''. 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.
 
  
== Installation ==
+
== Starting Plasma ==
 +
{{Note|Although it is possible to launch Plasma under [[Wayland]], there are some missing features and known problems. See [https://community.kde.org/Plasma/Wayland_Showstoppers Wayland Showstoppers] 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.}}
  
KDE 4.x is '''modular'''. You can install an entire set of packages or only install your preferred KDE applications.
+
Plasma can be started either using a [[display manager]], or from the console.
  
{{Note|If you do not have [[Xorg#Installation|Xorg]] installed on your system, be sure to install it before KDE.}}
+
=== Using a display manager ===
  
=== Full install ===
+
* 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]].
  
[[pacman|Install]] {{Grp|kde}} or {{Grp|kde-meta}} available in the [[official repositories]]. For differences between {{Grp|kde}} and {{Grp|kde-meta}} see the [[KDE Packages]] article.
+
=== From the console ===
  
=== Minimal install ===
+
* To start Plasma with [[xinit|xinit/startx]], append {{ic|exec startplasma-x11}} 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|1=XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland}}.[https://community.kde.org/KWin/Wayland#Start_a_Plasma_session_on_Wayland]
  
If you want to have a minimal installation of the KDE SC, install:
+
== Configuration ==
* {{Grp|kdebase}}
 
* {{Pkg|phonon-vlc}} or {{Pkg|phonon-gstreamer}} as phonon backend
 
  
=== Language pack ===
+
Most settings for KDE applications are stored in {{ic|~/.config/}}. However, configuring KDE is primarily done through the '''System Settings''' application. It can be started from a terminal by executing {{ic|systemsettings5}}.
  
If you need language files, install {{ic|kde-l10n-yourlanguagehere}} (e.g. {{Pkg|kde-l10n-de}} for the German language).
+
=== Personalization ===
  
For a full list of available languages see [https://www.archlinux.org/packages/extra/any/kde-l10n/ this link].
+
==== Plasma desktop ====
  
== Starting KDE ==
+
===== Themes =====
  
Starting KDE depends on your preferences. Basically there are two ways of starting KDE. Using '''KDM''' or '''xinitrc'''.
+
[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?K=plasma+theme AUR].
  
=== Using KDM (KDE Display Manager)===
+
Plasma themes can also be installed through ''System Settings > Workspace Theme > Plasma Theme > Get new themes from the Internet''.
  
''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.''
+
The [https://store.kde.org/ KDE-Store] offers more Plasma customization's, like [[SDDM]] themes and splash-screens.
  
[[Daemons|Enable/start]] {{ic|kdm.service}}.
+
====== Qt and GTK Applications Appearance ======
  
=== Using xinitrc ===
+
{{Tip|For Qt and GTK theme consistency, see [[Uniform look for Qt and GTK applications]].}}
''The meaning and usage of '''xinitrc''' is very well described [[Xinitrc|here]].
 
  
{{Pkg|kdebase-workspace}} provides startkde. Make sure it is installed. Then edit {{ic|~/.xinitrc}}, uncomment:
+
; Qt4
exec startkde
+
Breeze is not directly available for Qt4 since it cannot be built without KDE 4 packages, which have been dropped from the extra repository in August 2018 ({{Bug|59784}}). However you can install {{Pkg|breeze-gtk}} and pick GTK as GUI Style by running {{ic|qtconfig-qt4}}.
  
After a reboot and/or log-in, each execution of Xorg ('''startx''' or '''xinit''') will start KDE automatically.
+
; GTK
  
{{Note|If you want to start Xorg at boot, please read [[Start X at Login]] article.}}
+
The recommended theme for a pleasant appearance in GTK applications is {{Pkg|breeze-gtk}}, a GTK theme designed to mimic the appearance of Plasma's Breeze theme.
 +
Install {{Pkg|kde-gtk-config}} (part of the {{grp|plasma}} group) and select {{ic|Breeze}} or {{ic|Breeze-Dark}} as the GTK2/GTK3 theme in ''System Settings > Application Style > GNOME/GTK Application Style''.
  
== Configuration ==
+
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}}.
 +
 
 +
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/GTK Application Style'' > ''GTK2 Theme:''. Numix-Frost-Light looks similar to Breeze.
  
All KDE configuration is saved in the {{ic|~/.kde4}} folder. If your KDE is giving you a lot of trouble or if you ever want a fresh installation of KDE, just back this folder up and restart your X session. KDE will re-create this folder with all the default config files. If you want very fine-grained control over your KDE programs, then you may want to edit the files in this folder.
+
===== Faces =====
  
However, configuring KDE is primarily done in ''''System Settings''''. There are also a few other options available for the desktop with ''''Default Desktop Settings'''' when you right click the desktop.
+
Plasma and [[SDDM]] will both use a PNG file found at {{ic|~/.face.icon}} as a user's avatar. To configure with a graphical interface, you can use ''System Settings > Accounts Details > User Manager'', which may first need to be [[install]]ed (see the {{Pkg|user-manager}} package). The default icon can be found in {{ic|/usr/share/sddm/faces/}}.
  
For other personalization options not covered below such as activities, different wallpapers on one cube, etc please refer to the [[Plasma]] wiki page.
+
===== Widgets =====
  
=== Personalization ===
+
Plasmoids are little scripted (plasmoid scripts) or coded (plasmoid binaries) KDE applications designed to enhance the functionality of your desktop.
  
How to set up the KDE desktop to your personal style; use different Plasma themes, window decorations and icon themes.  
+
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 New Plasma 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.
  
==== Plasma desktop ====
+
Many Plasmoid binaries are available from the [https://aur.archlinux.org/packages.php?K=plasmoid 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".
+
===== Sound applet in the system tray =====
  
===== Themes =====
+
[[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.
  
[http://kde-look.org/index.php?xcontentmode=76 Plasma themes] can be installed through the Desktop Settings control panel. Plasma themes define how your panels and plasmoids look like. If you like to have them installed system-wide, themes can be found in both the official repositories and [https://aur.archlinux.org/packages.php?O=0&K=plasmatheme&do_Search=Go AUR].
+
{{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}}.}}
  
===== Widgets =====
+
===== Disable panel shadow =====
  
Plasmoids are little scripted or coded KDE apps that enhance the functionality of your desktop. There are two kinds, plasmoid scripts and plasmoid binaries.
+
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:
  
Plasmoid binaries must be installed using PKGBUILDS from [https://aur.archlinux.org/packages.php?O=0&K=plasmoid&do_Search=Go&PP=25&SO=d&SB=v AUR]. Or write your own PKGBUILD.
+
  $ xprop -remove _KDE_NET_WM_SHADOW
  
The easiest way to install plasmoid scripts is by right-clicking onto a panel or the desktop:
+
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:
  
  Add Widgets > Get new Widgets > Download Widgets
+
{{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>}}
  
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.
+
Set execution permissions for the script:
  
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.
+
  # chmod 755 /usr/local/bin/kde-no-shadow
  
===== Sound applet in the system tray =====
+
The script can be run on login with ''Add Script'' in ''Autostart'':
  
Install Kmix ({{Pkg|kdemultimedia-kmix}}) from the official repositories and start it from the application launcher. Since KDE autostarts programs from the previous session, the program need not be started manually every time one logs in.
+
$ kcmshell5 autostart
  
 
==== Window decorations ====
 
==== Window decorations ====
  
[http://kde-look.org/index.php?xcontentmode=75 Window decorations] can be changed in
+
[https://store.kde.org/browse/cat/114/ Window decorations] can be changed in ''System Settings > Application Style > Window Decorations''.
System Settings > Workspace Appearance > Window Decorations
+
 
There you can also directly download and install more themes with one click and some are available on [https://aur.archlinux.org/packages.php?O=0&K=kdestyle&do_Search=Go&PP=25&SO=d&SB=v AUR].
+
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?K=kde+window+decoration AUR].
  
 
==== Icon themes ====
 
==== Icon themes ====
  
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].
+
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.}}
 +
 
 +
{{Tip|Since some icon themes do not inherit from the default icon theme, some icons may be missing.
 +
To inherit from the Breeze, add {{ic|breeze}} to the {{ic|1=Inherits=}} array in {{ic|/usr/share/icon/''theme-name''/index.theme}}, for example: {{ic|1=Inherits=breeze,hicolor}}. You need to reapply this patch after every update to the icon theme, consider using [[Pacman hooks]] to automate the process.}}
  
Official logos, icons, CD labels and other artwork for Arch Linux are provided in the {{Pkg|archlinux-artwork}} package.  After installing you can find such artwork at {{ic|/usr/share/archlinux/}}.
+
==== Space efficiency ====
  
==== Fonts ====
+
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]. However, you can achieve something similar by editing the file {{ic|~/.config/kwinrc}} adding  {{ic|1=BorderlessMaximizedWindows=true}} in the {{ic|[Windows]}} section.
  
===== Fonts in KDE look poor =====
+
==== Thumbnail generation ====
Try installing the {{Pkg|ttf-dejavu}} and {{Pkg|ttf-liberation}} packages.
 
  
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.
+
To allow thumbnail generation for media or document files on the desktop and in Dolphin, install {{Pkg|kdegraphics-thumbnailers}} and {{Pkg|ffmpegthumbs}}.
  
If you have personally set up how your [[Fonts]] render, be aware that System Settings may alter their appearance.  When you go ''System Settings > Appearance > Fonts'', System Settings will likely alter your font configuration file ({{ic|fonts.conf}}).  
+
Then enable the thumbnail categories for the desktop via ''right click'' on the ''desktop background'' > ''Configure Desktop'' > ''Icons'' > ''Configure Preview Plugins...''.
  
There is no way to prevent this but if you set the values to match your {{ic|fonts.conf}} file the expected font rendering will return (it will require you to restart your application or in a few cases for you to have to restart your desktop).  
+
In ''Dolphin'', navigate to ''Control'' > ''Configure Dolphin...'' >  ''General'' > ''Previews''.
  
Note too that Gnomes' Font Preferences will also do this if you use both desktop environments.
+
=== Printing ===
  
===== Fonts are huge or seems disproportional =====
+
{{Tip|Use the [[CUPS]] web interface for faster configuration. Printers configured in this way can be used in KDE applications. }}
  
Try to force fonts DPI to '''96''' on ''System Settings > Application Appearance > 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 it does not work try set DPI directly on Xorg configuration [[Xorg#Setting_DPI_manually|here]].
+
=== Samba/Windows support ===
  
==== Space efficiency ====
+
If you want to have access to Windows services, install [[Samba]] (package {{Pkg|samba}}).
 +
 
 +
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#Enable Usershares]], after which sharing in Dolphin should work out of the box after restarting Samba.
 +
 
 +
{{Tip|Use {{ic|*}} (asterisk) for both username and password when accessing a Windows share without authentication in Dolphin's prompt.}}
 +
 
 +
Unlike GTK file browsers which utilize GVfs also for the launched program, opening files from Samba shares in Dolphin via KIO makes Plasma copy the whole file to the local system first with most programs (VLC is an exception).
 +
To workaround this, you can use 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 possibility 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.
 +
See [[Samba#Manual mounting]] and [[Samba#Automatic mounting]].
 +
 
 +
An GUI solution is available with {{AUR|samba-mounter-git}}, which offers basically the same functionality via an easy to use option located at ''System Settings'' > ''Network Drivers''. However, it might break with new KDE Plasma versions.
 +
 
 +
=== KDE Desktop activities ===
 +
 
 +
[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.
  
Users with small screens (eg Netbooks) can change some setting to make KDE more space efficient. See [http://userbase.kde.org/KWin#Using_with_small_screens_(eg_Netbooks) upstream wiki] for more info. Also you can use [http://www.kde.org/workspaces/plasmanetbook/ KDE's Plasma Netbook] which is a workspace made specifically for small, lightweight netbook devices.
+
=== Power management ===
  
=== Networking ===
+
[[Install]] {{Pkg|powerdevil}} for an integrated Plasma power managing service. This service offers additional power saving features, monitor brightness control (if supported) and battery reporting including peripheral devices.
  
You can choose from the following tools:
+
An alternative package without [[NetworkManager]] and [[Bluez]] dependencies is provided by {{AUR|powerdevil-light}}.
* NetworkManager.  See [[NetworkManager#KDE4|NetworkManager]] for more information.
 
* Wicd and its KDE front end {{AUR|wicd-kde}}. See [[Wicd]] for more information.
 
  
=== Printing ===
+
{{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]}}
  
{{Tip|Use the [[CUPS]] web interface for faster configuration.}}
+
{{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]].}}
  
The printers are configured in this way can be found in applications KDE.
+
=== Autostart ===
  
You can also choose the printer configuration through ''System Settings > Printer Configuration''. To use this method, you must first install the packages {{Pkg|kdeutils-print-manager}} and {{Pkg|cups}}.
+
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.
  
You need to start the avahi-daemon and cupsd daemons first or you will get the following error:
+
{{Note|
{{bc|The service 'Printer Configuration' does not provide an interface 'KCModule'
+
* Programs can be autostarted on login only, whilst shell scripts can also be run on shutdown or even before Plasma itself starts.
with keyword 'system-config- printer-kde/system-config-printer-kde.py'
+
* Shell scripts will only be run if they are marked [[executable]].
The factory does not support creating components of the specified type.
 
 
}}
 
}}
  
If you are getting the following error, you need to give the user rights to manage printers:
+
* Place [[Desktop entries]] (i.e. ''.desktop'' files) in the appropriate [[XDG Autostart]] directory.
There was an error during CUPS operation: 'cups-authorization-canceled'
 
  
For CUPS, this is set in {{ic|/etc/cups/cupsd.conf}}.
+
* Place or symlink shell scripts in one of the following directories:
  
Adding {{ic|lp}} to {{ic|SystemGroup}} allows anyone who can print to configure printers. You can, of course, add another group instead of {{ic|lp}}.
+
:; {{ic|~/.config/plasma-workspace/env/}}: for executing scripts at login before launching Plasma.
{{hc|/etc/cups/cupsd.conf|# Administrator user group...
+
:; {{ic|~/.config/autostart-scripts/}}: for executing scripts at login.
SystemGroup sys root lp}}
+
:; {{ic|~/.config/plasma-workspace/shutdown/}}: for executing scripts on shutdown.
  
=== Samba/Windows support ===
+
=== Phonon ===
  
If you want to have access to Windows services install [[Samba]] (package {{Pkg|samba}}).
+
From [[Wikipedia:Phonon (software)|Wikipedia]]:
  
You may then configure your Samba shares through
+
: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.
  
  System Settings > Sharing > Samba
+
: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.
  
=== KDE Desktop activities ===
+
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).
  
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.
+
==== Which backend should I choose? ====
  
On your desktop, click the Cashew Plasmoid and on the pop-up window press "Activities".
+
You can choose between backends based on [[GStreamer]] and [[VLC]] – each available in versions for Qt4 applications and Qt5 applications ({{AUR|phonon-qt4-gstreamer}}, {{Pkg|phonon-qt5-gstreamer}} – {{AUR|phonon-qt4-vlc}}, {{Pkg|phonon-qt5-vlc}}).
  
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.
+
[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]. The Gstreamer backend has some optional codec dependency, install them as needed:
  
=== Power saving ===
+
* {{Pkg|gst-libav}} — Libav codecs.
 +
* {{Pkg|gst-plugins-good}} — PulseAudio support and additional codecs.
 +
* {{Pkg|gst-plugins-ugly}} — additional codecs.
 +
* {{Pkg|gst-plugins-bad}} — additional codecs.
  
KDE has an integrated power saving service called "'''Powerdevil Power Management'''" that may adjust the power saving profile of the system and/or the brightness of the screen (if supported).
+
In the past other backends were developed as well but are no longer maintained and their AUR packages have been deleted.
  
==== How to enable Cpufreq based power saving ====
+
{{Note|1=<br>
 +
* Multiple backends can be installed at once and prioritized via the ''phononsettings'' application.
 +
* 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 using the VLC backend, you may experience crashes every time Plasma wants to send you an audible warning and in quite a number of other cases as well [https://forum.kde.org/viewtopic.php?f=289&t=135956]. A possible fix is to rebuild the VLC plugins cache:
 +
{{bc|# /usr/lib/vlc/vlc-cache-gen /usr/lib/vlc/plugins}}
 +
}}
  
{{Note|Cpufreq seems have been dropped from arch linux in favour of [[cpupower]] ([https://github.com/mate-desktop/mate-applets/issues/11 reference]).}}
+
== Applications ==
  
Since KDE 4.6, CPU frequency scaling is no longer managed by KDE.  Instead it is assumed to be handled automatically by the the hardware and/or kernel.  Arch uses {{ic|ondemand}} as default cpufreq governor from kernel vesion 3.3. See [[cpufreq|wiki article on cpufreq]].
+
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.
  
If you are happy with setting your governor once at boot (with the {{ic|cpufreq}} daemon script, for example) then this section is not relevant and can be skipped.
+
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.
  
# If you have not already done so, install the {{Pkg|cpufrequtils}} package (for the {{ic|cpufreq-set}} utility).
+
=== System administration ===
  
# Next, you will need to grant access to '''cpufreq-set''' for the appropriate users by configuring [[sudo]].  For example, if you are part of the ''wheel'' group, you could use {{ic|visudo}} to add:
+
==== Terminate Xorg server through KDE System Settings ====
%wheel ALL = (ALL) NOPASSWD: /usr/bin/cpufreq-set
 
to your {{ic|sudoers}} file.
 
  
3. From ''System Settings > Power Management > Power Profiles'' select a profile to edit or create a new one.  Check the ''Run Script'' option and add an appropriate {{ic|cpufreq-set}} command for the selected power profile. For example, your "Powersave" profile might have:
+
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.
sudo cpufreq-set -r -g ondemand
 
Your "Performance" profile might have
 
sudo cpufreq-set -r -g performance
 
  
{{Note|* The ''cpufreq-set'' examples above may be insufficient for setting the governor for all processors/cores.
+
==== KCM ====
For some CPU families the {{ic|-r}} switch may not set the governor for all cores/cpus and instead only set the governor for CPU 0.  In this case you will need to write a script to iterate through all your cores.  A simple script for a four core system could look like:
 
#!/bin/bash
 
for i in {0..3}; do
 
  sudo /usr/bin/cpufreq-set -c${i} -gondemand
 
done
 
* You can check which governors are active with {{ic|cpufreq-info -o}} or less intuitively by inspecting {{ic|/sys/devices/system/cpu/cpu*/cpufreq/scaling_governor}}.
 
}}
 
  
=== Monitoring changes on local files and directories ===
+
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''.
  
KDE now uses '''inotify''' directly from the kernel with '''kdirwatch''' (included in kdelibs), so Gamin or FAM are no longer needed. You may want to install this {{AUR|kdirwatch}} from AUR which is a GUI frontend for kdirwatch.
+
* {{App|sddm-kcm|KDE Config Module for [[SDDM]].|https://cgit.kde.org/sddm-kcm.git|{{Pkg|sddm-kcm}}}}
 +
* {{App|kde-gtk-config|GTK2 and GTK3 Configurator for KDE.|https://cgit.kde.org/kde-gtk-config.git|{{Pkg|kde-gtk-config}}}}
 +
* {{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/|{{Pkg|kcm-wacomtablet}}}}
 +
* {{App|Kcmsystemd|systemd control module for KDE.|https://github.com/rthomsen/kcmsystemd|{{AUR|systemd-kcm}}}}
  
== System administration ==
+
More KCMs can be found at [https://www.linux-apps.com/search?projectSearchText=KCM linux-apps.com].
  
=== Set keyboard layout in order switch language inputs ===
+
=== Desktop search ===
  
In order to do that, navigate to
+
KDE implements desktop search with a software called [[Baloo]], a file indexing and searching solution.
    System Settings > Hardware > 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 ===
+
=== Web browsers ===
  
Navigate to:
+
The following web browsers can integrate with Plasma:
System Settings > Input Devices > Keyboard > Advanced (tab) > "Key Sequence to kill the X server" submenu
 
and tick the checkbox.
 
  
=== Useful KCM ===
+
* {{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:Falkon|Falkon]]|A Qt web browser with Plasma integration features, previously known as Qupzilla. It uses Qt WebEngine.|https://userbase.kde.org/Falkon/|{{Pkg|falkon}}}}
 +
* {{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}}}}
  
KCM means KConfig Module. This modules help you to configure you system providing a interface on System Settings.
+
{{Tip|Starting from Plasma 5.13, one can integrate [[Firefox]] or [[Chrome]] with Plasma: providing media playback control from the Plasma tray, download notifications and find open tabs in KRunner. [[Install]] {{pkg|plasma-browser-integration}} and the corresponding browser add-on. Chrome/Chromium support should already be included, for Firefox add-on see [[Firefox#KDE/GNOME integration]].}}
  
'''Configuration for look&feel of your GTK apps.'''
+
=== PIM ===
* {{Pkg|kde-gtk-config}}
 
* {{AUR|kcm-gtk}}
 
* {{AUR|kcm-qt-graphicssystem}}
 
  
'''Configuration for the GRUB2 bootloader.'''
+
KDE offers its own stack for [[Wikipedia:Personal information management|personal information management]] (PIM). This includes emails, contacts, calendar, etc. To install all the PIM packages, you could use the {{Grp|kdepim}} package group or the {{Pkg|kdepim-meta}} meta package.
* {{AUR|grub2-editor}}
 
* {{AUR|kcm-grub2}}
 
  
'''Configuration for Synaptics driver based touchpads.'''
+
==== Akonadi ====
* {{Pkg|synaptiks}}
 
* {{AUR|kcm_touchpad}}
 
  
'''Configuration for [[Firewalls#ufw|UFW]]'''
+
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).
* {{AUR|kcm-ufw}}
 
  
'''Configuration for [[PolicyKit]]'''
+
Install {{Pkg|akonadi}}. For additional addons, install {{Pkg|kdepim-addons}}.
* {{AUR|kcm-polkit-kde-git}}
 
  
'''Configuration for Wacom Tablet'''
+
{{Note|If you wish to use a database engine other than [[MariaDB]], then when installing the {{Pkg|akonadi}} package, use the following command to skip installing the {{Pkg|mariadb}} dependencies:
* {{AUR|kcm-wacomtablet}}
 
  
More KCM can be found [http://kde-apps.org/index.php?xcontentmode=273 here].
+
# pacman -S akonadi --assume-installed mariadb
  
== Desktop search and semantic desktop ==
+
See also {{Bug|32878}}.
 +
}}
  
According to [https://en.wikipedia.org/wiki/Semantic_desktop Wikipedia], ''"the Semantic Desktop is a collective term for ideas related to changing a computer's user interface and data handling capabilities so that data is more easily shared between different applications or tasks and so that data that once could not be automatically processed by a computer can be (automatically processed)."''
+
===== MySQL =====
  
The KDE implementation of this concept is tied to (as of KDE 4.10) two major pieces of software, Akonadi and Nepomuk. Between the two of them, these programs look at your data and make an easily searchable index of it. The idea behind these pieces of software is to make your system "aware" of your data and give it context using meta-data and user-supplied tags.
+
By default Akonadi will use {{ic|/usr/bin/mysqld}} ([[MariaDB]] by default, see [[MySQL]] for alternative providers) to run a managed MySQL instance with the database stored in {{ic|~/.local/share/akonadi/db_data/}}.
  
Soprano and Virtuoso are two dependencies of the Nepomuk Semantic Desktop. Since the relationship between the two major components and their dependencies is not very clear, the following sections try to shed some light on their inner workings.
+
====== System-wide MySQL instance ======
  
=== Virtuoso and Soprano ===
+
Akonadi supports using the system-wide [[MySQL]] for its database.[https://techbase.kde.org/KDE_PIM/Akonadi#Can_Akonadi_use_a_normal_MySQL_server_running_on_my_system.3F]
  
The database used to store all the metadata used by the semantic desktop is a ''[https://en.wikipedia.org/wiki/Resource_Description_Framework Resource Description Framework (RDF)]'' database called Virtuoso. Internally, Virtuoso may be looked as a relational database. (A [https://en.wikipedia.org/wiki/Relational_model relational database] is different from a traditional single-table based database in the sense that it uses multiple tables related by a single key in order to store data.) It is currently controlled by OpenLink, and is available under commercial and an open source license.
+
{{Expansion|Add instructions.}}
  
From the [http://techbase.kde.org/Projects/Nepomuk/ComponentOverview#Soprano KDE Techbase], ''Soprano is a Qt abstraction over databases. It provides a friendly Qt-based API for accessing different RDF stores. It currently supports 3 database backends - Sesame, Redland and Virtuoso. The KDE Semantic Stack only works with Virtuoso. Soprano also provides additional features such as serializing, parsing RDF data, and a client server architecture that is heavily used in Nepomuk.''
+
{{hc|~/.config/akonadi/akonadiserverrc|2=
 +
[%General]
 +
Driver=QMYSQL
  
=== Nepomuk ===
+
[QMYSQL]
 +
Host=
 +
Name=akonadi_''username''
 +
Options="UNIX_SOCKET=/run/mysqld/mysqld.sock"
 +
StartServer=false
 +
}}
  
Nepomuk stands for "Networked Environment for Personal, Ontology-based Management of Unified Knowledge". It is what allows all the tagging and labeling of files as well to take place and also serves as the way to actually read the Virtuoso databases. It provides an API to application developers which allows them to read the data collected by it.
+
===== PostgreSQL =====
  
In the past, the "Strigi" service was used to collect data about the various files present on the system. However, due to many reasons, the most important of them being CPU and Memory usage, Strigi was replaced by a homegrown indexing service which is integrated with Nepomuk-Core.
+
Akonadi supports either using the existing system-wide [[PostgreSQL]] instance, i.e. {{ic|postgresql.service}}, or running a PostgreSQL instance with user privileges and the database in {{ic|~/.local/share/akonadi/db_data/}}.
  
For further information about Nepomuk, [http://techbase.kde.org/Projects/Nepomuk/ComponentOverview#Nepomuk_Components this page] is a good resource. However, some of the information in the previous page has been rendered outdated according to [http://vhanda.in/blog/2012/11/nepomuk-without-strigi/ this blog post].
+
====== Per-user PostgreSQL instance ======
  
==== Using and configuring Nepomuk ====
+
[[Install]] {{Pkg|postgresql}} and {{Pkg|postgresql-old-upgrade}}.
  
In order to search using Nepouk on the KDE desktop, press {{Keypress|ALT+F2}} and type in your query. Nepomuk is enabled by default. It can be turned on and off in
+
Edit Akonadi configuration file so that it has the following contents:
System Settings > Desktop Search
 
  
Nepomuk has to keep track of a lot of files. It is for this reason that it is recommended to increase the number of files that can be watched with inotify. In order to do that this command is a good option.
+
{{hc|~/.config/akonadi/akonadiserverrc|2=
sysctl fs.inotify.max_user_watches=524288
+
[%General]
 +
Driver=QPSQL
 +
}}
  
To do it persistently:
+
{{Note|
echo "fs.inotify.max_user_watches = 524288" >> /etc/sysctl.conf
+
* When Akonadi starts, it will create the {{ic|[QPSQL]}} section and set the appropriate variables in it.
 +
* The database will be stored in {{ic|~/.local/share/akonadi/db_data/}}.
 +
}}
  
Restart Nepomuk to see the changes.
+
Start Akonadi with {{ic|akonadictl start}}, and check its status: {{ic|akonadictl status}}.
  
====KDE without Nepomuk====
+
{{Note|
 +
* Starting with {{Pkg|akonadi}} 19.08.0-1 the PostgreSQL database cluster in {{ic|~/.local/share/akonadi/db_data/}} will get automatically upgraded when a major PostgreSQL version upgrade is detected.
 +
* For previous {{Pkg|akonadi}} versions major PostgreSQL version upgrades will require a manual database upgrade. Follow the [https://userbase.kde.org/Akonadi/Postgres_update update instructions on KDE UserBase Wiki]. Make sure to adjust the paths to PostgreSQL binaries to those used by {{Pkg|postgresql}} and {{Pkg|postgresql-old-upgrade}}, see [[PostgreSQL#Upgrading PostgreSQL]].
 +
}}
  
If you wish to run KDE without Nepomuk, there exists a {{AUR|nepomuk-core-fake}} package in the AUR.
+
====== System-wide PostgreSQL instance ======
{{Warning|As of now, Dolphin depends on {{Pkg|nepomuk-widgets}} and hence will break if used with the fake Nepomuk package}}
 
  
=== Akonadi ===
+
This requires an already configured and running [[PostgreSQL]].
  
Akonadi is a system meant to act as a local cache for PIM data, regardless of its origin, which can be then used by other applications. This includes the user's emails, contacts, calendars, events, journals, alarms, notes, and so on. It interfaces with the Nepomuk libraries to provide searching capabilities.
+
Create a PostgreSQL user account for your user:
  
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).
+
[postgres]$ createuser ''username''
  
For more information on Akonadi and its relationship with Nepomuk, see [http://blogs.kde.org/node/4503] and [http://cmollekopf.wordpress.com/2013/02/13/kontact-nepomuk-integration-why-data-from-akonadi-is-indexed-in-nepomuk/].
+
Create a database for Akonadi:
  
==== Disabling Akonadi ====
+
[postgres]$ createdb -O ''username'' --locale=en_US.UTF-8 -T template0 akonadi-''username''
  
See this [http://userbase.kde.org/Akonadi#Disabling_the_Akonadi_subsystem section in the KDE userbase].
+
Configure Akonadi to use the system-wide PostgreSQL:
  
==== Database configuration ====
+
{{hc|~/.config/akonadi/akonadiserverrc|2=
 +
[%General]
 +
Driver=QPSQL
  
Start {{ic|akonaditray}} from package {{Pkg|kdepim-runtime}}. Right click on it and select '''configure'''. In the Akonadi server configure tab, you can:
+
[QPSQL]
* Configuring Akonadi to use MySQL Server running on the System
+
Host=/run/postgresql
* Configuring Akonadi to use sqlite
+
Name=akonadi-''username''
 +
StartServer=false
 +
}}
  
==== Running KDE without Akonadi ====
+
{{Note|Custom port, username and password can be specified with options {{ic|1=Port=}}, {{ic|1=User=}}, {{ic|1=Password=}} in the {{ic|[QPSQL]}} section.}}
  
The package {{AUR|akonadi-fake}} is a good option for those who wish to run KDE without Akonadi.
+
Start Akonadi with {{ic|akonadictl start}}, and check its status: {{ic|akonadictl status}}.
  
== Phonon ==
+
===== SQLite =====
  
=== What is Phonon? ===
+
To use [[SQLite]] edit Akonadi configuration file to match the configuration below:
  
From [[Wikipedia:Phonon|Wikipedia]]:
+
{{hc|~/.config/akonadi/akonadiserverrc|2=
''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.
+
[%General]
''
+
Driver=QSQLITE3
 +
}}
  
'''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).
+
{{Note|
 +
* When Akonadi starts, it will create the {{ic|[QSQLITE3]}} section and set the appropriate variables in it.
 +
* The database will be stored as {{ic|~/.local/share/akonadi/akonadi.db}}.
 +
}}
 +
 
 +
===== Disabling Akonadi =====
 +
 
 +
See this [https://userbase.kde.org/Akonadi#Disabling_the_Akonadi_subsystem section in the KDE userbase].
  
=== Which backend should I choose? ===
+
=== KDE Telepathy ===
  
You can choose between various backends, like GStreamer ({{Pkg|phonon-gstreamer}}) or VLC ({{Pkg|phonon-vlc}}) available in the [[official repositories]], Xine ({{AUR|phonon-xine}}) or  MPlayer ({{AUR|phonon-mplayer-git}}) available on [[AUR]]. Most users will want GStreamer or VLC which have the best upstream support. Note that multiple backends can be installed at once and you can switch between them via ''System Settings > Multimedia > Phonon > Backend''.
+
[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.
  
{{Note|According to the [http://userbase.kde.org/Phonon#Backend_libraries KDE UserBase], Phonon-MPlayer and Phonon-Xine are currently unmaintained}}
+
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.
  
According to [https://www.archlinux.org/news/kde-sc-46-to-extra/ announcement of KDE 4.6 in Arch] and [http://mail.kde.org/pipermail/phonon-backends/2011-February/000500.html mail in Phonon dev list], users should prefer GStreamer over VLC due to the feature difference.
+
==== Use Telegram with KDE Telepathy ====
  
== Useful applications ==
+
[[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).
  
The official set of KDE applications may be found [http://www.kde.org/applications/ here].
+
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).
  
=== Yakuake ===
+
{{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.}}
  
[http://yakuake.kde.org/ This] application provides a Quake-like terminal emulator, which is toggled visible using the F12 key. It also has support for multiple tabs. Yakuake can be installed by package {{Pkg|yakuake}}.
+
=== KDE Connect ===
  
===  KDE Telepathy ===
+
[https://community.kde.org/KDEConnect KDE Connect] provides several features to connect your [[Android]] phone with your Linux desktop:
  
[http://community.kde.org/KTp KDE Telepathy] is a project with the goal to closely integrate Instant Messaging with the KDE desktop. It utilizes the Telepathy framework as a backend, and is intended to replace Kopete.
+
* 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.
  
To install all Telepathy protocols install the {{Grp|telepathy}} group.
+
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 KDE Connect from [https://play.google.com/store/apps/details?id=org.kde.kdeconnect_tp Google Play] or from [https://f-droid.org/packages/org.kde.kdeconnect_tp/ F-Droid]. If you want to browse your phone's filesystem, you need to [[install]] {{Pkg|sshfs}} as well and configure filesystem exposes in your Android app.
To use the KDE Telepathy client, install the {{Pkg|kde-telepathy-meta}} package that includes all the packages contained in the {{Grp|kde-telepathy}} group .
+
 
 +
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. For GNOME users, better integration can be achieved by installing {{AUR|gnome-shell-extension-gsconnect}} instead of {{Pkg|kdeconnect}}.
 +
 
 +
If you use a [[firewall]], you need to open UDP and TCP ports {{ic|1714}} through {{ic|1764}}. See https://community.kde.org/KDEConnect#Troubleshooting.
  
 
== Tips and tricks ==
 
== Tips and tricks ==
  
=== Configure KWin to use OpenGL ES ===
+
=== Use a different window manager ===
  
Beginning with KWin version 4.8 it is possible to use the separately built binary '''kwin_gles''' as a replacement for kwin. It behaves almost the same as the kwin executable in OpenGL2 mode with the slight difference that it uses ''egl'' instead of ''glx'' as the native platform interface. To test kwin_gles you just have to run {{ic|kwin_gles --replace}} in Konsole.
+
The component chooser settings in Plasma does not allow changing the window manager anymore. [https://github.com/KDE/plasma-desktop/commit/2f83a4434a888cd17b03af1f9925cbb054256ade]
If you want to make this change permanent you have to create a script in {{ic|$(kde4-config --localprefix)/env/}} which exports {{ic|1=KDEWM=kwin_gles}}.
+
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 :
  
=== Enabling video thumbnails under Konqueror/Dolphin file managers ===
+
{{hc|~/.config/plasma-workspace/env/set_window_manager.sh|2=
 +
export KDEWM=/usr/bin/i3
 +
}}
  
For thumbnails of videos in konqueror and dolphin install {{Pkg|kdemultimedia-mplayerthumbs}} or {{Pkg|kdemultimedia-ffmpegthumbs}}.
+
And then make it executable :
  
=== Speed up application startup ===
+
{{bc|$ chmod +x ~/.config/plasma-workspace/env/set_window_manager.sh}}
  
User Rob wrote on his blog this "[http://kdemonkey.blogspot.nl/2008/04/magic-trick.html magic trick]" to improve applications start up by 50-150ms.
+
{{Note|When using i3 window manager with Plasma, it may be necessary to manually set dialogs to open in floating mode in order for them to correctly appear. For more information, see [[I3#Correct handling of floating dialogs]].}}
To enable it, create this folder in your home:
 
$ mkdir -p ~/.compose-cache
 
  
''For those curious about what is going on here, this enables an optimization which Lubos (of general KDE speediness fame) came up with some time ago and was then rewritten and integrated into libx11. Ordinarily on startup applications read input method information from {{ic|/usr/share/X11/locale/<your locale>/Compose}}. This Compose file is quite long (>5000 lines for the en_US.UTF-8 one) and takes some time to process. libX11 can create a cache of the parsed information which is much quicker to read subsequently, but it will only re-use an existing cache or create a new one in {{ic|~/.compose-cache}} if the directory already exists.'' [Cit. Rob]
+
==== KDE/Openbox session ====
  
=== Hiding partitions ===
+
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.
  
In Dolphin, it is as simple as right-clicking on the partition in the 'Places' sidebar and selecting 'Hide <partition>'. Otherwise...
+
For those starting the session manually, add the following line to your [[xinit]] configuration:
  
If you wish to prevent your internal partitions from appearing in your file manager, you can create an udev rule, for example {{ic|/etc/udev/rules.d/10-local.rules}}:
+
{{hc|~/.xinitrc|
 +
exec openbox-kde-session
 +
}}
  
KERNEL=="sda[0-9]", ENV{UDISKS_IGNORE}="1"
+
==== Re-enabling compositing effects ====
  
The same thing for a certain partition:
+
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]].
  
KERNEL=="sda1", ENV{UDISKS_IGNORE}="1"
+
=== Configuring monitor resolution / multiple monitors ===
KERNEL=="sda2", ENV{UDISKS_IGNORE}="1"
 
  
=== Konqueror tips ===
+
To enable display resolution management and multiple monitors in Plasma, install {{Pkg|kscreen}}. This provides additional options to ''System Settings > Display and Monitor''.
  
==== Disabling smart key tooltips (browser) ====
+
=== KWin-lowlatency ===
  
To disable those smart key tooltips in Konqueror (pressing {{Keypress|Ctrl}} on a web page), open {{ic|~/.kde4/share/config/konquerorrc}} and add this section:
+
[https://github.com/tildearrow/kwin-lowlatency KWin-lowlatency] is a attempt to reduce latency and stuttering in the popular KWin compositor and is available as {{AUR|kwin-lowlatency}}.
  
[Access Keys]
+
=== Configuring ICC profiles ===
Enabled=false
 
  
==== Disabling the sidebar tab (filemanager) ====
+
To enable [[ICC profiles]] in Plasma, [[install]] {{Pkg|colord-kde}}. This provides additional options to ''System Settings > Color Corrections''.
  
To disable this small sidebar tab on the left side, open {{ic|~/.kde4/share/config/konqsidebartng.rc}} and set {{ic|HideTabs}} to {{ic|true}}.
+
ICC profiles can be imported using ''Add Profile''.
  
==== Using WebKit ====
+
=== Disable opening application launcher with Super key (Windows key) ===
  
WebKit is an open source browser engine developed by Apple Inc. It is a derivative from the KHTML and KJS libraries and contains many improvements. WebKit is used by Safari, Google Chrome and rekonq.
+
To disable this feature you currently can run the following command:
  
It is possible to use WebKit in Konqueror instead of KHTML. First install the {{Pkg|kwebkitpart}} package.
+
$ kwriteconfig5 --file kwinrc --group ModifierOnlyShortcuts --key Meta ""
  
Then, after executing Konqueror, press ''Settings > Configure Konqueror''.
+
=== Disable bookmarks showing in application menu ===
  
On the ''General'' submenu, select ''WebKit'' as the ''Default web browser engine''.
+
With Plasma Browser integration installed, KDE will show bookmarks in the application launcher.
  
=== Firefox integration ===
+
To disable this feature you currently can run the following commands:
  
See [[Firefox#KDE_integration]].
+
$ mkdir ~/.local/share/kservices5
 +
$ sed 's/EnabledByDefault=true$/EnabledByDefault=false/' /usr/share/kservices5/plasma-runner-bookmarks.desktop > ~/.local/share/kservices5/plasma-runner-bookmarks.desktop
  
 
== Troubleshooting ==
 
== Troubleshooting ==
  
=== Getting current state of KWin for support and debug purposes ===
+
=== Fonts ===
 +
 
 +
==== Fonts in a Plasma session look poor ====
  
This command prints out a wonderful summary of the current state of KWin including used options, used compositing backend and relevant OpenGL driver capabilities. [http://blog.martin-graesslin.com/blog/2012/03/on-getting-help-for-kwin-and-helping-kwin/ See more at Martin's blog]
+
Try installing the {{Pkg|ttf-dejavu}} and {{Pkg|ttf-liberation}} packages.
  
qdbus org.kde.kwin /KWin supportInformation
+
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.
  
=== KDE4 does not finish loading ===
+
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}}).
  
There might be a situation in which the graphic driver might create a conflict when starting KDE4. This situation happens after the login but before finishing loading the desktop, making the user wait indefinitely at the loading screen. Until now the only users confirmed to be affected by this are the ones that use Nvidia drivers and KDE4.
+
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.
  
A solution for Nvidia users is to edit the file at {{ic|/home/user/.kde4/share/config/kwinrc}} and change the option '''Enabled=true''' to '''false''' in the '''[Compositing]''' section. For more information look at this [https://bbs.archlinux.org/viewtopic.php?pid=932598 thread].
+
==== Fonts are huge or seem disproportional ====
  
If a minimal install was done, make sure you installed the required font by your phonon backend listed here: [[KDE#Minimal_install]]
+
Try to force font DPI to {{ic|'''96'''}} in ''System Settings > Fonts''.
  
=== KDE and Qt programs look bad when in a different window manager ===
+
If that does not work, try setting the DPI directly in your Xorg configuration as documented in [[Xorg#Setting DPI manually]].
  
If you are using KDE or Qt programs but not in a full KDE session (specifically, you did not run "startkde"), then as of KDE 4.6.1 you will need to tell Qt how to find KDE's styles (Oxygen, QtCurve etc.)
+
=== Configuration related ===
  
You just need to set the environment variable QT_PLUGIN_PATH. E.g. put:
+
Many problems in KDE are related to its configuration.
  
export QT_PLUGIN_PATH=$HOME/.kde4/lib/kde4/plugins/:/usr/lib/kde4/plugins/
+
==== Plasma desktop behaves strangely ====
  
into your {{ic|/etc/profile}} (or {{ic|~/.profile}} if you do not have root access). qtconfig should then be able to find your kde styles and everything should look nice again!
+
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 or uninstall it.
  
Alternatively, you can symlink the Qt styles directory to the KDE styles one:
+
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 on the [https://bugs.kde.org/ KDE bug tracker] '''only if it is an official widget'''. If it is not, it is recommended to find the entry on the [https://store.kde.org/ KDE Store] and inform the developer of that widget about the problem (detailing steps to reproduce, etc.).
# ln -s /usr/lib/kde4/plugins/styles/ /usr/lib/qt/plugins/styles
 
  
Under Gnome you can try to install the package libgnomeui.
+
If you cannot find the problem, but you do not want ''all'' the settings to be lost, navigate to {{ic|~/.config/}} and run the following command:
  
=== KDE and Qt programs look bad after upgrade (using kwin) ===
+
$ for j in plasma*; do mv -- "$j" "${j%}.bak"; done
  
The problem is caused by old cache. Run the following to rebuild it:
+
This command will rename '''all''' Plasma related configuration files 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.
  
  $ rm ~/.config/Trolltech.conf
+
==== Clean cache to resolve upgrade problems ====
  $ kbuildsycoca4 --noincremental
 
  
[https://bbs.archlinux.org/viewtopic.php?id=135301 Reference].
+
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, Ark being unable to extract archives or Amarok not recognizing any of your music. This solution can also resolve problems with KDE and Qt applications looking bad after an update.
  
=== Graphical related issues ===
+
Rebuild the cache using the following commands:
  
==== Low 2D desktop performance (or) artifacts appear when on 2D ====
+
$ rm ~/.config/Trolltech.conf
 +
$ kbuildsycoca5 --noincremental
  
===== GPU driver problem =====
+
Optionally, empty the {{ic|~/.cache/}} folder contents, however, this will also clear the cache of other applications:
 +
 +
$ rm -rf ~/.cache/*
  
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.
+
==== Volume control, notifications or multimedia keys do not work ====
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 =====
+
Hiding certain items in the System Tray settings (e.g. Audio Volume, Media Player or Notifications) also disables related features. Hiding the ''Audio Volume'' disables volume control keys, ''Media Player'' disables multimedia keys (rewind, stop, pause) and hiding ''Notifications'' disables showing notifications.
  
If this does not solve your problems, maybe your driver does not provide a good '''XRender''' acceleration which the current Qt painter engine relies on by default.
+
==== Login Screen KCM does not sync cursor settings to SDDM ====
  
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'''".  
+
The Login Screen KCM reads your cursor settings from {{ic|~/.config/kcminputrc}}, without this file no settings are synced. The easiest way to generate this file is to change your cursor theme in ''System Settings > Cursors'', then change it back to your preferred cursor theme.
  
The raster paint engine enables the CPU to do the majority of the painting, as opposed to the GPU. You may get better performance, depending on your system. This is basically a work-around for the terrible Linux driver stack, since the CPU should obviously not be doing graphical computations since it is designed for fewer threads of greater complexity, as opposed to the GPU which is many threads but lesser computational strength. So, only use Raster engine if you are having problems or your GPU is much slower than you CPU, otherwise is better to use XRender.
+
=== Graphical problems ===
  
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, and Native is just using the X11 rendering (mixture, usually).
+
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]].
  
'''The best and automatic way to do that''' is to install {{AUR|kcm-qt-graphicssystem}} from AUR and configure this particular Qt setting through
+
==== Getting current state of KWin for support and debug purposes ====
  
  System Settings > Qt Graphics System
+
This command prints out a 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].
  
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].
+
$ qdbus org.kde.KWin /KWin supportInformation
  
==== Low 3D desktop performance====
+
==== Disable desktop effects manually or automatically for defined applications ====
  
KDE begins with desktop effects enabled. Older cards may be insufficient for 3D desktop acceleration. You can disable desktop effects in  
+
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 Behavior > Desktop Effects'' and you can toggle desktop effects with {{ic|Alt+Shift+F12}}.  
System Settings > Desktop Effects
 
or you can toggle desktop effects with {{Keypress|Alt+Shift+F12}}.
 
  
{{Note| You may encounter such problems with 3D desktop performance even when using a more powerful graphics card, especially the catalyst proprietary driver (fglrx). This driver is known for having issues with 3D acceleration. Visit [[ATI|the ATi Wiki page]] for more troubleshooting.}}
+
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''.
  
==== Desktop compositing is disabled on my system with a modern Nvidia GPU ====
+
==== Enable transparency ====
  
Sometimes, KWin may have settings in its 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 {{ic|~/.kde4/share/config/kwinrc}} file and relogin. The KWin settings will turn to the KDE default ones and the problem should be probably gone.
+
If you use a transparent background without enabling the compositor, you will get the message:
  
==== Flickering in fullscreen when compositing is enabled ====
+
This color scheme uses a transparent background which does not appear to be supported on your desktop
  
As of KDE SC 4.6.0, there is an option in systemsettings > Desktop Effect > Advanced > "Suspend desktop effects for fullscreen windows" Uncheck it would tell kwin to disable unredirect fullscren.
+
In ''System Settings > Display and Monitor > Compositor'', check ''Enable compositor on startup'' and restart Plasma.
  
==== Screen Tearing with desktop compositing enabled ====
+
==== Disable compositing ====
  
KWin may suffer from screen tearing while desktop effects are enabled. Uncheck the VSync option under System Settings > Desktop Effects > Advanced > "Use Vsync".
+
In ''System Settings > Display and Monitor > Compositor'', uncheck ''Enable compositor on startup'' and restart Plasma.
  
For proprietary driver users, ensure that the driver's VSync option is enabled (amdccle for [[amd_catalyst|Catalyst]] users, and nvidia-settings for [[Nvidia]] users).
+
==== Flickering in fullscreen when compositing is enabled ====
  
=== Sound problems under KDE ===
+
In ''System Settings > Display and Monitor > Compositor'', uncheck ''Allow applications to block compositing''. This may harm performance.
  
==== ALSA related problems ====
+
==== Screen tearing with NVIDIA ====
  
{{Note|First make sure you have {{Pkg|alsa-lib}} and {{Pkg|alsa-utils}} installed.}}
+
See [[NVIDIA/Troubleshooting#Avoid screen tearing in KDE (KWin)]].
  
===== "Falling back to default" messages when trying to listen to any sound in KDE =====
+
==== Plasma cursor sometimes shown incorrectly ====
  
When you encounter such messages:
+
Create the directory {{ic|~/.icons/default}} and inside a file named {{ic|index.theme}} with the following contents:
: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|~/.icons/default/index.theme|2=
 +
[Icon Theme]
 +
Inherits=breeze_cursors
 +
}}
  
That can be solved by installing the GStreamer plugins (package {{Pkg|gstreamer0.10-plugins}}. If you still encounter problems, you can try changing the Phonon backend used by installing another such as {{Pkg|phonon-vlc}}.
+
Execute the following command:
Then make sure the backend is preferred via:
 
  System Settings > Multimedia > Phonon > Backend (tab)
 
  
=== I want a fresh installation of KDE for my system ===
+
$ ln -s /usr/share/icons/breeze_cursors/cursors ~/.icons/default/cursors
  
Just rename the settings directory of KDE (just in case you will want to go back to your original settings):
+
==== Unusable screen resolution set ====
mv ~/.kde4 ~/.kde4-backup
 
  
=== Plasma desktop behaves strangely ===
+
Your local configuration settings for kscreen can override those set in {{ic|xorg.conf}}. Look for kscreen configuration files in {{ic|~/.local/share/kscreen/}} and check if mode is being set to a resolution that is not supported by your monitor.
  
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.
+
==== Blurry icons in System tray ====
  
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).
+
In order to add icons to tray, applications often make use of the library appindicator. If your icons are blurry, check which version of libappindicator you have installed. If you only have {{Pkg|libappindicator-gtk2}} installed, you can install {{Pkg|libappindicator-gtk3}} or {{Pkg|libappindicator-sharp}} as an attempt to get clear icons.
  
If you cannot find the problem, but you do not want ''all'' the KDE settings to be lost, do:
+
=== Sound problems ===
  
  rm -r ~/.kde4/share/config/plasma*
+
{{Note|First make sure you have {{Pkg|alsa-utils}} installed.}}
  
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.
+
==== No sound after suspend ====
  
=== Konsole does not save commands' history ===
+
If there is no sound after suspending and if KMix does not show audio devices which should be there, restarting plasmashell and pulseaudio may help:
  
By default console commands' history is saved only when you type 'exit' in console. When you close Konsole with 'x' in the corner it does not happen.
+
$ killall plasmashell
To enable autosaving after every command execution you should add following lines into your .bashrc
+
  $ systemctl --user restart pulseaudio.service
  shopt -s histappend
+
  $ plasmashell
  [[ "${PROMPT_COMMAND}" ]] && PROMPT_COMMAND="$PROMPT_COMMAND;history -a" || PROMPT_COMMAND="history -a"
 
  
=== KDE password prompts display three bullets per char ===
+
Some applications may also need to be restarted in order for sound to play from them again.
  
You can change it under ''System Settings > Account Details''. At ''Password & User Account'' the options are:
+
==== MP3 files cannot be played when using the GStreamer Phonon backend ====
* Show one bullet for each letter
 
* Show three bullets for each letter
 
* Show nothing
 
  
=== Nepomukserver process still autostart even with semantic desktop disabled ===
+
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 {{AUR|phonon-qt4-vlc}} or {{Pkg|phonon-qt5-vlc}}.
Go to ''' System Settings > Startup and Shutdown > Service Manager > Startup Services''' and uncheck the Nepomuk Search Module.
 
  
=== File Indexer Service not working even after enabling everything properly ===
+
Then, make sure the backend is preferred via ''System Settings > Multimedia > Audio and Video > Backend''.
  
This is caused due to a corrupted Nepomuk database. It may be remedied by moving the database or deleting it all together. Log out of KDE and issue this command from a virtual console:
+
=== Power management ===
  
$ mv ~/.kde4/share/apps/nepomuk ~/.kde4/share/apps/nepomuk_backup
+
==== No Suspend/Hibernate options ====
  
to move your existing (and corrupt) nepomuk database. It will be recreated when you log in again.
+
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.
  
=== Desktop does not respond for several seconds at startup ===
+
=== KMail ===
  
There is a bug in either [https://bugs.freedesktop.org/show_bug.cgi?id=58758 pulseaudio] or [https://bugs.kde.org/show_bug.cgi?id=312560 kde] that makes the desktop not being usable for a few seconds after it has showed up (for example if you click on the K-menu it does not appears until that waiting time has elapsed).
+
==== Clean Akonadi configuration to fix KMail ====
  
The workaround is to disable {{ic|/etc/xdg/autostart/pulseaudio.desktop}} by adding the following line at the end (do not omit the semicolon):
+
See [https://docs.kde.org/trunk5/en/pim/kmail2/clean-start-after-a-failed-migration.html this] document for detail.
  
NotShowIn=KDE;
+
If you want a backup, copy the following configuration directories:
  
Note that you could also remove that file, or renaming it (to pulseaudio.desktop.disable or the like) but then it will not load in other Desktop Managers, and will be restored by a package update.
+
$ cp -a ~/.local/share/akonadi ~/.local/share/akonadi-old
 +
$ cp -a ~/.config/akonadi ~/.config/akonadi-old
  
[http://linuxadvantage.blogspot.fr/2013/01/kde-rather-slow-to-start-pulseaudio.html Reference].
+
==== Empty IMAP inbox in KMail ====
  
=== Mysterious hangs/slowness after upgrade ===
+
For some IMAP accounts KMail will show the inbox as a top-level container (so it will not be possible to read messages there) with all other folders of this account inside.[https://bugs.kde.org/show_bug.cgi?id=284172]. To solve this problem simply disable the server-side subscriptions in the KMail account settings.
  
Try cleaning up your cache. Sometimes after an upgrade, the old cache might introduce strange, hard to debug behaviour such as unkillable shells, hangs when changing various settings and several other problems such as ark being unable to unrar or unzip or amarok not recognizing any of your musics.
+
==== Authorization error for EWS account in KMail ====
  
To clean up your cache run as your normal user:
+
While setting up EWS account in KMail, you may keep getting errors about failed authorization even for valid and fully working credentials. This is likely caused by broken communication between [[KWallet]] and KMail. To workaround the issue set a passsword via qdbus:
 +
 
 +
$ qdbus org.freedesktop.Akonadi.Resource.akonadi_ews_resource_0 /Settings org.kde.Akonadi.Ews.Wallet.setPassword "XXX"
 +
 
 +
=== Networking ===
  
  rm ~/.config/Trolltech.conf
+
==== Freezes when using Automount on a NFS volume  ====
  kbuildsycoca4 --noincremental
 
  
Hopefully, your problems are now fixed.
+
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].
  
=== Dolphin and File Dialogs are extremely slow to start everytime ===
+
=== Aggressive QXcbConnection journal logging ===
  
For me this was caused by the upower service, if you don't need it, just run :
+
See [[Qt#Disable/Change Qt journal logging behaviour]].
  
  systemctl disable upower
+
=== KF5/Qt 5 applications do not display icons in i3/FVWM/awesome ===
  systemctl mask upower
 
  
As far as I can tell it has no side effects, but then I use a desktop not a laptop.
+
See [[Qt#Configuration of Qt5 apps under environments other than KDE Plasma]].
  
== Other KDE projects ==
+
=== Problems with saving credentials and persistently occurring KWallet dialogs ===
  
=== Official kde-unstable ===
+
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.
  
When KDE is reaching beta or RC milestone, KDE "unstable" packages are uploaded to the [kde-unstable] repo. They stay there until KDE is declared stable and passes to [extra].
+
In case you find the dialogs to unlock the wallet annoying when applications want to access it, you can let the [[Display manager|display managers]] [[SDDM]] and [[LightDM]] unlock the wallet at login automatically, see [[KDE Wallet#Unlock KDE Wallet automatically on login]]. The first wallet needs to be generated by KWallet (and not user-generated) in order to be usable for system program credentials.
  
You may add it by adding:
+
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.
  
[kde-unstable]
+
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.
SigLevel = PackageRequired
 
Include = /etc/pacman.d/mirrorlist
 
  
to {{ic|/etc/pacman.conf}}
+
=== Discover does not show any applications ===
  
# kde-unstable is based upon testing. Therefore, you need to enable the repositories in the following order: '''kde-unstable, testing, core, extra, community-testing, community'''.
+
This can be solved by installing {{Pkg|packagekit-qt5}}.
# To update from a previous KDE installation, run: <code>pacman -Syu</code> or <code>pacman -S kde-unstable/kde</code>
 
# If you don't have KDE installed, you might have difficulties to install it by using groups (limitation of pacman)
 
# '''Subscribe and read the arch-dev-public mailing list'''
 
# Make sure [[#Distro_and_Upstream_bug_report|you make bug reports]] if you find any issues.
 
  
=== Trinity ===
+
=== High CPU usage of kscreenlocker_greet with NVIDIA drivers ===
  
From the release of KDE 4.x, the developers dropped support for KDE 3.5.x. Trinity Desktop Environment is a fork of KDE3 developed by Timothy Pearson ([http://trinitydesktop.org/ trinitydesktop.org]). This project aims to keep the KDE3.5 computing style alive, as well as polish off any rough edges that were present as of KDE 3.5.10. See [[Trinity]] for more info.
+
As described in [https://bugs.kde.org/show_bug.cgi?id=347772 KDE Bug 347772] NVIDIA OpenGL drivers and QML may not play well together with Qt 5. This may lead {{ic|kscreenlocker_greet}} to high CPU usage after unlocking the session. To work around this issue, set the {{ic|QSG_RENDERER_LOOP}} [[environment variable]] to {{ic|basic}}.
  
{{Warning|KDE 3 is no longer maintained and supported by the KDE developers. The "Trinity KDE" is maintained by the Trinity project commmunity. Use KDE 3 on your own risk, regarding any bugs, performance issues or security risks.}}
+
Then kill previous instances of the greeter with {{ic|killall kscreenlocker_greet}}.
  
==Bugs==
+
=== OS error 22 when running Akonadi on ZFS ===
  
===Distro and Upstream bug report===
+
If your home directory is on a [[ZFS]] pool, create a {{ic|~/.config/akonadi/mysql-local.conf}} file with the following contents:
  
It is preferrable that if you find a minor or serious bug, you should visit [https://bugs.archlinux.org the Arch Bug Tracker] or/and [http://bugs.kde.org KDE Bug Tracker] in order to report that. Make sure that you be clear on what you want to report.
+
[mysqld]
 +
innodb_use_native_aio = 0
  
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]].
+
See [[MariaDB#OS error 22 when running on ZFS]].
  
KDE 4 config files are usually located at
+
=== Some programs are unable to scroll when their windows are inactive ===
  
~/.kde4/share/config/
+
This is caused by the problematic way of GTK3 handling mouse scroll events. A workaround for this is to set [[environment variable]] {{ic|1=GDK_CORE_DEVICE_EVENTS=1}}. However, this workaround also breaks touchpad smooth scrolling and touchscreen scrolling.
  
and for app-specific configs
+
=== TeamViewer behaves slowly ===
  
~/.kde4/share/apps/
+
When using TeamViewer, it may behave slowly if you use smooth animations (such as windows minimizing). See [[#Disable compositing]] as a workaround.
  
 
== See also ==
 
== See also ==
  
* [http://www.kde.org KDE Homepage]
+
* [https://www.kde.org/ KDE homepage]
* [http://bugs.kde.org KDE Bug Tracker]
+
* [https://bugs.kde.org/ KDE bug tracker]
* [https://bugs.archlinux.org Arch Linux Bug Tracker]
+
* [https://blog.martin-graesslin.com/blog/kategorien/kde/ Martin Graesslin's blog]
* [http://websvn.kde.org KDE WebSVN]
 

Latest revision as of 17:54, 22 December 2019

KDE is a software project currently comprising 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 Package group. 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

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.

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. See Wayland Showstoppers 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

From the console

  • To start Plasma with xinit/startx, append exec startplasma-x11 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 XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland.[1]

Configuration

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

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.

Plasma themes can also be installed through System Settings > Workspace Theme > Plasma Theme > Get new themes from the Internet.

The KDE-Store offers more Plasma customization's, like SDDM themes and splash-screens.

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

Breeze is not directly available for Qt4 since it cannot be built without KDE 4 packages, which have been dropped from the extra repository in August 2018 (FS#59784). However you can install breeze-gtk and pick GTK as GUI Style by running qtconfig-qt4.

GTK

The recommended theme for a pleasant appearance in GTK applications is breeze-gtk, a GTK theme designed to mimic the appearance of Plasma's Breeze theme. Install kde-gtk-config (part of the plasma group) and select Breeze or Breeze-Dark as the GTK2/GTK3 theme in System Settings > Application Style > GNOME/GTK 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.

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/GTK Application Style > GTK2 Theme:. Numix-Frost-Light looks similar to Breeze.

Faces

Plasma and SDDM will both use a PNG file found at ~/.face.icon as a user's avatar. To configure with a graphical interface, you can use System Settings > Accounts Details > User Manager, which may first need to be installed (see the user-manager package). The default icon can be found in /usr/share/sddm/faces/.

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 New Plasma 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. [2] 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. [3] 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.
Tip: Since some icon themes do not inherit from the default icon theme, some icons may be missing. To inherit from the Breeze, add breeze to the Inherits= array in /usr/share/icon/theme-name/index.theme, for example: Inherits=breeze,hicolor. You need to reapply this patch after every update to the icon theme, consider using Pacman hooks to automate the process.

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 and ffmpegthumbs.

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

In Dolphin, navigate to Control > Configure Dolphin... > 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#Enable Usershares, after which sharing in Dolphin should work out of the box after restarting Samba.

Tip: Use * (asterisk) for both username and password when accessing a Windows share without authentication in Dolphin's prompt.

Unlike GTK file browsers which utilize GVfs also for the launched program, opening files from Samba shares in Dolphin via KIO makes Plasma copy the whole file to the local system first with most programs (VLC is an exception). To workaround this, you can use 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 possibility 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. See Samba#Manual mounting and Samba#Automatic mounting.

An GUI solution is available with samba-mounter-gitAUR, which offers basically the same functionality via an easy to use option located at System Settings > Network Drivers. However, it might break with new KDE Plasma versions.

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 management

Install powerdevil for an integrated Plasma power managing service. This service offers additional power saving features, monitor brightness control (if supported) and battery reporting including peripheral devices.

An alternative package without NetworkManager and Bluez dependencies is provided by powerdevil-lightAUR.

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. [4] (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.

Autostart

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 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-gstreamerAUR, phonon-qt5-gstreamerphonon-qt4-vlcAUR, 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. The Gstreamer backend has some optional codec dependency, install them as needed:

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 via the phononsettings application.
  • According to the KDE forums, the VLC backend lacks support for ReplayGain.
  • If using the VLC backend, you may experience crashes every time Plasma wants to send you an audible warning and in quite a number of other cases as well [5]. A possible fix is to rebuild the VLC plugins cache:
# /usr/lib/vlc/vlc-cache-gen /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.

  • sddm-kcm — KDE Config Module for SDDM.
https://cgit.kde.org/sddm-kcm.git || sddm-kcm
  • kde-gtk-config — GTK2 and GTK3 Configurator for KDE.
https://cgit.kde.org/kde-gtk-config.git || kde-gtk-config
  • 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-wacomtablet
  • Kcmsystemd — systemd control module for KDE.
https://github.com/rthomsen/kcmsystemd || systemd-kcmAUR

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.

Web browsers

The following web browsers can integrate with Plasma:

  • Konqueror — Part of the KDE project, supports two rendering engines – KHTML and the Chromium-based Qt WebEngine.
https://konqueror.org/ || konqueror
  • Falkon — A Qt web browser with Plasma integration features, previously known as Qupzilla. It uses Qt WebEngine.
https://userbase.kde.org/Falkon/ || falkon
  • 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
Tip: Starting from Plasma 5.13, one can integrate Firefox or Chrome with Plasma: providing media playback control from the Plasma tray, download notifications and find open tabs in KRunner. Install plasma-browser-integration and the corresponding browser add-on. Chrome/Chromium support should already be included, for Firefox add-on see Firefox#KDE/GNOME integration.

PIM

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

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

Install akonadi. For additional addons, install kdepim-addons.

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

See also FS#32878.

MySQL

By default Akonadi will use /usr/bin/mysqld (MariaDB by default, see MySQL for alternative providers) to run a managed MySQL instance with the database stored in ~/.local/share/akonadi/db_data/.

System-wide MySQL instance

Akonadi supports using the system-wide MySQL for its database.[6]

Tango-view-fullscreen.pngThis article or section needs expansion.Tango-view-fullscreen.png

Reason: Add instructions. (Discuss in Talk:KDE#)
~/.config/akonadi/akonadiserverrc
[%General]
Driver=QMYSQL

[QMYSQL]
Host=
Name=akonadi_username
Options="UNIX_SOCKET=/run/mysqld/mysqld.sock"
StartServer=false
PostgreSQL

Akonadi supports either using the existing system-wide PostgreSQL instance, i.e. postgresql.service, or running a PostgreSQL instance with user privileges and the database in ~/.local/share/akonadi/db_data/.

Per-user PostgreSQL instance

Install postgresql and postgresql-old-upgrade.

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

~/.config/akonadi/akonadiserverrc
[%General]
Driver=QPSQL
Note:
  • When Akonadi starts, it will create the [QPSQL] section and set the appropriate variables in it.
  • The database will be stored in ~/.local/share/akonadi/db_data/.

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

Note:
System-wide PostgreSQL instance

This requires an already configured and running PostgreSQL.

Create a PostgreSQL user account for your user:

[postgres]$ createuser username

Create a database for Akonadi:

[postgres]$ createdb -O username --locale=en_US.UTF-8 -T template0 akonadi-username

Configure Akonadi to use the system-wide PostgreSQL:

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

[QPSQL]
Host=/run/postgresql
Name=akonadi-username
StartServer=false
Note: Custom port, username and password can be specified with options Port=, User=, Password= in the [QPSQL] section.

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

SQLite

To use SQLite edit Akonadi configuration file to match the configuration below:

~/.config/akonadi/akonadiserverrc
[%General]
Driver=QSQLITE3
Note:
  • When Akonadi starts, it will create the [QSQLITE3] section and set the appropriate variables in it.
  • The database will be stored as ~/.local/share/akonadi/akonadi.db.
Disabling Akonadi

See this section in the KDE userbase.

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.

KDE Connect

KDE Connect provides several features to connect your Android phone with your Linux desktop:

  • 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. If you want to browse your phone's filesystem, you need to install sshfs as well and configure filesystem exposes in your Android app.

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. For GNOME users, better integration can be achieved by installing gnome-shell-extension-gsconnectAUR instead of kdeconnect.

If you use a firewall, you need to open UDP and TCP ports 1714 through 1764. See https://community.kde.org/KDEConnect#Troubleshooting.

Tips and tricks

Use a different window manager

The component chooser settings in Plasma does not allow changing the window manager anymore. [7] In order to change the window manager used you need to set the KDEWM environment variable before KDE startup. [8] 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
Note: When using i3 window manager with Plasma, it may be necessary to manually set dialogs to open in floating mode in order for them to correctly appear. For more information, see I3#Correct handling of floating dialogs.

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 xinit configuration:

~/.xinitrc
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 provides additional options to System Settings > Display and Monitor.

KWin-lowlatency

KWin-lowlatency is a attempt to reduce latency and stuttering in the popular KWin compositor and is available as kwin-lowlatencyAUR.

Configuring ICC profiles

To enable ICC profiles in Plasma, install colord-kde. This provides additional options to System Settings > Color Corrections.

ICC profiles can be imported using Add Profile.

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 ""

Disable bookmarks showing in application menu

With Plasma Browser integration installed, KDE will show bookmarks in the application launcher.

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

$ mkdir ~/.local/share/kservices5
$ sed 's/EnabledByDefault=true$/EnabledByDefault=false/' /usr/share/kservices5/plasma-runner-bookmarks.desktop > ~/.local/share/kservices5/plasma-runner-bookmarks.desktop

Troubleshooting

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.

Configuration related

Many problems in KDE are related to its 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 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 on the KDE bug tracker only if it is an official widget. If it is not, it is recommended to find the entry on the KDE Store 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/ and run the following command:

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

This command will rename all Plasma related configuration files 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, Ark being unable to extract archives or Amarok not recognizing any of your music. This solution can also resolve problems with KDE and Qt applications looking bad after an update.

Rebuild the cache using the following commands:

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

Optionally, empty the ~/.cache/ folder contents, however, this will also clear the cache of other applications:

$ rm -rf ~/.cache/*

Volume control, notifications or multimedia keys do not work

Hiding certain items in the System Tray settings (e.g. Audio Volume, Media Player or Notifications) also disables related features. Hiding the Audio Volume disables volume control keys, Media Player disables multimedia keys (rewind, stop, pause) and hiding Notifications disables showing notifications.

Login Screen KCM does not sync cursor settings to SDDM

The Login Screen KCM reads your cursor settings from ~/.config/kcminputrc, without this file no settings are synced. The easiest way to generate this file is to change your cursor theme in System Settings > Cursors, then change it back to your preferred cursor theme.

Graphical problems

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.

Getting current state of KWin for support and debug purposes

This command prints out a 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

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

Enable transparency

If you use a transparent background without enabling the compositor, you will get the message:

This color scheme uses a transparent background which does not appear to be supported on your desktop

In System Settings > Display and Monitor > Compositor, check Enable compositor on startup and restart Plasma.

Disable compositing

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

Flickering in fullscreen when compositing is enabled

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

Screen tearing with NVIDIA

See NVIDIA/Troubleshooting#Avoid screen tearing in KDE (KWin).

Plasma cursor sometimes shown incorrectly

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

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

Execute the following command:

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

Unusable screen resolution set

Your local configuration settings for kscreen can override those set in xorg.conf. Look for kscreen configuration files in ~/.local/share/kscreen/ and check if mode is being set to a resolution that is not supported by your monitor.

Blurry icons in System tray

In order to add icons to tray, applications often make use of the library appindicator. If your icons are blurry, check which version of libappindicator you have installed. If you only have libappindicator-gtk2 installed, you can install libappindicator-gtk3 or libappindicator-sharp as an attempt to get clear icons.

Sound problems

Note: First make sure you have alsa-utils installed.

No sound after suspend

If there is no sound after suspending and if KMix does not show audio devices which should be there, restarting plasmashell 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.

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-vlcAUR or phonon-qt5-vlc.

Then, make sure the backend is preferred via System Settings > Multimedia > Audio and Video > Backend.

Power management

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.

KMail

Clean Akonadi configuration to fix KMail

See this document for detail.

If you want a backup, copy the following configuration directories:

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

Empty IMAP inbox in KMail

For some IMAP accounts KMail will show the inbox as a top-level container (so it will not be possible to read messages there) with all other folders of this account inside.[9]. To solve this problem simply disable the server-side subscriptions in the KMail account settings.

Authorization error for EWS account in KMail

While setting up EWS account in KMail, you may keep getting errors about failed authorization even for valid and fully working credentials. This is likely caused by broken communication between KWallet and KMail. To workaround the issue set a passsword via qdbus:

$ qdbus org.freedesktop.Akonadi.Resource.akonadi_ews_resource_0 /Settings org.kde.Akonadi.Ews.Wallet.setPassword "XXX"

Networking

Freezes when using Automount on a NFS volume

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

Aggressive QXcbConnection journal logging

See Qt#Disable/Change Qt journal logging behaviour.

KF5/Qt 5 applications do not display icons in i3/FVWM/awesome

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

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 display managers SDDM and LightDM unlock the wallet at login automatically, see KDE Wallet#Unlock KDE Wallet automatically on login. 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.

Discover does not show any applications

This can be solved by installing packagekit-qt5.

High CPU usage of kscreenlocker_greet with NVIDIA drivers

As described in KDE Bug 347772 NVIDIA OpenGL drivers and QML may not play well together with Qt 5. This may lead kscreenlocker_greet to high CPU usage after unlocking the session. To work around this issue, set the QSG_RENDERER_LOOP environment variable to basic.

Then kill previous instances of the greeter with killall kscreenlocker_greet.

OS error 22 when running Akonadi on ZFS

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

[mysqld]
innodb_use_native_aio = 0

See MariaDB#OS error 22 when running on ZFS.

Some programs are unable to scroll when their windows are inactive

This is caused by the problematic way of GTK3 handling mouse scroll events. A workaround for this is to set environment variable GDK_CORE_DEVICE_EVENTS=1. However, this workaround also breaks touchpad smooth scrolling and touchscreen scrolling.

TeamViewer behaves slowly

When using TeamViewer, it may behave slowly if you use smooth animations (such as windows minimizing). See #Disable compositing as a workaround.

See also