Librem 5 — painpoint assessment 2021

Glad to see this, although personally I will miss the mobile, wifi, and battery icons that currently display under the time on the lock screen. @guido.gunther

But since those are now kept visible in the notifications area, that’s cool.


Sadly, I wanted the actual battery percentage. The icons are relatively imprecise and of necessity rather small, better than nothing, but not what I was after.

If an actual percentage is not to be available then using colour to augment the icon would be helpful, although I understand that that is not a fully “accessible” design e.g. 0-19 red; 20-79 white; 80-100 green.

Ah, but in byzantium, you can now select “Show Battery Percentage” in the Power settings.

Time to upgrade, IW! :slight_smile:

Yes, I agree. It is becoming a problem. (In my defence, I’ve had other more serious and more pressing IT problems to deal with - and as a longer-time Librem 5 user, I have more to lose / more time needed than most from having to reflash. So it’s a double whammy.)


My manjaro pinephone just updated its phosh and the battery percentage on the lockscreen is a breath of fresh air.

1 Like

I recently reflashed from amber and was putting it off for a few months before doing so. I anticipated both a lengthy process and numerous issues along the way, but found neither.

I highly recommend using Angus’s update branch for the flash script described in this post. Successful Reflash to Byzantium

That branch takes care of two things.

  1. Updates the default encryption key for the luke partition.
  2. Resized the encrypted partition to the whole drive.

After flashing, restore your files, restart and enjoy what almost feels like a new device.


For me, it’s more about the extensive ‘configuration’ that I have done, all of which will have to be redone.


One thing I am wondering about is whether you get LUKS1 or LUKS2 as the end result. I think one really wants the latter but I have read in this forum (in other words, anecdotally) that you get the former.

So I would prefer to wait until that is ‘fixed’, if indeed there is something to fix.

Edit: @Kyle_Rankin can you shed light on what is the actual current situation?

Related discussion: Librem 5 - Unlock LUKS volume with a FIDO2 device

Is net data a premium in your part of the world? I’m wondering why you wouldn’t download an image and check for yourself. Then you’d have a first hand definitive answer rather than being dependent on others or any form of anecdotal murmuring.

Anyway, see image below, this is a header dump of the LUKS container from a LUKS variant Byzantium image, this is the (at time of writing) latest build…

If you’re holding out for these images to be available as LUKS2, you might be waiting for some time. It is possible to regenerate these images with a full LUKS2 container in fairly short time so I don’t think it’s worth holding out for Purism to provide LUKS2 directly. Depending on your machine specs, my one year laptop with NVME drive will create a LUKS2 variant from the original LUKS1 in around a minute, my very old entry level dual core machine with spinning rust will do it in around 12 minutes. It’s a relatively painless process.

I would still do the re-encryption before flashing to the phone, re-encrypting the live disk on the phone is not a problem but i can take some time (re-encrypting the container before expanding it is not too bad at just over 2 minutes, if you leave it until after expanding to fill the disk it’s a little over 16 minutes (assuming the phone is not doing anything else at the same time) re-encrypting on a desktop prior to flashing is around 17 seconds for me).

Data (quota) isn’t - but bandwidth is (in my very specific part of the world). So, no, I would not spend the time on a GB download just to get a one-bit answer that someone else already has.

… for whether Purism plans to change this, and if so when, can only come from Purism.

Lots of things are possible if you know how.

I’m not worried about how many minutes it takes to regenerate (12 minutes - 60 minutes - overnight is fine). I am more worried about the number of minutes of my time spent in this loop

* regenerate
* flash
* boot
* oh dear 😁
1 Like

humm, so they are shipping that to end users? As stable? Or as developer version?

As it was noted here:

That code is not yet finished.

1 Like

It came with a regular system update, but it’s manjaro (arch-based) so I suppose it’s a bit more bleeding-edge.

My point was that there was a specific request from the developers to distros of please not packaging that version because it was not yet complete :wink:

As in that has not yet been: finished nor released in an official version with a release tag.


Well… surprise!

1 Like

Bleeding-edge is fine, but Manjaro is often packaging our “experimental, with known issues, don’t use unless you’re a developer”-edge and shipping it to regular users…

Bug reports about top bar being visible on top of fullscreen apps incoming in 3… 2… 1… :stuck_out_tongue:


On the other hand, all the unwitting “testers’’” bug reports may help to some degree, I suppose…

1 Like

How did you solve this issue?

Thank you.

1 Like

If I remember correctly I had to set the keyring password once. Probably soon after first login. I set it to the same as my user password. The issue is not solved yet. I still have to provide the keyring password every time after first login after boot. One could ague that this is the correct behavior, because the login password and the keyring password are separate things.

Setting an empty password the keyring gets unloked at login without asking for a password … probably not the best from security point of view but much more convenient.

1 Like

Thank you very much!

Thank you :pray: