firefox 1.4.99 upgrade still have compreg.dat, creates issue

Bug #30791 reported by PeterShinners
162
This bug affects 1 person
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+1.5rc3.dfsg-1ubuntu3.

"""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.

Revision history for this message
PeterShinners (pete-shinners) wrote :

I gave the version information for "epiphany", not "epiphany-browser".
Epiphany version is 1.8.2-0ubuntu1

Revision history for this message
Jeroen (jeroenubuntu) wrote :

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..

Revision history for this message
Sebastien Bacher (seb128) wrote :

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

Revision history for this message
Jeroen (jeroenubuntu) wrote :

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://archive.ubuntu.com dapper Release.gpg [189B]
Hit http://archive.ubuntu.com dapper Release
Hit http://archive.ubuntu.com dapper/main Packages
Hit http://archive.ubuntu.com dapper/universe Packages
Hit http://archive.ubuntu.com dapper/main Sources
Hit http://archive.ubuntu.com dapper/universe Sources
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.

Revision history for this message
PeterShinners (pete-shinners) wrote :

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.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Christian, do you have an idea on this? :)

Revision history for this message
c7d2f5c8667d26fffd5e7772d632c76d (c7d2f5c8667d26fffd5e7772d632c76d-deactivatedaccount) wrote :

When you start epiphany from a shell, are there any messages output on console?

Revision history for this message
Jeroen (jeroenubuntu) wrote :
Download full text (6.7 KiB)

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/i686/cmov/libthread_db.so.1".
(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/i686/cmov/libc.so.6
#2 0xb710ca68 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#3 0xb710cf38 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#4 0xb771ef93 in gtk_dialog_run () from /usr/lib/libgtk-x11-2.0.so.0
#5 0x080b71ce in impl_permission_manager_test ()
#6 0xb71922a3 in g_type_create_instance () from /usr/lib/libgobject-2.0.so.0
#7 0xb71779e6 in g_object_thaw_notify () from /u...

Read more...

Revision history for this message
PeterShinners (pete-shinners) wrote :

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.

Revision history for this message
Jeroen (jeroenubuntu) wrote :

(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...

Revision history for this message
asubedi (asubedi) wrote :

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.

Revision history for this message
PeterShinners (pete-shinners) wrote :

Upgraded to today's new Firefox: 1.4.99+1.5rc3.dfsg-1ubuntu4
Current Epiphany version: 1.9.2-0ubuntu2

Still getting the same Epiphany error about initialization failed.

Revision history for this message
Sebastien Bacher (seb128) wrote :

what architecture do you use?

Revision history for this message
PeterShinners (pete-shinners) wrote :

Architecture is x86. Specifically "2.6.15-5-686"

Revision history for this message
Jeroen (jeroenubuntu) wrote :

i386. Can't help with this anymore, until I start running dapper again.

Revision history for this message
Daniel Holbach (dholbach) wrote :

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?

Revision history for this message
Jeroen (jeroenubuntu) wrote :

I switched back to breezy, Daniel.

Revision history for this message
PeterShinners (pete-shinners) wrote :

Created an attachment (id=5192)
Petes apt sources.list

Revision history for this message
asubedi (asubedi) wrote :

(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.

Revision history for this message
PeterShinners (pete-shinners) wrote :

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.

Revision history for this message
James "Doc" Livingston (jrl) wrote :

I'm also seeing this, with an up-to-date Dapper. This is probably firefox/gecko
related, because all my gecko-using applications (except firefox) either fail or
segfault on starting. My DevHelp report is bug 26533 and Yelp is bug 26711.

Revision history for this message
Sebastien Bacher (seb128) wrote :

We discussed that on IRC with Christian and James. The issue is created by
/usr/lib/mozilla-firefox/components/compreg.dat. This file is shipped with the
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?

Revision history for this message
Sebastien Bacher (seb128) wrote :

*** Bug 26533 has been marked as a duplicate of this bug. ***

Revision history for this message
Sebastien Bacher (seb128) wrote :

*** Bug 26711 has been marked as a duplicate of this bug. ***

Revision history for this message
Ian Jackson (ijackson) wrote :

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.

Revision history for this message
PeterShinners (pete-shinners) wrote :

As a user, renaming "/usr/lib/mozilla-firefox/components/compreg.dat" has fixed
this for me.
I'm posting this with Epihany!

Revision history for this message
Sebastien Bacher (seb128) wrote :

*** Bug 26861 has been marked as a duplicate of this bug. ***

Revision history for this message
asubedi (asubedi) wrote :

Yes, it works if I remove compreg.dat.

Revision history for this message
Vincent Untz (vuntz) wrote :

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...

Revision history for this message
rngadam (rngadam) wrote :

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...

Revision history for this message
Sebastien Bacher (seb128) wrote :

*** Bug 27103 has been marked as a duplicate of this bug. ***

Revision history for this message
Sebastien Bacher (seb128) wrote :

*** Bug 27306 has been marked as a duplicate of this bug. ***

Revision history for this message
Sebastien Bacher (seb128) wrote :

*** Bug 27305 has been marked as a duplicate of this bug. ***

Revision history for this message
Sebastien Bacher (seb128) wrote :

*** Bug 27960 has been marked as a duplicate of this bug. ***

Revision history for this message
Ian Jackson (ijackson) wrote :

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

Revision history for this message
Ian Jackson (ijackson) wrote :

Whatever this is, it doesn't seem to be happening any more.

Changed in firefox:
status: Needs Info → Fix Released
Revision history for this message
Ian Jackson (ijackson) wrote :

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
Revision history for this message
FrejSoya (frej) wrote :

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://bugzilla.gnome.org/show_bug.cgi?id=353115

Revision history for this message
Ian Jackson (ijackson) wrote :

As discussed on IRC with seb128:

I will change the firefox postinst to delete /usr/lib/firefox/components/compreg.dat (grumbling to stderr if it finds it).

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
Revision history for this message
Ian Jackson (ijackson) wrote :

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
Ian Jackson (ijackson)
Changed in firefox:
assignee: ijackson → nobody
Revision history for this message
John Vivirito (gnomefreak) wrote :

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.

Revision history for this message
Jan Mynarik (jan-mynarik) wrote :

No problem here in Feisty.

Revision history for this message
Hezekiah Carty (hez) wrote :

I don't have the problem on Dapper currently, but I can't install Feisty Herd 3 to test there (unrelated installer bug)

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

Fix seems to have been released. Thank you for reporting this bug with us.

Changed in firefox:
status: Needs Info → Fix Released
Revision history for this message
miked (miked11) wrote : Re: firefox 2.0.0.3 upgrade still have compreg.dat, creates issue

Downloaded, Updated, and Installed fine; but did still give this output.
Setting up firefox (2.0.0.3+1-0ubuntu1) ...
Please restart any running Firefoxes, or you will experience problems.
Warning: something created compreg.dat!
Your system was affected by this bug: https://launchpad.net/bugs/30791
compreg.dat has now been removed again, which should fix the symptoms.

Revision history for this message
Alexander Sack (asac) wrote : Re: [Bug 30791] Re: firefox 2.0.0.3 upgrade still have compreg.dat, creates issue

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.3+1-0ubuntu1) ...
> Please restart any running Firefoxes, or you will experience problems.
> Warning: something created compreg.dat!
> Your system was affected by this bug: https://launchpad.net/bugs/30791
> 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://www.asoftsite.org | `- http://www.debian.org/

Revision history for this message
miked (miked11) wrote :

root@Ubuntu704Beta:~# dpkg -l firefox | grep compreg.dat
root@Ubuntu704Beta:~#

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.

Revision history for this message
Sam_ (and-sam) wrote : Re: firefox 2.0.0.3 upgrade still have compreg.dat, creates issue

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://launchpad.net/bugs/30791
> 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.

Revision history for this message
Fabio Colombo (stratosphere1982) wrote :

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..

Revision history for this message
Jere Kupari (jere-kupari) wrote :

I also got this updating firefox
Warning: something created compreg.dat!
Your system was affected by this bug: https://launchpad.net/bugs/30791

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.3+1-0ubuntu2) to 2.0.0.4+1-0ubuntu1
(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.

Revision history for this message
Alexander Sack (asac) wrote : Re: [Bug 30791] Re: firefox 1.4.99 upgrade still have compreg.dat, creates issue

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://launchpad.net/bugs/30791
>
> 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.3+1-0ubuntu2) to 2.0.0.4+1-0ubuntu1
> (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

Revision history for this message
Jere Kupari (jere-kupari) wrote :

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.

Revision history for this message
Guillaume Romagny (golfromeo.ovh) wrote :

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

Revision history for this message
Ralph Corderoy (ralph-inputplus) wrote :

I just got the "Warning: something created compreg.dat! Your system was affected by this bug: https://launchpad.net/bugs/30791" when doing `apt-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.

Revision history for this message
Alexander Sack (asac) wrote :

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://launchpad.net/bugs/30791" when doing `apt-
> 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

Revision history for this message
Ralph Corderoy (ralph-inputplus) wrote :

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?

Revision history for this message
Giuseppe Fiorito (giuseppe-fiorito) wrote :

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.

Revision history for this message
Nitesh Mistry (mistrynitesh) wrote :

I found the same while updating today from FF2.0.0.6 to FF2.0.0.8

"Setting up firefox (2.0.0.8+1nobinonly-0ubuntu1) ...
 Please restart any running Firefoxes, or you will experience problems.
 Warning: something created compreg.dat!
 Your system was affected by this bug: https://launchpad.net/bugs/30791
 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)

Revision history for this message
Daniel Silberschmidt (dansilber) wrote :

same situation here, while updating firefox in gutsy today:

>(...)
>Preparing to replace firefox 2.0.0.8+nobinonly-0ubuntu1 (using .../firefox_2.0.0.10+2nobinonly-0ubuntu1.7.10.1_i386.deb)
>(...)
>Please restart any runnning Firefoxes, or you will will experience problems.
>Warning: something created compreg.dat!
>Your system was affected by this bug https://launchpad.net/bugs/30791
>compreg.dat has now been removed again, which should fix the symptoms.

I never used epiphany.

Revision history for this message
Pawel Tecza (ptecza) wrote :

I can confirm the report by Daniel Silberschmidt. I've never used that browser too.

Revision history for this message
Gordon Cock (gordonc) wrote :

I have received this same error on a newly installed Gutsy instance.

Setting up firefox (2.0.0.10+2nobinonly-0ubuntu1.7.10.1) ...

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

Revision history for this message
Olivier B (obourrion) wrote :

@ 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!

Revision history for this message
Sam_ (and-sam) wrote :

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://launchpad.net/bugs/30791
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/mozilla-firefox/components/compreg.dat - no file there
#/home/username/.mozilla/firefox/hpmkendp.default - file is here

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.

Revision history for this message
Sam_ (and-sam) wrote :

Hi,
correct: appeared.
Removed compreg.dat from ~/. and instantly it appears new same place.

Revision history for this message
Ralph Corderoy (ralph-inputplus) wrote :

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.

Revision history for this message
Sam_ (and-sam) wrote :

Thanks for the response Ralph,
also with the "L" no output.

Revision history for this message
maty1206 (maty1206-deactivatedaccount-deactivatedaccount) wrote :

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

Revision history for this message
Sam_ (and-sam) wrote :

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.

Revision history for this message
papukaija (papukaija) wrote :

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://launchpad.net/bugs/30791
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

Revision history for this message
Al Sharpe (asharpe-sympatico) wrote :

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

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

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.

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

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
Revision history for this message
papukaija (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://launchpad.net/bugs/30791
compreg.dat has now been removed again, which should fix the symptom".

It seems that this bug is fixed.

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

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://launchpad.net/bugs/30791
> 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
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.