This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Firefox throws an error on startup "Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0 Adding client to server's list failed, CORBA error:" orsame error when setting as default browser from preferences

  • 1 reply
  • 11 have this problem
  • 5 views
  • Last reply by hpfeil

spirals
spirals
more options

Only happens on first time firefox starts after cold boot or when setting as default from preferences. Have set Firefox as only option in file associations from within KDE components, Debian Control Center. This problem has existed since I rolled to Firefox 4, still with me after a clean reinstalling 3.6.17 deleted and reinstalled. I fixed that it would not open links from Thunderbird by selecting it in Control Center. All obvious "fixs" tried. help!

Only happens on first time firefox starts after cold boot or when setting as default from preferences. Have set Firefox as only option in file associations from within KDE components, Debian Control Center. This problem has existed since I rolled to Firefox 4, still with me after a clean reinstalling 3.6.17 [/usr/lib/firefox deleted and reinstalled]. I fixed that it would not open links from Thunderbird by selecting it in Control Center. All obvious "fixs" tried. help!

All Replies (1)

hpfeil
hpfeil
more options

When I got that same error starting Firefox 7, I noticed that a script that I ran earlier had changed the owner of all the directories in /tmp to root. Running chown on the usual suspects restored normal operation. I don't know which directory was the culprit, but I suspect /tmp/orbit-$USER and/or /tmp/plugtmp.