Feed aggregator

Aaron Honeycutt: Akademy Day 1

Planet Ubuntu - Sun, 07/26/2015 - 02:12

Before I start this blog I would like to thank the wonderful Ubuntu community for sponsoring my trip to the wonder hub of KDE development at Akademy!

Akademy 2015

My trip to Akademy 2015 in La Coruna Spain started at 4:45 pm on Friday in Miami with a flight to Lisbon. I was serve decent dinner and later breakfast. I did not get much sleep on the first part of the trip, but the second one from Lisbon to La Coruna I got about 1 hour or additional sleep with me finally arriving at 11:30 or so AM local time. I also saw the entertainment system reboot and show me that it was running Linux! I finally had the awesome experience of meeting some of the people I have been working with for over 2+ years over IRC, Hangouts and phone calls. Today was filled many great talks from our own Riddell and Clark on the new Plasma phone and continued work on the CI end of Kubuntu respectably.On the first day we also had the announcement of Plasma Mobile being worked on by Blue Systems and the larger KDE community as well. I’ll have some more pictures of that in there own blog post and album on imgur later on. Blue Systems has been kind enough to sponsor lunch for this weekend and next weekend. So here I type this blog post with under 2 hours of sleep for 36+ hours of uptime lol.

Randall Ross: Cool Conference Ideas

Planet Ubuntu - Sat, 07/25/2015 - 13:50

I just returned from a large, well managed conference in Portland (you know the one), and this was one of the ideas that stood out as excellent, at least in my opinion: Sticker Table!


People leave stickers, take stickers, and see stickers. It's a great way to give your project more visibility and it's also a great way to see what other projects are around, and possibly even at the show/conference.

Have you seen anything at recent shows that made you say, "Wow! Great idea." Please share in the comments or shoot an email to randall at ubuntu dot com.

Ronnie Tucker: GPS navigation for Ubuntu Phone

Planet Ubuntu - Sat, 07/25/2015 - 05:31
 uNAV is a turn-by-turn GPS navigation for the Ubuntu Touch OS. It is 100% GPL, and powered by OpenStreetMap and OSRM.

“I could show you a few screenshots, and I could tell you how it’s working. Or, I could show you me driving a random route [with it].”

Costales: Driving with my Ubuntu Phone [video]

Planet Ubuntu - Sat, 07/25/2015 - 03:22
uNAV is a turn-by-turn GPS navigation for Ubuntu Phone, 100% GPL powered by OpenStreetMap and OSRM.

I could show you a few screenshots and I could tell you how it is working...
Or I could show you to me driving a random route :)) Click for watch it and use fullscreen for the details:

Driving with Ubuntu Phone
Install uNAV into your phone from the Ubuntu Store (You have to update to OTA5!). 

I want to thank you:
David Planella, who helped me a lot with the development of this application |o/
Sergi Quiles Pérez, who helped me a lot with ideas, feedback and testing in this last version.
Carla Sella, Ilonka O., Morgane & Jonathan Wiedemann, Nathan Haines and Paco Molinero for the voices.
José Fernández Calero for this video.
And to all of you that you helped me in one way or another in these months :) Thanks!

Kubuntu Wire: Plasma Mobile Launched

Planet Ubuntu - Sat, 07/25/2015 - 02:57

If you are interested in a free OS for your phone, please visit our Home Page.

Watch the Video Demonstration.

Links to applications source.

Kubuntu: Kubuntu Team Launches Plasma Mobile References Images

Planet Ubuntu - Sat, 07/25/2015 - 02:47

The Kubuntu team is proud to announce the references images for Plasma Mobile.

Plasma Mobile was announced today at KDE's Akademy conference.

Our images can be installed on a Nexus 5 phone.

More information on Plasma Mobile's website.

Sebastian Kügler: Embracing Mobile

Planet Ubuntu - Sat, 07/25/2015 - 02:18

At Blue Systems, we have been working on making Plasma shine for a while now. We’ve contributed much to the KDE Frameworks 5 and Plasma 5 projects, and helping with the transition to Qt5. Much of this work has been involving porting, stabilizing and improving existing code. With the new architecture in place, we’ve also worked on new topics, such as Plasma on non-desktop (and non-laptop) devices.

Plasma Mobile on an LG Nexus 5

This work is coming to fruition now, and we feel that it has reached a point where we want to present it to a more general public. Today we unveil the Plasma Mobile project. Its aim is to offer a Free (as in Freedom), user-friendly, privacy-enabling and customizable platform for mobile devices. Plasma Mobile runs on top of Linux, uses Wayland for rendering graphics and offers a device-specific user interface using the KDE Frameworks and Plasma library and tooling. Plasma Mobile is under development, and not usable by end users now. Missing functionality and stability problems are normal in this phase of development and will be ironed out. Plasma Mobile provides basic functionality and an opportunity for developers to jump in now and shape the mobile platform, and how we use our mobile devices.

