Category Archives: Korora

Korora related posts.

The new Anaconda installer

It’s no secret that the new Anaconda installer for Fedora 18 has caused a stir. As part of a major internal re-write, the user interface has been completely re-designed which has caused some confusion and there are bugs and missing features. This is why we included an install video in Korora 18, to help walk you through the process.

However, like all good free and open source software, while this might be the case now it will just keep getting better (especially if users report their problems and post ideas on Bugzilla). Fedora 18 was so delayed that the community didn’t have a chance to address all issues in the interface, unfortunately. Some of the badness has already been fixed for the next release however, with more improvements to come.

So, yes, it might be hard to use for this release but it’s getting better. And thankfully it’s just the installer and not the rest of the interface, so it’s a one-off pain, not an every day one. If it’s really a drama, one could install version 17 and use FedUp to upgrade without using the new installer.

Finally, Anaconda developer Will Woods an excellent blog post on the re-write, which really opens your eyes to the need for it (it’s much, much more than just the user interface).

Here’s some of the content:

Why rewrite, anyway?
Back in August 2009 we were trying to redesign the storage UI to handle modern storage needs. This turned out to require rewriting a lot of the storage back-end code (again) because the existing anaconda code was basically all duct tape and bubble gum, creaking under the strain of modern demands.

You might think I’m exaggerating, but keep in mind that anaconda was originally written in 1999, for Red Hat Linux 6.1, It was designed to run off a 1.44MB floppy, using the still-newish Linux 2.2.x kernel.

In 2009 it still had its own custom initrd init system – called “loader” – written entirely in C. (Statically-linked, too, until 2007.) So anaconda had its own copy of stuff like mount(), and losetup, and mknod.. but no bash before the GUI started. (Good luck trying to debug anything!)

The design pre-dated udev and /sys – and devfs, HAL, and NetworkManager, and dbus – and had its own builtin module loading stuff instead of depmod and modprobe. So anaconda was doing all the hardware setup (probing, module loading and unloading, network setup, disk setup, RAID setup, etc., etc.) by itself… and not always doing it well. And every time there was a new device driver for anything we had to manually add support for it to the installer.

And specifically on the user interface:

And then there’s the GUI. It was single-threaded, so (for example) while we waited for lvm or yum to do something the UI would just.. stop drawing. If you dragged a window around you just ended up with big empty gray blotches until lvm finished and let us start refreshing the UI again.

It was also designed for much smaller screens – 640×480, or 800×600 if you were lucky. You can’t fit much on a screen that size (smaller than your average smartphone!), so it made sense to break the process into a series of steps. Except by 2009 you ended up with screens that looked like this [when setting the root password]:

root password
Great use of space there!

The logic for moving between steps had also gotten really hairy and fragile. Like, as soon as you finished partitioning the disk (but before you picked software to install!) we formatted the disks, because we used to need swap space to even think about running yum. But then what happens if it turns out you need more hard drive space to install the stuff you want? TOO BAD, YOU CAN’T GO BACK NOW!

So on behalf of Korora Project please forgive us for causing you frustration, but we’re here to help and believe us when we say it is already improving!

Bug: Korora 18 KDE installer sometimes not loading

Update: Try running the installer from the command line with two commands, like so:
xhost +

A couple of users have reported that running the installer under the KDE live image does not do any thing, i.e. the loading cursor appears run but no program loads. This does not appear to affect GNOME.

If you run it from the terminal you get a error about X and GTK.

[liveuser@localhost ~]$ liveinst
No protocol specified
xhost: unable to open display ":0"
Starting installer, one moment...
anaconda 18.37.11 for Fedora 18 started.
No protocol specified
** (anaconda:1940): WARNING **: Could not open X display
No protocol specified
Traceback (most recent call last):
File "/sbin/anaconda", line 923, in
setupDisplay(anaconda, opts)
File "/sbin/anaconda", line 585, in setupDisplay
File "/usr/lib64/python2.7/site-packages/pyanaconda/", line 213, in initInterface
from pyanaconda.ui.gui import GraphicalUserInterface
File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/", line 22, in
import meh.ui.gui
File "/usr/lib/python2.7/site-packages/meh/ui/", line 23, in
from gi.repository import Gtk
File "/usr/lib64/python2.7/site-packages/gi/", line 76, in load_module
File "/usr/lib64/python2.7/site-packages/gi/", line 244, in _load
overrides_modules = __import__('gi.overrides', fromlist=[self._namespace])
File "/usr/lib64/python2.7/site-packages/gi/overrides/", line 1624, in
raise RuntimeError("Gtk couldn't be initialized")
RuntimeError: Gtk couldn't be initialized

