Difference between revisions of "KDE"

From ArchWiki
Jump to navigation Jump to search
m (→‎Plasma: typo)
(→‎Graphical problems: added a fix for a minor, but annoying, problem)
 
Line 1: Line 1:
{{Merge|KDE Desktop Tricks}}
+
[[Category:KDE]]
[[Category:Desktop environments (English)]]
+
[[ar:KDE]]
{{i18n|KDE}}
+
[[cs:KDE]]
[[de:KDE]]
+
[[de:Plasma]]
 +
[[es:KDE]]
 +
[[fa:KDE]]
 
[[fr:KDE]]
 
[[fr:KDE]]
 +
[[it:KDE]]
 +
[[ja:KDE]]
 +
[[pl:KDE]]
 +
[[pt:KDE]]
 +
[[ru:KDE]]
 +
[[zh-hans:KDE]]
 +
[[zh-hant:KDE]]
 +
{{Related articles start}}
 +
{{Related|Desktop environment}}
 +
{{Related|Display manager}}
 +
{{Related|Window manager}}
 +
{{Related|Qt}}
 +
{{Related|SDDM}}
 +
{{Related|Dolphin}}
 +
{{Related|KDE Wallet}}
 +
{{Related|KDevelop}}
 +
{{Related|Trinity}}
 +
{{Related|Uniform Look for Qt and GTK Applications}}
 +
{{Related articles end}}
  
