firefox 1.4.99 upgrade still have compreg.dat, creates issue
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
firefox (Ubuntu) |
Fix Released
|
Wishlist
|
Mozilla Bugs |
Bug Description
As of the latest "Dapper" install, Epiphany does not run. It has been working
before but recent changes stopped it. This is running with Epiphany v
0.5.1-1build2 and Firefox v 1.4.99+
"""Epiphany can't be used now. Mozilla initialization failed."""
Firefox itself runs fine, so I'm guessing it's an API mismatch or something. No
extra information is given running from the command line, just the same dialog
message.
PeterShinners (pete-shinners) wrote : | #1 |
Jeroen (jeroenubuntu) wrote : | #2 |
I can confirm on my own pc, which had epiphany installed before Firefox upgrade,
but not on my sister's pc where I installed epiphany _after_ upgrading Firefox..
Sebastien Bacher (seb128) wrote : | #3 |
Please update your epiphany-browser package:
epiphany-browser (1.9.2-0ubuntu2) dapper; urgency=low
* debian/control.in:
- build with the current firefox package (Ubuntu: #19950).
-- Sebastien Bacher <email address hidden> Thu, 24 Nov 2005 01:16:20 +0100
Jeroen (jeroenubuntu) wrote : | #4 |
jeroen@gnubuntu:~$ apt-cache show epiphany-browser | grep Version
Version: 1.9.2-0ubuntu2
jeroen@gnubuntu:~$ LANG=en_EN.UTF-8 sudo apt-get update
Get:1 http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Fetched 1B in 0s (4B/s)
Reading package lists... Done
jeroen@gnubuntu:~$ LANG=en_EN.UTF-8 sudo apt-get install epiphany-browser
Reading package lists... Done
Building dependency tree... Done
epiphany-browser is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
jeroen@gnubuntu:~$
I still get the same error.
PeterShinners (pete-shinners) wrote : | #5 |
It appears I had two "epiphany-browser" versions in my apt-cache. I cleaned up
my sources.list and rechecked. I do have "Version: 1.9.2-0ubuntu2" and am seeing
the same error.
Sebastien Bacher (seb128) wrote : | #6 |
Christian, do you have an idea on this? :)
c7d2f5c8667d26fffd5e7772d632c76d (c7d2f5c8667d26fffd5e7772d632c76d-deactivatedaccount) wrote : | #7 |
When you start epiphany from a shell, are there any messages output on console?
Jeroen (jeroenubuntu) wrote : | #8 |
When I start epiphany in console, I first get the dialog asking me if I want to
restore previous windows and tabs. (Which makes sense, since epiphany crashed
last time aswell.)
Then, I get an error box. Title: Error
Body: Epiphany can't be used now. Mozilla initialization failed.
Backtrace was generated from '/usr/bin/epiphany'
(no debugging symbols found)
Using host libthread_db library "/lib/tls/
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227703936 (LWP 9518)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb6f6e0ad in poll () from /lib/tls/
#2 0xb710ca68 in g_main_
#3 0xb710cf38 in g_main_loop_run () from /usr/lib/
#4 0xb771ef93 in gtk_dialog_run () from /usr/lib/
#5 0x080b71ce in impl_permission
#6 0xb71922a3 in g_type_
#7 0xb71779e6 in g_object_
PeterShinners (pete-shinners) wrote : | #9 |
I get no information on the console. I noticed if I run with --bookmarks-editor
I see the bookmark dialog and the same "failed to initialize" dialog. I can
interact with the bookmarks, but pressing "Ok" on the error dialog quits the
process.
Jeroen (jeroenubuntu) wrote : | #10 |
(In reply to comment #9)
I cannot confirm this. epiphany -b just gives the "Epiphany can't be used now.
Mozilla initialization failed." dialog.
Then again, I think I might've deleted my bookmarks in an attempt to get
epiphany working again...
asubedi (asubedi) wrote : | #11 |
I can confirm that bookmark editor comes up when i do epiphany -b, but if I try
to open any bookmark, it fails. I built and installed epiphany from source deb
against the current version of firefox and it gave the same error.
PeterShinners (pete-shinners) wrote : | #12 |
Upgraded to today's new Firefox: 1.4.99+
Current Epiphany version: 1.9.2-0ubuntu2
Still getting the same Epiphany error about initialization failed.
Sebastien Bacher (seb128) wrote : | #13 |
what architecture do you use?
PeterShinners (pete-shinners) wrote : | #14 |
Architecture is x86. Specifically "2.6.15-5-686"
Jeroen (jeroenubuntu) wrote : | #15 |
i386. Can't help with this anymore, until I start running dapper again.
Daniel Holbach (dholbach) wrote : | #16 |
Jeroen, what does that mean? You switched back to breezy? Could anybody else who
gets this error message, check, if there are any held back packages (apt-get
dist-upgrade should show)? Pete, you said you had two versions of
epiphany-browser - could you attach your sources.list?
Jeroen (jeroenubuntu) wrote : | #17 |
I switched back to breezy, Daniel.
PeterShinners (pete-shinners) wrote : | #18 |
- Petes apt sources.list Edit (249 bytes, text/plain)
Created an attachment (id=5192)
Petes apt sources.list
asubedi (asubedi) wrote : | #19 |
(In reply to comment #16)
> Jeroen, what does that mean? You switched back to breezy? Could anybody else who
> gets this error message, check, if there are any held back packages (apt-get
> dist-upgrade should show)? Pete, you said you had two versions of
> epiphany-browser - could you attach your sources.list?
There are not any held back packages. I also built and installed epiphany from
source deb and from source tarball, but it gives the same error.
PeterShinners (pete-shinners) wrote : | #20 |
I've tried to gather more information about the problem. I could not find a way
to make it work, but here is what I've tried.
First I tried moving my ~/.gnome2/epiphany and ~/.gconf2/epiphany folders.
I also tried creating a new user accound from the 'desktop' config.
I looked at information from ldd and strace, but it feels like a large haystack.
Sorry I can't find any solid information. I may try downloading a nightly live
cd and testing that.
James "Doc" Livingston (jrl) wrote : | #21 |
Sebastien Bacher (seb128) wrote : | #22 |
We discussed that on IRC with Christian and James. The issue is created by
/usr/lib/
1.0.7 packages but not the 1.4.99, it should be removed on upgrade but it's not
for some people. Moving the file away fixed the issue for James. Could other
people having this crasher try that?
Sebastien Bacher (seb128) wrote : | #23 |
*** Bug 26533 has been marked as a duplicate of this bug. ***
Sebastien Bacher (seb128) wrote : | #24 |
*** Bug 26711 has been marked as a duplicate of this bug. ***
Ian Jackson (ijackson) wrote : | #25 |
As I said on IRC, here is my theory:
> This file is a registry of components including extensions.
> If you have pre-1.4.99 extensions installed then this compreg.dat file is
updated by those extensions somehow, normally.
> But the 1.0.7 package makes it a symlink to /var so the file ends up in /var.
> Now the 1.5 package removes the symlink. Then if anything were to try to
create the file in /usr it would just go ahead and do so.
...
> The problem is obviously that something is creating it again later.
> And it has to be something than runs as root.
> So my best guess at the culprit is some extension or embedder's maintainer
scripts, probably indirectly.
> How about this for a plan: since we have a workaround (delete the file) I will
postpone dealing with this until my next round of firefox maintenance (ie
probably at least a week). In the meantime if any information surfaces about
what creates the file we can add it to the bug report.
> I'll change the bug priority to P1 to make sure I pick it up later.
PeterShinners (pete-shinners) wrote : | #26 |
As a user, renaming "/usr/lib/
this for me.
I'm posting this with Epihany!
Sebastien Bacher (seb128) wrote : | #27 |
*** Bug 26861 has been marked as a duplicate of this bug. ***
asubedi (asubedi) wrote : | #28 |
Yes, it works if I remove compreg.dat.
Vincent Untz (vuntz) wrote : | #29 |
- compreg.dat Edit (63.5 KiB, text/plain)
Created an attachment (id=5278)
compreg.dat
I'm seeing this here too.
I'm attaching the compreg.dat file in case it is useful.
Looking at the timestamp of the file, it seems to be when I launched
gnome-app-install. But I see no reason why this would create the file...
rngadam (rngadam) wrote : | #30 |
Dapper Drake Flight CD 2 was released with this bug which leads to a
non-functionnal, segfaulting Yelp (System > Help, System > About Ubuntu). Upon
removing this compreg.dat file, all the problems go away. Not that obvious to
find that this was already reported thru this bug...
Sebastien Bacher (seb128) wrote : | #31 |
*** Bug 27103 has been marked as a duplicate of this bug. ***
Sebastien Bacher (seb128) wrote : | #32 |
*** Bug 27306 has been marked as a duplicate of this bug. ***
Sebastien Bacher (seb128) wrote : | #33 |
*** Bug 27305 has been marked as a duplicate of this bug. ***
Sebastien Bacher (seb128) wrote : | #34 |
*** Bug 27960 has been marked as a duplicate of this bug. ***
Ian Jackson (ijackson) wrote : | #35 |
- hook which breaks bash when the problem occurs Edit (889 bytes, text/plain)
Created an attachment (id=5583)
hook which breaks bash when the problem occurs
I have tested another breezy->dapper upgrade and this bug has not recurred for
me.
I have a rather unfriendly suggestion to make :-). I wrote a test program
(attached, compreg.c) which is intended to replace /bin/bash. When the problem
occurs, it starts grumbling on stderr and/or failing.
If you have a machine you don't mind breaking, please
1. make sure the compreg.dat doesn't already exist; if it does then it's too
late to see what created it.
2. update-alternatives --rename /bin/bash
3. cp compreg /bin/bash
4. run all updates and installations in script or similar if possible
When the machine breaks, you'll have found the problem. To make the machine
working again, boot from a rescue disk or equivalent and un-rename bash with
update-alternatives --remove --rename /bin/bash
Ian Jackson (ijackson) wrote : | #36 |
Whatever this is, it doesn't seem to be happening any more.
Changed in firefox: | |
status: | Needs Info → Fix Released |
Ian Jackson (ijackson) wrote : | #37 |
It turns out that it is happening still but we're still mystified. See my earlier comment for a possible way of finding out what is creating this file.
Changed in firefox: | |
status: | Fix Released → Needs Info |
FrejSoya (frej) wrote : | #38 |
This appears to cause other problems - in edgy.
It's another problem with compreg.dat, and removing the file is the cure.
This is reported upstream:
http://
Ian Jackson (ijackson) wrote : | #39 |
As discussed on IRC with seb128:
I will change the firefox postinst to delete /usr/lib/
I don't think this will solve the problem - the file is being created by some other package's maintainer scripts, and that other package is probably a mozilla embedder, so it's quite likely that compreg.dat is created after firefox is upgraded.
However, it may help in some cases and it will definitely make it easier to fix the problem when you don't know what it is - just reinstalling firefox will fix it.
We will take a more serious approach to finding this problem in edgy+1, since it is evidently not just an issue with breezy/dapper.
Changed in firefox: | |
status: | Needs Info → Confirmed |
Ian Jackson (ijackson) wrote : | #40 |
This partial workaround is being deployed in edgy. I'm putting the bug back to Needs Info / no milestone to represent the underlying problem.
Changed in firefox: | |
status: | Confirmed → Needs Info |
Changed in firefox: | |
assignee: | ijackson → nobody |
John Vivirito (gnomefreak) wrote : | #41 |
Is this still an issue for you? We are trying to trying sort out the older Mozilla issues and would like to know if this still happens.
Jan Mynarik (jan-mynarik) wrote : | #42 |
No problem here in Feisty.
Hezekiah Carty (hez) wrote : | #43 |
I don't have the problem on Dapper currently, but I can't install Feisty Herd 3 to test there (unrelated installer bug)
John Vivirito (gnomefreak) wrote : | #44 |
Fix seems to have been released. Thank you for reporting this bug with us.
Changed in firefox: | |
status: | Needs Info → Fix Released |
miked (miked11) wrote : Re: firefox 2.0.0.3 upgrade still have compreg.dat, creates issue | #45 |
Downloaded, Updated, and Installed fine; but did still give this output.
Setting up firefox (2.0.0.
Please restart any running Firefoxes, or you will experience problems.
Warning: something created compreg.dat!
Your system was affected by this bug: https:/
compreg.dat has now been removed again, which should fix the symptoms.
Alexander Sack (asac) wrote : Re: [Bug 30791] Re: firefox 2.0.0.3 upgrade still have compreg.dat, creates issue | #46 |
On Tue, Mar 27, 2007 at 02:24:57PM -0000, miked wrote:
> Downloaded, Updated, and Installed fine; but did still give this output.
> Setting up firefox (2.0.0.
> Please restart any running Firefoxes, or you will experience problems.
> Warning: something created compreg.dat!
> Your system was affected by this bug: https:/
> compreg.dat has now been removed again, which should fix the symptoms.
>
What version did you upgrade from?
Please do a
dpkg -l firefox | grep compreg.dat
and tell me the output.
- Alexander
p.s. please take care that the bug is listed as To: or CC: when
replying to this mail (e.g. /reply-all/).
--
GPG messages preferred. | .''`. ** Debian GNU/Linux **
Alexander Sack | : :' : The universal
<email address hidden> | `. `' Operating System
http://
miked (miked11) wrote : | #47 |
root@Ubuntu704B
root@Ubuntu704B
I upgraded from 2.0.0.1+, or what ever version a fresh install of Ubuntu 7.04 Beta has.
I don't know where the file would be, and Beagle cannot be run as root it says.
Sam_ (and-sam) wrote : Re: firefox 2.0.0.3 upgrade still have compreg.dat, creates issue | #48 |
Hey,
I've just upgraded to FF 2.0.0.4, in the download details was the following message (same as upon posted):
> Warning: something created compreg.dat!
> Your system was affected by this bug: https:/
> compreg.dat has now been removed again, which should fix the symptoms.
BUT, I didn't experience any problems before :-)
compreg.dat is not on my pc (feisty) now.
Fabio Colombo (stratosphere1982) wrote : | #49 |
I've the same problem Sam. I had a lot of problems, like for example webpages blocked and so on.. hope to solve the problem..
Jere Kupari (jere-kupari) wrote : | #50 |
I also got this updating firefox
Warning: something created compreg.dat!
Your system was affected by this bug: https:/
Firefox, Epiphany and everything seemes to work normally, before and after the update.
Alexander asked:
>What version did you upgrade from?
firefox (2.0.0.
(amd64)
>Please do a
>dpkg -l firefox | grep compreg.dat
>and tell me the output.
Did you mean dpkg -L | grep compreg.dat ?
-l seems to list only the package name.
Neither gives anything.
Alexander Sack (asac) wrote : Re: [Bug 30791] Re: firefox 1.4.99 upgrade still have compreg.dat, creates issue | #51 |
On Sat, Jun 02, 2007 at 01:09:34PM -0000, Jere Kupari wrote:
> I also got this updating firefox
> Warning: something created compreg.dat!
> Your system was affected by this bug: https:/
>
> Firefox, Epiphany and everything seemes to work normally, before and
> after the update.
>
> Alexander asked:
> >What version did you upgrade from?
>
> firefox (2.0.0.
> (amd64)
>
> >Please do a
> >dpkg -l firefox | grep compreg.dat
> >and tell me the output.
>
> Did you mean dpkg -L | grep compreg.dat ?
> -l seems to list only the package name.
>
> Neither gives anything.
>
compreg.dat is known to be created if you run epiphany as "root" or
with sudo. Though this is a bug, its not likely to be fixed soon (I
asked epiphany developers about that).
So as a workaround, please don't start epiphany as root.
Thanks,
- Alexander
Jere Kupari (jere-kupari) wrote : | #52 |
I'm quite sure I have never run epiphany as root. I don't even use epiphany normally.
But anyway, this bug doesn't seem to cause me any trouble.
Guillaume Romagny (golfromeo.ovh) wrote : | #53 |
I have the same message as Jere Kupari on feisty x86 during the upgrade from 2.0.0.3 to 2.0.0.4
I don't know what is epiphany, so running it as root is not (directly) possible.
Firefox is still working anyway !
Best regards,
Guillaume
Ralph Corderoy (ralph-inputplus) wrote : | #54 |
I just got the "Warning: something created compreg.dat! Your system was affected by this bug: https:/
It's a recent installation of 7.04 and I've never run Epiphany as root.
Alexander Sack (asac) wrote : | #55 |
On Fri, Aug 10, 2007 at 01:26:02PM -0000, Ralph Corderoy wrote:
> I just got the "Warning: something created compreg.dat! Your system was
> affected by this bug: https:/
> get upgrade -u' of 7.04. Firefox was one of the packages upgraded.
>
> It's a recent installation of 7.04 and I've never run Epiphany as root.
>
Well ... running any gtkmozembed application as root will create this
atm. Firefox doesn't do that anymore.
- Alexander
Ralph Corderoy (ralph-inputplus) wrote : | #56 |
OK, thanks. I'm not aware of running much GUI stuff as root. I do most things from the shell. Anyway, the history of this bug is confusing. What corrective action should a user take when `apt-get upgrade' refers them to this bug? And if it's not epiphany, are people trying to find out what might be creating it instead? Is there anything I and other sufferers can do to help?
Giuseppe Fiorito (giuseppe-fiorito) wrote : | #57 |
On ubuntu 7.04 and firefox 2.0.0.6 the bug still continue. I've to remove manualy the compreg.dat file to start firefox.
Nitesh Mistry (mistrynitesh) wrote : | #58 |
I found the same while updating today from FF2.0.0.6 to FF2.0.0.8
"Setting up firefox (2.0.0.
Please restart any running Firefoxes, or you will experience problems.
Warning: something created compreg.dat!
Your system was affected by this bug: https:/
compreg.dat has now been removed again, which should fix the symptoms."
I don't know what is epiphany, and neither is it installed on my pc (running Fiesty)
Daniel Silberschmidt (dansilber) wrote : | #59 |
same situation here, while updating firefox in gutsy today:
>(...)
>Preparing to replace firefox 2.0.0.8+
>(...)
>Please restart any runnning Firefoxes, or you will will experience problems.
>Warning: something created compreg.dat!
>Your system was affected by this bug https:/
>compreg.dat has now been removed again, which should fix the symptoms.
I never used epiphany.
Pawel Tecza (ptecza) wrote : | #60 |
I can confirm the report by Daniel Silberschmidt. I've never used that browser too.
Gordon Cock (gordonc) wrote : | #61 |
I have received this same error on a newly installed Gutsy instance.
Setting up firefox (2.0.0.
Never used Epiphany. Could this be something to do with Firefox add-Ons?
Currently using GMarks 0.9.7.2 , NoScript 1.1.8.3 and ubufox 0.4_beta1
Olivier B (obourrion) wrote : | #62 |
@ Daniel Silberschmidt
Check if your .mozilla directory has user rights and not root rights. It seems that it was my case, I removed the directory and relaunched firefox logged as a user and it worked again!
Sam_ (and-sam) wrote : | #63 |
Hi again,
slowly it's irritating, but after update to firefox 2.0.0.12 few days ago, message apeared again:
Warning: something created compreg.dat!
Your system was affected by this bug: https:/
compreg.dat has now been removed again, which should fix the symptom.
I don't use epiphany and don't run ff as root.
#dpkg -l firefox | grep compreg.dat - no output
#/usr/lib/
#/home/
and usually after every update this message:
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
just in case it correlates, which I don't think.
Sam_ (and-sam) wrote : | #64 |
Hi,
correct: appeared.
Removed compreg.dat from ~/. and instantly it appears new same place.
Ralph Corderoy (ralph-inputplus) wrote : | #65 |
Sam, thanks for the update.
> #dpkg -l firefox | grep compreg.dat - no output
That should be `dpkg -L firefox'; the original request above is wrong.
`dpkg -l' just lists the package status. `dpkg -L' lists all the files
installed by the package.
> and usually after every update this message:
> Processing triggers for libc6 ...
> ldconfig deferred processing now taking place
>
> just in case it correlates, which I don't think.
No, it doesn't.
Sam_ (and-sam) wrote : | #66 |
Thanks for the response Ralph,
also with the "L" no output.
maty1206 (maty1206-deactivatedaccount-deactivatedaccount) wrote : | #67 |
- Navegador\ web\ Firefox.log Edit (154 bytes, text/plain)
I have the same issue.
I use Ubuntu 7.10 and firefox 2.0.0.12.
When I try to use a web site which requires of Java JRE it close inmediatly.
I had reinstalled firefox and upgrade the OS
I had added the log file.
Thanks for your time
Sam_ (and-sam) wrote : | #68 |
Hi again,
same message and procedure as above on 12th of Feb. when updating today to firefox 2.0.0.13.
When "something" is creating compreg.dat, do we know by now who is the creator?
Will the result that it has to be removed every time and still remains in the home folder of .mozilla be constant? If so, I won't bother here anymore.
papukaija (papukaija) wrote : | #69 |
Why this bug is marked as fixed?
Today, I updated my Firefox to 2.0.0.14 and I got in the terminal :
"Warning: something created compreg.dat!
Your system was affected by this bug: https:/
compreg.dat has now been removed again, which should fix the symptom".
I don't use epiphany and don't run Firefox as root. I'm using Ubuntu 7.10
Al Sharpe (asharpe-sympatico) wrote : | #70 |
Just a thought.
I installed VMware Server beta 2 and it needed root to work.
It uses Firefox as root to launch VMware Infrastructure Web access to
perform host and virtual machine configuration.
I have noticed no problems and the file does regenerate upon starting up firefox.
It is a text file only.
FYI
John Vivirito (gnomefreak) wrote : | #71 |
Running it as root is going to cause this file to be made.
Alexander is there a way to maybe make firefox, epiphany not run as root without some warning stating this is going to cause the compreg.dat to be made and to remove it when you are done?
Marking as a wishlist bug and marking as incomplete.
John Vivirito (gnomefreak) wrote : | #72 |
I will ping the Alexander about this when i get back to IRC.
Changed in firefox: | |
assignee: | nobody → mozilla-bugs |
importance: | Medium → Wishlist |
status: | Fix Released → Incomplete |
papukaija (papukaija) wrote : | #73 |
My update from firefox 3 to 3.0.1 didn't give the error message:"Warning: something created compreg.dat!
Your system was affected by this bug: https:/
compreg.dat has now been removed again, which should fix the symptom".
It seems that this bug is fixed.
John Vivirito (gnomefreak) wrote : | #74 |
papukaija wrote:
> My update from firefox 3 to 3.0.1 didn't give the error message:"Warning: something created compreg.dat!
> Your system was affected by this bug: https:/
> compreg.dat has now been removed again, which should fix the symptom".
>
> It seems that this bug is fixed.
>
>
I can confirm this issue has been fixed. If you still see this issue
please update to latest 3.0.1.
status fixreleased
Changed in firefox: | |
status: | Incomplete → Fix Released |
I gave the version information for "epiphany", not "epiphany-browser".
Epiphany version is 1.8.2-0ubuntu1