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.

To clarify: Does this issue appear in the live installer, or in the OEM installer on first run? (I suspect it's the latter)

Did you consider reporting this issue to GNOME as well?

@mladen.pejakovic As far as I know when installed (like on debian with the non-free firmware-atheros package) the firmware is loaded into a volatile memory of the wireless card. Volatile memory requires power to maintain the stored information. So when you restart, the firmware remains, when you shut down, wait a bit and then start your system the firmware is lost.

@stefannagy, that's interesting, I did use ArchBang (Arch based live system) before installing Parabola. And after leaving the laptop shutdown overnight, bluetooth is now not working.

This just got fixed in the most recent round of upgrades.

@mladen.pejakovic Did you restart into Parabola from a distro with the firmware installed?

This looks like the same issue I'm having. My system uses English, so from the shell:

Does it look like this? If so, it's probably the same issue reported at https://forums.puri.sm/t/terrible-graphic-distortions-in-pureos/3612

Turned out not to be a problem with PureOS. After I played a bit with VBox settings the issue was resolved. I activated 3D acceleration, increased video memory to 128MB, upped usable RAM to 3GB and gave permission to use 2 CPU cores.

I am currently on Parabola GNU/Linux which is a Libre distro. Bluetooth working fine on Librem 15v3.

You are right. I created a new task: https://tracker.pureos.net/T538

I get massive CPU activity and a black VBox screen.

I experienced the same problem. After finding this thread and plugging in "pureos" as username on my VirtualBox running on Ubuntu I get massive CPU activity and a black VBox screen.

My new RAM is CT16G4SFD824A C16FE
My old RAM was CT16G4SFD8213 C16FH1

Since this was just mentioned again, I need feedback here... Go, or no go?
/me is for dropping it (at least temporarily).

is this a possible relation too https://tracker.pureos.net/T530

possible relation too
https://forums.puri.sm/t/battery-drain-while-suspended/2726/10
and by extension
https://tracker.pureos.net/T419

This is a meta-issue spawned from T534#9657