Not sure what you are asking.

What about those which don't have license field?

Upstream repository feed:

More sustainable than subscribing to a non-default repository - whether maintained by us or picking a third-party repository - is to setup a proxy for the feed which filters the repository feed and lets through only those with a license known to be Free.

Parabola patch is therefore overzealous: Only the three lines changing URL are relevant.

Parabola issue 1035 really tracks two different issues: a) contains non-free decompression engine for RAR archives, and b) support for non-free addons.

I did not remove any package using bleachbit.

This actually looks like the decryption worked okay and LVM is good.
Did you get this message *after* you entered your password to decrypt the device?

much better :) sorry

Since you apparently are using a fully encrypted disk, it would mean that any data would be lost when you reinstall.

Thanks for your help, highly appreciated !!!
Newbie with linux, my question may seem very stupid, but if I'm reinstalling PureOs do I keep my home directory folder datas safe (like with Mac system) or do they get 'crashed' (like with windows system) ?

Do not use Bleachbit - ever. See https://blog.martin-graesslin.com/blog/2012/07/do-not-use-bleachbit/
I can look into this later this week, to maybe figure out what's wrong, but if you can, reinstalling the OS is probably the best idea.

Hopefully that will help...

I agree with the conclusion done by Trisquel: While Debian arguably tolerate Free clients pulling non-free code from external services, PureOS cannot do that when seeking FSF endorsement.

Debian package does a fair job of stripping non-free sources, including the convenience code copy of glut code.

Upstream is dead, and alternatives exist. Seems just a matter of time before it is dropped in Debian.

Only Matthias can block packages.

GeoGebra licenses its documentation as CC-BY-SA-3.0, since at least version 3.2.40.0 packaged prior to initial release in Debian in 2010.

I am not trying to be fair nor compare them as technical solution - the idea of Tox was to have some default for PureOS secure chat/videoconferencing app but now that it seems that Matrix with its clients is going to end up being default for PureOS, I think we can safely disregard tox for now (at least until it gets properly packaged into Debian and is more end-user usable than Matrix).

As I understand it, QTox is different from Matrix:

Hm, looking the bug report (which is already couple of years old and the last msg was from 2 years ago), it seems this is stuck. I do wonder what is the current state of tox itself (especially now that matrix and riot are on rise).

oh well - it _is_ browser agnostic already (se Debian bugreport).

copyright referenced at the Github page seems to not cover documentation, and also what seems to be copyright portected in the documentation package is only the _packaging_ of it: Manoj is a Debian developer, and at least none of the few documentation files I randomly looked at were authored by Manoj.

Bogus issue: Does not affect freedoms.

I recommend *against* pulling in third-party code repositories.

This recent Debian thread looks related: http://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2017-September/020574.html

Better to be browser-agnostic by use of xdg-open

Both cups-filters and inkscape recommend imagemagick.

Removed from Debian testing (for different reason, but expected to not re-enter without addressing this bug first).

it is only matter of updated package in this case.

Good to know, we will maybe need to check some diff in Fedora packages but I assume that it is only matter of updated package in this case.

Thank you for the answer.

Ok, I'll retest in a month, it will probably work because meanwhile, for professional needs (I'll teach Krita course in Paris in a week), I installed a Fedora 26 and didn't ran into this issues on same hardware.

Thank you. Nice to meet you too!

This is most probably Wayland issue, it will be solved in updates this month.

Not sure should we treat this as a bug, it is default behavior and yes it has simple password on it (maybe we should just add that on download page).

Hi David,
first of all, nice to have you here.
Can you update first entire system and fix broken packages as suggested by the command you got in terminal. Also that can be an issue with Wayland session atm (it will be fixed if that is the case), so you can try on login screen to switch to X session.

Bug reported to Debian.

Upstream fixed the bug.

I left the Librem to an IT repair store, it's been a week and the guy have found nothing to solve the problem yet :s

can you post a screenshot of the issue?