Ping Debian maintainer but otherwise go ahead with change in PureOS.

@mak, please make this bug your priority :)

yes, that package name sounds perfect!

@mak can you take pictures of our and the ordered module? Also mak can elaborate more as he has the one.
@stefannagy can you also attach images of module you ordered? Trisquel having something and Debian not is of interest to me (adding also @jonas.smedegaard to maybe try and track what is the difference).

@mak, go forward with this implementation so contributions and work of phone team becomes natural within pureos :)

PureOS never had Chrome package in its archive and Chromium is now removed and blocked as well.

Just installed and tried it, works here. Can you update your system and see if it works for you as well?

There is new OEM image in place, please open new bug if it doesn't work as expected.

Yeah, I did mean in collaborative way (aka ping the current maintainer, offer help etc). Thanks for noticing my not so good way of putting it out :)

what the...did you maybe enable multiarch on PureOS (aka adding 32bit packages/libs). Also what sources do you have enabled (did you add any sources on your own?).

@mak is it possible that we have a kernel mismatch now with new ISO?

@james.rufer are you still experiencing the issue?

I just tried and installation went fine for me so I can't reproduce this @chris.lamb can you reproduce it? Also @james.rufer can you try running sudo apt install --reinstall samba-common-bin and then try again installing the package?

eh, you can do it, I assigned it to mak as he was doing all previous uploads (the ones I recall) though assigning is not at all blocker for anyone else to do it so go ahead (also on contrary, if you see some assigned bug to other person but you can fix it, go ahead).

It should work just fine (be sure to turn off secure boot and uefi if possible inside your BIOS). In general if you can boot Debian testing main, PureOS should also work there.

Isn't this upstream issue? If yes we would really need to create upstream tag as there are some bugs popping up looking like that.

Unless someone ports it to Wayland we can't actually work on this :-/

is this an upstream issue and did you update your PureOS to latest available updates?

Installation via snap is currently of out of scope for PureOS (we can't and will not guarantee third-party repos as that is contrary to FSF rules of endorsement).

Chris, can you own this one? :)

As Jeff already stated, branding can't be added to PureOS (besides its own) itself but Purism can use its OEM image for such branding. I will put it on wishlist severity for now. Also making mak aware of it.

ah, my bad... we also got wifi chip from thinkpenguin that is suppose to work with bt but it actually doesn't (and @mak actually confirmed it is basically the same chip we use for our librems)

In T23#8320, @mladen.pejakovic wrote:

How did we miss to load this firmware :-/

Because it is a proprietary firmware.

@chris.lamb can you check this, as this is also the issue in upstream (Debian). How did we miss to load this firmware :-/

This could indeed be related to stripped firmware as the firmware we strip out (the intel nonfree firmware) indeed contain power management parts.

Coreboot splash screen (with Purism logo) provides that info. Are you using latest coreboot? Note that it is indeed fast in showing that but putting some higher timeout would annoy users who want fast boot :-/

Synaptic the package manager? Please attach the output from terminal once you launch it.
Also note that synaptic does not have (at least last time I checked) Wayland support nor do I know any effort to port it so it will most likely drop from archive in time.

@mak remove and block from re-entering the chromium package from archive as GNU-libre ML is pointing this out.

PureOS does not intend to add i386 at this point nor in future unless compelling reason is there as it takes engineering time to add an arch and maintain it. Someone could probably compile wine to use 64bit libs only (though I didn't test it and how limited usage would be).

Hi @chris.lamb,
can you fast-track if this fix is in Debian yet and if not package quick fix for PureOS (and also ping Debian maintainers about it). Coordinate with @mak to get this fix in ASAP as it affects our users a lot.

That is not a job of PureOS and this is PureOS tracker. Also PureOS is only 64bit and last time I checked, steam was still usually 32bit built so you would need plethora of 32bit libs.

Steam client is nonfree software so it will never be part of PureOS.

Freedom, security, privacy (and anonymity) that don't hamper everyday workflow or slow down to much is the philosophy.
I trust lamby will do adopt and do things correctly for our side.

@lamby, please take a look and debug this one.

is this an issue or just another thing that needs to be packaged?

Okay, tested engimail as well, it works now - so I think the culprit was apparmor! Closing this for now, it can be re-opened if someone sees same issue.

what about only CLI option of it or should we get someone to build a gtk version of it?

it was in apparmor mode (I disabled it, updated packages, rebooted, ran new fresh profile and not it seems to be working nicely, though I didn't test enigmail yet). I will continue to report here and I also remember that @james.rufer had similar issues as well. Also I noticed that by mistake thunderbird got apparmor profile again enabled in Debian and then again disabled so I assume we also are just waiting that update to flow in.

@davidrevoy is this as well fixed now?

Please feel free to open if you experience the bug still (though if you do this is probably an upstream bug).

is this still a relevant bug?

@davidrevoy is this bug still existing?

https://tracker.pureos.net/w/development/pureos_archive_layout/

@jeff did you test this?
also it has CLI. I think in any case we should add this to defaults as it seems quite usable (@mak ?)

is this still happening? @todd I know you also use evolution often, do you experience the same issues?

by default we now don't see grub (ULTRA FAST TURBO BOOT MODE THAT ROCKS YOUR WORLD) so I think we can happily close this bug :)

Mak, once you finish other high-priority tasks please implement this into our defaults. In meantime I would like others to try this patch and report here.

We needed your history logs from apt and system :)
Unless you have them somewhere saved we passed the time (PureOS being rolling release distro and not seeing other bug reports on this subject) we can close this one (and anyone can re-open if they still see the bug or have logs).

This image is not anymore in usage, please report new bugs for new image if they have issue.

This is how GNOME developers designed it as you can't really be sure a service/daemon got updated and properly works so it requires a reboot. This is aimed at less experienced users and updates aren't always booletproof. Anyway, this is upstream design atm - not really sure if we should change it (Windows does updates in similar fashion).