Linux

As the title says, I'm trying to multiboot Fedora 40 and Ubuntu 24. The documentation and guides for this all seems pretty outdated through my searching and troubleshooting.

I currently have ubuntu installed. My drive partition table looks like this:

• sda1 -- EFI (250MB)
• sda2 -- /boot (ext4, 2GB)
• sda3 -- empty (ext4, 2TB) <-- Fedora partition
• sda4 -- Ubuntu 24 (LUKS encrypted, 2TB)

I'm trying to install Fedora now and it's giving me nothing but errors. The most useful guide I found for this specific setup just has you adding sda3 as the installation path (mounted at /) for Fedora and it's supposed to figure out the EFI and boot, but that doesn't happen. In fact, the EFI and /boot partitions show up under an "Unknown" tab in the Fedora custom partition window of the installation. They should be under a tab such as "Ubuntu 24 LTS". Fedora isn't recognizing the ubuntu installation (because it's encrypted?)

Am I wrong in assuming that both OS's should be sharing the EFI and /boot partitions? Maybe that's the issue?

Anybody out there successfully dual booting Linux distros with both distros encrypted?

I am thinking to make the following tool, but wanted to get opinions before I embark on this journey.

The tool builds container images.

The images are optionally distroless: meaning, they do not include an entire distro. They only include the application(s) you specify and its dependencies.

What else does the tool give you?

• the build tool uses a package manager to do dependency resolution, so you don't have to manually resolve them like many docker files do. (NOTE: The package manager is not installed on the container image. It is only used by the build tool)
• uses gentoo's portage to build the software from source (if not previously cached). This is helpful when you're using versions of software that aren't built against each other in the repos you download from
• allows specifying compile flag customizations per package.
• makes use of gentoo's existing library of package build or install recipes, so that you only have to write them for uncommon apps rather than in every docker file.

I find it crazy that so many dockerfiles are doing their own dependency resolution when we already have package managers.

What do you think? Is this tool useful or am I missing a reason why it wouldn't be?

It's actually not a bug, but obvious behavior.

I have a Logitech C920 and am looking to upgrade. Something suitable for streaming.

Some annoyances with the Logitech: sometimes autofocus fails and poor reproduction of blacks. Ex: Lack of detail when a black cat is on screen.

I already have a nice mic-- the webcam doesn't need one.

So a week ago I wiped my SSD and tried Kinoite and Bazzite. I switched mostly for a fresh Wayland experience with Plasma and also so that I don't spend too much time tinkering to solve some minor issues ( well it didn't go as expected).

I ended up settling with Aurora-dx because it's a good balance between Kinoite and Bazzite while still offering all the Ublue goodies.

Here are some things that I couldn't find fixes for even after I tried Reddit and the Ublue forums ->

1. Opening any Flatpak app or moving the cursor makes the display black out

I actually started experiencing this issue in other distros way before I switched to Kinoite / Ublue. After I've switched to AMD this was happening almost every time I turned on the computer.

(This is AMD specific) The issue can be fixed by setting a udev rule, like this :

sudo vim /etc/udev/rules.d/30-amdgpu-pm.rules

Then enter the following in the file :

KERNEL=="card0", SUBSYSTEM=="drm", DRIVERS=="amdgpu", ATTR{device/power_dpm_force_performance_level}="high"

Keep in mind that you may have "card1" instead of "card0" you can check it by doing an ls within

/sys/class/drm/

Alternatively if you just want your display to stop blacking out in your current session only then :

cat sys/class/drm/card1/device/power_dpm_force_performance_level >> high

2. Display turns off entirely in Fullscreen applications.

this is probably KDE specific, I do not know about Gnome

Display Configuration > Adaptive Sync > Never

This should fix it.

But when the computer wakes up after a sleep session, the issue could appear again. I don't think they have a fix for this yet.

3. Steam not able to add directories from any other location (including any folders in the same drive)

This is not a proper solution, It just happened to work for me so I thought I'd share.

Just symlink the Game directories you want to

.steam/steam/steamapps/common

like :

ln -s PATH_To_Game_Folder ~/.steam/steam/steamapps/common/Game_Folder 

For the folks using flatpak steam the steam directory will be under .var/apps/

I personally use Bazzite-arch container for gaming and it has been working really well, although the game shortcuts don't work unless you start the container.

