Is there a bug tracker for PCLOS?

[greywalk]

Hi,

where should a user report bugs he/she's found? does pclos have a bug tracker or is there any other way to report a bug?

[kjpetrie]

If it's a problem with a program not working as expected, ask for help in the Software section. If people conclude it is a bug, they will either suggest reporting it upstream to the author of the software or look for a patch and try to rebuild the application.

If it's a program that will not install, or complains about a missing function when you try to run it (in other words, a packaging mistake) report it in broken packages.

If you're not sure of the difference start in the software section and see what people suggest.

[sammy2fish]

Hi,

where should a user report bugs he/she's found? does pclos have a bug tracker or is there any other way to report a bug?

Well, we should damn well have one!  There are so many trackers out there.  We should be in the mix..!

[Archie]

Hi,

where should a user report bugs he/she's found? does pclos have a bug tracker or is there any other way to report a bug?

Well, we should damn well have one!  There are so many trackers out there.  We should be in the mix..!

+1

However, our resources are limited and another task to monitor an offsite bug tracker is already stretching what we cannot already afford.

I know there's a big difference between an "official" bug tracker but I kinda like the personal touch of getting an app to work when a developer and a user start working together rather than leaving everything to the developer.

[llewellyn]

Thanks to you all I solved Kmail kadressbook crash here on this forum
I did send in  crash reports and backtraces  to the kDE Bug System and got some acknowledgements of receipt but not much else. I do wonder however just how you all manage to develope things while being showered with stupid questions by stupid people like me. ITS A HUGE TASK Thank you so very much PCLOS has all sorts of little bugs but it is just the very best user experience I have had in years using Linux.

[Archie]

Thanks to you all I solved Kmail kadressbook crash here on this forum
I did send in  crash reports and backtraces  to the kDE Bug System and got some acknowledgements of receipt but not much else. I do wonder however just how you all manage to develope things while being showered with stupid questions by stupid people like me. ITS A HUGE TASK Thank you so very much PCLOS has all sorts of little bugs but it is just the very best user experience I have had in years using Linux.

Heya llewellyn,

First of all, there's no stupid questions if asked in all sincerity and with the desire to help one's self. Then there is this very thick line between this genuine trait and having an attitude. We want to help and the only way we can do this is if those seeking help will clear their minds and do exactly as requested. But this is not always the case and personally, there are times when I am just about to snap because of frustration. But I could just brush it off and laugh about it.

There are users who would blame the OS, the devs but never themselves, and we quite understand that it's never the machine, definitely not the devs nor the community members extending their assistance. We should look at the mirror once in a while and truthfully answer ourselves, do we like the person we see?

Oh, there are mornings when I can tell you I'd rather stay in bed... but I think about Neal, and the mugs of coffee that awaits me ... so I'm good. Yeah, yeah ... I know ... babbling.

Peace and much respect,
Archie

[menotu]

We have the best  bug tracker already named Neal  

Seriously though, a lot of bugs can and should be filed with the developers who create/maintain the software, with a note of the problem also posted on the PCLinuxOS forum along with any Bug Report number/links etc....

[Neal ManBear]

Our bug tracker is the forum. It is much more personal than other bug trackers. How? You get responses, usually within minutes. If it is a bug that we are responsible for, we start looking for a fix right away. If it is a bug in the software itself, we check to see if there is a fix from upstream or look for a way to patch it.     

Remember, the Bacon Brigade is a small team. We fix things as quickly as we can, but sometimes it may take a while. We depend on getting accurate information, so please, when you are asked by someone for more information, give it. We have skilled supporters here who know how to seek out the heart of a problem and are good at coming up with the right questions to ask. We look for what they discover to be available. It is a help to us.     

For software bugs, you can always post a report to their bug tracker. Then whoever is responsible for tracking down bugs and finding/creating a fix has your report to help him/her.