I'm trying to connect to use remote servers in multi monitor setup with following command

xfreerdp3 /d:foobar.intranet /u:myuser /v:xx.xx.xx.31 \
    +clipboard +sound -wallpaper /cert:ignore \
    /multimon:force /monitors:0,3

The problem is that both monitors are mirrored in full screen and are not interactable (it's like they show a default desktop without any input). My monitors are:

❯ xfreerdp3 /list:monitor
      *  2560x1440	+2560+0
         1920x1080	+7680+0
         2560x1440	+5120+0
         2560x1440	+0+0

The thing which makes no sense to me is that in the window preview both monitors are rendered correctly but if opened it's still frozen. I'm using CachyOS with KDE Plasma, both on the newest default release.

The ethernet works fine and everything else seems fine. I have disabled fast boot from Windows 11. I know it's not a hardware issue because my Wi-Fi card (Intel) works on Windows and worked on a previous Debian system I had on another hard drive. I have downloaded iwlwifi, but I am getting errors such as in dmesg:

[ 9437.311118] iwlwifi 0000:00:14.3: mac start retry 2

My kernel is up to date, shown by the output of uname r:

6.1.0-37-amd64

ip a:

1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: enp3s0:  mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether d8:43:ae:03:5f:42 brd ff:ff:ff:ff:ff:ff
    inet 192.168.50.226/24 brd 192.168.50.255 scope global dynamic noprefixroute enp3s0
       valid_lft 85427sec preferred_lft 85427sec
    inet6 fe80::84ec:5e5:4e87:f4db/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: wlo1:  mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 92:a0:88:5e:60:7b brd ff:ff:ff:ff:ff:ff permaddr bc:03:58:2d:af:f0
    altname wlp0s20f3

lspci:

0000:00:00.0 Host bridge: Intel Corporation Raptor Lake-P 6p+8e cores Host Bridge/DRAM Controller
0000:00:01.0 PCI bridge: Intel Corporation Raptor Lake PCI Express 5.0 Graphics Port (PEG010)
0000:00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-P [Iris Xe Graphics] (rev 04)
0000:00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic Platform and Thermal Framework Processor Participant
0000:00:06.0 System peripheral: Intel Corporation RST VMD Managed Controller
0000:00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module
0000:00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller Intel Corporation
0000:00:14.0 USB controller: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller (rev 01)
0000:00:14.2 RAM memory: Intel Corporation Alder Lake PCH Shared SRAM (rev 01)
0000:00:14.3 Network controller: Intel Corporation Raptor Lake PCH CNVi WiFi (rev 01)
0000:00:15.0 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #0 (rev 01)
0000:00:16.0 Communication controller: Intel Corporation Alder Lake PCH HECI Controller (rev 01)
0000:00:1c.0 PCI bridge: Intel Corporation Device 51b8 (rev 01)
0000:00:1c.5 PCI bridge: Intel Corporation Alder Lake-P PCH PCIe Root Port (rev 01)
0000:00:1f.0 ISA bridge: Intel Corporation Raptor Lake LPC/eSPI Controller (rev 01)
0000:00:1f.3 Multimedia audio controller: Intel Corporation Raptor Lake-P/U/H cAVS (rev 01)
0000:00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01)
0000:00:1f.5 Serial bus controller: Intel Corporation Alder Lake-P PCH SPI Controller (rev 01)
0000:01:00.0 VGA compatible controller: NVIDIA Corporation AD106M [GeForce RTX 4070 Max-Q / Mobile] (rev a1)
0000:01:00.1 Audio device: NVIDIA Corporation AD106M High Definition Audio Controller (rev a1)
0000:03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
10000:e0:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port
10000:e1:00.0 Non-Volatile memory controller: MAXIO Technology (Hangzhou) Ltd. NVMe SSD Controller MAP1602 (DRAM-less) (rev 01)

dmesg | grep net:

