@jonkri Is it possible that there is a typo in the file name that prevents your window manager from picking it up? I ask that because you posted the contents of '10-montors.conf' and if that is the actual name of the file perhaps that is not getting read properly?

Thanks @Jonathan. It looks like your link leads to a opensnitch deb, I'll test it out. Would be cool if this was submitted to Debian, is that planned?

I think flameshot launches, it is just waiting for input no? If you run $ flameshot gui what happens?

I'm glad to hear FTPS is working again. I'm going to close this issue for now.

Glad to hear that the update helped!

I've tested the image and seen that it works. Uploading to the download page is a separate discussion and should probably wait until we've tested the OEM image. We can close this bug however by stating that there are two locations for new images, one is a directory that just holds the output of the build system, the other is the official, tested download image.

That was a bit cryptic, sorry. I mean that in a binary .deb package you don't want your source control tool cruft left inside since it is extraneous and doesn't keep the original upstream source pristine. But, at the same time, you do want a branch that contains the debian directory since that is where the control file and other debian files live which give instructions to the final binary. The consequences are that one has to jungle many branches and to make sure you're on the right branch when you call gpb. Or perhaps I haven't got the hang of it yet.

Indeed. I used gbp to package flashrom for PureOS and will use it to package some other firmware. I still find the combination of git branching and Debian packaging confusing especially when one wants to package without .git and with debian/ :-|

New Debian maintainer: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919434

flashrom 1.0 is in our repos but is not available yet. Will check on what the hold up is.

For clarity, you mean adding a stable Firefox with its own branding and without any changes to defaults, right? This shouldn't be an issue since PureBrowser would be the default and Firefox would require installation by the user.

I received an update from the coreboot team regarding this problem. It apparently is not a PureOS issue only, it affects other OSes too. The quick fix is to suspend and resume again (obviously not a permanent fix). The coreboot team suspects it could be related to some ACPI setting in coreboot, but they haven't been able to find anything conclusive.

It would be great to get some more information on the state of the laptop when it is hibernating. I'm setting up something called "tellerstats" with lm-sensors (which are both in PureOS) to gather more info so I can see if I can reproduce the problem.

Looks like this is a wipefs error. Needs more investigation.

I will try to reproduce this.

Okay, if your hosting plan does not offer SSH, then as you say SFTP (and also SCP which is secure copy and uses SSH for data transfer) won't work. SSH is likely more secure however if configured correctly but perhaps you have no control over the plan your ISP offers you.

Just for clarity, you're pointing to the fact that the PureOS download page (https://pureos.net/download/) has an older ISO image which the downloads page you pointed to (https://downloads.puri.sm/live/gnome/2018-12-10/) has a more recent ISO release?

I will check and get confirmation.

Thank you for this report. I believe that this should go upstream into the Klavaro software itself

I don't think this is related to PureOS packaging because we tend not to change upstream Debian packages except where necessary. I'll take a closer look, but I don't really understand the key issue. I see that libgnutls is going to change, but will that fix the problem? It appears they're only going to turn it into a no-op, so won't we need a new FileZilla that brings back in the functionality somehow? What about other protocols like SFTP (or is that the same as FTPS?) or SCP?

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

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.

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.

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.

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.

In T660#12498, @jonas.smedegaard wrote:

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

In T660#12487, @jonas.smedegaard wrote:

On my machine;

It is confusing for sure. :-)

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)

Hello everyone,

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

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.

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.

Thanks to Birin Sanchez for this work around, tested here with a slightly later version 6.0.5-2, and functioned as expected.

Looking at GNOME's Screenshot with Strace I don't see a call to external networking resources. Running this command;

The video mentions specifically a couple of items;

1. Tor browser launcher not installed on device at default. (16:33)
2. httpseverywhere not isntalled (16:59)
3. Google is the default search engine (17:32)
4. Does using the default Wayland build change settings in the browser (comments re: 13:33)

Thanks Wayne, I'm glad to hear you're not dead in the water. Thank you for your patience as well. Sadly I didn't have time to drill down and find out more about the situation with dependencies yesterday, I hope to try and get some clarity on this today, but no guarantees as its a weekend. :-)

In T666#12337, @Wayne wrote:

I do not understand your last statement.

I don't know how many releases of python there were like that but I can't imagine many.

apt show hplip

shows, among other dependencies, this line;

wget, python3 (<< 3.7), xz-utils, python3 (>= 3.6~),

which seems to imply you won't be able to install this unless your python is higher or equal to version 3.6.* but not 3.7. I don't know how many releases of python there were like that but I can't imagine many.

Having an acceptance criteria (AC) in the issue might help, we can put it in the Description. Having an agreed upon "Definition of Done" is also useful and you've provided an example of DoD we can use, when the issue is in Green.

Just for the sake of clarity, you want to install PureOS on USB attached drive? So you're looking to have a persistent version of PureOS on the USB drive?

I just completed a bluetooth transfer of a photograph from my Pixel to the Librem 13 v3.

I did an apt update and installed a new deb -- firmware-atheros -- and that helped the situation. I have Debian repos enabled, not sure if firmware-atheros is in PureOS repos.

I can confirm this, seeing similar issue.

[   18.375949] usb 1-3: firmware: failed to load ar3k/AthrBT_0x11020100.dfu (-2)
[   18.375954] usb 1-3: Direct firmware load for ar3k/AthrBT_0x11020100.dfu failed with error -2
[   18.375956] Bluetooth: Loading patch file failed
[   18.375964] ath3k: probe of 1-3:1.0 failed with error -2

Yes, that would be my advice. You can do a dist-upgrade anyway and try and fix your system if it gets in a misconfigured state, but that can be time consuming and difficult. Usually with ten days or so that type of package conflict goes away as new software and bug fixes come into the repos.