<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Iain Lane on Medium]]></title>
        <description><![CDATA[Stories by Iain Lane on Medium]]></description>
        <link>https://medium.com/@iain.lane?source=rss-2e4866472bb7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*r3McRv4OwO8gJFjg.</url>
            <title>Stories by Iain Lane on Medium</title>
            <link>https://medium.com/@iain.lane?source=rss-2e4866472bb7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 07:32:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@iain.lane/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Codecs and PackageKit in GNOME Software on Ubuntu Artful]]></title>
            <link>https://medium.com/@iain.lane/codecs-and-packagekit-in-gnome-software-on-ubuntu-artful-447ddd70d3f9?source=rss-2e4866472bb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/447ddd70d3f9</guid>
            <category><![CDATA[ubuntu]]></category>
            <category><![CDATA[gnome]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Iain Lane]]></dc:creator>
            <pubDate>Fri, 30 Jun 2017 22:26:35 GMT</pubDate>
            <atom:updated>2017-06-30T22:26:54.240Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p>There are some changes coming soon™ to software installation via GNOME Software in Artful.</p><h3>PackageKit</h3><p><a href="https://www.freedesktop.org/software/PackageKit/pk-intro.html">PackageKit</a> is a distribution-agnostic API for managing installed software packages on a system. For irritating reasons, Ubuntu was stuck for a long time on an old version of PackageKit, but we recently managed to remove the blockers and update to a modern version.</p><p>For me, a really positive thing to come out of this is that we are able to remove our Ubuntu specific apt plugin inside GNOME Software. This plugin uses both libapt and aptdaemon to manage package listing, installation, updating and removal. We had to write all this code, it isn’t in the upstream package, and it has been the source of bugs in the past — bugs which wouldn’t have happened if we had been able to use PackageKit. Once this work is all uploaded to Ubuntu, we’ll be sharing the same plugin as most other distributions, meaning that we all benefit from everybody’s fixes.</p><h3>Installing codecs</h3><p>That’s all more or less invisible to users though — given that we’ve worked hard to fix many known bugs in the apt plugin.</p><p>Let’s talk about something else that’s possible now that we’re using the new PackageKit.</p><p>In Ubuntu currently, when you try to play an audio or video file for which you don’t have a codec, the experience looks like this.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FbU8LEQUnHCo%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DbU8LEQUnHCo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FbU8LEQUnHCo%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a240c2640bd9e4f1733071f2fd826d14/href">https://medium.com/media/a240c2640bd9e4f1733071f2fd826d14/href</a></iframe><p>The software that’s providing this procedure is called sessioninstaller. It’s a piece of software that provides PackageKit’s “session” interface, used by applications to request the installation of software such as codecs. Behind the scenes it doesn’t use PackageKit at all to install software — this is handled by aptdaemon. While this solution has worked well for Ubuntu for a long while, the sessioninstaller package (along with aptdaemon itself) is more or less unmaintained and we would like to centralise software installation and management in GNOME Software. Enabling the PackageKit backend allows GNOME Software to provide the session interface itself — it performs the same job that sessioninstaller does but inside the same program that we use for other software installation. It now looks like this.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F2Ae-d1UmOoA%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D2Ae-d1UmOoA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F2Ae-d1UmOoA%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/737c7485f99f8c333c72d8f575b5fbf9/href">https://medium.com/media/737c7485f99f8c333c72d8f575b5fbf9/href</a></iframe><p>This work is not in Ubuntu yet, but it will be before the Alpha 2 release of Artful. You can try it from <a href="https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2820/+packages">this PPA</a>, if you’re adventurous. To get to this stage, fixes were required in many components. The <a href="http://appstream.ubuntu.com/">AppStream generator</a> needed to be <a href="https://github.com/ximion/appstream-generator/commit/b9920b07a9c1ad47ad887035a3ab738780807f7e">enhanced</a> to provide decent metadata about the packages containing codecs. Some bugs in GNOME Software itself were <a href="https://git.gnome.org/browse/gnome-software/commit/?id=0d2d8ad8c367c4d321173ec76c93b0ff8d546a7d">discovered</a>, which prevented the results for showing properly. And PackageKit itself needed fixes in its aptcc backend. Some of these are <a href="https://github.com/hughsie/PackageKit/commit/c9b7a5646cc66853f57caec8194ac5f537ff96bd">already</a> <a href="https://github.com/hughsie/PackageKit/commit/e7d2a1080d5543ba447427634605a60ffb60ff8e">upstream</a>, and some <a href="https://github.com/hughsie/PackageKit/pull/199">are</a> <a href="https://github.com/hughsie/PackageKit/pull/200">proposed</a>. I don’t think any of the work we’ve done here is Ubuntu specific. These enhancements should benefit Debian users too, once the releases are uploaded there.</p><p>It’s been fun closing some of the gaps between Ubuntu and upstream. I hope we can continue to walk this path and improve the software management experiences further.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=447ddd70d3f9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Welcome]]></title>
            <link>https://medium.com/@iain.lane/welcome-16c91c0a71fb?source=rss-2e4866472bb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/16c91c0a71fb</guid>
            <category><![CDATA[gnome]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[ubuntu]]></category>
            <dc:creator><![CDATA[Iain Lane]]></dc:creator>
            <pubDate>Thu, 29 Jun 2017 13:30:37 GMT</pubDate>
            <atom:updated>2017-06-29T13:30:37.338Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p>I have another blog elsewhere on the interwebs, but I’ve created this one you’re reading now as a place to occasionally write about things I’m doing <a href="https://launchpad.net/~canonical-desktop-team">at work</a>.</p><p>I work at Canonical, on the desktop team. The team works on Ubuntu Desktop, publishing a release every six months containing the fruits of our efforts — or at least those ones that are ready enough for real people to use.</p><p><a href="https://insights.ubuntu.com/2017/04/05/growing-ubuntu-for-cloud-and-iot-rather-than-phone-and-convergence/">For the next release (out in October), we were given a big task</a>. Switch the desktop environment from Unity to GNOME Shell. Make the switch as smooth as possible for our users, but at the same time respect upstream’s design decisions. That sounds like a good thing: if you are led by the upstream team, then there should be less to change downstream, right? This is something that the Ubuntu Desktop has had a reputation for in the past.</p><p>There are some immediate wins here — some of the GNOME UX didn’t sit very well with Unity. A good example is <a href="https://developer.gnome.org/hig/stable/header-bar-menus.html.en">header bars</a> and menus. Unity had a global menu bar at the top of the screen, and latterly a switch to put those menus in the window’s title bar (so-called <em>locally integrated menus </em>or <em>LIM </em>for short). When a window is maximised, its title bar merges with the top menu to give you some more screen space. It is a <em>slick </em>part of Unity’s design, but it didn’t work very well with header bars. It’s not possible to merge them into the top bar, and their design made the applications look out of place. We (mainly Trevinho) tried hard to make them fit in, but there was a killer problem: what do you do when LIM is enabled? We’re supposed to show the menus in the application’s title bar in that case, but with header bars there <em>i</em>s no title bar, so no place to show the menus. We never solved that problem. Related to header bars, many GNOME applications also made changes to the way they provided menus, in most cases reducing them down to a top level item, which was in tension with Unity’s treatment of menus as important citizens. We worked with GNOME to develop features to allow applications to adapt their user interfaces if the desktop environment likes to show menus. In some ways it was a good example of collaboration, but in others — like creating multiple UIs that application developers needed to support to feel “native” in both GNOME Shell and Unity — it sucked. We tried create patches for applications to enable them to support these cases. Some upstream developers accepted these — thanks! — but others understandably didn’t want to maintain code they weren’t using or testing. So we were stuck with a bunch of patches to applications that didn’t look 100% awesome and were a bit of a pain to maintain. In the most annoying case we were maintaining a patch to add back a full menu structure that had been removed upstream. That means keeping up with feature changes and designing a logical way to lay out the menus, but doing this downstream. So it’s <em>great</em> that we get to remove this kind of patch now, and GNOME’s designers and developers will get to have their work delivered to Ubuntu’s users as they intended it to be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TXgsHELVnUj5hJPQiV5Frw.png" /><figcaption>Evince’s header bar converted to a toolbar in Ubuntu 16.04</figcaption></figure><p>There are also problems, though. There are a very large number of Ubuntu users that are used to the way that the Unity desktop works currently. We care very much about these users, and we want to ensure that they are happy with their desktop after we switch them over to GNOME. We can get a long way by admitting that there is a certain inevitable period of adjustment that users will need to go through. But there will be occasions when we in Ubuntu have a genuine disagreement with an upstream decision, and it’s tricky to know what the right thing to do there is. <a href="https://insights.ubuntu.com/2017/06/12/ubuntu-desktop-gnome-extensions-poll-results/">Take a look at the survey</a> conducted by Ken VanDine of the Canonical Desktop team. It is quite tempting to read the results of that survey, particularly where the views were tending strongly in favour of enabling particular extensions, as creating an obligation on us to implement the feature. But does it? The required next step, one that is currently ongoing, is to discuss the results with GNOME upstream and try to come to a resolution on each issue. In a lot of cases, even if the requested behaviour from Ubuntu isn’t completely agreed upstream, it will be possible to implement a setting that can be toggled downstream. In others where we diverge, though, it’s not clear to me what our response should be. Do we listen to the survey respondents and implement a feature that we couldn’t agree with upstream on — potentially irritating the upstream teams we are trying to build a good relationship with? Or do we disappoint those users that have expressed, sometimes quite clearly, their desire for a particular feature — even though we can say we lobbied on their behalf?</p><p>It looks like this is going to be the interesting release that reviewers have been asking for, but it’s not all on the surface. There are relationships to be built, and no doubt mistakes to be made along the way. See you at GUADEC to discuss these issues more.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16c91c0a71fb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>