On Thu, 5 Feb 2026 at 22:47, Van Snyder <[email protected]> wrote:
> Is anybody maintaining Okular? The search function is broken. It lands on > the wrong page. The search function works correctly in evince, but Okular > has many features I prefer, such as a "back" button. Hi, I know nothing about Okular, so I did a web search for "okular bug" and found this: https://community.kde.org/Get_Involved/Issue_Reporting Which advises that bugs of Okular can be searched here: https://bugs.kde.org/query.cgi Searching there for closed bugs of Okular shows that the most recent bug was closed on 2026-01-29. So the answer to your question appears to be "yes". You don't mention any details of your efforts to answer this question yourself before asking here, which suggests it's possibile that you might not know how to find the answer for yourself. On that basis, I have explained above my process to answer your question, hopefully that might assist you to find your own answers in future. I'm suggesting this to help you avoid wasted effort. The reason is that the Debian project is not the author of most code packaged by the project, it just distributes it. So while it is perfectly ok to ask for help here, or ask "is anyone else seeing this bug", it is generally true that for application bugs or ideas for improvements it is unlikely that anyone in Debian can solve issues of that nature. Bugs that Debian fixes are typically about matters such as package builds, configuration, coexistence, and interaction. Generally not about source code changes. Yes, you could report bugs that require source code changes to a Debian package maintainer, but then you are asking that person to do the work of reporting it to the upstream project. Because most Debian package maintainers want to avoid/minimise managing patches to upstream code, unless their package cannot function in Debian without the patch. To bring any issue that requires source code changes to the developers attention so that it might be addressed, the most effective way to communicate is to report the issue directly to the upstream project, which can usually be found by a web search, which will also usually reveal if the project is actively maintained, or not.
