mub

I'm using EndeavourOS (Arch btw) with KDE plasma 6.x (Wayland), SDDM, and systemd as boot manager. I have 2 displays, one HDMI-A-1 (1080p) and one on DP-1 (Ultrawide).

When I boot the password entry cursor defaults to the HDMI display, but I want it to default to the DP-1 display.

I've tried a few things, mostly suggestions from ChatGPT. But nothing has worked. The weird thing is at boot the boot menu and boot messages all appear on DP-1, and it is set as primary in KDE and that works fine as well. It is just the logon prompt that defaults to the wrong display.

Things I've tried so far.

• Adding video=DP-1:e to the options in the systemd entry - (No effect)
• Edited /etc/sddm.conf.d/wayland.conf to run a script that did the following: kwriteconfig6 --file startkderc --group General --key PrimaryScreen DP-1 (didn't fix it, actually broke the logon process so had to remove it)

I'm just not familiar enough with how SDDM works so hoping for some good pointers to provide the answer or point me in the right direction.

I'm running EndeavourOS and Windows 11. Each OS is on a separate disk, but I have a data disk that is currently NTFS that mount in both OSes. NTFS causes problems for some things in Linux, and I'm worried it'll bork the drive for windows eventually, so I'm keen to find an alternative. I've read about the WinBTRFS driver so wondering if that is a better way to go?

I don't want to run a server with a share to access this data because it is way to slow for my needs.

I have 2 screens attached to my EndeavourOS (KDE Wayland) PC. The secondary is HDMI the primary is Display Port. The boot menu and boot messages all appear on the primary display, but once the login appears the password entry defaults to the secondary. How do I force it to default to the primary?

Not everything actually requires a GUI, obviously. But anything that requires configuration, especially for controlling a hardware device, should have a fully functional GUI. I know Linux is all about being in control, and users should not be afraid to use the command line, but if you have to learn another bespoke command syntax and the location and structure of the related configuration files just to get something basic to work then the developer has frankly half arsed it. Developers need to provide GUI's so that their software can be used by as many people as possible. GUI's use a common language that everyone understands (is something on or off, what numeric values are allowed, what do the options mean).

Every 12 to 18 months I make an effort to switch to Linux. Right now I'm using Archlinux, and it has been a successful trip so far, except my audio is screwed, I can't use my capture card at all, I had issues with my dual displays at the start, and the is no easy way to configure my AMD graphics card for over clocking or well anything basic at all.

I'm not looking for a windows clone, I love that I can choose different desktop environments and theme many of them to death. I even like the fact there are so many distros. Choice is a big part of linux, but there is clearly a desire to get more people moving away from Windows and until that path is 95% seamless most people just won't. Right now I think Linux is 75% to 85% seamless depending on the use case and distro but adding more GUI front ends would, imho, push that well into the 90% zone.

GUI is not a dirty word, it is what makes using a new OS possible for more people.

EDIT: Good conversation all. This is genuinely not intended to be a troll post, I just feel it is good to share experiences especially on the frustations that arise from move between OSes.

Server

• Lenovo M700 Tiny Mini PC i7 6700t / 16GB RAM / 256GB M.2 + 1TB SSD
• OS - Linux Mint
• Hosting - Plex, qbittorrent, SMB, Minecraft, Terraria

"Core" Switch

• TP-Link 5 Port Gigabit Switch

WIFI and Internet Router / Firewall

• Ubiquity Unifi Dream Machine