Currently, when I switch activities but I want to be able to access a program that is being used in the prior activity that I was using, I must do the following: 1.switch activities 2. switch back to activities 3.rightclick on appropriate application and say move to activity "blah blah" 4.switch back to the new activity This is fine, except that I have to do it all over again when I log back in again. The system should remember which programs I have set to what activities even after a shutdown / logout. As a side note, I thought I had read a while ago that they were going to implement this (a few years back), but perhaps I read wrong. Reproducible: Always Steps to Reproduce: 1.Set application to appear in multiple activities 2.logout and log back in 3. Actual Results: You will have to redo steps 1 and 2 to get desired results. Expected Results: activity should remember that the application is associated with it. Activities are the main reason that I stick with kde. They are great, but this would make it SO MUCH better.
I think this can be closed too. It seems to remember my app / activity associations in KDE 4.11.3 just fine, regardless of whether it is on activity, two, or all. BTW the first part of the description if this issue is confusing, but that seems to be what it is about.
" BTW the first part of the description if this issue is confusing, but that seems to be what it is about." Yes, I don't think we are talking about the same thing. Let me give a specific example. (sorry if it is long winded.) I have been working on masters project, and have an activity assigned for it. However, I always start my computer in the "desktop" activity. I ALSO auto-start thunderbird so that I can check email, so it starts in the desktop activity. However, when I start working on my masters project (finished, by the way =]), I want to continue to be able to read email if one comes in. In order to make this work, I have to do the steps listed above (or else switch activities everytime I use thunderbird, which I do not want to do). So, specifically for this case, I would have to do the following: 1. Switch from "desktop" activity to "school" activity 2. Switch BACK to "desktop" activity 3. Right click on the top portion of thunderbird's window and select either "school" activities or "all" activities. (This is the part that it should remember, but does not) 4. Switch BACK to "school" activity and start working.
Maybe I'm being dense but I think that's the sort of of ing thing I tried out. I can have app1 set to "desktop", app 2 set to "school", app3, set to "all', and app4 set to both "desktop" and "school". I can then restart and when it comes back up all 4 apps are set to exactly those same activities. I should note I'm not doing anythig to "auto-start" any apps. KDE is doing that for me...it is remembering I left them open and reopening them when I log back in. This is a setting in Workspace Behavior. Looking at that now I see that you can have it set to do that for all apps (as I have it set) or just specific ones. Is that how you are auto-starting Thunderbird or is it with some Thunderbird tool?
"it is remembering I left them open and reopening them when I log back in." Okay, I think I see the difference. I have thunderbird set as an autostart application in the system settings (startup and shutdown / autostart). But I am guessing that under session management (also in startup and shutdown) that you have it set for "restore previous session" whereas I have it starting with an empty session. I will have to test this out and see if it remembers the activity settings in this way. Either way, I consider it a bug, as you shouldn't have to re-enter it over and over if you have it set to an "empty session".
Hello! This feature request was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this feature request is already implemented in Plasma 5, or is no longer applicable. Accordingly, we hope you understand why we must close this feature request. If the requested feature is still desired but not implemented in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham