the time we can expect to wait until fix is applied upstream

Merge request here: https://gitlab.com/lamby/osinfo-db/merge_requests/1

everything using VTE in Debian actually has to implement a workaround for this to work, gnome-terminal is carrying a patch for this for ages.

Currently blocked in Debian: gnucash unsatisfiable Build-Depends(-Arch) on armel: guile-2.2-dev

Assigning over for triage/priority :)

We can surely fix this annoying error without changing the Debian Policy (!).

@kakaroto This ticket is currently unassigned so it's not on anyone's radar. May I suggest assigning to @zlatan.todoric so that he can pass it on to whoever is free, etc.?

♥ thanks

@kyle.rankin Just email your comments to 903163@bugs.debian.org ? :)

pureos is probably aware of it as there exists still the corresponding section in the troubleshooting wiki

Fixed in pureos-security-hardening 0.0.1.

Fixed in pureos-security-hardening 0.0.1.

Fixed in pureos-security-hardening 0.0.1.

@kyle.rankin Can you provide any input (on the Debian bug preferably...) on the response from Guillem here: https://bugs.debian.org/903163#10 ? Thanks!

Another firewall alternative: https://www.opensnitch.io/

Also suid_dumpable

Alternatives to the subgraph firewall might include https://douaneapp.com/

ITP bug filed here: https://bugs.debian.org/903163
Initial, untested packaging here: https://salsa.debian.org/lamby/pkg-gpg-encrypted-root

This should reappear soon:

Subject: anbox_0.0~git20180612-1_amd64.changes ACCEPTED into unstable

(Diff of description appears to be:)

Thanks for the ping and this is good to know; can prioritise this over some other things on my radar :)

Interesting, I wonder what caused network-manager-openvpn-gnome to not be installed on my new system... Ah well!

NB. this is an external, USB adaptor.

Assigning @mak (in the first instance) as it's installer-related...

Check the Depends and Recommends of, for example, the pureos-gnome packages (and similar).

I assume this is resolved.. as in, shorten your hostname? :)

(renaming to reflect underlying issue as I understand it.

Unless you are suggesting we upload the 'experimental' version directly to PureOS for now?

@mladen.pejakovic So, GNUcash was removed from the Debian "testing" repository and it is thus not in PureOS. There is, therefore, nothing to backport against!

https://bugs.debian.org/901134#47 further movement FYI

In that case network-manager-openvpn-gnome was definitely not installed on my new system (installed 2018-04-26). :)

@mak I fear you have misread this bug report. This is about network-manager-openvpn-gnome, not network-manager-gnome.

This has nothing to do with Plan. You just happened to hit/see it whilst installing Plan.

@james.rufer (any reason why you added i386?)

Just went to do this but network-manager-gnome-openvpn is already in the list of Recommends since 31 May 2017 and crucially is actually on the same level as network-manager-gnome. Thus, whatever installed network-manager-gnome via the recommends system should have also installed network-manager-openvpn-gnome for you.

@kyle.rankin wrote:

And your smb.conf please! Sorry, not sure why I didn't ask before given that the error message clearly says it is "invalid"

Odd thing is when I went into the menu to open another application, "Plan" and "Plan Work package" are now installed

I'll take this back unless there is strong objection as it's still literally open in another window..although will upload after lunch.. :)

Installing "Plan" works fine for me. I suspect the installation failure here is a symptom of a different problem. Can you try and do an PureOS upgrade on the command line? ie. sudo apt update && sudo apt dist-upgrade and look specifically for any samba issues?

if you see some assigned bug to other person but you can fix it, go ahead

Sure thing :)

@zlatan.todoric Why re-assign? I did the last pureos-meta upload at least & was literally just doing this another window (have stopped, mind you..)

Fixed in:

@netnut404 Please clarify exactly which keyboard model you have (eg. US/DE/UK?)

systemd applies a software workaround for Librem 13 v2 and v3 devices so that the keys on those devices are correctly mapped. However, it turns out that this also remaps keys on UK and DE devices

I have a Librem13 v3 with a UK keyboard but I am pretty positive I needed the firmware fix to make it work *even in Grub*.

However, the workaround also affects UK and DE models which do not have this problem

Thanks. So getting the logs of the Software Center failure would be the next step to resolving this, ie. working out why/what it is failing there and fixing that.

I believe this is an isolated issue which was fixed, and is surfacing for users who didn't update for a long time (it happens for people who update via GNOME Software Center, AFAIK update via apt doesn't trigger the bug).

Fixed in systemd 238-5pureos1

@mladen.pejakovic Thank you for this. Would you like me to provide a patched package immediately? I can do this tomorrow.

lintian is simply too young, like the report says

Fixed in screenfetch 3.8.0-8pureos1 :)

Thanks, closing this issue to match. :)

Hi, so you can no longer reproduce this particular issue?

Fixed in pureos-meta_0.9.0_amd64.changes

We should be up-to-date with GNOME soon - caused by arm64 backlog at the moment I believe.

It does indeed sound like there was not enough RAM, but I am not sure what we could do about this?

Agreed. Changing status to "resolvd".

Agreed. Changing status to "wontfix"..

@mak You'll have to ping the sysadmins for access … sorry.

This is now here: https://source.puri.sm/Purism/Systems-Tasks/issues/58

… and after some testing.

Reviewed packages from Zhu on mentors.debian.net

Fixed in https://salsa.debian.org/lintian/lintian/commit/fa0de8203b53981c514f64ff0dd212386b31543a

https://bugs.debian.org/901130 modules

Reverted in https://salsa.debian.org/lintian/lintian/commit/05d705ff4e2175295d998cf304e5992709fbf7bd

https://bugs.debian.org/884797#34 Shengjing Zhu will take over this in Debian. Have offered to sponsor.

Fixed in Lintian: https://salsa.debian.org/lintian/lintian/commit/a1564876037e3e9e6d3fdf8fdceccec40fc85ffa

I cannot reproduce this - I can edit my computer's name here (it is not greyed out)

This is being tracked in Debian at: https://bugs.debian.org/901035

Would it be possible to see a picture of this "@@@@" ?

The os-release thing already results in a neat "PureOS" string