https://bugs.kde.org/show_bug.cgi?id=343518
--- Comment #48 from Wolfgang Bauer <wba...@tmo.at> --- (In reply to Piotr Mierzwinski from comment #47) > None of the tested by me applications are not restored after > relogin/restart. Where's the problem then? I suppose there is a typo in there... ;-) > I tested: Firefox, Thunderbird and new Opera. I think all > of them are based on GTK2. Actually not. At least Firefox can be build against GTK3 since a while and I think at least some distributions do that (openSUSE not, yet). So this might just be your point of regression... No idea about the others though. > All tested by me KF applications (konsole, > kwrite, dolphin) are restored correctly (including virtual desktop number). This proves IMHO that your problem is unrelated to *this* bug report, or the other one I marked this as duplicate of, which is about a problem in Qt5 as explained. > In Plasma 5.5.4 (ksmserver probably has the same version) Firefox and > Thunderbird were restored correctly. There has been no change to ksmserver (except see above), so another prove that this is not the same bug. > Looking what you are saying: 'I have heard of other users having problems > with Firefox in this regard since upgrading Plasma to 5.6 (or the beta).". I > also other persons also saying about problems, so maybe this is plasma 5.6.x > (ksmserver) bug. As mentioned, ksmserver hasn't been changed between 5.5 and 5.6. Except for this: https://quickgit.kde.org/?p=plasma-workspace.git&a=commit&h=5f0ca1305db4a925dbdbf927f541497be334feff According to the commit message it shouldn't be a problem though... If you are able to build plasma/ksmserver from source, I would recommend to do so with this patch reverted and see if it works then. > And if for you and for Paolo Carlini it is working then to who should to > report the bug? Good question, I don't know really. Maybe GTK3, or the applications affected. Or, as it might be a ksmserver bug after all (I never ruled that out), file a *new* bug report here. > I can add that the environment itself is pretty stable. I'm using it couple > of weeks and I didn't observe any crash. I never tried to imply in my previous comment that the environment is unstable. But your applications (or the toolkit they use) might be. Though not necessarily unstable per se, only just behaving incorrectly in regards to session management. -- You are receiving this mail because: You are watching all bug changes.
