Project Neon provides daily builds of KDE modules for Kubuntu. It is an easy way to get the latest code without having to build the entire KDE-Git/SVN tree and maintain the checkout. Project Neon is unstable, but it installs alongside stable packages. It is suitable for contributors such as new developers, translators, usability designers, documenters, promoters, and bug triagers. With Project Neon, people can experiment freely without risk to a working KDE environment.
Project Neon is especially useful for reporting bugs. With its daily builds, bugs can be reported in the most timely manner. The more time that elapses between when a bug is introduced and when it is reported, the more difficult it gets to find it and fix it. With Project Neon, a bug can be reported on the same day that it is introduced.
Introducing Project Neon KVM
The Project Neon team has developed another product—Project Neon KVM Image. Users can download an image and deploy it anywhere, using KVM virtualization technology. Now Project Neon is available more widely.
Project Neon KVM is for people who use a Linux distribution other than Kubuntu or a non-Linux operating system. Without disturbing the host environment, Project Neon KVM can be used to test new KDE releases, to try out new features, or to develop something entirely new.
The image contains a bare install of Project Neon daily build packages. Project Neon KVM images are built weekly and can be downloaded directly or as a torrent. At least 2GB's of RAM are suggested to run these images. Alternatively, ubuntu-vm/run.sh in the tarball can be edited to allocate less memory to the KVM. The default username/password for the VM is 'neon' (without the quotes).
The Project Neon team is on Freenode IRC at #project-neon. Mailing list information and archive are available at https://launchpad.net/~neon.
A special thank you to Jonathan Riddell for hosting the images.
Once we download the KVM image, will it be able to stay up to date via apt-get update/dist-upgrade, or do you have to download the KVM image every week or two?
Either method is fine, though if bandwidth is constrained, I'd suggest just using
sudo apt-get update && sudo apt-get dist-upgrade
It would be great if the debian packages would also be brushed up a little. They seem to need more love than the ubuntu ones.
Unfortunately the Kubuntu team is absolutely stretched to the limit, while we try and contribute back to Debian as much as we can, so while Debian users have to wait a bit longer, I'm sure they can try out our shiny KVM images to checkout what awesome features that they're going to get in the next release ;)
Great initiative! When trunk builds become more common an application will gain stability.
Would it be possible to switch-off/auto-detect compositing in a more convenient way? With compositing activated my screen gets black.
I ran into a small issue and noticed the crash dialogue in Neon desktop, but then grabbing for the debug packages failed, virtually trashed the desktop by heavy writing on the hard disc. Why aren't for a test desktop environment as Neon debug symbols installed by default?
In a virtual machine KWin should fall back to XRender-based compositing. I don't see any reason why this should not work. If you can figure out what is going wrong, please report a bug.
Thanks for the reply, I fixed it for me but I am not sure everyone can. ;-)
KVM switches are popular among users who have upgraded their home PC systems and want to still use their old computers but do not want to invest in a second keyboard, monitor and mouse.
So more users can participate in testing. If it only worked on Debian 7.
./run.sh: 3: exec: kvm: not found
# aptitude install qemu-kvm
Setting up qemu-kvm (1.1.0+dfsg-3) ...
ERROR: could not insert 'kvm_intel': Operation not supported
[FAIL] Module kvm_intel failed to load ... failed!
invoke-rc.d: initscript qemu-kvm, action "start" failed.
Setting up bridge-utils (1.5-4) ...
Setting up sharutils (1:4.11.1-1) ...
Could not access KVM kernel module: No such file or directory
failed to initialize KVM: No such file or directory
No accelerator found!
Looks like its failing to insert the kvm kernel module, I am afraid you will have to figure this one out using Google.