[revert to "open" - seems "incomplete" is for issues needing clarifications from original reporter blocking triaging of the issue at all, which is not the case here]

Closed due to lack of response from original reporter.

Closed due to lack of clarification from original reporter.

I will not try deduplicate this issue:
From a quick read, all the issues seems to have been discussed in the past in other issue reports. Obviously you might very well disagree on that (otherwise you wouldn't have invested your time in reporting it), so it needs a more careful examination which is better done by yourself.

I have a preliminary image with PureOS 10 for UEFI available, but some polishing work is still needed on this.

not a PureOS issue. Also, me_cleaner is pretty much dormant/dead

this can be closed, flashrom doesn't whitelist anymore

not a PureOS issue

Thanks for responding despite having moved on. Hope you enjoy whereever you've gone now :-)

I am not participating here since almost 2 years already.

Is this still an issue with current amber or byzantium branches of PureOS?

I take your word for it :-)

@nicole This sounds like your area of expertice...

Nope, not my department, that's @MrChromebox

I am fairly sure this has been fixed. @MrChromebox ?

@FaiscaOS Please create a separate issue report - even if it seems similar, there are many different wifi devices.

Nope, this is Coreboot, so if at all then @MrChromebox

This has been addressed in the Librem14 but we will not retr-fix this for the older L13 or L15, I'm afraid. Closing.

@nicole This sounds like your area of expertice...

@nicole This sounds like your area of expertice...

@nicole This sounds like your area of expertice...

@kakaroto Is this an issue with PureOS or the Librem laptops? If it is the latter then please track that somewhere at the Puri.sm Gitlab instead.

@kakaroto Is this an issue with PureOS or an issue with laptop hardware?

@kakaroto Is this still an issue?

@kakaroto Is this still an issue?

@kakaroto Is this still an issue?

That's four years old, I am fairly sure this has long been resolved.

@kakaroto and @nicole What is the status of this issue, and if wtill open then who is able to work on it?

Is this still an issue, now almost 4 years later?

@kakaroto is this still an issue?

According to https://tracker.pureos.net/T315#10888 this feature is unneeded and unwanted in PureOS.

This issue is likely solved in newer releases of PureOS. If not, please shout...

Is this still an issue with PureOS amber and/or byzantium?

This issue should be fixed with newer releases of PureOS. If not, then please shout...

Assuming this was a configuration error, not an issue in PureOS...

This issue was fixed with newer releases of PureOS.

Hopefully this issue was fixed with newer releases of PureOS. If not, then please shout...

Closed due to lack of response from original reporter.

sadly there can be no followup for this issue.