[    7.478761]  devinet_ioctl+0x392/0x7b0
[    7.478774]  inet_ioctl+0x1ae/0x1e0
[    7.685144]  devinet_ioctl+0x392/0x7b0
[    7.685157]  inet_ioctl+0x1ae/0x1e0
[    7.888357]  devinet_ioctl+0x392/0x7b0
[    7.888362]  inet_ioctl+0x1ae/0x1e0
[    8.095664]  devinet_ioctl+0x392/0x7b0
[    8.095672]  inet_ioctl+0x1ae/0x1e0
[    8.303182]  devinet_ioctl+0x392/0x7b0
[    8.303188]  inet_ioctl+0x1ae/0x1e0
[    8.506412]  devinet_ioctl+0x392/0x7b0
[    8.506421]  inet_ioctl+0x1ae/0x1e0
[   19.197826]  devinet_ioctl+0x392/0x7b0
[   19.197828]  inet_ioctl+0x1ae/0x1e0
[   19.197843]  ? inet_ioctl+0xd8/0x1e0
[   19.393622]  devinet_ioctl+0x392/0x7b0
[   19.393624]  inet_ioctl+0x1ae/0x1e0
[   19.393638]  ? inet_ioctl+0xd8/0x1e0
[   19.589894]  devinet_ioctl+0x392/0x7b0
[   19.589896]  inet_ioctl+0x1ae/0x1e0
[   19.589911]  ? inet_ioctl+0xd8/0x1e0
[   19.786597]  devinet_ioctl+0x392/0x7b0
[   19.786602]  inet_ioctl+0x1ae/0x1e0
[   20.003916]  devinet_ioctl+0x392/0x7b0
[   20.003928]  inet_ioctl+0x1ae/0x1e0
[   20.208988]  devinet_ioctl+0x392/0x7b0
[   20.209001]  inet_ioctl+0x1ae/0x1e0
[   30.195141]  devinet_ioctl+0x392/0x7b0
[   30.195144]  inet_ioctl+0x1ae/0x1e0
[   30.390248]  devinet_ioctl+0x392/0x7b0
[   30.390251]  inet_ioctl+0x1ae/0x1e0
[   30.588620]  devinet_ioctl+0x392/0x7b0
[   30.588627]  inet_ioctl+0x1ae/0x1e0
[   30.795221]  devinet_ioctl+0x392/0x7b0
[   30.795245]  inet_ioctl+0x1ae/0x1e0
[   30.998801]  devinet_ioctl+0x392/0x7b0
[   30.998806]  inet_ioctl+0x1ae/0x1e0
[   31.203105]  devinet_ioctl+0x392/0x7b0
[   31.203127]  inet_ioctl+0x1ae/0x1e0
[   41.215989]  ? inet_ioctl+0xd8/0x1e0
[   41.216580]  devinet_ioctl+0x392/0x7b0
[   41.216605]  inet_ioctl+0x1ae/0x1e0
[   41.429866]  devinet_ioctl+0x392/0x7b0
[   41.429891]  inet_ioctl+0x1ae/0x1e0
[   41.634575]  devinet_ioctl+0x392/0x7b0
[   41.634580]  inet_ioctl+0x1ae/0x1e0
[   41.831446]  devinet_ioctl+0x392/0x7b0
[   41.831449]  inet_ioctl+0x1ae/0x1e0
[   42.027082]  devinet_ioctl+0x392/0x7b0
[   42.027085]  inet_ioctl+0x1ae/0x1e0
[   42.223520]  devinet_ioctl+0x392/0x7b0
[   42.223523]  inet_ioctl+0x1ae/0x1e0
[   52.224482]  devinet_ioctl+0x392/0x7b0
[   52.224512]  inet_ioctl+0x1ae/0x1e0
[   52.432187]  devinet_ioctl+0x392/0x7b0
[   52.432215]  inet_ioctl+0x1ae/0x1e0
[   52.638609]  devinet_ioctl+0x392/0x7b0
[   52.638640]  inet_ioctl+0x1ae/0x1e0
[   52.844039]  devinet_ioctl+0x392/0x7b0
[   52.844044]  inet_ioctl+0x1ae/0x1e0
[   53.047908]  devinet_ioctl+0x392/0x7b0
[   53.047921]  inet_ioctl+0x1ae/0x1e0
[   53.251044]  devinet_ioctl+0x392/0x7b0
[   53.251046]  inet_ioctl+0x1ae/0x1e0
[   64.207542]  devinet_ioctl+0x392/0x7b0
[   64.207556]  inet_ioctl+0x1ae/0x1e0
[   64.415526]  devinet_ioctl+0x392/0x7b0
[   64.415539]  inet_ioctl+0x1ae/0x1e0
[   64.625743]  devinet_ioctl+0x392/0x7b0
[   64.625746]  inet_ioctl+0x1ae/0x1e0
[   64.825079]  ? inet_ioctl+0xd8/0x1e0
[   64.825169]  devinet_ioctl+0x392/0x7b0
[   64.825172]  inet_ioctl+0x1ae/0x1e0
[   65.021692]  devinet_ioctl+0x392/0x7b0
[   65.021697]  inet_ioctl+0x1ae/0x1e0
[   65.239627]  devinet_ioctl+0x392/0x7b0
[   65.239649]  inet_ioctl+0x1ae/0x1e0