We think this might be this upstream bug, however nothing concrete has been discovered.

Please try booting again after a power-cycle with your network cable either plugged in or out, the opposite of what it was when it wasn’t working. Please let us know how you go with this, especially if anyone finds something repeatable.

Update: Try running the installer from the command line with two commands, like so:
xhost +

Korora 18 (Flo) beta released

NOTE: Kororaa Linux has changed to the Korora Project and moved to a new website at

The Korora Project is pleased to announce the first beta release of version 18 (codename “Flo”) which is now available for download.

Derived from Fedora 181 stable, this release comes with the usual Korora extras out of the box, but now also includes:

  • Adobe Flash plugin
  • Experimental support for Valve’s Steam client
  • unburden-home-dir, which moves cache files (like in Firefox profiles) onto RAMFS at login
  • undistract-me, which pops up a GUI notification when a terminal command has completed

It is now possible to upgrade from Kororaa 17 to Korora 18, thanks to Fedora’s FedUp tool.

This is a beta and we’d love to hear about your experience so that we can make it better! Please send us feedback in the forums or log a bug report if you have any issues. Of course you can find us on social media like, Twitter, Google+ and Facebook.

1 Korora is not provided or supported by the Fedora Project. Official, unmodified Fedora software is available through the Fedora Project website.

Introducing the Korora Project

It’s with great pleasure that I announce that Kororaa Linux is changing to the Korora Project. We haven’t just been super busy working on the new 18 release, but also setting up this new project and everything that goes with that!

The motivation for this was not only the dropping of an excess letter ‘a’, but it’s also a reflection of the community which is starting to grow nicely and I wanted something people could better associate with and belong to.

The new website has been set up at and feedback is welcome (although be gentle, we’re still ironing out any kinks). All future news will be posted to that site, however the current domain will stay live for the foreseeable future also.

The forum has been migrated to the site and existing users will need to change their passwords.

Finally, I must send out a massive thank you to Ian (firnsy) Firns, who has done an amazing job not only with the new site and content but also helping to build the 18 release, including our new build system which makes life so much easier. Without him, this simply would not have been possible and as such he has become the first official Korora co-developer. Thanks firnsy!

