This was reported in Debian recently: http://bugs.debian.org/921030

(hm, not really resolved, but seems that's the option we got in this interface)

Thanks for trying, @jgn2112

@jeremiah.foster Better to merge new issue into older - especially when the older is referenced from other places as is the case here.

Let's close this one out guys. I wasn't able to get it working and gave up as I dont have the time.
I appreciate all the help.
Incidentally, I sold the computer to a guy who was handy with linux scripts and he said a "short" script would solve this. But again, its beyond my scope and time constraints.
PureOS seemed like a really slick OS too.
Maybe someday.

I asked him show lshw again to see if hardware is detected, correct driver used and capabilities detection. He said WiFi does not work now he upgraded. On the version before, it only failed to connect.

This is likely a duplicate of https://tracker.pureos.net/T202

Just to elaborate on that: The pureos-*installer executables are either compatibility scripts or helper scripts that change installer configuration to the OEM settings. All of them eventually will launch Calamares.

Where are we on this? Have things connected or are there still issues that I can help with?

Honestly I don't know where this bug or issue might be. On my Librem13 v3 with a 34" external screen and at 100% scaling both displays "just work". Can you share a screenshot of your "display mode" in the control center?

We only have one installer in PureOS and that is Calamares

4TB disks/partitions can not be supported, unless we switch from BIOS to UEFI with GPT support, or adding GPT support to the Librem's BIOS by other means.
See https://en.wikipedia.org/wiki/GUID_Partition_Table

I can't reproduce this. My laptop 'suspends' when the lid is closed.

With regard to installers, it is unclear to me which installer is the default. This is relevant because I'm trying to diagnose a situation where the installer fails on disks that are 4 TB large. It looks like, from the files that show which packages are included in the ISO, that we also have a 'pureos-installer' and a 'pureos-live-installer' along with 'calamares' which appears to be an installer as well. I assume that pureos-installer is the default (and pureos-live-installer is just for GNOME Live?

@jeremiah.foster I'm afraid I didn't make a note of which ISO I used :( I guess if the issue doesn't recur on the latest ISO we can close it.

Is there a link to the ISO? I'm planning on doing some testing of images so that we can measure 'reproducibility', knowing which image was used as the ISO for PureOS installation in this bug will serve as a good starting point. If this is no longer an issue, perhaps we close the issue?

Recently retested with the same Logitech headset and these package versions. It's working again!

There is an RSS bot that reposts Purism blog posts in the #community-general:talk.puri.sm room. I'm afraid I don't have any details, and the person that implemented it is away. But if you can generate RSS output that might be a start!

@jeremiah.foster Currently I manually trigger builds by running a command on the archive server. I could likely give you access to that with permission of the sysadmins. Since the automated builds might be very slow though and the system will override the previous image in case there is more than one image build on the same day, I think that you might be happier with a manual image build.

(Oh, I want that too but the page you linked is a high-level and textual status tracking document.)

@chris.lamb Ah, so you just want Git commit updates? That's a way easier thing to do, I assumed you wanted notifications about any archive changes and bugtracker changes.

I now put my own status-tracking document into the repository

In T701#13101, @EchedeyLR wrote:

The first error I read it was related with some kernel modules used for the touchpad but I was not sure. Please, run lshw again and dmesg.

The driver should be provided by the kernel like the old version.

The first error I read it was related with some kernel modules used for the touchpad but I was not sure. Please, run lshw again and dmesg.

That took awhile! But the whole process ran. I rebooted (the computer wouldn't shut down properly) and tried connecting via wifi. No luck. It wont even recognize available networks, which it has done in the past.
Incidentally, the error I've been getting from when I tried installing Linux mint definitely has something to do with the touchpad, but I've tried installing LM with the touchpad turned off and no dice.
So I can't install Mint, but I can install PureOS but can't get the driver for the wifi card.
Hmmmmm. I haven't given up yet.

It's upgrading right now...it's going to take awhile. I'll reboot and try the wifi when the upgrade is complete and I'll let you know.

I dont believe upgrade solve your problem but anyways you should maintain your system up-to-date for others reasons and make sure about both errors are not solved yet.

Okay, proceed to upgrade.

About both errors, I saw some posts and could be related with some kernel modules. We should wait for PureOS developers.

I have not hit Y yet...

Did not run sudo apt upgrade yet. Here is sudo apt update:

sudo apt update && sudo apt upgrade

OK...I checked for updates and it said the system was up to date. If you know how to manually update the kernel via the terminal, please let me know and I'll run the commands.
As far as the dmesg command, it returned an insanely long string where every line was the same:

It would be great if you test the wifi again before to exec dmesg

Please, upgrade your system first. Current available kernel version is about 4.19

I have no idea how to run as a superuser but it did give me a warning that the data may be incomplete unless I run the command as a superuser

Mmm on https://h-node.org/wifi/view/en/1941/Realtek-Semiconductor-Co---Ltd--RTL8821AE-802-11ac-PCIe-Wireless-Network-Adapter/1/1/undef/undef/undef/undef/wifi-works/RTL8821AE is reported as not run with free software but It was on Trisquel 8 (Ubuntu 16.04). Could you put lshw on your terminal and post here the *-network sections of the output?

Per your request.

lspci on your terminal

Please, make lspci on a terminal and post the output here.

Please, make lspci on a terminal and post the output here.

@chris.lamb For the Laniakea changes, I now put my own status-tracking document into the repository, so it is more obvious on why making such a change takes so long: https://github.com/lkorigin/laniakea/blob/master/docs/porting-status.md#status
I won't extend the existing codebase much (except for bugfixes) and instead just work on the new component versions for now, which unfortunately means very slow progress for a while.
As for the room itself, I can't comment on that, that's sysadmin business.

Great, thanks for the reply. What triggers the build? Is it possible for me to trigger a build? I'd like to test our PureOS ISO for reproducible builds so I'd like to build two images of PureOS twice and test with diffostat.

@jeremiah.foster There isn't a formal testing process. I check whether the system boots, installs and runs through the initial setup and the initial experience looks okay. Others do that as well on different hardware, and if nobody reports any major issues, the image is good to go.
If there was a particular change on the installer or initial setup that might have broken something, I will look at that change in more detail to see if really everything works as expected.
But that's about it, nothing fancy (or even structured) is currently happening.

So next in line to be tested in the February 2nd release, yes? If so what do we mean by "test", are we sanity testing i.e. it works in my machine kind of thing? I'd like to create a more formal QA process around this and would like to start from how we test today.

Thank you Jonas!

I recommended using 'tracker reset --hard' with GNOME photos, but it deleted some screenshots so caveat emptor; you may lose data.

Thanks for clarifying, @jeremiah.foster - I hope the current title is suitable.

Ehhh... What?
The latest release on https://downloads.pureos.net/ is the current one, and once it has been tested the released one (which should happen very quickly, ideally). If a release is considered broken, it is either removed or a more recent one is built.
Each and every image build is accompanied by a .packages files which lists the contained packages and their versions in details. See https://downloads.pureos.net/live/gnome/2019-02-10/pureos-8.0-gnome-live_20190210-amd64.packages for example.
There are also detailed file listings of stuff included in the installation images, as well as a build log and checksums (the former of which also contains all information on package versions).

flashrom 1.0 in PureOS and new Debian maintainer upstream.

So this issue seems to boil down to a wishlist item "bring in yacy to PureOS". PureBrowser has no leverage over what public search engines serve with regard to proprietary or non-proprietary javascript.

We should not mark the issue as "resolved" until it is no longer "broken" regardless of whether it is in the installer, green, or landing.

Well, I don't see how 'aggressive' fits here either way.