As is necessary with development on mobile devices, we’ve not stopped at providing source code that “can be made to work”, rather we’re doing a reference implementation of Plasma Mobile that can be used by those who would like to build a product based on Plasma Mobile on their platform. The reference implementation is based on Kubuntu, which we chose because there is a lot of expertise in our team with Kubuntu, and at Blue Systems we already have continuous builds and package creation in place. Much of the last year was spent getting the hardware to work, and getting our code to boot on a phone. With pride, we’re now announcing the general availability of this project for public contribution. In order to make clear that this is not an in-house project, we have moved the project assets to KDE infrastructure and put under Free software licenses (GPL and LGPL according to KDE’s licensing policies). Plasma Mobile’s reference implementation runs on an LG Nexus 5 smartphone, using an Android kernel, Ubuntu user space and provides an integrated Plasma user interface on top of all that. We also have an x86 version, running on an ExoPC, which can be useful for testing.

Plasma Mobile uses the Wayland display protocol to render the user interface. KWin, Plasma’s window manager and compositor plays a central role. For apps that do not support Wayland, we provide X11 support through the XWayland compatibility layer.

Plasma Mobile is a truly converged user interface. More than 90% of its code is shared with the traditional desktop user interface. The mobile workspace is implemented in the form of a shell or workspace suitable for mobile phones. The shell provides an app launcher, a quick settings panel and a task switcher. Other functionality, such as a dialer, settings, etc. is implemented using specialized components that can be mixed and matched to create a specific user experience or to provide additional functionality — some of them already known from Plasma Desktop.

Architecture diagram of Plasma Mobile

Plasma Mobile is developed in a public and open development process. Contributions are welcome and encouraged throughout the process. We do not want to create another walled garden, but an inclusive platform for creation of mobile device user experiences. We do not want to create releases behind closed doors and throw them over the wall once in a while, but create a leveled playing field for contributors to work together and share their work. Plasma Mobile’s code is available on git.kde.org, and its development is discussed on the plasma-devel mailinglist. In the course of Akademy, we have a number of sessions planned to flesh out more and more detailed plans for further development.

With the basic workspace and OS integration work done, we have laid a good base for further development, and for others to get their code to run on Plasma Mobile. More work which is already in our pipeline includes support for running Android applications, which potentially brings a great number of mature apps to Plasma Mobile, better integration with other Plasma Devices, such as your desktop or laptop through KDE Connect, an improved SDK making it very easy to get a full-fledged development environment set up in minutes, and of course more applications.

Serge Hallyn: Ambient capabilities

Planet Ubuntu - Fri, 07/24/2015 - 20:16

There are several problems with posix capabilities. The first is the name: capabilities are something entirely different, so now we have to distinguish between “classical” and “posix” capabilities. Next, capabilities come from a defunct posix draft. That’s a serious downside for some people.

But another complaint has come up several times since file capabilities were implemented in Linux: people wanted an easy way for a program, once it has capabilities, to keep them. Capabilities are re-calculated every time the task executes a new file, taking the executable file’s capabilities into account. If a file has no capabilities, then (outside of the special exception for root when SECBIT_NOROOT is off) the resulting privilege set will be empty. And for shellscripts, file capabilities are always empty.

Fundamental to posix capabilities is the concept that part of your authority stems from who you are, and part stems from the programs you run. In a world of trojan horses and signed binaries this may seem sensible, but in the real world it is not always desirable. In particular, consider a case where a program wants to run as non-root user, but with a few capabilities – perhaps only cap_net_admin. If there is a very small set of files which the program may want to execute with privilege, and none are scripts, then cap_net_admin could be added to the inheritable file privileges for each of those programs. Then only processes with cap_net_admin in their inheritable process capabilities will be able to run those programs with privilege. But what if the program wants to run *anything*, including scripts and without having to predict what will be executed? This currently is not possible.

Christopher Lameter has been facing this problem for some time, and requested an enhancement of posix capabilities to allow him to solve it. Not only did he raise the problem and provide a good, real use case, he also sent several patches for discussion. In the end, a concept of “ambient capabilities” was agreed to and implemented (final patch by Andy Lutomirski). It’s currently available in -mm.

Here is how it works:

(Note – for more background on posix capabilities as implemented in linux, please see this Linux Symposium paper. For an example of how to use file capabilities to run as non-root before ambient capabilities, see this Linux Journal article. The ambient capability set has gotten several LWN mentions as well.)

