There is currently a malicious attack going towards the AUR, in the form of a botnet impersonating git users/maintainers to take over packages and adding a malicious payload.

Arch team is aware and working hard to reset/delete the affected commits and packages.

Not properly released on kernel.org yet, but 7.0 has been tagged on the kernel git repository.

Just found this today.

Someone started making an activitypub enabled alternative to LinkedIn.

You can use your existing fediverse account, log in, set your job title, experience, education etc.

It's pretty new, so not a lot using it yet. Not even any jobs posted yet. ;)

Disclaimer: It does look like it's mostly written by an AI bot.

This seems to be a pretty great release.

If they are to be believed:

• Federated chat using Nextcloud Talk
• Performance optimizations for most things
• Circles enhanced to Teams with lots of new features
• Assistant 2.0 brings new AI features for productivity

I'm most hyped about the performance improvements. 😁

Four years since the launch of the Raspberry Pi 4, the Raspberry Pi 5 has arrived with a performance boost and house silicon that adds support for PCIe 2.0.

FOSDEM is a conference where thousands of open source developers meet and learn.

Location is as always in Bruxelles, Belgium, Europe, Earth.

Any of you going this year?

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.

My work place is a Microsoft shop through and through, so all their stuff is based in Azure, Active Directory, Outlook, O365 and Citrix. And they provide my with a Windows laptop for work, which is really great.

The only issue I have with it, is the Windows part. So I took it upon myself to see if I can use a Linux install for work in a Windows environment. So I took my already installed private Linux laptop to work and it seemed to be going alright, expect that it's an old laptop at this point, so the GPU was not good enough to run the screens and the Bluetooth version was to old for the peripherals.

So this weekend I took the plunge. I cloned the Windows drive with CloneZilla (in case of emergency, you know) and installed Arch Linux on my work laptop as the only OS.

And so far, everything has worked. Except for 1 small detail that I totally forgot about! Printing. Specifically label printing, as we do ship some stuff around the country. The printer in question is a Zebra label printer G420-something and is set up on the internet Windows network at work.

I've been at work all day and I haven't been able to setup this printer at all.

This is mostly a rant and acknowledgement that running Linux in a Windows work environment is possible, but it's also a small whimper for help to see if anyone has managed to be able to connect to a network Windows printer.

I've setup a default Samba and Avahi system, but it won't "probe" for the printer. I don't know the exact name/hostname/IP of the printer either.

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

It really has...