http://bugzilla.opensuse.org/show_bug.cgi?id=967538 http://bugzilla.opensuse.org/show_bug.cgi?id=967538#c1 --- Comment #1 from Stakanov Schufter --- Created attachment 666321 --> http://bugzilla.opensuse.org/attachment.cgi?id=666321&action=edit crashtxt of kontact (result of crash ksmserver) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967538 http://bugzilla.opensuse.org/show_bug.cgi?id=967538#c3 --- Comment #3 from Stakanov Schufter --- Created attachment 666322 --> http://bugzilla.opensuse.org/attachment.cgi?id=666322&action=edit crash of ksmserver with nvidia/amd hardware As I have another system with leap (on an AMD with Nvidia Graphics) which I updated this morning. I wanted to try what this would do, to discern, if this is graphic card dependent or not. No, on both system the crash rate is close to 100 % and a multiuser function is not given anymore. Just one user at the time. Unlike what I thought before, it is stable, and even after the first crash, it continues to crash. I put in attachment the file from this nvidia based system because konqui claimed that the informational content is maximal (compared to the one before from the intel based system. There were also a crash of k5init (I recall that, do not rely on the name) and of kmail of course. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967538 http://bugzilla.opensuse.org/show_bug.cgi?id=967538#c4 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Summary|"New Session" in the |"New Session" in the |application menu doesn |application menu doesn't | |work (and might even crash | |ksmserver) --- Comment #4 from Wolfgang Bauer --- I can confirm that "New Session" in the application menu doesn't work. And it causes ksmserver to crash if you select it a second time IME. I changed the title appropriately, and hope you agree (the original one was far to general and actually misleading IMHO). The user switching has been completely reworked in 5.5. Plasma has a proper user switcher now and doesn't "misuse" KRunner for that any more. But apparently something has not been hooked up properly. As a workaround, you can lock the screen and choose "New Session" there. This works fine here. There's also a new "user switch" plasmoid, I think that should work as well, but I haven't tried it. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967538 http://bugzilla.opensuse.org/show_bug.cgi?id=967538#c6 Luca Beltrame changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lbeltrame@kde.org, | |stakanov@freenet.de Flags| |needinfo?(stakanov@freenet. | |de) --- Comment #6 from Luca Beltrame --- Can this be tried from a konsole window, just in case to check that everything is working? qdbus org.kde.ksmserver /KSMServer org.kde.KSMServerInterface.openSwitchUserDialog -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967538 http://bugzilla.opensuse.org/show_bug.cgi?id=967538#c8 --- Comment #8 from Wolfgang Bauer --- PS: I found these upstream bug reports: https://bugs.kde.org/show_bug.cgi?id=357413 https://bugs.kde.org/show_bug.cgi?id=356945 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967538 http://bugzilla.opensuse.org/show_bug.cgi?id=967538#c10 --- Comment #10 from Wolfgang Bauer --- (In reply to Luca Beltrame from comment #9)

[11:50] <kbroulik> do you have automatic screen locking enabled?

Yes. Disabling the screen locker makes the "New Session" button work, but ksmserver still crashes when doing it a second time. And there's no change in behavior when using "breeze" as desktop and screen locker theme. I tried this to rule out a problem specific to the openSUSE theme.

[11:54] <kbroulik> when you Cancel the dialog and open it again it doesnt crash?

I already answered that: it crashes as well. So I think we have two separate problems here: - "New Session" not working (if the screen locker is enabled) - ksmserver crashing if you call the user switcher a second time They might be related, or not. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967538 http://bugzilla.opensuse.org/show_bug.cgi?id=967538#c12 --- Comment #12 from Stakanov Schufter --- (In reply to Luca Beltrame from comment #6)

Can this be tried from a konsole window, just in case to check that everything is working?

qdbus org.kde.ksmserver /KSMServer org.kde.KSMServerInterface.openSwitchUserDialog Does do nothing but gives following CLI output