P.S. The new Korora 18 images really are just around the corner, we’ve delayed to add some exciting new features such as out of the box support for Adobe Flash and inclusion of Valve’s Steam client. Stay tuned (on!

Work around NVIDIA blue screen bug, by downgrading version (Update: fixed NVIDIA version released)

Update: New version 304.32 has been released which apparently fixes this issue, so this is no-longer neccessary. If you have already done this to get a working system and locked the version, remove then and update.
sudo vim /etc/yum/pluginconf.d/versionlock.list && sudo yum clean all && sudo yum update

Thanks to zektor in the Kororaa forums for posting this fix. It is reported on RPMFusion’s Bugzilla and

The 300.x.x series NVIDIA driver (currently beta) has a bug which causes some newer GPUs to have a blue tinge on the screen. In Kororaa, Jockey installs this latest version.

If your card is supported by the previous version, you can downgrade to this to solve the problem, then lock yum so that it doesn’t upgrade to 300.x.x series.

Remove existing:

sudo yum erase *\nvidia\*

Downgrade version:
sudo yum install akmod-nvidia-295.53-1.fc17.1 \
xorg-x11-drv-nvidia-libs-295.53-\*.{x86_64,i686} \
xorg-x11-drv-nvidia-295.53-1.fc17 \
nvidia-settings-1.0-18.fc17 \

Lock version:
sudo yum install yum-versionlock
sudo yum versionlock akmod-nvidia-295.53-1.fc17.1 \
xorg-x11-drv-nvidia-libs-295.53-\*.{x86_64,i686} \
xorg-x11-drv-nvidia-295.53-1.fc17 \
nvidia-settings-1.0-18.fc17 \

Now you can reboot your machine.

Kororaa 17 (Bubbles) released

It is my pleasure to announce the release of Kororaa 17 (codename “Bubbles”) which is now available for download. Although I delayed this release by two weeks, unfortunately only half a dozen or so mirrors have currently synchronised the ISO images. Please be patient with slower downloads until the rest complete. Thank you.

We are starting to get a nice little community around Kororaa and I’d to thank everyone for their help and support, which is greatly appreciated. I’d like to especially thank the following three people (in alphabetical order), who have all played a crucial role in making this release possible:

  • Ian Firns (firnsy)
  • Jim Dean (ozjd)
  • Liam Campbell (lijcam)

Derived from Fedora 171, this release comes with the usual Kororaa extras out of the box, such as:

  • Tweaked KDE and GNOME base systems
  • Experimental support for Cinnamon desktop in GNOME
  • Third party repositories (Adobe, Chrome, RPMFusion, VirtualBox)
  • Firefox as the default web browser (with integration theme for KDE)
  • Firefox extensions enabled (Adblock Plus, DownThemAll, Flashblock, Xclear)
  • Instant messaging client (Kopete for KDE, Empathy for GNOME)
  • Microblogging client (Choqok for KDE, Gwibber for GNOME)
  • Full multimedia support (excluding Flash, see next)
  • Adobe Flash plugin installable via package manager
  • Jockey device manager to handle drivers such as ATI and NVIDIA
  • Video editor (Kdenlive for KDE, OpenShot for GNOME)
  • VLC as the default media player
  • SELinux enabled (particularly worthwhile for Flash)
  • English (Australian/British) support & dictionaries
  • and more..

GNOME 3 comes with two desktops – the default Shell (plus fallback mode) as well as experimental support for Cinnamon desktop from Linux Mint. Shell includes a number of extensions to provide an enhanced user experience (and help ease the transition from GNOME 2.x), and Cinnamon has also been designed to provide a more comfortable experience. Kororaa also includes GNOME Tweak Tool to put further customisation at the user’s fingertips.

GNOME Desktop Cinnamon Desktop
Kororaa 17 GNOME desktop Kororaa 17 Cinnamon desktop

The KDE desktop has a custom layout with specific default applications, such as Firefox for the web and VLC for media. KDE has long shipped the Netbook interface, designed for computers with smaller screen real estate.

KDE Desktop KDE Netbook Desktop
Kororaa 17 KDE desktop Kororaa 17 KDE Netbook desktop

It is still recommended that existing Kororaa users perform a fresh install and users still on Kororaa 15 should install 17 as the older version is no longer supported upstream.

We’d love to hear your feedback on the forums, so download it today and let us know!

Note: Kororaa is not provided or supported by the Fedora Project. Official, unmodified Fedora software is available through the Fedora Project website.

Kororaa 17 syncing to mirrors

Kororaa 17 has been ready for a few weeks now, but it is taking a very long time to sync to SourceForge mirrors. In addition, some bots picked up the new files and posted a release announcement (although I had not yet done one) which caused the few mirrors that had been sync’d to get hammered and as a result they dropped the files.

This has happened a few times now so I have changed the 17 release to staging mode for 3 days in the hope that it will be enough time to sync enough mirrors. When there are enough, I will release the files and post an announcement.

Sorry for the delay…

Kororaa 17 delayed

I was hoping to release Kororaa 17 by the end of this month, but it will most likely be delayed by a few weeks. I’ve been struggling mostly with getting SELinux to play nicely with Jockey, after upstream added a jockey module to default selinux-policy (which is a good thing). I think I have it cracked now, but it will need a lot of testing as it has now become a much complicated. In addition, there is an ATI driver coming which needs testing and I’m hoping to switch to akmods by default in this release, which also needs testing.

The other thing I was planning to release was an install DVD and I’ve run into issues there also, blockers with filesystem related I think to the removal of /bin and /sbin, etc. Not sure what to do on that one yet, so it might not happen.

I also need to fix some GNOME extensions which aren’t working (like alternate status menu) and customise Cinnamon at users’ requests (I haven’t even had time to really look at it yet).

The good news is that changes between the beta and final will all be pushed out via regular system updates, so if you’ve installed the beta you will probably not need to re-install. The only thing you’ll miss out on are any changes to default user skel like certain settings and mozilla profile updates, etc. Updating and then creating a new user will work around this, but there are unlikely to be any major changes any way.