Agreguesi i feed

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.

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.

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

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 xubuntu.org/getxubuntu/. As the main server and mirrors might be busy for the first few days after the release, we recommend using the torrents if possible.

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 [1]: https://discourse.maas.io/t/maas-2-5-0-alpha-1/106

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.

by

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.

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 SDF.org 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 Quitter.se 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 quitter.se PING quitter.se (193.180.164.105) 56(84) bytes of data. ^C --- quitter.se ping statistics --- 811 packets transmitted, 0 received, 100% packet loss, time 829416ms

My pump.io 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 pump.io 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.

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 packet.net baremetal server.

Prerequisites

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 100.100.100.97
• the unused public IP address is 100.100.100.98
• the network is 100.100.100.96/29
• 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: - 100.100.100.98/29 gateway4: 100.100.100.97 nameservers: addresses: - 8.8.8.8 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 100.100.100.98 netmask 255.255.255.255 broadcast 0.0.0.0 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 0.0.0.0 UG 0 0 0 eth0 100.100.100.97 0.0.0.0 255.255.255.240 U 0 0 0 eth0 root@c1public:~# ping -c 3 www.ubuntu.com PING www.ubuntu.com (91.189.89.118) 56(84) bytes of data. 64 bytes from www-ubuntu-com.nuno.canonical.com (91.189.89.118): icmp_seq=1 ttl=53 time=8.10 ms 64 bytes from www-ubuntu-com.nuno.canonical.com (91.189.89.118): icmp_seq=2 ttl=53 time=8.77 ms 64 bytes from www-ubuntu-com.nuno.canonical.com (91.189.89.118): icmp_seq=3 ttl=53 time=9.81 ms --- www.ubuntu.com 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="http://nginx.org/">nginx.org</a>.<br/> Commercial support is available at <a href="http://nginx.com/">nginx.com</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 100.100.100.96/29 Address: 100.100.100.96 01100100.01100100.01100100.01100 000 Netmask: 255.255.255.248 = 29 11111111.11111111.11111111.11111 000 Wildcard: 0.0.0.7 00000000.00000000.00000000.00000 111 => Network: 100.100.100.96/29 01100100.01100100.01100100.01100 000 HostMin: 100.100.100.97 01100100.01100100.01100100.01100 001 HostMax: 100.100.100.102 01100100.01100100.01100100.01100 110 Broadcast: 100.100.100.103 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 (100.100.100.97) and the LXD container public IP address (100.100.100.98) are in this range, therefore all are fine.

Simos Xenitellishttps://blog.simos.info/

When I searched for a way to configure ddclient for No-IP.com, 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
use=web
ssl=yesprotocol=noip
login=<USERNAME>
password=<PASSWORD>
<YOUR_HOSTNAME>
EOF

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 MY_HOST.redirectme.net: good: IP address set to 118.X.Y.Z

For more details, refer to ddclient -help.

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.

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.

• Platinum sponsors:
• TOSHIBA (for 33 months)
• GitHub (for 24 months)
• Civil Infrastructure Platform (CIP)
• Gold sponsors:
• The Positive Internet (for 49 months)
• Blablacar (for 48 months)
• Linode (for 38 months)
• Babiel GmbH (for 28 months)
• Plat’Home (for 27 months)
• Silver sponsors:
• Domeneshop AS (for 49 months)
• Trollweb Solutions (for 46 months)
• Nantes Métropole (for 43 months)
• Dalenys (for 39 months)
• Université Jean Monnet de St Etienne (for 35 months)
• Univention GmbH (for 34 months)
• Ribbon Communications, Inc. (for 28 months)
• maxcluster GmbH (for 22 months)
• Exonet B.V. (for 18 months)
• Leibniz Rechenzentrum (for 12 months)
• Vente-privee.com (for 9 months)
• CINECA
• Bronze sponsors:
• David Ayers – IntarS Austria (for 50 months)
• Evolix (for 49 months)
• Seznam.cz, a.s. (for 49 months)
• Freeside Internet Service (for 48 months)
• MyTux (for 48 months)
• Intevation GmbH (for 46 months)
• Linuxhotel GmbH (for 46 months)
• Daevel SARL (for 45 months)
• Bitfolk LTD (for 43 months)
• Megaspace Internet Services GmbH (for 43 months)
• NUMLOG (for 43 months)
• Greenbone Networks GmbH (for 42 months)
• WinGo AG (for 42 months)
• Ecole Centrale de Nantes – LHEEA (for 38 months)
• Sig-I/O (for 36 months)
• Entr’ouvert (for 33 months)
• Adfinis SyGroup AG (for 31 months)
• GNI MEDIA (for 25 months)
• Laboratoire LEGI – UMR 5519 / CNRS (for 25 months)
• Quarantainenet BV (for 25 months)
• RHX Srl (for 22 months)
• Bearstech (for 17 months)
• LiHAS (for 17 months)
• People Doc (for 13 months)
• Catalyst IT Ltd (for 11 months)
• Supagro (for 7 months)
• Demarcq SAS (for 5 months)
• TrapX Security

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

Kubuntu Linux has been my preferred Linux distribution for more than 10 years. My attraction to the KDE desktop and associated application set, has drawn from Kubuntu user, to a tester, teacher, developer, community manager and councilor. I feel really privileged to be part of, what can only be described as, a remarkable example of the free software, and community development of an exceptional product.

This latest release 18.04, effectively the April 2018 release, is a major milestone. It is the first LTS Long Term Support release of Kubuntu running the “Plasma 5” desktop.
The improvements are so considerable, in both performance and modern user interface ( UI ) design, that I was really excited about wanting to tell the world about it.

Which is why I was completely ecstatic when I was commissioned by Linux Magazine to write a 2000 word article, spanning some 4 pages, as a major review center piece in their magazine.

Published as “Linux Pro Magazine” in the US and “Linux Magazine” in Europe.

In the article I dive into one of the greatest and most unsung features of KDE Plasma 5; “Activities”. The introduction of activities in KDE has been a revelation to me, and completely changed the way that I work on a day to day basis. I encourage you whole heartedly to explore them, if you haven’t done so already.

Published in the August 2018 edition, and from which the introduction is available online at http://www.linux-magazine.com/Issues/2018/213/Kubuntu-18.04 or of course you can buy the August issue from http://www.linux-magazine.com/Issues/2018/213.

It is fantastic to see Kubuntu hitting the main stream publishing and to have an in-depth review article in one of the global leading Linux magazines is wonderful.

by Rick Timmis