Thanks Wayne. Closing this one.

This looks like a duplicate of tracker item. You might wish to check there, but there has been no resolution that I have seen. I too uninstalled it.

This may not be your issue, but there are problems with add-ons for Thunderbird 68. (I am not sure from which version you are updating, for example.) From the release notes, one unresolved issue is:

Yes, unrar-free recommends unar.

I am using the following script to report battery level to a log:

I am running without gnome (dwm/x11) and have UPower.conf as attached. I have had my librem 15v3 simply poweroff many times between 25-50% batter as reported by /sys/class/power_supply/BAT/capacity.

The Yubikey has a USB Keyboard driver included on the key. This may affect the way it appears in different operating systems.

can't reproduce, cancelling ticket

My Yubikey has worked on:

• Windows 10 laptop
• Ubuntu 18.04 on System76 PC
• Ubuntu 18.04 on Chromebook

Thanks for reporting this issue.

None of the above-mentioned modelines have worked for me on Librem 15v4 with a 3440x1440 monitor. Only the autodetected 1920x1080 outputs anything at all on the screen. Running Xorg and Debian 10.

Okay, I confirm that apt is configured to install recommended packages by default.

Well it is that or apt by default is configured to install recommended software.

@mladen , it did actually work with 3840 2160 26. I don't know what I had missed earlier. I now have 4K on my external monitor, Join Displays and Mirror, both work. Thanks!!!

I tried identifier HDMI1, but it doesn't work, the resolution disappears from the list, and xrandr throws this:

@t1b0 You have two errors:

I tried the other half of kyle's suggestion about /etc/X11/xorg.conf.d/10-monitor.conf , then I rebooted, and I logged in with GNOME on Xorg, but it still doesn't display to the external monitor. I tried both the xrandr command and the Display Settings UI:

HDMI output limited to 1080p

Similar? -> https://github.com/projecthamster/hamster-shell-extension/pull/238

@mak Please block pipx from entering PureOS.

Yay!

The package telegram-desktop is Free software, and its ties to commercial rtworked services does not affect PureOS compliance as a GNU Free Software Distribution.

Done

I see no reason for blocking MAME from PureOS.

I am just about to package 1.2.13 in Debian, which got a fix for

Oh neat, but we need 1.2.12 (the latest when I checked), it fixes issues for the phone. :)

Should be there: https://software.pureos.net/sw/org.gnome.Lollypop :-)

After I installed PureOS 9 for the 4th time, but this time without encrypted HOME partition, there were no problems after the update of packages and I didn't receive any warnings of wrong keyboard layout so far. So, the it seems that the problem appears when encryption during partitioning comes in place.

And... Here we go again... ;(

These are the last messages, after I do "apt full-upgrade"...

No, unfortunately not! I just installed the latest ISO with PureOS 9 from a USB flash drive, and it even gets worse! I mean, as long as the installation process is done, and after the reboot, 5 minutes later I get the notification there are system updates available. Whether I do these updates or I follow the instructions above and do it from the terminal with "sudo apt full-upgrade", after the next reboot I get the same error from the photos I've posted here earlier.
I guess the problem is connected to these 2 facts:

1. During the setup I set up my home partition to be encrypted (LUKS) with a password.
2. There may be really a problem with my keyboard layout, but I have no damn idea why, because: I'm using Librem15v3 - so you know what type of keyboard there is and I don't change the default settings during the installation process: the system language is English "unspecified" and the keyboard layout is US. After installation, when I do the system account setting, I choose again the default US layout and US English as environment locals (although as Bulgarian, living in Bulgaria I should later install my BG environment).

But that's the situation right now, and I can reproduce is to you. In the last 2 hours, it happens already 3 times in a row... :(

This is the content of a Matrix chat I had with the Felix Häcker in this room https://riot.im/app/#/room/#shortwave:matrix.org

Online privacy is some how tricky to handle as things are becoming complicated but nevertheless online privacy tools like tor, vpn, password manager etc. As per the BestVPNGuru, most effected and widely use tool is VPN due to level of encryption and anonymity.

Upstream developers claim it does support things like CalDAV

I tried to install Kodi with aptitude in an updated image of PureOS Amber and had several errors with dependencies:

ty

Upstream developers claim it does support things like CalDAV. Please discuss this with upstream.

Do you need git-all? Usually git-core is sufficient. git-all brings in things that require a different init system, this is why important system packages get removed.

Sure. I'll send an email :-) Cheers!

https://salsa.debian.org/installer-team/debootstrap/merge_requests/37 Merge request sent upstream.

We have two different Librem Key models at this point. The original which was made by Nitrokey and the "Made in USA" one. Each one has a different product ID and probably HID_NAME as well.

@max.polwin I'm afraid I fon't have any advice. Would you mind contacting me @support email?

hi I have exactly the same issue! @mladen did you find a solution or the cause for the issue?

Using the following text in the "85-libremkey.rules" file also works:

Actually, the Librem Key I have is different, its PRODUCT env is 20a0/4108/100. Could we use more general solution?

I agree completely and I thought actually that the "amber" dist was already upstream, but apparently not. I'll investigate and try and ensure the amber definition is in Debian's bootstrap.

@jeremiah.foster people are stepping on this while trying to bootstrap amber on Debian - would you take a stab of trying to get this into mainline deboostrap so boostrapping pureos becomes simpler everywhere in the future? I'm happy to help here.

Then current options don't include general CardDAV and CalDAV support.