> Anyway, doing the same with version 4:4.13.3-1 could be interesting, but > resolving the dependencies could be more tricky. If you want to try it, that > is the approach for 4:4.14.0-1 (the last one obviously needs root > permissions): > > debsnap --architecture all kde-baseapps-data 4:4.14.0-1 > > debsnap --architecture all kde-baseapps 4:4.14.0-1 > > debsnap --architecture amd64 kde-baseapps-bin 4:4.14.0-1 > > debsnap --architecture amd64 kdepasswd 4:4.14.0-1 > > debsnap --architecture amd64 konqueror 4:4.14.0-1 > > find binary* -type f | xargs dpkg -i I just did the downgrade of the above packages to 4:4.13.3-1 and session management is working again. I had a typo in the commands of the last mail (fixed above to avoid confusion), as it obviously must be "amd64" instead of "amd" (or whatever architecture you are using), so the correct commands are > debsnap --destdir . --architecture all kde-baseapps-data 4:4.13.3-1 > debsnap --destdir . --architecture all kde-baseapps 4:4.13.3-1 > debsnap --destdir . --architecture amd64 kde-baseapps-bin 4:4.13.3-1 > debsnap --destdir . --architecture amd64 kdepasswd 4:4.13.3-1 > debsnap --destdir . --architecture amd64 konqueror 4:4.13.3-1 > dpkg -i *.deb Then, as a plausibility check, I upgraded from 4:4.13.3-1 to 4:4.14.0-1 again. After the first logout/login, konqueror restored the session correctly, as the session has been saved with a 4:4.13.3-1 version and loading with 4:4.14.0-1 seems to work. Another logout/login later, the session management stopped working again. So now we know, that 4:4.13.3-1 is the last known good package and 4:4.14.0-1 the first known bad package. We also know, that saving, not loading the session really is the problem. Kind regards Patrick
Attachment:
signature.asc
Description: This is a digitally signed message part.