Created attachment 102828 [details] Errors and warning generated by plasmashell when started from a konsle window This happens on Fedora 24, 25 and Rawhide. Also, a few days ago the shell locked up, and, after I killed it, I restarted it from the konsole window (which was not closed when the shell was killed). There were a large number of errors and warnings displayed when the shell started. Many of these seem (to me) to be sloppy coding. Others (e.g., the lack of metadata every time my background image changes) seem to be caused by a failure to generate expected information when there's no reason to expect a casual user to know that your system expects - in this case - a directory containing several hundred images to have a "metadata" file.) Anyhow, for you perusal, I attach a copy of (some of) the messages generated when I restarted the shell.
The messages do not reveal any information why you do not see the Plasma desktop until VT switch. I suspect it is a video driver issue.
Can you give more info on the actual bug. You say the shell doesn't start, is this on every load of plasma shell from a terminal or just on login? Does this debug output continue immediately or only after the vt switch? Any issues with krunner (alt f2)?
If you can provide the information requested in comment #2, please add it.
Sorry, I overlooked this request. I haven't used that system for several weeks, but, IIRC, the problem was every time I loaded from a terminal. (I did try it several times before I reported it.) I was (again, IIRC) not starting after a VT switch, but from a konsol terminal running in a KDM window. On my system, the plasma shell has not started since Fedora 23. KDM runs, and (since I put Konsole in the .conf/autostart/) I've been mostly running KDE apps from a terminal. (By the way, I think that problem was because I deleted some configuration file that the installer ASSUMES to exist. I did several re-installs and updates since F-23 with no change to that behavior.)
Thanks for the update; changing status.
Thanks for the bug report Peter but I'm not sure we can really act upon it since information is missing or is presented in an incoherent way. And because you don't actually use the system any more. If it happens again to a clean system you use actively please feel free to create a new bug report and try to provide all necessary information in a clear tight way. Closing this bug report as invalid.