You are here

Planet Ubuntu

Subscribe to Feed Planet Ubuntu
Planet Ubuntu -
Përditësimi: 6 months 4 javë më parë

Valorie Zimmerman: Ade visits, and the weather changes so we can walk about Deventer

Mër, 08/08/2018 - 6:00md
A lovely lunch and a shared afternoon and evening with Ade was a pleasant interlude in our time together here in beautiful Deventer. We changed tables a few times to avoid the sun! Last night we were wakened at around 2am with wind blowing rain into the open windows, which was quite exciting. Thunder roared in the south. It was still quite cool and breezy this morning so we ate inside.

After lunch, Boud proposed a walk around the town while the temperatures were moderate. We walked over much of the old town of Deventer, and spend some time in the Roman Catholic church, the old church on the "hill" with twin spires, the old Brush Shop, and back past the Weighing House and a lovely cast bronze map of Deventer.

Our favorite tree:

The Roman Catholic church whose steeple we see from the terrace:
On the wall of the Weighing House:

Our little corner of Deventer:

Tomorrow we travel by fast train to Vienna! I hope there is time to drink a cup of coffee. :-)

Sean Davis: Mugshot 0.4.1 Released

Mër, 08/08/2018 - 12:04md

Mugshot 0.4.1, the latest release of the lightweight user profile editor, is now available! This release includes a number of bug fixes and will now run in the most minimal of environments.

What’s New? Code Quality Improvements
  • Replaced deprecated logger.warn with logger.warning (Python 2.x)
  • Replaced deprecated module optparse with argparse (Python 2.7)
  • Resolved Pylint and PEP8 errors and warnings
