Bug Reporting In Linux - How Could It Be Improved?

Reaching out to get your voice on the topic of Bug Reporting in Linux. We may use some of the comments in an upcoming episode. You can leave any comment you like but some potential questions would be:

  • Do you generally find it easy to open bug reports?
  • Who has the best bug report system you’ve used in open source?
  • Do you think there should be more consistency across distros?
  • What keeps you from opening more bug reports?
  • Do you find when you open bug reports the issue gets addressed?

Yes, However I am a technical person across multiple Linux projects. I have developed the skills and insight required to make rather detailed bug reports based on the template that project provides. Your Average user™ is not going to have a github account and bugzilla account for every item they use.

What type are we talking about? User submitted (Github Issues) or automated reports? I like gitlab for the very simple reason of “Its pretty and I use it”

It is already reported or I found a workaround!

Yes and no, Not all bug reports are equal. And not all of them have to be solved in a technical sense.

in Addition, in Git 2.27, The subcommand "bugreport" will be added

1 Like


That I cannot answer because I only submitted bug reports to Debian, Ubuntu and openSUSE and maybe some smaller projects. Every project was using a totally different bug tracker.

I am not sure because every project is different.

Not sure but I did not always get a satisfactory response although from the Debian project it is top notch. You will get a reply in no time even if the bug cannot be resolved in the moment.

Usually yes, specially when it is a Linux distro and as I said maybe I have to admit that I have more experience with Debian and even though people seemed to complain about their old school approach I think for me it worked the best. When I used Debian Unstable I was submitting bugs and on every issue I had a response.

  1. Somewhat. I am technical enough to be able to find them, or at least know where and how to look.

  2. Right now I think GitHub has the best features and is popular with devs. But right before I could get familiar with GitHub, Microsft bought them out and now I dont feel like using them. They say they dont do datamining on them but I like to press X to doubt.

  3. Oh heck yes! But devs, like standards, dont want to be truly consolidated under a single idea. The general idea of open source is to fork, to deviate away, from original ideas. Sure we take merges, but it makes people separate further if they dont like the idea of the newly merged code. So over time, we actually increase the drive of inconsistency.

  4. I wont make a bug report if you want me to register to anything: Github, Gitlab, Launchpad, Bugzilla, etc. Yes it makes sense to register. What I want is a field that pops up when your app crashes or a send feedback function that requires no account creation. Yes I also file bug reports via support email because I am a monster. But I also dont do mailing list because you nerds really intimidate me, a non-coder/non-dev.

  5. Oh yes, especially with smaller projects. I find that the main dev himself would message me and it would flatter me a bit. But it doesnt mean the issue gets resolved. I just want senpai to notice me, in some way.

I’m not disparaging this. This is, IMHO, one of the big blockers for the “average user.” If there was a way to implement anonymous (or unregistered) bug reports, even if they defaulted to a lower priority, that’d be great.


As a nerd on a non nerd mailing list. it isnt so bad™

1 Like