In T347#11724, @mladen wrote:

Wiki entry for TorBrowser: https://tracker.pureos.net/w/pureos/tips/torbrowser/

I Will redirect the index (page web) from https://pureos.net.br/ to https://pureos.net .

Thanks, no problem, I understand perfectly I'm waiting so that in the future we can have a pureos.net here in Brazil.

Hi David,

Hi wellton. Thanks for mirroring. I understand that downloads from our official sources can be slow. We are in the process of setting up mirrors worldwide and would love to add yours as a potential partnering mirror. However we have not developed a fully complete policy with regard to mirroring. At this time the feeling is that Purism would prefer that the 'pureos.net' name wasn't included in your mirror URL if at all possible. It seems to imply that yours is an 'official' mirror and ought to get 'official' support.

webrtc progress: https://blogs.gnome.org/tsaunier/2018/07/31/webkitgtk-and-wpe-gains-webrtc-support-back/

That's because of the 'su $user' command that's in there. Root doesn't have to type the user's password but a regular user (even the same user) does.

Hi @jeremiah.foster and @mak , I downloaded iso 04-22 (pureos-8.0-gnome-live_20190422-amd64.hybrid.iso) from link and not working.

At least I haven't partitioned the USB drive. :}

Yes, ENV{ID_VENDOR} is what we'd want, as ID_VENDOR is being set in an environment variable that gets passed along to these udev rules. I was just flagging that in your udevadm output it had set ID_VENDOR (via ATTRS{ID_VENDOR}) to Nitrokey.

The script does work when it runs by itself (always worth asking :-)

Based on this:

The format of the udev rule in the file itself may be the issue, I'm still trying to determine. Nitrokey offers packages: https://www.nitrokey.com/download/debian I'm going to see if they provide any inspiration.

The udev rule doesn't work in either machine; neither the L13v3 or L15v3. With regard to identifying the device, I'm included dmesg output (which I've not found super helpful) and udevadm output (which is better.)

So to get this straight, the udev rule works with your particular Librem Key on one laptop but not another? I wonder if for some reason the ID_VENDOR value changed from "Nitrokey" to something else in newer revisions of the Librem Key.

The rules file is in the right location (/etc/udev/rules.d) and it gets read according to systemd-udev:

Apr 23 10:02:36 slate systemd-udevd[386]: Reading rules file: /etc/udev/rules.d/85-libremkey.rules

The gnome-screensaver-lock works well. I cannot get the udev rule to be discovered on my L15v3 however. There is some information on this available on the Nitrokey from upstream where they publish their own udev rules but that fails to work for me as well.

@jeremiah.foster Please (not only update description but also) make a comment elaborating why you consider DuckDuckGo is really tracking users.

Eww, I don't think I have addressed this yet. Thanks for the issue report!

There is a new version of Calamares out and I wonder if this is still an issue? @hayder could you let us know if this bug is still open?

Thanks for reporting this issue. There is another new build, can you try that one: https://downloads.puri.sm/oem/gnome/2019-04-22/

Wow, what a marvel. now it worked 100% in ISO 2019-04-19. thank you.

emacs25 seems to only exist as a transitional binary package to emacs-gtk in PureOS:

emacs25    | 25.2+1-6+b2   | landing    | arm64
emacs25    | 25.2+1-6+b3   | landing    | amd64
emacs25    | 1:26.1+1-3.2  | green      | all
emacs25    | 1:26.1+1-3.2  | landing    | all
emacs25    | 1:26.1+1-3.2  | purple     | all

There appears to be some cruft in landing, but that has a lower version number so shouldn't be easily installable.
Are you sure this is still an issue?

Raising priority, since a package without security tracking from Debian for a year is bad!

Seems emacs25 was dropped a year ago from Debian but is still lingering in PureOS, and I guess then also blocking the more recently introduced emacs (without version in package name, currently containing version 26) to enter PureOS at all.

Working on adding an entry into the PureOS wiki about this. Thanks for your work EchedeyLR.

I'm not sure what vboot is, but if we're talking about Intel Boot Guard, it's my understanding that requires physically blowing fuses within the CPU, that then only allows signed UEFI to actually boot/run.

I can reproduce this here. The timezone shouldn't actually cause any problems here, yet the Release file was apparently signed and piblished with a timestamp in the future to your system. Very strange. There is no unusual behavior going on in the archive as far as I can see.

This issue resurfaced. Noticed it by running an update at around 00h10 Central European Time

The database connection got a bit messed up due to parts of the infrastructure rebooting.
Should all work again now (and soon even recover better from issues like this when the new software is in place).

librem5-devkit-tools_0.0.2_source.changes: misses mandatory field Binary
How was this source package built exactly? The Binary field needs to be present in .changes file in order to be processed.

This is not a bug in the archive. Source-only uploads are allowed, but the .changes file of this package apparently misses the mandatory Binary field and is therefore rejected. Not sure what caused this though, there might be an issue in the packages' build process somewhere.
See https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-binary for more info on the missing field.

I've reuploaded the same package I uploaded on jan 3rd. source package is librem5-devkit-tools.

I changed the line to GRUB_CMDLINE_LINUX_DEFAULT="quiet" and then ran "sudo update-grub" This seems to have sped things up, boot does not seem to be hanging, but I unfortunately can't quantify this. I still don't see the splash screen for disk encryption, and decided to go back and double check my grub.cfg file. Strangely, the "splash" parameter has disappeared from the "vmlinuz" lines of the file, so that may be why. I have three "vmlinuz" lines in my grub.cfg file, under separate/nested "menuentry" commands. It looks like this:

Rebuilding sure avoids some (possibly gazillions) edge cases. This issue is about something else, though: