Description of problem: when running plasma desktop as a normal user, after getting a root shell via sudo and running emacs the entire desktop hangs (clock freezes, no applications take input). Switching to another VT and running "killall emacs" frees the desktop. Version-Release number of selected component (if applicable): xfconf-4.13.6-2 How reproducible: every time Steps to Reproduce: 1. login to kde plasma as a non-privileged user 2. sudo -s 3. emacs Actual results: desktop hangs until emacs is killed Expected results: emacs gui appears, desktop is still usable. Additional info: This happens on 'real' systems with radion, intel and nvidia graphics, and also under virtualbox. Using an older version of xfconf (4.13.5-20) or removing xfconf entirely allows emacs to run normally. Possibly this is an emacs or plasma bug, but removing xfconf is a workaround.
So, I guess you have both KDE and Xfce installed? xfconf is the xfce config store. Can you attach 'journalctl -b -l' after this? also, can you try 'strace -f emacs' instead of just emacs and see where it stalls? I can't off hand think of why this could happpen.
Created attachment 1525285 [details] output of journalctl -b -l Removed entries from well before test was run
Created attachment 1525287 [details] output from strace -f emacs
To generate the strace I re-installed xfconf, created an at job to killall emacs after 2 minutes then ran strace -f emacs. I had installed xfce for testing, but I am not using it, so removing xfconf is possible.
If I ssh to F30 from a plasma session on F28 or F30 I see the same desktop hang when running emacs. It can also be worked around by removing the xfconf package, but that breaks xfce sessions which we use for X2go connections. On the hung desktop I still have a mouse pointer that I can move around but sometimes it disappears when I move it over the currently 'active' konsole window. Emacs is the only application that I have seen which triggers this behaviour. Happy to help debugging this.
This seems to be caused by the new gsettings backend somehow. If I: mv /usr/lib64/gio/modules/libxfconfgsettingsbackend.so /usr/lib64/gio/modules/libxfconfgsettingsbackend.so.off the problem goes away and I can run emacs over ssh. xfce still seems to work as a desktop environment. According to this: https://mail.xfce.org/pipermail/xfce-announce/2018-October/000644.html one should be able to disable the gsettings backend with the environment variable GSETTINGS_BACKEND but its not set in my shell and I haven't been able to find where its set for the xfconfd. While investigating this I found that simply moving the libxfconfgsettingsbackend.so to .off and back again to the proper file name seems to be enough to get a working emacs over ssh. That makes no sense to me at all.
Yeah, I am really not sure what to make of this either. Perhaps you would be willing to file this upstream at bugzilla.xfce.org?
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.