This means that pip being bundled by default—one of Python 3.4 coolest features—is missing. Trying to create a virtualenv using the bundled virtualenv module fails as well. Big mess.
Does that mean July 24th or might it be earlier, do you know?
Project manager: "But hey, we shipped on time!"
Because these corporations behave this way, it excludes them from the set of people Canonical has to worry about pleasing at release. So LTS releases, right on release, are actually allowed to be less stable than non-LTS releases. Because the majority of their useful lifetime, when anyone that matters is actually running them, will be spent stable.
Late adopters wait because they'd like somebody else to flush out the early bugs. If this is actually Canonical's plans, that 14.04.1 is the first release expected to be stable, then if I were a late adopter, I'd just wait for 14.04.2.
The let's-trick-people-into-adopting-something bit is basically an attitude of customer contempt. It's assuming that the release knows the customer's business better than the customer does. Whether it's right or wrong, it's a dick move, and acts to decrease trust.
Better for whom? Not for the people who take the LTS moniker seriously, I think.
Yes, Python is a mess. But, Python has been a horrific mess for years now, on multiple distros. I just ended up giving up on Python. Distro problems, 2/3 split, GIL and various other buggy nonsense slowly just reduced its value versus other languages.
sudo apt-get install xubuntu-desktop
sudo apt-get install lubuntu-desktop
I started with Gnome 3.10 (after ignoring it for most of it's existence except once in the early time) and it failed to register simple mouse clicks in a Steam game (the firs thing I tried). It's also sluggish and ugly and hard to get anything productive done.
So I went to KDE 4.11 next. And it's as ugly as ever. The huge sound indicator at the bottom is just so ugly. And then they have what looks like a Start menu thingy to launch applications. Oh boy, that felt odd. Still miles better than Gnome 3, but nothing I'd like to see on a daily basis.
XFCE is just too bare-bone for me. It's OK in looks, but the task bars are just clumsy.
So I'm probably sticking to Ubuntu for the next LTS cycle too and see what comes of the Unity 8 desktop. Sad to see there are no real contenders.
Also you check out tint2, which is a nice 3rd party panel also used in Crunchbang.
I don't think XFCE is perfect, but it ticks the important boxes for me. So much so that I just use it out of the box now rather than rolling my own from a vanilla OpenBox install (a fun exercise, btw).
Facts: Ubuntu desktop releases are available in a variety of 'flavours' including Lubuntu, Xubuntu and Gnome Ubuntu. The Kubuntu release has external sponsorship from Blue Systems. There is also UbuntuStudio that packages a lot of music/sound/graphics/video applications with a slightly remodelled XFCE4 UI. LTS status is limited to 3 years for the 'flavours' as opposed to 5 years for the Unity based Ubuntu, still one year overlap with the next LTS.
You can, as go8z says, install a range of desktop sessions on stock Ubuntu, but you do end up with a certain amount of duplication e.g. power manager, mousepad/Abiword and gedit/LibreOffice &c.
Plenty of choice so we can get our work done. It is all here...
If someone has a better link, please share!
I haven't been following Unity closely, but I thought this feature was present in OS GUIs since about 1997?
Yes, not exactly a revolutionary new feature, but newly enabled in unity by default.
It was, until all the fancy compositing WMs like Compiz came around. Those usually had it as an option, but not as the default because it lagged way too much.
As a friendly reminder, if you want to download the release as quickly as possible, use the torrent from http://www.ubuntu.com/download/alternative-downloads and be sure to seed for others.
Upgrades between LTS releases are not enabled by default until the first point release, 14.04.1, scheduled for July. It is recommended that most LTS users wait until then before upgrading to 14.04. You could add a '-d' flag if you're in a hurry!
"Hardware support - ARM multiplatform support has been added, enabling you to build a single ARM kernel image that can boot across multiple hardware platforms. Additionally, the ARM64 and Power architectures are now fully supported. "
Really? Can you do openstack with ARM/Power? what do you mean by "fully supported", does it mean ARM/Power/x86 all have the same set of packages? it has not been the case in the past.
If it is just a personal machine, have at it, I was using the Ubuntu Gnome 14.04 beta for some weeks with no major issues.
Others may wish to comment with specifics here.
The main reason I (as an end user with one laptop) have moved over to Gnome based UI is LibreOffice and the ALT keyboard mnemonics.
Ubuntu 14.04 (Trusty Tahr) Beta 2
Edit: I see the updated title now.
For some reason your other comment explaining this is [dead]. Can't see any reason why though.
Is it usually the same day or a few days later?
Fedora 20 on a 2009 13" MBP is an unfun experience. Using the UEFI boot means you get broken graphics drivers. Using the regular boot means you have to hold boot to get the image boot menu every time you power on. (I think - I could easily be wrong). You have to make sure the disk is blessed otherwise there's a large boot delay. (Fedora 20 doesn't use the right Broadcom drivers which means some interesti g catch22 about needing to connect to the internet to get WIFI drivers but not being able to because lol no drivers.)
I don't want to rant about Fedora when most of this is my lack of knowledge. But the combination of Gnome3 and this kind of fiddling around was odd and reminded me of a much older install experience. (Having said all that, Fedora 20 is nice and does have some really nice features.)
I don't know if this is still a case, but I was unable to use the proprietary nvidia drivers booting in pure UEFI mode (not BIOS compatible mode). I know that they've done a tone of UEFI work in grub/linux since then, so it's possible that this is no longer an issue.
Just speaking personally here. I've never been this impressed by a Linux release. If you have an HiDPI screen, then be prepared for a treat. It's absolutely stunning. It's fast, gorgeous, and near pixel perfect. Using the beta over the past few weeks has rekindled the joy and excitement of first discovering Linux as a kid (anyone remember those CDs in the back of magazines?)
The font rendering and window elements are now as sharp as OSX. The new version of GNOME provides integer scaling for all UI elements, not just text. That means no more huge fonts with tiny menu bars. Fonts look even better with anti-aliasing disabled using the gnome-tweak tool (IMHO). After years of tweaking ugly fonts & window managers, and being spoiled by a “retina” display, this is such a refreshing & welcome change to see in a mainstream distribution. After installing the restricted Nvidia driver, Unity is smooth and intuitive. It's clear they've put some effort into fixing the UI annoyances of prior versions.
This was my first time ever installing Linux on a Mac. I've always used a virtual machine. The first attempt using rEFInd was successful, but somewhat tedious. But then I found an easier way.
I installed rEFInd on OSX, booted into the Ubuntu Live Desktop, and then ran the installer with “ubiquity -b”. This worked. But Unity was a bit sluggish. This is because Ubuntu installs the open source version of the Nvidia driver by default (called “nouveau”). I learned the hard way that the restricted Nvidia drivers will not work with this boot method. If anyone else ends up with a frozen black screen, just do an F2 when rEFInd comes up, and add "text" to the boot command. Then you can remove the Nvidia drivers in console mode (although you'll need perfect vision for this, or a magnifying glass).
Now the easy way. The Ubuntu install tool provides several options on the first screen – one of which is to 'Install Ubuntu alongside OSX'.
I booted back into OSX, removed rEFInd, and deleted the Linux partitions - so now I just had the Mavericks partition, followed by free space. Download the Mac version of the ISO & create the installation USB courtesy of Google's assistance.
Now you can simply reboot OSX, hold down the Option key, and select the USB drive. Select the 'Install alongside Mac' option. It will automatically install to the free space. If you need Wifi during the installation, just open the terminal and run 'apt-get install bcm*'. This will load the Broadcom drivers & you'll be able to install any updates. Reboot to your desktop. Now use the Ubuntu software tool to install the Nvidia restricted drivers. Reboot once more, and savor the pixels and speed.
That's all there is to it. I'm going write this up in a blog post, along with some post-install tweaks (enabling the keys for brightness & the keyboard backlight, installing flux, vim/sublime, and remapping the keys in a Mac-friendly way). Just FYI, the various incarnations of Chrome do not yet support HiDPI on Linux. However, the Firefox Aurora version is fantastic (just set the scaling option in the about:config page).
The other big gripe I had was the touchpad. It was weirdly sensitive and didn't understand many gestures. The weirdly sensitive part is probably the biggest deal, as any incidental brush was picked up. I guess OSX ignores certain patterns to cut down on the accidental movements.
Your experience (a lovely distribution; frustrating to install on Mac (and I am carefully avoiding placing blame on any one organisation here)) is odd in 2014.
All that kind of fiddling around is similar to the hoops people jumped through with earlier distributions.
"The 2013 MacBook Pro can recognize multi-boot CD image (e.g., Ubuntu's official iso). So there is no need to use the "mac" iso image for installation. In fact, I recommend you avoid the "mac" iso image because it is a BIOS-boot only image and will force the Mac to enter BIOS emulation mode to install Ubuntu, which will need to be fixed to boot in its native EFI mode."
ubuntu-14.04-desktop-amd64.iso 17-Apr-2014 01:35 964M
Edit: As of five minutes ago, it's showing up!
And I (think?) this is the release where dash ads are default off.
The dash shouldn't be sending any user information to begin with.
I get that Canonical needs to get profitable fast, so personally I think they should take the RedHat road and release 'Ubuntu Enterprise' or something to that effect.
The 14.04 release has quite clearly shown that they have the expertise and industry collaboration to get the ball rolling on that.
Except for turning it off via the clearly marked option in the settings, or running a script that patches the feature out, or going into the source code and patching it out yourself, or waiting a few months until Canonical switches the default to "off."
But yeah, other than that, you have no recourse.
Nope, wrong way round. After the - er - strong reaction to the original appearance of the Amazon feature, later versions had a kill switch under Privacy. It was always possible simply to uninstall the appropriate package.
Layer you could only disable all. To disable only Amazon you had to remove a package or something.
If people could stop being so paranoid about nothing (the data is anonimised before sent for goodness' sake) then technology can advance much easier and quicker.
I get that companies feel the need to extract usable data to help fix problems (a sensible data dump is much more useful than a customer filling in a form with wierd information); or to sell anonymosed information.
But customers are right to be untrusting. Some companies have shown that they are not competant to keep data secure. Some companies have shown that they do not care about privacy.
You can either explicitly search locally by using Super-A, or turn off online search in the dash entirely via the privacy panel.
I feel like Canonical has a serious Not Invented Here problem, where they keep trying to re-invent the wheel by writing their own desktop environment, window manager, browser, startup system, etc.
Debian upstream does the same thing. Mozilla doesn't allow use of the Firefox trademark for non-Mozilla builds.