| Summary: | apper-sentinel never times out after an update that needs no reboot/logout | ||
|---|---|---|---|
| Product: | [Applications] apper | Reporter: | Martin Kho <kde-bugs> |
| Component: | general | Assignee: | Daniel Nicoletti <dantti12> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | chgonzalezg, rdieter, todorst |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 0.7.2 | |
Hi, I forgot step 5. close apper :-) Martin Kho Do you still have this issue iirc some problems around this where fixed in Apper 0.7.2, please try with that version. Hi Daniel, Sorry, I overlooked this report. This issue is indeed solved. Please close this report. Thanks, Martin Kho |
After a RefreshAndUpdate or Update check (issued by ApperD) apper-sentinel times out after some time. This, however, is not the case when updates are succesfully installed and there was no need to log out or reboot. apper-sentinel stays active forever, which blocks any future cache-refreshes (see UpdateIcon.cpp->refresh). Reproducible: Always Steps to Reproduce: 1. downgrade a package that needs no logout/reboot 2. wait till apper shows the 'update' for the downgraded package 3. update the package (hope it will be succesfull 4. watch apper-sentinel never times out Actual Results: apper-sentinel never time out, blocking cache-refreshes Expected Results: apper-sentinel time out, cache-refreshes are possible again It looks like apper-sentinel should watch (the results of) the transaction. In ApperSentinel.cpp I see: // connect the watch transaction coming from the updater icon to our watcher // connect(m_updateIcon, SIGNAL(watchTransaction(const QString &, bool)), // m_transWatcher, SLOT(watchTransaction(const QString &, bool))); Is this what can do the trick?