SUMMARY If I log out of my plasma session and then log in again, some apps will stop working properly, such as "evolution" (mail client). This does not happen in other DEs so I doubt the bug is from evolution. STEPS TO REPRODUCE 1. Launch a default plasma session. 2. Log out through Ctrl+Alt+Del or similar. 3. Log in again with the same user and everything else the same. 4. Launch evolution. OBSERVED RESULT Evolution does not log in to anything. EXPECTED RESULT Evolution should keep working, just like in the default session. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.0-3-amd64 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700 Eight-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD VEGA10 ADDITIONAL INFORMATION
Is the problem limited to Evolution, or does it affect other apps too? When you say it "does not log into anything", is that because it can't connect to the internet? Do you see this issue with other apps as well?
Created attachment 142837 [details] evolution_cannot_connect So far, I haven't noticed any other app presenting problems like this, but then again I don't use other apps that would log in to online services. I'm attaching a screenshot of the problems it throws, which happen also with option "--force-online". Clicking the "reconnect" button and going throw the gmail authorization dialog again has no effect (I do not receive a security alert from it, and it does not log in to my email in evolution).
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Information is already provided.
Are you using the systemd startup? You can find out with `kreadconfig5 --file startkderc --group General --key systemdBoot` If you're not using it, you can turn it on with `kwriteconfig5 --file startkderc --group General --key systemdBoot true` and then reboot. Can you try that and see if it fixes the issue for you? If so, you might just want to stick with systemd boot. If not, it will probably be fixed by https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1177.
(In reply to Nate Graham from comment #5) > Are you using the systemd startup? You can find out with `kreadconfig5 > --file startkderc --group General --key systemdBoot` > > If you're not using it, you can turn it on with `kwriteconfig5 --file > startkderc --group General --key systemdBoot true` and then reboot. > > Can you try that and see if it fixes the issue for you? If so, you might > just want to stick with systemd boot. If not, it will probably be fixed by > https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1177. Switching to systemd start didn't solve it, and introduced a new issue: if I set it to systemd start, log in, launch evolution, close it, log out, and launch evolution again, next time I restart the system it takes a very long time for plasma to start.
OK, in that case this will have been fixed by the fix for Bug 433293. *** This bug has been marked as a duplicate of bug 433293 ***