Tasks have a new capability set, pA, the ambient set. As Andy Lutomirski put it, “pA does what most people expect pI to do.” Bits can only be set in pA if they are in pP or pI, and they are dropped from pA if they are dropped from pP or pI. When a new file is executed, all bits in pA are enabled in pP. Note though that executing any file which has file capabilities, or using the SECBIT_KEEPCAPS prctl option (followed by setresuid), will clear pA after the next exec.

So once a program moves CAP_NET_ADMIN into its pA, it can proceed to fork+exec a shellscript doing some /sbin/ip processing without losing CAP_NET_ADMIN.

How to use it (example):

Below is a test program, originally by Christopher, which I slightly modified. Write it to a file ‘ambient.c’. Build it, using

$ gcc -o ambient ambient.c -lcap-ng

Then assign it a set of file capabilities, for instance:

$ sudo setcap cap_net_raw,cap_net_admin,cap_sys_nice,cap_setpcap+p ambient

I was lazy and didn’t add interpretation of capabilities to ambient.c, so you’ll need to check /usr/include/linux/capability.h for the integers representing each capability. Run a shell with ambient capabilities by running, for instance:

$ ./ambient.c -c 13,12,23,8 /bin/bash

In this shell, check your capabilities:

$ grep Cap /proc/self/status
CapInh: 0000000000803100
CapPrm: 0000000000803100
CapEff: 0000000000803100
CapBnd: 0000003fffffffff
CapAmb: 0000000000803100

You can see that you have the requested ambient capabilities. If you run a new shell there, it retains those capabilities:

$ bash -c “grep Cap /proc/self/status”
CapInh: 0000000000803100
CapPrm: 0000000000803100
CapEff: 0000000000803100
CapBnd: 0000003fffffffff
CapAmb: 0000000000803100

What if we drop all but cap_net_admin from our inheritable set? We can test that using the ‘capsh’ program shipped with libcap:

$ capsh –caps=cap_net_admin=pi — -c “grep Cap /proc/self/status”
CapInh: 0000000000001000
CapPrm: 0000000000001000
CapEff: 0000000000001000
CapBnd: 0000003fffffffff
CapAmb: 0000000000001000

As you can see, the other capabilities were dropped from our ambient, and hence from our effective set.

================================================================================
ambient.c source
================================================================================
/*
* Test program for the ambient capabilities. This program spawns a shell
* that allows running processes with a defined set of capabilities.
*
* (C) 2015 Christoph Lameter
* (C) 2015 Serge Hallyn
* Released under: GPL v3 or later.
*
*
* Compile using:
*
* gcc -o ambient_test ambient_test.o -lcap-ng
*
* This program must have the following capabilities to run properly:
* Permissions for CAP_NET_RAW, CAP_NET_ADMIN, CAP_SYS_NICE
*
* A command to equip the binary with the right caps is:
*
* setcap cap_net_raw,cap_net_admin,cap_sys_nice+p ambient_test
*
*
* To get a shell with additional caps that can be inherited by other processes:
*
* ./ambient_test /bin/bash
*
*
* Verifying that it works:
*
* From the bash spawed by ambient_test run
*
* cat /proc/$$/status
*
* and have a look at the capabilities.
*/

#include
#include
#include
#include
#include
#include
#include

/*
* Definitions from the kernel header files. These are going to be removed
* when the /usr/include files have these defined.
*/
#define PR_CAP_AMBIENT 47
#define PR_CAP_AMBIENT_IS_SET 1
#define PR_CAP_AMBIENT_RAISE 2
#define PR_CAP_AMBIENT_LOWER 3
#define PR_CAP_AMBIENT_CLEAR_ALL 4

static void set_ambient_cap(int cap)
{
int rc;

capng_get_caps_process();
rc = capng_update(CAPNG_ADD, CAPNG_INHERITABLE, cap);
if (rc) {
printf(“Cannot add inheritable cap\n”);
exit(2);
}
capng_apply(CAPNG_SELECT_CAPS);

/* Note the two 0s at the end. Kernel checks for these */
if (prctl(PR_CAP_AMBIENT, PR_CAP_AMBIENT_RAISE, cap, 0, 0)) {
perror(“Cannot set cap”);
exit(1);
}
}

void usage(const char *me) {
printf(“Usage: %s [-c caps] new-program new-args\n”, me);
exit(1);
}

int default_caplist[] = {CAP_NET_RAW, CAP_NET_ADMIN, CAP_SYS_NICE, -1};

int *get_caplist(const char *arg) {
int i = 1;
int *list = NULL;
char *dup = strdup(arg), *tok;

for (tok = strtok(dup, “,”); tok; tok = strtok(NULL, “,”)) {
list = realloc(list, (i + 1) * sizeof(int));
if (!list) {
perror(“out of memory”);
exit(1);
}
list[i-1] = atoi(tok);
list[i] = -1;
i++;
}
return list;
}

