The more images I see and the more impressive Flux seems.
People could already make it run on 16GB cards, let's hope it can get squeezed down even more.
The more images I see and the more impressive Flux seems.
People could already make it run on 16GB cards, let's hope it can get squeezed down even more.
It says it can lead to health issues... Not that it will... soooo.....
disable this system security feature temporarily,
This should be - if I'm not mistaken - possible using the pip env var I posted about earlier, like this:
PIP_BREAK_SYSTEM_PACKAGES=1 sudo apt install howdy
Or exporting it for the current shell, before running the installation
export PIP_BREAK_SYSTEM_PACKAGES=1
But I personally highly discourage it, because - AFAIK - if it even works it will mess up the deps in your system.
I'm no python expert but reading around it seems your only real solution is using a virtual environment, through pipx or venv as you already had found out, or using the
--break-system-packages
* Allow pip to modify an EXTERNALLY-MANAGED Python installation
(environment variable: `PIP_BREAK_SYSTEM_PACKAGES`)
pip flag which, as the name suggest, should be avoided.
EDIT: After rereading I got your problem better and I was trying to read the source for Howdy to see how to do it, so far no luck.
It's an error with a dependency written in Rust, the workaround is to use an older toolchain (1.72), it is fixed in the newer code of tokenizers, but probably it is not updated in AUTOMATIC1111 yet: you should check their bug tracker
To have more info you can read this issue: Link
Considering you are not using the Flatpak anymore it is, indeed, strange. The only reasons I can think of are: your network manager is using the wrong network interface to route your traffic ( if you go on an ip checking site like for example ipinfo do you see yours or the VPN's IP?) or that you have WebRTC enabled and the broadcaster is getting your real ip through that.
For the first case it can get pretty complicated, but it is probably an error during the installation of the VPN app or you set up multiple network managers and it gets confused on which one to configure. You should also enable the Advanced Kill Switch in the configuration.
For the second case you could try adding something like the Disable WebRTC add-on for firefox and check if it works. Remember to enable it for Private Windows too.
The last thing I can think of is that you allowed the broadcaster to get your real geolocation (in firefox it should be a small icon on the left of the address bar), or you are leaking some kind of information somewhere: there are a bunch of site that check for ip leak, but I don't know if that goes too deep for you.
If you want to check anyway the first two results from DDG are browserleaks and ipleak. Mullvad offered one too but it is currently down.
EDIT: If you enable the Advanced Kill Switch, and the app is working correctly, internet will not work while you are not connected to a VPN server or until you disable the switch again, so pay attention to that.
Probably when you installed the second linux you overwrote the boot loader instead of adding a new UEFI entry point.
But I've never had a Mac, so take this with a pinch of salt, and honestly considering things can change based on what, in which order, and how you installed things.. it could be something else.
Unfortunately, in general, people tend to just read, vote, and then forget about it without checking back: that's why I always try to add some source or ways to verify what I post.
And - in this specific case - probably some people just like LTT, I assume.
Linus is an investor in the framework company: Source on the framework forums that links to the video on youtube
spoiler
Why not directly link to the video? Because I don't want to! :P
That's a murder for sure