My apologies, I have no idea where I got that number. I reviewed my own hand-edited file and it says "backslash"

it's the value that we used for the other entries that were already in the file

Is there a workaround or manual way to fix this issue in the meantime?

This is the value I used and tested, and it's the value that we used for the other entries that were already in the file. If we were to change it for this case, we should also change it for the other, previous Librem 13 entries.

the value on the right side is supposed to be a key name. Shouldn't this be something like KEYBOARD_KEY_56=backslash instead

See also https://dev.getsol.us/T6371

Upstream PR filed here:

Yes, this should go upstream like with the parent issue. I have tested this fix against my Librem 13 v4.

@kyle.rankin Thanks for filing this. Should this also go upstream?

Is it possible, that it's fixed on US and UK layouts, but on DE not?
Still have this issue...

Very happy to take this. Indeed good call -- can you create a new, Librem 13v4-specific ticket for this and assign it to yours truly?

If it's better to open a new ticket than comment on this one that's fine, but having all the context of this ticket is useful. We now have a Librem 13v4 and so need to modify the same systemd files to add:

Impossible to continue with owncloud-client.
I have a message : incompatibility wtih Nextcloud server 14.0.4

Will do! I've used both in the past, but found GBP's branching model confusing. Jonas and Matthias have recommendations so I hope to find something that works. :-)

Ah, getcha. In that case, I suggest you checkout pristine-tar and the whole gbp-buildpackage flow in general. That will mean you have both worlds with no compromise. :)

Sorry, I haven't included my debian/ directory yet. I wanted to include a 'pristine' source. Of course I have added a patch, so it isn't pristine, but I wanted to get the source into salsa since there seems to be some movement with the ITA bug in Debian's bug tracker and hopefully we can all work with the same source.

Hey @jeremiah.foster I don't see your other branches, or I don't understand where your debian/ directory is..? :)

Since I haven’t received a response yet:
I went ahead and installed PureOS inside a VM. Can someone on the dev team point me to the necessary repos to build a new live disc? I’d like to try to modify the ISO disc with the changes I need.
I think I need these, but not 100% sure:
https://source.puri.sm/pureos/infra/make-live
https://source.puri.sm/pureos/core/live-build

Looks like you're booting the Purism Librem 13 v2 with a 4.17.0-3 Linux kernel. I'll see if I can find a machine to reproduce that error. In the mean time, would you try and boot from the latest live disk? https://pureos.net/download/ Instructions are here: https://tracker.pureos.net/w/installation_guide/live_system_installation

I've uploaded lastest flashrom code to salsa on debian.org; https://salsa.debian.org/jeremiah-guest/flashrom
Next step (happening now) is to build the package for PureOS and then share any useful artifacts with Debian maintainer.

It's FOSS. There is a problem with that tag.

Thank you everyone. Please re-open if you see any issue related to this at all. I appreciate all the work done on this issue and the high quality communication from everyone! It is quite satisfying to close this bug and I hope we can continue to resolve issues. Okay, enough of my blather.

Fixed on my side as well. Thank you.

Please read my post prior to Jonas's. If @user22492 does not comment by Friday, I'll close this. I was giving him a little time.

It's still on my todo list, but with a low priority, so it pretty much is at the bottom of the queue every time something else of higher importance is added.
Since we have AppStream and this feature isn't one of the most popular ones, its priority is low.
However, it is fixable and I intend to do so when the infrastructure redesign is applied.

I think we can close this, but I'd like more input from the original poster.

This is an ancient bug. I think we should move it to "won't fix" or try and fix it.

This is a known issue unfortunately; T155 I'll see if we can't update the status of that bug to solve this issue.

FYI, the same messages appear in the Applications Log when launching "Applications->System Tools->Software & Updates" from the GUI. The stack is just inverted:

Would it be possible to add the nls_ascii module into initrd on the install disc? If so, I may be able to install on my MBP much more easily.

Could we not change the boring background to something not specific to Purism but promoting, 'Security, Privacy, and Freedom'?

This issue seems possibly related to an issue in LibreOffice resolved today in debian (and thus not yet in PureOS) by tightening its dependency on apparmor: https://bugs.debian.org/918499

