(firefox:1787): GLib-WARNING **: g_set_prgname() called multiple times

[SirGe]

I had the same problem. The messages ((firefox-bin:22382): GLib-WARNING **: g_set_prgname() called multiple times) appear to be an unrelated symptom. Prism seems to be the issue.

Part of the apparent reason for many different proposed solutions is that once I successfully start firefox in safe mode (i.e. with -safe-mode), it restarts fine without any additional options. Once. If I stop it and try to start it again, it fails without any additional messages.

None of the above proposed cures fixed the problem in my case.

By a tedious process of alimination, I identified the trigger as prism: if I disable it, I have no problems, if I re-enable it, I bring the problem back. This extension is not particularly useful: it enables you to create prism launchers from Firefox, but you can do the same by editing XML files...

My versions: FF 3.6.2pre, prism 1.0b3 (from http://ppa.launchpad.net/ubuntu-mozi...y/ppa/ubuntu): I _really_ wanted tear-off tabs

This helped me realize just how much I depend in firefox working properly on my desktop - loads of thanks to all the Mozilla developers!

HTH

[harpoonz]

Thanks for doing the legwork SirGe! I was getting the same message until I disabled Prism.

[sambatyon.abulafia]

OK guys, I took the time to disable all the add ons and enable them one by one until the bug show itself. At the end, the add on which was causing all the problems was greasemonkey.

[ben2talk]

I have to click the firefox icon in my panel twice, first time gets shut down again for some reason. Same error as you guys in terminal.



Hmz... this post says it gets fixed by removing the .mozilla folder from your homefolder. I'll give it a try.

http://support.mozilla.com/tiki-view...6197&forumId=1

I think this is a problem in the file 'compatability.ini'. I have multiple profiles, so I opened /home/ben/.mozilla and clicked the magnifying glass, entered 'compatibility.ini' and deleted them all.

Firefox started perfectly - but only one time.

So, I edited 'compatability.ini' to read as follows:

[Compatibility]
LastVersion=3.6_20100124075447/20100124075447
LastOSABI=Linux_x86-gcc3
LastPlatformDir=/usr/lib/firefox
LastAppDir=/usr/lib/firefox

Then I saved it, and made it READ ONLY - then copied and pasted it into each of the profile folders.

Now I can launch Firefox normally, and this file isn't rewritten in a way that stops it launching

[shellehs]

@ben2talk thanks, it works 4 me~~

[pho3nixf1re]

i was having the same issue. in the compatibility.ini file i changed

[Compatibility]
LastVersion=3.6_20100218182626/20100218182626
LastOSABI=Linux_x86_64-gcc3
LastPlatformDir=/usr/lib/firefox-3.6
LastAppDir=/usr/lib/firefox-3.6

to

[Compatibility]
LastVersion=3.6_20100218182626/20100218182626
LastOSABI=Linux_x86_64-gcc3
LastPlatformDir=/usr/lib/firefox
LastAppDir=/usr/lib/firefox

notice the difference in the platform and app dir settings.

be sure to change the file to read only, otherwise firefox will overwrite the fix.

[pho3nixf1re]

WARNING! changing the directories like i did removed all my extensions. will post back if i can figure out what happened. at least firefox works. good thing firefox isn't my main browser anymore

[Arkitekt]

OK guys, I took the time to disable all the add ons and enable them one by one until the bug show itself. At the end, the add on which was causing all the problems was greasemonkey.

I also discovered this, but the reason it is causing a problem with 3.6 is because greasemonkey seems to not auto-update when a new version comes out, most of us have pre-3.6 versions. I myself had a version from January of 2009. Looks like in 0.8.3 greasemonkey added a 3.6 compatibility flag. Updating manually from the add-ons website to 0.8.20100211.5 fixed this issue for me.

I fixed my GLib warnings by downgrading libglib2.0-0 and libglib2.0-data to 2.22.1-0ubuntu1, the newest one from karmic-updates (2.22.3-0ubuntu1) seems to be unstable. For those wondering how to do this, in synaptic highlight the package and under the package menu on the toolbar select force version (CTRL-E).

Hope this solves this for everyone.

[Deathspawn]

I had the same problem. The messages ((firefox-bin:22382): GLib-WARNING **: g_set_prgname() called multiple times) appear to be an unrelated symptom. Prism seems to be the issue.

Part of the apparent reason for many different proposed solutions is that once I successfully start firefox in safe mode (i.e. with -safe-mode), it restarts fine without any additional options. Once. If I stop it and try to start it again, it fails without any additional messages.

None of the above proposed cures fixed the problem in my case.

By a tedious process of alimination, I identified the trigger as prism: if I disable it, I have no problems, if I re-enable it, I bring the problem back. This extension is not particularly useful: it enables you to create prism launchers from Firefox, but you can do the same by editing XML files...

My versions: FF 3.6.2pre, prism 1.0b3 (from http://ppa.launchpad.net/ubuntu-mozi...y/ppa/ubuntu): I _really_ wanted tear-off tabs

This helped me realize just how much I depend in firefox working properly on my desktop - loads of thanks to all the Mozilla developers!

HTH

Yep. Seems correct. Just installed prism and shortly after, it failed to start. Did the firefox -safe-mode and shut off all add-ons and it popped up fine. Though, I do notice when starting it in Terminal, it still throws up these errors:

spawn@quernerium:~$ firefox

(firefox-bin:27247): Gtk-WARNING **: Unable to locate theme engine in module_path: "ubuntulooks",

(firefox-bin:27247): GLib-WARNING **: g_set_prgname() called multiple times

But it starts.

[LouPirlu]

same problem, firefox 3.6 doesn't start (I see "Starting Firefox Web Browser" on the taskbar for a while, then disappears and nothing happens). Launching from the terminal I get the GLib warning.

launching in safe mode and disabling GreaseMonkey solved the Firefox-doesn't-open problem (but I still got the GLib warning), and downgrading the package libglib to 2.22.2 solved the warning (but again ffx didn't start). They seem to be two different issues.