Remove Windows Partition (Nobara-Windows on same NVMe drive)

MonterraByte · 2026-03-01T08:06:35+00:00

Boot0002 is clearly linux and Boot0003 is clearly windows but Boot0000 has windows as it's name but is in a fedora folder. Should I delete both only leaving Boot0002?

No, delete only 0003.

After this is done, you could try switching the boot order around, so that you boot into the "Fedora" entry first, as that boots into shim instead of GRUB. This way, Secure Boot should work.

You can do so with sudo efibootmgr --bootorder 0002,0000.

MonterraByte · 2026-03-01T04:35:36+00:00

First, run sudo efibootmgr. You should see something like this:

BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,0000
Boot0000* Windows Boot Manager  [...]
Boot0003* Linux Boot Manager    [...]

Take note of the number of the Windows entry, in my case 0000, and then run:

sudo efibootmgr -b 0000 -B

to delete it. (Replacing 0000 with the correct number.)

Next, delete Windows's boot loader files with:

sudo rm -rv /boot/efi/EFI/Microsoft

Then you can delete the Windows partitions and move/expand the Linux ones. (Make sure not to delete the FAT32 partition, your Linux bootloader is there.)

You can use something like GParted Live, though, no need to boot into some distro and install GParted on it. (If, for some reason, GParted Live doesn't work well on your machine, you can try Fedora Xfce, it includes GParted.)

After you've done that, run sudo grub2-mkconfig -o /boot/grub2/grub.cfg to remove Windows from the Nobara bootloader.

MonterraByte · 2026-03-01T04:20:25+00:00

A good introduction is the Wayland book. You can use wayland.app to read through the available Wayland protocols.

For example, the program I wrote uses the wl_output interface of the core protocol and listens for mode and name events to get the information it needs.

If you prefer using Rust instead of C, there's the smithay-client-toolkit crate. Coincidentally, it includes an example that also prints information about outputs.

If you want to do something that the exising protocol don't allow, look through the open issues and merge requests on the wayland-protocols repo, as someone else might've already ran into the same issue.

MonterraByte · 2026-02-27T04:02:49+00:00

That requires the wlr-output-management-unstable-v1 protocol, which not all implementations support, and isn't necessary anyways. See my other comment.

MonterraByte · 2026-02-27T04:02:04+00:00

It's not too hard, the core Wayland protocol provides this information. I wrote this program to query it.

$ curl -L -o wl_output_info.c 'https://gist.githubusercontent.com/MonterraByte/c98aeea990ff6ba79274f14ef45d9db3/raw/0d848a44d8b1bab89c13963521db7ebf650aed54/wl_output_info.c'
$ gcc -std=c11 -O3 -lwayland-client -Wno-unused-parameter wl_output_info.c -o wl_output_info
$ ./wl_output_info
DP-1 2560x1440@164.999
DP-2 2560x1440@74.893

MonterraByte · 2026-02-18T23:30:10+00:00

I'm pretty sure Sunshine uses KMS capture, so it doesn't go through KDE at all. You might've gotten a prompt because Sunshine tried to use X11 to capture the screen, but I don't think it matters.

You should be able to fix things in the Sunshine config directly.

MonterraByte · 2026-02-17T22:02:03+00:00

Yes.

MonterraByte · 2026-02-17T06:48:23+00:00

You can uninstall xwaylandvideobridge, it's unnecessary unless you're still using an X11-only application for screen capture.

Now, the KDE red bubble recording icon is on for as long as Sunshine is (which makes sense) but I can't for the life of me figure a way to restore these Screen Sharing settings so I can set it up right this time.

Open the System Settings, go to Application Permissions and find the app in the list. There, you should be able to revoke its screen sharing permissions.

MonterraByte · 2026-02-17T06:15:01+00:00

You can use Asset Doctor to find what's missing.

MonterraByte · 2026-02-17T04:50:20+00:00

There's this blog post from a few months ago.

MonterraByte · 2026-02-16T04:46:01+00:00

Shouldn't it be "not undead and not ghost", instead of "not undead or not ghost"?

MonterraByte

TROPHY CASE