I know your pain, this has been annoying me for months now.
1) The only way to fix the desktop I've found is brute force, I made a shortcut to do this and run it every time I resume from standby:
killall plasmashell; kstart plasmashell
2) I can't properly answer this but I'm posting all the info I've got so I can link this from the bug report page. The ...
According to announcements you need to add the corresponding Plasma Widget or the menu button from "Window Decorations" settings.
Global Menus have returned. KDE's pioneering feature to separate the menu bar from the application window allows for a new user interface paradigm, with either a Plasma Widget showing the menu, or with the menu neatly tucked ...
Look in ~/.config for a file named plasm-org.kde.plasma.desktop-appletsrc.
It will contain something like:
applicationName=GNU Emacs 24
Change the IconName ...
See bugreport: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829614. There is some kind of conflicts between KF5 5.22 and 5.23.
I had the same issue, and installing libkf5plasma5 from unstable resolved it.
apt install -t unstable libkf5plasma5
To have a device mounted on startup, you need to edit /etc/fstab as root. The format for /etc/fstab is as follows:
# <file system> <mount point> <type> <options> <dump> <pass>
<file system> is the device or remote filesystem you want to mount.
<mount point> is where you would like your device ...
Simple Linux permissions. The user semko owns its $HOME directory. Most other directories on a Linux system are owned by root or some other system related account and are writeable only by root or those accounts.
Probably what you want is:
# chgrp semko /media/mnt/*
# chmod g+w /media/mnt/*
Personal preference for me to use group ownership rather than ...
It took me half a day to (almost) fully investigate this, but I think I found how to do it, and you’re not gonna like it …
In a nutshell,
KDE just uses QT’s QLocale. Which itself uses hard-coded data inside qlocale_data_p.h, deep in QT’s core library code.
This data is apparently manually generated from the Unicode Consortium’s “Common ...
Add all users that should be able play back to the pulse-access group
# adduser problemofficer pulse-access
Create /etc/systemd/system/pulseaudio.service with the following content:
ExecStart=/usr/bin/pulseaudio --daemonize=yes --system=yes --disallow-module-loading=yes --disallow-exit=yes
The error logs show that the akonadi verion of the mysql server that these K* applications require is trying to access ~/.local/share/akonadi/db_data/ except db_data doesn't exist, so it throws an error much like touch ~/nonexistent_dir/file.txt would.
To solve, simply run the below commands.
cd ~/.local/share/akonadi/; mkdir db_data
Who is responsible for this?
Not Linux. Not Ubuntu. Not X.Org. The programs are not suspended.
The programs themselves are the culprit. Since times immemorial, programs have been able to know whether they were currently displaying something, because they know when the windowing system asks them to redraw their window. If the X session is not active then no ...
I have had the same problem with Kubuntu 18.04. Having gone read several posts about this problem, I've combined the answers into a solution that works automatically. There is a small Bash script that runs in the background and kills/restarts plasmashell every the user returns from lock screen. You can find the answer to the link below (script and way to run ...
I had same problem on my kali linux(kali-rolling version).
I solved this problem, just installed 'kwin-x11'
sudo apt-get install kwin-x11 kwin-decoration-oxygen
I think this might solve your problem too.
I tried going to the panel's context menu > Panel Options > Add Panel > Application Menu Bar, but only an empty panel appears at the top of the screen.
If this happens to you:
1. Go to System Settings > Startup and Shutdown > Background Services, and then enable the Application Menus Daemon. Always remember to click Apply!
2. Restart any open ...
According to some similar existing bugs on KDE forums, Xinerama can break kde-plasma5, so if you have Xinerama enabled in Xorg's config file (in /etc/X11/xorg.conf ) , try to disable it. It will be in the Section "ServerLayout" :
Option "Xinerama" "1"
So if you have the line like above, change the value to zero:
Option "Xinerama" "0"
I took a guess that the new directory might have the same name. I made sure my mlocate database was up to date, then searched for it.
$ sudo updatedb
$ locate RecentDocuments
I only had a few hits, and it revealed the location in Plasma 5.
I double checked, and the contents matched the recent documents in Application ...
If you are happy with a solution with config files: Install devilspie2 (Ubuntu: sudo apt install devilspie2) and create a ~/.config/devilspie2/smplayer.lua with this content:
if (get_application_name() == "SMPlayer") then
Then run devilspie2 and if everything works as expected, make sure KDE starts it after login.
The problem with using qdbus org.kde.JobViewServer.requestView from a shell script is that it's designed to delete the notification when the requesting D-Bus client exits, so tools like dbus-send and qdbus won't work because they exit immediately after calling requestView.
If you use qdbusviewer to create a request, you can play around with calls like these ...
You must have always the very last packages of QT5, KF5 for every Plasma 5 version, or the Plasma Desktop has many bugs, freezes or is completely broken. In Debian are mostly old or different versions, also mixed with KDE 4, which ends up in multiple problems. So Plasma 5 in Debian is far away from usable. Personally i think, that KDE has no priority for ...
My experience, GTK+ application theming doesn't work well if it's not gnome session.
You should try the lxappearance application while running KDE to apply GTK+ theme or Icon theme. Tested on KDE5 and LXQt.
I think the Pop icon theme blend well with both dark and light themes.
The window switcher installation is broken, resources are missing
It seems you downloaded some theme or custom task switcher that is not compatible with your current version.
I had same problem and fixed it selecting a working theme, then restarting (or relogging), using following command :
Hope it helps.
To fix it:
Switch to a console (as suggested in the comment): Ctrl+Alt+F2, login, and then:
kill the screenlock program (with htop, kill lockprogramname etc), or
restart the display manager (systemctl restart display-manager.service), or
try to run setxkbmap (env DISPLAY=:0 setxkbmap us), or
reboot the system
To avoid it in the future:
Use multiple ...
This was suggested by "achillion" on Arch's IRC channel:
You should check GTK's font and theme settings by launching the KDE GTK configurator with this command: kcmshell5 kde-gtk-config.
You must also install the configurator by installing the extra/kde-gtk-config package.
Relaunch Google Chrome after saving your changes in the configurator.
You are getting a installation inconsistency (typical of kali)
Consulting https://debian.packages.org, it can be found out that path/file is supplied by the package plasma-workspace (list of files here)
For installing it:
sudo apt install plasma-workspace
or if installed, for reinstalling it, to try to fix it, as:
sudo apt-get --reinstall install plasma-...