https://bugs.kde.org/show_bug.cgi?id=406140
Bug ID: 406140
Summary: "sudo emacs" makes plasmashell run at 100% CPU
Product: plasmashell
Version: 5.14.5
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: dhe...@gmail.com
CC: plasma-b...@kde.org
Target Milestone: 1.0
SUMMARY
When I run 'sudo emacs' in KDE, the graphical interface freezes due to 100% CPU
usage by plasmashell. I am forced to switch to a terminal (Ctrl+Alt+F2), then
kill all Emacs processes before I can use the interface again.
Using the terminal, I see that there is a plasmashell process running at 100%
CPU. Killing Emacs restores things to normal.
STEPS TO REPRODUCE
1. run 'sudo emacs'
2. KWin freezes with 100% CPU usage
OBSERVED RESULT
Unusable interface.
EXPECTED RESULT
Emacs should open normally.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Fedora 29
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.55.0
Qt Version: 5.11.3
ADDITIONAL INFORMATION
I have Fedora 29 on a different machine (both are Lenovo laptops) and 'sudo
emacs' has been working for years. The main difference is the new machine has
an Nvidia card with Optimus, so I had to install proprietary drivers otherwise
I couldn't even boot into X.
Emacs seems to be the only application which does this. 'sudo gparted', 'sudo
libreoffice', etc, all work normally. Running Emacs without sudo works
normally.
After killing emacs via a terminal, when I switch back to the terminal running
KWin, the following notification is visible:
"KWin Window Manager" - desktop effects were restarted due to a graphics reset.
I'm almost sure the bug is related to the Nvidia proprietary drivers, but I
wonder if there is a way to disable something in KDE that would allow it to
work again, or at least a way to better diagnose why running Emacs as sudo
causes this behavior.
--
You are receiving this mail because:
You are watching all bug changes.
