Showing that is like recommending these non-free network services by default.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Aug 30 2019
I don't recognize this as a freedom issue - care to elaborate, @EchedeyLR ?
Aug 29 2019
I would mark it as a Freedom Issue.
Here is why we should tolerate some advertisements on webpages by default:
Ok, then I am closing this. If someone comes up with a reason current behaviour here is basd, we can reopen.
It was my understanding that it was disabled by default.
I agree that Firefox Sync is enabled. I believe it has been enabled for quite some time.
Please do open separate issue reports for each of those other issues.
no no, as I tried to communicate, the provided info is appreciated.
Ok, testing from a VM image with purebrowser with no firefox compatibility mode, i was not able to reinstall uBlock Origin.
I am repeating the process in a VM with PureOS, with a version of purebrowser that does not have Firefox compatibility mode enabled
It is however *not* an acceptable solution to install addons from Mozilla
It is helpful if you can try distinguish stories that involve wandering off of PureOS and (re)installing things from elsewhere, from stories about solely using software provided as part of PureOS.
Thanks for the details.
As an additional piece of information to this puzzle, a user has reported in the forums that uBlock Origin was also removed from his Firefox, but not blocked so the user could reinstall it as well:
thanks - what is probably more interesting is what you did in-between: Did you start PureBrowser while the addon was removed?
Aug 28 2019
@richard.kolla I made a typo in the first test - please try this:
@richard.kolla Thanks for testing!
Step 1 did not work.
but already, getting fixed by only (?) removing and reinstalling the addon indicates that this is a bug in the addon rather than Firefox trying to suppress it (e.g. due to that new Mozilla content blocker perhaps conflicting with it).
@joao.azevedo thanks - what is probably more interesting is what you did in-between: Did you start PureBrowser while the addon was removed? Or did you have PureBrowser running while removing and reinstalling the addon?
Don't know if it adds any new information to this issue. But i got uBlock Origin back by reinstalling it. Removed it and then install again
This might be related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931640
Arguably, PureBrowser no longer blocks advertisements, as tracked specifically in T814.
Thanks for the clarification.
My output:
whoops, sorry: wrong package!
Unfortunately, Pocket is again included: Seems Firefox changed between 60 an 68 to embed Pocket in the core instead of providing it as a hidden system.
The package currently in PureOS green - 68.0.2esr-1pureos3 - depends on webext-ublock-origin, and the addon loads fine on my system.
Aug 27 2019
E-mail from customer:
Aug 24 2019
I think it is unlikely that anyone in Purism staff will take on the task of packaging a fork of Chromium: Our priority is on a web browser usable both on desktops and phones, and the main contender there is GNOME Browser a.k.a. Epiphany.
@jeremiah.foster It seems to me that the issue of using a self-signed certrificate is orthogonal to the issue reported here.
Aug 23 2019
In this case;
I would investigate further because we quote 4k 30Hz output on the v4 Librem Laptops and we can't if they seem to be tied down to 1920x1080p output.
Still no update from the command-not-found repo, and no progress on T638 so far, so I guess removing command-not-found altogether is the best solution for now 🤷
Yes, I think you're right. We'll discuss this and assign internally.
Aug 22 2019
Between this and the subtask added by Jeremiah, is this a hardware issue or software issue?
E-mail below from customer having issues outputting more the 1080p on his Librem 13v4. Not running PureOS but similar issues. E-mailed back and forth a bit and he ended up running his monitor at 1080p and is no longer having issues.
Did you check the hashsums on the USB drive for the image?
Aug 21 2019
When I surf to the https://giantitp.com I get this message, which seems to point to some serious misconfiguration;
First test image created: https://cloud.docker.com/repository/docker/miahfost/pureos
If you run "Self-Test" from GNOME Disks then I do not see any other course but to try another disk. If your device is still under warranty contact Purism support, we'll handle there. (I see that your laptop is Librem.)
@mladen any other suggestions?
I could try with an even newer version of the kernel, like 5.2.9, would that make sense?
I found Guido's pureos.sh script upstream: https://github.com/agx/debuerreotype/blob/pureos/pureos.sh
- use https://github.com/debuerreotype/debuerreotype/pull/63
- then s.th. like (just a quick hack):
@guido If you were to outline the steps you took for creating the 'green' docker image, I could follow that and put them into a pureos.sh script to submit upstream. I'm also setting this up to be automated.
Aug 20 2019
@mladen I already ran the Disks disk check utility (see comment Aug 13) and the disk is OK.
Ran it again, still OK.
This may indicate that your disk is failing. Start a live media (PureOS or Ubuntu) and check it for errors:
@mladen I just installed Ubuntu 19.04, sporting kernel version 5.0.0-25 and the issue persists!! The laptop fails to boot intermittently, the only difference is that the following error message is displayed before the panic stack trace
error: failure reading sector 0x802 from `hd0'
negative, the issue occurs with 4.19.0-5 (See my comment above from Aug 13)
@louis This means you are not using the latest live PureOS install ISO, which probably has this issue fixed.
@mladen could you please provide details regarding what I'm doing wrong exactly?
Are you expecting 4.19.0-5 to not be affected by this issue, or the opposite?
@louis You are doing something wrong, 2019-07-14 live ISO version has 4.19.0-5 kernel version.
I already tried with that exact version of live PureOS, and the same problem occurs.
I can only suggest that you try with live PureOS, download the latest version from here please: http://downloads.puri.sm/live/gnome/2019-07-14/
https://tracker.pureos.net/T298 May be useful here as well.
Nope, only one, which is the 128 GB SATA SSD that came with the laptop.
That URL looks good and has some good resources. It also fits with my understanding of EDID and KMS.
Do you have two disks in your laptop?
@mladen I just tried reinstalling with the latest OEM ISO as you suggested, and the issue persists. Configuration was the same (swap with hibernate, disk encryption enabled).
Aug 19 2019
So if it's pulling the wrong info from the EDID then we need to find a way to override it. I found this link https://wiki.archlinux.org/index.php/kernel_mode_setting#Forcing_modes_and_EDID and will delve into it later.
@louis I suggest that you use the latest ISO image: http://downloads.puri.sm/oem/gnome/2019-07-14/
So I reinstalled PureOS on the Librem13v4 again using the OEM usb key, and this time went for a apt full-upgrade directly, and the issue still occurs. I also tried installing PureOS using the live version and no swap, and after the installation, the problem occurs at every boot, without the couple minutes hanging time. Finally, I tried installing with the live version and hibernate swap (I think it's the default option when installing from the OEM usb key), and the behaviour is the same as originally (happens 30-40% of the time).
In T809#15183, @richard.kolla wrote:PureOS defaults to Wayland and has for sometime as per my testing of old ISOs. Both the customer and myself are using Wayland. He tried X.org and got the same result he said.