journalctl lists PIDs, so it might have a corresponding executable name with it.
You should block everything, except the things you want to get through. A firewall (at least in Linux) blocks everything inbound by default.
It means that clients and bots for Discord will also work with this.
As far as I can tell, it's not Discord, but an open source alternative. So I don't think it talks to regular discord servers, but you can use any Discord compatible client to talk to SpaceBarChat.
I don't use the share via email function so I can't tell if that's working or not. But I haven't seen the other issues you mentioned. I can install/update apps fine in the web-interface and I haven't seen any errors regarding whiteboard.
https://www.tech21century.com/best-android-os-for-pc-computers/ has a list of some.
BlissOS and PrimeOS is at the top.
There is currently work being done to get support for some snapdragon laptops into the kernel. I think 6.11 got preliminary support for a couple and patches for others are still waiting.
I don't use an alias, as the command to update is pretty small to begin with.
But you don't lower the amount of pixels you use. You just up the amount of pixels used to display a "pixel" when lowering the resolution. So the same amount of power is going to be used to turn those pixels on.
Have you tried the cachyOS support channels? They might do something different than Arch with drivers.
Could be quite a few different things.
Could be the kernel itself, gnupg, openSSH or even bash.
But we won't know for sure, until it's publically disclosed.
I don't know if it has androd widgets, but ServerBox monitors any machine over SSH.
I opted for the version with RAM and nvme for $270. had to pay shipping, but no import tax (lucky me). So all in all it was about $300 for me.
And yes I run Linux on it. Arch Linux to be precise. Have not encountered any driver issues.
Why not just log in as the user in TTY and then start it?
I'n not sure I understand the use-case of why it needs a Plasma session to start a script that needs to keep running afterwards. If the script itself does not need a plasma session, then you can just start it as a user service with systemd.
I bought a "cheap chinesium" one a couple of months back and have not regretted it (yet). It does what it claimed it would.
The one I bought: Aoostar R1
Maybe you where on an older Ubuntu LTS. I don't know which Ubuntu they consider "supported".
I've been running my HA in Docker on Arch Linux for the last 4-5 years and I have never been notified that my OS is unsupported. Could be portainer related.
Hi all.
Happy KDE Plasma user for a long time and I generally love the desktop experience. But I do have one small issue.
At work, I have 2x 4K displays. connected through a Dock. But in Plasma it's only able to give me around 1080p resolution on both of them. In contrast, the display manager SDDM and TTY displays 4k on each fine.
So am I missing a trick to get the max resolution in Plasma? My install is Arch Linux, kernel 6.4.12, Plasma 5.27, Wayland session.
I did install the displaylink AUR package, as I thought it might be the dock limiting the video output, but it isn't as TTY and SDDM seems to display it correctly.
Happy to hear any thoughts and any ideas. :)
EDIT: The screens turn on and work fine with 4K resolutions in a Plasma X11 session.
A script that goes through a lemmy images in storage and tries to prevent illegal or unethical content - db0/fedi-safety
tværpostet fra: https://lemmy.dbzer0.com/post/3076577
> I posted the other day that you can clean up your object storage from CSAM using my AI-based tool. Many people expressed the wish to use it on their local file storage-based pict-rs. So I've just extended its functionality to allow exactly that.
>
> The new lemmy_safety_local_storage.py will go through your pict-rs volume in the filesystem and scan each image for CSAM, and delete it. The requirements are
>
> * A linux account with read-write access to the volume files
> * A private key authentication for that account
>
> As my main instance is using object storage, my testing is limited to my dev instance, and there it all looks OK to me. But do run it with --dry_run if you're worried. You can delete lemmy_safety.db and rerun to enforce the delete after (method to utilize the --dry_run results coming soon)
>
> PS: if you were using the object storage cleanup, that script has been renamed to lemmy_safety_object_storage.py
