What's the deal with this "Ubuntu Browser" being set as the default? 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.
Rebranding stuff isn't Not Invented Here syndrome. Relax. They didn't re-invent anything. It's just Firefox with a few patches for integrating with their desktop environment. Plus, they gave up on their startup system. They'll be switching to systemd in future releases.
Ubuntu 14.04 released
111–120 of 132 posts
Re: Ubuntu 14.04 released
#112Re: Ubuntu 14.04 released
#113Can anyone comment on the difference between the PC and the Mac 64 bit images?
"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."
source: https://help.ubuntu.com/community/MacBookPro11-1/Saucy
Re: Ubuntu 14.04 released
#114Re: Ubuntu 14.04 released
#115Re: Ubuntu 14.04 released
#116If you use Emacs and depend on Ctrl-space note that you may have to disable the keybinding in ibus-setup and restart the ibus daemon. This bug was claimed to be fixed but it wasn't for me. However I'm running Xmonad with some Gnome utilities.
Re: Ubuntu 14.04 released
#117Earlier quoted context omitted.
Can anyone talk about how well a Macbook Pro copes with the UEFI version of Ubuntu? 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. (Fedo…
> Can anyone talk about how well a Macbook Pro copes with the UEFI version of Ubuntu? 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).
Re: Ubuntu 14.04 released
#118Just a reminder that we are now publishing Vagrant boxes as well: - https://vagrantcloud.com/ubuntu
Any chance you'll be publishing VMware boxes as well?
Re: Ubuntu 14.04 released
#119Earlier quoted context omitted.
Customer: "It doesn't work!" Project manager: "But hey, we shipped on time!"
I'm sure that the vendor will gladly return the money paid for it.
Absolutely.
Re: Ubuntu 14.04 released
#120Earlier quoted context omitted.
They send to Amazon what you type. And default was always on. And in latest versions option to disable was removed, you had to remove one package because "Ubuntu is about simplicity"
"And in latest versions option to disable was removed" 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.