int main(int argc, char **argv)
{
int rc, i, gotcaps = 0;
int *caplist = NULL;
int index = 1; // argv index for cmd to start

if (argc < 2)
usage(argv[0]);

if (strcmp(argv[1], "-c") == 0) {
if (argc <= 3) {
usage(argv[0]);
}
caplist = get_caplist(argv[2]);
index = 3;
}

if (!caplist) {
caplist = (int *)default_caplist;
}

for (i = 0; caplist[i] != -1; i++) {
printf("adding %d to ambient list\n", caplist[i]);
set_ambient_cap(caplist[i]);
}

printf("Ambient_test forking shell\n");
if (execv(argv[index], argv + index))
perror("Cannot exec");

return 0;
}
================================================================================


Jos&eacute; Antonio Rey: How UbuConLA 2015 evolved in the past months

Planet Ubuntu - Fri, 07/24/2015 - 20:09

Wow, what can I say. To be honest, I am really impressed on how UbuConLA is shaping. So far there’s been a lot of stuff going through my head since I just finished finals, but now that I have a clear view of the entire panorama I really like how this conference is turning out to be.

In the past I’ve staffed booths and given talks in conferences, as well as organized small-ish events. However, this is my first big conference, and you can’t just imagine the excitement smile I have on my face when I see things are running as expected. It’s been some rough past months trying to balance conference planning with booth planning at TXLF, as well as studies and some other communities I contribute to. However, it’s been such an amazing experience.

Several months ago I was in the middle of a dillema, since the venue we were thinking of changed some requirements. Fortunately, my university, University of Lima, has been extremely helpful. I cannot thank enough all the people I have met on the way and who have given me such a big help whenever things were starting to turn in the wrong direction, and all we have accomplished so far.

In the past couple days I have received the name badges and banners we will be using for the conference, and even though there’s still some stuff in the way I can’t be more excited about how things are starting to look. Last week everything was just in ideas, and we’re starting to see the digital come into a physical object. That, for me, is one of the most exciting parts.

Luckily (and at the same time unfortunately) we had to close the registration form yesterday. The auditorium that was given to us has a capacity of 233 people, and counting volunteers, speakers, staff and more reduces that a bit. How many people have registered so far, you ask? Three. Hundred. That means we’re gonna fill that auditorium! A full room, what more can we ask for. If you haven’t registered for the conference, do not fear. The registration is just a fast track and it’s first-come, first-served. So make sure to keep an eye on all the social media pages for information on how to attend.

The next couple weeks are going to be the most difficult ones. We have a public holiday coming up until Thursday here in Peru, and from then on we need to start the final preparations. This is looking so good, I hope you all are surprised when you come to the conference.

After going through some of the process of organizing a medium-sized conference I can now really appreciate all the effort it takes to organize a big, and even a medium-sized conference. If you go to a conference and see the chairs or organizers, make sure to give them a pat on the back and thank them for all the efforts. They’re the people we need to thank for keeping the human touch and interaction alive!

And I think that’s all. Hope to see you in August, can’t wait for UbuConLA to happen!


Ronnie Tucker: Linux Mint 17.2 offers desktop familiarity and responds to user wants

Planet Ubuntu - Fri, 07/24/2015 - 19:12

These days, the desktop OSes grabbing headlines have, for the most part, left the traditional desktop behind in favor of what’s often referred to as a “shell.” Typically, such an arrangement offers a search-based interface. In the Linux world, the GNOME project and Ubuntu’s Unity desktop interfaces both take this approach.

This is not a sea change that’s limited to Linux, however. For example, the upheaval of the desktop is also happening in Windows land. Windows 8 departed from the traditional desktop UI, and Windows 10 looks like it will continue that rethinking of the desktop, albeit with a few familiar elements retained. Whether it’s driven by, in Ubuntu’s case, a vision of “convergence” between desktop and mobile or perhaps just the need for something new (which seems to be the case for GNOME 3.x), developers would have you believe that these mobile-friendly, search-based desktops are the future of, well, everything.

 

Source: http://arstechnica.com/gadgets/2015/07/rare-breed-linux-mint-17-2-offers-desktop-familiarity-and-responds-to-user-wants/

Submitted by: Scott Gilbertson

Elizabeth K. Joseph: OSCON 2015

Planet Ubuntu - Fri, 07/24/2015 - 17:27

Following the Community Leadership Summit (CLS), which I wrote about wrote about here, I spent a couple of days at OSCON.

Monday kicked off by attending Jono Bacon’s Community leadership workshop. I attended one of these a couple years ago, so it was really interesting to see how his advice has evolved with the change in tooling and progress that communities in tech and beyond has changed. I took a lot of notes, but everything I wanted to say here has been summarized by others in a series of great posts on opensource.com:

…hopefully no one else went to Powell’s to pick up the recommended books, I cleared them out of a couple of them.