Bug Fixes
  • TypeError in _spawn(): The argument, args, must be a list (LP: #1443283)
  • User-specified initials are not correctly loaded (LP: #1574239)
  • Include Mugshot in Xfce Settings, Personal Settings (LP: #1698626)
  • Support -p and -w office phone flags in chfn. This flag varies between chfn releases. (LP: #1699285)
  • FileNotFoundError when comparing profile images (LP: #1771629)
Support for Minimal Chroot Environments
  • Fix crash when run without AccountsService
  • Handle OSError: out of pty devices
  • Specify utf-8 codec for desktop file processing when building
Translation Updates

Catalan, Chinese (Simplified), Danish, Lithuanian, Spanish


Source tarball (md5sig)

Benjamin Mako Hill: Lookalikes

Mar, 07/08/2018 - 11:00md

Am I leading a double life as an actor in several critically acclaimed television series?

I ask because I was recently accused of being Paul Sparks—the actor who played gangster Mickey Doyle on Boardwalk Empire and writer Thomas Yates in the Netflix version of House of Cards. My accuser reacted to my protestations with incredulity. Confronted with the evidence, I’m a little incredulous myself.

Previous lookalikes are here.

Lubuntu Blog: This Week in Lubuntu Development #8

Mar, 07/08/2018 - 12:09pd
Here is the eighth issue of This Week in Lubuntu Development. You can read the last issue here. Translated into: español Changes General Lubuntu 18.04.1 has been released! Lubuntu 16.04.5 has been released! We’re taking a new direction. The past couple of weeks have been focused on more desktop polish and some heavy infrastructure and […]

Sam Hewitt: Moving Beyond Themes

Dje, 05/08/2018 - 5:00md

FreeDesktop platforms have come a long way in terms of usability and as we strive to make them better platforms for application developers, I think it’s time to shed one more shackle that slows that down: themes.

Now, coming from me that view may be a surprise (because of all those themes that I call personal projects) but I do feel it’s necessary mainly because the level of visual customisation that is being done at the distribution level has led to widespread visual fragmentation which impacts both user- and developer-friendliness.

Letting the Past Go

What themes used to be were sets of preset or configuration files that would only tweak the details of the user interface such as the window borders or how buttons and scrollbars looked but the overall layout and function stayed the same.

But user interfaces of the past were much simpler, there were fewer window states, fewer points of interaction, less visual feedback, and just plain fewer pixels. These limitations in old toolkits meant that they largely stayed the same from theme to theme and things were relatively stable.

Fast-forward to today where we have modern toolkits like GTK+ 3 with more complex visuals and detailed interactions means that without the same level of quality control that you find at the toolkit level, maintaining a separate theme is a very fiddly and potentially buggy prospect. Not to mention getting all the details right matters for both usability and accessibility.

“Look and Feel” as a Toolkit Component

It’s unfortunate that “Adwaita” is thought of as a theme when in fact it is a core component of the toolkit, but this is mostly a holdover from how we’re used to thinking about look and feel as it relates to the user interface. Adwaita is as closely tied to GTK+ as Aqua is to the macOS user interface, and as a result it has broad implications applications built with GTK+.

The reality is that GTK+ 3 has no theme framework (there is no API or documentation for “themes”) and “Adwaita” is simply the name of the stylesheet deeply integrated in GTK+. So when third-party developers build GNOME apps, they rely on this stylesheet when determining the look and feel of their apps and, if necessary, use it as a reference when writing their own custom stylesheets (since it is a core toolkit component).

Today’s themes aren’t themes

GTK+ 3 themes are not themes in the traditional sense. They are not packages of presets designed to work with the user interface toolkit, they are more like custom stylesheets which exist outside of the application-UI framework and only work by essentially overriding the toolkit-level stylesheet (and quite often only the toolkit-level stylesheet).

When GTK+ 3 applications are being used under third-party themes, what is being broken is the boundary an application developer has set up to control both the quality of their application and how it looks and feels and this becomes really problematic when applications have custom CSS.

In order for third party themes to work properly and not cause cascading visual bugs, they have to either become monolithic and start incorporating all the custom stylesheets for all the applications that have them, or work with application developers to include stylesheets in their applications that support their themes. Neither of these solutions are good for platform or application development since it will become a task of never-ending maintenance.

Visual Fragmentation

Across the GNOME desktop ecosystem exists “visual fragmentation” and it’s a very real problem for app developers. Since very few distributions ship GNOME as-is, it is hard to determine what the visual identity of GNOME is and therefore it’s difficult to know which visual system to build your application for.

Integrating the stylesheet with the user interface toolkit, in theory, should have solved many issues regarding visual inconsistency across the GNOME platform, but that’s an unsolveable problem so long as themes persist.

The biggest offenders continue to be downstream projects that theme GNOME extensively by overriding the default icons and stylesheet, and insist that that’s part of their own brand identity, but so long as that practice carries on then this fragmentation will continue.

Upstream vs. Downstream Identity

It is extremely rare for a Linux distribution to also be the platform vendor, so it can be said that nearly all distros that ship a desktop platform (like GNOME) are “downstream” vendors.

Platforms like GNOME and KDE exist irrespective of distributions and they have their own visual and brand identities, and own guidelines around the user interface. On the other hand, distribution vendors see a need to have unique identities and some decide to extend that to the look and feel of the desktop and apply themes.

But this practice raises questions about whether it is right or not for distributions to cut out or override the upstream platform vendor’s identity to favour their own. Should distributions that ship GNOME be asked to leave the default look and feel and experience intact? I think yes.

A similar situation exists on Android where Google is trying to control the look and feel of Android and hardware OEMs all over the place are skinning it for their phones, but the blame for issues gets conflated with issues in Android (unless you do some monumental branding effort and effectively erase Android, like Samsung)

Distributions owe a lot to the desktop platforms, as such I think that effort should be made to respect the platform’s intended experience. Not to mention, the same concerns for quality assurance regarding applications also applies to the platform, GNOME developers lose out when then forced to dedicate time and resources to dealing with bugs related to issues created by downstream theming and deviations.

The Future

If ending the wild west of visual customisation (which would probably end all of those projects of mine) on GNOME is necessary to grow the ecosystem, so be it.

I would rather see GNOME evolve as a platform and become a little less developer-hostile by dropping support for third-party themes, than stagnate. Doing so would also bring us in line with the how the major (successful) platforms maintain a consistent look and feel and consider app developers’ control over their apps and their rights to their brand identities.

That said, I doubt such a hardline position will be widely warmly recieved, but I would like to see a more closed approach to look and feel. Though, perhaps actually building some sort of framework that allows for custom stylesheets (so that downstreams can have their unique visual identities) that doesn’t involve totally overriding the one at the toolkit level would be the best solution.

Ubuntu Studio: Ubuntu Studio 18.10 Wallpaper Contest

Mër, 01/08/2018 - 6:18md
As we begin getting closer to the next release date of Ubuntu Studio 18.10, now is a great time to show what the best of the Ubuntu Studio Community has to offer! We know that many of our users are graphic artists and photographers and we would like to see their/your talent also reflected more […]

Sean Davis: Xubuntu Development Update August 2018

Mër, 01/08/2018 - 1:56md

July was an surprisingly productive month for Xubuntu. While several folks in the team were on vacation for some portion of the month, we still managed to deliver a number of great updates!

LTS Updates Xenial Xerus – 16.04.5

This is the final point release for Xubuntu 16.04 “Xenial Xerus”. As Xubuntu has a 3-year support cycle, this release will be supported until April 2019. There have not been any major changes from the Xubuntu team for this point release, but there have been a number of other improvements and security updates for other components.

16.04.5 is expected to be released tomorrow, August 2, 2018. If you have a few moments, feel free to do some testing and make sure everything is working as well as we think it is!

Bionic Beaver – 18.04.1

This is the first point release for Xubuntu 18.04 “Bionic Beaver”. At this time, users of Xubuntu 16.04 should begin receiving notifications to upgrade to this release. There have been a few updates from the Xubuntu team, and others are still on their way. Download 18.04.1 here.

Application Updates Catfish 1.4.6

The latest release of Catfish features a greatly improved thumbnail manager and numerous bug fixes. With 23 translation updates, this is the most localized release to date! Finally, Catfish 1.4.6 is the first release as an official Xfce project. Check out my earlier blog post for more details.

Xfce4 Panel Profiles 1.0.8

Formerly known as Xfpanel Switch, Xfce4 Panel Profiles has joined the Xfce family. This application makes it incredibly easy to backup, restore, and share panel layouts with other Xfce users. The latest release improves profile management and includes a number of translations. Find out more about the latest updates on the release announcement.

Xfce Releases

There were 7 new Xfce releases in July, including the two applications listed just above. These releases feature a number of improvements and translation updates, with Xfwm4 4.13.1 featuring an astounding 81 non-translation updates!

Cosmic Cuttlefish Updates

The following components have been updated in Xubuntu 18.10 since July 1st.

Applications Libraries Panel Plugins Thunar Plugins Other Updates What to Expect in August?

With the summer months coming to a close, kids are back in school and everybody is back in front of their computers. This means more updates! Here are some things expected soon:

  • Updated packaging for the elementary-xfce icon theme. Work on separating this theme from xubuntu-artwork has already been completed. We are now just waiting for some sponsored uploads. The benefit of this change is that the elementary-xfce icon theme is now available in Debian!
  • Xfce Settings 4.13.5. There have been some improvements to the settings managers that we’ll be releasing soon. One improvement is the removal of the broken icon theme color generation. This worked great with GTK+ 2 themes, but has been pretty broken for GTK+ 3. With this removal, Appearance Settings now loads instantly!
  • I’ll be taking a look at the Pidgin codebase this month, hoping to improve the theme manager to support system-wide status icon and smiley theme installation. This will make it possible for us to ship the pidgin-elementary themes and further improve our desktop consistency.
  • There have been a few bugs reported with Thunar in Xubuntu 16.04 in regard to copying and moving files. I’ll be working to update the Thunar version in Xenial to fix these bugs and help folks transition to the latest and great Xubuntu 18.04. (LP: #1514912)

Keep up with the latest Xubuntu developments on our development tracker. Have a great month!

Sergio Schvezov: Snapcraft Build Environments

Hën, 30/07/2018 - 10:47md
Prologue After a week away from my computer I want to organize my thoughts on the progress made towards build VMs by providing this write up since that forum post can be a bit overwhelming if you are casually wanting to keep up to date. The reasons for this feature work to exist, for those not up to speed, is that we want to have a very consistent build environment for which anyone building a project can have an expectable outcome of a working snap (or non working one if it really doesn’t).

Benjamin Kerensa: Remembering Gerv Markham

Dje, 29/07/2018 - 12:44pd
Gervase Markham (cc by sa didytile)

Gerv Markham, a friend and mentor to many in the Mozilla community, passed away last night surrounded by his family.


Gerv worked at Mozilla for many years working in a variety of capacities including being a lead developer of Bugzilla and most recently working on special projects under the Mozilla Chairwoman.


I had the pleasure of working with Gerv in the Thunderbird community and most recently on the MOSS Grants Committee as one of the inaugural members. Between these two areas, I often sought Gerv’s mentoring and advice, as he always had wisdom to share.


Anyone who has been intimately involved with the Mozilla project likely engaged Gerv from time to time, although much of his work was behind the scenes but nonetheless important work.


I think it goes without saying Gerv had a significant impact on the open web through his contributions to Bugzilla and various projects that moved the open web forward and he championed the values of the Mozilla manifesto. All of us who knew him and got the opportunity to collaborate were rewarded with a good friend and valuable wisdom that will be missed.


Thanks Gerv for being a friend of Mozilla and the open web and you will be surely missed.

Sebastian Kügler: Lunar Eclipse Blood Moon

Sht, 28/07/2018 - 12:04pd

Blood Moon of July 2018
Tonight, I spent some time on the balkony with my SLR, a glass of Shiraz and the most significant lunar eclipse of the century.

Sam Hewitt: Adorbs for Telegram!

Pre, 27/07/2018 - 6:00md
Stickers are just glorified icons right??

Adorbs used to be an iMessage sticker pack that I maintained, but I let my Apple developer account lapse, so I made them into a Telegram sticker pack! Available now!

Download for Telegram

Xubuntu: 18.04.1 Released

Enj, 26/07/2018 - 9:35md

The first point release for 18.04 Bionic Beaver has now been released.

As usual, this point release includes many updates, and updated installation media has been provided so that fewer updates will need to be downloaded after installation. These include security updates and corrections for other high-impact bugs, with a focus on maintaining stability and compatibility with Ubuntu 18.04 LTS.

The point release images are available as torrents immediately from the links below.

64-bit systems32-bit systems

The images are also available as direct downloads from As the main server and mirrors might be busy for the first few days after the release, we recommend using the torrents if possible.

Andres Rodriguez: MAAS 2.5.0 alpha 1 released!

Enj, 26/07/2018 - 7:46md
Hello MAASters! I’m happy to announce that the current MAAS development release (2.5.0 alpha 1) is now officially available in PPA for early testers. What’s new? Most notable MAAS 2.5.0 alpha 1 changes include:
  • Proxying the communication through rack controllers
  • HA improvements for better Rack-to-Region communication and discovery
  • Adding new machines with IPMI credentials or non-PXE IP address
  • Commissioning during enlistment
For more details, please refer to the release notes available in discourse [1]. Where to get it? MAAS 2.5.0a1 is currently available for Ubuntu Bionic in ppa:maas/next. sudo add-apt-repository ppa:maas/next
sudo apt-get update
sudo apt-get install maas

Jonathan Riddell: KDE neon Bionic Update

Enj, 26/07/2018 - 5:06md

The work to rebase KDE neon on Bionic is progressing. Apologies if it feels slow but it’s keeping our infrastructure busy while continuing with the xenial builds alongside.  I’ve just managed to get the package version check to turn green which means all the packages are now built.  The installable ISOs are also green on our builders, but we’re keeping them hidden until we’ve ironed out the bugs.  The two installers we use have some quirks and hacks that need tidied up but the automated install tests are also turning green.  Some of you have already found our preliminary instructions for doing the upgrade and it seems to be working for everyone who has tried it, but “it seems to be working” is not what we want, “it is working” is what we want and while the git-unstable edition is green in the tests the user edition is not so some more tidying up to be done there. We’ll announce the installable ISOs and upgrade more formally for beta testing once the tests are green and turn on the full upgrade shortly after.  Hasta pronto.


Didier Roche: Open The Cosmic Gate: A beautiful theme gets a beautiful name

Mar, 24/07/2018 - 11:10pd
A beautiful theme gets a beautiful name

Communitheme has been a community effort from the start with an overwhelming amount of feedback from an even larger community. Surprisingly, the still ongoing discussion thread of more than 1500 messages hasn’t (yet?) broken discourse!

However, the effort to refresh the look and feel of Ubuntu has gone way beyond just a theme. From the start, Sam Hewitt’s beautiful Suru icons were included and over time, the effort brought new system sounds and new cursors under its wing. Some of the design discussions have gone even further than this, but the desire to stay as close to upstream GNOME as possible has put most of those in the freezer for now. So, in order to reflect the broad scope and in light of its upcoming inclusion in Ubuntu, a new name is in order.

After 8 months of intense labour, we are proud to announce the birth of Yaru!

A fully community grown theme, ready to look good and be awesome. Yaru continues on the Japanese influences of Suru, and its meaning, “to do” or “to give” fits perfectly with this project: Yaru is here because we did it, we’re happy to give it to you to spread Ubuntu’s culture of sharing, and we hope it helps you do cool stuff on Ubuntu. Best of all, even the name was vetted in by the community! A poll confirmed that this name is widely loved by the entire Communitheme-community. A longer explanation of Yaru vs Suru could be found here.

We did not do it in a day..

Communitheme project got immediately big expectations from the community. Many people were eagerly awaiting this style refresh and wanted it as default theme in the 18.04 LTS (codename Bionic Beaver) release. However, we decided to postpone its release to give us the freedom to keep changing the theme, since an LTS would mean that the theme’s look and feel is fixed for a few years. Two months after the Bionic release, looking at the commit activity and at the list of pull requests, it’s clear this was the right decision. We have gone through several iterations that affected also the very basic elements of style.

  • The color & shape of our button sets changed to look bright, sharp and elegant.
  • The colors for the window and sidebar background are changed to a more warm and welcoming tone, like we did for the headerbars at the beginning.
  • We abandoned the strong orange for the text selection and changed it to a more discrete blue.
  • We changed the Color & shape of GNOME and GTK notifications so that they pop up nicer from the background.
  • Finally, many changes were made to the transparency, borders, shadows, colors and depth effects so GNOME Shell looks like something in between Unity7, Unity8 and the new design ideas.

The use of flat design was also discussed thoroughly, because it is very common nowadays. Flat UI is less distracting and gives an uncluttered and sharp look, but it can also be boring and decrease the UX. We decided to mix both styles: the contours, GNOME shell and the headerbars are flat and the applications themselves in the center have a gentle 3D effect to better highlight where the focus should be.

Those themes are based on both upstream GNOME Shell and Adwaita themes sass files, making the whole maintenance way easier.

We did not do it alone…

We sincerely want to thank for all the feedback, ideas, PRs and also testing and reports the whole community, just to name a few: ya-d, jaggers, yazub, NusiNusi, nana-4, CraigD, vinceliuce, Paz-it, mivoligo, taciturasa. Without their huge support we surely would not have gone this far in so little time, and of course we want to thank the Design and Development team Stefan Eduard Krenn, Carlo Lobrano, Mads Rosendahl, Frederik Feichtmeier, Merlijn Sebrechts, Aaron Papin, whose constant effort and professionalism shaped Yaru theme commit after commit and discussion after discussion since the very beginning of this awesome journey.

What will happen in the coming days?

If you are one of the 19 000 people who downloaded the communitheme snap on ubuntu 18.04 LTS, basically nothing will change for you and you will still get the regular flow of daily (commitly? ;)) or weekly updates depending on which channel you have chosen ! We made a good deal in keeping backward compatibility for this user base. Snaps can’t be renamed yet, and consequently, we decided on keeping “communitheme” codename for this version. You still get latest of latest, and the build system has now some tweaks to ensure you get a compatible version with your system. You will still log into your communitheme dedicated session.

We are going to transition Cosmic (incoming 18.10 Ubuntu release) very soon to use a newly set of distribution packages under the Yaru new name. The new package will enter in the coming days to the ubuntu archive and the default ubuntu session will switch to it soon (once we get the package in main and makes some changes in various projects and default settings)! It won’t get as many refresh cycle as the snap based version, but we’ll make regular snapshots. Please use the snap if you want to give continuous feedback on the ubuntu hub with its dedicated section or or directly install from source.

Speaking of installing from source, we merged last week our different repositories (5 of them) into a single one to ease maintenance and releases. Now, we can get very easily the “Yaru” experience (GTK2, GTK3, GNOME Shell, icon, cursor and sound themes), cloning a single git repository and installing from it!

Eager to help?

Note that screenshots are still Work In Progress, there is still some discussions about keeping the Ubuntu logo by default on the launcher or not and other fundamentals changes that the community can decide until the Cosmic Cuttlefish release.

We still need some helps, in particular in the GTK2 world (which will be used to provide theming for Qt applications as well). It has never been easier to contribute to Yaru thanks to the recent repository reorganization: contributing to the projects is now simply heading to the Yaru repository under the ubuntu organization, read the README and contributing guidelines. All coordination still goes through the community ubuntu HUB and its dedicated topic. Will you be the next one? :)

Didier - on behalf of the whole communitheme core contributor team who contributed to this announce.

Stephen Michael Kellat: Social Media Presences Terminated So Far Today

Mar, 24/07/2018 - 3:38pd

Some people have been wondering where I've been online. In conformance to some "employee protection" orders at work, I've had to begin terminating various & sundry bits of online presence. These sorts of orders are such that I do eventually have to obey them.

My Twitter account is gone. I currently have no active presence there.

My Flickr account is gone. I currently have no active presence there.

My account on the Mastodon network via has been gone for some time. If you've been looking for me there that account isn't being restored any time soon.

My account on is as good as gone considering I can't even get a ping response back from that system. After all, this is what I get from attempting a ping:

$ ping PING ( 56(84) bytes of data. ^C --- ping statistics --- 811 packets transmitted, 0 received, 100% packet loss, time 829416ms

My account on Identica is locked in "Hotel California" mode and cannot be terminated by me at this time. That's probably a good thing. The network still exists, ya know.

Additionally, I've been getting tired of seeing things spill over on various social networks about how the current President of the United States (my 11th-line supervisor) is the embodiment of evil walking this planet. It is bad enough spending eight hours per day being paid by the federal government to hear that garbage while protecting the nation's financial interests. Coming home to hear that too is just a step too far. There just comes a point where I can't handle it anymore & have to cut something back.

This blog remains. I'm not going totally dark. Trying to be a light and to spread light is just not as easy as it sounds in this crazy world. Thankfully there is F/LOSS like the many flavours of Ubuntu to at least ensure that I don't have to include computer issues among my many worries right now. Worst comes to worst, you can give me a call on Telegram perhaps if you are so moved.

Simos Xenitellis: Configuring public IP addresses on cloud servers for LXD containers

Hën, 23/07/2018 - 6:30md

You have a cloud server and you got more than one public IP addresses.

How do you get those additional IP addresses to associate to specific LXD containers?

That is, how do you get your LXD container to use a public IP address?

This post has been tested with a baremetal server.


You have configured a cloud server and you arranged to have at least one additional public IP address.

In the following, we assume that

  • the gateway of your cloud server is
  • the unused public IP address is
  • the network is
  • the default network interface on the host is enp0s100 (if you have a bonded interface, the name would be something like bond0)
Creating a macvlan LXD profile

Create a new LXD profile and set up a macvlan interface. The name of the interface in the container will be eth0, the nictype is macvlan and the parent points to the default network interface on the host.

$ lxc profile create macvlan$ lxc profile device add macvlan eth0 nic nictype=macvlan parent=enp0s100

Here is how the profile macvlan looks like.

ubuntu@myserver:~$ lxc profile show macvlan config: {} description: "" devices: eth0: nictype: macvlan parent: enp0s100 type: nic name: macvlan used_by: Launching the container

Launch the container by specifying the macvlan profile on top (stacked) of the default profile. The container is called c1public.

$ lxc launch --profile default --profile macvlan ubuntu:18.04 c1public

Get a shell into the container and view the network interfaces

ubuntu@myserver:~$ lxc exec c1public bash root@c1public:~# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::216:3eff:fe55:1930 prefixlen 64 scopeid 0x20<link> ether 00:16:3e:55:19:30 txqueuelen 1000 (Ethernet) RX packets 82 bytes 5200 (5.2 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 16 bytes 2788 (2.7 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 .... root@c1public:~# ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 8: eth0@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:55:19:30 brd ff:ff:ff:ff:ff:ff link-netnsid 0

At this stage, we can configure manually the appropriate public IP address for the network interface eth0 of the container and it will work. If you are familiar with /etc/network/interfaces, you can go ahead and make the static network configuration. In the next section we are going to see how to use netplan to configure the network.

Configuring the public IP with netplan

In the container, create a file /etc/netplan/50-static-public-ip.yaml so that it as follows. There are two options for the renderer, networkd (systemd-networkd which is available on Ubuntu 18.04) and NetworkManager. We then specify the public IP address, the gateway and finally the DNS server IP addresses. You may want to replace the DNS server with that of your cloud provider.

root@c1public:~# cat /etc/netplan/50-static-public-ip.yaml network: version: 2 renderer: networkd ethernets: eth0: dhcp4: no dhcp6: no addresses: - gateway4: nameservers: addresses: - Applying the netplan network configuration

Run the following command to apply the netplan network configuration. Alternatively, you can restart the container.

root@c1public:~# netplan --debug apply ** (generate:294): DEBUG: 15:46:19.174: Processing input file //etc/netplan/50-cloud-init.yaml.. ** (generate:294): DEBUG: 15:46:19.174: starting new processing pass ** (generate:294): DEBUG: 15:46:19.174: Processing input file //etc/netplan/50-static-public-ip.yaml.. ** (generate:294): DEBUG: 15:46:19.174: starting new processing pass ** (generate:294): DEBUG: 15:46:19.174: eth0: setting default backend to 1 ** (generate:294): DEBUG: 15:46:19.175: Generating output files.. ** (generate:294): DEBUG: 15:46:19.175: NetworkManager: definition eth0 is not for us (backend 1) DEBUG:netplan generated networkd configuration exists, restarting networkd DEBUG:no netplan generated NM configuration exists DEBUG:device lo operstate is unknown, not replugging DEBUG:netplan triggering .link rules for lo DEBUG:device eth0 operstate is up, not replugging DEBUG:netplan triggering .link rules for eth0 root@c1public:~#

Here is the network interface with the new IP address,

root@c1public:~# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet netmask broadcast inet6 fe80::216:3eff:fe55:1930 prefixlen 64 scopeid 0x20<link> ether 00:16:3e:55:19:30 txqueuelen 1000 (Ethernet) RX packets 489 bytes 30168 (30.1 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 18 bytes 1356 (1.3 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ... root@c1public:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default _gateway UG 0 0 0 eth0 U 0 0 0 eth0 root@c1public:~# ping -c 3 PING ( 56(84) bytes of data. 64 bytes from ( icmp_seq=1 ttl=53 time=8.10 ms 64 bytes from ( icmp_seq=2 ttl=53 time=8.77 ms 64 bytes from ( icmp_seq=3 ttl=53 time=9.81 ms --- ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 8.106/8.896/9.810/0.701 ms root@c1public:~# Testing the public IP address

Let’s test that the public IP address of the LXD container works. We install nginx and modify a bit the default HTML page.

ubuntu@c1public:~$ sudo apt update ... ubuntu@c1public:~$ sudo apt install nginx ... ubuntu@c1public:~$ cat /var/www/html/index.nginx-debian.html <!DOCTYPE html> <html> <head> <title>Welcome to nginx!</title> <style> body { width: 35em; margin: 0 auto; font-family: Tahoma, Verdana, Arial, sans-serif; } </style> </head> <body> <h1>Welcome to nginx!</h1> <p>If you see this page, the nginx web server is successfully installed and working. Further configuration is required.</p> <p>For online documentation and support please refer to <a href=""></a>.<br/> Commercial support is available at <a href=""></a>.</p> <p><em>Thank you for using nginx.</em></p> </body> </html> ubuntu@c1public:~$ sudo sed -i 's/to nginx/to nginx running in a LXD container with public IP address/g' /var/www/html/index.nginx-debian.html ubuntu@c1public:~$

Let’s visit the public IP address with our browser!

It worked!

Troubleshooting Help! I can see the IP address but there is no route?!?

Most likely you misconfigured the network prefix in the netplan configuration file. Find the details at

ubuntu@myserver:~$ sudo apt install ipcalc ubuntu@myserver:~$ ipcalc Address: 01100100.01100100.01100100.01100 000 Netmask: = 29 11111111.11111111.11111111.11111 000 Wildcard: 00000000.00000000.00000000.00000 111 => Network: 01100100.01100100.01100100.01100 000 HostMin: 01100100.01100100.01100100.01100 001 HostMax: 01100100.01100100.01100100.01100 110 Broadcast: 01100100.01100100.01100100.01100 111 Hosts/Net: 6 Class A

The public IP addresses have the range 100.100.100.[97-102]. Both the gateway ( and the LXD container public IP address ( are in this range, therefore all are fine.

Simos Xenitellis

Nobuto Murata: Minimal Dynamic DNS configuration for with ddclient

Sht, 21/07/2018 - 8:56pd

When I searched for a way to configure ddclient for, some pages mention protocol=dyndns2 with a custom URL. But actually, ddclient supports protocol=noip out of the box, so minimal steps would be something like:

$ sudo apt install ddclient$ cat <<EOF | sudo tee /etc/ddclient.conf

And here we go.

$ echo 'run_daemon="true"' | sudo tee -a /etc/default/ddclient$ sudo service ddclient restart$ journalctl -u ddclient.service
systemd[1]: Started LSB: Update dynamic domain name service entries.
ddclient[24631]: SUCCESS: updating good: IP address set to 118.X.Y.Z

For more details, refer to ddclient -help.

Xubuntu: Xubuntu 17.10 EOL

Sht, 21/07/2018 - 7:20pd

On Thursday 19th July 2018, Xubuntu 17.10 goes End of Life (EOL). For more information please see the Ubuntu 17.10 EOL Notice.

We strongly recommend upgrading to the current release, Xubuntu 18.04, as soon as practical. Alternatively you can download the current Xubuntu release and install fresh.

Raphaël Hertzog: Freexian’s report about Debian Long Term Support, June 2018

Pre, 20/07/2018 - 4:28md

Like each month, here comes a report about the work of paid contributors to Debian LTS.

Individual reports

In June, about 202 work hours have been dispatched among 13 paid contributors. Their reports are available:

  • Abhijith PA did 8 hours (out of 10 hours allocated, thus keeping 2 extra hours for July).
  • Antoine Beaupré did 24 hours (out of 12 hours allocated + 12 extra hours).
  • Ben Hutchings did 12 hours (out of 15 hours allocated, thus keeping 3 extra hours for July).
  • Brian May did 10 hours.
  • Chris Lamb did 18 hours.
  • Emilio Pozuelo Monfort did 17 hours (out of 23.75 hours allocated, thus keeping 6.75 extra hours for July).
  • Holger Levsen did nothing (out of 8 hours allocated, thus keeping 8 extra hours for July).
  • Hugo Lefeuvre did 4.25 hours (out of 23.75 hours allocated, but gave back 10 hours, thus keeping 9.5 hours for July).
  • Markus Koschany did 23.75 hours.
  • Ola Lundqvist did 6 hours (out of 8 hours allocated + 17.5 remaining hours, but gave back 15.5 unused hours, thus keeping 4 extra hours for July).
  • Roberto C. Sanchez did 29.5 hours (out of 18 hours allocated + 11.5 extra hours).
  • Santiago Ruano Rincón did 5.5 hours (out of 8 hours allocated + 7 extra hours, thus keeping 9.5 extra hours for July).
  • Thorsten Alteholz did 23.75 hours.
Evolution of the situation

The number of sponsored hours increased to 210 hours per month. We lost a silver sponsor but gained a new platinum sponsor with the Civil Infrastructure Platform project (hosted by the Linux Foundation, see their announce).

We are very happy to see the CIP project engage directly with the Debian project and try to work together to build the software stack for tomorrow’s world’s infrastructure.

The security tracker currently lists 57 packages with a known CVE and the dla-needed.txt file 52.

Thanks to our sponsors

New sponsors are in bold.

No comment | Liked this article? Click here. | My blog is Flattr-enabled.