{{Article summary start}}
+
KDE is a software project currently comprising a [[desktop environment]] known as Plasma, a collection of libraries and frameworks (KDE Frameworks) and several applications (KDE Applications) as well. KDE upstream has a well maintained [https://userbase.kde.org/ UserBase wiki]. Detailed information about most KDE applications can be found there.
{{Article summary text|For users on Linux and Unix, KDE offers a full suite of user workspace applications which allow interaction with these operating systems in a modern, graphical user interface. This article covers its installation, configuration, and troubleshooting.}}
 
{{Article summary text|KDE uses the [[Qt]] toolkit.}}
 
{{Article summary heading|Overview}}
 
{{Article summary text|{{Graphical user interface overview}}}}
 
{{Article summary heading|Related}}
 
{{Article summary wiki|Plasma}}
 
{{Article summary wiki|Qt}}
 
{{Article summary wiki|KDevelop 4}}
 
{{Article summary end}}
 
  
From [http://www.kde.org/community/whatiskde/softwarecompilation.php KDE - KDE Software Compilation]:
+
== Installation ==
  
:''The KDE Software Compilation grew out of the history of the KDE Project. In its inception, KDE was formed to create a beautiful, functional and free desktop computing environment for Linux and similar operating system. At the time, these systems lacked a graphical user environment that could rival the offerings from the larger proprietary operating system vendors. KDE was created to fill this gap.''
+
=== Plasma ===
  
:''The KDE Software Compilation is the set of libraries, workspaces, and applications produced by KDE that share this common heritage, and continue to use the synchronized release cycle. Software may move in and out of this semi-formally defined collection depending on the particular needs of the contributors who are working on that software, with exceptions made to ensure that binary compatibility remains at the library level throughout any major release of the compilation.''
+
Before installing Plasma, make sure you have a working [[Xorg]] installation on your system.
  
From [http://www.kde.org/download/ KDE - Getting KDE Software]:
+
[[Install]] the {{Pkg|plasma-meta}} meta-package or the {{Grp|plasma}} group. For differences between {{Pkg|plasma-meta}} and {{Grp|plasma}} reference [[Package group]]. Alternatively, for a more minimal Plasma installation, install the {{Pkg|plasma-desktop}} package.
  
:''KDE software consists of a large number of individual applications and a desktop workspace as a shell to run these applications. You can run KDE applications just fine on any desktop environment. KDE applications are built to integrate well with your system's components. By using also KDE workspace, you get even better integration of your applications with the working environment while lowering system resource needs.''
+
To enable support for [[Wayland]] in Plasma, also install the {{Pkg|plasma-wayland-session}} package.
  
==Overview==
+
=== KDE applications ===
  
'''KDE 4.7''' Software Compilation is the current major release of KDE that includes a number of improvements and bug fixes.  The new Arch package set for KDE makes it possible to only install those applications you like.''
+
To install the full set of KDE Applications, install the {{Grp|kde-applications}} group or the {{Pkg|kde-applications-meta}} meta-package. Note that this will only install applications, it will not install any version of Plasma.
  
Important features of the Arch Linux KDE SC in short:
+
=== Unstable releases ===
* '''Split packages'''; for more Information see [[KDE_Packages|KDE Packages]] and [[DeveloperWiki:Splitting_KDE|Splitting KDE]].
 
* You can use different Phonon backends, like Gstreamer or VLC
 
* Meta packages ensure a smooth upgrade and emulate the old monolith packages for those who prefer them.
 
  
Important hints for upgraders:
+
See [[Official repositories#kde-unstable]]
* Always check if your mirror is '''up to date'''.
 
* pacman will ask you to replace '''all''' kde packages with kde-meta packages.
 
* '''Do not force an update'''.  If pacman complains about conflicts please '''file a bug report'''.
 
* You can remove the meta packages and the sub packages you do not need after the update.
 
* If you do not like split packages just keep using the kde-meta packages.
 
  
Information about upstream changes is available [http://kde.org/announcements/4.7 here]
+
== 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.}}
  
==Installation==
+
Plasma can be started either using a [[display manager]], or from the console.
  
=== Full install ===
+
=== Using a display manager ===
  
To install the entire KDE set, first '''fully upgrade your system''':
+
* 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 -Syu
+
=== From the console ===
  
and then:
+
* 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]
  
# pacman -S kde
+
== Configuration ==
  
or
+
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}}.
  
# pacman -S kde-meta
+
=== Personalization ===
  
{{Note|Learn about the difference between kde and kde-meta packages in the [[KDE Packages]] article.}}
+
==== Plasma desktop ====
  
If you need language files:
+
===== Themes =====
  
# pacman -S kde-l10n-yourlanguagehere
+
[https://store.kde.org/browse/cat/104/ Plasma themes] define the look of panels and Plasma widgets. 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].
  
e.g. kde-l10n-'''de''', for the German language.
+
Plasma themes can also be installed through ''System Settings > Global Theme > Get New Global Themes...''.
  
{{Note| KDE 4.x is '''modular'''; you can install your preferred KDE applications without having to install an entire set of packages.  See [[KDE Packages]] for more information.}}
+
The [https://store.kde.org/ KDE Store] offers more Plasma customization's, like [[SDDM]] themes and splash-screens.
  
{{Note| KDE 4.x does not need Gamin or Fam packages for monitoring changes on local files and directories [[#Monitoring_changes_on_local_files_and_directories|see more]]}}
+
====== GTK application appearance ======
  
=== Minimal install ===
+
{{Tip|For Qt and GTK theme consistency, see [[Uniform look for Qt and GTK applications]].}}
  
If you want to have a minimal installation of the KDE SC, here is an example:
+
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 > Configure GNOME/GTK Application Style...''.
  
# pacman -S kdebase kde-l10n-yourlanguagehere phonon-vlc
+
{{Out of date|The Plasma GTKd background service overwrites GTK settings on Plasma startup.}}
  
You can choose phonon-gstreamer instead phonon-vlc.
+
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}}.
  
{{Note| You need to install a ttf-* package. phonon-vlc already requires ttf-freefonts, but when using phonon-gstreamer you should add ttf-dejavu or another too. For more information see {{Bug|26012}}.}}
+
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'' > ''Configure GNOME/GTK Application Style...'' > ''GTK2 theme:''. Numix-Frost-Light looks similar to Breeze.
  
==Starting KDE==
+
===== Faces =====
  
[[Daemon#Performing daemon actions manually|Start the dbus daemon]] and add dbus to your [[Daemons#Starting on Boot|DAEMONS array]] so it starts automatically on boot.
+
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/}}.
  
Starting KDE depends on your preferences. Basically there are two ways of starting KDE. Using '''KDM''' or '''xinitrc'''.
+
===== Widgets =====
  
=== Using KDM (KDE Display Manager)===
+
Plasmoids are little scripted (plasmoid scripts) or coded (plasmoid binaries) KDE applications designed to enhance the functionality of your desktop.
''It is highly recommended to get familiar with the [[Display Manager|full article]] concerning display managers, before you make any changes. See also [[KDM]] Wiki page.''
 
  
==== Starting KDM through /etc/inittab [''recommended''] ====
+
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.
  
Edit '''{{ic|/etc/inittab}}''' and comment out:
+
Many Plasmoid binaries are available from the [https://aur.archlinux.org/packages.php?K=plasmoid AUR].
#id:3:initdefault:
+
 
+
===== Sound applet in the system tray =====
[...]
+
 
+
[[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.
#x:5:respawn:/usr/bin/xdm -nodaemon
+
 
 +
{{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}}.}}
  
Then uncomment:
+
===== Disable panel shadow =====
  
id:5:initdefault:
+
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:
 
[...]
 
 
x:5:respawn:/usr/bin/kdm -nodaemon
 
  
==== Starting KDM as a daemon ====
+
$ xprop -remove _KDE_NET_WM_SHADOW
Add "'''kdm'''" (without the quotes) to daemons array in '''{{ic|/etc/rc.conf}}'''
 
  
DAEMONS=(syslog-ng dbus network crond ... '''kdm''')
+
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:
  
{{Note| In both methods KDM loads Xorg automatically.}}
+
{{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>}}
  
===Using xinitrc===
+
Set execution permissions for the script:
''The meaning and usage of '''xinitrc''' is very well described [[Xinitrc|here]].
 
  
Edit '''{{ic|/home/}}'''{{ic|''your-username''}}'''{{ic|/.xinitrc}}'''. Then uncomment:
+
# chmod 755 /usr/local/bin/kde-no-shadow
exec ck-launch-session startkde
 
After a reboot or/and login, each execution of Xorg ('''startx''' or '''xinit''') will start KDE automatically.
 
  
{{Warning| By doing this you may have restart/shutdown functions disabled in your KDE menu.}}
+
The script can be run on login with ''Add Script'' in ''Autostart'':
  
{{Note| If you want to start Xorg at boot, please read [[Start X at boot]] article.}}
+
$ kcmshell5 autostart
  
==Configuration==
+
==== Window decorations ====
  
{{Note| Configuring KDE is primarily done in ''''System Settings''''. There are also a few other options available for the desktop with 'Desktop Settings' when you right click the desktop.}}
+
[https://store.kde.org/browse/cat/114/ Window decorations] can be changed in ''System Settings > Application Style > Window Decorations''.
  
For other personalization options not covered below such as activities, different wallpapers on one cube, etc please refer to the [[Plasma]] wiki page.
+
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].
  
===Personalization===
+
==== Icon themes ====
  
How to set up the KDE desktop to your personal style; use different Plasma themes, window decorations and icon themes.  
+
Icon themes can be installed and changed on ''System Settings > Icons''.
  
====Plasma Desktop====
+
{{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.}}
  
[[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".
+
{{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.}}
  
=====Themes=====
+
==== Space efficiency ====
  
[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 [http://aur.archlinux.org/packages.php?O=0&K=plasmatheme&do_Search=Go AUR].
+
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.
  
=====Widgets=====
+
==== Thumbnail generation ====
Plasmoids are little scripted or coded KDE apps that enhance the functionality of your desktop.  There are two kinds, plasmoid scripts and plasmoid binaries.
 
  
Plasmoid binaries must be installed using PKGBUILDS from [http://aur.archlinux.org/packages.php?O=0&K=plasmoid&do_Search=Go&PP=25&SO=d&SB=v AUR].  Or write your own PKGBUILD.
+
To allow thumbnail generation for media or document files on the desktop and in Dolphin, install {{Pkg|kdegraphics-thumbnailers}} and {{Pkg|ffmpegthumbs}}.
  
The easiest way to install plasmoid scripts is by right-clicking onto a panel or the desktop:
+
Then enable the thumbnail categories for the desktop via ''right click'' on the ''desktop background'' > ''Configure Desktop'' > ''Icons'' > ''Configure Preview Plugins...''.
  
  Add Widgets -> Get new Widgets -> Download Widgets
+
In ''Dolphin'', navigate to ''Control'' > ''Configure Dolphin...'' > ''General'' > ''Previews''.
  
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.
+
=== Night Color ===
  
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.
+
Plasma provides a [[Redshift]]-like feature (working on both [[Xorg]] and [[Wayland]]) called Night Color. It makes the colors on the screen warmer to reduce eye strain at the time of your choosing. It can be enabled in ''System Settings > Display and Monitor > Night Color''.
  
====Window Decorations====
+
=== Printing ===
  
[http://kde-look.org/index.php?xcontentmode=75 Window decorations] can be changed in
+
{{Tip|Use the [[CUPS]] web interface for faster configuration. Printers configured in this way can be used in KDE applications. }}
System Settings -> Workspace Appearance -> Window Decorations
 
There you can also directly download and install more themes with one click and some are available on [http://aur.archlinux.org/packages.php?O=0&K=kdestyle&do_Search=Go&PP=25&SO=d&SB=v AUR].
 
  
====KDE 4 Theme Integration with GTK Applications====
+
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]].
Please go to [[Uniform Look for QT and GTK Applications]].
 
  
====Icon Themes====
+
=== Samba/Windows support ===
Not many full system icons themes are available for KDE 4.  You can open up '''System Settings > Application Appearance > Icons''' and browse for new ones or install them manually. Many of them can be found on [http://www.kde-look.org/ kde-look.org].
 
  
====Arch Linux Logo Icon in Kicker menu====
+
If you want to have access to Windows services, install [[Samba]] (package {{Pkg|samba}}).
Right click on the Kicker menu button, press '''Application launcher settings''' and then press the icon on the '''right'''. Then you may choose an Arch Linux icon or any other icon that will replace the default one.
 
  
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/}}.
+
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.
  
====Fonts====
+
{{Tip|Use {{ic|*}} (asterisk) for both username and password when accessing a Windows share without authentication in Dolphin's prompt.}}
  
===== Fonts in KDE look poor =====
+
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.
  
Try installing the [http://www.archlinux.org/packages/extra/any/ttf-dejavu/ ttf-dejavu] and [http://www.archlinux.org/packages/community/any/ttf-liberation/ ttf-liberation] packages.  
+
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]].
  
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.
+
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.
  
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}}).
+
=== KDE Desktop activities ===
  
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).  
+
[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.
  
Note too that Gnomes' Font Preferences will also do this if you use both desktop environments.
+
=== Power management ===
  
===== Fonts are huge or seems disproportional =====
+
[[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.
  
Try to force fonts DPI to '''96''' on '''System Settings > Application Appearance > Fonts.'''
+
An alternative package without [[NetworkManager]] and [[Bluez]] dependencies is provided by {{AUR|powerdevil-light}}.
  
If it does not work try set DPI directly on Xorg configuration [[Xorg#Setting_DPI_manually|here]].
+
{{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]}}
  
====Space efficiency====
+
{{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]].}}
KDE is often '''criticized''' for being bloated.  
 
  
The user might get this perception from seeing''' many toolbars and pretty big scaled icons in the applications'''. One thing that improved the situation was the new Kwin-Theme that came with KDE SC 4.4.* with the more elegant buttons that one can also resize. '''KDE Apps allows to hide many toolbars, menubars and statusbars'''.
+
=== Autostart ===
  
=====All sorts of *bars=====
+
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.
Most toolbars of a program can be removed in the menubar-entry "'''Settings'''". There you often can hide the statusbar and often all toolbars. The last step should be to remove the menubar itself via '''Ctrl + M'''.
 
  
If you do not want to remove any bars you can still make them smaller or remove the text via:
+
{{Note|
System Settings -> Application Appearance -> Style -> Fine Tuning ->  (Main toolbar text / Secondary toolbar text)
+
* 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]].
 +
}}
  
Since most aspect ratios of modern flat screens are wider than 4:3 it could be reasonable to put the toolbar '''at the left or right of a window''' to artificially stretch windows more to the monitors aspect ratio.
+
* Place [[Desktop entries]] (i.e. ''.desktop'' files) in the appropriate [[XDG Autostart]] directory.
  
=====Plasma=====
+
* Place or symlink shell scripts in one of the following directories:
There are also some settings and modifications you can apply to your plasmoids to make KDE less space wasting.
 
  
For example, the "Digital Clock" wastes more space than the "Analogue Clock". The little plasma icon ("Cashew") that one can see in the panel can be hidden by locking the widgets via rightclicking onto the panel.
+
:; {{ic|~/.config/plasma-workspace/env/}}: for executing scripts at login before launching Plasma.
 +
:; {{ic|~/.config/autostart-scripts/}}: for executing scripts at login.
 +
:; {{ic|~/.config/plasma-workspace/shutdown/}}: for executing scripts when Plasma exits.
  
If you have got many tasks in your task-manager you should consider using ''Smooth-tasks''.
+
=== Phonon ===
  
This alternative task-manager allows you to just display the icons of a task thus using less space but still maintaining the ability of the user to distinguish the different tasks.
+
From [[Wikipedia:Phonon (software)|Wikipedia]]:
  
Install [http://aur.archlinux.org/packages.php?ID=29410 smooth-tasks] from the [[AUR]].
+
: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.
  
After installing and substituting it with the original task-manager you should have a deep look at the settings since they are much broader.
+
: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.
One way of using the features of smooth-tasks could be to only display the icons of tasks and move the panel to the left or right of the screen. This is most useful on widescreens.
 
  
On very small screens it could be reasonable to set the bottom-panel to auto-hide completely.
+
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).
  
For netbooks there is a special workspace, called Plasma Netbook, that makes better use of the screen:
+
==== Which backend should I choose? ====
  
System Settings -> Workspace Behavior -> Workspace -> Workspace Type
+
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}}).
  
=====KWin=====
+
[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:
Windows decorations can also be resized by decreasing button size in the decoration thus making the whole top border smaller:
 
System Settings -> Workspace Appearance -> Window Decorations -> Configure Decoration... -> Button size
 
You could also remove the side-border of all windows via:
 
System Settings -> Workspace Appearance -> Window Decorations -> Configure Decoration... -> Border size
 
  
=== Networking ===
+
* {{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.
  
NetworkManager support has been added in KDE SC.  See [[Networkmanager#KDE4|NetworkManager]] for more information.
+
In the past other backends were developed as well but are no longer maintained and their AUR packages have been deleted.
  
Also you can use [http://aur.archlinux.org/packages.php?ID=48672/ wicd-kde].
+
{{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}}
 +
}}
  
=== Printing ===
+
== Applications ==
  
{{Tip|Use the [[Cups]] web interface for faster configuration.}}
+
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.
  
The printers are configured in this way can be found in applications KDE.  
+
Aside from the programs provided in KDE Applications, there are many other applications available that can complement the Plasma desktop. Some of these are discussed below.
  
You can also choose the printer configuration through '''System Settings -> Printer Configuration'''. To use this method, you must first install the packages:
+
=== System administration ===
  
# pacman -S kdeadmin-system-config-printer-kde cups
+
==== Terminate Xorg server through KDE System Settings ====
  
{{Note|If you are getting the following error: ''"The service 'Printer Configuration' does not provide an interface 'KCModule' with keyword 'system-config-printer-kde/system-config-printer-kde.py' The factory does not support creating components of the specified type."''}}
+
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.
This means you need to start the cupsd daemon first.
 
  
{{Note|If you are getting the following error: ''"There was an error during CUPS operation: 'cups-authorization-canceled' "''}}
+
==== KCM ====
This means you need to give the user rights to manage printers.
 
For CUPS, this is set in '''/etc/cups/cupsd.conf'''.<br>
 
Adding '''lp''' to '''SystemGroup''' allows anyone who can print to configure printers. You can, of course, add another group than '''lp'''.
 
{{hc|/etc/cups/cupsd.conf|# Administrator user group...
 
SystemGroup sys root lp}}
 
  
===Samba/Windows support===
+
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''.
  
If you want to have access to Windows services:
+
* {{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}}}}
  
pacman -S samba
+
More KCMs can be found at [https://www.linux-apps.com/search?projectSearchText=KCM linux-apps.com].
  
You may then configure your Samba shares through
+
=== Desktop search ===
  
  System Settings -> Sharing -> Samba
+
KDE implements desktop search with a software called [[Baloo]], a file indexing and searching solution.
  
=== KDE Desktop Activities ===
+
=== Web browsers ===
  
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.
+
The following web browsers can integrate with Plasma:
Since KDE 4.5, the feature of changing Desktop Activities has been simplified.
 
  
On your desktop, click the Cashew Plasmoid and on the pop-up window press "Activities".
+
* {{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}}}}
  
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.
+
{{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]].}}
  
===Power Saving===
+
=== PIM ===
  
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).
+
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.
  
==== How to enable Cpufreq based power saving ====
+
==== Akonadi ====
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.  While some distributions use the {{ic|ondemand}} cpufreq governor by default, Arch does not.
 
  
As a prerequisite to the following, you should carefully read through the [[cpufreq|wiki article on cpufreq]] and ensure that the appropriate kernel modules are loaded.  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.
+
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).
  
1. If you have not already done so, install the {{ic|cpufrequtils}} package (for the {{ic|cpufreq-set}} utility):
+
Install {{Pkg|akonadi}}. For additional addons, install {{Pkg|kdepim-addons}}.
pacman -S cpufrequtils
 
  
2. Next, you will need to grant access to {{ic|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
+
{{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:
%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:
+
  # pacman -S akonadi --assume-installed mariadb
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.
+
See also {{Bug|32878}}.
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
 
 
}}
 
}}
  
{{Note | 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}}.
+
===== MySQL =====
 +
 
 +
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/}}.
 +
 
 +
====== System-wide MySQL instance ======
 +
 
 +
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]
 +
 
 +
{{Expansion|Add instructions.}}
 +
 
 +
{{hc|~/.config/akonadi/akonadiserverrc|2=
 +
[%General]
 +
Driver=QMYSQL
 +
 
 +
[QMYSQL]
 +
Host=
 +
Name=akonadi_''username''
 +
Options="UNIX_SOCKET=/run/mysqld/mysqld.sock"
 +
StartServer=false
 
}}
 
}}
  