That afternoon Jono joined David Planella of the Community Team at Canonical and Michael Hall, Laura Czajkowski and I of the Ubuntu Community Council to look through our CLS notes and come up with some talking points to discuss with the rest of the Ubuntu community regarding everything from in person events (stronger centralized support of regional Ubucons needed?) to learning what inspires people about the active Ubuntu phone community and how we can make them feel more included in the broader community (and helping them become leaders!). There was also some interesting discussion around the Open Source projects managed by Canonical and expectations for community members with regard to where they can get involved. There are some projects where part time, community contributors are wanted and welcome, and others where it’s simply not realistic due to a variety of factors, from the desire for in-person collaboration (a lot of design and UI stuff) to the new projects with an exceptionally fast pace of development that makes it harder for part time contributors (right now I’m thinking anything related to Snappy). There are improvements that Canonical can make so that even these projects are more welcoming, but adjusting expectations about where contributions are most needed and wanted would be valuable to me. I’m looking forward to discussing these topics and more with the broader Ubuntu community.


Laura, David, Michael, Lyz

Monday night we invited members of the Oregon LoCo out and had an Out of Towners Dinner at Altabira City Tavern, the restaurant on top of the Hotel Eastlund where several of us were staying. Unfortunately the local Kubuntu folks had already cleared out of town for Akademy in Spain, but we were able to meet up with long-time Ubuntu member Dan Trevino, who used to be part of the Florida LoCo with Michael, and who I last saw at Google I/O last year. I enjoyed great food and company.

I wasn’t speaking at OSCON this year, so I attended with an Expo pass and after an amazing breakfast at Mother’s Bistro in downtown Portland with Laura, David and Michael (…and another quick stop at Powell’s), I spent Tuesday afternoon hanging out with various friends who were also attending OSCON. When 5PM rolled around the actual expo hall itself opened, and surprised me with how massive and expensive some of the company booths had become. My last OSCON was in 2013 and I don’t remember the expo hall being quite so extravagant. We’ve sure come a long way.

Still, my favorite part of the expo hall is always the non-profit/open source project/organization area where the more grass-roots tables are. I was able to chat with several people who are really passionate about what they do. As a former Linux Users Group organizer and someone who still does a lot of open source work for free as a hobby, these are my people.

Wednesday was my last morning at OSCON. I did another walk around the expo hall and chatted with several people. I also went by the HP booth and got a picture of myself… with myself. I remain very happy that HP continues to support my career in a way that allows me to work on really interesting open source infrastructure stuff and to travel the world to tell people about it.

My flight took me home Wednesday afternoon and with that my OSCON adventure for 2015 came to a close!

More OSCON and general Portland photos here: https://www.flickr.com/photos/pleia2/sets/72157656192137302

Canonical Design Team: Converting old guidelines to vanilla

Planet Ubuntu - Fri, 07/24/2015 - 04:02
How the previous guidelines worked

Guidelines essentially is a framework built by the Canonical web design team. The whole framework has an array of tools to make it easy to create a Ubuntu themed sites. The guidelines were a collaboration between developers and designers and followed consistent look which meant in-house teams and community websites could have a consistent brand feel.

It worked in one way, a large framework of modules, helpers and components which built the Ubuntu style for all our sites. The structure of this required a lot of overrides and work arounds for different projects and added to a bloated nature that the guidelines had become. Canonical & Cloud sites required a large set of overrides to imprint their own visual requirements and created a lot of duplication and overhead for each site.

There was no build system nor a way to update to the latest version unless using the hosted pre-compiled guidelines or pulled from our bazaar repository. Not having any form of build step meant having to rely on a local Sass compiler or setup a watcher for each project. Also we had no viable way to check linting errors or create a concrete coding standard.

The actual framework its self was a ported CSS framework into Sass. Not utilising placeholders or mixins correctly and with a bloated amount of variables. To change one colour for example or changing the size of an element wouldn’t be as easy as passing a mixin with set values or changing one variable.

Unlike how we have currently built in Vanilla, all preprocessor styles are created via mixins. Creating responsive changes would be done in a large media query at the end of any document and this again would be repeated for our Canonical or Cloud styles too.

Removing Ubuntu and Canonical from theme

Our first task in building Vanilla was referencing all elements which were ‘Ubuntu’ centric. Anything which had a unique class, colour or style. Once identified the team systematically took one section of each part of guidelines and removed the classes or variables and creating new versions. Once this stage was achieved the team was able to then look at refactoring and updating the code.

Clean-up and making it generic

We decided when starting this project to update how we write any new module / element. Linting was a big factor and when using a build system like gulp we finally had the ability to adhere to a coding standard. This meant a lot of modules / elements had to be rewritten and also improved upon, trimming down the Sass nesting, applying new techniques such as flex box and cleaning duplicated styles.

