Linux

https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.9.0-amd64-netinst.iso

I've seen this video of Timothy Roscoe at USENIX ATC '21 recently and was very interested in multikernel OSes.

While Barrelfish is abandoned, it seems that Kirsch is his successor.

However, since I've seen this video I wonder what changed since the keynote, why it doesn't seem to be a thing for mainstream kernels and if there was any roadmap/will to expand mainstream kernels like linux to embrace the whole hardware.

Do you have any pointers/ideas or resources to share on this?

I'm trying to use Android Studio, but the virtual android doesn't start because of KVM error. Tinkering around with another VM application I understood that it's a location/permission issue (flatpak Gnome Boxes had the same issue, couldn't load KVM, but Boxes installed via terminal worked and I could start a VM).

On the official Android Studio website they suggest extracting the tar.zip in /usr/local but the system doesn't allow me to, so I extacted it on the desktop and the app runs, but I get a "/dev/kvm is not found" error, which should be because of the location I'm running Android Studio from.

So, should I just sudo force move the folder of Android Studio from desktop to /usr/local or is there a better way to do it?

PoP_OS just in case it can be useful to know.

Thanks in advance!

I have a server running Debian 12. It seems to hang up and freeze sometime between 12 hours and like 2-3 days. I really want to see what's happening, but I can't access my containers with the web UIs, can SSH, and adding a monitor shows the DE completely frozen. Rebooting fixes it for a while, but it locks up again after some time.

I had the same issue with 10 year old hardware so I threw together a "new" machine with some spare parts and it still happens I also tried rocky Linux and the same thing happened on both machines.

Any help and direction would be greatly appreciated!

I created a simple alias for xargs, with the intend to pipe it when needed. It will simply run a command for each line of it. My question to you is, is this useful or are there better ways of doing this? This is just a little bit of brainstorming basically. Maybe I have a knot in my head.

# Pipe each line and execute a command. The "{}" will be replaced by the line.
# Example:
#   find . -maxdepth 2 -type f -name 'M*' | foreach grep "USB" {}
alias foreach='xargs -d "\n" -I{}'

For commands that already operate on every line from stdin, this won't be much useful. But in other cases, it might be. A more simplified usage example (and a useless one) would be:

find . -maxdepth 1 | foreach echo "File" {}

It's important to use the {} as a placeholder for the "current line" that is processed. What do you think about the usefulness? Have you any idea how to use it?

KDE, Gnome, Gamescope and now Wlroots already have a working implementation of the protocol.

2025 Year of the Linux Desktop.

https://github.com/AlfredoSequeida/hints

Disclaimer: I'm not affiliated to this excellent piece of software.

Open TV is an ultra fast IPTV player for Linux, MacOS and Windows.

Since the last time I posted here, Open TV has changed a lot. I took all the feedback from lemmy, github and hacknews and worked very hard on the last few months to deliver the best IPTV experience on desktop. Here's all the cool new stuff:

• EPG and EPG Notifications (TV guide)
• Download vods and movies
• Re-stream channels to allow multiple devices/people to watch from a single iptv subscription
• Optional keyword search
• Editable sources in Settings
• Option to refresh sources on start in Settings
• Custom sources, channels and groups you can share and import with the .otv, .otvg and .otvp formats
• Support for custom http headers in m3u
• Much more robust m3u processing
• Vastly improved error handling and reporting with both in-app error messages and logging
• More settings added like default volume and default view
• Scroll to load more
• Improved hotkeys and UI/UX
• A ton of bug fixes
• The app was added to scoop (scoop.sh)!

Open TV is a solo open source project. If you enjoy using the app, feedback and bug reports are super appreciated. Donations are also very welcome and always appreciated, no matter the amount.

I'm proud to share a major development status update of XPipe, a new connection hub that allows you to access your entire server infrastructure from your local desktop. XPipe 14 is the biggest rework so far and provides an improved user experience, better team features, performance and memory improvements, and fixes to many existing bugs and limitations.

If you haven't seen it before, XPipe works on top of your installed command-line programs and does not require any setup on your remote systems. It integrates with your tools such as your favourite text/code editors, terminals, shells, command-line tools and more. Here is what it looks like:

Reusable identities + Team vaults

You can now create reusable identities for connections instead of having to enter authentication information for each connection separately. This will also make it easier to handle any authentication changes later on, as only one config has to be changed.

Furthermore, there is a new encryption mechanism for git vaults, allowing multiple users to have their own private identities in a shared git vault by encrypting them with the personal key of your user.

Incus support

• There is now full support for incus
• The newly added features for incus have also been ported to the LXD integration

Webtop

For users who also want to have access to XPipe when not on their desktop, there exists the XPipe Webtop docker image, which is a web-based desktop environment that can be run in a container and accessed from a browser.

This docker image has seen numerous improvements. It is considered stable now. There is now support for ARM systems to host the container as well. If you use Kasm Workspaces, you can now integrate the webtop into your workspace environment via the XPipe Kasm Registry.

Terminals

• Add support for the new Ghostty terminal on Linux
• There is now support for Wave terminal on all platforms

Performance updates

• Many improvements have been made for the RAM usage and memory efficiency, making it much less demanding on available main memory
• Various performance improvements have also been implemented for local shells, making almost any task in XPipe faster

Services

• There is now the option to specify a URL path for services that will be appended when opened in the browser
• You can now specify the service type instead of always having to choose between http and https when opening it
• There is now a new service type to run commands on a tunneled connection after it is established
• Services now show better when they are active or inactive

File transfers

• You can now abort an active file transfer. You can find the button for that on the bottom right of the browser status bar
• File transfers where the target write fails due to permissions issues or missing disk space are now better cancelled

