Bug 369301 - Muon doesn't find packages after installing a package
Summary: Muon doesn't find packages after installing a package
Status: RESOLVED UPSTREAM
Alias: None
Product: muon
Classification: Applications
Component: muon (show other bugs)
Version: 5.6
Platform: Kubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Jonathan Thomas
URL:
Keywords:
: 372343 378996 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-09-25 01:07 UTC by Lastique
Modified: 2017-09-29 09:13 UTC (History)
12 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lastique 2016-09-25 01:07:19 UTC
After installing/updating a package in Muon, searching for other packages does not produce any results.

Reproducible: Always

Steps to Reproduce:
1. Start Muon package manager.
2. In the search field, type some package name that you know exists in the repository (e.g. kmail). Note that the package is found and displayed in the list below.
3. Now select and install some package that was previously not installed. Upgrading packages by pressing "Full Upgrade" also works.
4. After the installation completes, type the same package name from bullet 2 in the search field again.

Actual Results:  
The second time the package is not found. In fact the package list is always empty as if no packages ever found through the search field.

Expected Results:  
The search should continue to work.

Kubuntu 16.04, x86_64.
Comment 1 Tony 2016-09-27 20:32:00 UTC
I used to have a similar issue (before i ditch it and went full terminal...) and it was related to muon building a search index.  Let it do its think, close and open it again, that's what worked for me.
Comment 2 Lastique 2016-09-27 21:04:17 UTC
(In reply to Tony from comment #1)
> I used to have a similar issue (before i ditch it and went full terminal...)
> and it was related to muon building a search index.  Let it do its think,
> close and open it again, that's what worked for me.

The search doesn't start to work even if you wait until it finishes rebuilding the index. Only restart helps.

But it would still be a bug even if it started working after rebuilding the index had completed. Somehow other package managers don't have this problem.
Comment 3 popanz 2016-10-11 09:30:39 UTC
Strange, I switched yesterday from Kubuntu 16.04 (backports repository enabled) to KDE Neon 5.8. And have now exactly the same problem. But I'm convinced that I didn't have this problem with Kubuntu, despite the fact, that I think there was the same version installed.
Comment 4 lnxusr 2016-10-25 15:56:15 UTC
I have the same problem.  This needs to be changed to critical because Muon is pretty much seriously broken.
Comment 5 V字龍(Vdragon) 2017-05-18 10:26:44 UTC
*** This bug has been confirmed by popular vote. ***
Comment 6 Joe 2017-05-18 11:21:09 UTC
372343 is a duplicate of this
Comment 7 popanz 2017-05-18 11:51:17 UTC
It's happening not only when a package is installed, but sometimes even when you start muon and just wait a while.
Comment 8 James Cain 2017-06-12 17:27:14 UTC
The same behavior exists in Neon 5.10, although I don't think that fact alone warrants another bug report. Neon is pretty much useless at the moment, and should be pulled from the repos in it's current state IMHO, as attempting to find a package is pretty much impossible, unless someone knows the package name (and in that case one could easily drop to a cli and install it), and is willing to scroll through every package in the archives to find it. 

As mentioned above, waiting for the index to complete and closing > re-opening the app seems to work. But do note that each time a new search is queried, an application restart needs to be completed.
Comment 9 Carlo Vanini 2017-06-23 09:46:50 UTC
*** Bug 372343 has been marked as a duplicate of this bug. ***
Comment 10 popanz 2017-06-23 10:10:48 UTC
That still happens with Verion 5.7
Comment 11 Carlo Vanini 2017-06-23 11:54:24 UTC
Neon (I checked dev-unstable edition) delivers Muon 5.7 although the package version is 4:5.6.0+p16.04+git20170418.1548-0.
But libqapt is still 3.0.2-0ubuntu1.1.

This bug has been fixed in libqapt 3.0.3. Link to relating commit:
https://cgit.kde.org/libqapt.git/commit/?id=6f130ef3db5ae31cd3a739762cdc68d3d299d5d0
For some reason the git version is not available in Neon.
Comment 12 Carlo Vanini 2017-06-26 11:50:08 UTC
*** Bug 378996 has been marked as a duplicate of this bug. ***
Comment 13 Christoph Feck 2017-06-26 13:57:31 UTC
Changing status according to comment #11.
Comment 14 V字龍(Vdragon) 2017-06-26 14:14:40 UTC
Is there any link to track this issue in to so-called-upstream?  I still can't find the fixed package version in the update list.
Comment 15 Christoph Feck 2017-06-26 14:26:31 UTC
The upstream link is also in comment #11.
Comment 16 V字龍(Vdragon) 2017-06-26 14:35:12 UTC
(In reply to Christoph Feck from comment #15)
> The upstream link is also in comment #11.

Whoops I mis-read the Product: line to neon instead of Muon, I'm fine about it then.
Comment 17 V字龍(Vdragon) 2017-06-27 04:35:22 UTC
The fix has landed on "Dev Edition [unstable]
Comment 18 V字龍(Vdragon) 2017-06-27 04:53:31 UTC
The fix has landed on KDE neon "Dev Edition [unstable]" archive, neon users may try it out by adding the archive and APT Pinning libqapt3 package, via creating a new file at `/etc/apt/apt.conf.d/50-neon-use-dev-unstable-libqapt` with the following content:

```
# Only upgrade libqapt package from unstable dev archive
Package: *
Pin: release l=KDE neon - Dev Edition Unstable
Pin-Priority: 99

Package: libqapt3
Pin: release l=KDE neon - Dev Edition Unstable
Pin-Priority: 501

```