kjeksomanen on DeviantArthttps://www.deviantart.com/kjeksomanen/art/Arch-Linux-desktop-KDE-4-7-265095122kjeksomanen

Deviation Actions

kjeksomanen's avatar

Arch Linux desktop - KDE 4.7

By
Published:
12K Views

Description

What:
Current desktop on one of my computers. Running Arch Linux with KDE 4.7 after being sick of Unity and Gnome 3.
Just started using it, so it still feels a little bit alien to use.

Why:
Finally got a SSD (Crucial M4 64 GB), so got my main desktop computer up and running again with newly gained power! Been using Ubuntu for half a year now, and it's effective to work with, but it's not very good looking.

On the other hand I have Gnome 3.2 on my laptop with Arch Linux as well, but that's just good looking, but impossible to be effective with..

Therefore I had to try something new, and *box-setups doesn't seem like something I could use for everyday-use, so a friend told me to try KDE :)

How:
Desktop theme: Caledonia [link]
Window decoration: Zink [link]
Application style: Oxygen, shipped with KDE 4.7
Application colors: Obsidian Coast, a little modified
Icons: the lovely kAwOken [link]
Fonts: Ubuntu Fonts [link]
Splash screen: Caledonia-KSplash [link]
Wallpaper: Deep Love Wallpaper [link]
Image size
1920x1080px 1.86 MB
© 2011 - 2024 kjeksomanen
Comments29
Join the community to add your comment. Already a deviant? Log In
WonderlandRevisited's avatar
I used to avoid Arch Linux because of the lack of package signing, but Wikipedia says that Arch Linux has had package signing by default since 2012.

Paste from Wikipedia:

Until pacman version 4.0.0[19] Arch Linux's package manager lacked support for signed packages.[20] Packages and metadata were not verified for authenticity by pacman during the download-install process. Without package authentication checking, tampered-with or malicious repository mirrors can compromise the integrity of a system.[21] Pacman 4 allowed verification of the package database and packages, but it was disabled by default. In November 2011 package signing became mandatory for new package builds, and as of 21 March 2012 every official package is signed.[22]

In June 2012, package signing verification became official and is now enabled by default in the installation process.[23][24]