https://bugs.kde.org/show_bug.cgi?id=525919
--- Comment #12 from [email protected] --- (In reply to Norbert Harrer from comment #11) > (In reply to yhl3051 from comment #10) > > Something changed because selecting "Restart" now works! I will keep this > > ticket open though, unless someone says I can close it. > > It's still reproducible here as of today, so whatever changed on your > side has not reached my machine, or is not in Discover. > > Setup: Fedora 44, plasma-discover 6.7.5-1.fc44, plasma-workspace 6.7.5, > kwin 6.7.5, PackageKit 1.4.0, fwupd 2.1.8. Same procedure as before: one > pending RPM update, Restart chosen from the dropdown, update left to > finish. All windows closed, the session stayed up, and the journal shows > the same pattern: > > 21:59:23 Started dbus-:[email protected] > 21:59:28 plasma-shutdown: KWin failed to complete logout > > The offline update was armed afterwards (/system-update set, action > "reboot"), as before. > > To narrow down what fixed it for you, could you check: > > - Did you use the Restart option from the dropdown at the bottom? > The restart button (not the dropdown) on the page shown after the > update finishes takes a different path: it opens the logout prompt, > and has always worked here, also on 6.7.5. > - Which packages changed on your system since the last failure? > ("dnf history list" or "rpm -qa --last") To begin with, I did choose the dropdown, chosen before pressing Update. Same procedure as the failing runs. Nothing relevant changed here however. Current versions, same as when it was failing: plasma-discover-6.7.5-1.fc44 plasma-discover-flatpak-6.7.5-1.fc44 plasma-workspace-6.7.5-1.fc44 kwin-6.7.5-1.fc44 PackageKit-1.4.0-1.fc44 fwupd-2.1.8-1.fc44 The journal shows 20 consecutive Discover-triggered failures from Sep 18 to Oct 14 08:47 EDT, then the one success at about 10:53 EDT. So the success has a cause I could not identify. It may be timing, or some state difference I did not capture, rather than a fix. Differences I could find for the successful run: - Only 3 RPM updates, all third-party (google-chrome-stable, google-chrome-canary, chatgpt), no Flatpak or firmware entries. - That Discover instance was launched from a terminal with QT_LOGGING_RULES="*discover*=true" (I was debugging another bug), which may change timing slightly. I checked whether Flatpak updates in the same run correlate with the failure: only 3 of the 20 failing runs had any, so they are not the trigger. At my next update I will capture the session bus with the same busctl command you used and report the logoutAndReboot count. The log analysis was done with AI assistance; the data is from my own system. -- You are receiving this mail because: You are watching all bug changes.