entropy@linux-cujp:~> qdbus org.kde.ksmserver /KSMServer method bool org.kde.KSMServerInterface.canShutdown() method QString org.kde.KSMServerInterface.currentSession() method bool org.kde.KSMServerInterface.isShuttingDown() method void org.kde.KSMServerInterface.logout(int, int, int) method void org.kde.KSMServerInterface.openSwitchUserDialog() method void org.kde.KSMServerInterface.restoreSubSession(QString) method void org.kde.KSMServerInterface.resumeStartup(QString) method void org.kde.KSMServerInterface.saveCurrentSession() method void org.kde.KSMServerInterface.saveCurrentSessionAs(QString) method void org.kde.KSMServerInterface.saveSubSession(QString, QStringList, QStringList) method QStringList org.kde.KSMServerInterface.sessionList() signal void org.kde.KSMServerInterface.subSessionCloseCanceled() signal void org.kde.KSMServerInterface.subSessionClosed() signal void org.kde.KSMServerInterface.subSessionOpened() method void org.kde.KSMServerInterface.suspendStartup(QString) method void org.kde.KSMServerInterface.wmChanged() method QDBusVariant org.freedesktop.DBus.Properties.Get(QString interface_name, QString property_name) method QVariantMap org.freedesktop.DBus.Properties.GetAll(QString interface_name) signal void org.freedesktop.DBus.Properties.PropertiesChanged(QString interface_name, QVariantMap changed_properties, QStringList invalidated_properties) method void org.freedesktop.DBus.Properties.Set(QString interface_name, QString property_name, QDBusVariant value) method QString org.freedesktop.DBus.Introspectable.Introspect() method QString org.freedesktop.DBus.Peer.GetMachineId() method void org.freedesktop.DBus.Peer.Ping() entropy@linux-cujp:~> org.kde.KSMServerInterface.openSwitchUserDialog If 'org.kde.KSMServerInterface.openSwitchUserDialog' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf org.kde.KSMServerInterface.openSwitchUserDialog So if this is not an error of my part on what to input, it does not work for me. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967538 http://bugzilla.opensuse.org/show_bug.cgi?id=967538#c14 --- Comment #14 from Stakanov Schufter --- (In reply to Wolfgang Bauer from comment #13)

