Originally this sounded like a duplicate of bug 1431200, as that's
pretty much the only point in time when an upgrade of the systemd
package could even remotely trigger a graphics state change, by
accidentally reloading/restarting some units like plymouth. But you said
that this happens on upgrading non-systemd systems, so systemd can't
possibly do that. Installing/upgrading things like console-setup-linux
could very well do that, though.
Do you have a way to reproduce this? By e. g. "sudo apt-get install
--reinstall systemd", or reinstalling other packages from that set, like
console-setup-linux?
With "non-systemd systems", did you mean you upgraded from e. g. utopic,
or that you manually installed upstart-sysv again to continue running
upstart under vivid?
** This bug is no longer a duplicate of bug 1431200
daemon-reload runs alsa-restore.service and others
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** No longer affects: apt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1428712
Title:
Screen turns green and locks out during apt full-upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1428712/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
