I think that none of the Linux adherents will deny the great contribution that Ubuntu has made to the development of the ecosystem. Yes, there are not enough resources for many things, projects are often abandoned halfway through. But it seems to me that they managed to achieve a great balance between stability and freshness of the package base. Some very correct line between maintaining the noble mold of Debian and the continuous search for what broke during the update in Arch Linux. Do you just want to work? We are using LTS versions of the distribution with default repositories. Do you need any specific software? We connect a PPA from the developer. We installed fresh hardware, we need support in the kernel, but we don’t want to leave LTS - we use LTS Enablement Stacks (HWE).
Not everyone likes the default Unity shell, but here the entire Ubuntu Flavors family is available to the user. In my choice, I settled on KDE and Kubuntu, respectively. Everything was fine, but sitting on LTS releases inevitably causes a craving for adventure and breaking the system. And then I went in search of something new.
KDE Neon
When the KDE developers realized that their development rate was far outpacing the rate at which maintainers were implementing new packages, they decided to create a separate distribution. No, I understand that now readers will experience a lot of sarcasm and rightly point their finger at hundreds of more such distributions with boring wallpapers. However, it's not all bad.The key feature of the project is the main package base of the stable version of Ubuntu LTS and the entire KDE environment, which receives an update immediately after release. For example, KDE Plasma 5.9.3 will only be available in the upcoming Kubuntu 17.04 release. With Neon, the bulk of the packages are absolutely stable and you have all the benefits of long-term support for the distribution. That is, not a full-fledged distribution kit, but a convenient constructor, despite the presence of its own assemblies.
Distribution structure
Any more or less experienced user understands that the line between distributions is often very blurred. And the same Xubuntu differs from Lubuntu with Kubuntu only in a set of default packages and sometimes connected repositories. I was very pleased that the creators did not follow the path of the same Elementary OS, but simply carefully connected their repository.The team aims to use their repository on all compatible distributions. If you have a certain sense of adventure, you can upgrade to Neon by simply updating /etc/apt/sources.list. Although there may be some problems here too.
Installation options
The recommended option is to install from scratch from their image. You can download them from the official page. Delivery options:User Edition- fresh stable KDE environment packages, optimal for daily use.
User LTS Edition- LTS version of Plasma Desktop + fresh application packages (Krusader, Konsole and others) - optimal for those who need a stable DE, but want updates to the software base.
Developer Edition Git-Unstable- pre-release version from an unstable branch. Daily assembly.
Developer Edition Git-Stable- pre-release version from bugfix branches. Daily assembly.
You can also connect their repositories to regular Kubuntu. However, the official manual warns that in this case everything will probably break down. They are not compatible with the Kubuntu base and are not tested. I went exactly this way. Indeed, several packages broke off, but we managed to resolve the dependencies manually without any problems. If you try this option, don't forget to do something like
sudo rsync -axv / /mnt/backup/root_backup
General feelings
The system is very stable, I have not encountered any major problems. Despite the fact that I initially have five or six third-party PPAs connected. KDE Neon maintainers work very carefully and almost never push dependencies beyond the boundaries of their software. Fresh plasma does not drop) RAM eats also very delicately - something in the region of 500-600 MB, taking into account background processes like Owncloud and preload daemon. Arrives once a week or a week and a half big update for several dozen packages. Everything is really very fresh.New in Plasma 5.9
A nicer network manager
Projects with open source code, including KDE, have benefited greatly from professional programmers who have developed a wealth of high-quality applications that can satisfy almost any need.
Typically, many apps come with all sorts of features to make them popular with a wide range of users, which I think is a good idea because they allow for flexibility and endless customization options.
In this article we will look at best programs for kde plasma. And at the end of the article you can leave comments and offer yours best apps for kde.
Dolphin is one of the best file managers for Linux. Unlike Nautilus, which has lost its functionality over the years, Dolphin has a ton of hot, powerful features that make it attractive to casual and advanced users.
He has sidebar and a top and bottom status bar toolbar that's no different from most file managers, but you'll notice that its interface is highly customizable, giving you the ability to customize it depending on your work environment and taste. This allows it to be included in our list of the best kde programs.
2. Okular.
Okular is a document viewing application that allows you to view files in PDF format, CHM and EPUB, as well as many others. Although it is developed for KDE Plasma, it can run on Windows and MacOS, as well as other Linux systems.
Some of the most useful functions Okular include PDF annotation, highlighting and line drawing, copying images to clipboard, and text-to-speech (via jovie).
3. KDE Connect.
KDE Connect allows you to integrate Android devices with your computer by synchronizing notifications, sharing clipboard contents, transferring files to different devices or even using your phone as a remote keyboard for your computer.
As long as your devices are connected to the same Wi-Fi networks and both devices have KDE Connect installed, you can take advantage of such a well-designed and functional application.
4. KMyMoney.
KMyMoney is a personal budgeting tool designed for the plasma application suite, although its use is not limited to KDE. It is a GnuCash alternative that works best on GTK systems like Gnome and has amazing features that can help your personal budget.
Working with the application is quite simple. You can enter your data manually into different categories or import transactions from CSV, QIF, OFX and other formats. KMyMoney also has a section that allows users to set expected income and expenses on a monthly or yearly basis.
5. Calligra Suite.
Calligra is an office suite for KDE. It is a worthy alternative to LibreOffice for those who want full integration with the KDE desktop environment. The complete package has applications for word processing, spreadsheets, vector graphics, digital images, presentations and many others.
Please note that Calligra does not support saving in office Microsoft formats(.doc and .docx), but you can read, edit and save them in ODF format.
6.Kate.
Kate is the default text editor in Plasma and is an advanced text editor that allows you to perform a wide range of operations, no matter your skill level.
Kate is not as simple an application as Notepad in Windows; it has many important features that make it relevant for text printing or other complex operations with text files. You can also add additional features to the application using scripts and plugins that can be found on the Internet.
7. Krita.
Krita is creative application, which was originally part of the Calligra Suite, but became independent with the release of version 3.0. It's slightly better than GIMP itself. popular application open source for image editing.
But these applications have different purposes, and do not necessarily have to be a direct replacement for each other, because they are both the best kde applications in this direction. GIMP is more designed for editing photos and pictures, and Krita is more for drawing your masterpieces.
8. KdenLive.
Kdenlive is an exceptional video editing application designed specifically for kde systems, but you can run it on any DE if need be. It has a huge range of features that will satisfy both professionals and amateurs, and the application continues to be constantly improved. Who said it's impossible to edit video on Linux?
9. Amarok.
Music apps are a dime a dozen, no matter what. operating system you use, but there are apps that stand head and shoulders above the rest. Amarok is a long-time favorite among Linux users due to its impressive feature set, which can be extended using plugins and scripts. If you can accept its unconventional interface, then it will become an indispensable program for you.
10. Digikam.
Digikam is another photo editing and library management app with a lot of advanced features that have made it quite popular among photographers. It supports all major image formats and can organize your own photo catalogs by date, time frame, or tags. It also has image quality enhancement tools. In addition, functionality can be expanded using plugins and extensions.
conclusions
Outdated translations are marked like this.
Contents
Installing KDE Software
We recommend using your distribution to install KDE software. .
From the GUI
Discover
Discover is the KDE Software Center and work with all the distribution supporting appstream (Ubuntu, Debian, Arch-Linux, OpenSUSE, Red Hat, Fedora, ...). If you want more info about discover, visit the discover page.
Searching for KDE in Discover.
openSUSE - YaST
In openSUSE, you have the choice between using discover and YaST software management tool.
You will find the openSUSE package management tool in the Computer tab of the start menu. Open it and click on the Software management icon to launch the package manager.
Searching for KDE in the YaST software management.
Use the search field to find the package you want to install; you can search for a package by name or description, you only need to enter part of its name. You will be presented with a list of packages that match your request. Select the packages to install and click Apply. Visit this page to get additional information about how to work with packages and about the openSUSE distribution.
Windows Store
Some KDE applications are also available in the Windows Store. For example, you can buy Krita a digital painting software or KStars .
Using the Command Line
If you find using the manager ineffective, you may want to install from command line. This is much faster, however the downside is that you need to know the exact name of the package you want to install. Each system has useful commands to search for example, try using the first word of the install command below, appending --help . As an example, yum --help will list the commands you can use for Fedora, but there are a lot of them which can be confusing at first.
openSUSE
With openSUSE you install software using zipper for example to install KWrite you will open a console and enter zypper in kwrite .
Ubuntu
With Ubuntu Linux you install software using apt. For example to install KWrite you will open a console and enter sudo apt install kwrite
Fedora
Fedora uses yum and to install KWrite you have to open the console and type yum install kwrite If you are not sure about the package name, you can use yum list with templates to see all packages with the word as part of the package name - - For example the yum list *network* will list all available packages with "network" as part of the name. To go even further, yum search mpeg will list all packages, or mpeg in the package name or description.
Gentoo
With Gentoo you install software using emerge, e.g. for KWrite you would open a console and type emerge --ask kwrite (using --ask to get an overview of necessary dependencies and USE flag options before confirming). If you are unsure of the name of a package, you can use emerge --search to see all the packages with a word as part of the package name - e.g. emerge --search network will list all available packages with "network" as part of the name.
Mageia and OpenMandriva Lx
you can use urpmi to install KDE software from the command line. Other useful commands can be found on the Urpmi Wikipedia page
Arch Linux and Manjaro
With Arch linux and arch linux based distribution like Manjaro, you can install software using the pacman utility. For example to install KWrite you will open a console and enter sudo pacman -S kwrite
This note and several related ones are dedicated to KDE 3.X, and they were written when there were quite old versions. Nevertheless, they could have been of some interest at the time of placement, since during the entire existence of the “troika” no radical changes took place in it. Now the place for this note is in the dustbin of history.
It is easy to guess that the KDE project is based on the website http://www.kde.org, from where it can be downloaded absolutely free of charge in the form of source texts (and binary packages for some Linux distributions). KDE binaries are included in almost any Linux distribution that claims to be fully functional (and in many it is also the default desktop. It is available in collections of binary packages and port systems of all BSD systems. However, for FreeBSD it is better to take KDE binaries not from the standard distribution this OS, and from the site http://freebsd.kde.org/ - there will most likely be a more recent version.
To install KDE, you must also take care of obtaining the Qt library, a freely distributed (for non-commercial use) version of which is taken in source form from the developer’s website http://www.trolltech.com/. However, it also exists in Linux distributions and BSD systems - you just need to ensure that the versions match - they usually correlate quite clearly with the KDE versions.
KDE requires the X system, as well as many additional components, including the main graphics and multimedia libraries, some of which inevitably drag along the Glib and Gtk libraries as dependencies. However, all this equipment is available in distribution kits and, most likely, is installed from them by default. And many of the additional components are associated with KDE “soft” (optional) dependencies - in KDE the division of “hard” and “soft” dependencies is very consistent.
Of course, the process of building KDE yourself is not the easiest, both due to the complexity of the dependencies of additional components, and in terms of time investment. However, this is one of the few cases where custom assembly can provide a significant performance increase. in addition, it allows you to exclude dependencies that are clearly unnecessary for the user from among the “soft” ones - in most packaged Linux distributions, all of them are included in precompiled assemblies by default. An alternative to completely manual assembly is to use ports of BSD systems and port-like Source systems Based Linux distributions - all of them allow significant variations in personal settings, including cutting off unnecessary dependencies.
The KDE environment itself, in source form, includes about one and a half dozen packages, the list and composition of which varies somewhat from version to version. In the current version at the time of writing (3.3.1) it looks like this:
Kdeaccessibility-3.3.1.tar.bz2 kdeaddons-3.3.1.tar.bz2 kdeadmin-3.3.1.tar.bz2 kdeartwork-3.3.1.tar.bz2 kdebase-3.3.1.tar.bz2 kdebindings-3.3.1 .tar.bz2 kdeedu-3.3.1.tar.bz2 kdegames-3.3.1.tar.bz2 kdegraphics-3.3.1.tar.bz2 kdelibs-3.3.1.tar.bz2 kdemultimedia-3.3.1.tar.bz2 kdenetwork -3.3.1.tar.bz2 kdepim-3.3.1.tar.bz2 kdesdk-3.3.1.tar.bz2 kdetoys-3.3.1.tar.bz2 kdeutils-3.3.1.tar.bz2 kdewebdev-3.3.1. tar.bz2
In addition, KDE includes the arts and kdevelop packages, which have their own version numbering, as well as the kde-i18n package, which provides internationalization of the environment, as well as localization packages for individual languages, including almost every conceivable language (although localization for them is done with great care). different completeness and quality).
All this equipment, including the Qt library, in the source code is almost three hundred megabytes. Which cannot but evoke memories of the monstrous nature of KDE. However, not everything listed is required for installation and, accordingly, downloading. However, in many packaged Linux distributions, all KDE components are linked by cross-package dependencies (including all optional ones), and you have to install them all. But in FreeBSD, SB Linux, and even more so with manual assembly, you can only get by with those that are actually necessary.
The first, and indisputable, candidate for removal from the list is the kde-i18n package (and this is already more than 100 MB of source code): obviously, no one needs support for a good fifty languages at the same time. A separate package for your own is enough (in our conditions this is kde-i18n-ru), in extreme cases - a couple of more friendly ones.
Further, it is clear that only these same developers need the kdevelop package, while most users can easily do without it. Well, the user must make the decision to install other packages independently. For this purpose I will briefly describe the purpose of each.
First, let’s talk about the packages that are required to be installed in any case. As you might guess, there are two of them - kdelibs and kdebase. The first is a set of KDE-specific library functions that complement the core Qt library. The second includes the main components of KDE - the KWM window manager itself and its accessories, a minimum set of themes and basic applications - file manager, aka browser, konqueror, set text editors(kwrite, kedit, kate), konsole terminal emulator.
Oddly enough, the arts package is also mandatory - its own sound system KDE, used to play system sounds even if KDE multimedia components are not installed.
All other components are purely optional, so I will describe those that I use myself, in order of importance for me personally:
- kdenetwork - network components, including the excellent kppp dialer and kget - an ftp client, which in itself is not outstanding, but when integrated with the file manager/browser konqueror, it greatly helps make life easier;
- kdepim is a package of personal assistants, which, in my opinion, is not entirely logical, includes mail client kmail and its complementary address book;
- kdewebdev - a web development package based on the excellent Quanta Plus HTML code editor, harmoniously complemented by auxiliary tools such as a link integrity checker (klinkstatus) and a link map creation tool (kimagemapeditor);
- kdegraphics - package includes a couple of viewers graphic files, Very convenient program taking screenshots, a simple but good graphics editor kolourpaint (plus two more, averagely lousy);
- kdemultimedia - the package includes a very decent media player noatun (albeit worse than mplayer, especially in the KDE form - but it is not included in the standard package), mixer, recorder, etc.;
- kdeutils - in addition to all the jewelry, it includes a calculator, a necessary thing;
- kdeadmin - a package of system administration utilities that, with rare exceptions, require superuser privileges; I don’t use it, although for some reason I usually install it.
I also always install two more packages - kdeaddons (IMHO absolutely necessary, as it includes, among other things, plug-ins for the editor kate, konqueror and others) and kdeartwork, which includes additional desktop decorations (wallpapers, icons and etc.), life without which would be boring. And also kdegames, where you can find several solitaire games and a couple of variations on the immortal Tetris theme - but I don’t play any other games.
It remains to mention packages that I never install and therefore have a vague idea of the contents of: kdeedu (as you might guess, something related to education (I don’t know what or who), kdetoys - some bells and whistles, kdeaccessibility - so-called special features , and kdesdk is a set of scripts and utilities for developers.
In most cases, the user does not have to worry about installing KDE in any special way - either the installer of his distribution handles this task, or standard system package management. A certain problem arises only if the proposed installation scheme is for some reason not satisfactory, for example, due to deliberate redundancy: I have already noted that a number of packages from the KDE set have no practical meaning for most users. And here it may be advisable to resort to manual assembly of the required components.
The process of building KDE itself is also not particularly difficult - you just need to follow the sequence of building packages: first the Qt library is built, therefore the arts sound system, then the kdelibs library, and then kdebase. Other packages, if necessary, are assembled after these others - and in more or less any order.
To build the Qt library, the tarball of its sources is unpacked into the directory in which we want to see it in the future - by default it is /usr/local, recently Qt is often placed in the /opt directory, in any case, the result is a subdirectory like qt- vesion. It should be renamed:
$ mv qt-version qt
and in the profile file - system-wide or user, that is, root - adjustments are made to the values description variables paths (this is described in detail in the accompanying documentation). For an sh-compatible family it looks something like this:
QTDIR=/usr/local/qt PATH=$QTDIR/bin:$PATH MANPATH=$QTDIR/man:$MANPATH LD_LIBRARY_PATH=$QTDIR/lib:$LD_LIBRARY_PATH export QTDIR PATH MANPATH LD_LIBRARY_PATH
These variables will be required already at the configuration/compilation stage, so you need to either log in again or re-read the profile file in the prescribed manner. Then a couple of commands are given
$ ./configure && make
Of the configuration options, at least one seems useful - -qt-gif , which includes support for GIF graphics (by default, oddly enough, this is not implied).
It’s interesting that when building Qt, it seems that any gcc flags are ignored, except for some that were initially specified in it - so you don’t have to get carried away with optimizing this library. By default, Qt is built with optimization level -O2.
The assembly of each of the KDE packages itself is performed through three traditional sacred actions -
$ ./configure && make && make install
of which the first deserves special attention. The thing about configuration scripts for KDE packages is that they usually run to completion - even if dependencies are broken. A full report is issued regarding the testing of the script. At the same time, there is a clear distinction between “hard” dependencies, without which the assembly and operation of the package is impossible, and “soft” dependencies, which add optional (but often enabled by default) functions to it.
If everything is clear with “hard” dependencies - they must be satisfied without fail - then with regard to “soft” dependencies the user is given a choice. For example, KDE's soft dependencies include the cups printing system and the sane scanning system. However, it is quite possible that the user does not need these functions (for example, due to the lack of appropriate units). And therefore, it may well be possible to turn them off by specifying the appropriate configuration script options - and a complete list of them, as usual, is obtained by the command
./configure --help
By default, Qt and KDE packages are installed in their own branches of the /usr/local directory - /usr/local/qt and /usr/local/kde. However, there has been a recent trend in many Linux distributions to move such large software packages to the /opt directory (and this is encouraged by the File Hierarchy Standard). Linux systems). To follow this trend, when executing the configuration script, you must set the appropriate options:
./configure --prefix=/opt --with-qt-dir=/opt/qt
After building Qt and kdelibs (and before building the rest of the KDE packages), you need to make the corresponding libraries publicly available to all applications. To do this, you need to enter the lines in the /etc/ld.so.conf file
/opt/qt/lib /opt/kde/lib
and run the command
$ldconfig
Now about optimization. KDE (like Qt) is written in C++, and, accordingly, optimization requires not the CFLAGS flag, but the CXXFLAGS flag. However, they can be equated to each other -
Export CXXFLAGS="$CFLAGS"
Well, we’ll talk about possible values of CFLAGS some other time.
Page 5 of 24
4.4. Description of packages
The base distribution currently consists of eleven packages. Some
Some of them are necessary, others are optional. Each package is available in any
from the previously listed formats.
. kdesupport (RECOMMENDED)
This package contains support libraries that were not written
as part of the KDE project, but are nonetheless necessary. If you already
do you have these libraries (libgif, libjpeg, libmime, libuu, libgdbm),
and the required versions, you do not have to install this package.
If you are not sure, it is better to install it. Note that for
Debian packages, this package is required.
. kdelibs (REQUIRED)
This package contains common libraries that are required for all
KDE applications.
. kdebase (REQUIRED)
This package contains the core applications that form
the core of KDE. This includes a window manager, a terminal emulator,
control center, file manager and panel.
. kdegames (OPTIONAL)
Various games such as Mahjong, Snake, Asteroids and Tetris.
. kdegraphics (OPTIONAL)
Various programs related to graphics such as viewer
postscript files, dvi file viewer, drawing application.
. kdeutils (OPTIONAL)
Various desktop utilities such as calculator,
editor and others useful applications.
. kdemultimedia (OPTIONAL)
Multimedia applications such as CD player and mixer.
. kdenetwork (OPTIONAL)
Applications for the Internet. On this moment package contains program
Email, news reader app and some
other network applications.
. kdeadmin (OPTIONAL)
Applications for system administration. Currently the package
contains a user manager and runlevel editor
(runlevel editor) system V.
. kdetoys<НЕОБЯЗАТЕЛЕН)
Nice little apps
. korganizer (OPTIONAL)
Without an organizer, something is missing in the work environment. Is it true?
kdesupport (if needed) must be installed before other packages.
Next should be kdelibs. Other packages can be installed in
in any order.
4.5. Installation instructions for different package formats
4.5.1. Installing Debian packages
Debian packages are installed according to the upcoming FHS
(file hierarchy standard).
To install Debian packages:
. run: dpkg -i
for each and every one of the packages that you want to install.
4.5.2. Installing RPM packages
RPM packages copy files to /opt/kde.
To install binary RPMs:
. go to super user mode
. run: rpm -i
To create a binary RPM from a source rpm and for installation
First do the following:
. go to super user mode
. run: rpm -i
. cd /usr/src/redhat/SPECS
. rpm-bb
. cd ../RPMS/i386 (or other, depending on what you are using
architecture)
. rpm -i
4.5.3. Installation using source code in tar.gz archives
The source package.tgz is installed in /usr/local/kde by
default. You can change this setting using the option
-prefix in the configuration script.
. Unpack the packages by typing: tar xvzf
. Change to the directory created by the package: cd
Some packages (most notably kdebase) have
special settings that may be useful to you when
installation. To view these parameters, run:
./configure -help.
. Compile the package: make
. Install the package: su -c "make install" (unless you're already in
superuser). If you are already a super user - just
type "make install" (without quotes).
4.5.4. Installing binary .tar.gz files
Binary packages.tar.gz are installed in /opt/kde.
. go to super user mode
. cd/
. tar xvzf
Loading...
