| Summary: | Search fails to find apt package | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | pqwoerituytrueiwoq |
| Component: | discover | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | normal | CC: | aleixpol, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.27.11 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Screenshot | ||
|
Description
pqwoerituytrueiwoq
2024-09-17 17:24:18 UTC
Does discover find it if you search for the common name "ungoogled chromium" rather than the exact package name? If not, then this is a packaging issue in the repo owner for not providing appstream metadata with the package. I'm using Fedora, which does provide appstream metadata for this package. how can i check the 'appstream metadata'? 'ungoogled chromium', 'chromium', and 'ungoogled' do return the package `appstreamcli search [search term]` in a terminal window will do the trick. If those other keywords find it, then it sounds like this is working as expected: search works on the basis of keywords, not package names. Related bug: https://bugs.launchpad.net/launchpad/+bug/1574948 i guess you would call this a side stream bug (go down stream then up in stream in a different direction) |