help-circle
rss
HDMI Forum Rejects Open-Source HDMI 2.1 Driver Support Sought By AMD - Phoronix
> For three years there has been a bug report around 4K@120Hz being unavailable via HDMI 2.1 on the AMD Linux driver. The wait continues...
fedilink

Can Linux be dual booted on a computer with Windows?
I have a Lenovo Yoga running Windows 10 on a 1TB SSD and at some point will probably have to upgrade it to Windows 11. I use it for school and have to keep Windows on it for now because of what I'm currently doing. I want to start getting into Linux in hopes of making the switch sometime down the line. Is partitioning the disk and dual booting Windows/Linux a thing and is it possible/easy to do? If so, what distro would anyone recommend? (I've heard good things about Mint). Back in the day I had gotten bored one night, installed Ubuntu on an external drive and played around with it a very tiny bit before forgetting about it, but that's the extent of my Linux knowledge, so kindly keep explanations ELI5 :) Edit: Thank you everyone! You've given me lots of good advice and knowledge, some terms to Google, and some good places to start. I appreciate it! Looking forward to joining the wonderful world of Linux!
fedilink

Are there any Windows-exclusive programs you use?
I had to test/fix something at work and I set up a Windows VM because it was a bug specific to Windows users. Once I was done, I thought, “Maybe I should keep this VM for something.” but I couldn’t think of anything that wasn’t a game (which probably wouldn’t work well in a VM anyway) or some super specific enterprise software I don’t really use. I also am more familiar with the Apple ecosystem than the Microsoft one so maybe I’m just oblivious to what’s out there. Does anyone out there dual boot or use a VM for a non-game, non-niche industry Windows exclusive program?
fedilink

[Q] Estimate laptop power consumption.
Hello everyone ! I have no idea if I’m in the right community, because it’s a mix of hardware and some light code/command to extract the power consumption out of my old laptop. I need some assistance and if someone way more intelligent than me could check the code and give feedback :) **Important infos** - 12 year old ASUS N76 laptop - Bare bone server running Debian 12 - **No battery** (died long time ago) Because I have no battery connected to my laptop It's impossible to use tools like `lm-sensors`, `powerstat`, `powertop` to output the wattage. But from the [following ressource](https://www.baeldung.com/linux/power-consumption) I can estimate the power based on the Energy. ``` time=1 declare T0=($(sudo cat /sys/class/powercap/*/energy_uj)); sleep $time; declare T1=($(sudo cat /sys/class/powercap/*/energy_uj)) for i in "${!T0[@]}"; do echo - | awk "{printf \"%.1f W\", $((${T1[i]}-${T0[i]})) / $time / 1e6 }" ; done ``` While It effectively outputs something, I'm not sure if I can rely on that to estimate the power consumption and if the code is actually correct? :/ Thanks :).
fedilink

Laptop not working after installing nimdow
I have installed nimdow window manager. I have auto-login enabled. Nimdow is the default option. The only options I have at boot are (from the bootloader): default, timeout, edit, resolution, print and help (help is not working). How am I supposed to go back to GNOME or disable auto-login? I tried accessing the recovery shell, but I can't access it by spamming escape. Someone PLEASE help. Google Bard is useless.
fedilink


Fedora 40 Will Enable Systemd Service Security Hardening
# Summary Improve security by enabling some of the high level systemd security hardening settings that isolate and sandbox default system services. # Benefit to Fedora Fedora services will get a significant security boost by default by avoiding or mitigating any unknown security vulnerabilities in default system services.
fedilink

Question about the order of FDE steps with LUKS and LVM
I'm setting up FDE and wonders which one is better. "LVM over LUKS" or "LUKS over LVM"? Or something else? Does one is definitely better then the other? What are your preference? Thanks.
fedilink



I’m relatively unfamiliar with Linux. I’m getting a ThinkPad T460 and want to install Mint on it. Is there anything about the T460 I should know?
It's probably been 15 years since I've used Linux and Mint seems to be the recommended distro for people who aren't all that familiar with Linux like me, but I didn't know if there was anything I should know with this ThinkPad model that anyone is familiar with. My searching around shows people saying everything from it was painless to install to they had tons of issues and I have no idea how common either one is. So any advice would be appreciated. Thanks!
fedilink


I just thought it was funny. And i hope to see a new version of this someday.
fedilink

The robustness of Linux is widely acknowledged, but it can’t quite match the microsecond management of a real-time operating system (RTOS) for time critical situations such as CNC machine instructions, vehicular control, or health sensor collection. If your software must record, manage, or control events within a narrow and precise time window and you’re invested in Linux for core development, you can consider some of these strategies for handling time-critical tasks without abandoning your familiar environment.
fedilink