But the main goal was to make it generic, extendable and easy. Not the simplest of tasks, this meant removing any custom modules or specific style / classes but also building the framework to change via a variable update or a value change with in a mixin. We wanted the Vanilla theme to inherit another developers style and that would cascade through out the whole framework with ease. Setting the brand colour for example would effect the whole framework and change a multiple of modules / elements. But you are not restricted which we had as a bottle neck with the old guidelines.

Using Sass mixins

Mixins are a powerful part of Sass which we weren’t utilising. In guidelines they were used to create preprocessor polyfills, something which was annoying. Gulp now replaces that need. We used mixins to modularise the entire framework, thus giving flexibility over which parts of the framework a project requires.

The ability to easily turn on/off a section of vanilla felt very powerful but required. We wanted a developer to choose what was needed for their project. This was the opposite of guidelines where you would receive the entire framework. In Vanilla, each section our elements or modules would also be encapsulated with in mixins and on some have values which would effect them. For example the buttons mixin;

@mixin vf-button($button-color, $button-bg, $border-color) { @extend %button-pattern; color: $button-color; background: $button-bg; @if $border-color != null { border: 1px solid $border-color; } &:hover { background: darken($button-bg, 6.2%); @if $button-bg == $transparent { text-decoration: underline; } } }



The above code shows how this mixin isn’t attached to fixed styles or colours. When building a new Vanilla theme a few variable changes will style any button to the projects requirements. This is something we have replicated through out the project and creates a far better modular framework.

Creating new themes

As I have mentioned earlier a few changes can setup a whole new theme in Vanilla, using it as a base and then adding or extending new styles. Change the branding or a font family just requires overwriting the default value e.g $brand-colour: $orange !default; is set in the global variables document. Amending this in another document and setting it to $brand-colour: #990000; will change any element effected by brand colour thus creating the beginning of a new theme.

We can also take this per module mixin. Including the module into a new class or element and then extend or add upon it. This means themes are not constricted to just using what is there but gives more freedom. This method is particularly useful for the web team as we build themes for Ubuntu, Canonical and Cloud products.

An example of a live theme we have created is the Ubuntu vanilla theme. This is an extension of the Vanilla framework and is set up to override any required variables to give it the Ubuntu brand. Diving into the theme.scss It shows all elements used from Vanilla but also Ubuntu specific modules. These are exclusively used just for the Ubuntu brand but are also structured in the same manner as the Vanilla framework. This reduces complexity in maintaining these themes and developers can easily pick up what has been built or use it as a reference to building their own theme versions.

Jonathan Riddell: Mi Charla

Planet Ubuntu - Fri, 07/24/2015 - 03:49

Los transparencias de mi presentación de ayer a Akademy-ES es ahora en mi página web de charlas.

by

The Fridge: Ubuntu 14.10 (Utopic Unicorn) End of Life reached on July 23, 2015

Planet Ubuntu - Thu, 07/23/2015 - 16:11

This is a follow-up to the End of Life warning sent earlier this month to confirm that as of today (July 23, 2015), Ubuntu 14.10 is no longer supported. No more package updates will be accepted to 14.10, and it will be archived to old-releases.ubuntu.com in the coming weeks.

The original End of Life warning follows, with upgrade instructions:

Ubuntu announced its 14.10 (Utopic Unicorn) release almost 9 months ago, on October 23, 2014. As a non-LTS release, 14.10 has a 9-month month support cycle and, as such, the support period is now nearing its end and Ubuntu 14.10 will reach end of life on Thursday, July 23rd. At that time, Ubuntu Security Notices will no longer include information or updated packages for Ubuntu 14.10.

The supported upgrade path from Ubuntu 14.10 is via Ubuntu 15.04. Instructions and caveats for the upgrade may be found at:

https://help.ubuntu.com/community/VividUpgrades

Ubuntu 15.04 continues to be actively supported with security updates and select high-impact bug fixes. Announcements of security updates for Ubuntu releases are sent to the ubuntu-security-announce mailing list, information about which may be found at:

https://lists.ubuntu.com/mailman/listinfo/ubuntu-security-announce

Since its launch in October 2004 Ubuntu has become one of the most highly regarded Linux distributions with millions of users in homes, schools, businesses and governments around the world. Ubuntu is Open Source software, costs nothing to download, and users are free to customise or alter their software in order to meet their needs.

Originally posted to the ubuntu-announce mailing list on Thu Jul 23 21:49:45 UTC 2015 by Adam Conrad

Ubuntu 14.10 (Utopic Unicorn) End of Life reached on July 23, 2015

The Fridge - Thu, 07/23/2015 - 16:11

