kexec-tools causes improper reboot in lmde

Bug #741083 reported by viking777
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Linux Mint
Incomplete
Undecided
Unassigned

Bug Description

LMDE 32bit
After the installation of kexec-tools during todays updates it is no longer possible to reboot the computer properly. The reboot process reaches the point "stopping early crypto disks......done" then immediately starts up with "will now restart with kexec".
The resulting desktop is slow and unresponsive and can only be cured by a complete shutdown and cold boot.
Even if this was not the case, rebooting should bring you to a grub menu, not restart another kernel on top of the old one which is what appears to be happening.
Problem is 100% reproducible and is solved by removing the package kexec-tools.

Revision history for this message
viking777 (viking-f2s) wrote :

As the package kexec-tools is no longer being offered for installation with new updates I would consider the bug to be closed.

Revision history for this message
Laegnur (laegnur) wrote :

Hi!

I install "Linux Mint XFCE RC" and this also happens to me.

Revision history for this message
Clement Lefebvre (clementlefebvre) wrote :

Please share more info on the version of kexec-tools causing the problem.

Changed in linuxmint:
status: New → Incomplete
milestone: none → lmde-201104
Revision history for this message
Mr. Aljoriz Dublin (aljoriz) wrote :

Alternatively you can enter this code and answer NO so that kexec-tools will no handle reboots:

$ sudo dpkg-reconfigure kexec-tools

Revision history for this message
Mauro D'Aloisio (maurodaloisio) wrote :

I have the same problem. I'm running LMDE 64 bit fully updated

mauro@lmde ~ $ apt-cache policy kexec-tools
kexec-tools:
  Installato: 1:2.0.1-4
  Candidato: 1:2.0.1-4
  Tabella versione:
 *** 1:2.0.1-4 0
        500 http://ftp.debian.org/debian/ testing/main amd64 Packages
        100 /var/lib/dpkg/status
mauro@lmde ~ $

Revision history for this message
Mauro D'Aloisio (maurodaloisio) wrote :

The workaround proposed in comment #4 works fine for me

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.