My guess would be that it had an issue with the current partitioning on your disks. Say you want to install on your NVMe, and keep what’s on your SATA SSD, you could try the following:
echo 1|sudo tee /sys/block/sda/device/deletesudo blkdiscard -f /dev/nvme0n1I’ll just wipe the partitions entirely, the box is literally just spare/test.
But yeah cheers, will try something like that 
edit:
yeah looks like wiping the partitions out fixed it, that was what I was planning to do at some point but managed to run the commands you mentioned from another CLI session on the omarchi installer.
cheers!
box is a 3300x with 32 GB and a Vega 64, should be a nice responsive little machine running this!
I think I mentioned this before when I did some testing of my own but I wasn’t sure, however it’s come up again in a PR I was making on GitHub.
bash’s supposed automatic POSIX compliant mode does not work, and it appears neither does --posix, or set -o posix?
$ man bash
…
OPTIONS
--posix
Change the behavior of bash where the default operation differs from the POSIX standard to match the
standard (posix mode). See SEE ALSO below for a reference to a document that details how posix mode af‐
fects bash's behavior.
…
INVOCATION
If bash is invoked with the name sh, it tries to mimic the startup behavior of historical versions of sh as
closely as possible, while conforming to the POSIX standard as well.
…
SHELL BUILTIN COMMANDS
set [+abefhkmnptuvxBCEHPT] [+o option-name] [--] [-] [arg ...]
-o option-name
posix Change the behavior of bash where the default operation differs from the POSIX standard
to match the standard (posix mode). See SEE ALSO below for a reference to a document
that details how posix mode affects bash's behavior.
…
The link in “see also” has a lot of points, none of which seem relevant here.
Here’s a simple test:
❯ cat sh-test
#!/bin/sh
set -o posix
if [[ "yes" == "yes" ]]; then
echo "Hello World"
fi
[[ "$a" == "$b" ]] is a non-POSIX-compliant bash-ism (it would be [ "$a" = "$b" ]), so this should fail, right? Wrong.
❯ ./sh-test
Hello World
❯ sh sh-test
Hello World
❯ bash --posix sh-test
Hello World
❯ bash --posix
bash-5.2$ ./sh-test
Hello World
bash-5.2$ exit
exit
Am I doing something wrong or is the compliant mode simply not compliant?
Does it only affect the “startup behaviour” (which from what I can tell is just reading a reduced set of configuration)? But the man page uses the Oxford-comma before while conforming to the POSIX standard as well., which implies it does both. So… WTH?
Also, if anyone’s wondering, it’s not the code. This does fail as expected in dash:
❯ dash sh-test
sh-test: 3: set: Illegal option -o posix
# after removing set
❯ dash sh-test
sh-test: 3: [[: not found
Bash’s posix mode is for Posix-compatibility not a Posix-only-and-block-everything-else… It doesn’t disable all the bashisms.
Exactly what it does is listed in excruciating detail here:
That’s the same list I linked, but it’s still misleading at best.
When they put “while conforming to the POSIX standard” in the description, then allowing non-POSIX-standard syntax is problematic. And it’s also just plain wrong, it’s not compliant code so it shouldn’t run in compliant mode.
Figured out that switching it to Pro Audio let it separate
Whenever I [Esc] out of Spectacle, I get alt-tabbed…
Ah! this is something that also happens to me, in various circumstances, very infuriating. Tried to diagnose it once in the past, but gave up.
Fresh install of openSUSE Tumbleweed with KDE 6.5.0 and libpipewire 1.5.81 - audio gets un-muted whenever the system resumes from sleep, irrespective of the state it was in when entering sleep.
Do you have a command line that mutes the audio? If so, you could drop a script in /usr/lib/systemd/system-sleep:
#!/usr/bin/env bash
case $1 in
post)
<command to mute audio>
;;
esac
IDK how well the timing would work out.
What’s the tldr on using SecureBoot/TPM with Linux?
Arch workstation, systemd-boot, default kernel. Installed win11 on a new drive to play bf6, dual boot mostly works. Setting ASUS Secure Boot to “Other OS” in bios launches Linux nvme into systemd-boot menu with Arch and Win11, both can reach desktop but Win11 yells for misconfigured SecureBoot and bf6 doesn’t work.
Setting ASUS Secure Boot to Windows UEFI works great for windows and bf6, but throws a secure boot error on Linux drive and doesn’t reach systemd-boot menu/desktop.
Current fix is to just reboot to bios and switch the settings. It’s annoying but not the worst. I guess the ‘right’ way would be to sign Linux boot with Microsoft keys? Will this bite me down the road and add unnecessary complexity or is it mostly plug and play
Sounds like you do not have a secure boot key for Linux. This guide might help:
Upgraded my system today and discovered that display link docking stations do not work on an all AMD systems. At least my particular setup.
This is what I looked like all day today trying to figure out why my system was having random crash/freezes with journalctl showing random errors:
Note: Worked completely fine on windows.
Here’s a really weird one, seen it on all KDE Plasma 6 with Wayland, including on fresh openSUSE with Plasma 6.5.0 but it’s been going on through all of the 6.x releases.
I have two monitors - a Coolermaster GP27U (left) and a basic LG 4K60 (right) connected via DisplayPort to a Radeon RX7800XT. The GPU’s DP outputs determine which monitor is the default primary. The GP27U can be slow to sync, so I physically connected the LG monitor as my physical primary, otherwise I would miss POST/boot screens, and just rearranged them in the KDE desktop.
Everything appears fine, except this appears to trigger two glitches in KDE:
I noticed that the edit panels entry animation looked as if it was moving Windows around excessively (as if they were going off screen and looping around). It was as if the un-rearranged layout gets used for the animation, which messes up the window position calculation.
On a whim I decided to swap the DP connectors around, so that the software rearrange wasn’t required. Both issues resolved immediately and the edit panels animation looks normal too.
I wanted to give KDE a try, and I can’t for the life of me figure out what I’m doing wrong…
I can’t get Dolphin to show a list of files and folders without preview, sorted by modified date, not folders first - everything just sorted by modified date.
After that, if I open any folder it just goes back to Icons with previews. Go back one step and yes, my settings are gone there too.
I’ve checked Configure → View → General and it is set to Use common display style for all folders. It just reverts back to Icons every time.
Am I missing something obvious here?
Maybe you have conflicting configs?
The per folder settings are stored here:
~/.local/share/dolphin/view_properties/
You can try and deleting everything in that folder then restart dolphin.
Your global config is found here:
~/.config/dolphinrc
I did try that, there were no files in ~/.local/share/dolphin/view_properties/ and I tried setting things manually in global config, but it still just reverted back.
Next I tried removing the config file and let it recreate - still same.
It finally somewhat worked in a very annoying way…
I had to:
And if I dare adjust even one setting in “Adjust view display style” - poof, goes back to icons and I need to do it all over again.
I wonder if it will survive the reboot…
More troubles with KDE…
Is there a way to make krunner learn, or at least manually make it prioritize search results?
I can’t imagine most people are looking for Kate or Blender when they type “Ter” in the search box.
There are some articles out there describing how to add keywords to .desktop files, but all those keywords are already there.
Some suggest disabling search categories, but that won’t help either - it buries Konsole under every other app.
Notice it tries to be helpful and allows me to tab to auto complete but that is somehow even worse.
There is something weird going on here, on my system Terminal is the first result with “ter” typed in.
On yours Terminal doesn’t even seem to show up at all.
Are you using the default one, Konsole?