Category Archives: Blog

We want what is dearest to you :)

Photo by Markus Spiske on Unsplash

Just a couple of days ago I had to let the community know that Axel, our dear friend and sponsor had passed way too early aged 51. After the shock faded, we realized that not only had we lost a friend, but also our sponsor that had made siduction sustainable for the past years. So now, after 10 years, we have to ask the community to carry the load and sponsor the project.

Setting up donations and sponsorship

In Germany, due to rules and regulations that we are famous for, it is quite cumbersome to set up to be able to collect donations, and it is also a lot of work to be done to keep it up. So, we have been looking for a service not unlike the well-known Patreon, but Open Source and with the option to allow one time donations and monthly backing. We decided to use Open Collective. We are still working on setting things up, but they are already functional. So, if your money is burning a hole in your pocket, you can already throw it in our general direction. We have set up two donation pages, one for Europe and one for the US. If you live in neither, choose what you prefer or what is closest to you.

What do we need money for?

We need to pay for two servers (web server and build server). Server cost at the moment is ~ $80 per month, which is too expensive. Both servers are oversized, and we will try to cut things down a bit to maybe $50. We also need funds to meet at least once per year at a Linux convention. Then there is the occasional need to either exchange broken hardware or supply hardware for a certain use case. We roughly estimate that we need $1.500 per year to keep the project up and running.

What does Open Collective do for us?

Open Collective has some nice features. For one, it takes care of everything for us, it eliminates the need to set up a charitable organization, takes care of taxes and the like. On the other hand it is fully transparent both ways. Anyone can see what comes in and what goes out and what it was spent for. There is not much to see on our page yet, but a good example can be seen on the Manjaro community page.

On the downside, if you want to call it that, they keep 10% of the money coming in to pay for their infrastructure and the services they offer. We think that is a fair trade-off for us, as we don’t have the time nor the nerve to deal with this any more than necessary.

With that, I want to thank all past and future donators and sponsors, Please stay safe and healthy in these dire times!

siduction 2021.1.1 »C-Blues« Point Release

To circumvent a bug that made the Calamares installer fail to create GPT partitions in EFI mode, we have released a siduction 2021.1.1 point release. For the technically inclined users among you let me dive into what happened behind the scenes of this bug. A new version 4.2 of dosfstools prevents kpmcore, which sits at the heart of KDE Partition Manager and gets utilized in Calamares, to create GPT partitions.

Dosfstools is to blame

Dosfstools no longer allows empty labels, but it also changed the way labels are reset. In the specific use case of creating a fat32 partition for the ESP, there is no label to reset as the partition does not exist yet. And so the installation fails, whereas if partitions are created before the installation and then pointed to in Calamares, things worked as expected.

Downgrade to the rescue

A fixed official version of dosfstools in the repositories will take a while, so we decided to downgrade dosfstools to 4.1.2, which resulted in the package dosfstools 4.2-1.1~really4.1-2. This point release is only important for fresh installs with Calamares. That is why noX did not get updated, it only has the cli-installer, no Calamares. Users, who have installed siduction already, don’t need to do anything.

Results of the Core Meeting

Photo by Levin on Unsplash

On the weekend we had a core meeting of siduction devs to talk about the future of the distribution. Proposed goals were the lessening of the workload, specialy for our main dev Alf (agaida) and more frequent releases. Other than that we had the revival of the siduction manual on the menu (which was in fact a fork of the excellent Bluewater Manual from the sidux days).

Lessen the workload

When it comes to lightening the workload, the only feasable way is to cut down on the number of images we produce. Reason for that is that some of the desktop enviromnents we ship have had no maintainer for a while. For the next release (which is not far away), we stop releasing images for the desktop environments GNOME, MATE and LXDE. That leaves us with images for KDE Plasma, Xfce, Cinnamon and LXQt. We also keep releasing the minimal entry points noX and Xorg.

That does not mean, users cannot use the desktops we dropped anymore. They are still available in the archives. We just stop customizing and producing images dedicated to them.

Advanced CI and CD

