Time to fly off to the sun to meet KDE friends old and new and plan out the next year of freedom fighting. See you in Almería!
Time to fly off to the sun to meet KDE friends old and new and plan out the next year of freedom fighting. See you in Almería!
ISO Image Writer is a tool I’m working on which writes .iso files onto a USB disk ready for installing your lovely new operating system. Surprisingly many distros don’t have very slick recommendations for how to do this but they’re all welcome to try this.
It’s based on ROSA Image Writer which has served KDE neon and other projects well for some time. This adds ISO verification to automatically check the digital signatures or checksums, currently supported is KDE neon, Kubuntu and Netrunner. It also uses KAuth so it doesn’t run the UI as root, only a simple helper binary to do the writing. And it uses KDE Frameworks goodness so the UI feels nice.
First alpha 0.1 is out now.
Download from https://download.kde.org/unstable/isoimagewriter/
Signed by release manager Jonathan Riddell with 0xEC94D18F7F05997E. Git tags are also signed by the same key.
It’s in KDE Git at kde:isoimagewriter and in bugs.kde.org, please do try it out and report any issues. If you’d like a distro added to the verification please let me know and/or submit a patch. (The code to do with is a bit verbose currently, it needs tidied up.)
I’d like to work out how to make AppImages, Windows and Mac installs for this but for now it’s in KDE neon developer editions and available as source.
The Plasma team had a mammoth 2.5 hour meeting to discuss some of the aspects of the Plasma releases going forward. Much of the debate was around when to do an LTS release and we’ve gone with Plasma 5.12 due in January. There will continue to be a couple of 5.8LTS releases in 2018 and more as necessary. We’re picking up 5.12 as an LTS at the request of openSUSE who wanted it for their next Leap release. We also banned new features which might affect the Wayland port unless they’re already functional in Wayland. Here’s the full list.
There’s another election on Thursday called by a prime minister who thought she could increase her small majority in parliament and see off her rivals who will oppose her. Except that’s politics, you have an opposition. Theresa May’s dictatorial instinct has got worse during the campaign and she is now talking about removing human rights and banning encryption. She was home secretary for 6 years, in charge of MI5, GCHQ and English police, she has taken zero responsibility for the attacks that happened recently nor made the more valid point that there is nothing you can do to stop a determined person driving a van into people.
She was incharge of GCHQ which catalogues vulnerabilities in Windows and works with the NSA who create viruses used to attack systems in Iran (and probably elsewhere). These viruses were used to blackmail everyone in the UK by blocking our health records and other systems. There has been no political fallout from this which I’m astonished at. The responsibility lies with Theresa May and she’s getting away with her incompetence.
But this election is primarily about one issue so important it has created its own ugly word, Brexit. Our freedoms will be taken away. I should have the freedom to go to Barcelona and Guadeloupe just as I would to Glasgow or London. That will be removed. All the political parties have let us down by letting the isolationist nationalism of Brexit persuade people that somehow removing freedoms and mis-aligning regulations will improve their quality of life. It will not. Paperwork will increase, taxes will go up to pay for the bill, rights will be removed. None of the parties have even vaguely said how they will pay for the EU bill or get their magic free-trade deal or why that’s a good thing without the necessary regulation.
The SNP is the only party offering a realistic alternative to Brexit. An independent Scotland would continue with a strong relationship with rUK and the EU same as Ireland can. We need a referendum and I’m looking forward to it. London will try to block it in an undemocratic repressive move, a sign of things to come under a Tory government.
Labour want a hard Brexit same as the Tories. They want to waste money on vanity projects like nuclear bombs same as Tories. It is very pleasing to see the English get a genuine economic alternative for the first time in my adult life. But it doesn’t forgive for their destructive Brexit nationalism.
The Lib Dems have the nonsense situation of wanting a second referendum on EU membership but not on Scottish independence. They were government for 5 years in charge of GCHQ organising mass surveillance. They aren’t liberal or democratic.
And the Greens don’t have a hope to win and will just split the vote. The nonsense first-past-the-post system doesn’t make it sensible to vote for them (or ‘us’, I’m a member).
The Tories will win in the UK. The SNP will win in Scotland. The Tories will claim the SNP doesn’t have a mandate for a referendum despite already having one and everything will get very Catalan. Ara es l’hora.
Modern elections are weird, they are won by spending thousands and millions on Facebook adverts which can target swing voters in swing constituencies. The party (or referendum campaign) with the most money can buy the most adverts and wins. Except for the SNP who win by offering the best choice, we can be proud of that.
One of the best things about making software collaboratively is the translations. Sure I could make a UML diagramming tool or whatever all by my own but it’s better if I let lots of other people help out and one of the best crowd-sourcing features of open community development is you get translated into many popular and obscure languages which it would cost a fortune to pay some company to do.
When KDE was monolithic is shipping translation files in separate kde-l10n tars so users would only have to install the tar for their languages and not waste disk space on all the other languages. This didn’t work great because it’s faffy for people to work out they need to install it and it doesn’t help with all the other software on their system. In Ubuntu we did something similar where we extracted all the translations and put them into translation packages, doing it at the distro level makes more sense than at the collection-of-things-that-KDE-ships level but still has problems when you install updated software. So KDE has been moving to just shipping the translations along with the individual application or library which makes sense and it’s not like the disk space from the unused languages is excessive.
So when KDE neon came along we had translations for KDE frameworks and KDE Plasma straight away because those are included in the tars. But KDE Applications still made kde-l10n tars which are separate and we quietly ignored them in the hope something better would come along, which pleasingly it now has. KDE Applications 17.04 now ships translations in the tars for stuff which uses Frameworks 5 (i.e. the stuff we care about in neon). So KDE neon User Editions now include translations for KDE Applications too. Not only that but Harald has done his genius and turned the releaseme tool into a library so KDE neon’s builder can use it to extract the same translation files into the developer edition packages so translators can easily try out the Git master versions of apps to see what translations look missing or broken. There’s even an x-test language which makes xxTextxx strings so app developers can use it to check if any strings are untranslated in their applications.
The old kde-l10n packages in the Ubuntu archive would have some file clashes with the in-tar translations which would often break installs in non-English languages (I got complaints about this but not too many which makes me wonder if KDE neon attracts the sort of person who just uses their computer in English). So I’ve built dummy empty kde-l10n packages so you can now install these without clashing files.
Still plenty to do. docs aren’t in the Developer Edition builds. And System Settings needs some code to make a UI for installing locales and languages of the base system, currently that needs done by hand if it’s not done at install time (apt install language-pack-es). But at last another important part of KDE’s software is now handled directly by KDE rather than hoping a third party will do the right thing and trying them out is pleasingly trivial.
I did a day’s training at the FLOSS UK conference in Manchester on Chef. Anthony Hodson came from Chef (a company with over 200 employees) to provide this intermediate training which covered writing receipes using test driven development. Thanks to Chef and Anthony and FLOSS UK for providing it cheap. Here’s some notes for my own interest and anyone else who cares.
Using chef generate we started a new cookbook called http.
This cookbook contains a .kitchen.yml file. Test Kitchen is a chef tool to run tests on chef recipes. ‘kitchen list’ will show the machines it’s configured to run. Default uses Virtualbox and centos/ubuntu. Can be changed to Docker or whatever. ‘kitchen create’ will make them. ‘kitchen converge to deploy. ‘kitchen login’ to log into v-machine. ‘kitchen verify’ run tests. ‘kitchen test’ will destroy then setup and verify, takes a bit longer.
Write the test first. If you’re not sure what the test should be write stub/placeholder statements for what you do know then work out the code.
ChefSpec (an RSpec language) is the in memory unit tests for receipes, it’s quicker and does finer grained tests than the Kitchen tests (which use InSpec and do black box tests on the final result). Run with chef exec rspec ../default-spec.rb rspec shows a * for a stub.
Beware if a test passes first time, it might be a false positive.
ohai is a standalone or chef client tool which detects the node attributes and passes to the chef client. We didn’t get onto this as it was for a follow on day.
Pry is a Ruby debugger. It’s a Gem and part of chefdk.
To debug recipes use pry in the receipe, drops you into a debug prompt for checking the values are what you think they are.
I still find deploying chef a nightmare, it won’t install in the normal way on my preferred Scaleway server because they’re ARM, by default it needs a Chef server but you can just use chef-client with –local-mode and then there’s chef solo, chef zero and knife solo which all do things that I haven’t quite got my head round. All interesting to learn anyway.
Twitter seems ever dominant and important for communication. Years ago I added a microblogging feed to Planet KDE but that still needed people to add themselves and being all idealistic I added support for anything with an RSS feed assuming people would use more-free identi.ca. But identi.ca went away and Twitter I think removed their RSS ability but got ever more important and powerful.or the relaunched theme a couple of years ago we added some Twitter feeds but they were hidden away and little used.
So today I’ve made them show by default and available down the side. There’s one which is for all feeds with a #kde tag and one with @kdecommunity feed. You can hide them by clicking the Microblogging link at the top. Let me know what you think.
Update: my Bootstrap CSS failed and on medium sized monitors it moved all the real content down to below the Twitter feeds rather than floating to the side so I’ve moved them to the bottom instead of the side. Anyone who knows Bootstrap better than me able to help fix?
I’ve also done away with the planetoids. zh.planetkde.org, fr.planetkde.org, pim.planetkde.org and several others. These were little used and when I asked representatives from the communities about them they didn’t even know they existed. Instead we have categories which you can see with the Configure Feed menu at the top to select languages.
I allowed the <embed> tag which allow for embedding YouTube videos and other bits. Don’t abuse it folks 🙂
Finally Planet KDE moved back to where it belongs: kde.org. Because KDE is a community, it should not be afraid of its community.
Let me know of any issues or improvements that could be made.by
Boudhayan Gupta dropped by for the final day of the Plasma Sprint because he had 3D printed that save icon and wanted to test it. Coincidently I found a treasure in the glove compartment of my dad’s car, a Eurythmics Greatest Hits audio CD.
So how does KDE applications do for legacy media? Mixed results.
Dolphin works even if it does report it as a 0B media [Update: fixed by the awesome Kai Uwe]
However classic KDE tool KFloppy less so, it hard codes locations in /dev to find the floppy but my USB floppy drive just appears at /dev/sdc, even one I fixed that it uses an external tool which breaks fdformat.
Meanwhile CDs are also something we ship apps for but never test. This makes the Plasma Sprinters sad because they desperately want to hear Love Is a Stranger.
kio-audio CD didn’t work but then when we looked at it again it worked perfectly, don’t you hate when that happens? This was a killer feature of KDE back when everyone was ripping CDs to their hard disk for the first time.
Playing Audio CDs natively less successful, Amarok shows it as a source but says it has 0 tracks. Dragon plays it fine but Dragon has no concept of a playlist so you can’t select a track. kscd works but is a perfect example of why skins and client side window decorations are a bad idea because it still looks like it did years ago.
We also tried k3b which works for making a new audio CD but doesn’t let you add files to a data project (bug 375016) so shouldn’t be released quite yet. [Update: also fixed by Kai Uwe, what a useful chap.]
Where else does KDE support legacy formats that need checking up on?
The KDE neon Docker Images are the easiest and fastest way to test out KDE software from a different branch than your host system.
Coming live from the Plasma Sprint sponsored by Affenfels here in Stuttgart, the KDE neon Docker images now support Wayland. This runs on both X and Wayland host systems. Instructions on the wiki page.
Below you can see my host system running Plasma 5.9 on X is running Plasma master with Wayland.
Hugs to David E.by
We’ve had a busy weekend at FOSDEM in Brussels for the last two days and now I’ve travelled into my fifth country of the trip picking up a few hackers on the way for the KDE Plasma Sprint which is happening all this week in Stuttgart, do drop by if you’re in town.by
When you download a KDE neon ISO you get transparently redirected to one of the mirrors that KDE uses. Recently the Polish mirror was marked as unsafe in Google Safebrowsing which is an extremely popular service used by most web browsers and anti-virus software to check if a site is problematic. I expect there was a problem elsewhere on this mirror but it certainly wasn’t KDE neon. KDE sysadmins have tried to contact the mirror and Google.
You can verify any KDE neon installable image by checking the gpg signature against the KDE neon ISO Signing Key. This is the .sig file which is alongside all the .iso files.
gpg2 --recv-key '348C 8651 2066 33FD 983A 8FC4 DEAC EA00 075E 1D76' wget http://files.kde.org/neon/images/neon-useredition/current/neon-useredition-current.iso.sig gpg2 --verify neon-useredition-current.iso.sig gpg: Signature made Thu 19 Jan 2017 11:18:13 GMT using RSA key ID 075E1D76 gpg: Good signature from "KDE neon ISO Signing Key <firstname.lastname@example.org>" [full]
Adding a sensible GUI to do this is future work and fairly tricky to do in a secure way but hopefully soon.by
You voted for change and today we’re bringing change. Today we give back the installer to the people. Today Calamares 3 was released.
It’s been a long standing wish of KDE neon to switch to the Calamares installer. Calamares is a distro independent installer used by various projects such as Netrunner and Tanglu. It’s written in Qt and KDE Frameworks and has modules in C++ or Python.
Today I’ve switched the Developer Unstable edition to Calamares and it looks to work pretty nicely.
However there’s a few features missing compared to the previous Ubiquity installer. OEM mode might be in there but needs me to add some integration for it. Restricted codecs install should be easy to add. LUKS encrypted hard disk are there but also needs some integration from me. Encrypted home holders isn’t there and should be added. Updating to latest packages on install should also be added. It does seem to work with UEFI computers, but not with secure boot yet. Let me know if you spot any others.
I’ve only tested this on a simple virtual machine, so give it a try and see what breaks. Or if you want to switch back run
apt install ubiquity-frontend-kde ubiquity-slideshow-neon''.
Google Code-in has just finished where school pupils do tasks to introduce themselves to open development. I had one to update the screenshots on www.kde.org. The KDE website is out of date in many ways but here’s a wee way to fix one part of it. Despite me having about half a dozen students work on it there’s still some old screenshots there so if anyone wants the satisfaction of contributing to www.kde.org’s front page here’s an easy way.
www.kde.org has screenshots of all our apps but many still use the old KDE 4 Oxygen widget theme and icons.
For 10 screenshots which is using the old theme take a new screenshot using the new theme.
They can be checked out from Subversion here https://websvn.kde.org/trunk/www/sites/www/images/screenshots/ also provide one the resized screenshot which is 400 pixels wide exactly.
Keep the filenames the same and in lower case.
Upload as a single .zip or .tar.gz containing the screenshots with the right file name and a folder resized/ with the 400px screenshots
Plasma is nearing a new release and with 5.9 coming shortly we have the question of should we switch Neon to use Wayland by default for the Developer Unstable edition. To evaluate it I updated the Plasma Wayland ISO and found it pleasingly functional on VirtualBox. Time to install this setup on my real hardware and see what breaks.by
KDE Plasma 5.8 is designated an LTS edition with bugfixes and new releases being made for 18 months (rather than the normal four months). This will please a category of user who don’t want new features on their desktop but do want it to keep working and bugs to be removed. Because Neon aims to service Plasma and its users in every way we have now created the KDE neon User LTS Edition.
This comes with Plasma 5.8 LTS, updated for new bug fix releases (e.g. 5.8.5 is out at the end of this month) and will not change to Plasma 5.9 when they becomes available. A common critisism of LTS editions is that it just means users get old versions with known bugs. KDE neon User LTS Edition comes with the latest KDE Applications and it comes with the latest KDE Frameworks release and Qt 5.7, so all the KDE software we ship is the latest stable version. Along with other KDE neon editions we’ll also ship the HWE updates for Linux and Mesa when they become available.
For those interested in archive details it’s
deb http://archive.neon.kde.org/user/lts xenial main
Switching from User Edition to User LTS Edition archive is unsupported but will likely work.
A recent Reddit post gave some pleasing feedback about KDE neon, allow me the indulgence of picking some pleasing quotes from it:
I feel like the KDE neon team has done such a great job with an out-of-the-box experience with this distro that it feels insanely polished.
Jep, I’m even using KDE neon at work. I’ve been able to simply focus on my tasks, and not worry about troubleshooting the OS.
KDE neon cured my distro hopping as well.
KDE neon is the bee’s knees.
Anyone else feel this last should become an official marketing slogan?by
Last month we moved the neon archive to a new server so packages got built on our existing server then uploaded to the new server. Checking the config it seemed I’d made the nasty error of leaving it open to the world rather than requiring an ssh gateway to access the apt repository, so anyone scanning around could have uploaded packages. There’s no reason to think that happened but the default in security is to be paranoid for any possibility. The security advisory is out, the archives have been wiped and all packages in User rebuilt so upgrade now to get the new package builds, or for extra security do a reinstall. The new User Edition ISO is out and I’ll update the website once that gets mirrored enough. Developer Editions packages are being rebuild now and go directly into the archives so you should start seeing those appear shortly as they are built. Sorry for the hassle folks, you wouldn’t want us to just hide it I’m sure.
Appstream has had a long history of getting its very sensible features into the hands of users. It’s an XML format which describes applications so that projects such as KDE can ship files with their apps which give a name, description, translations of this and pretty screenshots.
The first step is getting the Appstream metainfo files into the applications. KDE has this in many places but not all, if you spot an application please add one. It’s been supported in Extra CMake Modules for a while but the install directly changed recently just to confuse matters.
Then your archive has to extract the appstream files, in Neon we use Appstream Generator written by the Appstream master Matthias Klumpp and Harald set up some time ago but it broke last month. That meant we had to update to a new version so Scarlett had to add a load of new packages to Neon to get Appstream Generator to build and I had to work out how to debug D to convince it to work. Then we moved our archive to a new server for space and because it was fun so parts of the job which runs it had to been rewritten to work remotely. Finally there’s a pesky bug which means it looks at the oldest package not the newest one so any problems with the Appstream files stay around forever. So for now I deleted old packages.
So at least you can install Minuet from Discover, it gained an appstream file back in 16.04 but it was broken so we had to wait for 16.08 to get a working one.
But wait, this infrastructure for package managers is fiddly. Discover is showing the most popular installed app as Dilbert cartoons, which makes no sense. Turns out the popcon data for applications is made using fancy Docker scripts on an obscure server we’ve largely forgotten about but Cron doesn’t like Docker and doesn’t let it output anything when running even though the same command works fine when run manually. So I regenerated the popcon data manually in the hope we can work out how to cron it later on. And finally Discover is back showing popular apps and all the latest ones at that. Sorry for the delay folks.
Getting it to work in Neon developer editions is future work I fear.
KDE neon has now, using the latest containerised continuous integration technologies released KDE1 neon Docker images for your friendly local devop to deploy.
Give it a shot with:
apt install docker xserver-xephyr
adduser <username> docker
<log out and in again>
Xephyr :1 -screen 1024×768 &
docker pull jriddell/kde1neon
docker run -v /tmp/.X11-unix:/tmp/.X11-unix jriddell/kde1neon
(The Docker image isn’t optimised at all and probably needs to download 10GB, have fun!)by
Plasma 5.8 LTS has been released, it’s time now to look again at Plasma’s comprehensive features. Chris From the Linux Action Show voiced our Plasma 5.8 video so you can review the comprehensive features we’ve been polishing for the last couple of years and the shiny new ones in this release to make a desktop we’re proud to advocate to enthusiasts, home users, businesses and developers alike.
The KDE neon builders have been firing away this afternoon and Plasma 5.8 LTS is now available in the User Edition archive. If you don’t already have KDE neon installed you can grab the latest User Edition ISO to install it on your hard disk.
A feature I’ve been wanting for ages in KDE is the ability to install plugins from within the application. This was made more urgent when we added Gwenview in KDE neon and had to choose between either an empty Plugins menu or adding a dependency on Kipi Plugins which brought in Konqueror and several KDElibs 4 tools.
So I got round to coding the feature based on discussions I’d had previously and work on the Samba browser in Dolphin I’d done before. Using Packagekit and Appstream libraries directly to find the package and install it. But some reviewers convinced me to use an external app to care about the install. So now all Gwenview does it launch the Appstream URL and wait until a plugin gets installed. In Plasma’s case that means Discover starts up and uses Packagekit or whatever backend it’s set up with to install Kipi Plugins. A nice bit of integration there. Future work would be to put this functionality in Kipi Plugins directly so all apps can use it without much effort. Where else can KDE apps benefit from being able to install addons within the app?