There is no other like Purism!
2 Likes
Still in alpha while Debian12 which it is based on is going to become “oldstable” soon.
2 Likes
Considering screenshot, is there a way I can help testing Crimson although I’m not expert? Maybe beta tester? I could download and install it and just use my L5 allowing Crimson to send to Purism all my logs and feedbacks so they can fix bugs.
I’d like to be useful for Purim and you Community.
Please let me know, thank you!
5 Likes
Do you mean how-to install this last development crimson on Librem 5?
3 Likes
Crimson_User_Page contains evil mobian logo by default. I know you love free(gratis) bug fixes, but small details will show the whole quality on the system. 
1 Like
Ay, there is - testing is always good, even if we’re no where near beta. And even if it’s not for devs, the community needs testing to see what are the changes and new features. And it’s a good way to pass the time, if you’re on a holiday
We had a testing with the previous images in January and I’ll set up a new thread and table for testing these new images too today, so we can collect observations to a more usable form. Any bugs should be reported to the mailing list.
5 Likes
Well, they have to go throught this step first and already have plans for going towards Dawn after it. That’s quite the speed up from previous, so there is a good chance that eventually PureOS will finally catch up to current (or at least close[er]).
8 Likes
I liked the Development Report a lot, like every month. It is great to read about the background work, have clear pointers to the milestones and upcoming work, and I learned more about what is patched and not.
Do not forget that this work is also accelerated by the totally optional PureOS subscriptions.
Many thanks to all who contribute, whether in developing, planning, donating or providing feedback.
And now off to see if I can install the new image on my secondary Librem 5…
10 Likes
You can use the Librem 5 reflashing procedure with the librem5-flash-image script to install the Crimson image.
In step 2 of the “Flash the system image” section, run the following instead:
- ./scripts/librem5-flash-image --stable
+ ./scripts/librem5-flash-image --dist crimson
By default, the script pulls from the current/latest images, which is Byzantium currently and the latest for Byzantium (2025.04). This is why the --dist crimson is needed and the other option defaults are okay.
5 Likes
I used this v5: ./librem5-flash-image --stable --variant luks --dist crimson
5 Likes
It’s the same thing as what I provided.
The script arguments have those as defaults.
--stabledefaults toTruewhen it is not provided.--variant lukshas a default value oflukswhen it is not provided.
4 Likes
The post states that it allows to use a numeric pin code as password again and while I agree that it can be more convenient to login, it’s very insecure given that this password might be the same to grant root access via sudo.
So is there actually any progress going on around mobile Linux to allow signing in via PIN but for example limiting retries to fallback for an actual secure password, separating PIN and password or some similar mechanism to improve security while offering this convenience?
Because this is really something that keeps bugging me using the Librem 5 daily. You either get one or the other, a proper password or a PIN and from my understanding mechanisms like signing in via fingerprint sensor should allow combinations like this as well, right?
3 Likes
I agree that this is a problem.
Another solution would be to take sudo access away from the purism user. This however would mean ensuring that all provided functionality still works under that condition and in practice would mean also first creating a separate account that does have sudo access.
Even with this though there is an argument that the lock screen ought to limit the number of attempts.
2 Likes
Ok I did it and it worked!! Thank you so much, Carlos (but also everybody else suggested me how to upgrade dist 
)
Please now could you kindly let me know how to activate feedback to Purism develop team? I want they receive all my feedbacks automatically but in anonymous so that they can fix bugs (alpha/beta tester) and I can do my little little part of help improving L5?
Thank you!! 
3 Likes
From old, the’ve requested that bugreports sent via mailing list, but if you are familiar of the process and get more involved, there is the actual dev system and the PureOS issue tracker, where you can make your reports (first is directly about the new Crimson, latter is a bit more broader). However, the registration to that may need you to contact the Purism team as automatic registration was closed due to spam. For more general testing, use the testing thread where you can report changes in behavior and features and edit the table yourself (good place to ask questions if your encountering odd behavior that you’re not sure is a bug).
Btw @JCS: The documentation text about this could be expanded a bit, to include more “how-to” and “tips on good/informative reports”. [This could have been a ticket 
]
4 Likes
Sorry, JR-Fi, I find your post a little bit confusing 
please where I can send to Purism development team my feedbacks?
For example: I installed Crimson and I’m trying to format my microsd card but when I open disk app and I try to “create partition”, a new window opens but it’s wider than L5 screen so I can’t tap window button (please see screenshot I attached here). I can’t solve it rotating L5! So I’m sure it’s a bug. How can report it?
Thank you
1 Like
Well, you can start by copying(or rather, moving) your previous message to the testing thread, so all issues in the forum are at least in one place and not among the conversations in this one. The mailing list, and the issue trackers all need you to sign up before you can post your issue there, so start with that [you can use any one of them]. There is a chance that serious issues are picked up from the forum thread as well (as devs occasionally visit here). In very serious cases you can also try support email, but that is not meant for this kind of feedback, so lets try to avoid flooding it.
The zoom size issue is unlikely serious and may go away after phosh is updated eventually. In the mean time you can try Mobile-settings app Compositor setting to that problematic app.
3 Likes
This is not even a bug which should be reported. It’s GNOME software and not PureOS. And it’s also nothing that is worse than Byzantium. However you can report it to GNOME Disk Utility repository (still a thing on Mobian).
More important to know are things like “is calling functional?” or “does W-Lan work properly?”, is there any stability issue … that kind of stuff is interesting in first place for Crimson release.
3 Likes
I would just do that on a desktop/laptop. Problem solved. Remembering to shut the Librem 5 down before removing or inserting a µSD card.
Evidently this particular application is not adaptive yet. You could report that but it is only one of many applications that are not adaptive yet, and it ought not to be the highest priority.
You may be able to work around this issue by scaling the screen. It may then be hard to read the screen but then at least you should be able to see the whole window and touch what you need to touch.
5 Likes
Once I reported that Nautilus doesn’t fit the screen, few weeks later GNOME devs have adjust this (we will get it with Dawn). So, they do their job very well. It’s just important to tell the true minimum size requirements (think about Phoshs top and bottom panel as well as the default 200% screen scale).
I’m sure other applications are also not up to date about this.
4 Likes