Steve Langasek <[email protected]> writes: > On Fri, Jul 25, 2014 at 11:42:16AM -0700, Russ Allbery wrote:
>> I continue to be baffled by people's apparent belief that this >> happening during a major upgrade is some sort of regression. Having >> those buttons not work after a major component upgrade, until the X >> session was restarted, has been typical behavior for as long as I've >> been using Debian with a desktop environment. > The distinction is between having to restart your *session* and having > to restart your *system*. The systemd/logind issue introduces a > requirement for the latter, which /is/ a regression. Yeah, I just figured that out. I agree that's a regression. > I can't imagine how anyone can simultaneously hold the view that Debian > should use systemd for improved integration with end-user-targeted > desktop environments, and believe that Debian should leave these end > users grubbing around on the console to do something as fundamental as > rebooting their system after upgrade. This confuses me, however. Surely the difference between a one-time disruption and ongoing pain is too obvious to need stating? -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
