On Mon, Nov 24, 2014 at 9:23 AM, Jonathan Dowland <j...@debian.org> wrote: > On Mon, Nov 24, 2014 at 06:01:45PM +0900, Joel Rees wrote: >> 2014/11/24 17:18 "Jonathan Dowland" <j...@debian.org>: >> > I guess your argument makes sense if you are talking about all source >> packages >> > from the systemd stable, including logind; it's unlikely Patrick's init >> system >> > was switched to systemd-as-init as a result of upgrading. Either way >> though, >> > he's moved from a 'testing' system at some indeterminate point in the >> past to >> > a 'testing' system now; neither are 'releases' and so the release >> schedule has >> > little relevance to his situation. > > I don't have anything to add to the above, but I just wanted to point out > that your mailer seems to be mangling the quoting here. > >> So, are you saying he shouldn't report a bug? > > I'm not saying that, no. He should report a bug, if he can remember enough of > the details to make it a worthwhile report. Right now we have no idea what > piece of software was performing the suspending prior to upgrade.
I don't think I can responsibly report a bug as I have no idea which package I might report it against. This was a rather large upgrade of a testing system which had not been upgraded in quite awhile. Any number of things might have changed. I do think, though, that defaults, however sensible they may be (and suspending a laptop when the lid is closed and it is on AC power does not strike me as particularly sensible), should not be allowed to override settings I've made. Had I not had physical access to this server, I would have been screwed! Patrick -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cajvvksohyoymuwrdpa1glc7daqdefkcphj_fdv3sxj3wus-...@mail.gmail.com
