Bug fixes, code freezes, and PBI speed increases! There’s lots of exciting news this week in PC-BSD so let’s have a look.
PC-BSD 10.0 Release has entered into the “code freeze” phase of development. In order to increase stability and focus on prioritizing bug fixing, major feature changes under the hood should no longer be committed for 10.0 Release. Trac ticket owners are encouraged to finish and submit your cosmetic / general bug fixes as soon as possible.
PC-BSD release candidate 4 (p3) is currently being built and is expected to be finished sometime over the weekend. Please click here to check and see if the latest image is currently available. If it is not available please check again later.
The PC-BSD update system has received quite a bit of new stability improvements in the form of additional code. Users can expect to see an improvement in the form of less errors during updates and an overall smoother update transition between builds.
Here’s a quick recap of some other awesome new features / bug fixes that have been committed over the last week. Please test and report any problems as quickly as possible so we can make sure 10.0 Release will be ready to roll (no pun intended) when the time comes.
- Most recent package set for 9.2 is currently being uploaded
- Improved Nvidia video card detection routines
- The PBI format received a substantial upgrade over the course of the week allowing for PBI load times to be reduced in some cases up to 40%.
- A fix has been implemented for the virtualbox driver
- New wine PBI’s have just finished testing, and should be available in the next couple of days
- Fixes have been committed for missing shortcut keys in the PC-BSD installer
- Keyboard layout issues have been resolved for multiple desktop environments
- Auto-mount detection has been improved for multiple desktop environments
That’s it for this week folks. Please keep us informed if you have problems that are persisting in the newest Release Candidate image.
2013 is gone, and a new PC-BSD image is here. We are now in 10.0 Release Candidate 3 (p2) and are moving very quickly towards final release. There is still some fine tuning that we are working on, so keep those bug reports coming. There are some awesome new key features / support features that have been added so let’s have a look at what’s new in PC-BSD land.
The guys and gals at the PC-BSD project continue to push the envelope on cutting edge features. This week a new detection routine was finished that will offer simple detection on ATI Hybrid Graphics enabled laptop computers. The new detection system was tested on a Samsung NP350 that would stall during installation because X was not able to detect either graphics card properly during the installation and first start-up respectively. Now if the first video card fails X detection, a message will be displayed that it could not be started. It will then try the next one. More research and development is needed to see if we can apply this same fix to laptops using Nvidia as well.
For any of our testers out there that want to stay as cutting edge as possible and also assist in the current development in PC-BSD 10 Release, please go ahead and upgrade to the newest image by clicking here. We are in a time crunch now, but we want to make sure we find any major / critical bugs and get them squashed ASAP. Also I am still looking for testers to help us isolate any issues with the HPLIP package when installed while other printers (i.e brother, epson, etc) are installed as well. The goal is too possibly add more printer support to PC-BSD, however please understand this is something for down the road and will not be a quick fix. If you need more specific information about our goals with this side project please send me an e-mail at firstname.lastname@example.org.
New logic has been added to handling disk detection during PC-BSD installation. There was an issue in the gui install as well as text install where the 4k sector size option was causing an installation failure. If you were experiencing this issue and would like to test out PC-BSD 10.0 please go ahead and download the latest image and give it a go.
Special shout out to our Indonesian translation team for translating PC-BSD entirely into Indonesian Bahasa. Thanks for the hard work, and…record time for a translation to be completed. When I said “run with it” I didn’t actually know you were going to be able to finish it in 5 days. We went from having around 20% translated a few days ago to completely localized now, and we couldn’t be happier at the potential for reaching an entirely new market for us.
Due to the state of upstream support for Linux jails in FreeBSD we are re-classifying Linux jails as unsupported / experimental. The decision comes after frequent breaks in the way jails are handling the linux scripts and also the inability to handle advanced linux programs. We are hoping this is something that we can again start supporting in 10.1, but currently it is just too darned clunky to be called a supported feature. One thing Kris also mentioned to me in passing was that Linux jails were never meant to be pushed as far as they are sometimes pushed. We will continue to monitor the state of progress on this upstream and keep you informed on any information that comes our way.
That’s it for this week. You crazy kids stay out of trouble.
Just a short update today to let you all know what the low down is!
PC-BSD version 10.0 Release Candidate 2 is now live! Please note this is a beta-test release and NOT an official release. For more information on RC2 please visit the following blog page: http://blog.pcbsd.org/2013/12/pc-bsd-10–0-rc2-available/ . PC-BSD 10.0 Release RC2 can be downloaded from http://iso.cdn.pcbsd.org/.
Quick Note: Please report any bugs found @ trac.pcbsd.org. The window is closing to get bug reports in before official release and we need to try to get any “major” or higher priority bugs knocked out before then.
Kris has reported today that he is in the final stages of getting virtualbox working on PC-BSD 10.0. He has fixed many of the seg fault issues that we were seeing from previous versions and will be looking to have these packages ready in the next week or so hopefully by RC3.
AMD KMS support appears to be improving based on my first interactions with the new 10.0 release RC2 image. I’ve noticed much less graphical distortion, and better stability all around.
Tons of bugfixes and stability improvements went in today so big thanks to everyone involved for knocking those out. We are still aware of the issue with the FreeBSD bootloader not functioning, but rest assured Kris is putting in every effort to get this resolved for you quickly.
That’s it for this week folks!
The first PC-BSD 10.0-RELEASE image, based upon FreeBSD 10.0-RC2, is now available for download!
This image is still a pre-release version of the upcoming 10.0-RELEASE. There is a known issue with VirtualBox not yet working, so if you rely upon this functionality you should wait to update until it is fixed in RC3, or the official RELEASE.
Online updating to 10.0-RELEASE is not yet enabled, but will be for the next test revision based upon FreeBSD 10.0-RC3.
10.0-RELEASE notable features
- Includes FreeBSD 10.0-RC2 from 12/19/2013
- Updated KMS / AMD driver support
- ISO file is a hybrid USB file, and can be “dd“ed to a USB media.
- New text-based installer
- New UEFI loader on installation media
- Able to select between GRUB/BSD loaders during installation
- New desktops! Gnome 3, Mate (Replaces Gnome2) and Cinnamon
- And much more!
Found a bug? Please report it, in as much detail as possible, to our Trac database.
In the words of Dr. Sheldon Cooper (The Big Bang Theory TV Show), “i’m not insane…my mother had me tested”. That’s the way i’m sure many of the devs felt at the end of this week. While fending off the impending insanity caused by lack-of-flash-itis, the reason for our package issues with version 10.0 finally have started to come into focus. For more information on the package / pkgng debacle please see this blog post: http://blog.pcbsd.org/2013/12/end-of-the-pkg-woes/. Though we typically just recommend users just upgrade to new package sets, I personally opted to do a complete reinstall of 10.0 Beta P6. The primary issue myself and many other developers kept running into was issues with the centOS linux compatibility layer that was just too buggy to make good use of at this time.
In other similar news PC-BSD is likely to begin starting a new version naming system to help differentiate the different types of releases and hopefully offer a little more clarity to users that may be less than familiar with the conventional FreeBSD naming system. Along with the new naming system a new package release schedule will also be added to help users maintain more stability by not having to update their packages every couple of weeks. Stay tuned for more information on this as it develops.
Flash is now working in both firefox and chromium as well as many other internet browsers. The new PBI’s have been approved and include the fixes to make sure flash works with all the recent changes in version PC-BSD 10.0. For Chromium look for the version of 31 ending in .63. For Firefox look for version 25_01. I’m not sure if the issue is widespread but there was an additional step needed to make flash work in firefox on one of my primary test systems. If flash is working in other browsers, but not firefox run the command nspluginwrapper –v –a –i. For some reason flashpluginctl on / off was not running the script as it was supposed to. From most mainstream testing this looks to be a fairly minor and isolated issue.
PBI’s continue to be added to the PC-BSD AppCafe as well as tons of new compatibility updates for current 10.0 PBI’s. Total PBI’s ready for PC-BSD’s 10.0 release are now in excess of 720. PC-BSD version 9.2 has also been receiving tons of PBI updates so make sure to check those out as well!
Special thanks to Ken and Kris both as well for all the bug fixes you guys have committed this week (and for listening to my non-stop rants on why flash is so important). The schedule has been insane, but the light at the end of the tunnel is near.
As we go into the new year soon we’d like to tell everyone thank you and wish you the best during the holidays. I will now leave you with a bit of holiday cheer for all of who have or will experience that inevitable holiday computer failure.
Best Regards and Happy Holidays,
On the twelfth day I left it, my PC gave to me:
Twelve programs stalling;
Eleven chips a-smoking;
Ten ports a-jamming;
Nine jails a-frying;
Eight times i’m crying;
Seven blown partitions;
Six bad controllers;
Five seeeeeeg faults; (singer should hold out seg just FYI)
Four bad blocks;
Three bad controllers;
Two faulty pools;
And a burnt-out CPU fan.
Hey everyone, I just wanted to let you know that the recent issues with package updates should be corrected with the new package set that just came out.
The graphical package manager will not be able to update to the new package set, instead you will need to run the following command manually:
sudo pkg upgrade
If this fails because of a package conflict, you will need to remove the offending package before trying the upgrade again. For instance, a number of user’s have had to run this command first:
sudo pkg remove –f py27-distribute-0.6.35
Once you have updated to the new package set, the graphical package utility will work perfectly fine again (since it got updated itself).
General background on the problem:
With the update of the new FreeBSD package utility (pkg) from 1.1.x ->1.2.x, there were a number of errors due to a bunch of backwards compatibility being missing in the new version. This meant that once you updated to the newer version you no longer had access to the packages on the PC-BSD repository (due to the changes in the repo format). Since our new 1.2.x packages were just released on the PC-BSD repo, you should now be able to continue changing your packages again. Another issue that came with 1.2.x was that a number of the utility flags all got changed suddenly — causing our graphical utility to need updating as well. We got that utility updated fairly quickly, but the updated package was in the new 1.2.x format — meaning that you have to use the command line to perform this one upgrade.
We are terribly sorry for the inconvenience. Please let us know here or on the forums if you run into any other issues.