Besides that we will try to advance our Continuous Integreation and Delivery provided by Jenkins to churn out automated builds on a daily or weeky basis (no details decided yet) and make succesful builds available to our users. These builds will only be marginally tested, but we will make sure they boot correctly and the installer is in usable shape. These images will mostly work correctly, but are no replacement for the approved official releases. We have not yet decided, how these will be made available to you, but a dedicated forum section might be the easiest way.

Not a small feat

The siduction manual in it’s recent formfactor has been unmaintainable for a while now. Also some of the information in there is deprecated or needs to be adjusted. We plan to move the formfactor from (partialy badly written) HTML to Markdown (MD). Both of these tasks will have to be done manual and in conjunction in order not to move stuff to MD that will get kicked out afterwards. Once that is done, we will present the manual on a new platform that can turn MD into a visualy pleasing, easy to use and to maintain format. Volunteers wanted!

Artists in dire demand

Besided that we will be working on stabilizing the artwork in a way where it scales more correctly on all possible resolutions. Unless somebody with skills in the fine arts volunteers to supply us with artwork per release we will have to stick to what we are using now (which I find totaly acceptable) .

Contributors, step up

That being said, we have been keeping siduction rolling since 2011 with a small and more or less stable team and the support of you guys. What we would need is a stronger dev team to be able to work on new ideas and projects. So if you feel intrigued by working on the edge, come to IRC and talk to us. You do not need to be a software developer. We would love to have people with skills in art, translations, web-developement and maintainance, or just people with a passion for debian and siduction. We will for sure find something to do for you.

Last but not least we will try to get a booth at FROSCon 2019 in August, which is held in Siegburg, close to the German city of Bonn.

Core-Team Meeting in Berlin

Photo by Ricardo Gomez Angel on Unsplash

Tomorrow, on March 30, the siduction core team meets in Berlin to do some brain storming about the future of siduction. There will be five participants: Alf (agaida). Axel (ab), Torsten (towo), Markus (coruja) and me (devil). Topics will be a release plan that involves less work, a way to revive the manual in a different form factor and ways to spread siduction to more users.

Anyone that is in Berlin on the weekend is invited to join in. We will be at Coffee Fellows from 14:00 to ~ 18:00UTC/GMT +1 hour. There is an offfice space on the first floor, where you can find us. You can also participate via IRC in that time frame, if you have suggestions or questions for us. your link into our channels is on your desktop.

Next release plans

We are planning™ to release a full set of siduction images with all flavours before going to CLT (Chemnitzer Linux-Tage) next month. There are at least three reasons for that:

  • We can boast about it at the conference
  • We will have a new installer for you to try
  • We promised to do so

And here are the gory details: Six years ago we thought it would be a cool idea to have our installer running in a browser with the help of a tiny http server. Today for some reasons we do not think it is quite that cool. One of the reasons for that being the fact, that the guy who initialy wrote the installer is not available anymore.

Then, about three years ago someone by the name of Teo Mrnjavac had a marvelous idea, that will, similar to systemd, unify linux in a in my humble opinion positive way. I am talking about the Calamares Installer Framework. As you can see at the bottom of their webpage, your favorite distro is listed there already. It is used more and more by distributions and every one of them makes the code better. Sharing one installer eases a lot of problems for smaller distributions. The partitioning is done by KDE’s partition manager. What it does not do yet is LVM and RAID, but those are in the pipeline. Also, Calamares will make it’s way into Debian soon.

So for the past weeks that is what we have been working on. Calamares is C++, Qt 5 for the user interface and python modules to pick what you need and configure to your liking. Then apply a branding and you are done. Of course this was the fast-forward-mode, but we managed to get it up and running in less than two weeks. We are doing more testing to make sure it lives up to it’s reputation with siduction as well.

It also works fine with BIOS and UEFI, which kills another problem for us: The integration of UEFI in the old installer was far from perfect and included manual setup work before starting the installer. Given that we do not run into any blockers with the installer, we are confident that the freeze for Debian GNU/Linux 9 »Stretch« will allow us a release of all flavours without too many problems.

We also plan to make this next release our first release with 64-bit only. Yep, we think the time is right to drop the 32-bit plattform without making too many users unhappy. Should you be one of those not happy with our plan, please let us know your reasons on our forum. If you have a good reason to still run 32-bit, you might even be able to talk us into a custom build. But overall, dropping this architecture saves us a lot of time that can be better spent elsewhere.

