Linux

Lately I noticed that when I want to ssh to a server using a password I need to specify -o PubkeyAuthentication=no or I won't be asked for a password and the authentication will fail (well, for all I know, setting some other option may work too).

I use password authentication only once on freshly installed servers/vms, so it's not a huge deal, but... it still bothers me (mainly because I don't remember which option to set).

Do you guys have any idea what it may be?

Host 127.*.*.* 192.168.*.* 10.*.*.* 172.16.*.* 172.17.*.* 172.18.*.* 172.19.*.* 172.2?.*.* 172.30.*.* 172.31.*.*
  LogLevel quiet
  Stricthostkeychecking no
  Userknownhostsfile /dev/null

Host *
  ForwardAgent no
  AddKeysToAgent no
  Compression yes
  ServerAliveInterval 10
  ServerAliveCountMax 3
  HashKnownHosts no
  UserKnownHostsFile ~/.ssh/known_hosts
  ControlMaster no
  ControlPath ~/.ssh/master-%r@%n:%p
  ControlPersist no

AuthorizedPrincipalsFile none
Ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
GatewayPorts no
KbdInteractiveAuthentication yes
KexAlgorithms sntrup761x25519-sha512@openssh.com,curve25519-sha256,curve25519-sha256@libssh.org,diffie-hellman-group-exchange-sha256
LogLevel INFO
Macs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,umac-128-etm@openssh.com
PasswordAuthentication yes
PermitRootLogin yes
PrintMotd no
StrictModes yes
UseDns no
UsePAM yes
X11Forwarding no
Banner none
AddressFamily any
Port 22
Subsystem sftp /nix/store/78mv13w9mgh0s0rd7rnr6ff4d7a39bpd-openssh-9.7p1/libexec/sftp-server 
AuthorizedKeysFile %h/.ssh/authorized_keys /etc/ssh/authorized_keys.d/%u
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_ed25519_key

Do you use any of the mentioned virtual network interfaces? What for?

I'm interested in using Varia since it has an option for remote however I am not seeing the option, do I need to do something different, I installed from flat hub.

I created a second partition on my main drove to install steam games, that way they persist in case I want to reinstall Linux or access from a portable windows install, but wanted it to mount on boot.

In partition manager, for some dumb reason, I presumed that flagging it as 'boot' would mean just that.

Obviously this was wrong, and now I can't unflag the drive for some reason. It says it applies the changes but just leaves it flagged.

EDIT : Appreciate all the input, never did figure out what the cause was.... Somewhere in booting between two kernels it just .. stopped being a pain in the ass .... Not my favorite type of resolution

Two weeks ago, I did some updates on my nobara desktop and ever since I've had a significant delay in any audio playing.

I've been poking at it with no luck, and am just out of ideas. Logs don't show anything worrying, running pulse audio in debug looks fine, tried reinstalling packages, tried some tweaks i found online and nothing seems to work.

Rebooting into live environments from USB shows the sound working fine so decent chance the hardware is ok.

Been administrating headless *nix systems since the 90s, finally decided to try on the desktop now that I don't have to use Windows, and .. struggling with this.

I control my media pc running Popos with a remote mouse/keyboard combo I found on Amazon and while this works pretty good, I would like a more "big picture mode" like experience that works well with using a remote.

I know theres some distros out there that are geared specifically for a media pc but I don't wanna reinstall my system. My internet is painfully slow at times and drops out frequently (yay for rural America) so even doing system updates can take a long time or just time out. I'd rather not babysit my pc to get everything working again how i want it so if I could find just a desktop environment to use that would be great. If not, such is life.

So far, Plasma bigscreen looked the most promising: https://plasma-bigscreen.org/ but any recommendations would be helpful. I've tried looking some up myself but searching the web has become pretty useless for something more niche or specific like this and I figure the good people on here would have better advice anyways.

Open TV is an ultra-fast IPTV app that uses mpv for playback.

After rewriting the app in Rust (tauri specifically) for the last 3 months, Open TV is finally on flathub 🎊🎊

The app also now supports multi sources and other niceties.

If you use hypnotix or other IPTV apps, please give my app a try!

Like the app? Please consider donating. Open TV is a completely solo effort. It would help me allocate more time to its development.

