Thanks for clarifying.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
May 29 2021
Thanks for clarifying.
Thanks for clarifying.
May 28 2021
Closing as invalid: Impossible to investigate further when not even original reporter knows what concretely to investigate.
What I meant to say above is that "incomplete" to me makes sense for an issue actionable only by original reporter.
Closing as "invalid", by the reasoning that an issue unreproducible even by original reporter is not actionable.
@MrChromebox Is this still an issue, and is it tied to PureOS?
@MrChromebox Is this an issue, and is it tied to PureOS?
@MrChromebox Do you know if this is still an issue, and if it is tied to PureOS or (as it seems to me) to Purism firmware flashed onto laptops and possibly published directly by Purism as package as well but not shipped with PureOS)?
thanks for the clarification - tagging accordingly.
Seems nothing is incomplete here...
Assuming this issue is solved with a) using newer PureOS and b) only using PureOS.
Purism has abandoned the development of PureBrowser for some time now.
Purism has abandoned the development of PureBrowser for some time now.
Purism has abandoned the development of PureBrowser for some time now.
Purism has abandoned the development of PureBrowser for some time now.
@joao.azevedo this issue is hexchat hardcoding a specific web browser - and therefore not specific to PureBrowser (that's just how it was noticed).
Purism has abandoned the development of PureBrowser for some time now.
Purism has abandoned the development of PureBrowser for some time now.
Purism has abandoned the development of PureBrowser for some time now.
Purism has abandoned the development of PureBrowser for some time now.
Purism has abandoned the development of PureBrowser for some time now.
Purism has abandoned the development of PureBrowser for some time now.
Purism has abandoned the development of PureBrowser for some time now.
Purism has abandoned the development of PureBrowser for some time now.
Purism has abandoned the development of PureBrowser for some time now.
Closed due to lack of response from original reporter.
Purism has abandoned the development of PureBrowser for some time now.
Purism has abandoned the development of PureBrowser for some time now.
Purism has abandoned the development of PureBrowser for some time now.
Purism has abandoned the development of PureBrowser for some time now.
Purism has abandoned the development of PureBrowser for some time now.
Purism has abandoned the development of PureBrowser for some time now.
Purism has abandoned the development of PureBrowser for some time now.
Also on a related note, Purism has abandoned the development of PureBrowser for some time now.
Please (if still an issue now several years later) report that other issue as an independent issue report. Thanks.
Purism has abandoned the development of PureBrowser for some time now.
Purism has abandoned the development of PureBrowser for some time now.
Purism has abandoned the development of PureBrowser for some time now.
@adfeno I notice you mention lack of help examining, and also that you rely on licensecheck for your examination.
Purism has abandoned the development of PureBrowser for some time now.
@stefannagy I can confirm that GOA lacks generic support for CalDAV/CardDAV - it is confusing that they provide support for one specific CalDAV/CardDAV-based service (by hardcoding URIs instead of following the specs to RESTfully resolving them) which is certainly not the same.
We've settled in T553 on tracking all supported releases - i.e. both stable (currently amber) and development (currently byzantium).
So please keep this issue open until we decide to no longer support amber (or close if this specific issue is considered irrelevant for amber).
May 27 2021
This issue is real - also tracked as a Purism development issue: https://source.puri.sm/Librem5/gnome-online-accounts/-/issues/3
@ringonz Please provide more details about the failing wifi device, otherwise we are unable to help you any further.
See https://tracker.pureos.net/T943#17385
[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.
Thanks for responding despite having moved on. Hope you enjoy whereever you've gone now :-)
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...
@FaiscaOS Please create a separate issue report - even if it seems similar, there are many different wifi devices.
@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?