Created attachment 115586 [details] Grey backgruond SUMMARY I have installed the LabPlot2 on Fedora 28 Scientific (KDE Plasma) using Program Center. After the start of LabPlot2 its window has only a grey backgruond and there is no any reflection on my actions. Restart of the system and Reinstall of the LabPlot do not help. In addition, I have installed and use succefuly the LabPlot2 on my labtop and workstation with the same OS. VERSIONS (available in About System) KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.48.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION
I checked the package on a regular Fedora 28 and could not reproduce this problem. Are you using the updated packages 2.4.0-9? If it works on the same OS on another computer the package seems to be ok. Can you run "labplot2" in a terminal to see any error message that might give a clue?
It is seemed I have found the reason. The labplot starts successefuly in terminal under the root. But how it was happen? I did the same actions for instalation on all my computers.
Created attachment 115648 [details] Not root start
Created attachment 115649 [details] After the not root start
Created attachment 115650 [details] start under the root
Created attachment 115651 [details] Successeful work under the root
Can you try to start LabPlot without any options ("labplot2" without "-qwindowtitle ...")? If it runs as root, the problem is located in the user settings. Can you add a new user and try to start it under the new user? If that works, just remove the user specific settings in $HOME/.config of your normal user.
(In reply to Stefan Gerlach from comment #7) > Can you try to start LabPlot without any options ("labplot2" without > "-qwindowtitle ...")? > If it runs as root, the problem is located in the user settings. Can you add > a new user and try to start it under the new user? If that works, just > remove the user specific settings in $HOME/.config of your normal user. If I start LabPlot without any options then there is the same problem. The way with new user does decide the problem. Unfortunately, I cannot find the file with specific user settings. Moreover, the start with terminal is comfortable for me. Thank you so much for your help!
Resetting the user configuration should should fix this problem for the user if it works for another user. Closing the ticket here.