Thanks for reporting.

Thanks Jonas!

Since this bugreport may be used as inspiration for users wanting to work around the issue, I have adjusted the description to talk about adding file below /etc, because editing existing file below /lib is lost when package udev is updated.

Well, the message was a false and the actual culprit was a SQL query failing. The cause of that is fixed now, so this shouldn't happen again (but if it does, I'll look into it again). Not sure why exactly the database was in a wrong state though, but that's really hard to figure out at this point.
That's why the issue is resolved.

It should not be surprising that logfiles indicate that -1pureos2really60.7.1esr1 was rejected multiple times, because that is what I experienced and the reason I wrote "tried several times" in the description.

@jonas.smedegaard No, I mean the same file (without it being rebuilt) was apparently already uploaded and rejected before. Dak hashes the files to not process the same, already rejected upload multiple times (even if it has different names) - and to prevent people from just uploading the same thing over and over again.
That said, this case is really strange, as the upload actually wasn't known before, as far as I can see in the database.
I forced the package in now, it is available in the landing suite now (and will be built soon), but I'll keep an eye on this issue - could maybe be a bug in dak.

@mak: Failed again: "firefox-esr_60.7.0esr-1pureos4_source.changes is already known."

How do you mean the package was "indeed already known"? If you mean to say that you are certain that those releases had already been accepted preciously then what happened to them?

According to dak and the SHA256 hash of the package, the upload is indeed already known and would just be rejected again - can you rebuild the package again and do another upload?
TBH it is *really* weird that the package is rejected, as I would expect to find the originally rejected upload in the rejected queue, but that doesn't appear to be there.
So if your next upload doesn't succeed, let me know immediately! (I also made dak forget about the last upload attempt).

Yes, this is by design for extra security, as well as adding the convenience of not having to enter in unlock passphrases two different times at boot (once for /, once for swap). The downside is that it removes the ability to resume from hibernate.

I've not experienced any issues with recent updates, including update to cryptsetup packages.

Note see also https://tracker.pureos.net/T753

In the first case described here, updating grub (sudo update-grub) had no effect. Problem remains

I don't know for sure. I'm taking a look at them right now and have downloaded and updated here. I'll report my experience with the updates.

Can we assume that today's update (6/17) for the cryptsetup packages to 2.1.0-5 does not address this issue? I have marked all those as 'hold' for now.

The code excluded in the Debian package is a separate upstream project added by upstream as a convenience code copy.

Hmm... I can't reproduce this either and looking at https://repo.pureos.net/pureos/dists/green/InRelease all dates are correct.

We saw this behavior again today (see internal chat system for more.) I cannot reproduce but am just noting here that others are reporting this issue.

The solution is: Windows requires spice-guest-tools to be installed for this to work. So this is not actually a bug with PureOS. Thanks @jeremiah.foster

I made the logo on inkscape. Then i sent a PR to the flatpak guys.

Just as a data point: I am a daily startpage user but it has availability and performance problems. I switch to ddg every now and then when startpage does not respond but that is not something we want to put on our users (that's why I opted to merge the ddg patch for the moment).

I'm just a buyer but my specialty is in surveillance and privacy, currently finishing my master's in communication. I would recommend startpage as an alternative to DuckDuckGo.

It is not perfect but its features and its limitations are well known both to us and to our users.

The Librem 5 team needs a GNOME Web that ships with a list of serach engines that work on mobile and has reasonable results. We need this in GNOME Web ASAP because we'll be shipping the phone in the next couple of months, so for us this is a high priority.

Thanks for clarifying, @jeremiah.foster.

I don't think I did do that @jonas.smedegaard - the details of the task description show something more nuanced than "bad". If you feel that there is no evidence for DDG tracking and fingerprinting users, and personally I deem the DDG statement as acceptable, then I think we can move forward. In other words, that caveat I added shouldn't be a blocker but rather something to keep in mind and as evidence that we've thought about the problem.

@jeremiah.foster you extended the description field of this issue to specifically list DuckDuckGo as bad.

The same thing came up realted to GNOME Web: https://source.puri.sm/Librem5/librem5-base/merge_requests/36 - phone and laptops should ship the same list (only exception I could see is a engine with super nice search results that doesn't work on mobile)

Did you boot up PureOS any time? I believe the logo is the text on that font instead of a drawing like others.

Another solution is to add:

This bug was also reported on the debian bug tracking system https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927338

This package is basically unmaintained, so I'll have to find another solution.

Case 4)
No prior partitions.

best I can tell, this is an issue with compiling memtest86+ with gcc-8, and not something that can be easily fixed within the framework of current coreboot toolchain

No, that doesn't help;

TASK DETAIL

http://tracker.pureos.net/T563

EMAIL PREFERENCES

http://tracker.pureos.net/settings/panel/emailpreferences/

We've recently done a phd restart so let's see if that helps . . .

Thanks for opening the discussion here.

Changing to 'incomplete' since we cannot recreate the original issue.

Can currently also not reproduce it. Seems to be very dependent on internal state? We can close it if you want.

@jeremiah.foster , here is the tracker issue we were talking about in the L5 team meeting today

This is blocking https://tracker.pureos.net/w/pureos/tips/prevent_device_tracking_by_untrusted_access_points/

Plan is to remain on Buster for PureOS Green.