===Monitoring changes on local files and directories===
+
===== PostgreSQL =====
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.
 
  
==System Administration==
+
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/}}.
  
===Set keyboard layout in order switch language inputs===
+
====== Per-user PostgreSQL instance ======
In order to do that, navigate to
 
    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===
+
[[Install]] {{Pkg|postgresql}} and {{Pkg|postgresql-old-upgrade}}.
Navigate to
 
    System Settings -> Input Devices -> Keyboard -> Advanced (tab) > "Key Sequence to kill the X server" submenu
 
and tick the checkbox.
 
  
===Useful KCM===
+
Edit Akonadi configuration file so that it has the following contents:
  
KCM means KConfig Module. This modules help you to configure you system providing a interface on System Settings.
+
{{hc|~/.config/akonadi/akonadiserverrc|2=
 +
[%General]
 +
Driver=QPSQL
 +
}}
  
'''Configuration for look&feel of your GTK apps.'''
+
{{Note|
*[https://aur.archlinux.org/packages.php?ID=45462 chakra-gtk-config]
+
* When Akonadi starts, it will create the {{ic|[QPSQL]}} section and set the appropriate variables in it.
*[https://aur.archlinux.org/packages.php?ID=40980 kcm-gtk]
+
* The database will be stored in {{ic|~/.local/share/akonadi/db_data/}}.
*[https://aur.archlinux.org/packages.php?ID=40582 kcm-qt-graphicssystem]
+
}}
  
'''Configuration for the GRUB2 bootloader.'''
+
Start Akonadi with {{ic|akonadictl start}}, and check its status: {{ic|akonadictl status}}.
*[https://aur.archlinux.org/packages.php?ID=47871 grub2-editor]
 
*[https://aur.archlinux.org/packages.php?ID=45816 kcm-grub2]
 
  
'''Configuration for Synaptics driver based touchpads.'''
+
{{Note|
*[https://aur.archlinux.org/packages.php?ID=35531 kcm_touchpad]
+
* 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]].
 +
}}
  
'''Configuration for main system config file rc.conf.'''
+
====== System-wide PostgreSQL instance ======
*[https://aur.archlinux.org/packages.php?ID=47842 kcm-rcconf-settings]
 
  
'''Configuration for [[Firewalls#ufw|UFW]]'''
+
This requires an already configured and running [[PostgreSQL]].
*[https://aur.archlinux.org/packages.php?ID=46880 kcm-ufw]
 
  
'''Configuration for Policy Kit'''
+
Create a PostgreSQL user account for your user:
*[https://aur.archlinux.org/packages.php?ID=54016 kcm-polkit-kde-git]
 
  
'''Configuration for Wacom Tablet'''
+
[postgres]$ createuser ''username''
*[https://aur.archlinux.org/packages.php?ID=41960 kcm-wacomtablet]
 
  
More KCM can be found [http://kde-apps.org/index.php?xcontentmode=273 here].
+
Create a database for Akonadi:
  
==Desktop Search and Semantic Desktop==
+
[postgres]$ createdb -O ''username'' --locale=en_US.UTF-8 -T template0 akonadi-''username''
Most users who freshly install KDE are wondering what functionality the following four pieces of software are able to offer. Most features are still somehow hidden under the hood and yet not many applications featured in the KDE SC are using these interfaces. This chapter intends to first explain the features and then convince the user of the power these tools offer once properly integrated into KDE. The following sections are more or less a roughly shortened version of [http://thomasmcguire.wordpress.com/2009/10/03/akonadi-nepomuk-and-strigi-explained/  this blogpost].
 
  
===Soprano===
+
Configure Akonadi to use the system-wide PostgreSQL:
Soprano is a library for QT that is able to process RDF data. This is semantic data. Semantic data is a special kind of metadata which is much more flexible than metadata you might know from MP3-Tags or Meta-Tags in HTML since RDF data more resembles the structure of a spoken sentence, thus allowing a much wider field of ways dealing with them. Soprano stores semantic data in a backend and allows low level access to this data.
 
  
===Nepomuk===
+
{{hc|~/.config/akonadi/akonadiserverrc|2=
Nepomuk is somehow the glue between Soprano and the KDE Desktop and thus the user. Nepomuk allows to tag the files with various entries and offers an API for the applications featured in KDE SC. It is enabled by default. Nepomuk can be turned on and off in
+
[%General]
System Settings -> Desktop Search
+
Driver=QPSQL
  
Nepomuk has to keep the trace of a lot of files, because of that is recommended to increase the number of files that can be watched with inotify, to do that:
+
[QPSQL]
sysctl fs.inotify.max_user_watches=524288
+
Host=/run/postgresql
 +
Name=akonadi-''username''
 +
StartServer=false
 +
}}
  
To do it persistant:
+
{{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.}}
echo "fs.inotify.max_user_watches = 524288" >> /etc/sysctl.conf
 
  
And restart Nepomuk.
+
Start Akonadi with {{ic|akonadictl start}}, and check its status: {{ic|akonadictl status}}.
  
===Akonadi===
+
===== SQLite =====
Akonadi is one of the ways of getting data into Nepomuk. Its intention is to gather all kinds of PIM data from KMail, KAdressbook or Kopete. It collects chat contacts, email addresses, email attachments and email contents. First of all it feeds Nepomuk with this data but moreover it provides a centralized access point for all this data.
 
  
==== Disabling Akonadi ====
+
To use [[SQLite]] edit Akonadi configuration file to match the configuration below:
  
If you do not want Akonadi to be ran in your system (for your own reasons), edit {{ic|~/.config/akonadi/akonadiserverrc}} and turn
+
{{hc|~/.config/akonadi/akonadiserverrc|2=
 +
[%General]
 +
Driver=QSQLITE3
 +
}}
  
  StartServer=true
+
{{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].
  
to
+
=== KDE Telepathy ===
  
  StartServer=false
+
[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.
  
And then relogin into your account.
+
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.
  
==== Configuring Akonadi to use MySQL Server running on the System ====
+
==== Use Telegram with KDE Telepathy ====
  
First, you need to set up the database using the following commands (replace password with the correct one):
+
[[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).
  
  CREATE DATABASE akonadi;
+
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).
  GRANT ALL PRIVILEGES ON akonadi.* TO 'akonadiuser' IDENTIFIED BY 'password';
 
  FLUSH PRIVILEGES;
 
  
If {{ic|~/.config/akonadi/mysql-local.conf}} does not exist then
+
{{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.}}
  
cp /usr/share/config/akonadi/mysql-global.conf ~/.config/akonadi/mysql-local.conf
+
=== KDE Connect ===
  
and uncomment the following line
+
[https://community.kde.org/KDEConnect KDE Connect] provides several features to connect your [[Android]] phone with your Linux desktop:
  
sql_mode=strict_trans_tables
+
* 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.
  
Then edit {{ic|~/.config/akonadi/akonadiserverrc}}:
+
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.
  
[%General]
+
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}}. To start the KDE Connect daemon manually, execute {{ic|/usr/lib/kdeconnectd}}.
Driver=QMYSQL
 
 
[QMYSQL]
 
Name=akonadi
 
Host=localhost
 
ServerPath=/usr/bin/mysqld
 
StartServer=false
 
User=akonadiuser
 
Password=<password>
 
Options=
 
 
[Debug]
 
Tracer=null
 
  
Restart the Akonadi server with:
+
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.
  
akonadictl restart
+
== Tips and tricks ==
  
===Strigi Search===
+
=== Use a different window manager ===
Strigi is another way of feeding data into Nepomuk. It preferably indexes the users home-folder. Indexing means that it not only gathers filenames but also information about your music collection or tagged downloads you did with Kget. The Strigi search is also integrated into KDEs launcher which can be accessed via:
 
{{Keypress|Alt}} + {{Keypress|F2}}
 
  
By default, Dolphin has a search bar on top-right where you may type what you want to be found from Strigi's index.  
+
The component chooser settings in Plasma does not allow changing the window manager anymore. [https://github.com/KDE/plasma-desktop/commit/2f83a4434a888cd17b03af1f9925cbb054256ade]
 +
In order to change the window manager used you need to set the {{ic|KDEWM}} [[environment variable]] before KDE startup. The instructions are available on the KDE UserBase Wiki—[https://userbase.kde.org/Tutorials/Using_Other_Window_Managers_with_Plasma Tutorials/Using Other Window Managers with Plasma].
  
{{Note | Strigi has implications for resource usage on your computer - CPU, memory, disk access, disk space, battery life. If Strigi is too resource-hungry for you, you can turn it off in "'''System Settings -> Desktop Search'''". }}
+
{{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]].}}
  
Strigi folder indexing can be configured in:
+
==== KDE/Openbox session ====
System Settings -> Desktop Search -> Desktop Query -> Customize index folders…
 
  
==KDM (KDE Desktop Manager)==
+
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.
  
===KDM Xserver file===
+
For those starting the session manually, add the following line to your [[xinit]] configuration:
An example configuration for KDM can be found at {{ic|/usr/share/config/kdm/kdmrc}}. See {{ic|/usr/share/doc/HTML/en/kdm/kdmrc-ref.docbook}} for all options.
 
  
===Configuring KDM===
+
{{hc|~/.xinitrc|
 +
exec openbox-kde-session
 +
}}
  
You can visit '''System Settings > Login Screen''' and make your changes. Whenever you press "Apply", a '''KDE Polkit authorization''' window appears which will ask you to give your root password in order to finish the changes.
+
==== Re-enabling compositing effects ====
  
==== Problems while Configuring KDM as a user ====
+
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]].
  
If you seem not to be able to KDM settings when launching System Settings as user, press
+
=== Configuring monitor resolution / multiple monitors ===
  
{{Keypress|Alt}} + {{Keypress|F2}}
+
To enable display resolution management and multiple monitors in Plasma, install {{Pkg|kscreen}}. This provides additional options to ''System Settings > Display and Monitor''.
  
and type
+
=== KWin-lowlatency ===
  
  kdesu kcmshell4 kdm
+
[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}}.
  
In the pop-up kdesu window, enter your root password and wait for System Settings to be launched.
+
=== Configuring ICC profiles ===
  
{{Note| Since you have launched it as root, be careful when changing your settings. All settings configuration in root-launched System Settings are saved under {{ic|/root/.kde4}} and not under {{ic|~/.kde4}} (your home location).}}
+
To enable [[ICC profiles]] in Plasma, [[install]] {{Pkg|colord-kde}}. This provides additional options to ''System Settings > Color Corrections''.
  
In the System Settings window, go to Login Screen.
+
ICC profiles can be imported using ''Add Profile''.
  
==Phonon==
+
=== Disable opening application launcher with Super key (Windows key) ===
  
===What is Phonon?===
+
To disable this feature you currently can run the following command:
  
''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.
+
$ kwriteconfig5 --file kwinrc --group ModifierOnlyShortcuts --key Meta ""
''
 
  
from Wikipedia.
+
=== Disable bookmarks showing in application menu ===
  
'''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).
+
With Plasma Browser integration installed, KDE will show bookmarks in the application launcher.
  
===Which backend should I choose?===
+
To disable this feature you currently can run the following commands:
  
You can choose between various backends, like GStreamer ({{Pkg|phonon-gstreamer}}), VLC ({{Pkg|phonon-vlc}}), Xine in [unsupported] ({{AUR|phonon-xine}}) or even MPlayer in [unsupported] ({{AUR|phonon-mplayer}}). 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.
+
$ mkdir ~/.local/share/kservices5
 +
$ sed 's/EnabledByDefault=true$/EnabledByDefault=false/' /usr/share/kservices5/plasma-runner-bookmarks.desktop > ~/.local/share/kservices5/plasma-runner-bookmarks.desktop
  
According to [http://www.archlinux.org/news/kde-sc-46-to-extra/ announce of KDE 4.6 in Arch] and [http://mail.kde.org/pipermail/phonon-backends/2011-February/000500.html mail in Phonon dev list]:
+
== Troubleshooting ==
<blockquote>"Phonon Xine is not maintained and thus will not see releases."</blockquote>
 
<blockquote>"This intial preference currently rates GStreamer highest, followed by VLC as there is some feature difference."</blockquote>
 
  
==Using WebKit in Konqueror==
+
=== Fonts ===
  
===What is WebKit?===
+
==== Fonts in a Plasma session look poor ====
  
WebKit is an open source browser engine developed by Apple Inc. It is used by Safari and Google Chrome. WebKit is a derivative from the KHTML and KJS libraries and contain many improvements.
+
Try installing the {{Pkg|ttf-dejavu}} and {{Pkg|ttf-liberation}} packages.
  
===How to use in Konqueror===
+
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.
  
It is possible to use WebKit in Konqueror instead of KHTML. First install the kwebkitpart package :
+
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}}).
  
  pacman -S kwebkitpart
+
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.
  
Then, after executing Konqueror, press '''Settings > Configure Konqueror'''.
+
==== Fonts are huge or seem disproportional ====
  
On the "General" submenu, select the "WebKit" as the "Default web browser engine".
+
Try to force font DPI to {{ic|'''96'''}} in ''System Settings > Fonts''.
 
You can, of course, choose KHTML again, if you do not like WebKit as the rendering engine.
 
  
==Firefox integration==
+
If that does not work, try setting the DPI directly in your Xorg configuration as documented in [[Xorg#Setting DPI manually]].
See [[Firefox#Firefox_with_better_KDE_integration]].
 
  
==Using Telepathy==
+
=== Configuration related ===
A new project, known as [http://community.kde.org/Real-Time_Communication_and_Collaboration Real-Time Communication and Collaboration], has been started in KDE.
 
The goal is to integrate Instant Messaging clients with the desktop systems.
 
  
At the moment things are in progress and miss some features, but a very base communication system is ready.
+
Many problems in KDE are related to its configuration.
  
To install all Telepathy protocols install the ''telepathy'' group.
+
==== Plasma desktop behaves strangely ====
To use the Telepathy KDE client, install the ''telepathy-kde'' group.
 
  
==Troubleshooting==
+
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.
  
===KDE4 does not finish loading===
+
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.).
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.
 
  
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 thread: [https://bbs.archlinux.org/viewtopic.php?pid=932598].
+
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 when in a different window manager===
+
$ for j in plasma*; do mv -- "$j" "${j%}.bak"; done
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.)
 
  
You just need to set the environment variable QT_PLUGIN_PATH. E.g. put
+
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.
  
export QT_PLUGIN_PATH=$HOME/.kde4/lib/kde4/plugins/:/usr/lib/kde4/plugins/
+
==== Clean cache to resolve upgrade problems ====
  
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!
+
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.
  
Alternatively, you can symlink the Qt styles directory to the KDE styles one:
+
Rebuild the cache using the following commands:
# ln -s /usr/lib/kde4/plugins/styles/ /usr/lib/qt/plugins/styles
 
  
===KHotkeys issue===
+
$ rm ~/.config/Trolltech.conf
Ιf '''khotkeys''' does not work, make sure you have a fully updated system first.
+
  $ kbuildsycoca5 --noincremental
You can also create {{ic|~/.kde4/Autostart/reloadkhotkeys.sh}} with contents
 
#!/bin/bash
 
(sleep 3 && qdbus org.kde.kded /modules/khotkeys reread_configuration) &
 
and then do a
 
  chmod u+x ~/.kde4/Autostart/reloadkhotkeys.sh
 
then logout & login.
 
  
===Enabling thumbnails under Konqueror and Dolphin file managers===
+
Optionally, empty the {{ic|~/.cache/}} folder contents, however, this will also clear the cache of other applications:
 +
 +
$ rm -rf ~/.cache/*
  
For thumbnails of videos in konqueror and dolphin:
+
==== Volume control, notifications or multimedia keys do not work ====
  
  # pacman -S kdemultimedia-mplayerthumbs
+
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.
or
 
  
  # pacman -S kdemultimedia-ffmpegthumbs
+
==== Login Screen KCM does not sync cursor settings to SDDM ====
  
=== Suspend to Disk/Ram not working ===
+
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.
If you are starting KDE with startx try adding ck-launch-session to the {{ic|.xinitrc}},
 
as so:
 
#!/bin/sh
 
#
 
# ~/.xinitrc
 
#
 
# Executed by startx (run your window manager from here)
 
# exec gnome-session
 
exec ck-launch-session startkde
 
# exec startxfce4
 
# ...or the Window Manager of your choice
 
This is done '''automatically with KDM'''.
 
  
=== Graphical related issues ===
+
=== Graphical problems ===
  
==== Low 2D desktop performance (or) Artifacts appear when on 2D ====
+
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]].
===== GPU driver problem =====
 
Make sure you have the proper driver for your card installed, so that your desktop is at least 2D accelerated. Follow these articles for more information: [[ATI]], [[NVIDIA]], [[Intel]] for more information, in order to make sure that everything is all right.
 
The open-source ATI and Intel drivers and the proprietary (binary) Nvidia driver should theoretically provide the best 2D and 3D acceleration.
 
  
===== The Raster engine workaround =====
+
==== Getting current state of KWin for support and debug purposes ====
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.
 
  
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'''".  
+
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].
  
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.
+
$ qdbus org.kde.KWin /KWin supportInformation
  
Since Qt 4.7+, recompiling Qt is not needed. Simply export '''QT_GRAPHICSSYSTEM=raster''', or "opengl", or "native" (for the default). Raster depends on the CPU, OpenGL depends on the GPU and high driver support (it is buggy and highly in development, so I would not expect it to work), and Native is just using the X11 rendering (mixture, usually).
+
==== Disable desktop effects manually or automatically for defined applications ====
  
'''The best and automatic way to do that''' is to install [http://aur.archlinux.org/packages.php?ID=40582 kcm-qt-graphicssystem] from AUR and configure this particular Qt setting through
+
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 > Qt Graphics System
+
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''.
  
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].
+
==== Enable transparency ====
  
==== Konsole is slow in applications like vim ====
+
If you use a transparent background without enabling the compositor, you will get the message:
This is a problem that is caused by slow glyph rendering. You can solve this by switching to a scalable font like Bitstream Vera Sans Mono.
 
  
==== Low 3D desktop performance====
+
  This color scheme uses a transparent background which does not appear to be supported on your desktop
KDE begins with desktop effects enabled. Older cards may be insufficient for 3D desktop acceleration.  You can disable desktop effects in
 
System Settings -> Desktop Effects
 
or you can toggle desktop effects with
 
{{Keypress|Alt}} + {{Keypress|Shift}} + {{Keypress|F12}}
 
  
{{Note| You may encounter such problems with 3D desktop performance even when using a more powerful graphics card, but using catalyst proprietary driver (fglrx). This driver is known for having issues with 3D acceleration. Visit [[ATI|the ATi Wiki page]] for more troubleshooting.}}
+
In ''System Settings > Display and Monitor > Compositor'', check ''Enable compositor on startup'' and restart Plasma.
  
==== Desktop compositing is disabled on my system with a modern Nvidia GPU ====
+
==== Disable compositing ====
  
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.
+
In ''System Settings > Display and Monitor > Compositor'', uncheck ''Enable compositor on startup'' and restart Plasma.
  
 
==== Flickering in fullscreen when compositing is enabled ====
 
==== Flickering in fullscreen when compositing is enabled ====
According to https://fedoraproject.org/wiki/KDE/How_to_reduce_fullscreen_flicker :
 
  
Press Alt+F2 and run:
+
In ''System Settings > Display and Monitor > Compositor'', uncheck ''Allow applications to block compositing''. This may harm performance.
  
    kwriteconfig --file kwinrc --group Compositing --key UnredirectFullscreen --type bool false
+
==== Screen tearing with NVIDIA ====
  
Apply the changes by pressing Alt+F2 and running:
+
See [[NVIDIA/Troubleshooting#Avoid screen tearing in KDE (KWin)]].
  
    qdbus org.kde.kwin /KWin reconfigure
+
==== Plasma cursor sometimes shown incorrectly ====
  
This forces KWin not to use window unredirection but can affect performance of fullscreen OpenGL applications when desktop effects are enabled. Desktop effects can be suspended to prevent performance issues (press Alt+Shift+F12) before running such applications.  
+
Create the directory {{ic|~/.icons/default}} and inside a file named {{ic|index.theme}} with the following contents:
  
See https://bugs.kde.org/show_bug.cgi?id=177495
+
{{hc|~/.icons/default/index.theme|2=
 +
[Icon Theme]
 +
Inherits=breeze_cursors
 +
}}
  
As of KDE SC 4.6.0, there is an option in systemsettings -> Desktop Effect -> Advanced -> "Suspend desktop effects for fullscreen windows"
+
Execute the following command:
Uncheck it would tell kwin to disable unredirect fullscren.  (icarus-c)
 
  
===Sound problems under KDE===
+
$ ln -s /usr/share/icons/breeze_cursors/cursors ~/.icons/default/cursors
  
====ALSA related problems====
+
==== Cursor jerking/flicking when changing roles (e.g., when mousing over hyperlinks) ====
{{Note| First make sure you have '''alsa-lib''' and '''alsa-utils''' installed.}}
 
  
====="Falling back to default" messages when trying to listen to any sound in KDE=====
+
Try installing the appropriate 2D acceleration driver for your system and window manager.
When you encounter such messages:
 
:The audio playback device ''<name-of-the-sound-device>'' does not work.
 
:Falling back to default
 
Go to
 
System Settings -> Multimedia -> Phonon
 
and set the device named "'''default'''" above all the other devices in each box you see.
 
  
=====I cannot play mp3 files when using the GStreamer Phonon backend=====
+
==== Unusable screen resolution set ====
That can be solved by installing the GStreamer plugins:
 
  pacman -S gstreamer0.10-plugins
 
  
If you still encounter problems, you can try changing the Phonon backend used by installing another such as {{Pkg|phonon-vlc}}:
+
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.
  pacman -S phonon-vlc
 
Then make sure the backend is perfered via:
 
  System Settings -> Multimedia -> Phonon -> Backend (tab)
 
  
====OSS4 related problems====
+
==== Blurry icons in system tray ====
If you have OSS4 installed and encounter any problems you should be aware that developers of Kmix are still integrating OSSv4 support. There is an [http://aur.archlinux.org/packages.php?ID=29286 AUR package] that is still experimental.
 
  
=== Arch linux specific packaging issues ===
+
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}} as an attempt to get clear icons.
Due to some upgrades on the packages or a newer versioned pacman with bugs (pft, like there are any ;) there could be some problems during upgrading. Please read the sections below, if you have a problem.
 
  
===I wanted a minimal installation of KDE. After I installed some packages and logged in KDE, there are no panels===
+
=== Sound problems ===
If you wanted a minimal installation of KDE, logged in, heard the login sound but nothing else happened, you may not have installed the Plasma binaries. These are included in
 
  kdebase-workspace
 
Install this package and restart Xorg.
 
  
===I want a fresh installation of KDE for my system. What should I do?===
+
{{Note|First make sure you have {{Pkg|alsa-utils}} installed.}}
Just rename the settings directory of KDE (just in case you will want to go back to your original settings):
 
mv ~/.kde4 ~/.kde4-backup
 
  
===Plasma desktop behaves strangely===
+
==== No sound after suspend ====
Plasma issues are usually caused by unstable '''plasmoids''' or '''plasma themes'''. First, find which was the last plasmoid or plasma theme you had installed and disable it or uninstall it.
 
  
So, if your desktop suddenly exhibits "locking up", this is likely caused by a faulty installed widget. If you cannot remember which widget you installed before the problem began(sometimes it can be an irregular problem), try to track it down by removing each widget until the problem ceases. Then you can uninstall the widget, and file a bug report (bugs.kde.org) '''only if it is an official widget'''. If it is not, I recommend you find the entry on kde-look.org and inform the developer of that widget about the issue (detailing steps to reproduce, etc).
+
If there is no sound after suspending and if KMix does not show audio devices which should be there, restarting plasmashell and pulseaudio may help:
  
If you cannot find the problem, but you do not want ''all'' the KDE settings to be lost, do:
+
$ killall plasmashell
 +
$ systemctl --user restart pulseaudio.service
 +
$ plasmashell
  
  rm -r ~/.kde4/share/config/plasma*
+
Some applications may also need to be restarted in order for sound to play from them again.
  
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.
+
==== MP3 files cannot be played when using the GStreamer Phonon backend ====
  
===Hiding partitions===
+
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}}.
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}}:
 
  
KERNEL=="sda[0-9]", ENV{UDISKS_PRESENTATION_HIDE}="1"
+
Then, make sure the backend is preferred via ''System Settings > Multimedia > Audio and Video > Backend''.
  
The same thing for a certain partition:
+
=== Power management ===
  
KERNEL=="sda1", ENV{UDISKS_PRESENTATION_HIDE}="1"
+
==== No Suspend/Hibernate options ====
KERNEL=="sda2", ENV{UDISKS_PRESENTATION_HIDE}="1"
 
  
===Konsole does not save commands' history===
+
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.
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.
 
To enable autosaving after every command execution you should add following lines into your .bashrc
 
shopt -s histappend
 
[[ "${PROMPT_COMMAND}" ]] && PROMPT_COMMAND="$PROMPT_COMMAND;history -a" || PROMPT_COMMAND="history -a"
 
  
===Kimpanel does not work with the IBus backend===
+
=== KMail ===
There is a bug ({{bug|19580}}) with current Arch kimpanel packaging. See [[IBus#Kimpanel]] for a workaround.
 
  
===KDE password prompts display three bullets per char===
+
==== Clean Akonadi configuration to fix KMail ====
You can change it under '''System Settings > Account Details'''. At '''Password & User Account''' the options are:
 
*Show one bullet for each letter
 
*Show three bullets for each letter
 
*Show nothing
 
  
===knotify4 process constantly uses CPU time===
+
See [https://docs.kde.org/trunk5/en/pim/kmail2/clean-start-after-a-failed-migration.html this] document for detail.
It is a bug with Gstreamer phonon back-end. Try changing to VLC phonon on '''System Settings > Multimedia > Phonon > Backend'''. If this is not in the list, install it:
 
  
#pacman -S phonon-vlc
+
If you want a backup, copy the following configuration directories:
  
If you do not want change the back-end you can try use an external player to play the sound systems. First install mplayer, vlc or any other sound player.
+
$ cp -a ~/.local/share/akonadi ~/.local/share/akonadi-old
 +
$ cp -a ~/.config/akonadi ~/.config/akonadi-old
  
Go to '''System Settings > Application and System Notifications > Manage Notifications > Player Settings''' and change to '''Use an external player''' putting the path of your preferred sound player.
+
==== Empty IMAP inbox in KMail ====
  
===Nepomukserver process still autostart even with semantic desktop disabled===
+
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.
Go to ''' System Settings > Startup and Shutdown > Service Manager > Startup Services''' and uncheck the Nepomuk Search Module.
 
  
==Other KDE projects==
+
==== Authorization error for EWS account in KMail ====
  
===KDE unstable (snapshot)===
+
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:
  
===== kde-snapshots (unofficial) =====
+
$ qdbus org.freedesktop.Akonadi.Resource.akonadi_ews_resource_0 /Settings org.kde.Akonadi.Ews.Wallet.setPassword "XXX"
  
The member '''Zolnierz''' is maintaining a repo where he uploads development snapshots of KDE packages. You may visit [http://bbs.archlinux.org/viewtopic.php?id=76245 this topic] for more information.
+
=== Networking ===
 
 
===== Semi-official kde-unstable =====
 
  
When KDE is reaching beta or RC milestone, KDE "unstable" packages are uploaded to the [kde-unstable] repo.
+
==== Freezes when using Automount on a NFS volume  ====
  
You may add it by adding:
+
Using [[Fstab#Automount with systemd]] on a [[NFS]] volume may cause freezes, see [https://bugs.kde.org/show_bug.cgi?id=354137 bug report upstream].
  
[kde-unstable]
+
=== Aggressive QXcbConnection journal logging ===
Include = /etc/pacman.d/mirrorlist
 
  
in '''{{ic|/etc/pacman.conf}}'''
+
See [[Qt#Disable/Change Qt journal logging behaviour]].
  
They stay there until KDE is declared stable and passes to [extra].
+
=== KF5/Qt 5 applications do not display icons in i3/FVWM/awesome ===
  
Make sure [[#Distro_and_Upstream_bug_report|you make bug reports]] if you find any issues.
+
See [[Qt#Configuration of Qt5 apps under environments other than KDE Plasma]].
  
Read [[#Users|this section]] in the wiki as well.
+
=== Problems with saving credentials and persistently occurring KWallet dialogs ===
  
===KDE Legacy===
+
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.
  
Along with the official KDE4, the KDE3 code "lives" under the fork project called "Trinity".  
+
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.
  
==== Unofficial community repository for KDE 3 ====
+
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.
From the release of KDE 4.x, the developers dropped support for KDE 3.5.x. Nevertheless you can still use KDE 3.5.x through a project called '''kdemod3'''
 
[http://bbs.archlinux.org/viewtopic.php?id=97612 In this thread]. The current rebuild of the unsupported KDEmod3 is based on the Trinity project code (KDE 3.5.12). See Trinity on Arch Linux below.
 
  
{{Warning| KDE 3 is no longer maintained and supported by the KDE developers. The "Trinity KDE" is maintained by the Trinity project commmunity. KDEmod3 is no longer maintained by the Chakra Projects developers. Use KDE 3 on your own risk, regarding any bugs, performance issues or security risks.}}
+
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.
  
===Trinity on Arch Linux===
+
=== Discover does not show any applications ===
Trinity SVN is currently KDE 3.5.13. An unofficial effort to provide a working set of PKGBUILDs for Trinity for Arch Linux is in the beginning stages and produces a working KDE 3.5.13 desktop for Arch Linux. Links for binary packages built from the Trinity SVN code as well as the PKGBUILDs are available. For details on this effort, see the Trinity Arch wiki:
 
*'''[[Trinity|Trinity on Arch]]'''
 
  
Trinity Stable (KDE 3.5.12) packages are also available as an update to kdemod3. The following repository holds binary packages from the Trinity (3.5.12) code base:
+
This can be solved by installing {{Pkg|packagekit-qt5}}.
  
# Trinity 3.5.12 - i686
+
=== High CPU usage of kscreenlocker_greet with NVIDIA drivers ===
[kdemod3]
 
Server = http://rapinjam.com/beta/lefa/kdemod3/i686/
 
 
# Trinity 3.5.12 - x86_64
 
[kdemod3]
 
Server = http://rapinjam.com/beta/lefa/kdemod3/x86_64/
 
  
* After adding the repository, issue '''&lsquo;pacman -Syu&rsquo;'''. If that fails to trigger the update (or if you do not have kdemod3 installed), then use '''&lsquo;pacman -Sy kdemod3-complete&rsquo;'''
+
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}}.
  
=== Chakra Project KDEmod ===
+
Then kill previous instances of the greeter with {{ic|killall kscreenlocker_greet}}.
  
The Chakra Project KDEmod (for KDE4) is no longer active and the current Chakra Project's KDE is no longer compatible with Archlinux packages and repos.
+
=== OS error 22 when running Akonadi on ZFS ===
  
If you have installed KDEmod (for KDE4), please remove it and install KDE SC from the official Archlinux repos.
+
If your home directory is on a [[ZFS]] pool, create a {{ic|~/.config/akonadi/mysql-local.conf}} file with the following contents:
  
==Bugs==
+
[mysqld]
 +
innodb_use_native_aio = 0
  
===Distro and Upstream bug report===
+
See [[MariaDB#OS error 22 when running on ZFS]].
It is preferrable that if you find a minor or serious bug, you should visit [http://bugs.archlinux.org the Arch Bug Tracker] or/and [http://bugs.kde.org KDE Bug Tracker] in order to report that. Make sure that you be clear on what you want to report.
 
  
If you have any issue and you write about in on the Arch forums, first make sure that you have '''FULLY''' updated your system using a good sync mirror (check [https://www.archlinux.de/?page=MirrorStatus here]) or try [[Reflector]].
+
=== Some programs are unable to scroll when their windows are inactive ===
  
KDE 4 config files are usually located at
+
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.
  
~/.kde4/share/config/
+
=== TeamViewer behaves slowly ===
  
and for app-specific configs
+
When using TeamViewer, it may behave slowly if you use smooth animations (such as windows minimizing). See [[#Disable compositing]] as a workaround.
  
~/.kde4/share/apps/
+
== See also ==
  
==External Links==
+
* [https://www.kde.org/ KDE homepage]
* [http://www.kde.org KDE Homepage]
+
* [https://dot.kde.org/ KDE news]
* [http://bugs.kde.org KDE Bug Tracker]
+
* [https://planet.kde.org/ KDE Blogs]
* [http://bugs.archlinux.org Arch Linux Bug Tracker]
+
* [https://forum.kde.org/ KDE Forums]
* [http://websvn.kde.org KDE WebSVN]
+
* [https://wiki.kde.org/ KDE Wikis]
 +
* [https://bugs.kde.org/ KDE bug tracker and reporter]
 +
* [https://blog.martin-graesslin.com/blog/kategorien/kde/ Martin Graesslin's blog]

Latest revision as of 19:16, 28 March 2020

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 Plasma widgets. 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 > Global Theme > Get New Global Themes....

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

GTK application appearance
Tip: For Qt and GTK theme consistency, see Uniform look for Qt and GTK applications.

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 > Configure GNOME/GTK Application Style....

Tango-view-refresh-red.pngThis article or section is out of date.Tango-view-refresh-red.png

Reason: The Plasma GTKd background service overwrites GTK settings on Plasma startup. (Discuss in Talk:KDE#)

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

Night Color

Plasma provides a Redshift-like feature (working on both Xorg and Wayland) called Night Color. It makes the colors on the screen warmer to reduce eye strain at the time of your choosing. It can be enabled in System Settings > Display and Monitor > Night Color.

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 when Plasma exits.

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. To start the KDE Connect daemon manually, execute /usr/lib/kdeconnectd.

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. The instructions are available on the KDE UserBase Wiki—Tutorials/Using Other Window Managers with Plasma.

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

Cursor jerking/flicking when changing roles (e.g., when mousing over hyperlinks)

Try installing the appropriate 2D acceleration driver for your system and window manager.

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 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.[8]. 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