I haven’t had time to deep dive but recently, Angelfish has been loading pages and (most) often immediately throwing up a certificate warning. Those certificates have all been legit. I wonder if we need some intermediary in the Angelfish build? @rinigus if you don’t have time, I could try to find some.
EDIT: this is running on the volla22 build. The stock browser will open the sites in question (and then crash 
As we focus on Qt6 right now, I prefer to spend time there. That should, if it will work, automatically bump Angelfish as well
Ok, got ya. It’s not a show stopper anyway, just odd. Still more stable than the 78 mozzila.
Not sure if it’s a problem with the package or Chum or SFOS package management in general, but Angelfish dependencies - all those opt- packages - don’t remove themselves after uninstalling it, which has caused problems during system upgrades 8they take up too much space in /opt).
It’s not ‘that’ much? I have 292.6M installed. But that wasn’t the issue. The certificate issue was intermittent.
EDIT: my system partition: /dev/mapper/system_a 7.6G 3.1G 4.4G 41% /
If you need to get rid of stuff you can always remove all ‘opt-qt5-*’ packages.
so, I started poking around and the question I had is, if I were to try to get v24.xx with qt6 running, I’m going to have to work around the name clash. Suffix/Prefix fix?
I would suggest that old Angelfish (5.15) would change the name (prefix?) and the new one will be just Angelfish. I expect that we all migrate to qt6 and opt-qt515 will stay only for legacy apps/platforms
Ok, to get started I could do a private package on obs and that shouldn’t produce any name collisions, or?
yes, that should be just fine