This is a follow-up to the End of Life warning sent earlier this month to confirm that as of today (July 23, 2015), Ubuntu 14.10 is no longer supported. No more package updates will be accepted to 14.10, and it will be archived to old-releases.ubuntu.com in the coming weeks.

The original End of Life warning follows, with upgrade instructions:

Ubuntu announced its 14.10 (Utopic Unicorn) release almost 9 months ago, on October 23, 2014. As a non-LTS release, 14.10 has a 9-month month support cycle and, as such, the support period is now nearing its end and Ubuntu 14.10 will reach end of life on Thursday, July 23rd. At that time, Ubuntu Security Notices will no longer include information or updated packages for Ubuntu 14.10.

The supported upgrade path from Ubuntu 14.10 is via Ubuntu 15.04. Instructions and caveats for the upgrade may be found at:

https://help.ubuntu.com/community/VividUpgrades

Ubuntu 15.04 continues to be actively supported with security updates and select high-impact bug fixes. Announcements of security updates for Ubuntu releases are sent to the ubuntu-security-announce mailing list, information about which may be found at:

https://lists.ubuntu.com/mailman/listinfo/ubuntu-security-announce

Since its launch in October 2004 Ubuntu has become one of the most highly regarded Linux distributions with millions of users in homes, schools, businesses and governments around the world. Ubuntu is Open Source software, costs nothing to download, and users are free to customise or alter their software in order to meet their needs.

Originally posted to the ubuntu-announce mailing list on Thu Jul 23 21:49:45 UTC 2015 by Adam Conrad

Ubuntu Podcast from the UK LoCo: S08E20 – Who’s Your Caddy? - Ubuntu Podcast

Planet Ubuntu - Thu, 07/23/2015 - 15:22

It’s Episode Twenty of Season Eight of the Ubuntu Podcast! Mark Johnson, Laura Cowen, and Martin Wimpress are together with guest presenter Joe Ressington and speaking to your brain.

In this week’s show:

That’s all for this week, please send your comments and suggestions to: show@ubuntupodcast.org
Join us on IRC in #ubuntu-podcast on Freenode
Follow us on Twitter
Find our Facebook Fan Page
Follow us on Google+

Carla Sella: Let's test Ubuntu Phone's Wi-Fi Hotspots (internet tethering) feature

Planet Ubuntu - Thu, 07/23/2015 - 12:48
In system settings under "cellular"
 the new "Wi-Fi" hotspot feature
Enabling Hotspot feature





Hot spot feature settings


We have a brand new Wi-Fi Hotspots (internet tethering) feature that's about to land in Ubuntu Phone with OTA-6.I know a lot of persons that have been waiting for this feature eagerly.So let's see how easy it is to help out testing it :-).You can test this feature on  both Ubuntu 15.04 (Vivid Vervet) and Ubuntu 15.10 (Wily Werewolf) based phone images
First you need to enable "Developer mode" on your Ubuntu Phone, to do this you go to system settings, "About this phone", swipe down right to the bottom and tap on "Developer mode", on the Developer mode page turn on "Developer mode" switch:


Now let's connect the phone to your Ubuntu desktop PC with a USB cable and in terminal write:
citrain device-upgrade <silo #> <pin/password on device>
so for testing this feature the command will be:
$ citrain device-upgrade  46 0000
where 0000 is your device's pin or password and 46 is the silo number.
If you don't have the phablet-tools-citrain package installed you need to:
$ sudo apt install phablet-tools-citrain 

Now to start the hotspot: 
  1. Ensure Wi-Fi is enabled.
  2. Go to System Settings -> Mobile/Cellular​
  3. Tap “Wi-Fi hotspot”
  4. Set up your hotspot
  5. Enable it.
If you hit an issue, here's how to report it:

- ​A client can't see the hotspot or the hotspot does not work:​
  * File against: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+filebug
​​  ​* Please attach /var/log/syslog as well as ~/.cache/upstart/indicator-network.log​

- There's a problem with the System Settings UI:
  * File against: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+filebug
  * ​Please attach log files which you'll find here: ~/.cache/upstart/application-legacy-ubuntu-system-settings-.log​


Enjoy testing :-D.

Valorie Zimmerman: I'm loving Akademy!

Planet Ubuntu - Thu, 07/23/2015 - 10:20
And it hasn't even started. Scarlett and I flew to A Coruña arriving Tuesday, and spent yesterday seeing the town. Today is all about preparing for the e.V. AGM and the Akademy talks and BoFs following. 


Wish you were here!

Riccardo Padovani: Meizu MX4 is awesome after OTA-5

Planet Ubuntu - Thu, 07/23/2015 - 08:00

One month ago I wrote my first review about Meizu MX4 and I was disappointed about the lack of optimization that the phone received and some of the problems as well.

