I've verified that this is still a problem in Ubuntu 18.04 nightly.
You need two hard drives available, as it otherwise won't ask you which
drive you want to overwrite.
I've attached screenshots of the UX issue. If you only have one hard
drive, then screen 3 does not happen, and "Install Now" on
5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: zeyelth1921 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Thu May 21 13:05:44
Just updated to 5.4.0-33.37 and it did not fix it
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879939
Title:
Audio stopped working after 5.4.0-31 kernel update
To manage notifications about this
Updated to 5.4.0-37.41 and the bug appears to be fixed!
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879939
Title:
Audio sto
Confirmed to still be an issue in 13.04.
It is also worth pointing out that this bug has potential security and
privacy implications if the DNS server provided by the local ISP can't
be trusted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
This is a usability bug where the user is given incorrect feedback from
the installer, potentially resulting in the user canceling the
installation for fear of erasing data on the wrong drive.
When installing Ubuntu 14.10 (ubuntu-14.10-desktop-amd64.iso) and
selecting "Erase
Updating the BIOS solved the cold reboot issues for me a long time ago.
Motherboard: Asus P7P55D
BIOS ver. which supposedly fixed it: 2003.
Machine do seem to lock up under heavy traffic in Ubuntu 11.10 though,
but I am not sure if this is due to a recently introduced bug, or a
change in network
I had the same problem with package "amarok 2:2.3.0-0ubuntu4" (Ubuntu
10.04, 64bit). Updating to "amarok 2:2.3.1-1ubuntu1~lucid1~ppa2" by
adding the "ppa:kubuntu-ppa/backports" repository seems to have fixed
it.
--
Amarok does not quit (and therefore cannot be started again)
https://bugs.launchpa
I had the same issue with my Asus R1E Tablet PC under Ubuntu 10.04. All
the events worked, but the script responsible for rotating the screen
simply didn't update the tablet rotation.
Wrote a patch which takes care of it. Works for me on my tablet, but I
can't test it on other tablets, so YMMV.
*