I don't know what other information would be useful, so just ask and I should be able to provide it. I have spent a good amount of time troubleshooting, but I am new to Linux and don't have a ton of Comp Sci experience.

Why do I get this in the console when restarting plasmashell with killall plasmashell and kstart5 plasmashell in Debian11/KDE with Wayland and how to solve the problem? Of PipeWire I currently only have libpipewire-0.3-0 installed, I searched for screencast in Apper but don't have anything of that installed. I'm using PulseAudio and I think I also got this error when I ran something else than plasmashell but it's probably the same cause. I'm not screenrecording but have some apps that can do so. I tried uninstalling xdg-desktop-portal and this reduced these errors but the error still shows, it went from 8 times the above error to only one:

error creating screencast "Failed to connect PipeWire context"
trying to show an empty dialog
DataControlOffer: timeout reading from pipe
DataControlOffer: timeout reading from pipe
DataControlOffer: timeout reading from pipe
DataControlOffer: timeout reading from pipe

**Edit**: it's two errors now and unlike before these only occur after waiting for approximately 20 second after starting plasmashell (the other errors are because of kdeconnect trying to start without being configured to so which I blocked and asked about separately):

...
error activating kdeconnectd: QDBusError("org.freedesktop.DBus.Error.Spawn.ExecFailed", "Failed to execute program org.kde.kdeconnect: Permission denied")
kdeconnect.interfaces: dbus interface not valid
kdeconnect.interfaces: dbus interface not valid
error creating screencast "Failed to connect PipeWire context"
error creating screencast "Failed to connect PipeWire context"
libpng warning: iCCP: known incorrect sRGB profile

**Edit 2**: this error does not occur on another machine with nearly the same setup. Plasmashell is version 5.20.5 in Debian11. The same error occurs again when waiting for a while. How can I find out the source or traceback of this error message (may be a separate question)? I'd like to find out what software causes it, it's probably something that plasmashell launches. **Edit 3**: after upgrading to **Debian12** and resuming from sleep these lines show in journalctl shortly after resuming. Why and what should I do:

systemd: NetworkManager-dispatcher.service: Deactivated successfully.
kwin_wayland_wrapper: kwin_screencast: Failed to connect PipeWire context
kwin_wayland_wrapper: kwin_screencast: Failed to connect PipeWire context
plasmashell: error creating screencast "Failed to connect PipeWire context"
...

Is there some problem with kwin_wayland or a pipewire package missing? It seems like many people get these messages so some further information would be useful.

I would like to have a way of switching the audio output device (internal speakers/headphones to bluetooth speakers etc) by keyboard actions (which I usually can do without searching, finding and putting my glasses on my nose). Plasma tray elements can be activated with shortcuts, and thus I can connect, disconnect, switch between bluetooth devices by keyboard, because when the drop-down menu is visible, selection with arrow-keys and Enter to activate does the trick. But that doesn't work when trying to switch between audio devices themselves. I can bring forth the audio volume tray element with a shortcut: but further interaction by keyboard is limited to volume level. There is a widget called [audio device switcher](https://store.kde.org/p/1195707/) which brings the options more to the front, but its shortcut does nothing. Overall, it lacks keyboard interaction. The closest thing to what I want is to simply disable bluetooth by the first method *IF* that device is the one that is currently playing...

