Clicking "learn about new tab" takes user to https://support.mozilla.org/en-US/kb/about-new-tab-page?redirectlocale=en-US&redirectslug=about-tiles-new-tab

I think that this has been resolved

We can close this as it's been removed from PureOS repositories. Telegram available via flathub.

This seems to be currently working.

I did not see you had updated mentors.debian.net - there is no notificatin system there. Can you ensure that you ping back here when you post on there?

I can confirm that the Samsung memory corrects the issue under Ubuntu.

I recommend https://www.findx.com/ and https://gigablast.com/, they are 100% free software.

I'm wondering if this is on anyone's horizon yet? If not I would put it on my TODO list since it would be good to have this running so we can test phone stuff on PureOS in gitlab's CI as well (instead of "only" Debian testing).

I recommend https://www.findx.com/ and https://gigablast.com/, they are 100% free software.

updated…

OK - errors fixed, most warnings fixed!

Sorry - my bad, had forgotten to upload my key. It's there now, but I saw some complaints from lintian. I'll fix those first, but in the meantime, if you can give me feedback, I'd be grateful!

Can you please run gnome-software in verbose mode (killall gnome-software ; gnome-software --verbose) and see what GS says when you load the Blender page?
(paste the log somewhere, ideally)

I'm still seeing these despite the numerous updates/reboots that have happened since along with uninstalling and reinstalling Blender.

Sorry, I don't see it on https://mentors.debian.net/packages/index.

I have seen that lock screen button does not appear in right top bar options.

Thanks! Uploaded, please feedback there!

@vivia.nikolaidou Excellent question. I suggest you upload it directly to mentors.debian.net - that way you follow the process "just like" a regular contributor. I can comment on the package there.

Given that my package is essentially ready, do you need to check it first before I upload it there? If so, which files do you need to see?

Yes, that Purism Forums entry was mine. I am having the same issue that you are having.

Ah, I should have guessed. Thanks!

This bug is exclusive to VirtualBox, for some reason VBox doesn't play nice with Wayland which leads to GDM having trouble.
It's on my todo list to look into this already.

Just learning the ropes, is there somewhere else I should have filed this? I also couldn't find the issue elsewhere.

Maybe the same problem? --> https://tracker.pureos.net/T520

Very good ideas. Indeed, I believe there is already a ticket regarding this but I can't find it right this second... feel free to create another. :)

Thanks @chris.lamb ! Is this anywhere in documentation? Also, in my opinion (I know it's a beta) the user should just be dropped into the desktop session. This will be a barrier for people I recommend PureOS to, and I have handed out a lot of LiveUSB keys at workshops with a wide variety of users.

Hi @seandiggity. Try pureos with no password. :)

Thanks. I have subscribed to this bug.

Thanks a lot! I reported it here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904702

FYI. This is not fixed by any updates this month, including the Linux 4.17.0-1 image update on 7/26.

[Assinging ticket back]

Still to do: check if the ping URL is configurable (and log an issue if it isn't)

Pings the URL http://network-test.debian.org/nm to test connectivity. Would https://www.debian.org/something be a better target? This would be protected from tampering, and indistinguishable from any other Debian website address.

Tested PureBrowser 52.9.0 with a fresh profile per https://tracker.pureos.net/T524 . Immediately visible issues (screenshot below):

Is this a duplicate of https://tracker.pureos.net/T202 ?

Tested PureBrowser 52.9.0 with a fresh profile per https://tracker.pureos.net/T524

Tested with a fresh profile per https://tracker.pureos.net/T524

You can create a fresh profile, launch PureBrowser and then delete the profile:

This issue should be fixed by now (since 52.9.0esr-1pureos2 released to landing on July 6th).

I am also experiencing the drain issue. However, I am running Ubuntu 18.04 and seeing:

@chris.lamb @francois Actually, I already resynchronized systemd with Debian, so this issue should actually be gone now.
Can someone else maybe verify that it's gone as well (a quick test in my VM didn't result in that issue).

I saw the older version in the repos, that's why I thought that's what was installed. Sorry for that.

@SheepKid12 regarding the PureBrowser version, I get:

On the browser case, it would be great if you compare the about:config between firefox (the based version) and purebrowser. On many firefox forks related with privacy and security (like tor browser) about:config have a lot of changes or some of them like disable location services, referer or website fonts, etc.

PureOS 8 is still in beta state. Maybe, the developers will add some features later.

I've also noticed firefox esr 46, which is out of date compared to esr 52 and 60.

Ah. That bit was unclear. :p

I'm expecting no notification, since it shouldn't happen while i'm actively using the computer :)

What are you expecting instead?

Oh neat. (But would we not get that patch/change if we just merged systemd?)

If we fix the underlying issue all users logged into a GNOME session will be in the KVM group and no additional work is necessay, it works out of the box (as users would expect). Just pull this systemd patch into PureOS:

Jumping somewhat to a reasoned conclusion, given that the security for the most-common devices in/around the free software ecosystem (ie. Thinkpads) do not provide much security there has been a correspeonding lack of activity and effort put into the software.

The thing is that we plan to make PureOS target the average user so most of the time there will be no system administrator but only people who don't know what a terminal or a command line is. We cannot exclude this type of people who are the ones that currently have no access to software freedom by not being technical enough.

What we need to determine is if it is "doable" under Gnome/Debian with a reasonable level of security on par with iOS, Android and Windows (as examples).

As promised, I did a bit of research into these. The general consensus is that fingerprint readers are essentially insecure devices that give a false sense of security.

In T486#8954, @mladen.pejakovic wrote:

Yes, there was a typo. :)

So, I have a UK device and am not seeing this subsequent remapping. What, exactly, should I be looking for?

Sorry, I just realized I never replied: L15 is not affected, and only OSes with latest systemd are affected.

Fixed in https://source.puri.sm/pureos/core/pureos-meta/commit/d5c4459a71290fa0b0570e0d76b6b272d9fcf6f5

@zlatan.todoric Sorry for the late reply. As I am about to depart for Debconf, I can't really comment on the issue, but I can provide pictures of the chip I got from ThinkPenguin, which pretty much was exactly the same type that was already built into my Librem device:

Thanks for reeporting. Don't know how this slipped through.