(In reply to Stakanov Schufter from comment #12)

...

So if this is not an error of my part on what to input, it does not work for me.

You need to put everything on *one* line, i.e. there should be no line break between "qdbus org.kde.ksmserver /KSMServer" and "org.kde.KSMServerInterface.openSwitchUserDialog".

qdbus org.kde.ksmserver /KSMServerorg.kde.KSMServerInterface.openSwitchUserDialog Path '/KSMServerorg.kde.KSMServerInterface.openSwitchUserDialog' is not a valid path name. like this? This is in one line Or do I have to su for it? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967538 http://bugzilla.opensuse.org/show_bug.cgi?id=967538#c16 --- Comment #16 from Stakanov Schufter --- (In reply to Wolfgang Bauer from comment #15)

(In reply to Stakanov Schufter from comment #14)

...

like this? This is in one line

You "forgot" the space between "/KSMServer" and "org.kde.KSMServerInterface.openSwitchUserDialog" now.

I probably should have mentioned that explicitly... ;-)

...

Or do I have to su for it?

No, rather the opposite. You *have* to run it as (the logged in) user. It won't work as root.

OK. That works and opens the dialogue. It does not crash immediately but of course it has no functionality. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967538 http://bugzilla.opensuse.org/show_bug.cgi?id=967538#c18 --- Comment #18 from Stakanov Schufter --- (In reply to Luca Beltrame from comment #17)

I've talked with the upstream developer and now he understood the cause of the problem: he'll try to fix it for the next Plasma 5 release (5.5.5) which should be next week.

That is good news. As I said I am positively surprised by the speed of reaction. "Kudos" to all involved. Have a good day. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967538 http://bugzilla.opensuse.org/show_bug.cgi?id=967538#c20 --- Comment #20 from Stakanov Schufter --- (In reply to Wolfgang Bauer from comment #19)

(In reply to Luca Beltrame from comment #17)

...

I've talked with the upstream developer and now he understood the cause of the problem: he'll try to fix it for the next Plasma 5 release (5.5.5) which should be next week.

But please note that at the moment this only applies to "New Session" not working if the screen locker is enabled though.

The upstream developer apparently is not able to reproduce the crashes...

That is, on a machine with Leap he does not have this problem? Or does it indicate that this is not a KDE but (partially) a downstream problem? In other words: as I can trigger and reproduce it "on command", is there anything I could provide to further help to find the problem? (List of packages installed, further debugdumps etc?). Please do not hesitate to ask. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967538 http://bugzilla.opensuse.org/show_bug.cgi?id=967538#c23 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|"New Session" in the |"Switch User" in the |application menu doesn't |application menu doesn't |work (and might even crash |work (and might even crash |ksmserver) |ksmserver) Flags| |needinfo?(stakanov@freenet. | |de) --- Comment #23 from Wolfgang Bauer --- @stakanov: Can you please give libQtQuick5 from here a try and report back whether it fixes the crashes (or causes unexpected side effects)? http://download.opensuse.org/repositories/KDE:/Qt5/openSUSE_Leap_42.1/ But please note that this only should fix the crashes. "Switch User" not working at all if automatic screen locking is enabled is a different problem as mentioned, and will be fixed by the running Plasma update to 5.5.5. PS: adjusted the bug title. The application menu entry is actually called "Switch User" but it's incorrectly translated as "New Session" in 5.5 in the german translation at least. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967538 http://bugzilla.opensuse.org/show_bug.cgi?id=967538#c25 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(opensuse-kde-bugs | |@opensuse.org) | --- Comment #25 from Wolfgang Bauer --- (In reply to Stakanov Schufter from comment #24)

Sorry if I am asking but, could I give you feedback on Monday?

If you prefer to, no problem. But of course the sooner I submit an update, the sooner this will be fixed for other users... ;-)

Or otherwise said: are there any "quirks" to be expected?

Not really. I am not completely sure that everything will continue to behave correctly in case the patch is triggered, but without it there will be a crash anyway at that point. That said, I haven't noticed anything strange here upto now, neither on my 13.2 systems nor on a Leap 42.1 VM. And it fixes the crashes reliably here. I'll try to explain a bit: The crash happens in the JavaScript interpreter when a new String object is allocated but a non-string is passed as value. This is not allowed and should not happen, but it apparently does in some circumstances. My patch checks whether the passed value is really a string, and just returns if not, thus preventing the crash. So it doesn't fix the actual problem, it only prevents the resulting crash. But I don't see much point in debugging QMLs JavaScript interpreter code to find the real bug, especially considering that it seems to be fixed in Qt 5.6 anyway (at least I cannot reproduce the crashes with 5.6). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967538 http://bugzilla.opensuse.org/show_bug.cgi?id=967538#c28 --- Comment #28 from Stakanov Schufter --- Created attachment 669984 --> http://bugzilla.opensuse.org/attachment.cgi?id=669984&action=edit crash of B (after the crash of user D, all user now subsequently crash). This is the second crash in the row. I hope this gives you some more info. I would say it is easier to avoid the feature (as I did before) and to use ctrl+alt+FNx to switch. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967538 http://bugzilla.opensuse.org/show_bug.cgi?id=967538#c30 Stakanov Schufter changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(opensuse-kde-bugs | |@opensuse.org) --- Comment #30 from Stakanov Schufter --- I did install your patch. It draws in about 10 packages from the repo as dependency. If you do, when you finish and restart, you end up with sddm allowing you only the login to ice-wm. No other desktop option allowed. IWM does start but this is of course not a desired solution. Please let me know if there is something I have to check. I think currently, by using the repo (which uninstalls kde4 branding and installs kde5 branding) you are not operative in kde. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967538 http://bugzilla.opensuse.org/show_bug.cgi?id=967538#c32 Stakanov Schufter changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(opensuse-kde-bugs | |@opensuse.org) --- Comment #32 from Stakanov Schufter --- Now I have installed your patch. As for the problem: it seems to work well, but I would wait for one day of continuous usage. As for side effects: I have now silent crashes of Kontact. "No survivors", you have to restart the whole application. Kontact 5.1 showed already before severe inconsistency as compared with version 4. It did and does not show new email in separate folders for pop after filtering. While the new messages are there and marked as unread. (If this is not known up to now I can report it. There has been a bug report upstream, but it was closed as solved about the release of 4.3. Well then this is a regression. Moreover, now that the patch is installed, it crashes silently (and also very fast) when moving the window of Kontact. If this is connected i can revert to kmail4. But it may be a problem to other users. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967538 http://bugzilla.opensuse.org/show_bug.cgi?id=967538#c34 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(opensuse-kde-bugs |needinfo?(stakanov@freenet. |@opensuse.org) |de) --- Comment #34 from Wolfgang Bauer --- (In reply to Stakanov Schufter from comment #33)

Update: I am using that patch now a while. I encounter here since install of it a problem with shutdown.

Hm, are you sure this is related? I.e. does the problem disappear if you switch libQtQuick5 back to the standard version and reappear if you install mine again? I don't see how a patch to libQtQuick5 should cause a problem with shutdown (but then, sddm does use it too)... If yes, could you please also try with the package from here? http://download.opensuse.org/repositories/home:/wolfi323:/branches:/home:/wo... This has one patch less. I originally branched from KDE:Qt5 which had an additional (upstream) patch to fix a (possibly huge) memory leak compared to Leap's version. But that's part of Tumbleweed since 2 months already, and I haven't encountered any problem with it here either. To be sure, I removed that now though in that new package, so it only additionally contains my patch to prevent the crashes, compared to the standard version in Leap 42.1. Just for understanding: if you select "Shutdown" in the Plasma session, you only get back to sddm (or not), and then it hangs? Or are you choosing shutdown on the login screen? Does it work from there? And which sddm theme are you using? I suppose that *might* have an influence... Also, does this happen with a single session, or when multiple sessions are open? Is this happening reliably/unconditionally, or what exact steps do you take to trigger it? If the mouse cursor shows up on the text screen, it would seem to me like sddm is hanging... Could be caused by my patch, but then it would crash at this point without the patch IMO. (In reply to Stakanov Schufter from comment #32)

As for side effects: I have now silent crashes of Kontact. "No survivors", you have to restart the whole application.

This patch can't have any influence on Kontact, as Kontact does not use libQtQuick5 at all. Also, as mentioned the patch only *prevents* a crash. If that causes another crash, the application would have crashed already in the first place without the patch.

Kontact 5.1 showed already before severe inconsistency as compared with version 4. It did and does not show new email in separate folders for pop after filtering. While the new messages are there and marked as unread. (If this is not known up to now I can report it. There has been a bug report upstream, but it was closed as solved about the release of 4.3. Well then this is a regression.

4.3 was long before KMail has been ported to Akonadi. The code (and even the architecture) is completely different meanwhile, so that bug report is irrelevant here (even though the symptoms might be similar). I see you commented there, but that's pointless, better open a new one. There have been some important bugfixes in Akonadi (and KDEPIM5) recently though (e.g. in regard to moving messages) that will be in 16.04 (to be released in April). I haven't seen a problem here with POP, but then I don't use (client-side) filters any more. Sounds like the filters may change the read/unread flag. I'd suggest to verify that the filter(s) are not setup to do that by mistake. Could of course also be caused by a bug when moving messages, i.e. that the flags get lost in that case for example. But please, let's not continue that here. This is a completely different problem, and not even remotely related... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967538 http://bugzilla.opensuse.org/show_bug.cgi?id=967538#c36 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(opensuse-kde-bugs | |@opensuse.org) | --- Comment #36 from Wolfgang Bauer --- (In reply to Stakanov Schufter from comment #35)

If I did read well the recent update published should have fixed the ksm-server issue.

No. How do you get that idea? The last update contained KDE Applications 15.12.3, and there was an update to KDE Frameworks 5.20.0 too, both are unrelated. The Plasma update to 5.5.5 released a week ago fixes the problem that "Switch User" does not work at all (if automatic screen locking is enabled). The libQtQuick5 package I offered for testing should fix the crash. But if it may cause such a shuttdown regression with sddm as you described, I won't submit it as update. It works perfectly here though, so I cannot investigate. So please, test the second version from comment#34. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=967538 http://bugzilla.opensuse.org/show_bug.cgi?id=967538#c38 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS --- Comment #38 from Wolfgang Bauer --- (In reply to Stakanov Schufter from comment #37)

The patch works. The shutdown problems are there but are independent of the patch.

Good! (or not, depending on how you look at it...)

I checked with a fresh install (from scratch) on the notebook. Same issues. So you can free the patch as the patch works as expected avoiding the crashes.

Ok, I will submit an update then... Thanks for your testing! :-) -- You are receiving this mail because: You are on the CC list for the bug.