> I don't care about session management: because I do not restart the
session, I restart the session whenever the system freezes

Under these premises, it would be a matter of clarity to state from the
main KDE web page that KDE development mainly focuses on single user
workflows and that the desktop support for multiuser environments can at
best be casual. Would have saved most of the whining here.

> That should be obvious - users should stick to LTS and AFAIK an LTS
doesn't offer the upgrade. User's choice: you can have the latest and
greatest (e.g. 15.04) or stay with the more stable  offering.

Unfortunately, it is not this simple. It is not LTS -> 15.04, so you
stay with LTS and you are done. It is LTS -> 14.10 -> 15.04.  Those who
switched from LTS to 14.10 had no information at all that they would
have been compelled into Plasma 5 while "there are still monsters" (in
Thomas' words). Conversely, they got reassured multiple times about the
fact that Plasma 5 would have been offered as a technical preview side
to side with Plasma 4 until it was ready, and that the Plasma 3 ->
Plasma 4 transition mistakes would have been avoided.

In any case, now that the damage is done, let's try to limit it as much
as possible. Can someone help identify:

- if wily's qt 5.4.2 contains the same fixes that are in the Fedora
package mentioned above and if it can be safely backported to vivid in a
ppa

- what additional patches are needed on top of the kwin package
contained in the kubuntu kde backports ppa, to see if a fixed package
can be shipped in a further PPA

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446865

Title:
  kwin does not remember on which desktop to open windows on session
  start

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to