Hello dear team, I am a plasma user using Arch Linux, I reported a bug on november 2024 but I din’t get attention or some answer. Today I am opening a new bug founded so, my question is:
How I can get attention from developers?
Hi! Looking at the previous bug you submitted, my main recommendation would be to carefully review and follow the guidelines on the Community Blog here: Get Involved/Issue Reporting - KDE Community Wiki
Specifically, following the default template - with very clearly detailed Steps to Reproduce - is critical for bug triagers to be able to either confirm that a bug can be reproduced on their own systems, or to ask clarifying questions.
I see that in your second bug, you kept the template sections in place - that’s good progress 
However, to be most effective, the steps to reproduce a bug should be more specific. Effectively written steps should specify exactly what needs to be clicked on, typed in, and observed/measured, so folks can make sure that as close to the same situation as possible is being reproduced on their own devices.
Hope that helps!
2 Likes
Hello and thank you for your answer, I agree with the information about my first bug report, but, 2 months without answer?
I believe kde team should send a message closing the thread or something for We know if this is checking or no.
Thank’s for the help.
The majority of bug triagers, like the majority of the KDE community overall, are volunteers jumping in to help contribute as they are able.
A meaningful response to a bug report requires that the report itself is structured as needed, but also that the situation described in the report is reproducible by a triager. In the case of the bug you’re asking about, it sounds like an issue with how a KDE component interacts with a very specific version of a third-party program, in a specific situation involving Windows - I’m not surprised that not many KDE volunteers are in a position to provide a helpful response there.
If you’re in a niche situation, want something to work better or differently, and don’t want to wait for someone to come along with the time, ability, and interest to help…then the reality of upside of free and open-source software is that you might need to be the one to make it happen.
The upside of free and open-source software is that the doors to making it happen are open If getting directly involved in the code is an interest area of yours, Get Involved/development - KDE Community Wiki is a great place to start - I’m mostly a regular user, but I’ve had a couple of merge requests accepted for little things that I ran into and was able to figure out.
If what you’re going for has a commercial application, then perhaps an entity who would benefit from that functionality working would be willing to sponsor its investigation / development?
Just some thoughts there - hope that is helpful.
2 Likes
Ohhh, OK, I understand.
I was thinking that it worked similar to other working groups, such as, in the case of Arch Linux, each package has a person responsible and when you report something, that person responds via Github if your report is valid, invalid or requires more information to determine.
From what you explain to me, I understand that in the case of KDE there is a group of volunteers who, depending on their availability, may or may not see the problem you report. That explains why my report has been without interaction for more than 2 months. Ha ha ha.
Unfortunately I am not a user capable of analyzing the component code and debugging the error, so in my case I will have to accept the failure only or look at desktop environment alternatives.
Thanks for the help.