I'm using KDE Plasma with KWin window manager on a dual-monitor setup. The monitors have different resolutions and sizes, which causes the mouse pointer often get "stuck" in the corner where the two screens meet and a lot of time i can't find my cursor (because it got stuck somewhere). **The Goal:** When I use Ctrl+Tab to switch between windows, I want the mouse pointer to automatically be at the top-left corner of the newly focused window's monitor — regardless of which screen the window is on. I often have to move the cursor manually across monitors, and the inconsistent layout makes it difficult. Ideally, I want this to be: Automatic (when a window is focused) Manually Toggleable (enable/disable this behavior) There is kwin script that doing this in x11 , but not wayland:

$ cat /etc/os-release
RELEASE_TYPE=stable
PRETTY_NAME="Fedora Linux 41 (KDE Plasma)"

$ uname -r
6.15.5-100.fc41.x86_64

$ plasmashell --version
plasmashell 6.4.2

$ kwin_wayland --version
kwin 6.4.2

$ echo $XDG_SESSION_TYPE
wayland

$ kscreen-doctor -o
Output: 1 LVDS-1 12b909d5-b42a-4b0a-a5aa-be5426328038
        priority 1
        Geometry: 1920,0 1366x768
        Scale: 1
Output: 2 HDMI-A-1 226c7f57-ff7d-4b83-9c56-b7f3d753fa84
        priority 2
        Geometry: 0,0 1920x1080
        Scale: 1

I'm using KDE Plasma with Dolphin on Debian 12 Bookworm, and I want to completely disable all tracking and history features related to: - Recent Files - Recent Folders - Clipboard History - Search History - Recently Used Applications I want also to clear any data and history that has already been collected by these features. How to prevent KDE from re enabling or recreating those logs. Im looking for a thorough and systemwide solution that ensures KDE does not track or show anything from past activity. What is the correct way to achieve this?

I have a Logitech M325 mouse and use KDE Plasma 5 on X11. I am a long-time middle-button paster. I love the newer hi-res wheels for actually scrolling things, especially given that I can just put a spin on it However, I've found it difficult to paste because pressing the wheel often results in a bit of scroll too. I most often notice this in konsole where I'm pasting to bash and suddenly find myself in older shell history rather than appending to the command I was building. Anyone know of a neat trick to make the first few scroll ticks be ignored or achieve something similar?

There are blinking dots below my cursor, I made a photo of them because they are less visible on screenshots. They appear and disappear randomly when cursor changes its type (default, loading, window stretching etc). Some of those dots blink and change color. How do I fix it? Debian unstable, KDE Plasma, Vega 64 GPU.

I have some problems installing Nvidia drivers on my Kubuntu system and to get them working (GPU-Model: GeForce GTX 980 Ti). I tried it first in the standard way: $ sudo add-apt-repository ppa:graphics-drivers/ppa $ sudo apt-get update $ sudo apt-get install nvidia-driver-450 The installation finished, but after restarting, the new drivers don't work very well. I'm using a 4K monitor with 3840x2160 (16:9) resolution, but with the driver in use, it only allows for a resolution of 1024x768 (4:3), so my whole screen gets distorted. Also, the command nvidia-smi fails: NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. Furthermore, after removing the drivers manually and restart, everything is back to normal. I tried with this method instead: $ sudo ubuntu-drivers autoinstall, but I get the same results. Then, I tried to execute the runfile provided by NVIDIA on their download site, but it fails because it is unable to disable Nouveau (the current Kernel driver in use). I also executed this command: lspci -vnn | grep VGA -A 12 to check. This is what I get when running normal: And here the same output with NVIDIA drivers enabled: 01:00.0 VGA compatible controller : NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at f6000000 (32-bit, non-prefetchable) [size=16M] Memory at e0000000 (64-bit, prefetchable) [size=256M] Memory at f0000000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: Kernel modules: nvidiafb, nouveau 01:00.1 Audio device : NVIDIA Corporation GM200 High Definition Audio [10de:0fb0] (rev a1) Subsystem: NVIDIA Corporation GM200 High Definition Audio [10de:17c8] Any advice how to get the NVIDIA drivers installed and working on Kubuntu? I tried pretty much every installation guide, but none of them really worked.

