Per Sebastien's comment, I have added a couple of sentences about this
to the Intrepid release notes.  I trust that's OK.

I think Martin Soto's assessment is spot on.  It _is_ worrying that
Ubuntu should (as a matter of policy) be so sanguine about this.  It's
also surprising that GNOME developers should have been happy to take a
broadly working session manager, remove much of its session management
support on the basis of some concerns about architecture and code
quality, and push the result as if it were a stable point update.

Would it be so hard (this is just an aside about Gnome, not about
Ubuntu) to temporarily revert any changes elsewhere in Gnome that depend
on the new DBUS session API, pull the "new" gnome-session back out to a
branch until it works properly, and revert to the 2.22 session manager?
I suppose that would feel like a backward step and make few friends
among developers.


Chris

-- 
gnome session does not restore the previous session
https://bugs.launchpad.net/bugs/249373
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

Reply via email to