Upgrade to crimson?

Hi, I have a Librem 14 desktop computer.

I’m trying to install a specific software application. I was receiving errors during the installation so I got help from the software vendor. They told me the software requires libwebkit2gtk-4.1-0.
This is not the version in Byzantium so I would have to upgrade to crimson.

Are there instructions on how to upgrade from Byzantium to Crimson?

1 Like
1 Like

Clean installation:

  1. Download the Crimson image:
https://downloads.puri.sm/crimson/gnome/2024-05-10/pureos-11-gnome-live-20240510_amd64.iso
  1. Download balenaEtcher:
https://github.com/balena-io/etcher/releases/download/v1.7.9/balenaEtcher-1.7.9-x64.AppImage
  1. Using a freely available USB drive with at least 4 GB capacity, execute balenaEtcher, select the USB drive and Crimson image, then start the flashing process.
  2. After the process is done, boot the Live USB and install PureOS.

That is likely not to be recommended at this time - in two respects:

  1. Whether you should upgrade c.f. install from scratch.
  2. Whether you should run crimson at all.

AIUI crimson for the Librem 14 hasn’t been released yet. Maybe it works well. Maybe there are still some outstanding issues.

Don’t get sidetracked by posts talking about different hardware platforms. My understanding is

  • Librem 11 - crimson comes out-of-the-box and is required
  • Librem 5 - crimson is available as basically an α release i.e. crash test dummy
  • Librem 14 - search
  • Librem 16 - as yet unreleased product so I have no idea
  • other (13/15/Mini/Server) - no idea

Relating to the instructions for a clean install above, rather than an upgrade, I would add:

-1. Search in this forum for whether anyone is doing it and what their experience is like. Oh, and you would want to make damn sure that it does actually come with libwebkit2gtk-4.1-0 so best to ask someone who is already doing it whether that is in fact the case i.e. to check that for you. No point doing the upgrade only to find that it doesn’t solve the actual problem that you are trying to solve.

‌0. Image the disk before you start (for any major upgrade, whether “in situ” or re-install from scratch).

1 Like

See also: