| Summary: | Cannot file a new bug in the "kcm" component of the "kdeconnect" product | ||
|---|---|---|---|
| Product: | [Websites] bugs.kde.org | Reporter: | John Veness <john.kde> |
| Component: | general | Assignee: | KDE sysadmins <sysadmin> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | normal | CC: | sheedy |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Screenshot
Screenshot for macos-application KCM? |
||
|
Description
John Veness
2023-10-03 17:30:46 UTC
Created attachment 162060 [details] Screenshot for macos-application Compare to what happens if I try to file a new bug in the "macos-application" component of the "kdeconnect" product (https://bugs.kde.org/enter_bug.cgi?product=kdeconnect&component=macos-application). The 'kcm' component of kdeconnect is closed to new bug entry as it is no longer active. Given you're on a Linux desktop presumably, please put the bug to messaging-application or common. Created attachment 162081 [details] KCM? OK, thanks. Maybe KCM could be removed from the list in https://bugs.kde.org/describecomponents.cgi?product=kdeconnect ? Also, the bug I wanted to report was in the attached screenshot. Is that not a KCM? Yes, that is a KCM - however as it forms part of the overall Linux desktop experience bugs relating to it should go to "messaging" (as not great as that name is). I'm afraid the describecomponents page always shows all components that a product has, regardless of whether they are currently open for bug entry or not. |