| |
@@ -1,8 +1,8 @@
|
| |
diff --git a/libdiscover/backends/PackageKitBackend/PackageKitBackend.cpp b/libdiscover/backends/PackageKitBackend/PackageKitBackend.cpp
|
| |
- index 106a93322..d1bdd2422 100644
|
| |
+ index 096f659de..60dd417d6 100644
|
| |
--- a/libdiscover/backends/PackageKitBackend/PackageKitBackend.cpp
|
| |
+++ b/libdiscover/backends/PackageKitBackend/PackageKitBackend.cpp
|
| |
- @@ -422,7 +422,7 @@ void PackageKitBackend::checkForUpdates()
|
| |
+ @@ -473,7 +473,7 @@ void PackageKitBackend::checkForUpdates()
|
| |
|
| |
if (!m_refresher) {
|
| |
acquireFetching(true);
|
| |
@@ -12,7 +12,7 @@
|
| |
connect(m_refresher.data(), &PackageKit::Transaction::errorCode, this, &PackageKitBackend::transactionError);
|
| |
connect(m_refresher.data(), &PackageKit::Transaction::finished, this, [this]() {
|
| |
diff --git a/libdiscover/backends/PackageKitBackend/PackageKitNotifier.cpp b/libdiscover/backends/PackageKitBackend/PackageKitNotifier.cpp
|
| |
- index 25eabb2ce..f2ddaa6cd 100644
|
| |
+ index 5332e0b8a..e3b5a6dfd 100644
|
| |
--- a/libdiscover/backends/PackageKitBackend/PackageKitNotifier.cpp
|
| |
+++ b/libdiscover/backends/PackageKitBackend/PackageKitNotifier.cpp
|
| |
@@ -53,7 +53,7 @@ PackageKitNotifier::PackageKitNotifier(QObject *parent)
|
| |
@@ -24,9 +24,9 @@
|
| |
regularCheck->start();
|
| |
if (!value.isEmpty())
|
| |
qWarning() << "couldn't understand value for timer:" << value;
|
| |
- @@ -262,7 +262,7 @@ void PackageKitNotifier::onDistroUpgrade(PackageKit::Transaction::DistroUpgrade
|
| |
- void PackageKitNotifier::refreshDatabase()
|
| |
- {
|
| |
+ @@ -267,7 +267,7 @@ void PackageKitNotifier::refreshDatabase()
|
| |
+ }
|
| |
+
|
| |
if (!m_refresher) {
|
| |
- m_refresher = PackageKit::Daemon::refreshCache(false);
|
| |
+ m_refresher = PackageKit::Daemon::refreshCache(true);
|
| |
This is an age long bug.
There is a 5 minutes timer on login that cancels any offline update started before it. So discover would say "Ready to reboot" but upon reboot no update would happen.
Proposing this for F38 final since it's likely that one may start updates right after the first boot.