This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1793508
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1793508
Title:
no matching swap device at initramfs
Status in linux package in Ubuntu:
Incomplete
Bug description:
This is the result of a well-known - wrong - behaviour.
It happened to me with the upgrade from 16.04 to 18.04. Google gives plenty
of help, unambiguously.
Like
https://www.kubuntuforums.net/showthread.php/72993-initramfs-tools-looking-for-non-existant-swap-partition
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861151
https://askubuntu.com/questions/1060917/from-swap-partition-to-swap-file-now-get-no-matching-swap-devide-is-available
and many more.
However, I couldn't find a bug report for it. It struck me at the upgrade
from kubuntu 16.04 to 18.04. I have now done what was suggested elsewhere. Yet,
I could not find a real explanation nor a bug report. In my case, like in many
of those, the UUID for resume was kind of 'out of the blue'. And once changed
to the real UUID for the swap device, everything is fine.
However, I am not happy with a situation like that. Many a user that we tried
over the last 20 years to adopt Linux as main OS will not want to search Google
for this bug, and will not want to vi (or similar) some system file.
Therefore I take the liberty to report this. From the dates of the posts, it
seems that this bug has been lingering for quite some time, Wouldn't it be the
right moment to prevent it from striking again?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793508/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