Im kinda baffled. I use lutris for launching windows games in linux and for the longest time now its worked great. Well i was playing a game and it was working fine. i closed it went and did some other stuff for an hour or so and came back. When i went to launch it suddenly its throwing errors about needing umu to launch proton even tho proton worked just fine not an hour ago. I think ok ive had issues with flatpacks before. Let me uninstall the flatpack and get the system package. I do so and now proton doesnt even appear as an option in the configure menu. I googled around and i cant find any similar issue. The thing that really baffles me is it just seems to have stopped working for no reason. I didnt update anything, didnt change anything. The Lutris on my desktop still works perfectly fine too. Its just the one on my laptop doesnt want to use proton now? Anyone experienced this and know whats up? The umu thing it mentioned at first would need to be compiled from the github and i know thats not something Lutris normally needs since i have had it working without doing that and currently do on my desktop. I guess i could manually install it anyway but i worry itll just make things worse.

Edit: Its suddenly working again i have no idea why

Plasma 6 has come into its own over the last two releases. The wrinkles that always come with a major migration have been ironed out, and it’s time to start delivering on the promises of the new Qt 6 and Wayland technology platforms that Plasma is built on top of.

Plasma 6.2 includes a smorgasbord of new features for users of drawing tablets. It implements more complete support for the Wayland color management protocol, and enables it by default. There is also improved brightness handling for HDR and ICC profiles, as well as HDR performance. A new tone mapping feature built into Plasma’s KWin compositor will help improve the look of images with a brightness or set of colors greater than what the screen can display, thus reducing the “blown out” look such images can otherwise exhibit.

When it comes to power management You can now override misbehaving applications that block the system from going to sleep or locking the screen (and thus prevent saving power), and you can also adjust the brightness of each connected monitor machine separately.

Plasma’s built-in app store and software management tool, Discover, now supports PostmarketOS packages for your mobile devices, helps you write better reviews of apps, and presents apps’ license information more accurately.

In Plasma 6.2, KDE have overhauled System Settings’ Accessibility page and added colorblindness filters. They've also added support for the full “sticky keys” feature on Wayland.

This and more in full anounncement and changelog.

Right now I use Read You on my phone to get RSS feeds and I read articles on my browser but I want to cut the time I stare at my phone throughout the day so I came up with this system:

Once a week I will look at all the feeds I follow on my PC RSS reader, select the ones I want to read during the next week and save them / export them (possibly in PDF or ePUB?) so that I can put them on my old Kindle (that has no internet access) and read them only using the kindle during the week.

This will drastically reduce the time I use my phone to first scroll and select articles and then to actually read them. Looking at a screen all day for work and also looking at a screen (phone) in my free time is not good for me and I want to change that.

If no RSS reader has that option, does anyone know of another program or firefox extension that would let me "export" web pages as pdfs or epubs?

Write is a handwriting app that works on a lot of platforms including Linux which cannot be said about most handwritten note-taking applications.

More information and demo: https://github.com/styluslabs/Write/

I've used it for uni on a Linux tablet/convertible and it worked really quite well and has some nice convenient features for note-taking.

The UI looks like it's from android 4.something though ^^'

What I really appreciate about it is that its storage format are plain SVG(Z) which are extremely compatible. All you need to view your scribbles is an SVG viewer (i.e. a web browser) which basically every computer with a GUI has. Their website is in fact mostly just the output of their own app.

I'm having trouble getting an IP address via DHCP on my HP ProLiant DL380 Gen9 server running Debian. I've tried various troubleshooting steps, but nothing seems to work.

Error messages:

• "No DHCPOFFERS received"
• "No working leases in persistent database - sleeping"
• "Activation of network connection failed" (GNOME)
• "IP configuration unavailable" (Plasma)

Hardware:

• HP ProLiant DL380 Gen9 server

Software:

• Debian operating system
• GNOME and Plasma desktop environments

Troubleshooting steps:

• Checked network cable and ensured it's properly connected
• Restarted network service
• Set /etc/NetworkManager/NetworkManager.conf managed=true

Additional information:

• Internet worked during the Debian installation process, but not after booting into the installed system.
• The problem occurs on both GNOME and Plasma desktop environments, but Plasma provides a slightly more helpful error message.

I'd appreciate any help or guidance on resolving this issue. Has anyone else experienced similar problems with DHCP on a HP ProLiant DL380 Gen9 server with Debian?

