Linux

Randomly on my laptop screen this appears and debian just freezes. Sometimes these vertical lines don't appear and system freezes anyway. Its just random. How do i identify if this is hardware or software issue? and then how to identify exact piece of hardware or software causing this problem.

Hi I'm looking for a retro style desktop environment (or maybe just some skin or something) for my Debian workstation. Preferably something that looks like Mac OS 9.

This is my second "I feel like a complete idiot" question of the week, so thank you for your patience.

How does one find an app-id, e.g., for setting up window rules in my window manager (River)? For example, if I'm using Nautilus as a file manager and I wanted to have the Nautilus Previewer window float by defining a River WM rule, I can do every bit of that trivially, other than identifying the app-id. (In this case, I believe it's org.gnome.NautilusPreviewer, but I'm looking for a general case.) Please note this question is about Wayland and not X.

I dropped into GNOME and viewed active windows with Looking Glass (lg), but that seems like a silly workflow just to ID a window.

NixOS' influence and importance at pushing Linux forward into the (previously) unexplored landscape of configuring your complete system through a single config file is undeniable. It's been a wild ride, but it was well worth it.

And although it has only been relatively recently that it has lost its niche status, the recent influx of so-called 'immutable' distros springing up like mushrooms is undeniably linked to and inspired by NixOS.

However, unfortunately, while this should have been very exciting times for what's yet to come, the recent drama surrounding the project has definitely tarnished how the project is perceived.

NixOS' ideas will definitely live on regardless. But how do you envision NixOS' own future? Any ETA's for when this drama will end? Which lessons have we learned (so far) from this drama? Are there any winners as a result of this drama? Could something like this happen to any distro?

In case you're out of the loop. Though, there's a lot that has transpired since but which hasn't been rigorously documented at a single place; like how 4 out of 5 NixOS board members have quit over the last 2 months or so.

Hi all, I've recently switched over to Linux Mint from Windows 10 and I'm having trouble installing a CH340 driver from Sparkfun. I've managed to unzip the contents and have it in this location: /home/user/Downloads/CH341SER_LINUX. I've tried running the files using the ./ command for both the ch34x.c and Makefile but ran into a bash issue which I'm stuck trying to figure out. Could someone please tell me how to make it work? I've already looked up a couple of different videos on Youtube but they kind of skip the explanation of how to install this driver on Linux in favor of Windows and MacOS.

Please see the attached image for the response I get in the terminal.

UPDATE: It turns out I had a bad micro USB cable. Most of the ones I was using to connect to an ESP32 board were charge only. Mint apparently had the driver for this all along. Thanks for the help everyone.

The cursor randomly enlarges every now and then. Anyone else experiencing the same problem? If so, have you solved it?

Could this be due to using different containers? I use flatpaks for everything apart from a few exceptions where I use distrobox, and in these the Plasma cursor is slightly different, but it doesn't justify the bug but just a different version of the cursor.

should i be worried installing these two? what does it mean though?

(these are captured from Pop! OS software manager)

I want to revive an old Lenovo laptop with an AMD A6 2.6GHz and 4GB ram, what would be the best option for a DE?

