SUMMARY After having saved a session, which includes Dolphin, unpon restarting KDE, two instances of Dolphin are opened: one on the proper desktop, and another on desktop 1 (upper leftmost of of a grid of 8, 4 columns x 2 rows). Deleting the redundant instance (desktop 1), and re-saving the session does not change the startup behavior. STEPS TO REPRODUCE 1. Place all running apps in preferred desktops and locations 2. Save Session 3. Shut down and restart OBSERVED RESULT Saved instance of Dolphin is properly located on saved desktop and location. An additional instance of Dolphin is located on desktop 1. EXPECTED RESULT Only one instance of Dolphin should be opened on saved desktop and in proper location. No other instance of Dolphin should be open on any desktop. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
*** This bug has been marked as a duplicate of bug 336990 ***
Note: all other apps are restored to their proper desktops. Dolphin is the only one not restoring properly* *The Google Chrome browser has not worked properly for years - never restores on startup although it does open on proper desktop when started manually. But then that's another story ;)
(In reply to Nate Graham from comment #1) > > *** This bug has been marked as a duplicate of bug 336990 *** If this old bug has already been resolved then why is it still appearing more than 6 years later? What is the solution or how do I fix it, Please?
Whenever I try to save the current session, this error is sent to the log (using journalctl -f): Nov 10 00:55:04 localhost.localdomain plasmashell[2124]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:285:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
(In reply to David Allen from comment #3) > (In reply to Nate Graham from comment #1) > > > > *** This bug has been marked as a duplicate of bug 336990 *** > > If this old bug has already been resolved then why is it still appearing > more than 6 years later? What is the solution or how do I fix it, Please? That bug report isn't resolved, it's still open.
(In reply to Nate Graham from comment #5) > (In reply to David Allen from comment #3) > > (In reply to Nate Graham from comment #1) > > > > > > *** This bug has been marked as a duplicate of bug 336990 *** > > > > If this old bug has already been resolved then why is it still appearing > > more than 6 years later? What is the solution or how do I fix it, Please? > That bug report isn't resolved, it's still open. Sorry, my misunderstanding. I thought that since the status says "Resolved duplicate of 336990",that meant this one was resolved as well. Or maybe I misunderstand the meaning of the status field? Anyway, thanks for your clarification.