Sonar X2 is Problem Reporting temporarily not working?

As far as I'm aware the minidump is part of the report that is automatically sent to Cakewalk. I just clicked OK on mine to send it and I got an e-mail confirming that it had been sent and received with a reference number.

Still not getting confirmation email that Reported Problem has been received and cannot go into report number. When I put in my new report number I get a report I submittted in May 2012.

Is Problem Reporting temporarily not working?.

Ryan my music of is not on Internet. So when it crashed I took the mini dump file and tried to send along with report I found. Othing that allowed me to attach a file. This was using the problem reporter. 

(Side note: I pulled out your hyperlink as it contained your personal email)

I understand what you're referring to now. When that email was sent (the one you're pasting above), it was prior to your report being updated. At the time, it was a "New" report so any details could be added.

Your report was eventually updated to "Under Investigation" and then "Submitted to Development". These are human actions. Someone looked at the details of your report and determined that they had enough information to pass it along officially. I can see the entire history of it on my end. 

In truth, it was actually me on this report. I ran your .dmp file through our debugging symbols and added the crash info to the internal report with your details of what happened. This is essentially the same exact thing the Fault Reporter does, it just does it very quickly and doesn't require much human interaction (if any at all).

Your report currently set to "Status Changed" because it looks like it moved around internally a bit with some additional info. Messaging is closed for the report unless the devs or QA need more information. If that were to be the case, when they changed the report to "More Info Needed" it would open up some fields for you to add messages and files.

The point of the Problem Report system ultimately is for a user to report a problem and then for us to decipher what the problem is. Once we've determined whether or not its a bug or a SONAR related crash, we push it to our system internally and the report turns to a read-only report. When it gets resolved, the final stage emails the user so they are aware of the resolution. 

Allowing more information to continually be added only confuses things after that point. This particular form isn't meant to be a back and forth correspondence between the end user and our development team indefinitely. If we're closing out the report, it's not because we're trying to be rude, it's really us just trying to be more efficient.

It also allows us to not receive profane emails when customers disagree because they don't understand that things like "Closed - Feature Request" only means we pushed the information to a different team of Cakewalk employees (and yes... this happens a lot ;). 

I guess what I'm trying to get at is that it looks like your report was processed completely normally as intended by the system. You guys are all extremely helpful reporting this information to us, but you shouldn't have to worry yourselves about the day-to-day status changes with what we do internally. What I would worry about is:

1) Was the report clear? Check, yes it was.
2) Did Cakewalk acknowledge it? Check, yes they did.
3) Is it fixed yet? I'm not sure. I tried following your recipe but I'm unable to replicate it. Are you still running into this crash?

What's happening is there's a long-standing bug in the web page. Instead of taking the web page's input fields, it takes a cookie created by a previous report submission. Maybe find & delete the cookie or use a different browser, a different login, or a different computer.

bvideo

What's happening is there's a long-standing bug in the web page. Instead of taking the web page's input fields, it takes a cookie created by a previous report submission. Maybe find & delete the cookie or use a different browser, a different login, or a different computer.

Actually, that had always irritated me as well so we stopped creating cookies on new problem reports a while ago (apparently May 29th). What I failed to do, however, was to stop requesting cookies. Those are some old cookies, I wouldn't eat them.


Thanks for pointing it out. Should be fixed now.

Ryan, that was fast!