Sorry this is gonna have to be rebased due to it being rebuilt against protobuf.
Rejected for inclusion due to limited value add, not being developed, and no stable release.
Due to a lack of response, I guess this can be closed.
As an update to this, I still have no idea what's causing it. As far as I can tell, our polkit rules for it should be fine, and all of the dependencies are met. I made a comment here with my findings so far.
I think I am part of the way there, but I am running into an issue, and I am not quite sure I understand the root cause. I have compiled software before, but I am a network engineer, not a software developer, so some of this slips through my fingers.
@macroonsail: This is still technically accepted for inclusion. Someone just has to step up to volunteer as a maintainer and provide a patch.
@JoshStrobl Yes that seems to have fixed the problem now open vpn is working. Thanks so much :-)
I did the install and it worked for me. No reboot was necessary.
Is this still DOA? I would really like to have the app available
I haven't tracked down a specific solution for this and since I don't use OpenVPN (I've mostly been getting results related to AES-NI, various hardware solutions, BSD-related OSes, etc.), have any configs, etc. I can't validate much further than providing the two eopkg files below. These files include an updated mbedtls and a build of openvpn that defaults to AES ciphers (patch from Fedora), enables async push and changes the TLS crypto library. The limit of my testing was checking ciphers, tls, and digests via openvpn's CLI.
Thank you, this is most helpful. I tested both workarounds - kernel 5.6.18-156.current is working stable.
Any update on this issue ? Could really like to use my vpn without me distro jumping somewhere else.
Thanks, Josh! I tried to build Firefox locally before with this change but ran out of memory, and then forgot about it myself 😀
Kinda forgot about this issue when I was doing R755:0c1a26795c0912699779644a70880fa2c85009b3, but I'm cooking another Firefox build locally with the supplied change and will validate + push when it's fixed.
Should be filed at https://github.com/getsolus/3rd-party
Caps Lock LED blinking
The ICM files you're referring to should be shipped in ALSA's ucm conf project. This is in fact the case, they're in ucm-conf 1.2.3 so it should just be a matter of us updating to the latest releases of that, topology conf, and alsa itself. We can see about getting that sorted this week.
In which environment you are facing this?
LGTM and thanks for taking up maintainership of this!
I don't have a strong preference on the matter. A sysuser is probably sufficient.
Sun, Jul 12
Although I think it's a better practice to create a dedicated user. dnsmasq starts as root and then falls back to nobody for security reasons (?). Giving it a dedicated user would allow it to behave while not being exposed to too many privileges.
If that's something you want to tinker with so it has access to that PID you're more than welcome to.
Update to 2.81
Panel Used By