I am just about to package 1.2.13 in Debian, which got a fix for
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 17 2019
Nov 16 2019
Nov 15 2019
Oh neat, but we need 1.2.12 (the latest when I checked), it fixes issues for the phone. :)
Nov 14 2019
Should be there: https://software.pureos.net/sw/org.gnome.Lollypop :-)
Nov 11 2019
Nov 10 2019
Nov 9 2019
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.
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:
- During the setup I set up my home partition to be encrypted (LUKS) with a password.
- 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... :(
Nov 8 2019
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
Nov 7 2019
Nov 5 2019
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.
Nov 4 2019
Upstream developers claim it does support things like CalDAV
Nov 1 2019
I tried to install Kodi with aptitude in an updated image of PureOS Amber and had several errors with dependencies:
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.
Oct 28 2019
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.
Oct 27 2019
@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?
Oct 26 2019
Oct 25 2019
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.
Oct 24 2019
Then current options don't include general CardDAV and CalDAV support.
That would means that without a Nextcloud/Owncloud account I could set up a CardDAV/CaldDAV service using the option dedicated for Nextcloud?Perhaps. But I imagine you'd want to ask upstream in GNOME to determine for sure
Oct 23 2019
There's no older kernel to boot from so I can't run update-initramfs. Looks like I would need to reinstall if I want to use PureOS. Thanks for your help.
@nicole We are already tracking this here: https://tracker.pureos.net/T298
Oct 22 2019
Good point - I will add it to the wiki. I will also dig into why it is not coming via an update, although I suspect it may be because it is not available in the upstream configuration.
I just wanted to point out, that it doesn't seem to be added via an update (but it should - in my opinion, if that's not an option it should be probably added in the wiki?)
I'm fine with the manual edit. :)
In T285#16002, @hansolo wrote:In T285#14573, @mladen wrote:Another solution is to add:
### Enable Echo/Noise-Cancellation load-module module-echo-cancel use_master_format=1 aec_method=webrtc aec_args="analog_gain_control=0 digital_gain_control=1" source_name=echoCancel_source sink_name=echoCancel_sink set-default-source echoCancel_source set-default-sink echoCancel_sink # automatically switch to newly-connected devices load-module module-switch-on-connect ignore_virtual=noto ~/.config/pulse/default.pa or to the bottom of the /etc/pulse/default.pa file.
NOTE: You need to logout and login again or to restart pulseaudio with pulseaudio -k command for the changes to come into effect.I don't have this snippet (or any sign of echo-cancelling) in my default.pa, running a fully updated PureOS.
In T285#14573, @mladen wrote:Another solution is to add:
### Enable Echo/Noise-Cancellation load-module module-echo-cancel use_master_format=1 aec_method=webrtc aec_args="analog_gain_control=0 digital_gain_control=1" source_name=echoCancel_source sink_name=echoCancel_sink set-default-source echoCancel_source set-default-sink echoCancel_sink # automatically switch to newly-connected devices load-module module-switch-on-connect ignore_virtual=noto ~/.config/pulse/default.pa or to the bottom of the /etc/pulse/default.pa file.
NOTE: You need to logout and login again or to restart pulseaudio with pulseaudio -k command for the changes to come into effect.
Oct 21 2019
Just came across this thread after consistently having issues in video conferences at work with Librem15 v4.
Sorry for my confusion @guido .
I don't know how many people use this feature on Debian but I doubt that many people concerned about privacy, as Librem users are, will want to switch this feature on.
Okay, agreed. Let's move this to the Apps_Issues bug tracker so that developers can see this and take action.
Thanks for your input @jeremiah.foster.
There is a certain amount of professionalism having this as a option - I believe it shows that we want to fix issues and that we're open about the issues we have. This can be empowering for users, most of whom come from closed, proprietary worlds where they never see the data that the send to nor see their issues fixed in a timely manner. At the same time, I agree with Francois that this may appear to be an invasion of privacy even if you can turn it off. The reason is that users don't know clearly what information is gathered and how. "Reports" are sent on "technical problems". I feel this is very vague and I imagine most people will turn it off, so my preference is to have this turned off by default and perhaps not part of the initial setup. If a user reports issues we can ask them to turn it on. Also, where does the collected information show up?
Oct 18 2019
That would means that without a Nextcloud/Owncloud account I could set up a CardDAV/CaldDAV service using the option dedicated for Nextcloud?
In T837#15974, @jeremiah.foster wrote:Okay, but I believe that Nextcloud provides a standards compliant CalDAV interface which GOA can use. I'll double check.
I think that the upgrade may have brought in a new kernel and changed boot files. You may need to run update-initramfs or follow one of these solutions: https://tracker.pureos.net/w/troubleshooting/broken_upgrade/
If this feature is really important for the PureOS team, then we should keep it.
related https://source.puri.sm/Librem5/Apps_Issues/issues/162 - i think it would be a good feature to have if people opt in - it's by no means about convenience but to give us enough data to fix issues. It's also data that might be hard for the user to provide.
Oct 17 2019
No, I turned it on for the first time followed the prompts, wrote down my passwords / passphrases and ran the typical sudo apt update and sudo apt upgrade.
Okay, but I believe that Nextcloud provides a standards compliant CalDAV interface which GOA can use. I'll double check.
As @stefannagy references, its just CardDAV and CalDAV in general, not just Nextcloud/Owncloud as he already said.
Confirmed that using ENV{PRODUCT}=="316d/4c4b/101" works as expected. Closing this issue, going to add documentation here: https://docs.puri.sm/Librem_Key/Getting_Started/User_Manual.html#automatically-lock-the-desktop-when-removing-the-librem-key
Wow, that is really cool Neil. I ran udevadm monitor as well, but I did not try to change the ENV variable to {PRODUCT}. I'll test that now.
Oct 16 2019
After running the following command
Oct 15 2019
So I'm not sure what's happening here but it cannot boot because it can't find your disks. Usually /dev/mapper maps your disk UUIDs to the luks encryption and /etc/fstab holds the info on your boot disk. Those are unavailable for some reason on your system.
Simply
apt install macchanger
I can only speculate that it might be a Gnome-specific issue. I have no idea. I'm sure it'll be fixed eventually.
The wording has improved. Words such as GNU, Linux, Gnome, Plasma and distribution have been cleverly avoided, which is a good thing IMHO. A bit of redundancy is immediately obvious though. But overall it's going in the right direction. I'm pretty certain that 1 installer for both flavors is the right approach.
In T822#15824, @jeremiah.foster wrote:This might be better addressed upstream, presumably uBlock Origin itself audits the remote lists?