http://bugzilla.opensuse.org/show_bug.cgi?id=959849 http://bugzilla.opensuse.org/show_bug.cgi?id=959849#c2 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #2 from Wolfgang Bauer <wbauer@tmo.at> --- As you are already using Plasma 5.5.1 from an additional repo, could you please try with the latest Dolphin 15.12.0 from KDE:Applications repo? I cannot reproduce this problem here (13.2, Plasma 5.5.1, Frameworks 5.17.0, KDE Applications 15.12.0). Although such a problem (application not quitting when closed, caused by a bugfix in KF 5.17) is only known so far for Kate and Ark (and I've seen it with Konqueror5 too but that hasn't been released yet... ;-) ), where it has been fixed in 15.12.0. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=959849 http://bugzilla.opensuse.org/show_bug.cgi?id=959849#c4 --- Comment #4 from Wolfgang Bauer <wbauer@tmo.at> --- (In reply to Mark Fairbairn from comment #3)

ok - I've just switched Dolphin to the updated apps repo (haven't switched everything to that repo)and will keep an eye on it for the next few days.

You should probably switch at least Kate and Ark too, as those are affected as mentioned. Opening a text file or archive in dolphin *might* cause dolphin to hang too because the corresponding application (Kate or Ark) does not quit. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=959849 http://bugzilla.opensuse.org/show_bug.cgi?id=959849#c6 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |farcusnz@gmail.com Flags| |needinfo?(farcusnz@gmail.co | |m) --- Comment #6 from Wolfgang Bauer <wbauer@tmo.at> --- So, how's the status here? Is this still a problem? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=959849 http://bugzilla.opensuse.org/show_bug.cgi?id=959849#c8 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(farcusnz@gmail.co | |m) --- Comment #8 from Wolfgang Bauer <wbauer@tmo.at> --- (In reply to Mark Fairbairn from comment #7)

I do still occasionally see it

Hm. I still haven't seen that a single time.

but mostly after a plasma freeze and the need for a hard reboot(running intel graphics) - but dolphin opening up here is probably unrelated (although it does tend to open up even if there were no instances of dolphin open at the time of the freeze).

Well, if you do a hard reboot, the previous session is being restored, as the session is of course only stored on logout. But then, you already should have had dolphin being restored in the current login... If it happens the next time, could you maybe tell the exact command line with which dolphin is being started? To get that, hover over the dolphin process(es) in ksysguard (Ctrl+ESC), or run "ps ux|grep dolphin". Should give a clue whether it's being restarted by the session manager or not, and might even hint at the problem in any case. In this case (hard reboot after a freeze) it could also be caused by some filesystem inconsistency I suppose, but I think that's hardly a reason why (only) dolphin should be restarted. Still, also try to delete ~/.config/ksmserverrc, and see if that "fixes" your problem. -- You are receiving this mail because: You are on the CC list for the bug.