How soon is it morally aceptable to abandon bug report, if it does not get attention?

Ask Fedora
, ,
1

Hello. First of all, it is not an attempt in snarkiness, and I really appreciate your hard work.

I encountered persistent and reproducible plasma freezes/crashes in F41 KDE after install, and decided to report a bug. it doesn’t appear to gather any attention (likely, because I did something wrong while reporting it, or just because of high load on engineers), and I’m not sure what to do next. I would like to move on to another distro that may work better for me, because issue is unresolved. But at the same time I will feel really bad if bug will get attention later, and I could have helped to diagnose it, but already moved on.

So, is this considered OK to just close the bug?

2

Why would you close the bug if it’s not resolved and is still an issue?

1 Like
3

Thanks for the answer. Because people who eventually may address the bug will spend time checking logs and considering options may ask for additional information/actions from me. And if I just moved on and will not provide - it would be douche move (IMO).

4

can you link to that bug?

Please give the output of uname -r

This may be a crash with Kernel 6.13 which is happening everywhere

5

https://bugzilla.redhat.com/show_bug.cgi?id=2347548

$ uname -r
6.13.4-200.fc41.x86_64

6

that might be unrelated but you have the cursed kernel version for sure.

  1. report this to kde plasma. Fedora nearly never causes KDE issues that are not upstream. bugs.kde.org
  2. dont expect very fast replies
  3. I think I have seen your issue somewhere, I think people are talking about it, but may not want to reply there?
1 Like
7
  1. Ok, I’ll do it sometime tomorrow.
  2. Good to know.
  3. Ok, so it is better to linger for a while, just in case.

Thanks for the reply!

8

If the issue affects many users, your report will probably be one of many similar reports, in which case attention will focus on reports that provide the best clues. Those are often in an upstream bug reporting system for the component at fault, so the people working on the bug may not see your report unless to point it out using the upstream system. You should:

  1. search for similar bug reports, including other distros and upstream projects
  2. check the LHDB for your model – user comments addressing model-specific issues can be helpful.

This can be a lot of work, but sometimes the effort provides a more complete picture needed to understand the bug.

2 Likes
9

Thank you! I was seemingly too focused on Fedora - I did indeed found such bug reported and worked on in KDE bug tracking tool. In such case I will just close my bug report. This was educational experience for me.

10

You shouid not do that. Instead link the related bug with kde into your report

2 Likes
11

Linux runs on a huge variety of hardware configurations which tends to limit automated testing to a smaller subset. When a bug is reported via Bugzilla, it will eventually get triaged.

However if the bug doesn’t cause a crash, it will be added to a list of items to be addressed when show stopping incidents have been dealt with. During the past few years issues with Wayland and/or NVidia have consumed a lot of resources. Getting everything working with Wayland and NVidia are high priority for many technical reasons.

If a submitted bug has not been cleared before EOL for the OS version that it was reported against, an invitation to verify whether or not it has been fixed in the most recent OS version will be extended.

1 Like
12

Not always. Sometimes they will be automatically closed when the Fedora version for which it was reported reached end of life.