Language Selection

English French German Italian Portuguese Spanish

GNOME 3.2 Release Candidate Is Here, 'Final' Landing in One Week

Filed under
Software

GNOME 3.2 is almost here, the team has made available the release candidate version for testing and the final build is expected to land in a week.

If you can't wait for that long or want to help some of the remaining bugs, if any, you can grab the sources and see what the second update to the third major iteration of the GNOME desktop environment looks like.

The GNOME team is done with major revamps for a while, GNOME 3.2 is all about polish, adding new features and improving existing ones.

"It's the last step, it's the release candidate, it's shining gold, it's 3.1.92, it's out! So, what are you waiting for? Download it! Build it! Test it! Try to break it!," the release announcement read.

Rest here




More in Tux Machines

Gnumeric 1.12.23 Open Source Spreadsheet Editor Brings Fuzzed File Hardening

The development team of the open-source Gnumeric spreadsheet editor software used in numerous GNU/Linux distributions announced the immediate availability for download of Gnumeric 1.12.23. Read more

Wily Werewolf Alpha 2 Released

The second alpha of the Wily Werewolf (to become 15.10) has now been released! This alpha features images for Kubuntu, Lubuntu, Ubuntu MATE, Ubuntu Kylin and the Ubuntu Cloud images. Pre-releases of the Wily Werewolf are *not* encouraged for anyone needing a stable system or anyone who is not comfortable running into occasional, even frequent breakage. They are, however, recommended for Ubuntu flavor developers and those who want to help in testing, reporting and fixing bugs as we work towards getting this release ready. Read more

Samsung docs detail Linux TRIM bug and fix

We've been covering a report from search provider Algolia pointing out a potential issue in Samsung SSDs' TRIM implementation. More recently, Samsung itself reported that the bug actually resides in the Linux kernel, and that the company had submitted a patch for the problem. Now, we have more details of the bug. Samsung has provided us with internal documents detailing the exact cause of the issue, and the subsequent solution. We're geting a bit technical here, so we'll take some liberty to simplify. When Linux's RAID implementation receives a sequence of read or write operations, it creates separate buffers in memory for each of them. Read more

Google Play Store/Chrome Web Store