I know I see the little button that does it automatically but I don't want to use that I want to know how to do it correctly. -Problem is, every guide says to use the .asc file. I don't have that, tails gave me a .IMG file, a .SIG file, and then I downloaded a tails-signing.key file. How do I manually verify this file with just those files?

They're in their 60's, finally convinced them.

They say things like "This is the same..."

and I'm like

"Ya because that's Firefox, the only program you use..."

"What was Windows even doing for us?"

Some app launchers these days run each app in a new systemd scope, which puts the app process and any child processes into their own cgroup. For example I use rofi which does this, and I noticed that fuzzel does also. That is handy for tracking and cleaning up child processes!

You can see how processes are organized by running,

$ systemctl --user status

I think that's a quite useful way to see processes organized. Looking at it I noticed a couple of scopes that shouldn't still be running.

Just for fun I wanted to use this to try to script a better killall. For example if I run $ killscope slack I want the script to:

1. find processes with the name "slack"
2. find the names of the systemd scopes that own those processes (for example, app-niri-rofi-2594858.scope)
3. kill processes in each scope with a command like, systemctl --user stop app-niri-rofi-2594858.scope

Step 2 turned out to be harder than I liked. Does anyone know of an easy way to do this? Ideally I'd like a list of all scopes with information for all child processes in JSON or another machine-readable format.

systemctl --user status gives me all of the information I want, listing each scope with the command for each process under it. But it is not structured in an easily machine-readable format. Adding --output json does nothing.

systemd-cgls shows the same cgroup information that is shown in systemctl --user status. But again, I don't see an option for machine-readable output.

systemd-cgtop is interesting, bot not relevant.

Anyway, I got something working by falling back on the classic commands. ps can show the cgroup for each process:

$  ps x --format comm=,cgroup= | grep '^slack\b'
slack           0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-niri-rofi-2594858.scope
slack           0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-niri-rofi-2594858.scope
slack           0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-niri-rofi-2594858.scope
...

The last path element of the cgroup happens to be the scope name. That can be extracted with awk -F/ '{print $NF}' Then unique scope names can be fed to xargs. Here is a shell function that puts everything together:

function killscope() {
    local name="$1"
    ps x --format comm=,cgroup= \
        | grep "^$name\b" \
        | awk -F/ '{print $NF}' \
        | sort | uniq \
        | xargs -r systemctl --user stop
}

It could be better, and it might be a little dangerous. But it works!

[Solved] just had to create a new partition and then it lets me select FAT.

I'm not sure what happened, I remeber using gnome disks to do this before but it isn't working now now the only options I get are (MBR/DOS) or (GPT) and neither one will let me access the actual USB afterwards in anything other than GNOME disks. I can't use file explorer and add anything to it.

What is going on here? I swear this worked well before but now something has changed suddenly and I can't get it to work anymore.

When I restore a Debian disk image to the USB it will finally show up in the file explorer but I can't add anything to it and the only options I get to format it are those ones that won't let me access it in the file explorer and actually use the USB.

What am I doing wrong?

Official statement regarding recent Greg' commit 6e90b675cf942e from Serge Semin

Hello Linux-kernel community,

I am sure you have already heard the news caused by the recent Greg' commit 6e90b675cf942e ("MAINTAINERS: Remove some entries due to various compliance requirements."). As you may have noticed the change concerned some of the Ru-related developers removal from the list of the official kernel maintainers, including me.

The community members rightly noted that the quite short commit log contained very vague terms with no explicit change justification. No matter how hard I tried to get more details about the reason, alas the senior maintainer I was discussing the matter with haven't given an explanation to what compliance requirements that was. I won't cite the exact emails text since it was a private messaging, but the key words are "sanctions", "sorry", "nothing I can do", "talk to your (company) lawyer"... I can't say for all the guys affected by the change, but my work for the community has been purely volunteer for more than a year now (and less than half of it had been payable before that). For that reason I have no any (company) lawyer to talk to, and honestly after the way the patch has been merged in I don't really want to now. Silently, behind everyone's back, bypassing the standard patch-review process, with no affected developers/subsystem notified - it's indeed the worse way to do what has been done. No gratitude, no credits to the developers for all these years of the devoted work for the community. No matter the reason of the situation but haven't we deserved more than that? Adding to the GREDITS file at least, no?..

I can't believe the kernel senior maintainers didn't consider that the patch wouldn't go unnoticed, and the situation might get out of control with unpredictable results for the community, if not straight away then in the middle or long term perspective. I am sure there have been plenty ways to solve the problem less harmfully, but they decided to take the easiest path. Alas what's done is done. A bifurcation point slightly initiated a year ago has just been fully implemented. The reason of the situation is obviously in the political ground which in this case surely shatters a basement the community has been built on in the first place. If so then God knows what might be next (who else might be sanctioned...), but the implemented move clearly sends a bad signal to the Linux community new comers, to the already working volunteers and hobbyists like me.

Thus even if it was still possible for me to send patches or perform some reviews, after what has been done my motivation to do that as a volunteer has simply vanished. (I might be doing a commercial upstreaming in future though). But before saying goodbye I'd like to express my gratitude to all the community members I have been lucky to work with during all these years.

I've been 100% on Linux for several years now and I don't miss Windows at all in any aspect.

But in my opinion, there is one thing that Windows does significantly better than Linux, kiosk mode.

I wish Linux had something similar. All the solutions I've been able to find are far more complex and technical to implement and use.

If anybody has suggestions for something that's easy to use on Linux that works similar to Windows kiosk mode, I'd love to try it.

Edit: including corruption of superblocks

[Solved] So I disabled the CD ROM repository using the software and updates application on Debian 12 because it kept asking me to insert the CD ROM when I would try to install stuff.