I am new to Linux and wondering about having multiple distros on the same SSD and the best way to partition them. My current plan is to try Nobara Linux while having Linux Mint as a backup. By default I think that both the Mint and Nobara installers will create a partition for /boot and a combination / & /home partition. (Also, the SSD I'm using also has a Windows 10 installation.)

My main question: would running both installers this way could potentially cause any issues with each distro having a separate boot partition on the same SSD?

Bonus question: I plan to have an additional partition for shared data between the 2 distros (documents, pictures, games, etc.). If I recall correctly, by default Mint uses EXT4 and Nobara uses BTRFS for their formatting. Will it make a significant difference for picking one format over the other for the shared partition?

Where can I find i3/Sway themes, aside from the Sway Wiki?

Anyone else have this issue? I thought maybe it was just my shitty surface pro 3 but it happens on my T530, T460s, and my desktop. I thought maybe it was an extension I had so I uninstalled them all except ublock. Still happening. For now I've just switched to librewolf and installed all the extensions I had on Firefox. Works fine and doesn't keep my CPU at 100% so problem solved I guess, but I'm still curious if anyone else has this issue?

My issue is that many of my remote desktop apps require knowing the IP adress of the other PC. I'm looking for a VPN that auto-discovers other devices on the same network. That way I could just "ssh" into the same IP every time, because it would be IP inside of a virtual network. Ideally I am looking a solution that does not require internet connection.

Thanks.

Edit: I should probably specify my usecase. I have a portable desktop and use VNC from a laptop to connect to it. To do that I need the IP of the desktop but that's different on a different network. This can be solved by using hostname.local as the "IP". (hostname is the "ubuntu" in "bob@ubuntu$:~/Documents") The solution is quite simple, I just haven't known about it.

Don't get me wrong. I absolutely love Fedora Atomic (Silverblue, Bazzite, Kinoite, Aurora, IOT, etc.), more than any other distro I used, and I plant to continue using it.

It never made any problems on any of my devices, and because it is pretty much indestructible and self-managing, I even planned to install it on my Mum's new laptop, in case her current one (basically a toaster with Mint on it) breaks.

But with the last days, my trust is damaged quite a bit.

First one, where I couldn't update anymore on uBlue, because of faulty key pairs. This is a huge thing for me because uBlue updates in the background, and if I wouldn't have read it here on Lemmy, I would have found out way too late, which is a security risk imo.

And now, my devices weren't able to boot anymore due to some secure boot stuff. Again, if I wouldn't have subscribed the Fedoramagazine, I would have noticed it way too late.
I was able to just boot into an older image and just paste a few commands from the magazine's post, and it was resolved in just seconds (download time not included).

Both instances were only a minor thing for ME.
But both would have been a headache if I wouldn't follow those blogs, which is a thing only nerds (like myself) do.
Nobody else cares about their OS, it is supposed to just work, hence why I use Atomic.

I don't wanna blame the devs (both j0rge/ uBlue and the Fedora team), they were very quick, transparent and offered very simple fixes.
And, being able to just boot into an older image, just in case, is something I am very thankful for, but nothing I want to depend on.

Having to be informed about stuff like this and then having to use the CLI is just a no-go for most people.

Am I over-reacting about this too much? What's your view on those things?

Hello everyone;

I'm trying to install some flatpak packages, but have been unsuccessful. For example, when I run flatpak install flathub org.libreoffice.LibreOffice it gets stuck on Looking for matches…. I tried running the command with sudo, and it worked after 3 minutes of hanging on Looking for matches…:

user@JustThinking:~$ sudo flatpak install flathub org.libreoffice.LibreOffice
Looking for matches…
Required runtime for org.libreoffice.LibreOffice/x86_64/stable (runtime/org.freedesktop.Platform/x86_64/23.08) found in remote flathub
Do you want to install it? [Y/n]: y

org.libreoffice.LibreOffice permissions:
    ipc       network               fallback-x11          pulseaudio              wayland      x11
    dri       file access [1]       dbus access [2]       bus ownership [3]

    [1] host, xdg-config/fontconfig:ro, xdg-config/gtk-3.0, xdg-run/gvfsd
    [2] com.canonical.AppMenu.Registrar, org.gtk.vfs.*
    [3] org.libreoffice.LibreOfficeIpc0


        ID                                              Branch                 Op            Remote            Download
 1. [|] org.freedesktop.Platform.GL.default             23.08                  i             flathub           < 172.2 MB
 2. [ ] org.freedesktop.Platform.GL.default             23.08-extra            i             flathub           < 172.2 MB
 3. [ ] org.freedesktop.Platform.Locale                 23.08                  i             flathub           < 360.2 MB (partial)
 4. [ ] org.freedesktop.Platform.VAAPI.Intel            23.08                  i             flathub            < 13.4 MB
 5. [ ] org.freedesktop.Platform.openh264               2.2.0                  i             flathub           < 944.3 kB
 6. [ ] org.gtk.Gtk3theme.Mint-Y-Aqua                   3.22                   i             flathub           < 114.8 kB
 7. [ ] org.freedesktop.Platform                        23.08                  i             flathub           < 227.5 MB
 8. [ ] org.libreoffice.LibreOffice.Locale              stable                 i             flathub            < 84.8 MB (partial)
 9. [ ] org.libreoffice.LibreOffice                     stable                 i             flathub           < 323.1 MB

Installing 1/9…

It stayed like this for a while (the [|] didn't change either), until...

        ID                                              Branch                 Op            Remote            Download
 1. [—] org.freedesktop.Platform.GL.default             23.08                  i             flathub               1.0 kB / 172.2 MB
 2. [ ] org.freedesktop.Platform.GL.default             23.08-extra            i             flathub           < 172.2 MB
 3. [ ] org.freedesktop.Platform.Locale                 23.08                  i             flathub           < 360.2 MB (partial)
 4. [ ] org.freedesktop.Platform.VAAPI.Intel            23.08                  i             flathub            < 13.4 MB
 5. [ ] org.freedesktop.Platform.openh264               2.2.0                  i             flathub           < 944.3 kB
 6. [ ] org.gtk.Gtk3theme.Mint-Y-Aqua                   3.22                   i             flathub           < 114.8 kB
 7. [ ] org.freedesktop.Platform                        23.08                  i             flathub           < 227.5 MB
 8. [ ] org.libreoffice.LibreOffice.Locale              stable                 i             flathub            < 84.8 MB (partial)
 9. [ ] org.libreoffice.LibreOffice                     stable                 i             flathub           < 323.1 MB

Installing 1/9…                        0%  0 bytes/s

It will certainly never install with this speed. I stopped it with Control+C.

I tried to install it from Software Manager (mintinstall), but it presents me with a time out error after some waiting: While pulling runtime/org.freedesktop.Platform.GL.default/x86_64/23.08 from remote flathub: Socket I/O timed out. I'm on Linux Mint 21.3, updated just today. I accidentally installed an older version (installed just a few days ago) and updated two times, didn't work on the older versions either.

Any help would be appreciated.

(BTW, does anyone know why there are two graphic cards in my system info, the second being Intel Corporation Sunrise Point-LP Integrated Sensor Hub? That is certainly not a graphics card.)

I undertook a sizeable upgrade today, bringing a skylake era build into the 2020s with a 13th gen. All core components- memory, motherboard, GPU, everything must go... except the drives. We were nervous, my friend really felt we should reinstall. There was debate, and drama. Considerations and exceptions. No, I couldn't let my OS go. I have spent years tweaking and tuning, molding my ideal computing environment. We pushed forward.

Well I'm pleased to say it was mostly uneventful. The ethernet adapter was renamed causing misconfigured dhcp, but otherwise it booted right up like nothing happened. Sorry, linux is boring now.

Are there any software issues I may/should deal with when doing a full system upgrade? I'm going from AM4 to AM5, so new CPU, motherboard and RAM.

It should be pretty straightforward under Linux, right? Just swap my drives over and boot up? I've only ever done single upgrades at a time, never a full generation.

I recently an install of Nobara Linux and there seems to be an issue during boot. Sometimes it fails to boot correctly and the screen looks glitchy with random noise and colors with no obvious way to move past it, forcing a manual shutdown via the power button (a couple times it seems to have failed complete and the system automatically booted in Windows 10). When this doesn’t happen, Nobara appears to boot normally and have no issues once I reach the login screen.

I only have a few weeks of experience with Linux with Linux Mint. I did not encounter any boot problems with Mint so I don't think there are any hardware issues. I suspect I must have made an error somewhere with the Nobara installation or with how I set up the partitions. I tried to follow with advice I found online, but maybe the info was incomplete or out of date.

I installed Nobara-39-Official-2024-01-24 and finished running all system and driver updates.

Nobara Partition setup:

• /boot/efi = 600 MB, FAT32, flags: boot & bios-grub
• /boot = 1 GB, EXT4
• / = 50 GB, EXT4
• / home = 110 GB, EXT4
• no mount (label: games) = remaining SSD space ~273GB, EXT4

The remaining portion of my 1TB SSD is dual boot Windows 10.

If anyone could diagnose this, it would be a great help.

I'm using Debian 12 from a fresh install (with Wayland). The mouse I'm using is an Azeron Cyro keypad. Azeron does not offer configuration software for Linux, but the device has onboard memory and can be configured via Windows or windows emulator. Importantly, what I'm trying to achieve here is not possible on Windows using Azeron's software.

My goal is to use one of the 16 keypad buttons on the mouse to disable mouse movement while pressed, resuming mouse movement when released. This is how I currently use the mouse in Windows so that I do not have to lift the mouse to reposition it. I'm able to achieve using reWASD on Windows, but they also do not offer a Linux version of their software.

I've tried a few different solutions, but I haven't been able to find something that fits this need, so I'm hoping someone might be able to guide me in a better direction:

• AntiMicroX - I've tried using the Flatpak, AppImage, and .deb packages. The software works as expected on other devices (for example, an xbox controller), and while my mouse shows up as a device, the button remapping does not work, the thumb stick is not available for calibration, and there seems to be no access to the mouse sensor.
• Input-Remapper - Very similar results to AntiMicroX, and also, I don't see a way to use Input-Remapper to disable mouse input anyway.
• Mouseless - While I can generate mouse movement commands through Mouseless, I haven't been able to disable mouse movement from my physical mouse.
• evdevremapkeys - This has been my most successful tool. With the debugger, I'm able to see my key presses (unless I have the key unmapped on the mouse) and I'm able to remap existing keys with a yaml configuration, but I've still not found a way to disable the mouse input.

I found something that seemed close to what I need in a two year old reddit post which mentions that it's possible with Sway (via man sway-input). I don't understand the proposed solution though and I'm not very familiar with compositors, how to interact with them or how installing one would affect my OS environment...

Does anyone know of a way I might be able to achieve this?

It's in the eye of the beholder, of course. But it would be great to see some solid recommendations.

I was thinking about going immutable for a long time and now I'm choosing a distro to hop to.
My question is: what are good immutable distros other than Fedora Silverblue spins, UBlue family and NixOS?
Maybe someone uses/used any? What is/was your experience with it?

Just installed Bazzite and it seems to work well so far.

Then I added a second standard user to the system and thought they'd have access to all software I just installed for the main user. But that doesn't seem the case, Bazzite prompted me to install all those again for the second user.

Is that just a thing with immutable distros or did I do this in a wrong way? I tried looking this question up, but I couldn't find any info on multi user setups with immutable distros.

Welcome to the monthly update for openSUSE Tumbleweed for June 2024. This month was busy with events like the Community Summit in Berlin and the openSUSE Conference, but a number of snapshots continued to roll out to users. Developers, system administrators and users receive updates designed to enhance your experience and ensure high levels of security and performance.

Should readers desire a more frequent amount of information about snapshot updates, readers are encouraged to subscribe to the openSUSE Factory mailing list.

Let’s go!

New Features and Enhancements

• Linux Kernel 6.9.7: This kernel introduces several important fixes and enhancements across various subsystems. Key updates include addressing undefined references in netfilter when CONFIG_SYSCTL is disabled, correcting TCP Fast Open handling, and resolving a conflicting quirk in Advanced Linux Sound Architecture for Realtek devices. Improvements in file system writeback operations, multi-threaded path handling and memory management for Hisilicon crypto drivers enhance stability. Networking updates include fixes for race conditions in netpoll, enhancements for specific SFP modules, and improvements in WiFi drivers such as RTW89, Ath9k, Ath12k, and MT76. Additional platform-specific updates address issues in ACPI, ARM64 configurations, HID device handling, and Bluetooth driver fixes.
• PipeWire 1.2.0 and WirePlumber 0.5.4: PipeWire 1.2.0 introduces asynchronous processing, node.sync-group for synchronized scheduling, and improved config parsing error reporting. It also adds mandatory metadata support for buffer parameters, multiple data-loops with CPU affinity, and dynamic log level adjustments. Key fixes include RTP-SAP module enhancements, ROC 0.3 support, and improved Bluetooth BAP broadcast code parsing. WirePlumber 0.5.4 refines the role-based linking policy, allowing role-based sinks alongside standard audio operations and enabling regular filters to act as best targets. It addresses startup crashes due to empty config files, improves Bluetooth profile auto-switching, and fixes issues with DSP filters and infinite loop scenarios in autoswitching scripts. Together, these updates enhance the flexibility, reliability, and overall performance of audio management in Linux environments. Both also received updates in snapshot 20240627
• Mesa and Mesa-drivers 24.1.2: Both packages underwent a specfile cleanup, involving the relocation of Rust crate sources into subprojects folders and updates to baselibs.conf. Due to the maintenance burden associated with Rust crates as system dependencies, these crates are now downloaded as vendored dependencies, as detailed in the README-suse-maintenance.md. The update adds support for building libvulkan_nouveau, including necessary Rust crates such as paste-1.0.14, proc-macro2-1.0.70, quote-1.0.33, syn-2.0.39, and unicode-ident-1.0.12. However, building libvulkan_nouveau on Leap is not possible due to the requirement for rust-cbindgen >= 0.25. For more details, refer to the release notes at https://docs.mesa3d.org/relnotes/24.1.2.
• KDE Plasma 6.1.1: Discover improves UI elements and Packagekit support, while Dr Konqi corrects the Sentry dbus interface usage. Plasma Addons addresses reference issues in Effects/cube, and krdp ensures version compatibility and resolves session controller bugs. Kscreenlocker improves greeter functionality, and KWin introduces multiple fixes for shaders, tiling, and input panels. Libkscreen and libplasma update protocol versions and fix plugin loading issues. Plasma Desktop enhances task icon sizing, panel opacity and file dragging across screens. Plasma Audio Volume Control removes unnecessary symlinks, and Plasma Systemmonitor correctly positions loading overlays. Powerdevil improves battery protection UI and limits backlighthelper calls.
• Python-setuptools 70.0: Key features in this new major version include emitting warnings for ignored [tools.setuptools] entries in pyproject.toml, improved error messaging for pkg_resources.EntryPoint.require and handling None location distributions more gracefully. The update also refreshes unpinned vendored dependencies, supports PEP 625 by standardizing package name and version in filenames and ensures encoding consistency for .pth files. Obsolete Python < 3.8 code has been removed, and pkg_resources now uses stdlib importlib.machinery. Bug fixes address race conditions in the install command, improve handling of nested namespaces with package_dir and correct various pkg_resources method behaviors. The patch for reproducibility has also been refreshed.
• Xen 4.18.2_06: This version resolves intermittent system hangs when Power Control Mode is set to Minimum Power. Patches also improve CPU mask handling and interrupt movement in various scenarios. Upstream bug fixes include improvements in scheduler resource data management and include fixes for building with GNU Compiler Collection 14.

Key Package Updates

• NetworkManager 1.48.2: This package updates support for matching OVS system interfaces by MAC address and fixes port reactivation and VPN secrets handling for 2-factor authentication. It saves connection timestamps during shutdown for proper autoactivation after restart. Key changes in 1.48.0 deprecate autotools building, add support for changing OpenSSL ciphers for 802.1X authentication, and set unmanaged device reasons in the StateReason property visible in nmcli. Additionally, it replaces the mac-address-blacklist property with mac-address-denylist, improves WiFi 6 GHz band detection and optimizes performance to avoid high CPU usage during route updates. Previous version 1.46 adds brought dynamic SSID-based stable IDs, randomized MAC addresses and several enhancements for handling IPv6, D-Bus and cloud setup.
• ibus-table 1.17.6: This update drops Python2 support, transitioning all scripts to Python3 using pyupgrade. It now allows the use of keys with Unicode keysyms in keybindings, enhancing customization and flexibility. Additionally, the frames_per_buffer=chunk_size option is now utilized in self._paudio.open() for improved audio handling. The update also includes translation enhancements from Weblate, with Czech translations reaching 36.6 percent, Japanese at 45.3 percent, and Chinese (Simplified) at 92.0 percent.
• btrfsprogs 6.9: The mkfs utility now halts if the mount status cannot be determined when using the --force option and corrects the minimum size calculation for zoned devices. The check command removes the --clear-ino-cache option, shifting its functionality to the rescue command group, and adds detection and repair for incorrect file extent item ram_bytes values. The qgroup commands now sync the filesystem before searching for stale entries, handle uncleaned subvolumes and squota enabled scenarios, and display the cleaning status of subvolumes. The receive command fixes stream parsing for strict alignment hosts, and tune change-csum and dump-tree commands include updates for handling dev-replace status items. The convert command improves extent iteration for preallocated/unwritten extents. The build process now ensures compatibility with e2fsprogs 1.47.1 and improves header file dependency tracking. Documentation was also updated.
• GNU’s Emacs 29.4: An emergency bugfix took place in this release. In this update, arbitrary shell commands are no longer executed when enabling Org mode, significantly enhancing security by preventing the execution of potentially malicious commands.

Bug Fixes

• Python-dnspython 2.6.1:

  • CVE-2023-29483 - Eventlet before 0.35.2 in dnspython allows remote "TuDoor" DNS attack interference.

• php8 8.3.8:

  • CVE-2012-1823 involved a vulnerability where attackers could inject arguments into PHP-CGI, leading to potential security issues. The new vulnerability, CVE-2024-4577, was discovered to bypass this original fix, allowing the same or similar types of argument injection attacks. The update ensures that this bypass is no longer possible, reinforcing the security measures originally put in place for CVE-2012-1823.
  • Similarly, the bypass of CVE-2024-1874 was made with the fix to CVE-2024-5585.

• kernel-firmware-nvidia-gspx-G06 (NVIDIA GPU driver)

  • CVE-2024-0090 was a vulnerability where a user can cause an out-of-bounds write.
  • CVE-2024-0091 was a vulnerability where a user can cause an untrusted pointer dereference. A successful exploit of this vulnerability might lead to denial of service.
  • CVE-2024-0092 was an improper check or improper handling of exception conditions might lead to denial of service.

• XZ 5.6.2:

  • CVE-2024-3094 Through a series of complex obfuscations, the liblzma build process extracts a prebuilt object file from a disguised test file existing in the source code, which is then used to modify specific functions in the liblzma code. This results in a modified liblzma library that can be used by any software linked against this library, intercepting and modifying the data interaction with this library. More details in snapshot 20240605

• cJSON v1.7.17:

  • CVE-2024-31755 - A segmentation violation, which can trigger through the second parameter.

Conclusion

The month of June 2024 saw a range of significant updates, security fixes and enhancements. The Linux Kernel 6.9.7 update improved stability and performance. Mesa and Mesa-drivers 24.1.2 introduced Rust crate dependencies and improved Vulkan support. KDE Plasma 6.1.1 brought UI improvements and a major version of Python-setuptools 70.0 arrived for rolling release users. A few critical security vulnerabilities were taken care of and fixes related to the XZ backdoor continued, so that Tumbleweed remains secure, efficient and feature-rich for all users.

For those Tumbleweed users who want to contribute or want to engage with detailed technological discussions, subscribe to the openSUSE Factory mailing list . The openSUSE team encourages users to continue participating through bug reports, feature suggestions and discussions.

Contributing to openSUSE Tumbleweed

Your contributions and feedback make openSUSE Tumbleweed better with every update. Whether reporting bugs, suggesting features, or participating in community discussions, your involvement is highly valued.

More Information about openSUSE:

Official

• openSUSE News
• openSUSE Mailing List
• openSUSE Wiki

Fediverse

• https://discuss.tchncs.de/c/opensuse@lemmy.world

(Image made with DALL-E)