This theme (Gently) used to make the highlighted areas of VLC in the image below transparent, now it doesn't. Other applications are working fine (Kate, Dolphin, plasmoids, menus). I've been playing around in InkScape for hours but no changes

I wanted to install kde plasma, so I followed the next steps: pacman -S xorg-server xorg-apps xorg-xinit xterm pacman -S xf86-video-nouveau pacman -S plasma-meta kde-applications-meta pacman -S sddm systemctl start sddm.service But when i run systemctl start sddm.service to start KDE plasma in the login screen doesn't apper the mouse but it's there because I can move the profile the mouse seems invisible on the other hand when I type the password and enter I have a black screen but this time I can see the mouse. How i can solve it? Btw i installed gdm and works why kde plasma not?? Thx.

In the Plasma Renderer, there's an option that says "GL Core Profile" and I can force it if I want to: What is it and what does it do if I force it?

I can’t log into my KDE-Plasma-Desktop on my Debian 12.x after deleting some KDE-specific packages. The login screen appears, but nothing happens when I enter my password. I was trying to delete some packages to make the system leaner. What should I do?

My File, Edit... Menus are gone from the Dolphin file manager. For the life of me I cant figure out how to get it back. Thank you.

In KDE System Monitor > Applications, in KDE Plasma 6.x, there is an option to send signals to various applications. For example SIGTERM, SIGINT, SIGKILL, etc. Please see the attached screenshot for more details. How can other signals like SIGQUIT or SIGABRT be sent? Is there some way to configure this?

In KDE Dolphin there is a mechanism to open a terminal/Konsole window by using the shortcut key ALT+SHIFT+F4. Is there a mechanism where the terminal that is opened only from Dolphin opens with a specific Profile? Is there a way to configure this? Setting a profile as default in Konsole application results in all the terminal windows opening with that specific profile, even those opened from within Dolphin. The objective is to distinguish between terminals/Konsole that are opened from within Dolphin and those terminals/Dolphin that are opened from outside of Dolphin by using the universal key combination CTRL+ALT+T or some other means. * KDE Plasma Ver 6.0 * QT version 6.0

I recently upgraded my laptop to Debian 13 test. I lost the shape of KDE Plasma, and can't install theme either manually or from store. The error message I got when I want to install from store is

Installation of /tmp/OhyYxP-Nordic.tar.xz failed: Could not install dependency: 'kns://colorschemes.knsrc/api.kde-look.org/1326271'

