https://bugzilla.suse.com/show_bug.cgi?id=1226110 https://bugzilla.suse.com/show_bug.cgi?id=1226110#c18 --- Comment #18 from Steffen Walter <swalter0306@web.de> --- (In reply to Fabian Vogt from comment #15)
(In reply to Steffen Walter from comment #14)
(In reply to Alessandro Soraruf from comment #13)
(In reply to Steffen Walter from comment #12)
(In reply to Alessandro Soraruf from comment #11)
Confirm that now session are saved, but as reported by Steffen Walter the session file name has changed, so after update users will loose all the old sessions. I've resolved copying my latest .config/session/konsole_xxxx session file into the new ones.
Hmmm... maybe I didn't get your solution right, but right now my latest .config/session/konsole_xxxx session file is dating from Thursday, June 6th 2024 16:25:33 CEST, which is pretty much when things stopped working altogether.
Newer session files are from other applications like dolphin, kdf ... after I received the fix on June 16th. But nothing new for konsole, although I've used it also in several sessions since patching.
If you look at your latest session file them have a new ID value after the application name, in this example the main "problem" was in konsole sessions:
...cut... konsole_10149e1e2d7000162292777200000021750016_1697324951_114676 konsole_10149e1e2d7000165799946700000020290012_1697480091_880313 konsole_10149e1e2d7000162292777200000021750016_1697639404_621519 konsole_10149e1e2d7000165799946700000020290012_1697639404_839539 konsole_10149e1e2d7000162292777200000021750016_1697639613_577384 konsole_10149e1e2d7000162292777200000021750016_1697663203_958785 konsole_10149e1e2d7000165799946700000020290012_1697663204_191830 dolphin_dolphin_dolphin kwin_saved at previous logout_ konsole_10149e1e2d7000171784449600000022590009_1718573630_340245 konsole_10149e1e2d7000171784464700000032710009_1718573630_329854
If you see the last two have new ID different from the previous one. On a therminal console (CTRL-F1) before logging in KDE I've done:
cp konsole_10149e1e2d7000162292777200000021750016_1697663203_958785 konsole_10149e1e2d7000171784449600000022590009_1718573630_340245
cp konsole_10149e1e2d7000171784449600000022590009_1718573630_340245 konsole_10149e1e2d7000171784449600000022590009_1718573630_340245
and this solved and now the session for that user are always saved fine.
That didn't help in my case, so I guess my problem is slightly different. What I tried next is to backup ~/.config/session and then delete the session files from the original. All this of course outside of KDE.
First I deleted dolphin* from ~/.config/session , logged into KDE and opened a new dolphin window. After closing my KDE session there was a new dolphin session file with the current timestamp in ~/config/session as I would expect. In the next KDE session, the dolphin windows was reopened again ==> Works.
The same I did with konsole but no avail. There is no new konsole session file after closing KDE in ~/.config/session . If I restore one from the backup directory, I see that the timestamp changes, but the content of the file is not updated. As a result there is no konsole window reopened in the next KDE session.
Any ideas on that behavior?
Check the output of konsole and the journal for warnings and error messages. You can check that "iceauth list" has valid output.
I discovered in the meantime that the issue is connected to the my main user on this machine while another user that is rarely used has a perfectly working session management again. So I'd like to reset or initialize this for my user - but that seems to be more complex than I thought. What I've tried so far: * Switching to "Start with empty session", reboot and switch back to "Restart last opened applications" * delete ./config/session and ./config/ksmserverrc from a console outside KDE and re-login Unfortunately both attempts did not help, so what am I missing? When I play around with the two users, I see some entries in /var/log/messages like 2024-06-23T13:07:40.281391+02:00 mob-kischdle4 ksmserver[4436]: Qt: Session management error: networkIdsList argument is NULL But these appear also with the user that is OK. I think these might be pointing to the heart of the matter, they appear only at the "damaged" user: 2024-06-23T13:07:40.908625+02:00 mob-kischdle4 kdeconnectd[4662]: Qt: Session management error: Authentication Rejected, reason : MIT-MAGIC-COOKIE-1 authentication rejected 2024-06-23T13:07:44.904210+02:00 mob-kischdle4 konsole[4778]: Qt: Session management error: None of the authentication protocols specified are supported 2024-06-23T13:09:11.401531+02:00 mob-kischdle4 dolphin[5389]: Qt: Session management error: None of the authentication protocols specified are supported 2024-06-23T13:23:02.513410+02:00 mob-kischdle4 konsole[9230]: Qt: Session management error: None of the authentication protocols specified are supported Ah, and "iceauth list" has similar output for both users like iceauth: creating new authority file /home/steff/.ICEauthority I guess best way to go would be to re-initialize the session management for (In reply to Fabian Vogt from comment #17)
(In reply to Steffen Walter from comment #16)
I think these might be pointing to the heart of the matter, they appear only at the "damaged" user:
2024-06-23T13:07:40.908625+02:00 mob-kischdle4 kdeconnectd[4662]: Qt: Session management error: Authentication Rejected, reason : MIT-MAGIC-COOKIE-1 authentication rejected 2024-06-23T13:07:44.904210+02:00 mob-kischdle4 konsole[4778]: Qt: Session management error: None of the authentication protocols specified are supported 2024-06-23T13:09:11.401531+02:00 mob-kischdle4 dolphin[5389]: Qt: Session management error: None of the authentication protocols specified are supported 2024-06-23T13:23:02.513410+02:00 mob-kischdle4 konsole[9230]: Qt: Session management error: None of the authentication protocols specified are supported
Ah, and "iceauth list" has similar output for both users like
iceauth: creating new authority file /home/steff/.ICEauthority
That means $ICEAUTHORITY is not set for some reason, which is essential for this to work. It's set by plasma-ksmserver.service.
Yes, that is true indeed, "echo $ICEAUTHORITY" brings up an empty line. How would I set that for this user? I could not spot that "plasma-ksmerver.service" in (In reply to Fabian Vogt from comment #17)
(In reply to Steffen Walter from comment #16)
I think these might be pointing to the heart of the matter, they appear only at the "damaged" user:
2024-06-23T13:07:40.908625+02:00 mob-kischdle4 kdeconnectd[4662]: Qt: Session management error: Authentication Rejected, reason : MIT-MAGIC-COOKIE-1 authentication rejected 2024-06-23T13:07:44.904210+02:00 mob-kischdle4 konsole[4778]: Qt: Session management error: None of the authentication protocols specified are supported 2024-06-23T13:09:11.401531+02:00 mob-kischdle4 dolphin[5389]: Qt: Session management error: None of the authentication protocols specified are supported 2024-06-23T13:23:02.513410+02:00 mob-kischdle4 konsole[9230]: Qt: Session management error: None of the authentication protocols specified are supported
Ah, and "iceauth list" has similar output for both users like
iceauth: creating new authority file /home/steff/.ICEauthority
That means $ICEAUTHORITY is not set for some reason, which is essential for this to work. It's set by plasma-ksmserver.service.
I see plasma-ksmserver.service running in sytemctl status. What do I have to do to get the environment variable set? -- You are receiving this mail because: You are on the CC list for the bug.