I don't know when this happened. There was a system update a few days ago which went fine. Two days ago I wanted to download something onto one of my HDDs and got an I/O error. After investigating I found out that I no longer am the owner of any of my drives and can't create/delete any files. Chmod/chown didn't help. Editing the fstab file didn't help since it had the exact same contens as when everything worked. Shuffeling exec,rw around has no effect. Mounting/unmounting didn't do anything. Phisically removing the drives also didn't work. Adding a completely new drive automatically set it to restricted. How the hell does soemthing like this happen? I don't want to do a system wipe.

Edit: Windows is to blame

It appears Windows did something to the drives the last time I used it which messed up the partitin tables and prevented Linux from mounting them correctly. After poking around in the journalctl like suggested I found an entry with the error message. Googling brought me to an arch forum post with the same problem. All that had to be done was to go back into Windows and run shutdown /s /f /t 0 in cmd/powershell. Link to the post: https://bbs.archlinux.org/viewtopic.php?id=231375

Tnx everyone for the assistance!

cross-posted from: https://beehaw.org/post/16434132

YouTube video: https://youtu.be/uScsmjvdwyo

Invidious video from YouTube without YouTube: https://inv.nadeko.net/watch?v=uScsmjvdwyo or https://invidious.nerdvpn.de/watch?v=uScsmjvdwyo

Video description:

It’s clear there are some people who don’t understand Proton. So let’s talk about it. #Proton #SteamPlay #CompatibilityLayer

00:00 Introduction
00:41 The basics of a computer
01:46 What Proton is not
03:04 What is an emulator
04:32 Proton acts like a map
05:25 Proton translates API and system calls
06:18 Proton provides a Windows-like software environment
06:55 Why are some games incompatible?
08:52 Shouldn't we demand native Linux games?
11:07 Conclusion

The RPM Package Manager (RPM) is a powerful package management system. Highlights of the version 4.20 include:

• Declarative build system support
• Dynamic spec improvements
• Guaranteed, RPM-controlled per-build directory
• Support for spec-local file attributes and generators
• Support for group membership in sysusers.d(5) files
• Proper distro-agnostic debuginfo support
• Sanitized spec comments and indentation syntax
• Sanitized --build-in-place mode
• New unshare plugin for scriptlet isolation
• Plugin API made public

Hello everyone!

I'd like to announce the start of development and the public availability of what we currently refer to as Leap 16.0 pre-Alpha. Since this is a pre-Alpha version, significant changes may occur, and the final product may look very different in the Alpha, Beta, Release Candidate, or General Availability stages. The installer will currently offer you Base, GNOME, and KDE.

Users can get our new Agama install images from get.opensuse.org/leap/16.0. The installer will currently offer you Base, GNOME, and KDE installation.

Leap 16.0 is a traditional distribution and a successor to Leap 15.6 with expected General Availability arriving in the Fall of 2025.

We intend to provide users with sufficient overlap so that 15.6 users can have a smooth migration, just like they're used to from previous releases.

Further details are available on our roadmap. The roadmap is subject to change since we have to respond to any SUSE Linux Enterprise Server 16 schedule changes.

Users can expect a traditional distribution in a brand new form based on binaries from the latest SLES 16 and community packages from our Factory development codebase.

There is no plan to make a Leap 15.7, however, we still need to deliver previously released community packages from Leap 15 via Package HUB for the upcoming SLES 15 SP7. This is why there are openSUSE:Backports:SLE-15-SP7 project and 15.7 repos in OBS.

The target audience for pre-Alpha are early adopters and contributors who would like to actively be part of this large effort. Adopters should consider booting Agama Media from time to time just to check compatibility with their hardware.

For non-contributor users, I highly recommend waiting until we have a Beta, which is expected in the late Spring of 2025.

Specifically for Agama I highly recommend using github.com/agama-project and collaborating with the YaST team on suggestions and incorporating any changes.

For the rest of the components, the workflow isn't changing; just select version 16.0 for bug submissions.

Feature requests will be reviewed every Monday at a feature review meeting where we'll convert code-o-o requests into JIRA requests used by SUSE Engineering where applicable.

The factory-auto bot will reject all code submit requests against SLES packages with a pointer to code-o-o. You can get a list of all SLFO/SLES packages simply by running osc ls SUSE:SLFO:1.1:Build.

Just for clarification SLFO, SUSE Linux Framework One, is the source pool for SLES 16 and SL Micro 6.X.