Questions about Linux-Linux dualboot
So I've had enough from partitioning my HDD between Linux and Windows, and I want to go full Linux, my laptop is low end and I tend to keep some development services alive when I work on stuff (like MariaDB's) so I decided to split my HDD into three partitions, a distro (Arch) for my dev stuff, a distro (Pop OS) for gaming, and a huge shared home partition, what are the disadvantages of using a shared home (yes with a shared profile, I still want to access my Steam library from Arch if I want that) Another thing that concerns me is GRUB, usually when I'm dualbooting with Windows, the Linux distro takes care of the grub stuff, should only a single distro take care of GRUB? or I need to install "the grub package" on both? Do both distros need separate boot partitions? Or a single one for a single distro (like a main distro) will suffice? Another off topic question, my HDD is partitioned to oblivion, can I safely delete ALL partitions? Including the EFI one? I'm not on a MacBook, a typical 2014 Toshiba that's my laptop
fedilink

What should I do with a spare elitedesk sff?
I already have a nas running on one. I already have a Kodi/HTPC desktop. Running endeavor w/ KDE. I was going to put regular arch on it but was wondering if anyone had some other ideas.
fedilink


  • Lemmy
  • edit-2
    1d
How do you remove the restraints from LLMs?
Hello, I'm currently using GPT4All on Debian, I was wondering, how do you get the AI to do whatever you want? I'm using the Nous Hermes 2 Mistral DPO model.
fedilink

Neat factor
I've messed around with Linux before, mostly in VMs, but I'm looking to switch over from Windows permanently on my laptop because I think Linux is cool. Most people in this community talk about pros and cons of this distro or this other distro, but I'd like to hear your opinions based on entirely subjective factors. I think Arch is neat, I think Ubuntu isn't as neat, why? Who knows. Tell me about how you chose a specific distro because you thought the name was cool or because it ships with some completely unknown utility no one uses.
fedilink

Serving my blog posts as Linux manual pages | James’ Coffee Blog
Reading this blog post made my day :)
fedilink


Hello, I am trying to boot and install Linux mint onto a desktop Intel CPU with Nvidia gpu and I have been sitting here (notice the little white line)for 20+ minutes now. I can boot into compatibility mode and did that successfully and installed but I am not sure if I installed a different version since I booted into compatibility mode (only reason I think this is that it could not detect more than one monitor at a time after install). Do I just have to wait? Thanks Solution: in grub screen when selecting what to boot to, press e to edit boot commands and add ```nvidia-drm.nomodset=1``` at the bottom and then continue to boot. You will need to do this once more after installing and rebooting. Then install Nvidia drivers and reboot once more and you are good to go.
fedilink