Flatpak with siduction

Yesterday I wrote about how to install and use Snap to install the latest LibreOffice 5.3. I promised to do the same with Fedora/GNOME’s alternative package format Flatpak. Needless to say this also applies for pure Debian Unstable and Debian Testing installs. For Debian Jessie you would need backports enabled. For yesterdays post on Snap, the same goes for Unstable and Testing, whereas Jessie is left out in the rain for now.

Even though there is no flatpak for the latest version 5.3 of LibreOffice yet, we will install LO 5.2.5, which then can be updated to 5.3 in a few hours or days. Setting the base framework for flatpak is a little more work as you have to install the basic runtime (at least on a KDE system, maybe it comes automaticaly with a GNOME install. OK, lets get started withthe package itself:
# apt install flatpak
Now we need to get the runtime:
$ wget
$ flatpak remote-add --user --gpg-import=gnome-sdk.gpg gnome
$ flatpak install --user gnome org.gnome.Platform 3.20

Now you can download the flatpak package for Libreoffice from the Flatpak-Apps page. Move to the directory where the download landed and install it:
$ flatpak install --user --bundle LibreOffice.flatpak
When that is done, you can start LO from the same directory by running:
$ flatpak run org.libreoffice.LibreOffice

Updates can be performed by running:
$ flatpak update --user org.libreoffice.LibreOffice

These alternate packaging formats are ideal for installing software that is not (yet) available in your distribution or versions not yet available, like LO 5.3 in our example. Developers can install different versions of a software that do not interfer with each other for testing. Which one of the new self-contained package formats (there is also Appimage) you prefer is totaly up to you. They offer a sandboxing model that is supposed the keep them separated from the environment. In the case of Flatpak they can talk to each other by means of Flatpak Portals.

Snaps with siduction

I am sure, everyone has heard about Ubuntu’s new package format snap by now. Today I wanted to try the brand new and still hot off the press LibreOffice 5.3 for a review. So I found that the Document Foundation had a snap ready for deployment. The prerequisites for siduction are not many:
# apt update && apt install snapd
After that, you can check, which snaps are avaialable for LibreOffice with:
$ snap info libreoffice
As you can see, the new version 5.3 is in the edge-channel. That is all you need to know to install it with:
# snap install libreoffice --channel=edge
Afterwards a repeated
$ snap info libreoffice
will reflect the installed packages. As you might have a version of LibreOffice already installed through your package manager, you will need to start the snap, using the full path:
$ /snap/bin/libreoffice &
Later on you can refresh them with
$ snap refresh libreoffice

Just a day or two ago, the first snaps of KDE apps turned up in the KDE-Store Tomorrow I will give flatpak, the alternative new package format by Fedora a try with libreoffice. You can read the results here tomorrow

New fast siduction mirror in the US

As of today we are happy to share with you a new mirror in the United States. It is located at Princeton University and should be our fastest mirror in the US.
The URLs are:

  • Princeton University
    deb unstable main
    deb-src unstable main
    deb unstable main contrib non-free
    deb-src unstable main contrib non-free

  • Direct links are to be found on our website.
    Please let us know if any problems arise.

    Structural changes coming up

    As you may have sensed by now, we are having problems this year getting out a proper release of the desktop environments we ship. There is more than one reason for that. For one it was really hard to get things in shape for a release. KDE for example was in heavy developement most of the time. Now that we have Plasma 5.8.x with longtime support, things settle down a bit and we will hopefuly get a release of that flavour out until the end of the year. GNOME and Cinnamon are also in steady movement, Xfce and MATE don’t move that much.

    On the other hand the time that siduction team members have at their hands have lessened over time. Speaking for myself, my workload has grown a lot during the past two years. Another team member joined a team that took on the job to bring LXQt in shape and into Debian (and they succeeded). A third team member got himself a job whereas before he was unemployed for some time (and of course we are happy for him). All these constraints make it harder to achieve our goals of releasing siduction in the way we did until now. That does not mean in any way that siduction is unmaintained. We steadily work on it as is needed and try to guide you through shallow waters. Just the big tasks like releases get left behind.

    There were no new contributors joining the team, so that does not help either. So we have come up with an idea that will lessen our workload a bit. The idea is for flavour maintainers to determine when a flavour is good and ready for release. We know in advance what is going to happen in critical flavours and if there is transitions or other big changes coming up, that might brake things. So, e.g. when KDE seems in good shape to be released to the public, so may be another flavour. Then those two could go out as a snapshot. Possibly a month later some other flavours are good to go.

    We found a long time contributor, who is willing to manage these kind of releases. That means checking if the flavour(s) are in releasable shape, coordinate a release and ship them on their way to you. That will help us and our users. You as a user get fresher snapshots as entry points to the distribution, which also attracts new users. For us as the team behind siduction it raises the visibility of the distribution, which also attracts new users and maybe even contributors. So we will give this a try and see how it goes. Like I said before, we hope to get results out before the end of the year.

    One other thing that is in dire need of love is our manual. Once a wealth of knowledge, it is now vastly aging and mostly unmaintained. The way it is technicaly set up makes it hard to contribute to and very unwieldy for us to maintain the infrastructure. There is two things to do here: We need to do the heavy lifting of transferring the content to a multilingual wiki like MediaWiki. We have languages in the manual, that are totaly unmaintained because noone in the team speaks the language (nor has the time) to work on these. Those languages are Portugese, Italian, Romanian, and Polish. We still need to decide what to do with them. Right now they are counterproductive because in parts they are by now plain wrong or misleasing. My idea is to archive them until maybe someone later picks up a language.

    The second task is to go over all German and English items in the manual and correct them where needed and bring them up to current, also write new ones (e.g. for systemd). All this needs manpower. So if you would like to help with any of this, you are very welcome, please reach out to us on our forum or on IRC on the OFTC network in #siduction-core. Working over the manual can be done as your time allows, there is no ETA to this. We are also always looking for artists. This is also a commitment that does not take up much of your time, it is mostly about creating an icon here and there.

    Debian fell over

    With systemd 230, released a couple of days ago, the developers changed a default setting, that eliminates one of the few annoyances I experienced with systemd. Many a forum thread all over the net tried to solve the problem. This annoyance resulted in a message during reboot or shutdown, that the system is waiting for a process to shut down. This could take up to 90 seconds, if you did not set the level lower manually. These were stray background processes, that belonged to one or more users on the system and should have been shut down, when the owning user gets logged out.

    The systemd developers with systemd 230 set the option KillUserProcesses in /etc/systemd/logind.conf to yes. That means that 95 percent of desktop users will not see these delays anymore, because all processes of a user will be closed when the user gets logged out. On the other hand, users of tools like screen, tmux and some others will find their processes also killed server-side, even though these were meant to be long-running background jobs. That being said, the devs did explain in the release note for systemd 230 under the third bullet, what users of such tools need to do to keep KillUserProcesses on yes and still have their long-running jobs stay alive. The problem at hand was being layed out in detail in a bugreport and it’s follow-up discussion already in April.

    In Debian and Fedora this new behaviour led to long discussions (and the usual systemd laments of course). The bug report for Debian on this matter now led to the new standard setting being reverted in Debian with systemd 230-2 as of today. So, if you like your processes being stopped when your user logs out, you need to manualy revert the setting in /etc/systemd/logind.conf to yes again after updating to systemd 230-2. We decided months ago to have this set to yes as default for siduction. This will take effect with our next release. But if you want to set this to yes now, you need to do so yourself.

    Should you be one of the users of screen, tmux, mosh and maybe a few other affected tools, there is ways to keep the setting at yes and still keep long running processes alive when logging out. You need two things to do this: first you set enable-linger [USER1 USER2...] for your respective users, as shown in the manpage to loginctl. PAM has been adapted to allow this as normal user. Then you can follow the manpage of systemd-run to start e.g. screen with the command systemd-run --scope --user screen in it’s own scope. This will keep the job running after logout, even though other user processes are stopped.

    We admired Debian for deciding pro systemd, but we think, reverting this new default is the wrong decision in the face of desktop users.