I mean that if the code is not suitable for Debian main (which our previous conversation at Riot seemed to indicate), then a) maintain it in Debian contrib, and b) have Purism redistribute it (not as part of PureOS, but) from the puri.sm domain.

yes, you are right, it happens during the initial setup. If your password has characters that differ from an EN keyboard layout, you are going to fail. That is how I found out, what was happening. If you skip wireless setup at that point and finish initial setup, in Gnome-Shell, you can see in the indicator top right, that lang is still EN. Switching to DE then and there is no problem.

He meant for it to go via Debian ("maintain the code in contrib") I think, but let's see what he says - I'm not too familiar with all these things.

Alas, I'm afraid I don't 100% follow that conversation. What does @jonas.smedegaard mean by "same hosting" - as in, upload directly to *PureOS* or for it to go via Debian.

Oh thanks! Then I'll just submit it without the manpage for now.

Confirming that the latest image of Plasma PureOS has installed correctly on a Librem 15V3. Working excellently. USB stick was flashed with Etcher. I would recommend this software over others.

Very odd... Potentially, your system is set up correctly, but gnome-control-center doesn't display information correctly.
So, I am quite sure now that this issue is actually a duplicate of T549

@mladen.pejakovic I've split this issue and created T549 so we can track the GNOME bug individually.
Thanks for the feedback!

I can still reproduce this with the image in https://downloads.puri.sm/playground/2018-08-10/

Also confirmed, as expected, with https://downloads.puri.sm/playground/2018-08-10/.

Restarting the installer, here is a screenshot of the checkbox

I agree.

Wouldn't spend too long on the manpage -it is not 100% required.

After another crash, the logs look pretty similar:

And possibly some extra golang packages... :)

This will also require the packaging of (at least) the grpcio-tools Python package.

Created https://tracker.pureos.net/w/troubleshooting/purebrowser_first_start/

james@Librem13v3-PureOS:~$ dpkg -l pureos-minimal
Desired=Unknown/Install/Remove/Purge/Hold

+++-==============================================-============================-============================-==================================================================================================
ii pureos-minimal 0.9.1 amd64 Minimal core of PureOS
james@Librem13v3-PureOS:~$ dpkg -l pureos-standard
Desired=Unknown/Install/Remove/Purge/Hold

+++-==============================================-============================-============================-==================================================================================================
ii pureos-standard 0.9.1 amd64 PureOS standard system
james@Librem13v3-PureOS:~$ dpkg -l plymouth
Desired=Unknown/Install/Remove/Purge/Hold

+++-==============================================-============================-============================-==================================================================================================
ii plymouth 0.9.3-3pureos1 amd64 boot animation, logger and I/O multiplexer
james@Librem13v3-PureOS:~$

I would not. I regard the Forum as a discussion and the Task Tracker as a place for formal issues affecting multiple users. It is, however, good to include links to the Forum here.

Yes exactly. Sorry for the double entry. Should this task be deleted?

Ping Debian maintainer but otherwise go ahead with change in PureOS.

Please check whether the following packages are installer: pureos-minimal, pureos-standard, plymouth.
Without the pureos-* packages, the system isn't considered valid PureOS. They usually only get removed when someone adds 3rd-party unsupported repositories.

Hmm, I can't update this in Debian unless I am NMUing the package of another maintainer, which I really don't want to do.
I could update this in PureOS, which would introduce a delta between Debian and PureOS.
The ideal solution would have been if the Debian maintainer had just updated the package...

@mak, please make this bug your priority :)

Ported it to python3! Just busy (and a bit confused) writing the manpage, but I don't expect it to take very long anymore :)

Bump. @zlatan.todoric any ETA on how soon can this be done ? @mladen.pejakovic needed to use flashrom yesterday and it wasn't working because it's still outdated, and I realized this hasn't been fixed yet.
Thanks!

In T327#9870, @kyle.rankin wrote:

assumed that getting this packaged into PureOS would be faster than into Debian

@mak Only via the live installer.

Thanks for the clear explanation @mak . I understand perfectly.

Sorry, by "upstreaming" I meant "get packaged into Debian." At the time I wrote this in February I was hoping we could get this into PureOS relatively quickly and had assumed that getting this packaged into PureOS would be faster than into Debian so I wanted to do the fast thing first if it was indeed faster.

These are actually two issues, I realize this now, sorry.

@mladen.pejakovic

The installer should pick this up automatically.

@chris.lamb Can you please test if this issue is fixed in my test image from http://downloads.puri.sm/playground/2018-08-10/ ?
Please be aware that the playground image suffers from unrelated issue T542

Not a high priority because this only affects a playground OEM image. Needs to be fixed though before we update the image (which should happen soonish).

@francois Solving this issues is a *tremendous* task. AppStream supports the notion of language packs, but in order for that to be useful, we need to add localization component metadata to a lot of packages and also make adjustments on other GNOME components, and likely GNOME Software as well.
I had a chat with some people from Canonical about this, and we might be looking into this again together. But this will take quite a while to get resolved in PureOS, unless we suddenly get a lot more engineering manpower.

@francois How did you try to install PureOS? Via the live installer, or via the OEM installer?

Any update on this? :)

We already talked about it in the forum. I don't remember. I used a tool to change some gnome settings. But don't remember what. Might be there was an option for it?

The first step here would be to getting it into Debian. I can handle this if you like; please assign me the ticket.

I strongly suggest this as well. LittleSnitch, a similar program that has been around for over a decade, is the first thing I install (and recommend others install) when I work with a new OS X instance.

ajlok: Very odd that you have this option while I don't, as we're both using the Librem 13v3. Is there a setting in Gnome that I might be missing somehow?

In T535#9784, @thegoat wrote:

Not related to the core issue but figured I'd mention it - in my Librem 13v3 power settings, the drop down menu next to "when the power button is pressed" only has three available options - “Suspend” “Power Off” and “Nothing.” There should also be a "Hibernate" option but it's not there for me. I'm running PureOS and my system is fully updated.

Just checking if there has been any progress on this issue? It is blocking non technical users pretty much here in France. Especially the lack of internationalization and spell checking in LibreOffice.

Thanks for creating an issue to track this!

Update: This happens only from the cli! If you search for 'keepass' and run it from the Gnome3 application search it works!

Not related to the core issue but figured I'd mention it - in my Librem 13v3 power settings, the drop down menu next to "when the power button is pressed" only has three available options - “Suspend” “Power Off” and “Nothing.” There should also be a "Hibernate" option but it's not there for me. I'm running PureOS and my system is fully updated.

Thanks for reporting, and providing a workaround!

No problem to upgrade it on last version.

No problem to install it on last version.