#asahi · 2025-11-03 20:41
jannau"atomic commit failed: Permission denied" might be serious. The timestamp is after sdd is already running?#asahi · 2025-11-03 20:40
jannauquaff: "Could not find edid for connector" is expected for laptop displays / eDP#asahi · 2025-11-03 20:37
quaffI'mm gonna uninstall toshy and see if that helps#asahi · 2025-11-03 20:37
quaffI think that kwin_wayland_drm is just a warning#asahi · 2025-11-03 20:37
quaffkwin_wayland_drm: Could not find edid for connector DrmConnector(id=41, gpu=\"/dev/dri/card3\", name=\"eDP-1\", connection=\"Connected\", countMode=1)\n"#asahi · 2025-11-03 20:37
quaffNov 03 12:31:32 Pluto sddm-helper-start-wayland[1326]: "kwin_wayland_drm: atomic commit failed: Permission denied\n"#asahi · 2025-11-03 20:36
jannau`journalctl -b0 -g 'sddm|kwin' in the stuck state hopefully reveals something#asahi · 2025-11-03 20:35
quaffokay ssh enabled. I'll try and load plasma and check journalctl#asahi · 2025-11-03 20:34
jannauquaff: I see a single instance of "gkr-pam: unable to locate daemon control file" as well without noticeable effect#asahi · 2025-11-03 20:33
quaffjannau: I don't lemme turn it on and try#asahi · 2025-11-03 20:33
quaffI see that error, not sure if it's related#asahi · 2025-11-03 20:33
quaff"gkr-pam: unable to locate daemon control file" in journald#asahi · 2025-11-03 20:33
jannauquaff: can you access the system via ssh?#asahi · 2025-11-03 20:32
jannautty switching needs support from the program running the the graphical session. so if that hangs it's not possible to switch#asahi · 2025-11-03 20:30
quaffonly thing I see on my screen is what was on tty2 before I jumped to sddm that second time#asahi · 2025-11-03 20:29
quaffokay. just going from the top: I booted up to sddm, dropped to tty2, logged in and stopped sddm, ran startplasma-wayland (worked!), logged out and dropped back to tty2, started sddm up again, and tried to log into plasma via sddm, but the screen seems to be frozen. I can't jump between tty2-<*>. caps lock still works, so system isn't completely frozen#asahi · 2025-11-03 20:28
jannaudid you retry plasma from sddm?#asahi · 2025-11-03 20:23
quaffI have! I'm up to date. I just tried running startplasma-wayland, and it worked... so something seems to be happening between sddm <-> plasma/cosmic/gnome (I tried all of these as well)#asahi · 2025-11-03 20:23
jannauor maybe not as kwin at least starts to show sddm#asahi · 2025-11-03 20:22
jannauquaff: maybe the same issue? have you tried upgrading the system from the command line?#asahi · 2025-11-03 20:21
jannauquaff: I think so but I wouldn't expect that you will be able to see anything from there you can't see in the journal when starting plasma from sddm#asahi · 2025-11-03 20:21
austriancoderjannau: correct..#asahi · 2025-11-03 20:20
jannauaustriancoder: so some inconsistent package state?#asahi · 2025-11-03 20:15
quaffafter booting up, and sddm loads.. if I drop to tty2/3, stop sddm, then run startplamsa-wayland manually, that should work, right?#asahi · 2025-11-03 20:14
quaffjannau: fair. I remember it did reboot (and logged in) properly once after upgrading. I was messing around with toshy afterwards (I dont' think it messages with anything?) and the second reboot was when I was getting issues. I'm testing now again and seeing it's stuck on a black screen after I attempt to login via sddm#asahi · 2025-11-03 20:13
austriancoderhttps://www.irccloud.com/pastebin/sQAJLTmz/#asahi · 2025-11-03 20:13
austriancoderjannau: after enabling wifi via nmcli and ssh into it, I was able to track it down and it works again (and I am not sure how I got into this situation)#asahi · 2025-11-03 20:08
jannauquaff: updated system works here#asahi · 2025-11-03 19:57
jannauupdating a test install as we speak to f43#asahi · 2025-11-03 19:56
quaffjannau: okay I'll dig around a bit more later to see if I can figure out if it's just a quaff issue, or if it's something else#asahi · 2025-11-03 19:54
jannauaustriancoder: can you paste the output of `journalctl -b0 -g 'drm|kwin|sddm' | grep -v audit`? piping it to fpaste would upload it directly to centos' pastebin#asahi · 2025-11-03 19:49
jannaunot really expecting any changes on that front and we would be reluctant to announce it with an unexplained issue#asahi · 2025-11-03 19:48
quaffunless y'all are worried it's something that might be prevalent for everyone else. I'll spend a little time later digging to see if I can find the cause. it's probably something stupid I did tho#asahi · 2025-11-03 19:48
quaff🙏 no worries, I'll wait until 43 is officially out, then I'll try again. no rush!#asahi · 2025-11-03 19:46
chaos_princessprobably a different issue then#asahi · 2025-11-03 19:45
quaffchaos_princess: hmmm I think I waited a longer than that and it stayed a black screen when I toggled through the ttys looking for plasma (tty1?)#asahi · 2025-11-03 19:44
quaffjannau: offline... yes! there was a little offline phase, I remember thinking "hm.. I don't remember doing this from 41->42" #asahi · 2025-11-03 19:43
chaos_princessi sometimes notice it fail to come up after sddm, but the solution was always to switch to a different tty and wait 1-2 seconds#asahi · 2025-11-03 19:43
jannauquaff: ^^^#asahi · 2025-11-03 19:43
jannauyou did `dnf system-upgrade --releasever=43 download` and then did the offline upgrade?#asahi · 2025-11-03 19:43
jannausorry. I should have read mote carefully. after sddm is a different thing#asahi · 2025-11-03 19:40
quaffjannau: ah okay. just wanted to lend my voice to any issues related (seemingly) to f43. but everything else seems to work okay. booting, sddm, tty login, etc.#asahi · 2025-11-03 19:38
quaffcouldn't see anything in journalctl, so I dropped to tty3 and tried to run startplasma-wayland, and saw some error that looks like it might be drm related, not sure tho.#asahi · 2025-11-03 19:38
jannauquaff: if it's the issue I suspect it's timing and possibly a change in behaviour in kwin 6.5.1#asahi · 2025-11-03 19:36
quaffI stupidly upgraded to f43. using sddm + plasma. upgraded f42->f43, rebooted, then rebooted again, when I login (after sddm), plasma doesn't start. I tried to troubleshoot, but the error seems to be related to a lack of a drm driver? I stopped there. I'm unsure if it was f43, or something I did, will wait for the official release and try again.#asahi · 2025-11-03 19:33
jannaustill, restarting sddm does not help? the only issue I'm aware of is a race between sddm start and display driver probing (replacing simpledrm with dcp)#asahi · 2025-11-03 19:32
austriancoderjannau: does not fix it .. makes it even worse: switching tty's does not work any more#asahi · 2025-11-03 19:30
austriancoderjannau: I just did a dnf update - not upgrade to newest fedora 43#asahi · 2025-11-03 19:30
jannauaustriancoder: restarting sddm from a tty ssh does not fix it?#asahi · 2025-11-03 19:29
jannaumy f43 test system is gnome/gdm but has no issues