https://bugs.kde.org/show_bug.cgi?id=525911

--- Comment #5 from [email protected] ---
```markdown
  **Update — this looks like a regression, not a long-standing bug**

  I hadn't hit this before roughly a month ago, and it was working flawlessly
prior to that. I don't have an exact "last known good" date, but checking `dnf5
history list`, here's every update in that window that touches a component
involved in this bug:

```

2026-08-07  plasma-workspace / plasma-discover  -> 6.7.4-1 2026-08-26  dnf5 /
libdnf5                       -> 5.4.3.0-2  (455 pkgs) 2026-09-02 
plasma-workspace                     -> 6.7.4-2 2026-09-09  dnf5 / libdnf5     
                  -> 5.4.4.0-1 2026-09-10  plasma-workspace / plasma-discover  
-> 6.7.5-1  (current) 2026-09-15  PackageKit                            ->
1.4.0-1  (current, 522 pkgs) 2026-09-18  dnf5 / libdnf5  (05:41)              
-> 5.4.5.0-1  (current) 2026-09-18  first documented failure (18:52)

```

  The `dnf5`/`libdnf5` upgrade at 05:41 landed roughly 13 hours before the
first failure I reported that same day, and `dnf5`/`libdnf5` was updated three
separate times in this window total. I can't pin down the exact update that
introduced this (my "last known good" is approximate), but this feels like a
significant lead given the mechanism I described earlier: the double
`logoutAndReboot()` call from Discover appears to be triggered by
`PackageKit.Offline` D-Bus property churn, and `libdnf5` is what backs
PackageKit's `dnf5` backend and would control how/when those properties get set
and change during an offline-update transaction.

  If a `dnf5`/`libdnf5` behavior change altered the timing or frequency of
`PackageKit.Offline` property-change signals during an offline transaction,
that could explain why this wasn't showing up before and is now — without
Discover's own QML code having changed at all recently (the relevant
`onStateChanged` handler in `UpdatesPage.qml` has been unchanged since it
landed in 6.7.0, well before this window).

  Not conclusive, but seemed worth recording in case it helps narrow down where
to look, or in case anyone else can correlate this against their own update
history.
```

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to