@mak Please have a look at this - smells AppStream-related.

I suspect that the line with UbuntuDrivers is totally unrelated and just a warning (despite the confusingly misleading initial word in captial letters).

In T660#12498, @jonas.smedegaard wrote:

@jeremiah.foster does it spew anything _after_ that error message about UbuntuDrivers?

@jeremiah.foster does it spew anything _after_ that error message about UbuntuDrivers?

In T660#12487, @jonas.smedegaard wrote:

On my machine;

ah - sorry, @EchedeyLR: Seems my window didn't refresh properly so I missed your latest response above. Thanks!

(me awaits responses from both @jeremiah.foster and @EchedeyLR for clarification, but suspects this issue is totally unrelated to that "UbuntuDrivers" message and instead the issue relates to AppStream...)

I experience the same issue.

@EchedeyLR What is the output of this command:

That pc is using a default installation.

@jeremiah.foster: Do you experience same issue, or do you talk about GNOME Applications because the stacktrace in the error message hints about it being tied to software-properties-gtk?

I tried open "Software & Updates" application from launchpad but It did not work. Then, I thought it was possible it returns some information trying run it from terminal and I did it and put the output into the description.

Sorry, I put it on task's name but not into description.

If understand from the subject that the error message mentions "UbuntuDrivers" but is that the applications that you attempted to run, or something else, @EchedeyLR ?

Apparently it can be used for configuring apt repos but I don't know that we need to have that in PureOS by default?

It is confusing for sure. :-)

...or @jeremiah.foster maybe you can clue me in here: What is "this particular piece of software" that you are talking about? Perhaps I am missing something obvoius here, but I am totally clueless right now :-/

Sorry, I don't follow: which applications are we talking about here?

A couple other issues with this particular piece of software;

• It is listed as being 'proprietary' software
• It won't run when one clicks on "launch" (see screenshot)

https://bugs.debian.org/919226 related

I have removed the 128 GB Intel SATA SSD and replaced it with a 500 GB Samsung 970 Evo NVMe M.2.
I did install PureOS from scratch and did not encounter any kernel panic.

This problem appears to be fixed with the update I made on 1/13/19. python3-libapparmor now has python3 << 3.8 and I am able to install this package. Above, I provided a link for a LibreOffice issue where this package was needed for debugging. That LibreOffice issue seems to also be fixed with this update.

It's working for me as well, thank you.

I saw that there was an AppArmor package update today from the pureOS repo so I upgraded it, and it seems to have fixed the issue. I can now launch LibreOffice successfully!

Thank you for this information and assistance. You make a good point on downloading the file. As paranoid as I am, it had not occurred to me, though I was really thinking in terms of editing my own file.

Hello everyone,

@jeremiah.foster, if the changes to the profile are few, could you post them so we can modify our profiles? Thanks. (And thanks for your post on this issue about the rolling release aspect in the forum topic.)

I have same problem. When I try to uninstall and install libreoffice-common, I get this messge :

I was having the same issue yesterday and also found AppArmor repeatedly mentioned in $ sudo journalctl | tail output, even after running:

Reopened the issue until it can be confirmed there is a fix in our repos.

On my system the Apparmor service simply doesn't start anymore and cannot be reloaded.

In T670#12428, @jeremiah.foster wrote:

So you get this message when you boot from your laptop? (I just want to make sure you're not booting from the USB stick.) Do you have the USB stick plugged in when you boot? If so, if you could remove it and then reboot and see what it says.

So you get this message when you boot from your laptop? (I just want to make sure you're not booting from the USB stick.) Do you have the USB stick plugged in when you boot? If so, if you could remove it and then reboot and see what it says.

In T670#12278, @jeremiah.foster wrote:

So, there is a kernel panic because the kernel can't seem to find a file system to mount. How did you install GNOME? Did you use a USB stick or an ISO or similar? Or are you using apt-get or some other means?

Hi Jeremiah,
No I still have issues ,I haven’t had any solution yet

Martial -- do you have more feedback? Have you been able to boot?

We need more feedback on this issue. Closing for now, re-open if necessary.