Latest Mystery: Firefox Launches LibreOffice.
 

It has been going on for sometime and is finally starting to get on my nerves.
When I go to close Firefox (5 or 6) by clicking on the X in the upper right hand corner of the frame, LibreOffice (3.4) starts up. Ditto, sometimes, but not always, when I click on "Bookmarks."
I've searched both programs for configuration files that might have been changed, but cannot find anything.
Any ideas greatly appreciated.
Thanks.
:hattip:

Try starting Firefox from a terminal, then exiting it and seeing whether it throws anything into the terminal that might help shoot this trouble.

:redface:
Thanks for the reminder. :)
Here is what happens:

Now, when "firefox" is enter into the terminal the program fires up and there are no entries into the terminal.
When I click on the 'x' in the upper right hand corner of the border, the 7 lines appear. There is a pause
at,

Warning: -accept=pipe,name=-1470415805;urp; is deprecated. Use --accept=pipe,name=-1470415805;urp; instead.

and then LibreOffice fires up. When I close it the next 3 lines appear.
Thanks, again.

I had a similar problem a few days ago. Any Icon I clicked on the desktop launched Libreoffice. I was having a WTF moment for sure. I had upgraded FF, TB, and Seamonkey, and -solibs. A reboot solved the problem, but I have no clue what caused it.

Ah, so I'm not going crazy! :) Thanks. :hattip:
I usually shut the machine down at night or when I'm away from it for several hours at a time, but the problem remains when it is restarted.
Thanks, again.

Not sure at all, but just a thought: what if your machine has been compromised somehow, and you were not launchin directly firefox but some kind of "placeholder" script? (That doesn't fit with the re-install solution that seemed to work but it can be a way to look).

What actually is launched when you type firefox ? The firefox binary or some script ?

A command like these:

or
...might help to give some hints.

Just an idea...

Edit: Added the 'which' command too...

Or even simpler command:

And if in doubt, you can also go and look inside the firefox executable and see what it does provided, its a script.

Well yes, sorry, I had only a ssh access to a headless server opened, so I couldn't actually test what is the firefox file. So if it's a script, reading it might gives some clues too.

(Btw, I saw you sent the which command at the same time I edited my message: yes it's complementary but not really a simpler substitute, the two lines have slightly different purposes. Just to say, nothing important tho :) )

Just to confirm that I have had this problem on occasion as well. Never paid much attention to it as I thought it was a bug. Using the latest Firefox and Alien Bob's LibreOffice 3.4.2

Deleting the libreoffice plugin from /usr/lib/mozilla/plugins/ fixed it for me.

Running the two different commands in a terminal returns the following:

Well I can't do a lot about that, but this means it actually launches the "executable" (expected to be a script) in '/usr/lib64/firefox-6.0/firefox'

Maybe you can try to read it if you see something weird in it, if it seems legit.

Btw, speccy talked about a plugin, that could make sense too (as it seems to be a kind of binding between firefox and libreoffice).

Edit: A quick reading of mine, it seems that the script is a kind of "launcher", it searches for the binary for firefox, based on some env, checked some debug flags/arguments, and then simply call the found binary, passing the other args to it...
The broken plugin option might be the right one, unless you see something really bad in your script.

I had this issue with midori for a long time. Whenever I would start midori (regardless of whether I launched it from the terminal or my fluxbox menu) Libreoffice would start up.

I never fixed it. I just stopped using midori because of it

Glad to see it might not have been a pebkac though

Well, somehow all problems exist between keyboard and chair: if it's not the end-user, it might be the admin or the developer himself... :)

I found an openoffice plugin, deleted it, and the problem is solved.
Thanks!
:hattip: