Maybe you wondered how to change Windows 11 startup sound to something your liking, or how to restore the glorious Windows 7 startup/shutdown sounds. It can be done pretty easily. Follow the guide below:
https://gist.github.com/horsecz/08b164802c7f349fdb56a4587cf7d407
Hello,
occassionally I have delay while booting my Fedora Linux 44 KDE Plasma Desktop edition. The delay probably occurs right before getting into KDE Plasma.
It always happens on the same screen and looks the same as follows:
actual image of the screen when issue occurs - it's waiting for my input
Here on this screen while booting the system it is just stuck and waits for me to press any key to continue. That's all, I press any single any key (tried: space, enter, 'K', 'F', ...) and it will continue booting. Getting into TTY3 while in this state does not work (CTRL+ALT+F3 / CTRL+F3 / F2 / F4 does nothing, not continuing the boot either).
What is interesting is, that in journalctl there is no record of any time delay on these lines - even I do not press random key for few (5-20) seconds:
The first time gap can be seen much later here (07:06:06 - 07:06:10 - 07:06:31):
(Un)Fortunately this "waiting for random key to press to continue boot" issue does not occur every boot, but rather seems random - can happen twice today and then never the rest of the week or two, then occur again few times in week.
It seems also interesting that journalctl -b (or journalctl -b -0) which is supposed to be log of last boot (it seems like it is) shows me different elapsed time than on the screen (compare the line where are miliseconds in the first image with miliseconds on the second image, e.g. "Succesfully loaded SELinux policy in X" or "Relabeled /dev, /dev/shm, /run/ in X").
My guess was that system runs out of enthropy thus waiting for user input, but that was probably wrong? I don't know.
System:
Operating System: Fedora Linux 44
KDE Plasma Version: 6.6.5
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.1
Kernel Version: 7.0.12-201.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 9700X 8-Core Processor
Memory: 64 GB of RAM (62.4 GB usable)
Graphics Processor: NVIDIA GeForce RTX 5070 Ti
Hello.
As the title says, I am here simply to share my personal experience with GNU/Linux operating systems (Ubuntu, Fedora Linux, Debian) after I have decided to migrate from obsolete rotting Windows 10 instead of upgrading to Windows 11 during April 2026 - June 2026.
The text is enormously long, mostly because:
- it gathers experience over 2 months, noted in some detail
- there is no intention of it being another "I use Arch btw", "[distribution name] is the best", "Windows bad, Linux good" post nor text, therefore just typing "it did not work, Fedora bad" is simply not enough
Your opinion and discussion is most welcome.
See the link here to read: https://gist.github.com/horsecz/e920d1860641bc7a547e8bf9891b439d
This may be relevant to some of you since you are in r/Fedora and my setup includes using Fedora Linux most of the time.
Hello, I have an interesting issue.
My audio setup is as described below:
- HiSense soundbar connected to TV via HDMI (which is connected to laptop)
- Xiaomi Sound Pocket A (B/T speaker connected to laptop)
- Xiaomi Sound Pocket B (B/T speaker connected to laptop)
They all can play simultaneously (connected in qpwgraph), however whenever I connect second Xiaomi Sound Pocket, instead of "normal" codec/mode (A2DP/SBC) it plays in MONO (HSP/mSBC).
This happens only when first B/T speaker is already connected. Happens for both speakers.
Example:
This issue occurs on lastest Debian Linux 13.4/KDE Plasma Desktop (6.3.6).
This issue did not occur on previous/older Manjaro Linux/KDE Plasma Desktop (not sure the exact version, but I would guess KDE Plasma 5.x.x, since it was 1-2 years old non-updated version).
Both of these speakers are the same. I know they both have some sort of function which somehow connects them to each other and they act as a single speaker (TWS Stereo Combo) - this may do some mess? I had no issues on older version of KDE/Linux (except sound delays, which occured after a while).
There is no option in Volume Settings nor elsewhere to change the codec from HSP/mSBC to A2DP/SBC when both speakers are connected.
Any help would be appreciated :(
Hello,
I need to get simultaneous audio output to multiple devices (on Debian 13, KDE Plasma Desktop). I have achieved this via:
1. Terminal command (creates new virtual audio sink): "pactl load-module module-null-sink media.class=Audio/Sink sink_name=my-sink"2. pavucontrol: set default output device to "my-sink"3. helvum: connect "monitor_FL/FR" from "my-sink" to "playback_FL/FR" to desired output devices
Worked on: Fedora 44 (GNOME/05.2026), Debian 13 (KDE Plasma Desktop/05.2026).
This works flawlessly. My setup is:
The issue: after disconnecting any bluetooth speaker (turning off, severing B/T connection), it disappears from 'helvum' - this itself is fine, but when connecting it again, it is not linked with "my-sink" virtual device. I need to manually link it again.
Is it possible to make the link/connection "persistent"? I really don't want to manually link it each time I turn it on ... Or is there any other (better) solution than mine that would work?
Past solution:
Manjaro, KDE Plasma Desktop (version from approx. 2024, not updated since installation) had an option for virtual device and allowed simultaneous output from all devices. This option is now gone.
------------
Note: ergh, maybe the thread title is a little bit off, since I have simultaneous playback, only it is not persistent :D
