KDE bugtracker is confusing. Is it just me?

Today I reported my first bug to the KDE bugtracker after I noticed dolphin was crashing when the space key is pressed. So I went to the bugtracker, got on the search page and litetally chose the category for dolphin and searched for “space” . No recent bugs were shown, so I continued to write the report. However, I promtly found out that there are 6 (six!!) duplicate bugs and that this issue surfaced a month ago when I got notified about my bug being another duplicate.
So, the issue is: is the search feature on KDE bugtracker a bit lacking? Did all those people who reported the duplicates try to search and too found nothing? Did they not check first? Or is it that we all somehow don’t know how to use the search properly?
Wondering if someone had a similar experience.

1 Like

KDE uses the bugzilla bug tracker. Its a bit tricky to use. I don’t know how you searched, but there is a good chance you only looked at currently open bug reports.
For example the default search bar only shows open bugs. Your bug was already fixed in the development version and therefore it didn’t show up.

There are good reasons why KDE uses this bug tracker instead of gitlab:
https://community.kde.org/Get_Involved/Issue_Reporting/Why_not_GitLab_Issues

1 Like

thanks for helping.

https://bugs.kde.org/page.cgi?id=quicksearch.html

has good tips for how to formulate a search… yes, it’s a lot.

\

2 Likes