Language Selection

English French German Italian Portuguese Spanish

Who Was To Blame For The Ubuntu BIOS Bug?

Filed under
Security
Ubuntu

So who is to blame for the corruption of the BIOS?

Ultimately I would put the majority of the blame at the door of the manufacturers and the BIOS developers. You simply should not be able to corrupt the BIOS and there should be a reset option which returns it to factory settings if all else fails. The Ubuntu developers were the unlucky people to instantiate the bug by including a defective driver within the Kernel.

Some of the blame has to go to the users as well. Maybe we need to be a bit smarter when installing operating systems and not necessarily jump at the latest thing.

Read more

More in Tux Machines

Audiocasts: Full Circle Weekly News, mintCast and GNU World Order

KDE: Usability & Productivity Report From Nate Graham

  • This week in Usability & Productivity, part 54
    This week in KDE’s Usability & Productivity initiative, something big landed: virtual desktop support on Wayland, accompanied by a shiny new user interface for the X11 version too. Eike Hein has been working on this literally for months and I think he deserves a round of applause! It was a truly enormous amount of work, but now we can benefit for years to come.
  • KDE Now Has Virtual Desktop Support On Wayland
    KDE landing virtual desktop support on Wayland this week is certainly quite exciting while also a new UI was added for the X11 virtual desktop support too. Some of the other KDE improvements that landed this week and relayed by Nate Graham include the digital clock widget now allowing adjustments to the date formatting, the KDE Information Center's USB devices section will now actually display all USB devices, wallpaper chooser view improvements, and various other improvements.

Screenshots/Screencasts: Robolinux 10.4 LXDE, deepin 15.9, and Parrot OS 4.5 KDE

Livepatching With Linux 5.1 To Support Atomic Replace & Cumulative Patches

With the Linux 5.1 kernel cycle that should get underway in just over one month's time, there will now be the long in development work (it's been through 15+ rounds of public code review!) for supporting atomic replace and cumulative patches. Read more