Today the [KDE Community](https://kde.org/) is announcing a new **[najor release of Plasma 6.0, and Gear 24.02](https://kde.org/announcements/megarelease/6)**. KDE Plasma is a modern, feature-rich desktop environment for Linux-based operating systems. Known for its sleek design, customizable interface, and extensive set of applications, it is also open source, devoid of ads, and makes protecting your privacy and personal data a priority. With Plasma 6, the technology stack has undergone two major upgrades: a transition to the latest version of the application framework, Qt 6, and a migration to the modern Linux graphics platform, Wayland. They will continue providing support for the legacy X11 session for users who prefer to stick with it for now. The new version brings the new windows and desktop overview, improved colour management, a cleaner theme, more effects, better overall performance, and much more.
fedilink

  • Fin
  • English
  • 1d
Using Plasma 6’s new wallpaper to spread the news about KDE’s big releases.
I want more people to know about this big release, also to help support and spread Linux *without spending a dime*. You don't need to change your Desktop Environment or Operating Systems. Especially if you are a content creator please show the wallpapers for your viewer in the next 1 or 2 or more uploads. The wallpaper can be downloaded on the link below. https://kde.org/announcements/megarelease/6/
fedilink


vSphere+Debian+KDE Plasma=Crash?
I needed a test VM at work the other day so I just went with Debian because why not, during the install I chose KDE plasma as the DE. I did nothing else with it after installing it and after leaving it alone for a while (somewhere between 20-60 minutes) the CPU useage shot up to the point vSphere sent out an alert and the VM was unresponsive (the web console just showed a blank console which I couldn't type in) It did this every time I booted the VM. It seems to be the combination of vSphere Debian and KDE that causes this as I installed GNOME on the same VM and it was fine. I also created another Debian VM this time choosing GNOME during the install and that was also fine, until I installed KDE on that and then it started doing the same thing. I also created an Arch VM with KDE and that didn't have any issues. Any idea why this combination causes issues? Journalctl output of the last boot from both Debian VMs below: Original VM: https://text.is/032Z Secondary test VM: https://text.is/JR45
fedilink

As you can see in the picture, no input device is detected. I already went and installed pavucontrol and played around in the settings, changed the profile, etc, etc, no luck. I already went through the OpenSuse documentation for diagnosing sound problems and didn't find anything that would help. When I enter `cat /proc/asound/cards` in the terminal I get ` 0 [Generic ]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xc07c8000 irq 72 1 [Generic_1 ]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xc07c0000 irq 73 ` and when I enter `lspci -v | grep -i audio` I get `pcilib: Error reading /sys/bus/pci/devices/0000:00:08.3/label: Operation not permitted 04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt Radeon High Definition Audio Controller 04:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor (rev 60) 04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller` According to alsamixer my chip is a Realtek ALC287. I am running the latest updates on everything including the kernel (did try different kernel but did not fix the issue). Any suggestions would be appreciated. Edit: just boosted into Linux Mint with a flash drive and I don't have any mic input over there either. I'm assuming this has to do with some driver issue? For the record, I am dual booting and the mic works fine on Windows.
fedilink

(SOLVED) Linux Laptop Gets Stuck on Black Screen After Suspending, No Way to Use Unless Restarted With Power Button
Recently bought a new laptop that comes with an AMD Radeon gpu and installed OpenSuse Tumbleweed on it which I had installed on my previous laptop as well but never had issues with suspending and resuming. However, with the new laptop, I am unable to resume after suspending or closing the lid unless I force it to shut down by holding the power button which is a major inconvenience. I'm also dual booting alongside Windows and have secure boot enabled and have the Linux and Windows partitions encrypted if that's what's causing it *which I doubt since this is the same setup I had on my old laptop* Any suggestions or advice would be greatly appreciated. Edit: I was able to figure out that it does not suspend at all when I close the lid or click the suspend button on Gnome. Only found this out because when going through YaST Services Manager and manually starting systemctl suspend, the laptop suspends just fine and wakes back up. So I'm starting to think it's more of a systemd issue? Any inputs? Edit: turns out it was an issue with the official opensuse built kernel not sitting well. Downloaded a community version from the opensuse repository and it works fine. Very odd
fedilink

I can’t change my /home location, and it’s driving me mad
For the past week, I've been trying to switch my */home* partition from my 500GB nvme to my 1TB sata ssd. I've been asking and receiving help from people in my previous post, but I keep hitting wall after wall in making it work and I seem to be missing a step. Big thank you to @pixelscript@lemmy.ml, @NateSwift@beehaw.org, for replying to my comments and helping me along. **Previous post:** [I finally installed Linux, but I'm having a mixed experience](https://lemmy.ml/post/12329332) **Context:** ``` OS: Fedora Linux 39 (KDE Plasma) x86_64 Kernel: 6.5.6-300.fc39.x86_64 DE: Plasma 5.27.8 WM: Kwin CPU: AMD Ryzen 5 5600X GPU: Nvidia Geforce GTX 1660 ``` I have a 500GB nvme which I want to have my entire */* stored within. And I have a 1TB sata ssd which I want to have my */home* to be stored in. I've tried many of the steps some helpful people here on lemmy have detailed, and though it's gotten me closer to getting it right, but I still can't seem to login when I switch my *fstab*. **Allow me to go through every step I've done so far.** I reinstalled fedora, hoping I could separate my */home* in the installer. No such luck, anytime I switched my */home* partition into the 1TB drive my entire root directory would follow it. I decided to do the auto install on my nvme and do it manually when it's fully installed. So just to be clear I am starting from a clean install nothing except neofetch and vim installed. I created two new directories directly in */*. They were */new_home* and */old_home*. I formatted my 1TB disk, partitioned it, and then formatted the partition into an ext4, 931.5 G partition. I mounted it to */new_home* ``` NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS sda └─sda1 ext4 1.0 f56df020-2420-4b0c-af4d-2c4c6a56a0b0 718.4G 16% /new_home ``` From here I ran the command `sudo rsync -a /home/adelie/new_home`. *this is why the current available space is 718.4G.* I also added a new file to */new_home* called confirm.txt in order to tell which was which at a glance. I check the permissions and ownership of both */home* and */new_home* with `ls -la` they were identical. ``` adelie@localhost-live:/new_home$ ls -la /new_home total 8 drwxr-xr-x. 3 root root 4096 Feb 27 11:06 . dr-xr-xr-x. 1 root root 204 Feb 25 21:13 .. drwx------. 15 adelie adelie 4096 Feb 27 11:11 adelie adelie@localhost-live:/new_home$ ls -la /home total 0 drwxr-xr-x. 1 root root 12 Feb 25 21:01 . dr-xr-xr-x. 1 root root 204 Feb 25 21:13 .. drwx------. 1 adelie adelie 348 Feb 27 11:25 adelie adelie@localhost-live:/new_home$ ``` The story is the same inside the $USER files, the files and directories are identical and so are there permissions and ownership. I added */dev/sda1* to fstab to auto boot both drives. ``` UUID=d5877671-6a39-4d96-9a2a-514b6007a59b / btrfs subvol=root,compress=zstd:1 0 0 UUID=ed92de40-2403-4365-9b5c-eb10d519757c /boot ext4 defaults 1 2 UUID=02E9-123A /boot/efi vfat umask=0077,shortname=winnt 0 2 UUID=d5877671-6a39-4d96-9a2a-514b6007a59b /home btrfs subvol=home,compress=zstd:1 0 0 UUID=f56df020-2420-4b0c-af4d-2c4c6a56a0b0 /new_home ext4 defaults 1 2 ``` At this point I haven't changed the boot path for */home* yet. When I rebooted, everything worked as expected. When I entered the KDE login screen it let me go into my desktop when I inputted my password correctly. After this I decided to swap them. ``` UUID=d5877671-6a39-4d96-9a2a-514b6007a59b / btrfs subvol=root,compress=zstd:1 0 0 UUID=ed92de40-2403-4365-9b5c-eb10d519757c /boot ext4 defaults 1 2 UUID=02E9-123A /boot/efi vfat umask=0077,shortname=winnt 0 2 UUID=d5877671-6a39-4d96-9a2a-514b6007a59b /old_home btrfs subvol=home,compress=zstd:1 0 0 UUID=f56df020-2420-4b0c-af4d-2c4c6a56a0b0 /home ext4 defaults 1 2 ``` When I entered into the KDE login screen, anytime I inputted my password correctly it would kick me back to the login screen within the second. At this point I assumed it was a KDE issue and that I was missing a step in order to login correctly. I read a comment explaining *TTY*, and that I should try logging in from there to confirm if it was a KDE issue or not. When I tried it I ended up with this. ``` Fedora Linux 39 (KDE Plasma) Kernel 6.5.6-300.fc39.x86_64 on an x86_64 (tty3) Localhost-live login: adelie Password: Last login: Tue Feb 27 xx:xx:xx on tty3 -- adelie: /home/adelie: change directory failed: Permission denied Logging in with home = "/". ``` From my root account I checked */home* and */old_home*, and */home* contained *confirm.txt*, meaning that everything mounted properly, I then changed the fstab back to what is was originally. This is where I'm at now. I'm totally lost on what step I missed. I'd like to get this working in order to actually be able to use my computer, as I am committed to changing my */home* directory before making any major changes or installs. If anybody has any idea on what I missed please feel free to pitch in. ***Update: The issue was SELinux. My SELinux contexts were bad and were denying me access to my own data. I reset the context with this command,** `restorecon -Rv /home/` **I'd like to give a big thanks to,** /u/shininghero@kbin.social; for pointing out SELinux as a possible issue. /u/burrito@sh.itjust.works; for providing the command to fix this issue. /u/kbal@fedia.io; for being so patient with me, and helping me go through the list of possible issues.
fedilink

Btw there is [skim](https://github.com/lotabout/skim), a Rust fzf replacement that is in most repos!
fedilink


Welcome to the monthly update for openSUSE Tumbleweed for February 2024. This month we get one more day in February because of Leap year, but here is what we have for the month. This blog aims to provide readers with an overview of the key changes, improvements and issues addressed in openSUSE Tumbleweed snapshots throughout the month. Should readers desire a more frequent amount of information about openSUSE Tumbleweed snapshots, readers are advised to subscribe to the [openSUSE Factory mailing list](https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/). **New Features and Enhancements** - [Linux Kernel](https://www.kernel.org/): February brought updates to the Linux kernel, progressing through versions 6.7.2 to 6.7.6. These updates focus on enhancing memory management, addressing some security vulnerabilities, and introducing support for new hardware models, ensuring improved compatibility and performance across various systems. - Fixes for various issues, including null-pointer dereference in powerpc/mm, incorrect node setting for arm64 irq, and build errors in powerpc architecture. - Correcting the node assignment for VMAP stack in the arm64 irq module. - Fix for a null-pointer dereference in pgtable_cache_add in the powerpc/mm module. - Fixes for various issues in filesystems like ext4 and JFS. - Ensuring proper handling of NMIs during very early boot in the x86/boot module. - New hardware support or models: - Colorful X15 AT 23 Laptop - [KDE Frameworks](https://kde.org/announcements/frameworks/5/5.115.0/): Update for version [5.115.0](https://kde.org/announcements/frameworks/5/5.115.0/). - xtra CMake Modules: The ECMUninstallTarget now ports generated code away from deprecated exec_program, enhancing compatibility and maintainability. - KHolidays: Adds [St Brigid’s Day](https://en.wikipedia.org/wiki/Imbolc). - [KIO](https://api.kde.org/frameworks/kio/html/index.html): Once again KDirModel, allows expanding network directories in file picker. - [prison](https://github.com/KDE/prison) : Enables exceptions for videoscannerworker.cpp. - [Mesa](https://www.mesa3d.org/): Updates to 23.3.6 - zink: Addresses flickering artifacts in Selaco, broken colors/dual-source blending on [PinePhone Pro](https://pine64.org/devices/pinephone_pro/), and fixes sparse bo placement. - panfrost: Resolves graphical artifacts on T604 (T600), fixes intermittent compiler failures when building valhall tests, and pads compute jobs with zeros on v4. - radeonsi: Fixes unsynchronized flips/tearing with KMS DRM rendering on 780M and addresses heavy corruption in Amnesia: The Dark Descent. - VK: Various fixes for flaky tests, fullscreen “banding” artifacts in Age of Empires IV, and failures in dEQP-VK pipeline tests. - [systemd](https://freedesktop.org/wiki/Software/systemd/): Updates to version 254.9. - vconsole-setup: Resolved issue where vconsole-setup would fail if the only found vc is already used by plymouth. - systemd-testsuite: Dependency updated to “qemu” instead of “qemu-kvm”, the latter being obsolete. - test/test-shutdown.py: Option added to display test I/Os in a dedicated log file. - [man pages](https://manpages.opensuse.org/): Documentation update to include ranges for distributions config files and local config files. - libbpf: Version of libbpf dlopened by systemd updated (weak dependency). - [glibc](https://www.gnu.org/software/libc/): Updated from version 2.38 to 2.39, - PLT Rewrite: Introduction of a new tunable, glibc.cpu.plt_rewrite, allows for enabling PLT rewrite on x86-64 architectures. - Sync with Linux Kernel 6.6: Synchronization with Linux kernel 6.6 shadow stack interface. - New Functions: Addition of new functions on Linux, including posix_spawnattr_getcgroup_np, posix_spawnattr_setcgroup_np, pidfd_spawn, pidfd_spawp, and pidfd_getpid. - scanf-family functions: Support for the wN format length modifiers for arguments pointing to specific types. - Memory Allocation Tunable: Introduction of a new tunable, glibc.mem.decorate_maps, for adding additional information on underlying memory allocated by glibc. - ISO C2X: Inclusion of the <stdbit.h> header from ISO C2X. - AArch64: Addition of new symbols to libmvec on AArch64. - ldconfig Enhancements: ldconfig now skips file names containing specific characters and patterns. - Dynamic Linker Improvements: The dynamic linker calls the malloc and free functions in more cases during TLS access if a shared object with dynamic TLS is loaded and unloaded. - [Cups-Filters](https://www.cups.org/): Updates to version 1.28.17 - Improved Printer Capability Discovery: Enhancements to more reliably discover all printer capabilities from driverless printers, particularly borderless printing. This includes preferring Apple Raster over PWG Raster or PCLM formats. - PPD Generator Optimization: The PPD generator now creates only one *cupsFilter2 line for raster, utilizing the most desirable/reliable format, usually Apple Raster. - Media Database Handling: Enhancements in handling media-col-database and media-col-ready IPP attributes separately if needed, revealing important functionality like borderless printing. - Margin Alternatives Consideration: Consideration of all margin alternatives when generating PPD files for driverless printers, ensuring the discovery of borderless functionality for many printers. - Image Printing Enhancements: Images are now printed in their original size with “print-scaling=none”, and deprecated data types for reading TIFF images have been replaced with modern equivalents. - [openvpn](https://openvpn.net/): Updates to version 2.6.9 - Enhanced Logging: SSL alerts are now logged more prominently, improving visibility into SSL-related issues. - Documentation Improvements: Clarifications and additions to documentation, including the documentation of the tls-exit option as a primarily test option. - Code Cleanup: Removal of unused function prototypes and redundant code, ensuring cleaner codebase and improved maintainability. - Error Handling: Addition of missing error checks and enhancements to error messages for better debugging and troubleshooting. - Security Enhancements: Implementation of the --tls-export-cert feature and addition of checks for TLS 1.0 PRF availability, improving security measures. - Configuration Clarifications: Clarifications regarding the tls-crypt-v2-verify option and removal of redundant options like --tls-export-cert. - Library Compatibility: Support added for newer versions of dependencies like mbedtls 3.x.y, with TLS 1.3 support disabled. **Security Updates** This month’s updates include critical security patches and bug fixes for [glibc](https://www.gnu.org/software/libc/), [GStreamer](https://gstreamer.freedesktop.org/), [Salt](https://saltproject.io/), [Xen](https://xenproject.org/) and many other packages. **Bug Fixes** - [glibc](https://www.gnu.org/software/libc/): [Had a few Common Vulnerabilities and Exposures](https://en.wikipedia.org/wiki/Common_Vulnerabilities_and_Exposures) fixed. [CVE-2023-6246](https://www.suse.com/security/cve/CVE-2023-6246.html), [CVE-2023-6779](https://www.suse.com/security/cve/CVE-2023-6779.html), which was a buffer overflow, [CVE-2023-6780](https://www.suse.com/security/cve/CVE-2023-6780.html), which was an integer overflow, both that lead to an incorrect calculation of the buffer size. - [GStreamer](https://gstreamer.freedesktop.org/): [CVE-2024-0444](https://www.suse.com/security/cve/CVE-2024-0444.html) made it possible for a malicious third party to trigger a crash in the application. - [Salt](https://saltproject.io/): [CVE-2024-22231](https://www.suse.com/security/cve/CVE-2024-22231.html) was vulnerable to a directory traversal attack and [CVE-2024-22232](https://www.suse.com/security/cve/CVE-2024-22232.html), with a specially crafted url, could lead to a directory traversal in the salt file server. - [Xen](https://xenproject.org/): [CVE-2023-46839](https://www.suse.com/security/cve/CVE-2023-46839.html) had a high complexity and required high privileges. - [dnsmasq](https://thekelleys.org.uk/dnsmasq/doc.html): Both [CVE-2023-50387](https://www.suse.com/security/cve/CVE-2023-50387.html) and [CVE-2023-50868](https://www.suse.com/security/cve/CVE-2023-50868.html) could allow for remote attackers to cause a denial of service. - [qemu](https://www.qemu.org/): [CVE-2023-6693](https://www.suse.com/security/cve/CVE-2023-6693.html) could allow a hacker to steal data via a network device. - [bind](https://bind9.readthedocs.io/): [CVE-2023-50387](https://www.suse.com/security/cve/CVE-2023-50387.html) was associated with a “KeyTrap” DNS flaw lets attackers overload servers remotely. The other three were [CVE-2023-4408](https://www.suse.com/security/cve/CVE-2023-4408.html), [CVE-2023-5679](https://www.suse.com/security/cve/CVE-2023-5679.html) and [CVE-2023-6516](https://www.suse.com/security/cve/CVE-2023-6516.html). - [Node.js](https://nodejs.org/en/): Multiple CVEs were fixed. These were [CVE-2024-21892](https://www.suse.com/security/cve/CVE-2024-21892.html), which let unprivileged users gain elevated rights, [CVE-2024-22019](https://www.suse.com/security/cve/CVE-2024-22019.html), which was a flaw that let attackers crash servers with malformed requests, and [CVE-2024-22017][(https://www.suse.com/security/cve/CVE-2024-22017.html), which was a path traversal bug via Buffer manipulation in an experimental feature. There was also [CVE-2024-21896](https://www.suse.com/security/cve/CVE-2024-21896.html), [CVE-2023-46809](https://www.suse.com/security/cve/CVE-2023-46809.html), [CVE-2024-21891](https://www.suse.com/security/cve/CVE-2024-21891.html), [CVE-2024-21890](https://www.suse.com/security/cve/CVE-2024-21890.html), [CVE-2024-22025](https://www.suse.com/security/cve/CVE-2024-22025.html) and [CVE-2024-24758](https://www.suse.com/security/cve/CVE-2024-24758.html), which kept Proxy-Authentication headers after redirects; upgrade as needed. **Conclusion** February 2024 for openSUSE Tumbleweed showcases a diverse range of updates and improvements across essential components. There were critical security patches for software like glibc, GStreamer and Salt. The kernel updated from 6.7.2 at the beginning of the month to 6.7.6. There were updates for KDE Frameworks, Mesa, systemd, Cups-Filters and other core components. Other significant upgrades during the month included fwupd 1.9.13, PostgreSQL 16.2, Pulseaudio 17.0, GTK 4.12.5, Python 3.11.8, RPM 4.19.1.1, Mozilla Firefox 122.0.1, PHP 8.2.16, Poppler 24.02.0, Shadow 4.14.5, binutils 2.42, Qemu 8.2.1 and, Python 3.12. Next month should see systemd 255.3 arrive in the rolling release as the package is currently in staging.. The openSUSE team encourages users to continue participating through bug reports, feature suggestions and discussions. Contributing to openSUSE Tumbleweed Your [contributions](https://contribute.opensuse.org) and feedback make openSUSE Tumbleweed better with every update. Whether reporting bugs, suggesting features, or participating in community discussions, your involvement is highly valued.
fedilink

Fedora Silverblue Live USB?
Is it not possible to run Fedora Silverblue in live boot like other distros? I wanted to test it on my laptop before installing. The laptop currently runs ZorinOS. I downloaded the ISO from the Fedora website - [here](https://fedoraproject.org/atomic-desktops/silverblue/). When I try booting from the USB it only gives me the option for installing it. **Edit:** I’m looking for a live+persistent mode. My wording wasn’t great.
fedilink


Today i was doing the daily ritual of looking at distrowatch. Todays reveiw section was about a termal called warp, it has built in AI for recomendations and correction for commands (like zhs and nushell). You can also as a chatbot for help. I think its a neat conscept however the security is what makes me a bit skittish. They say the dont collect data and you can check it aswell as opt out. But the idea of a terminal being read by an Ai makes me hesitant aswell as a account needed to use warp. What do you guys think?
fedilink

Is it worth buying the Mac keyboard for a dedicated Linux PC instead of the windows one?
What is your personal preference based on experience? I Assume because Mac is Unix and Linux is Unix based, it would be more suited, but I have no personal experience with the layout. I am willing to try something new if i hear enough merits for it, and I also find the windows layout somewhat inadequate(The grass is greener on the other side /s) I dailydrive Gnome, I am not a programmer, but i am a power user (On a tangent: Why is gnome so restrictive, it feels like its missing a ton of UI features that are trivial without a boatload of 3rd party extensions that break every update; why doesn't Win+Shift+number launch a new instance, every other DE does, why doesn't it?; I don't use KDE because I just don't like it, I feel Gnome could be way more if it just natively integrated the extensions ). aesthetically the windows key annoys me and i hate putting stickers on keyboards; I like how the mac layout looks(My very minimal experience with an in store mac-book has cautioned me away from the fisher-price OS so i don't know if it is intuitive to use)
fedilink

I would just like to preface this. This is the first blog post I've ever written, so please please please give me feedback if you can. I also didn't intend on it being here on Lemmy, but Hugo is quite a complex tool that'll take some time for me to understand. Webdev is not my cup of tea. # Introduction. About a month ago, I switched from Endeavour OS to a spin of Fedora called Fedora Onyx (Now Fedora Atomic Budgie, from now on shortened to FAB). Why? I love Arch, it was even my first distro (I am sane I promise) thanks to a friend, but it's infamous for breaking. Which it did. Time and time again. Whether I was doing something wrong or not is irrelevant now, but on every Arch or Arch-based install I've done; overtime something has caused seemingly random parts of the system to begin to break down or slow down. After 3 years of this behavior across countless installs, enough was enough. I'd played around with Atomic, otherwise known as Immutable, distros before in VMs but never used one on bare metal. I knew what I was getting into though, sandboxing and containerization left right and center, Flatpak for apps and restriction to the base directories. A routine backup later, and it was distro-shopping time. # What I looked for. I initially didn't plan on FAB nor an Atomic distro, I was actually going for NixOS (and if I were to switch from Atomic, NixOS would be my new home). But I'm of the mind of I want to use my computer more than building it, at least on the software side of things, and I know that if I had a NixOS system I'd never stop tweaking it. After trying NixOS in a VM a couple times, this constant tweaking ended up in the system breaking both times to the point where it was impossible to edit the .nix config file without chroot (and a lot of GRUB entries, a rather bit messy if you ask me). I needed a system that: - Wouldn't break without my active attempt to do so. - Was modern, had the latest versions of software available and the newest kernels (once an Arch user, always an Arch user). - Had a large community and buzz in-case I needed support. After the events of NixOS, I turned to Fedora. I've used Fedora Workstation a couple times on my laptop & desktop, and Fedora Silverblue (technically Fedora Atomic Gnome) I'd tried in a VM. Fedora Workstation fits two of those three requirements, omitting only the reliability I craved. But Fedora's Atomic spins were a perfect fit. # Budgie? Desktop Environments are incredibly subjective and no one is better than another, I don't like Gnome nor KDE simply due to the scale of them. Large enough to jokingly label those desktops as Gnome/Linux and KDE/Linux rather than GNU/Linux. This is a nightmare if you ask me, the system and the DE should be separate areas of an OS stack. Gnome's scale can be felt across the entire Linux-verse, more and more apps are being made with Libadwaita; essentially alienating anyone who doesn't use Gnome if they value consistency in the appearance of their system. KDE uses the Qt framework for UI, which causes itself to be alienated from the majority of Linux apps. So I need a small desktop that uses GTK, but has modern features and animations while being under active development. Out of the 2 remaining Fedora Atomic spins, Sway or Budgie, it has to be Budgie. I. Love. Budgie. I've used it many times in my old Arch installs and I'm constantly on the lookout for the best Budgie experience. Budgie is everything I want out of a DE, it's small, it's fast, it's modern, it's GTK, and under active development. It was also the first FOSS project I donated to! With everything backed up, the distro chosen and a USB flashed. It was time to switch. # Week 1 & 2. FAB started out exactly like most distros, you have to use Flatpak to manage all your apps otherwise going Atomic is almost pointless. FAB shipped with Gnome Software installed but again, I love consistency in the appearance of my system and so opted to use Flatpak and Flathub straight from a terminal. Gnome Software also seems to take a good minute to finish the 'Loading Software Catalogue' step, whereas the CLI faces no such issue. To install packages onto the base system, known as 'layering', you have to use a specialized package manager that supports layering on Atomic. Fedora Atomic ships with a tool called rpm-ostree that replaces dnf . I layered Xfce-Terminal, Flatseal*, Vim, Neofetch, and packages for virtualization onto my system. Your layered packages can be seen with the command: ``` rpm-ostree status ``` *The flatpak version of Flatseal didn't seem to apply any of the overrides. It started out quite nicely, I usually mount my secondary drives into /mnt/DRIVELABEL but due to the restrictions to the base directories I had to change this to /run/media/USERNAME/DRIVELABEL, not a big deal and should be expected. Gaming was obviously fine as it was on Arch. Blender did everything perfectly too, after overrides to access my projects folder. It was almost easy to forget I was on an Atomic distro. So far, I'm loving it. # Week 3. Week 3 is when things start to get interesting, Atomic distros such as VanillaOS advertise themselves as perfect for developers. I'm a hobbyist developer, I make odd projects here and there for my personal use and other automations. Week 3 is when I wanted to start a new project. Week 3 is also when I almost gave up on 'Immutable' distros. I introduced myself to Toolbox , a program that's used to create containerized images of non-Atomic distros right under your host system; like a Docker container (It actually uses Podman as the backend so it is a Docker container of sorts). Running: ``` toolbox create ``` Defaults to creating a Fedora container (I'm guessing it's Fedora server), so you have access to dnf and the total mutability of non-Atomic distros on your Atomic distro. I then proceeded to installing my editor of choice and packages for Python & Rust. I learnt a lot about how to manage development on an Atomic distro in Week 3, Toolbox advertises that it enables 'seamless' integration of software from the container and host system. In my experience, it's not quite that simple. I won't divulge into what went wrong because it's completely my fault and nothing wrong with Fedora, Atomicity or Toolbox. But to summarize the containerization was almost too much, causing me to flash a NixOS USB and plan to switch. VSCodium wouldn't see that I've installed the languages I did, nor find my font (Geist Mono Nerd Font). This put a very sour taste for Toolbox in my mouth. But the weekend came and I left my computer for a good day. I came back and wiped everything from my dev environment, even the Toolbox container. Toolbox allows you to specify what distro you want to install, so I came up with the brilliant idea of Arch. After that I proceeded to install Yay, VSCodium, Python and a couple other languages. Finally, peace at last. The trick was to install VSCodium from the Toolbox, I knew that prior to the wipe but VSCodium isn't in the Fedora repos. So now, with everything all under the Toolbox container, programming is quite a nice experience. # Week 4 & Beyond. So this is it, one month after installing and I can't see myself ever going back to a non-Atomic distro. Even using NixOS doesn't seem quite as likely now. I've grown to enjoy and embrace the sandboxing & containerization now that I've figured out what to do in order to achieve a task. The best part, my system is (mostly) identical to what it was at the start. So in theory, it'll be the same even as the years go by. Not that I'm likely to keep this exact install for years, on my desktop at least I like to try new things and ultimately end up getting bored of an install after an amount of time. So to answer the popular question right now, is Atomicity the future of the Linux desktop? I say yes, if we can make them easier for first-timers. Right now, I'd recommend everyone to use a normal distro for a while before trying Atomic distros. During setup, the two are quite distinct from each other, and doing the setup on a normal distro is required foundation for an Atomic setup. However... Do I believe anyone who has some experience using Linux should try an Atomic distro? Absolutely! Even if you never encounter breakages on a normal distro, using something Atomic if you don't have specific use-cases brings no downsides. Going Atomic definitely teaches you a lot about Sandboxing, Containerization, Linux and miscellaneous Security concepts. Plus, doesn't it just sound cool? "Yeah, I use an Atomic system." It even has a psychological benefit, I feel a stronger sense of solidarity and security from this system. Maintenance is easier, as I know where and how each app has installed itself and what it can access or do. I've layered on all the packages I could want so my base system should almost never change now beyond updates. I could even re-base to a different Fedora Atomic spin if I wanted to. So, if you've used Linux for some amount of time, I highly recommend giving Atomic a try. It's quite a unique & interesting way to use your system. If you've never used Linux, I don't recommend going straight to Atomic as there are certain new and developing concepts that are used heavily throughout the system. Do I think Atomicity is the future? Yes, I can definitely see them gaining a larger share of the Linux desktop given time. To make a reliable Linux desktop, I see almost no other solution than Atomicity that doesn't require extensive Linux experience.
fedilink

(SOLVED) OpenSuse TW Not Suspending Properly on Gnome But Sleeps Properly on KDE (Follow Up)
I made a post yesterday about how I got a new laptop and it does not suspend properly and just goes to a black screen where my only option is to force shut it down by holding the power button. After an entire day I still have not figured it out. But, I did narrow it down. TLP, drivers (it's all open source AMD), small swap partition, etc, are not the issue. After two reinstalls, I decided to install it with KDE just out of curiosity to see if it still has the problems and nope. Works just fine. Now I went ahead and installed Gnome on top of the KDE install and once again, if I try to suspend through Gnome, it fails to do so and gives me a black screen where nothing is responsive. What could be the cause of this? I also tried running on Xorg and the problem still persisted. But I'm pretty sure by now that it is a Gnome problem and not a device problem. If you want more context you can check out my previous post. Any inputs or advice would be greatly appreciated. Edit: Turns out the official OpenSuse build of kernel 6.7.6-11 does not sit well with my laptop and instead downloading and using a community version of the kernel posted on software.opensuse.org ended up fixing the issue. Very odd.
fedilink

    Create a post

    From Wikipedia, the free encyclopedia

    Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

    Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word “Linux” in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

    Rules

    • Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
    • No misinformation
    • No NSFW content
    • No hate speech, bigotry, etc

    Related Communities

    Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

    • 0 users online
    • 657 users / day
    • 1.34K users / week
    • 2.98K users / month
    • 9.27K users / 6 months
    • 1 subscriber
    • 3.63K Posts
    • 90.4K Comments
    • Modlog
    Lemmy
    A community of privacy and FOSS enthusiasts, run by Lemmy’s developers

    What is Lemmy.ml

    Rules

    1. No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia. Code of Conduct.
    2. Be respectful, especially when disagreeing. Everyone should feel welcome here.
    3. No porn.
    4. No Ads / Spamming.

    Feel free to ask questions over in: