I don't know where should i post this, but not discussing this at all is not constructive.
I am using Kubuntu and sometimes reporting bugs. But it is really annoying. I understand the reasons why it's happening like this but i do not have a solution.

Two examples

1. Arora - brainstorm.php#idea74928
I got an idea/bug and posted it here at the brainstorm. Then i was told:
>Arora is a Qt application, not a KDE application
I went to Arora bug tracker and posted the bug. But, as i was already told here:
>In addition, those are Kubuntu specific changes, and should be reported to them at Launchpad and not to the Arora developers.

2. KPackageKit - https://bugs.kde.org/show_bug.cgi?id=216440
Found a bug (as i thought in KPackageKit) and posted it to KDE bug tracker. I was told:
>Use aptcc backend or fill a bug report against packagekit python backend (in ubuntu bug report tools).

So you see my problem. To help make KDE (as i thought) better - i meet a lot of barriers. And after that i lose any desire to report bugs.

So barriers are:
1. When i see a bug, i don't know the name of the package in problem
2. I don't know to what distribution should i report the problem - if i should
3. Sometimes it is not a KDE/Ubuntu package, like Arora

And i have 3 choices
1. Do not report bugs
2. Report bugs despite the barriers - but i do not have time for this
3. Wait, get an advice here at KDE forum

Also, when i tried to report a bug at https://bugs.launchpad.net/
i cannot find a simple way to report a bug:

I cannot find the link "Report a bug".

Another example from the same category (even if a haven't received a reply yet):
"Usability, KPackageKit, remove dummy window" https://bugs.kde.org/show_bug.cgi?id=206463

Virtually all bug trackers require that you login to be able to file bugs. You have logged in right?

bcooksley wrote:Virtually all bug trackers require that you login to be able to file bugs. You have logged in right?

Yes i have - you can see this in the top-right corner

You need to be on the project page in launchpad to do that. For example, Arora has the bug tracker here: https://bugs.launchpad.net/arora (notice the "report a bug" link).

Thanks for the help with bug reporting on launchpad.
What are your thoughts on other mentioned issues?

It's always a bit hard to find where to post the bug. Distros have their own hacks w.r.t. what is there upstream. If you start by posting at your distro's bugtracker, Launchpad for example, has a remote bug tracking tool that can keep track of upstream bugs.

So here is a possible way to do it:
1. Find the package that contains the application. For example, if you wish to see the package name for dolphin:

Code: Select all

sayakb@CodeFreak:~$ apt-cache showsrc dolphin
Package: kdebase

2. Report a bug at launchpad for the above package.

3. If it is an upstream bug, you will be notified and you can report it at bugs.kde.org. Then you or the bug triager can add a remote bug watch to the launchpad bug.

If you want to save time, you can find the Kubuntu developers on IRC at #kubuntu-devel (network: freenode) so that you can immediately know where to report it.

And if you are told to report it upstream, be sure to add the upstream bug report number to the launchpad report, as well as the launchpad report number to the upstream report. It does help if both sides can track each other.