Mastodawn

Luna Lactea May 1, 2025

I just spent three hours ricing my top panel in Plasma only to realize it's past bed time & I'm still on the first section of Panel Colorizer. I finished the rest pretty quickly though. I generated a nice color palette from my wallpaper but I can't figure out how to apply it to my terminal properly. I need to change my fish prompt to be able to accept it so the text isn't the default colors, which is hard to see against the background color that does apply properly, but I don't know how to edit it & I only barely managed to make it look like bash. Hyfetch also thinks my shell is bash despite it being set to fish with chsh & in my Konsole profile, & echo $0 prints nothing. I have no idea what's going on with that, but chsh & changing it in Konsole worked fine on KDE Neon, I guess Fedora just has it stuck as bash forever. I still need to figure out what desktop effects I want & figure out how to apply my color palette to the rest of the system too.

Luna Lactea May 1, 2025

Has anyone else had this issue with the shell still being recognized as bash no matter what you do on Fedora?

Luna Lactea May 1, 2025

I don't know what I did, but it's recognized as fish correctly now.

Luna Lactea May 1, 2025

Here's what it looks like right now. It still needs work.

Luna Lactea May 2, 2025

Now I can't log in when turning it on

neocat_cry_loud

SDDM says yes & then lets me in, then it goes back to SDDM. I can't keep doing this shit.

Luna Lactea May 2, 2025

I can log in fine on a different TTY with just a terminal though.

Luna Lactea May 2, 2025

What the fuck even causes this? I didn't even do any updates. Plasma just doesn't start & it sends me back to SDDM to log in again.

Luna Lactea May 2, 2025

I have a class that I'm supposed to be doing RIGHT NOW. This computer is doing this on purpose!!! The only thing I can think of is maybe something in my dotfiles is making it crash since I customized alot.

Luna Lactea May 2, 2025

I'm going to cry

Luna Lactea May 2, 2025

Systemd can't start plasmashell. "This application failed to start because no Qt platform plug-in could be initialized. Reinstalling the application may fix this problem." & "qt.qpa.plugin: Could not load the Qt platform plugin 'xcb' in '' even though it was found."

Maybe I can export this log to a text file & copy it to my phone. Somehow this laptop is still connecting to Wi-Fi so I can use magic-wormhole. If that doesn't work I have ADB installed & I can use that to copy the file to my phone.

evil princess May 2, 2025

@jackemled a quick and dirty idea would be to install a different desktop and tell sddm to run that for now, something like twm is small, but it's X11 and weird because it's old, otherwise xfce is a good choice as a backup

Luna Lactea May 2, 2025

@theking I don't even have X11 installed on this laptop apparently💔
Maybe I could install Sway?

Luna Lactea May 2, 2025

@theking Or is Qt a big Wayland thing & not just a Plasma thing? If anything depends on Qt I won't be able to use it until I fix Qt. I don't even know how to manually start a desktop like that or tell SDDM to use a different one. On my desktops at home SDDM has a dropdown menu in the corner to switch between Plasma-X11 & Plasma-Wayland, but I don't know how to add entries to that menu.

@jackemled @theking Qt is a GUI toolkit for application development in C++ that predates the first versions of the K Desktop Environment

KDE Plasma and KDE Gear are the most prominent use of Qt on Linux, but they by no means own Qt (infact, plenty of Windows-only software such as AMD’s Radeon configuration tool thingy are built with Qt)

As for Sway: it doesn’t depend on Qt, you can install and use it even with broken Qt

Luna Lactea May 2, 2025

@Reiddragon @theking Thank you! I'll probably use Sway as a backup then.

Luna Lactea May 2, 2025

@Reiddragon @theking Or maybe Niri if it doesn't depend on Qt😳

@jackemled @theking afaik only Kwin depends on Qt. Most other Wayland WMs are built on wlroots instead, which is its own thing and doesn’t depend on any toolkit

Luna Lactea May 2, 2025

@Reiddragon @theking I'm starting to think I was actually using X11 the whole time

neocat_cry_loud

My issue seems to be related to X11, unless XWayland is that vital of a component. I also don't have the option to switch display servers on the login screen like I do on my desktop, which I do know has both X11 & Wayland installed.

@jackemled @theking most compositors that I’m aware of can be used without XWayland (labwc straight up kills the XWayland server if you don’t have any X11 clients running for long enough, and Sway allows disabling it in the configuration file, with both of them only starting the XWayland server after an X11 client tries to connect (unless configured otherwise))

What’s the issue, exactly? reading the thread I’m seeing something about getting kicked back to SDDM after logging in?

PS: turns out I’m actually running w/o XWayland right now

