[gutsy tribe-2] firefox doesn't create profile if not present

Bug #124262 reported by Gavin McCullagh
This bug report is a duplicate of:  Bug #123917: Can't start Firefox. Edit Remove
4
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Invalid
Undecided
Mozilla Bugs

Bug Description

Installed gutsy tribe-2 from

 - alternative cd cli install
 - apt-get install ubuntu-desktop

Immediately when I started firefox the profile dialog popped up with no profiles. i tried to create one and got a strange error message (will try to reproduce and get that.

firefox version2.0.0.4+2-0ubuntu3

Revision history for this message
Gavin McCullagh (gmccullagh) wrote :

I get this error:

***MEMORY-WARNING***: firefox-bin[17906]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon...

though that also happens when I have an existing working profile and firefox works as normal. See screenshot for what happens when there isn't a profile.

I've checked permissions etc. It manages to create .mozilla/firefox/xxxxxxDefault\ Userz so I'm not clear what the problem is.

Revision history for this message
Califax (pascal.ziener) wrote :

I got the same error and i figured out that Firefox created a FILE with the usual random name instead a FOLDER. I think Firefox has a problem with that.

As a temporary fix helps:

1. create a folder "default" in "./mozilla/firefox"
2. and put:

    [Profile0]
    Name=default
    IsRelative=1
    Path=default

   in .mozilla/firefox/profiles.ini

Revision history for this message
Califax (pascal.ziener) wrote :

Supplement:

I forgot to say that i meant the profile folder, where Firefox creates a file for. This happend after a new installation of Kubuntu Tribe2 and a following apt-get dist-upgrade. Then i installed Firefox. So i had no profile before.

Sorry for my bad English!

Changed in firefox:
assignee: nobody → mozilla-bugs
Revision history for this message
John Vivirito (gnomefreak) wrote :

***MEMORY-WARNING***: firefox-bin[17906]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon...

is not an error its a warning, this warning has nothing to do with profile issue. Rejecting bug because as it is known all over the place, We(ubuntu-mozillateam) will be working on something for that warning, anyway all apps that use glibc will have this warning.
please open a bug on the profile issue if there is an issue outside of the warning you are getting and please use the Help>Report a bug entry from firefox help menu to report firefox bugs from now on as it will give us alot of info we need to proceed with bugs.

Changed in firefox:
status: New → Invalid
Revision history for this message
Gavin McCullagh (gmccullagh) wrote :

The reported bug *is* the profile issue. That's why the title of the bug reads "[gutsy tribe-2] firefox doesn't create profile if not present" and the first post talks only about that.

I added the comment with the warning just in case it was relevant.

Seeing as you've decided to invalidate this (due to extra info being given?), I guess I'll see if I can report it upstream and pray that it is really an upstream bug and not an ubuntu one.

Revision history for this message
John Vivirito (gnomefreak) wrote :

gavinmc,
please open a bug on the profile issue if there is an issue outside of the warning you are getting and please use the Help>Report a bug entry from firefox help menu to report firefox bugs from now on as it will give us alot of info we need to proceed with bugs. when you file a bug in the way i gave you it sends info like extentions and other important info we need to diagnose this issue. This sounds more like an upgrade issue upgrading from feisty to gutsy.

Revision history for this message
Gavin McCullagh (gmccullagh) wrote :

I have reported again using firefox's bug reporting. see bug 125648

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.