Description of problem: 1) user must know to be patient not to reset the machine 2) When / is encrypted or in an encrypted LVM, user do not see the dialog to enter the key when the system reboots after kdump finished. Steps to Reproduce how it currently works: 1. install fedora with / in an encrypted LVM 2. configure and test kdump 3. trig it while you are in a graphical desktop Actual results: 1) Screen freeze 2) kdump work - invisibly ; user need to know to be patient not to reset the machine 3) new boot, in a text terminal it is waiting for encryption key, but the user still look at the frozen desktop image...! (This is my own experience) Wanted results: 1) Switch to text mode showing message that crash dump is getting saved. 2) kdump kernel saves dump 3) reboot new kernel, and user can see key dialog. Additional info: Initiated by discussion in https://bugzilla.redhat.com/show_bug.cgi?id=1028397#c15
Arthur, can you help on this issue?
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Adding any other logic in crash path will be objected in upstream, because we will firstly make sure crash dump success. It is not reliable to do anything else in a panicked kernel. Sorry, it is a known issue but there's no solution for this now. Will address this once we have a good way to reset the graphic on early boot phase