Luna Lactea May 2, 2025

@Reiddragon @theking When starting the computer, it boots as usual & correctly shows the SDDM login screen. When putting in the correct password, it seems to log in & shows the black screen with a cursor that it usually does before Plasma loads, then it goes back to the SDDM login screen. When putting in the incorrect password, it never leaves SDDM & gives a "login failed" password. Since the results look different I know I'm successfully logging in. When switching to a TTY it also allows me to log in with no issue & access my shell.

Luna Lactea May 2, 2025

@Reiddragon @theking Also it turns out I'm definitely using Wayland, because all of the Wayland stuff is installed. I have some X11 stuff installed too but it seems to just be for XWayland.

@jackemled @theking you can also check with echo $XDG_SESSION_TYPE

Luna Lactea May 2, 2025

@Reiddragon @theking It says tty.

@jackemled @theking oh, you have to type that while inside a desktop

Luna Lactea May 2, 2025

@Reiddragon @theking I can't get to the desktop, that's the problem💔

@jackemled @theking oh, I thought you meant that launching the desktop from TTY worked

are you getting any errors if you try launching from a TTY? (you can start sway just typing its name, forgot the command to launch a Plasma wayland session from the TTY)

Luna Lactea May 2, 2025

@Reiddragon @theking I didn't try launching the desktop from my tty because I didn't know how. I actually just found out & tried it & got it to work. Now the issue is why SDDM can't do it anymore. The resource I found mentioned that fish was the issue, but if fish is the problem, why am I not having this issue with any of my other computers, which also have fish set as the shell?
https://furry.engineer/@jackemled/114438905598835077

Luna Lactea (@[email protected])

@Foxarc @[email protected] I FOUND https://discuss.kde.org/t/cant-start-plasma-from-sddm-anymore-only-from-cli/25575 Running `startplasma-wayland` works! I get into my desktop!! I have no idea why SDDM is unable to start Plasma though. It's a SDDM issue, not a Plasma issue & probably not a display server issue!

Furry.Engineer - Duct tape, hotfixes, and poor soldering!

@jackemled @theking the shell should have no effect on how the display manager launches the desktop (tbh I want to say that whoever’s blaming Fish for this is full of shit, but it could also be SDDM or Fedora does something exceptionally dumb)

Luna Lactea May 2, 2025

@Reiddragon @theking It seems to be SDDM, but I wonder if maybe Fedora has SDDM set up to run a shell script to start Plasma instead of launching it directly or something. Maybe that script doesn't work right in fish. That doesn't explain why it took so long & so many restarts after setting up fish the way I like for it to happen though. I don't know how to configure SDDM or else I would investigate & compare it to my other computers.

@jackemled @theking Idk how SDDM does things specifically, but the way you’re supposed to run shell commands from a program is to always call /bin/sh regardless of what the default shell is for a given user specifically so different parsing rules of different shells don’t break things

I have no reason to believe SDDM does something different because that would be the dumbest shit ever

my guess is either some downstream patches from Fedora breaking things, or Fedora building from a buggy commit (both of which have happened before with Fedora)

Luna Lactea May 2, 2025

@Reiddragon @theking Exactly, whenever I write a script I start with #! /bin/bash, because bash is almost always preinstalled, so I get a standardized environment for the script to run in. I wonder what really causes this & why it seems to want X11 resources when it's supposed to be Plasma.

@jackemled @theking SDDM runs in X11 by default afaik, so there’s that (tho I doubt that’s what’s causing issues)

tbh having some logs would help greatly in troubleshooting this; can you get anything with journalctl?

Luna Lactea May 2, 2025

@Reiddragon @theking I shared my journalctl log as a 0x0.st link somewhere in the thread.

@jackemled @theking which session is selected in the bottom-left corner in SDDM?

Luna Lactea May 2, 2025

@Reiddragon @theking There's no menu there. On my desktops that have KDE Plasma there is a menu there, but on this laptop with Fedora there is nothing to select different sessions, even if I log out or switch user.

@jackemled @theking uhhhhh that’s not normal

there should be at least 2 sessions there for Plasma X11 and Plasma Wayland (and a 3rd one for Sway if you have that installed)

tbh fedora fuckery is sounding more and more likely

Luna Lactea May 2, 2025

@Reiddragon @theking That has to be it. I wonder why it's so fucked up.

@Reiddragon @theking I did chsh & switched back to bash & SDDM works again! What the fuck!!!!!!!!

@jackemled @theking ok something’s definitely wrong there; I’ve used all sorts of wacky shells on my Linux system (including xonsh and powershell (it was for a shitpost)) and SDDM never failed to launch Plasma with that