4. KDE plasma desktop and task manager panel frozen and crashes randomly.

This issue is likely related to any applets you have added to the panel or the desktop. For me this happened when I added the 'Network speed Indicator' and tried to resize the panel (strangely this never occurred to me in the past, but hey it's been a solid 5 years since I tried KDE or any DE for that matter)

The solution is to either delete or rename the following file to something else

~/.config/plasma-org.kde.plasma.desktop-appletsrc

Then restart the system. Plasma should create a new file which will essentially reset the panel and desktop settings to stock.

I hope that someone will find use in the contents of this post.

So a week ago I wiped my SSD and tried Kinoite and Bazzite. I switched mostly for a fresh Wayland experience with Plasma and also so that I don't spend too much time tinkering to solve some minor issues ( well it didn't go as expected).

I ended up settling with Aurora-dx because it's a good balance between Kinoite and Bazzite while still offering all the Ublue goodies.

Here are some things that I couldn't find fixes for even after I tried Reddit and the Ublue forums ->

1. Opening any Flatpak app or moving the cursor makes the display black out

I actually started experiencing this issue in other distros way before I switched to Kinoite / Ublue. After I've switched to AMD this was happening almost every time I turned on the computer.

(This is AMD specific) The issue can be fixed by setting a udev rule, like this :

sudo vim /etc/udev/rules.d/30-amdgpu-pm.rules

Then enter the following in the file :

KERNEL=="card0", SUBSYSTEM=="drm", DRIVERS=="amdgpu", ATTR{device/power_dpm_force_performance_level}="high"

Keep in mind that you may have "card1" instead of "card0" you can check it by doing an ls within

/sys/class/drm/

Alternatively if you just want your display to stop blacking out in your current session only then :

cat sys/class/drm/card1/device/power_dpm_force_performance_level >> high

2. Display turns off entirely in Fullscreen applications.

this is probably KDE specific, I do not know about Gnome

Display Configuration > Adaptive Sync > Never

This should fix it.

But when the computer wakes up after a sleep session, the issue could appear again. I don't think they have a fix for this yet.

3. Steam not able to add directories from any other location (including any folders in the same drive)

This is not a proper solution, It just happened to work for me so I thought I'd share.

Just symlink the Game directories you want to

.steam/steam/steamapps/common

like :

ln -s PATH_To_Game_Folder ~/.steam/steam/steamapps/common/Game_Folder 

For the folks using flatpak steam the steam directory will be under .var/apps/

I personally use Bazzite-arch container for gaming and it has been working really well, although the game shortcuts don't work unless you start the container.

I hope this post helps someone out.

Edit: Solved, while changing EDID make sure to remove the old module first and reinstall it with the new EDID

I have a faulty DP to HDMI adapter, that unfortunately never seems to parse the EDID data, so while connecting to a TV I used this guide and a 1920x1080.bin file from the internet and it worked, but unfortunately I was unable to use the TV speakers(I guessed the EDID file didn't specify that the device had audio out)

Using a separate pc I extracted my TVs EDID.bin file and repeated the steps but unfortunately, it just doesn't work, its stuck on the old 1920x1080.bin(I can tell because it shows up as 'Linux Foundation 23'') The issue persists even after I delete the old .bin file from /usr/lib/firmware/edid

I am using wayland

System info:

