I suggest closing this bug report. I think there's a bug in how the GRUB
configure scripts handle this kind of error but it's unrealistic
anyone's going to fix it in this old version. I've given up trying to
upgrade my system.
FWIW I managed to get dpkg to reconfigure and find a new path for GRUB.
Just tested this again, problem is still there. Is there any hope for a
fix for grub-efi-amd64 to reconfigure the device in the 23.10 upgrade
context? If not my system is going to be trapped running 23.04 with no
way to upgrade safely, which means I need to find a workaround.
--
You received this
Boy this bug is vexing. Another report of this bug has info that it was fixed
in the Curtin sources in December 2018.
https://bugs.launchpad.net/curtin/+bug/1527664
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Public bug reported:
Installing biosdevname can result in a system that will not have working
networking on reboot. I think there should be a warning / dialog when
the package is installed that warns users they need to do further system
configuration after installation.
biosdevname creates a udev
I believe Ubuntu 14.04 now ships with Apache 2.4 by default, but Munin
has not been updated to the 2.4-style configuration file. At least, I
just set up Ubuntu 14.04 with a naive "apt-get install apache2 munin
munin-node", and wasn't able to access http://localhost/munin/.
Something like jm-3's pa
Hey guys,
So, I was looking for Ubuntu because Win Xp is not supported anymore. I
carefully readed everything here, but i have no clue how i could fix my problem.
Can please someone explain what i have to do, in a language that a
"noob" like me can understand? I never did anything with linux.
-
I should add that 148 systems using this Realtek ethernet controller are
listed as Ubuntu Certified Hardware. Either those systems have something
special that makes them work, or the certification process missed this
driver problem.
http://www.ubuntu.com/certification/catalog/component/pci:8168:10
This bug has a long and sad history; see Ubuntu bug 141343 from 2007 for
instance. This bug is also reported in every other Linux system I've
looked for; the problem seems to be in the Linux kernel, not any
specific distribution. My understanding is that the right driver is
being installed, in that
