| Summary: | Muon does not find available packages to install after fresh install | ||
|---|---|---|---|
| Product: | [Unmaintained] muon | Reporter: | Rohan Garg <rohan> |
| Component: | muon | Assignee: | Aleix Pol <aleixpol> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | minor | CC: | andysem, rohan, sitter, stasnel |
| Priority: | VLO | ||
| Version: | 2.1.3 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Rohan Garg
2014-02-13 18:08:56 UTC
The xapian cache most certainly wasn't up-to-date when muon was started because only muon (respectively moun-notifier after IIRC 3 minutes) will trigger the initial update because the kubuntu installer doesn't do it. So what I can reproduce is: no cache -> muon -> updates cache -> when done muon's internal package list doesn't get updated apparently -> restart muon -> search works. This mostly seems like a cache reloading problem that wouldn't be there if the kubuntu installer simply made sure to generate the xapian cache. QApt::Backend::Search > if (d->xapianTimeStamp == 0 || !d->xapianDatabase) { d->xapianDatabase is only set in in Backend::openXapianIndex, which will not set anything if there was no cache to begin with > d->xapianDatabase = new Xapian::Database("/var/lib/apt-xapian-index/index"); consequently search always aborts because it has no database instance to work on. furthermore Backend::openXapianIndex is not called by any muon application after Backend::xapianUpdateFinished() was emitted, or more to the point all applications will try to open and if it fails, try to update, but then never try to open again. the probably most appropriate and simple fix would be to have Backend::emitXapianUpdateFinished call Backend::openXapianIndex, so that a finished update always tries to open the cache, thus providing a d->xapianDatabae and enabling ::search to actually do anything. we'll have to wait for Aleix to provide some input on that approach though. all in all this issue has next to no impact as it only ever happens when there is absolutely no cache (i.e. directory missing), once a cache is present (even if a very old one) the database can be opened and search will work. to reproduce run > sudo rm -rf /var/cache/apt-xapian-index and start muon. I think that what Harald says makes sense. Can't do much without the xapian db anyway. Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. Muon is no longer maintained, please switch no a supported alternative like https://apps.kde.org/discover/ or the package manager native no your system. Sorry for the inconvenience. (In reply to Christoph Cullmann from comment #6) > Muon is no longer maintained, please switch no a supported alternative like > https://apps.kde.org/discover/ or the package manager native no your system. Just wanted to comment that Discover is not an alternative to Muon as it is not a package manager. Without Muon, KDE doesn't have a native package manager. |