Skip to main content

Your submission was sent successfully! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates from Canonical and upcoming events where you can meet our team.Close

Thank you for contacting us. A member of our team will be in touch shortly. Close

An error occurred while submitting your form. Please try again or file a bug report. Close

  1. Blog
  2. Article

Canonical
on 1 September 2010


So, the default wallpaper…

My initial vision:

Seeing so many screenshots of the Ubuntu desktop during the second to last release all sporting identical backdrops, made me wonder: wouldn’t it be amazing if all our users received (or evolved) subtly different wallpapers – not radically enough to dilute the intent but just enough to become an elegant addition to the OS and give a sense of personalisation.

Ideally they might not even notice at first but would become aware and pleasantly surprised by catching the differences out of the corner of their eye, double-taking the position of a particularly prominent graphic in relation to another, a subtle hue shift over the course of hours/days/weeks or wondering why their desktop image wasn’t the same as either their friend’s or someone who’s screenshot they’d just seen in a recent blog post.

If nothing else it would be a relatively inexpensive experiment that could offer the start of something new and would be a great celebration of the individuality and diversity of our user base.

The reality:

With the advent of the new visual identity and my involvement therein, it seemed like the perfect opportunity to look into this idea in more detail. The Lucid wallpaper was specifically designed with this purpose in mind. It deliberately used little more than simple radial blurs layered to give an impression of light and depth – where the position of elements would not act negatively against the composition and that we imagined would be easy to animate and move programatically without causing rendering/artefacting issues across a wide range of screen sizes – it was always going to be a fine balancing act but worth it in our opinion.

There are a number of ways we could have done this. We decided to look at having a matching screensaver that would re-write the default wallpaper whenever the user woke their machine from sleep, this seemed like the easiest way to avoid unnecessary processor cycles or unexplained delays (possibly at startup/shutdown). This would also allow us to do a very clean crossover effect between desktop and screensaver where open windows, etc. would elegantly fade away and visa versa.

Sadly we have been unable to allocate the time to get this built internally. I discussed it in a session at the last UDS and there is an open blueprint relating to it. I am still one hundred percent behind pursuing this idea and am actively seeking people to help me make it a reality.

If you’d like to help please get in touch.

Related posts


Massimiliano Gori
2 July 2025

Source to production: Spring Boot containers made easy

Cloud and server Article

This blog is contributed by Pushkar Kulkarni, a Software Engineer at Canonical. Building on the rise in popularity of Spring Boot and the 12 factor paradigm, our Java offering also includes a way to package Spring workloads in production grade, minimal, well organized containers with a single command. This way, any developer can generate ...


Massimiliano Gori
2 July 2025

Spring support available on Ubuntu

Cloud and server Article

This blog is contributed by Vladimir Petko, a Software Engineer at Canonical. The release of Plucky Puffin earlier this year introduced the availability of the devpack for Spring, a new snap that streamlines the setup of developer environments for Spring on Ubuntu. In this blog, we’ll explain what devpacks are and provide an overview of ...


Canonical
1 July 2025

Chiseled Ubuntu containers for OpenJRE 8, 17 and 21

Cloud and server Article

Today we are announcing chiseled containers for OpenJRE 8, 17 and 21 (Open Java Runtime Environment), coming from the OpenJDK project. These images are highly optimized for size and security, containing only the dependencies that are strictly necessary. They are available for both AMD64 and ARM64 architectures and benefit from 12 years of ...