Now with the OTA-5 the phone is working as it should have from the very beginning. It’s a real shame that Meizu started selling them before this update, because a lot of reviews currently online are bad due to problems fixed in this update. It’s like a whole new phone!

Meizu MX4 specific improvements Battery

One of the things that I most appreciated in the BQ Aquaris E4.5 was the battery life which the MX4 was not on par with, until two day ago that is.

After the update I did a full recharge and I didn’t have to charge again for 36 hours. Maybe for some of you that is not a lot but for me it’s much longer than I was used to from Android. I always had 4G turned, watched at least 30 mins of videos on YouTube, received and replied to more than 500 messages, received and replied to emails, surfed the web, a couple of calls and more.

Battery life could be a killer feature of Ubuntu, and there is still a lot to improve.

Optimization

With this update the phone doesn’t lag and doesn’t get too hot. There’s also an increase of icons per row (following a change with the grid units) which is much better!

Oh yea and the the LED for notifications work! Yes!

General improvements

The speed improvement is terrific. With every update a lot of things change and you can spend hours finding all of them. If you’re passionate about technology you definitely have to buy an Ubuntu Phone (the MX4 or the Aquaris depending on your price range).

Some of the most interesting I found are: - Unity Rotation: finally it isn’t weird to use the phone in landscape mode. Though there are still some bugs and the dash doesn’t rotate which I hope they fix soon! - New icons: which look great, awesome job Design Team! they also look much clear and have better in the MX4’s resolution. Kudos! - Change reviews: time to update some old feedback I left when the apps where still in development. - New Tab in Browser: has been improved with some of the contributions I worked on in the last few months. I love the Browser and I love all the updates it is getting as well as in the Desktop

Now I’ve very happy with the phone and I still miss nothing from Android. Yes of it isn’t for everyone (yet) but the number of improvements it has every month is astonishing and I think it will become available to the masses very soon.

But it is still missing from apps which can be filled in when some big companies come and join on this trip!

Thanks to Aaron Honeycutt for helping me writing this article.

If you like my work and want to support me, just send me a Thank you! by email or offer me a beer:-)

Ciao,
R.

Ubuntu App Developer Blog: Announcing UbuContest 2015

Planet Ubuntu - Thu, 07/23/2015 - 06:04

Have you read the news already? Canonical, the Ubucon Germany 2015 team, and the UbuContest 2015 team, are happy to announce the first UbuContest! Contestants from all over the world have until September 18, 2015 to build and publish their apps and scopes using the Ubuntu SDK and Ubuntu platform. The competion has already started, so register your competition entry today! You don’t have to create a new project, submit what you have and improve it over the next two months.

But we know it's not all about shiny new apps and scopes! A great platform also needs content, great design, testing, documentation, bug management, developer support, interesting blog posts, technology demonstrations and all of the other incredible things our community does every day. So we give you, our community members, the opportunity to nominate other community members for prizes!

We are proud to present five dedicated categories:

  1. Best Team Entry: A team of up to three developers may register up to two apps/scopes they are developing. The jury will assign points in categories including "Creativity", "Functionality", "Design", "Technical Level" and "Convergence". The top three entries with the most points win.

  2. Best Individual Entry: A lone developer may register up to two apps/scopes he or she is developing. The rest of the rules are identical to the "Best Team Entry" category.

  1. Outstanding Technical Contribution: Members of the general public may nominate candidates who, in their opinion, have done something "exceptional" on a technical level. The nominated candidate with the most jury votes wins.

  1. Outstanding Non-Technical Contribution: Members of the general public may nominate candidates who, in their opinion, have done something exceptional, but non-technical, to bring the Ubuntu platform forward. So, for example, you can nominate a friend who has reported and commented on all those phone-related bugs on Launchpad. Or nominate a member of your local community who did translations for Core Apps. Or nominate someone who has contributed documentation, written awesome blog articles, etc. The nominated candidate with the most jury votes wins.

  1. Convergence Hero: The "Best Team Entry" or "Best Individual Entry" contribution with the highest number of "Convergence" points wins. The winner in this category will probably surprise us in ways we have yet to imagine.

Our community judging panel members Laura Cowen, Carla Sella, Simos Xenitellis, Sujeevan Vijayakumaran and Michael Zanetti will select the winners in each category. Successful winners will be awarded items from a huge pile of prizes, including travel subsidies for the first-placed winners to attend Ubucon Germany 2015 in Berlin, four Ubuntu Phones sponsored by bq and Meizu, t-shirts, and bundles of items from the official Ubuntu Shop.

We wish all the contestants good luck!

Go to ubucontest.eu or ubucon.de/2015/contest for more information, including how to register and nominate folks. You can also follow us on Twitter @ubucontest, or contact us via e-mail at contest@ubucon.de.

 

Pages

Subscribe to Ubuntu Arizona LoCo Team aggregator