[Bug 959849] New: multiple instances of Dolphin opening on boot
http://bugzilla.opensuse.org/show_bug.cgi?id=959849 Bug ID: 959849 Summary: multiple instances of Dolphin opening on boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs@opensuse.org Reporter: farcusnz@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.80 Safari/537.36 Build Identifier: Leap 42.1 with plasma 5.5.1 When booting, plasma randomly loads instances of dolphin. Session is set to restore on boot but Dolphin in prev sessions have always been closed (so this indicates that the process wasn't really terminated on close) Setting to start with a new session stops the problem. Today on boot - plasma kindly started six instances of dolphin for me. Reproducible: Sometimes -- 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#c1
--- Comment #1 from Mark Fairbairn
http://bugzilla.opensuse.org/show_bug.cgi?id=959849
http://bugzilla.opensuse.org/show_bug.cgi?id=959849#c2
Wolfgang Bauer
http://bugzilla.opensuse.org/show_bug.cgi?id=959849
http://bugzilla.opensuse.org/show_bug.cgi?id=959849#c3
--- Comment #3 from Mark Fairbairn
http://bugzilla.opensuse.org/show_bug.cgi?id=959849
http://bugzilla.opensuse.org/show_bug.cgi?id=959849#c4
--- Comment #4 from Wolfgang Bauer
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#c5
--- Comment #5 from Mark Fairbairn
http://bugzilla.opensuse.org/show_bug.cgi?id=959849
http://bugzilla.opensuse.org/show_bug.cgi?id=959849#c6
Wolfgang Bauer
http://bugzilla.opensuse.org/show_bug.cgi?id=959849
http://bugzilla.opensuse.org/show_bug.cgi?id=959849#c7
Mark Fairbairn
http://bugzilla.opensuse.org/show_bug.cgi?id=959849
http://bugzilla.opensuse.org/show_bug.cgi?id=959849#c8
Wolfgang Bauer
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.
http://bugzilla.opensuse.org/show_bug.cgi?id=959849
http://bugzilla.opensuse.org/show_bug.cgi?id=959849#c9
Karl Cheng
participants (1)
-
bugzilla_noreply@novell.com