OS: Fedora Linux 40 (Workstation Editi 
Host: TECRA R940 PT439V-03U02WAR 
Kernel: 6.8.11-300.fc40.x86_64 
Uptime: 29 mins 
Packages: 2209 (rpm), 32 (flatpak) 
Shell: bash 5.2.26 
Resolution: 1920x1080 
DE: GNOME 46.2 
WM: Mutter 
WM Theme: Adwaita 
Theme: Adwaita [GTK2/3] 
Icons: Adwaita [GTK2/3] 
Terminal: gnome-terminal 
CPU: Intel i7-3540M (4) @ 3.700GHz 
GPU: AMD ATI Radeon HD 7550M/7570M/765 
Memory: 1998MiB / 7879MiB 

Dmesg -H

[Jun20 22:26] Linux version 6.8.11-300.fc40.x86_64 (mockbuild@f09cc32e12c24ed6a1a66c2a2e9f1728) (gcc (GCC) 14.1.1 20240522 (Red Hat 14.1.1-4), GNU ld version 2.41-37.fc40) #1 SMP PREEMPT_DYNAMIC Mon May 27 14:53:33 UTC 2024
[  +0.000000] Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.8.11-300.fc40.x86_64 root=UUID=XXXXX ro rootflags=subvol=root rhgb quiet drm.edid_firmware=DP-2:edid/sony.bin

Any help is appreciated

Hey everyone,

I'm facing an issue with KDE Plasma 5 on Debian 12. Whenever I skip a song on Spotify, the notification sound plays. I've come across suggestions in other forums to simply mute notifications, but I still want to receive notifications. Therefore, muting notifications is not an option for me.

I have disabled all Spotify notifications in the notification manager, yet I'm unsure how the sound still persists. I don't want to disable notification sounds in the Plasma Workspace, as mentioned earlier.

Any insights or solutions would be greatly appreciated. Thanks in advance!

Edit: Specs might help:

OS: Debian 12 bookworm Kernel: x86_64 Linux 6.1.0-21-amd64 DE: KDE 5.103.0 / Plasma 5.27.5 CPU: Intel Core i7-4790 @ 8x 4GHz GPU: GeForce GTX 745 GPU Driver: nouveau RAM: 8GB

im on a dinit based system and want to start syncthing as a regular user service. currently, its running as root (which bugs me a lot, as it's playing on the network) using the syncthing-dinit service located at /etc/dinit.d/syncthing. i know i can run it with a custom syncthing dinit service file. but, i just want to know how to make use of the existing syncthing-dinit service file

thanks in advance

Edit: SOLVED thanks to r00ty !

Hello, I have this weird issue that my Debian 11 will tell me the root folder is full, while I can only find files for half of the accounted space.

df -h reports 56G while the disk analyser (sudo baobab) only finds 28G.

Anyone ever encountered this? I don't have anything mounted twice.... (Not sure what udev is). Also it does not add up to 100%, it should say 7.2G left not 4.1G

df -h /dev/sda* Filesystem Size Used Avail Use% Mounted on udev 16G 0 16G 0% /dev /dev/sda1 511M 22M 490M 5% /boot/efi /dev/sda2 63G 56G 4.1G 94% / /dev/sda4 852G 386G 423G 48% /home

Edit: my mtab

Edit 2: what Gparted shows

hardware is a nuked MacBook Pro, Intel Core i5-4278U @ 2.60GHz, model A1502 (EMC 2875), Retina Mid-2014 13"

I tried to install debian 12.5 from a live usb on this computer. On the network page of debian's installation GUI I get this message:

No Ethernet card was detected. If you know the name of the driver needed by your Ethernet card, you can select it from the list.

so I logged in to recovery mode and executed

sudo lspci -vnnk -s 03:00.0

that returns

network controller [0200]: broadcom inc. and subsidiaries BCM4360 802.11ac wireless network manager adapter [14e4:43a0] (rev 03)

there is more information that I wanted to save to a lspci.txt file on the live usb (sdc1) to share with you, but I failed the syntax.

Why I want to do this: installing debian, on the GUI's networking page there is a candidate with this exact specification (broadcom 802.11ac wireless network manager), but I cannot install it because I don't have wifi or an ethernet cable, so I'd have to download this package from this computer I'm using now and copy it to the live usb to install alongside debian 12.5. I just wanted to print the whole command just in case it's helpful.

ETA: how do I install rpm fusion repos on debian? I only found instructions for fedora and rhel https://rpmfusion.org/Configuration

thanks

openSUSE Leap Micro 6.0 Beta is now available! We expect that it will very quickly transition to RC and GA as the infra readiness advances. Leap Micro 6.0 Beta images can be found at get.opensuse.org or directly at download.opensuse.org.

About Leap Micro

Leap Micro 6.0 is a rebranded SUSE Linux Enterprise Micro 6.0 which is an ultrareliable container and VM host by SUSE. This is the first publicly released product based on the fresh code base "SUSE Linux Framework One" (previously known as ALP).

Leap Micro 6.X is available for x86_64 and aarch64, released every 6 months, and supported until the next-next release is out. That means that Leap Micro 6.0 will become EOL once Leap Micro 6.2 gets released.

All pieces related to Rancher and Elemental are purposely excluded from Leap Micro 6.X as SLE Micro for Rancher is free for use without any subscription within Rancher deployments.

No more traditional installer

Leap Micro 6.X is deployed via self-install image which writes a preconfigured image to the disk and enlarges root partition. Users can use combustion, ignition or default to the jeos-firstboot wizard to do the initial setup of the system.

Do not get mistaken by the availability of openSUSE-Leap-Micro-6.0-*.iso is not installable. We refer to the image as a Packages image, which is basically an offline repository on a DVD.

New FDE, VMWare, and Cloud images

Aside from the self-install image Micro 6.0 comes with qcow, Full Disk Encryption, and RealTime images. All images can be found at download.opensuse.org

For the first time Leap Micro 6.X has also cloud-init therefore shortly after the release we will also have cloud images available on GCP, Azure, and AWS.

Changes to the product building

Leap Micro 6.X is using the new product composer instead of the old product builder. This allowed us to consume update-info from the newly designed maintenance workflow of SLE Micro 6.0 and was preferred by the openSUSE maintenance team.

Changes to the repositories and maintenance workflow

Leap Micro 5.X users receive all updates released for relevant SLE Micro version via a repository named repo-sle-update. This particular repository no longer exists in Leap Micro 6.X.

Instead, the repo-main repository will contain all released updates for the relevant version of SUSE Linux Micro to date.

Please note that the repository path slightly changed too, we'll ensure that migration via transactional-update shell followed by zypper dup --releaser 6.0 works via compatibility symlinks on download server.

New way of managing repository definitions

openSUSE-repos is not new to our users, however, for the first time, openSUSE Leap Micro 6.0 deployments come with openSUSE-repos preinstalled. openSUSE repos uses a local RIS service that easily lets us maintain repository definitions with a package update.

Users migrating from 5.5/5.4 releases are advised to install zypper in openSUSE-repos to ensure they have up-to-date repository paths.

Documentation

Please refer to SLE Micro 6.0 documentation including Release notes.

Reporting Issues

Please refer to the Leap Micro section in our Submitting bug reports page.

Next steps

Missing maintenance setup was a long-term blocker for the transition out from Alpha, otherwise, the distribution itself is stable and feature-full. Now that we have it, we need to polish some remaining infrastructure issues and users can expect a release within the next few days. Ideally before oSC2024 next week.

Today, I wanted to have another go with nix. Previously I just read about it and didn't do anything for a couple of months. Now, I installed nix package manager with very few lines of code and two more to install many packages as described in his post. Installation was very fast on my banana laptop. Until now I used distrobox but I always wondered which distro/ package manager to use. What's your experience with it? For now, I'll test it. It's super easy to use. It may not be straight forward to a linux newcomer but if you know what you want, e.g. ffmpeg you can just add it with home-manager edit and install it with home-manager switch. So far, I love it!

Interesting times ahead! I am really looking forward to the Leap Micro release and hope it advances the state of the art. :-)

What's up with homebrew that you'd have it installed by default on linux?

I don't understand the appeal of it, can someone help me?

While Plasma 6.0 was all about getting the migration to the underlying Qt 6 frameworks correct (and what a massive job that was), 6.1 is where developers start implementing the features that will take you desktop to a new level.

In this release, you will find features that go far beyond subtle changes to themes and tweaks to animations (although there is plenty of those too), as you delve into interacting with desktops on remote machines, become more productive with usability and accessibility enhancements galore, and discover customizations that will even affect the hardware of your computer.

These features and more are being built directly into Plasma's Wayland version natively, avoiding the need for third party software and hacky extensions required by similar solutions implemented in X.

Things will only get more interesting from here. But meanwhile enjoy what will land on your desktop with your next update.

Some of the new features:

• Improved remote desktop support with a new built-in server
• Overhauled desktop edit mode
• Restoration of open applications from the previous session on Wayland
• Synchronization of keyboard LED colors with the desktop accent color
• Making mouse cursor bigger and easier to find by shaking it
• Edge barriers (a sticky area for mouse cursor near the edge between screens)
• Explicit support eliminates flickering and glitches for NVidia graphics card users on Wayland
• Triple Buffering support for smoother animations and screen rendering