First, make sure it's a bug. If Subversion does not behave the way you expect, look in the documentation and mailing list archives for evidence that it should behave the way you expect. Of course, if it's a common-sense thing, like Subversion just destroyed your data and caused smoke to pour out of your monitor, then you can trust your judgement. But if you're not sure, go ahead and ask on the users mailing list first, users@subversion.apache.org, or ask in IRC, irc.freenode.net, channel #svn.

You should also search in the bug tracker to see if anyone has already reported this bug.

Once you've established that it's a bug, and that we don't know about it already, the most important thing you can do is come up with a simple description and reproduction recipe. For example, if the bug, as you initially found it, involves five files over ten commits, try to make it happen with just one file and one commit. The simpler the reproduction recipe, the more likely a developer is to successfully reproduce the bug and fix it.

Though as a member of mywindowshosting.com I do have such kind of information needed.So If you like my information please do inform me about.Thanks

When trying to report bugs at inscape.org, users are redirected to launchpad. I have a launchpad account which I have used in the past for this but I get a "page is stale" redirect advising me to check for browser add ons - of which there is only 1- a google tracker block. And I don't want to give any data to google. At all.

So basically a stalemate - suggestions for alternative where I can post the bug report that respects my privacy wishes?

I have similar desire not to give google any info about me. I'm sure it's absolutely wasted energy, but I boycott google as much as possible. Makes me crazy just to have to allow youtube videos on my forum. But my desire to serve and support Inkscape users wins out over my desire to boycott google.

But I am able to post on LP. Can you share exactly which browser add-on it's requesting? I certainly don't have any google addons. Not that I know of. I don't know what "google tracker block" is.

Or is it asking to remove some certain addon? (Off to search for a google blocker addon, haha.....)

EditOh, you mean cross-site requests? Just my brief searching, it looks like it's nearly impossible to be protected against all XSS. It sounds like the technology is changing faster than addon writers can create ways to block them.

But you know, there's always using a proxy. Or they have these VPN (virtual private networks) these days. Of course, you can't join any forum which is running decent security, because the VPN ip addresses are ID'd as spammers. Aaarrrrghhgg!!! This all just makes me crazy! Makes me want to buy an acre in some wilderness area, and become a hermit!

But getting back on the subject. If you could share all the relevant info (all of it) I'd be glad to post the report for you. Well, as long as I can at least generally understand it. If it's a very technical bug which I can't understand, I would not be able to answer developers questions, or test possible fixes, or anything like that.

I'm not familiar with Ghostery, I've never used it. I notice in your screenshot there seems to be an indication that there's an update available. If it were me, I guess I'd at least try getting that update.

I can't speak for Launchpad. It's one of the few sites which I regularly use, which does not require me to log in again, every couple of weeks. It's probably been a couple of years since I've logged in. And after that, I just stay logged in. (I wish more sites would do that!)

Well anyway, the error message doesn't mention anything about google. I would go by what the error message says, to fix the problem. If Ghostery blocks or hides the referrer header, that's probably the reason you can't log in, rather than google. (Or else it's the cookie issue, as the error message indicates.)

Actually I'm surprised LP is using a tracking cookie. Not that I'm any kind of expert, but LP doesn't seem like the kind of site that would track people. But if you have to accept the cookie for a moment, in order to log in, you can always delete the cookie immediately after you're logged in. The only thing they would find out (assuming you gave the cookie enough time to "phone home") is that you were on LP. (And being logged in, LP already knows you're there.) If you have to accept the google tag manager script to be able to log in, you can allow it, and immediately disallow it, after you're logged in. I do that all the time, using NoScript.

As much as I despise some of the products which google has created, the truth is, you'd have to devote a lot of time completely avoiding google products these days. Their products are everywhere!

Anyway, sorry I can't be more help. In my experience, sometimes you just have to give in. I've gone from trying not to give anyone any info, to trying to minimize it as much as possible. You'd have to (1) be an expert, and (2) devote a lot of time to it, to prevent from being tracked at all. And that would probably include not being able to use some websites at all.

It happened the last time I visited and there was no update for Ghostery, and I've just checked now before replying there is no update pending. Generally with Ghostery updates relate to to the tracker database rather than functional updates.

To help you interpret what you're looking at next to "Essential" it says "1 tracker 1 Blocked" - underneath it names the tracker with the font in strikethrough.

What is happening is, as this is not the first time I have logged in to Launchpad, something is trying to force me to update the cookie stored on my machine and the instigator is a Google originating tracker.