20365 - Full Circle on Linux does not, in fact, work

Status: VERIFIED WORKSFORME

(SeaMonkey :: General, defect, P3)

Description

[elladan]

Ok.  I start up Mozilla M11, go to www.slashdot.org, and it crashes 5 seconds
later.  Cool!  Yes!  And then I get this nice bug feedback program.  Cool.

So, I enter the bug.  And it can't send it.  It says, "Connecting...
Retrieving... etc." and then says it can't connect.

Ooops!  This is mostly a problem because many people would assume the bug
reporting tool can actually report bugs, and thus might mistakenly enter
bugs into it, going to great lengths to enter them properly.

That would be bad.

Comment 1

[Chris McAfee]

no core-file problem?  leaf.

Comment 2

[Daniel (Leaf) Nunes]

It's possible that fullcircle doesn't grok proxies, or something. I have been
consistently able to crash and send reports with fullcircle enabled builds, from
inside the nscp firewall.

It's *also* possible that the server was down for a while... can you try again?

Comment 3

[elladan]

Ok.  Tried again with M12.  Still doesn't work.

Steps used to send:
1. Enter bug report
2. Go to Full Circle window, click "Send unsent incidents"

Status of incident changes through:
Connecting
Sending
Receiving [waits a while]

Error message shows up: Connect Failed

The message goes back to Queued


There was no proxy etc. configured.  I tried setting one, same result.

Comment 4

[Daniel (Leaf) Nunes]

I know for certain that data is working from some linux clients (the very same
bits you're failing with!). The only thing i can imagine is that you are behind
a firewall that is not allowing the data through. I'm not sure how the data is
transfered... reassigning to the talkback expert.

Comment 5

[Shiva Thirumazhusai]

Hope this may may help you.

Using the Quality Feedback Agent with Automatic Proxy Configuration

If you are using automatic proxy configuration, and you want to use the Full
Circle Talkback Quality Feedback Agent to send incident
reports to Netscape, you need to replace the talkback.ini file with one that
contains the appropriate proxy configuration information:

     1.  If you are using an HTTP proxy, or both an HTTP and SOCKS proxy, create
a file named talkback.ini, containing
     these three lines, using your proxy host name, domain, and port:

          UseUserHTTPProxyInfo=1
          UserHTTPProxyHost="yourproxy.yourdomain.com" UserHTTPProxyPort=xxxx

        If you are using a SOCKS Proxy, create a file with these three lines:

          UseUserSOCKSInfo=1
          UserSOCKSHost="yourproxy.yourdomain.com"
          UserSOCKSPort=xxxx

     2. Replace the existing talkback.ini file with the version you created.


     On Unix systems, copy the talkback.ini file in to this location:
     $HOME/.fullcircle/NetscapeCommunicator5.0LinuxIntel2000xxxxxx/Talkback.ini

     ("2000xxxxxx" refers to a directory name that can vary. To find out the
name of this directory for the version of Communicator that you
     are using, choose About Communicator from the Help menu. The actual name of
the 2000xxx directory appears in the title at the
     top of the window.)

Comment 6

[elladan]

On further testing, the utility was able to send bugs successfully.

This was apparently a failure on the server end, possibly due to excess
load right after a Mozilla release.  The client appears to work.

Comment 7

[leger]

Marking Verified as WorksForMe per above comments.  Please use latest nightly 
build from: http://www.mozilla.org/binaries.html and reopen bug if is happens 
again.  Thanks!