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

@chris.lamb I didn't misread the report, I just mistyped the package name (fixed). The statement in itself is still true.

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

There's also tools like vmdeboostrap that invoke deboostrap / pbuilder directly. It would be much simpler if they could work out of the box.

No, with the new installation there can't be a kernel mismatch anymore. The problem here is that Libreboot is run with an UEFI payload which boots into an (unsupported) EFI mode of the live-cd, which still offers a debian-installer install option.
See https://tracker.pureos.net/T460 for reference.

@chris.lamb No, if network-manager-openvpn-gnome is in the list it *will* be installed, unless there is something else pulled in that is mandatory and conflicts with the package.
It will not be explicitly seeded if it is pulled in by another package that is also seeded.

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

IIRC, we had a couple different customer questions about Steam functioning under PureOS, and even though I knew it wouldn't, I thought I should test so as to not tell them wrong. In other words, don't test on your production machine ;)

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

oot@librem15v3-enterprise-pureos:/home/james# dpkg --print-architecture
amd64
root@librem15v3-enterprise-pureos:/home/james# dpkg --print-foreign-architectures
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

PureOS never had Chrome package in its archive and Chromium is now removed and blocked as well.

@zlatan.todoric This is my only source

Fair enough, but there are two mentions here, and chrome is a package which is installed through the package manager. Any thoughts on font issues there?

Just installed and tried it, works here. Can you update your system and see if it works for you as well?

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?

There is new OEM image in place, please open new bug if it doesn't work as expected.

Yeah, I did mean in collaborative way (aka ping the current maintainer, offer help etc). Thanks for noticing my not so good way of putting it out :)

what the...did you maybe enable multiarch on PureOS (aka adding 32bit packages/libs). Also what sources do you have enabled (did you add any sources on your own?).

No. This could be closed unless you have reason to keep it open.

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

@mak is it possible that we have a kernel mismatch now with new ISO?

Here is report from terminal after running

@james.rufer are you still experiencing the issue?

I just tried and installation went fine for me so I can't reproduce this @chris.lamb can you reproduce it? Also @james.rufer can you try running sudo apt install --reinstall samba-common-bin and then try again installing the package?

eh, you can do it, I assigned it to mak as he was doing all previous uploads (the ones I recall) though assigning is not at all blocker for anyone else to do it so go ahead (also on contrary, if you see some assigned bug to other person but you can fix it, go ahead).

Sure thing :)

It should work just fine (be sure to turn off secure boot and uefi if possible inside your BIOS). In general if you can boot Debian testing main, PureOS should also work there.

@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..)

Isn't this upstream issue? If yes we would really need to create upstream tag as there are some bugs popping up looking like that.

Unless someone ports it to Wayland we can't actually work on this :-/

is this an upstream issue and did you update your PureOS to latest available updates?

Installation via snap is currently of out of scope for PureOS (we can't and will not guarantee third-party repos as that is contrary to FSF rules of endorsement).

Chris, can you own this one? :)

As Jeff already stated, branding can't be added to PureOS (besides its own) itself but Purism can use its OEM image for such branding. I will put it on wishlist severity for now. Also making mak aware of it.

Fixed in:

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

I just had my librem 13 v3 replaced due to an unrelated hardware issue and this issue , which I had before, and applied some fix in both from the forum has returned with the hardware swap (note: hard disk is same and OS install is the same).
I know whatever I applied also had to be tweaked in qubes as I have both pureos and qubes installed, So I am trying to recall exactly how I had it fixed in both OS's.

Purism branding elements can be packaged in the repositories of both the normal and OEM versions of PureOS, but preinstalled (or activated) only in the OEM version (i.e. so that the "purism-branding" package is installed by default on factory-preloaded Librem devices, but not on non-purism devices where people install PureOS themselves).

Note: password was actually not required; it logged in directly after entering the username.

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

Purism's Librem devices come in few variants: Librem 13 and Librem 15, with US, UK and German keyboard layouts.

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*.

First, are we 100% sure that removing this fixes it for UK?

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

Username: pureos
Password: live

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.

Can you provide the background etc. for your rationale?

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).

This is no longer a freedom-issue, just cleanup internally...

Please drop blocking from Debian: Package has been dropped as obsolete now: See https://bugs.debian.org/874575

It does not look like I can change this to 'resolved,' even though I am the item's creator.

Fixed in systemd 238-5pureos1

This was much trickier than usual to resolve, especially with the Britney dupe-pkg-on-arch:all bug being present as well, but it worked out in the end. lintian is updated in green now.

@chris.lamb Yes, please, who knows when will updated systemd be released.

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

This is still not working for Librem 13v3.

Right, because I uploaded a newer version to sid since I created this issue 4 or 5 days ago.

lintian is simply too young, like the report says

Heh, the reason for the arm64 issues is that our arm64 builder died, so nothing got built for that architecture for more than a week, No wonder issues exist with package migration.

@chris.lamb At the moment, lintian is simply too young, like the report says:

Package is 1 days old (needed 4)

Fixed in screenfetch 3.8.0-8pureos1 :)

Reopened, because it has happened again. From a user:

Due to several other issues, I re-installed the OS

I simply re-installed the OS...

Thanks, closing this issue to match. :)

no indeed I can't