Oracle continues its tradition of sabotaging the users

Oracle continues its tradition of sabotaging the users

Below I blogged about Fedora 25 and its bugs.

As a part of that test I installed the latest VirtualBox 5.1.10.

You probably already know where this is going: of course, it did not work. Entirely. Completely. Totally.

Well, not entirely - the VB itself starts up and even allows you to create a VM. But that VM does not start. It complains about "some error code that occurred" and recommends running a command

sudo /sbin/vboxsetup

But when you run this command, it only throws several more errors, complaining of how this system is not set up for compiling the kernel modules and recommends, in turn, to run several Yum commands to install kernel_core_devel packages.

Well, guess what, those packages do not exist in the Fedora 25 repositories. A multi-billion corporation should have done due diligence and verified its setup before releasing a specifically Fedora 25 package of VirtualBox, instead of writing God knows what in a script and releasing it, hoping that it would work.

If they ever did their due diligence, they would have probably learned, that Fedora, starting with version 20, uses DMF instead of Yum for package management. What a bunch of irresponsible yahoos!

There are bug reports to Oracle for this, which they are in no rush to resolve, but you can fix the things very easily. more...

Posted by: LinuxLies at 09:34 AM | No Comments | Add Comment
Post contains 280 words, total size 2 kb.

Experimenting with Fedora 25 just for fun

Experimenting with Fedora 25 just for fun

Same old, same old - another bugged, untested release

For a long time I have an issue with the releases of Fedora from 14 till 19. They just do not work gracefully with AMD platform's sleep modes. Once Fedora goes to sleep, it either does not want to wake up at all, or wakes up everything but the monitor.

Once I realized that switching from XOrg console to a text console wakes up the monitor, but switching back puts it back into energy saving mode, I found a workaround to the later issue on Fedora 19: pulling out and re-inserting DVI cable wakes up the monitor in XOrg as well.

Just out of curiosity I decided to test and see if this bug has been fixed in the latest releases. Yes, this bug no longer exists. Hurray! But there exists another.

The freshly installed vanilla Fedora 25 never booted into the KDE desktop. It froze in the black (huh?) screen with the KDE logo and the spinning circle underneath. It just sat there after entering the login credentials. I decided to give it a little whack over the head and used the console switching trick. And then the desktop loaded!

This freeze apparently was not specific to KDE spash screen - the panel, desktop and application launcher menu froze upon clicking them until console was switched to text and back.

For a week now I have been faithfully installing every update that became available, but this bug still exists. According to a quick Google search Fedora 25 freezes all the time and for just about everyone. Another piece of turd released by the inept and reluctant "Open source developers" who do not give about their users. more...

Posted by: LinuxLies at 09:18 AM | No Comments | Add Comment
Post contains 657 words, total size 4 kb.