On Fri, 2014-05-30 at 17:57 +0300, Victor Porton wrote: > 30.05.2014, 17:52, "Khalid Aziz" <kha...@debian.org>: > > On Fri, 2014-05-30 at 16:51 +0300, Victor Porton wrote: > >> 30.05.2014, 16:32, "Khalid Aziz" <kha...@debian.org>: > >>> That means you are seeing the gnome issue. I have seen it on my machines > >>> for some time where just plain reboot with kexec disabled only brings me > >>> to login screen or the getty prompt. It definitely does that when any > >>> user, even myself, is logged in on any of the virtual consoles or logged > >>> in remotely. If kexec reboot works from virtual console, kexec is > >>> working normally. I suspect you will see the same problem with reboot > >>> even if you disable kexec. > >> `sudo reboot` (without kexec) works for me both from virtual console and > >> gnome terminal. > > > > Are you using sysvinit or systemd? > > Both are installed. I am not sure which of them runs. I think it is sysvinit, > but I'm not sure. > > -- > Victor Porton - http://portonvictor.org
I spent some time playing with kexec-tools with systemd installed. kexec-tools is definitely not systemd-ready. If you do have systemd-sysv package installed, you are running systemd, and kexec-tools is unlikely to initiate a kexec reboot. Can you verify if you are on systemd or sysvinit? -- Khalid -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