The instructions [here](https://unix.stackexchange.com/questions/465089/kde-plasma-broken-after-upgrade) didn't worked.

I recently switched to Fedora KDE 36, with Plasma 5.25.2. Using X11, because I'm experiencing bad visual glitches with Wayland (NVIDIA GPU). Now I would like to enable some form of **transparency+blur** on Plasma's Breeze theme (dark). I have been searching for some time now, but I have not found a solution that is applicable/up-to-date. Here's what I tried: - Go to System Settings -> Appearance -> Application Style, click the Configure style button on Breeze, go to the Transparency tab and change it: That doesn't do anything. - Look for transparent Breeze themes. I read somewhere that one "needs to use a theme that supports transparency". First result is always Breeze Transparent , but that's a Yakuake skin, so don't bother. Tried KvKonqi and Genome Dark with Kvantum. Not similar enough, and they don't respect the accent colour. They allow for some spotty transparency though (in Dolphin every other line is opaque...) - Go to System Settings -> Window Management -> Window Rules -> Add New... and create a transparency rule for every window. That works, but it does not apply blur - even though in System Settings -> Workspace Behaviour -> Desktop Effects, Blur and Background contrast are enabled. There is also the Translucency option, and it allows me to make moving windows translucent, which works okay. They don't blur either, though. - There is this Reddit post claiming that one can simply edit /usr/share/plasma/desktoptheme/default/metadata.desktop and change contrast to a higher value. This file does not exist on my machine, but I do have a /usr/share/plasma/desktoptheme/F36/metadata.desktop with the appropriate entry. Could not see any change. Does anybody have a working solution? Note that panel transparency is working, and the one app that allows transparency while respecting the blur settings is Konsole.

*Picture: Debian 12 Bookworm with Plasma 5.27 and Lightly installed from boehs's fork . Colour Scheme is called "Valo" and it's soon to be published in KDE Store / Pling.* Intended as a general guide for "***how-to-make-KDE-Plasma-applications-translucent***" for most Linux distributions while using colour schemes based on **Luwx/Lightly** . The three new options are in random order - I encourage you to try them and choose whichever the best suits your needs. ---- **Kvantum Engine** is a different approach and the colour schemes made for Lightly ***possibly are not translucent when using Kvantum***. --- **I would like to express my deepest gratitude** to **Luwx** -the original creator of Lightly - you have made something marvelous - to boehs and many others who have updated and maintained the original work - **and to creators of the new options**: **Séra Balázs** for Darkly, **ekaaty** for vinyl-theme and **taj-ny** for kwin-effects-forceblur. --- My hobby is to create transparent / tranlucent colour schemes based on Lightly - I am creator of Alpha colour scheme which is used as a reference in kwin-effects-forceblur aka *Better Blur*. My full set of colour schemes can be found in KDE Store / Pling (some old are not so good) and more are to published soon. Most of them are translucent when using Lightly based solutions. **When downloading colour schemes via System Settings' "Get new color schemes" you can find most of them with key word "lightly"**. --- If you have knowledge of how to install Lightly to a distribution not included here - please share it with us by writing an answer or a comment.

**The currently blocking question: What can we change anywhere in the Live ISO on boot that will cause the thing that Grub should be launching to emit logs explaining why it just quits and hangs?** ***OR*** **What command can I run from the command line that is the same as what GRUB would have done to launch the Live USB experience? Perhaps from that I could read manuals and add useful diagnostic flags.** I'm trying to run Fedora-KDE-Desktop-Live-42-1.1.x86_64.iso * (written to 4gb USB by Fedora Media Writer) on a Surface Laptop 3. I'm able to boot to it initially and choose any of the choices (run, test media & run, edit commands, command-line, troubleshoot). After any variant of *run* it is stuck on a blank screen. I've seen several reports on these symptoms on reddit and fedora forums with no resolution. I figure I'd try here and include a piece of information that I haven't seen elsewhere: The main command is:

setparams 'Start Fedora-KDE-Desktop-Live'

       linux ($root)/boot/x86_64/loader/linux quiet rhgb  root=live:CDLABEL=Fedora-KDE-Live-42 rd.live.image
       initrd ($root)/boot/x86_64/loader/initrd

(By the way, file syntax seems to be a Grub & possibly "Kickstart" file format?) When running it there's an underscore cursor which doesn't move or output anything, a Microsoft Surface touch keyboard available. The touch keyboard widget responds to clicks to open/dismiss, but after a few seconds that stops responding. Removing quiet rhgb doesn't do anything. I haven't found any --verbose kind of options either. Here's the new information: **If I add some echo statements, I can see that the whole script completes!** I guess it hangs because it thinks it has nothing else to do:

setparams 'Start Fedora-KDE-Desktop-Live'

       echo 11
       linux ($root)/boot/x86_64/loader/linux quiet rhgb  root=live:CDLABEL=Fedora-KDE-Live-42 rd.live.image
       echo 22
       initrd ($root)/boot/x86_64/loader/initrd
       echo 33

Running this shows all three expected outputs within ~20 seconds.

11
22
33
_

So does anyone know what ought to be happening instead? Is there some other script on the memdisk I could modify first for more diagnostic information to find out what is quitting silently? * I've now the Gnome-based Fedora-Workstation-Live-42-1.1.x86_64.iso too and it misbehaves the same way.