After disabling it I used Aptitude to update the packages I had already installed but I noticed that before I disabled the CD ROM repository it told me that because I didn't have it inserted that it used some older versions of software.

After removing the CD rom repository it just updated everything and didn't show that message.

My concern is that I know Debian uses some older versions of stuff because of its stability and I read very briefly about "Franken Debian" situations where people use versions of stuff that weren't intended to be used with the stable version of Debian.

Did I mess up by doing that and create a situation like that? And if so, after a fresh reinstall when I get here again is virtually mounting the USB stick I have the Debian DVD ROM on an option for it to stick with that CD ROM repository? (I don't have a physical CD ROM on this machine)

I see that it can be slower because of having all the dependencies included with the flatpak itself instead of relying solely on whats installed on the system. I read that this means it isolates or sandboxes itself from the rest of the system.

Does this not mean that it can't infect the rest of the system even if it had malware?

I have seen people say that it isnt good for security because sometimes they force you to use a specific version of certain dependencies that often times are outdated but I'm wondering why that would matter if it was truly sandboxed and isolated.

Do they mean that installing flatpak itself is a security risk or that also specific flatpaks can be security risks themselves?

[Solved] just had to log out and back in Original post: I'm running Debian 12 and I set a separate root password from my username password.

When trying to install a .deb file I noticed that it said I was not in sudoers file so I looked it up and tried the command SU and successfully entered my root password.

The I tried doing

sudo usermod -aG sudo [username]

And then I verify the addition of the user to the sudo group with

groups [username]

And this does indeed show that I am in the sudo group however when I try to install a .deb file after that or even sudo apt update its still telling me I am not in sudoers list.

Any ideas what I'm doing wrong here?

I went with GNOME just because I'm used to it and want stability as my main focus but I was wondering if using one DE over another can affect security or privacy at all? Or is that all dependant on the distro you are using?

Highlights

• Fix an fd leak and confusion in the protocol that would cause leaks and wrong memory to be used.
• Fix bug where the mixer would not be synced correctly after selecting a port, leaving the audio muted. (#4084)
• Backport v4l2 systemd-logind support to avoid races when starting. (#3539 and #3960).
• Other small fixes and improvements.

PipeWire

• Fix a bug where renegotiation would sometimes fail to deactivate link.
• Fix an fd leaks and confusion in the protocol.

modules

• Fix a use-after-free in the rt module when stopping a thread.

SPA

• Fix bug where the mixer would not be synced correctly after selecting
• a port, leaving the audio muted. (#4084)
• Fix a compilation issue with empty initializers. (#4317)
• Backport v4l2 systemd-logind support to avoid races when starting. (#3539 and #3960).
• Fix a potential crash when cleaning ALSA nodes.

JACK

• Align buffers to the max cpu alignment in order to allow more optimizations.

Fixed a bug that could cause suspend/resume to fail when using the NVreg_PreserveVideoMemoryAllocations option: https://github.com/NVIDIA/open-gpu-kernel-modules/issues/472 Fixed a bug that caused the cursor image to be truncated on Gamescope: https://github.com/ValveSoftware/gamescope/issues/1099 Re-enabled GLX_EXT_buffer_age on Xwayland. This extension had been previously disabled on Xwayland due to a bug which is now fixed. Added support for mmap of exported DMA-BUF objects. Reduced some cases of stutter with OpenGL syncing to vblank while using GSP firmware. Fixed a regression that could cause some applications to exit due to resource exhaustion on some GPUs while using GSP firmware. Added several new per-plane and per-CRTC vendor-specific properties to nvidia-drm. These properties may be used by Wayland compositors to program the GPU's color pipeline for HDR hardware acceleration. Introduced a driver optimization to mitigate the performance loss from the 'd3d9.floatEmulation' option in DXVK. Fixed a bug that caused FarCry 5 running through DXVK to display a black screen. Updated the framelock settings page of the nvidia-settings control panel to use the GTK3 theme text color rather than defaulting to white for the text color, improving legibility with some themes. Fixed some performance regressions that were observed with Vkd3d 2.9. Fixed a bug that could cause flickering in some applications when using Unified Back Buffer (UBB). Fixed a bug which could cause incorrect and/or washed out colors to be displayed with HDR scanout: https://bugs.kde.org/show_bug.cgi?id=482780 Implemented support for VK_EXT_depth_clamp_control. Fixed a bug which could cause applications using GBM to crash when running with nvidia-drm.modeset=0. Fixed a bug that could cause kernel crashes upon attempting KMS operations through DRM when nvidia_drm was loaded with modeset=0.

Ubuntu 24.10 is available to download and install from the official website. It ships with the Linux 6.11 kernel and the latest GNOME 47 desktop enviroment. This version switches to Wayland by default for hardware with NVIDIA graphics, matching the previous Xorg transition for Intel and AMD graphics users, and uses the open-source NVIDIA 560 kernel modules by default on supported hardware. The kernel also has kdump-tools, which enables kernel crash dumps by default. This helps streamline troubleshooting by automatically capturing critical data after a crash.

Canonical also said in its blog post, "For gamers, significant improvements have also been made to the compatibility of the Steam snap, with an expanded permissions model and improved NVIDIA driver support. The Steam snap also bundles gaming-specific Mesa PPAs to deliver optimized performance out of the box when combined with the low latency settings enabled in the latest kernel."

Updates are also visible in the Ubuntu Dock, which better handles Progressive Web Applications. The OpenJDK 21 and OpenJDK 17 packages in Ubuntu have also changed and are now TCK (Technology Compatibility Kit) certified on amd64, arm64, s390x, ppc64el, and armhf. Passing the TCK tests means the OpenJDK packages for version 17 and version 21 on Ubuntu are compliant with the Java SE specification for their corresponding versions.