I highly recommend using code-o-o to co-ordinate larger community efforts such as Xfce enablement, where will likely need to update some of SLES dependencies. This allows us to share the larger story and better reasoning for related SLES update requests. The list of features is also extremely valuable for the Release article.

For quality control, we have basic test suites based on Agama installations in Leap 16.0 job group. Later, we plan to rework the existing Leap 16.0 Images job group for testing the remaining appliance images.

The project where we maintain community packages is subject to change as we have not fully finalized yet how to make Package HUB; we may use a similar structure with Backports as in 15.3+).

Further test suite enablement is one of the areas where we currently need the most help. Related progress.opensuse.org trackers poo#164141 Leap 16.0 enablement and poo#166562 upgrade from 15.6.

Another area where you can help is new package submissions and related maintainer review of package submissions to Leap 16.0. These reviews make sense as we'd like to check with maintainers whether that software in a given version makes sense for inclusion into Leap 16.0, rather than blindly copying all packages over.

Do you want to help us on this front? Spread the news and feel free to join the #openSUSE_Marketing Telegram channel(https://t.me/openSUSE_Marketing)! https://en.opensuse.org/openSUSE:Marketing_team

Many thanks to all who helped us to reach this point.

Lubos Kocman on behalf of the openSUSE Release team

I've been using volumeicon for a long time, to enable the audio hotkeys on my laptop. But the problem is that if you plug in a USB or bluetooth headset, it doesn't automatically switch to it as the default. You'd have to kill the service and restart it.

So I wrote a script that can offer me all the same functionality, and just mapped my audio hotkeys in my WM.

Thought someone might find the source useful.

Can I use it fully offline?

How do I back it up to USB drive?

What does the day-to-day operation of Pass compared to Keepass look like?

I am trying to learn it as I want to use it, as I think that keepass is bloated for my use case, and I would appreciate any help here.

Hi folks,

I have Alpine Linux installed in an encrypted LUKS partition. I came across this tutorial which shows how to setup a key in a USB drive and when the drive is inserted and the computer booted, the LUKS partition auto-unlocks with the key on the USB drive.

https://askubuntu.com/questions/1414617/configure-ubuntu-22-04-zfs-for-automatic-luks-unlock-on-boot-via-usb-drive

I would like to setup the same thing but I do not have Alpine linux installed on ZFS, so I'm looking for ways to adapt the instructions.

So far, what I've done is:

1. I've setup the key on the usb stick and I can unlock the LUKS partition with that key.
2. create a /etc/mkinitfs/features.d/usb-unlock.sh script with the following content:

(the echo to /dev/kmesg was to check whether the script did indeed run at boot by trying to print to the kernel messages but I can't find anything in the kernel messages).

#!/bin/sh

echo "usb-unlock script starting..." > /dev/kmsg

USB_MOUNT="/mnt/my-usb-key" # The USB stick mounting point
LUKS_KEY_FILE="awesome.key"  # The name of your keyfile on the USB stick

# Search for the USB stick with the key
for device in $(ls /dev/disk/by-uuid/*); do
    mount $device $USB_MOUNT 2>/dev/null
    if [ -f "$USB_MOUNT/$LUKS_KEY_FILE" ]; then
        # Unlock the LUKS partition
        cryptsetup luksOpen /dev/sda3 cryptroot \
            --key-file "$USB_MOUNT/$LUKS_KEY_FILE" && exit 0
    fi
    umount $USB_MOUNT
done
echo "No USB key found, falling back to password prompt." # this message never appears, despite not having found the key on the usb stick

echo "usb-unlock script ending." > /dev/kmsg

3. I added usb-unlock to the features in mkinitfs.conf:

mytestalpine:~# cat /etc/mkinitfs/mkinitfs.conf 
features="ata base ide scsi usb virtio ext4 cryptsetup keymap usb-unlock"

4. run mkinitfs to rebuild the initramfs. Then reboot to test the implementation, which was unsuccessful.

What am I missing / doing wrong? Thank you for your help!

Edit: forgot to add step 4

cross-posted from: https://lemmy.kde.social/post/2098933

I wanted a podcast player that looks great and could be used in my region, with Fedora. So I found Musicpod as flatpack and downloaded it. But when I open it, and want to add podcast it says "It looks like your computer isn't connected to the internet" so I can't search. My internet is connected, I use other apps, without problem. Its on Fedora 40, with VPN on. Anything I have to change,or do you recognize this issue?