Miscellaneous

• There are now translations for Swedish, Polish, Indonesian
• There is now the option to censor all displayed contents, allowing for a more simple screensharing workflow for XPipe
• The Yubikey PIV and PKCS#11 SSH auth option have been made more resilient for any PATH issues
• XPipe will now commit a dummy private key to your git sync repository to make your git provider potentially detect any leaks of your repository contents
• Fix password manager requests not being cached and requiring an unlock every time
• Fix Yubikey PIV and other PKCS#11 SSH libraries not asking for pin on macOS
• Fix some container shells not working do to some issues with /tmp
• Fix fish shells launching as sh in the file browser terminal
• Fix zsh terminal not launching in the current working directory in file browser
• Fix permission denied errors for script files in some containers
• Fix some file names that required escapes not being displayed in file browser

A note on the open-source model

Since it has come up a few times, in addition to the note in the git repository, I would like to clarify that XPipe is not fully FOSS software. The core that you can find on GitHub is Apache 2.0 licensed, but the distribution you download ships with closed-source extensions. There's also a licensing system in place as I am trying to make a living out of this. I understand that this is a deal-breaker for some, so I wanted to give a heads-up.

Outlook

If this project sounds interesting to you, you can check it out on GitHub or visit the Website for more information.

Enjoy!

I installed LXDM and LightDM, I couldn't login from the DM in either cases, so I decided to run LXQt using startx which worked, except I couldn't sudo from the terminal emulator inside LXQt, while I was able to sudo normally in tty, I've tried enabling elogind, nothing changed, my user is in the wheel group and my system is up to date

cross-posted from: https://lemmy.world/post/24599872

What are the best ways to run a game on sandboxed mode with only game HDD shared to it. There should not be network access for the game and there should be GPU (intel integrated) pass-through.

I have tried Gnome boxes, but GPU pass through is not working and checked distrobox, but that too shares HOME folder.

Hi there! So i build a new pc with hardware < year old and installed mint on it and it takes annoyingly long to boot, 1:50min from the output of systemd-analyze:

Startup finished in 14.075s (firmware) + 10.681s (loader) + 51.070s (kernel) + 34.573s (userspace) = 1min 50.400s 
graphical.target reached after 34.570s in userspace.

The 50sec on kernel boot seems strange to me, maybe 34sec of userspace as well.

It seems to be the systemd-usdev-settle.service according to the output of systemd-analyze blame:

29.451s systemd-udev-settle.service
 3.254s NetworkManager-wait-online.service
  948ms zfs-load-module.service
  491ms NetworkManager.service
  154ms blueman-mechanism.service

The output of systemctl status systemd-udev-settle.service shows:

systemd-udev-settle.service - Wait for udev To Complete Device Initialization
     Loaded: loaded (/usr/lib/systemd/system/systemd-udev-settle.service; static)
     Active: active (exited) since Wed 2025-01-22 12:06:16 CET; 5min ago
       Docs: man:systemd-udev-settle.service(8)
   Main PID: 526 (code=exited, status=0/SUCCESS)
        CPU: 2ms

Jan 22 12:05:47 tower systemd[1]: Starting systemd-udev-settle.service - Wait for udev To Complete Device Initialization...
Jan 22 12:05:47 tower udevadm[526]: systemd-udev-settle.service is deprecated. Please fix zfs-load-module.service, zfs-import-cache.service not to pull it in.
Jan 22 12:06:16 tower systemd[1]: Finished systemd-udev-settle.service - Wait for udev To Complete Device Initialization.

So i think i need to fix the zfs modules, because they slow udev down, but how?

Any other tips to improve boot time of my system? Ubuntu on my 4 yo laptop takes maybe 20-30 seconds to boot, so linux should be a lot faster. I appreciate any helpl!

Hello everybody! here's the problem: In my EndeavourOS laptop I had a /swapfile, but couldn't take snapshots with snapper because of it (if I understood correctly). So, I created a 16Gb swap partition using GParted from a live USB. Then, I edited /etc/fstab to remove the line about the swapfile and to add the newly created swap partition:

UUID=506d48e6-1cc0-4136-ba55-6f2f187bcdb1   swap           swap    defaults   0 0
# /swapfile                                   none           swap    sw         0 0

I took the UUID from

$ sudo blkid  
/dev/nvme0n1p3: LABEL="swap" UUID="506d48e6-1cc0-4136-ba55-6f2f187bcdb1" TYPE="swap" PARTLABEL="SWAP" PARTUUID="b4543e4e-4623-4317-99aa-086b0e62836e"
...

if I run sudo swapon -a it gets enabled correctly and it all works fine. The problem however is that when I reboot the machine, it gets stuck in the systemd screen saying "a job is running for /dev/disk/etc..." forever, and the only way I have to log in is to boot from a live USB, modify /efi/loader/entries/somethingverylong.conf to add these kernel options:

systemd.swap=0 noresume

and then reboot, and manually enable the swap.

I'm not understanding very well what's happening here. why is the system stuck if I don't add these parameters? how can I solve it?

thanks in advance!

Now to make it all RGB and shit 👾

That's pretty much it, after several months, maybe even a year of wanting to take the leap, a couple days ago I finally did it. I just wanted to share this cuz I think it's an absolute win, and I guess just see if anyone has any general advice to keep in mind during the process. I ended up choosing Fedora, right now I'm dual booting while I'm still in the process of finding software alternatives and getting everything set up, but trying to minimize my use of windows as much as possible, and so far I've been loving it. I love this community and I just wanted to thank everyone that has given any advice or suggestions in the past, i'm really excited about this and grateful that I could get to this point.