Author Topic: firefox - Segfault (Read 4205 times)

The Chief · « **Reply #30 on:** April 15, 2011, 07:49:01 PM »

Well, crap!

I was gonna tell how I hosed my Firefox (wouldn't run - segfault every time) and so thought to re-install it, but then thought I'd better update first, and then noticed Firefox was in the update list and that cured my dumb mistake.

But hey! Maybe it wasn't dumb ol' me after all! You guys have made me feel better about myself!

Texstar · « **Reply #31 on:** April 15, 2011, 08:30:22 PM »

sqlite3 developers released a bad package 3.7.6 that caused Firefox to segfault. They updated it to 3.7.6.1 which fixed the issue so we pushed it out as fast as possible. I like to keep sqlite3, nspr4 and nss3 updated because every time a new Firefox/Thunderbird update comes out they always build against the latest versions of those packages. As they say *poopie* happens.

Old-Polack · « **Reply #32 on:** April 16, 2011, 02:44:51 AM »

Quote from: Texstar on April 15, 2011, 08:30:22 PM

sqlite3 developers released a bad package 3.7.6 that caused Firefox to segfault. They updated it to 3.7.6.1 which fixed the issue so we pushed it out as fast as possible. I like to keep sqlite3, nspr4 and nss3 updated because every time a new Firefox/Thunderbird update comes out they always build against the latest versions of those packages. As they say *poopie* happens.

Doesn't seem to be fixed here. Reinstalled and got this;

Code: [Select]

libsqlite3_0-3.7.6.1-1pclos2011
libsqlite3-devel-3.7.6.1-1pclos2011
rpmdb: Page 1489: item 70 hashes incorrectly
rpmdb: /var/lib/rpm/Basenames: DB_VERIFY_BAD: Database verification failed
error: db4 error(-30972) from db->verify: DB_VERIFY_BAD: Database verification failed

I've done the;

[root@fatman ~]# rm -f /var/lib/rpm/__db.*

[root@fatman ~]# rpm -vv --rebuilddb

routine three times, but error still comes up. Also ran a e2fsck -f on this / partition from another installation, which didn't report any errors.

reinstalled librpm4.4 and got

Code: [Select]

librpm4.4-4.4.6-18pclos2007
rpmdb: Page 1489: item 70 hashes incorrectly
rpmdb: /var/lib/rpm/Basenames: DB_VERIFY_BAD: Database verification failed
error: db4 error(-30972) from db->verify: DB_VERIFY_BAD: Database verification failed

Did the rpm -vv --rebuilddb routine again, which seems to go good for a while then I get a lot of this;

Code: [Select]

rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30974) getting "wZ��
�������ޟ}@���" records from Filedigests index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30974) getting " P        N��
                                           m�\#@���" records from Filedigests index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30974) getting "▒���
                                  �
                                   %����q��B@���" records from Filedigests index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30974) getting "▒���
                                  �
                                   %����q��B@���" records from Filedigests index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot add record originally at 1098
D: closed   db index       /var/lib/rpm/Packages
D: closed   db environment /var/lib/rpm/Packages
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
D: closed   db index       /var/lib/rpmrebuilddb.22484/Filedigests
D: verified db index       /var/lib/rpmrebuilddb.22484/Filedigests
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
D: closed   db index       /var/lib/rpmrebuilddb.22484/Sha1header
D: verified db index       /var/lib/rpmrebuilddb.22484/Sha1header
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
D: closed   db index       /var/lib/rpmrebuilddb.22484/Sigmd5
D: verified db index       /var/lib/rpmrebuilddb.22484/Sigmd5
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
D: closed   db index       /var/lib/rpmrebuilddb.22484/Installtid
D: verified db index       /var/lib/rpmrebuilddb.22484/Installtid
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
D: closed   db index       /var/lib/rpmrebuilddb.22484/Provideversion
D: verified db index       /var/lib/rpmrebuilddb.22484/Provideversion
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
D: closed   db index       /var/lib/rpmrebuilddb.22484/Requireversion
D: verified db index       /var/lib/rpmrebuilddb.22484/Requireversion
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
D: closed   db index       /var/lib/rpmrebuilddb.22484/Dirnames
D: verified db index       /var/lib/rpmrebuilddb.22484/Dirnames
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
D: closed   db index       /var/lib/rpmrebuilddb.22484/Triggername
D: verified db index       /var/lib/rpmrebuilddb.22484/Triggername
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
D: closed   db index       /var/lib/rpmrebuilddb.22484/Conflictname
D: verified db index       /var/lib/rpmrebuilddb.22484/Conflictname
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
D: closed   db index       /var/lib/rpmrebuilddb.22484/Providename
D: verified db index       /var/lib/rpmrebuilddb.22484/Providename
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
D: closed   db index       /var/lib/rpmrebuilddb.22484/Requirename
D: verified db index       /var/lib/rpmrebuilddb.22484/Requirename
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
D: closed   db index       /var/lib/rpmrebuilddb.22484/Group
D: verified db index       /var/lib/rpmrebuilddb.22484/Group
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
D: closed   db index       /var/lib/rpmrebuilddb.22484/Basenames
rpmdb: Page 1150: item 154 has bad type
rpmdb: Page 1189: invalid next_pgno 2579
rpmdb: /var/lib/rpmrebuilddb.22484/Basenames: DB_VERIFY_BAD: Database verification failed
error: db4 error(-30972) from db->verify: DB_VERIFY_BAD: Database verification failed
D: verified db index       /var/lib/rpmrebuilddb.22484/Basenames
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
D: closed   db index       /var/lib/rpmrebuilddb.22484/Name
D: verified db index       /var/lib/rpmrebuilddb.22484/Name
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
D: closed   db index       /var/lib/rpmrebuilddb.22484/Packages
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery
D: closed   db environment /var/lib/rpmrebuilddb.22484/Packages
D: verified db index       /var/lib/rpmrebuilddb.22484/Packages
failed to rebuild database: original database remains in place
D: removing directory /var/lib/rpmrebuilddb.22484
error: failed to remove directory /var/lib/rpmrebuilddb.22484: No such file or directory

I don't do databases, so what now?

Texstar · « **Reply #33 on:** April 16, 2011, 03:14:02 AM »

Don't know what sqlite would have to do with your rpm datbase. I ran the same commands as you on both systems here and I got nuff'n like you got so what now?

Edit: what about copying older version of the sqlite3 library to you broke rpm partition?

AS · « **Reply #34 on:** April 16, 2011, 03:26:12 AM »

Quote

Doesn't seem to be fixed here. Reinstalled and got this;
Code: [Select]
libsqlite3_0-3.7.6.1-1pclos2011 libsqlite3-devel-3.7.6.1-1pclos2011 rpmdb: Page 1489: item 70 hashes incorrectly rpmdb: /var/lib/rpm/Basenames: DB_VERIFY_BAD: Database verification failed error: db4 error(-30972) from db->verify: DB_VERIFY_BAD: Database verification failed

It's not clear to me if the reinstallation of sqlite related packages, in the end went well or not.

If not, I would suggest to copy the required sqlite files from a working and updated installation, that's because rpm depend from libsqlite3

info about my updated system libsqlite3:

rpm -qa | grep sqlite
libsqlite3_0-3.7.6.1-1pclos2011
libsqlite3-devel-3.7.6.1-1pclos2011

ls -l /usr/lib/libsql*
-rwxr-xr-x 1 root root 822 Apr 14 20:20 /usr/lib/libsqlite3.la*
lrwxrwxrwx 1 root root 19 Apr 14 21:14 /usr/lib/libsqlite3.so -> libsqlite3.so.0.8.6*
lrwxrwxrwx 1 root root 19 Apr 14 21:14 /usr/lib/libsqlite3.so.0 -> libsqlite3.so.0.8.6*
-rwxr-xr-x 1 root root 646640 Apr 14 20:20 /usr/lib/libsqlite3.so.0.8.6*

As far as I know the source of the rpm database is /var/lib/rpm/Packages, all others are rebuilt against this one,
this info is for an eventual recover from a backup.

I give a shot at rpm -vv --rebuilddb (in a virtualbox fake installation) and all went well.

AS

CJ · « **Reply #35 on:** April 16, 2011, 03:39:03 AM »

Quote from: as on April 15, 2011, 03:55:21 PM

could you add also the following ?

rpm -qa | grep libglib

Sure...:

Code: [Select]

rpm -qa | grep libglib
libglibmm2.4_1-2.28.0-1pclos2011
libglib2.0_0-2.28.6-1pclos2011
libglib1.2-1.2.10-17pclos2007
libglib2.0_0-devel-2.28.6-1pclos2011

CJ

Old-Polack · « **Reply #36 on:** April 16, 2011, 04:07:29 AM »

Quote from: Texstar on April 16, 2011, 03:14:02 AM

Don't know what sqlite would have to do with your rpm datbase. I ran the same commands as you on both systems here and I got nuff'n like you got so what now?

Like I said, I don't do databases. I have no idea what relates to what when discussing databases. The sqlite upgrade/installation brought up the rpmdb error message in synaptic, and the rpmdb brings up a db4 error. Something, it would seem, needs to be reinstalled to correct the situation. The question is, what would that be?

Everything was working correctly until the last few days upgrades. I don't know if the upgrades caused this, or if it's just a coincidence of timing. The only thing I'm sure of is that a problem now exists, that didn't exist a week ago. I'm more concerned with how to fix the problem than what precipitated it, unless it was a specific package upgrade. More than likely it's a local problem that only needs to be fixed on my machine, but it's also possible that it could occur on other machines, and I'm just the first to see it.

Others had problems with Firefox segfaulting; I didn't. After the latest upgrades that seemed to cure their problems, I suddenly have Firefox segfaulting for the first time ever, as well as the rpmdb now spitting out errors I've never seen before. Synaptic still works, as far as installing/reinstalling/uninstalling packages goes, but it also shows the rpmdb errors reported. While it's still working, some suggestions as to what I should try reinstalling would be helpful.

Old-Polack · « **Reply #37 on:** April 16, 2011, 04:27:54 AM »

Quote from: as on April 16, 2011, 03:26:12 AM

Quote
Doesn't seem to be fixed here. Reinstalled and got this;
Code: [Select]
libsqlite3_0-3.7.6.1-1pclos2011 libsqlite3-devel-3.7.6.1-1pclos2011 rpmdb: Page 1489: item 70 hashes incorrectly rpmdb: /var/lib/rpm/Basenames: DB_VERIFY_BAD: Database verification failed error: db4 error(-30972) from db->verify: DB_VERIFY_BAD: Database verification failed

It's not clear to me if the reinstallation of sqlite related packages, in the end went well or not.

If not, I would suggest to copy the required sqlite files from a working and updated installation, that's because rpm depend from libsqlite3

info about my updated system libsqlite3:

rpm -qa | grep sqlite
libsqlite3_0-3.7.6.1-1pclos2011
libsqlite3-devel-3.7.6.1-1pclos2011

ls -l /usr/lib/libsql*
-rwxr-xr-x 1 root root 822 Apr 14 20:20 /usr/lib/libsqlite3.la*
lrwxrwxrwx 1 root root 19 Apr 14 21:14 /usr/lib/libsqlite3.so -> libsqlite3.so.0.8.6*
lrwxrwxrwx 1 root root 19 Apr 14 21:14 /usr/lib/libsqlite3.so.0 -> libsqlite3.so.0.8.6*
-rwxr-xr-x 1 root root 646640 Apr 14 20:20 /usr/lib/libsqlite3.so.0.8.6*

As far as I know the source of the rpm database is /var/lib/rpm/Packages, all others are rebuilt against this one,
this info is for an eventual recover from a backup.

I give a shot at rpm -vv --rebuilddb (in a virtualbox fake installation) and all went well.

AS

[root@fatman ~]# rpm -qa | grep sqlite

Code: [Select]

error: rpmdb: damaged header #1981 retrieved -- skipping.
libsqlite3-devel-3.7.6.1-1pclos2011
qt4-database-plugin-sqlite-4.7.2-1pclos2011
libsqlite3_0-3.7.6.1-1pclos2011

[root@fatman ~]# ls -l /usr/lib/libsql*

Code: [Select]

-rwxr-xr-x 1 root root    822 Apr 14 13:20 /usr/lib/libsqlite3.la*
lrwxrwxrwx 1 root root     19 Apr 16 02:59 /usr/lib/libsqlite3.so -> libsqlite3.so.0.8.6*
lrwxrwxrwx 1 root root     19 Apr 16 02:59 /usr/lib/libsqlite3.so.0 -> libsqlite3.so.0.8.6*
-rwxr-xr-x 1 root root 648116 Apr 14 13:20 /usr/lib/libsqlite3.so.0.8.6*

Except for the damaged header error, seems much the same.

AS · « **Reply #38 on:** April 16, 2011, 04:31:39 AM »

Quote

-rwxr-xr-x 1 root root 648116 Apr 14 13:20 /usr/lib/libsqlite3.so.0.8.6

sorry this is not the expected size!

Old-Polack · « **Reply #39 on:** April 16, 2011, 05:04:18 AM »

Quote from: as on April 16, 2011, 04:31:39 AM

Quote
-rwxr-xr-x 1 root root 648116 Apr 14 13:20 /usr/lib/libsqlite3.so.0.8.6

sorry this is not the expected size!

Reinstalled again;

[root@fatman ~]# ls -l /usr/lib/libsql*

Code: [Select]

-rwxr-xr-x 1 root root    822 Apr 14 13:20 /usr/lib/libsqlite3.la*
lrwxrwxrwx 1 root root     19 Apr 16 06:02 /usr/lib/libsqlite3.so -> libsqlite3.so.0.8.6*
lrwxrwxrwx 1 root root     19 Apr 16 06:02 /usr/lib/libsqlite3.so.0 -> libsqlite3.so.0.8.6*
-rwxr-xr-x 1 root root 646640 Apr 14 13:20 /usr/lib/libsqlite3.so.0.8.6*

AS · « **Reply #40 on:** April 16, 2011, 05:06:07 AM »

have you tried to rebuild the rpm database now, after libsqlite3 reinstallation ?

Old-Polack · « **Reply #41 on:** April 16, 2011, 05:14:33 AM »

Quote from: as on April 16, 2011, 05:06:07 AM

have you tried to rebuild the rpm database now, after libsqlite3 reinstallation ?

Yup and it closes like this.

Code: [Select]

D: adding 38 entries to Requireversion index.
D: adding 10 entries to Provideversion index.
D: adding 1 entries to Installtid index.
D: adding 1 entries to Sigmd5 index.
D: adding "7a56dd6fc2d9bd78af24d7d320452963d1c7acfb" to Sha1header index.
D: adding 4 entries to Filedigests index.
D: closed   db index       /var/lib/rpm/Packages
D: closed   db environment /var/lib/rpm/Packages
D: closed   db index       /var/lib/rpmrebuilddb.5613/Pubkeys
D: verified db index       /var/lib/rpmrebuilddb.5613/Pubkeys
D: closed   db index       /var/lib/rpmrebuilddb.5613/Filedigests
D: verified db index       /var/lib/rpmrebuilddb.5613/Filedigests
D: closed   db index       /var/lib/rpmrebuilddb.5613/Sha1header
D: verified db index       /var/lib/rpmrebuilddb.5613/Sha1header
D: closed   db index       /var/lib/rpmrebuilddb.5613/Sigmd5
D: verified db index       /var/lib/rpmrebuilddb.5613/Sigmd5
D: closed   db index       /var/lib/rpmrebuilddb.5613/Installtid
D: verified db index       /var/lib/rpmrebuilddb.5613/Installtid
D: closed   db index       /var/lib/rpmrebuilddb.5613/Provideversion
D: verified db index       /var/lib/rpmrebuilddb.5613/Provideversion
D: closed   db index       /var/lib/rpmrebuilddb.5613/Requireversion
D: verified db index       /var/lib/rpmrebuilddb.5613/Requireversion
D: closed   db index       /var/lib/rpmrebuilddb.5613/Dirnames
D: verified db index       /var/lib/rpmrebuilddb.5613/Dirnames
D: closed   db index       /var/lib/rpmrebuilddb.5613/Triggername
D: verified db index       /var/lib/rpmrebuilddb.5613/Triggername
D: closed   db index       /var/lib/rpmrebuilddb.5613/Conflictname
D: verified db index       /var/lib/rpmrebuilddb.5613/Conflictname
D: closed   db index       /var/lib/rpmrebuilddb.5613/Providename
D: verified db index       /var/lib/rpmrebuilddb.5613/Providename
D: closed   db index       /var/lib/rpmrebuilddb.5613/Requirename
D: verified db index       /var/lib/rpmrebuilddb.5613/Requirename
D: closed   db index       /var/lib/rpmrebuilddb.5613/Group
D: verified db index       /var/lib/rpmrebuilddb.5613/Group
D: closed   db index       /var/lib/rpmrebuilddb.5613/Basenames
D: verified db index       /var/lib/rpmrebuilddb.5613/Basenames
D: closed   db index       /var/lib/rpmrebuilddb.5613/Name
D: verified db index       /var/lib/rpmrebuilddb.5613/Name
D: closed   db index       /var/lib/rpmrebuilddb.5613/Packages
D: closed   db environment /var/lib/rpmrebuilddb.5613/Packages
D: verified db index       /var/lib/rpmrebuilddb.5613/Packages
D: removing directory /var/lib/rpmrebuilddb.5613

Note everything closed and verified. No error messages. Guess there's a direct relationship after all.

Also;

[root@fatman ~]# rpm -qa | grep sqlite
qt4-database-plugin-sqlite-4.7.2-1pclos2011
libsqlite3_0-3.7.6.1-1pclos2011
libsqlite3-devel-3.7.6.1-1pclos2011

No damaged header error either.

AS · « **Reply #42 on:** April 16, 2011, 05:18:49 AM »

@OP,

nice done!

@CJ, and all others still having firefox or libsqlite3 problems:

Quote from: CJ on April 16, 2011, 03:39:03 AM

Quote from: as on April 15, 2011, 03:55:21 PM
could you add also the following ?

rpm -qa | grep libglib

Sure...:
Code: [Select]
rpm -qa | grep libglib libglibmm2.4_1-2.28.0-1pclos2011 libglib2.0_0-2.28.6-1pclos2011 libglib1.2-1.2.10-17pclos2007 libglib2.0_0-devel-2.28.6-1pclos2011
CJ

If you have followed the thread, the reinstallation of libsqlite3 is highly advisable.

AS

Old-Polack · « **Reply #43 on:** April 16, 2011, 05:24:24 AM »

Quote from: as on April 16, 2011, 05:18:49 AM

@OP,

nice done!

Good catch on your part about the size mismatch. Thank you, my friend; I missed that completely.

Texstar · « **Reply #44 on:** April 16, 2011, 07:32:23 AM »

I hate it when stuff happens to other people but not me on my systems. Kinda makes it hard to offer a fix when it isn't broken for me. Firefox wasn't segfaulting on me at all even with the sqlite3 3.7.6. I happen to come across it while testing Linuxera's iso in root mode on vbox.

PCLinuxOS-Forums

News:

Author Topic: firefox - Segfault (Read 4205 times)

The Chief

Re: firefox - Segfault

Texstar

Re: firefox - Segfault

Old-Polack

Re: firefox - Segfault

Texstar

Re: firefox - Segfault

AS

Re: firefox - Segfault

CJ

Re: firefox - Segfault

Old-Polack

Re: firefox - Segfault

Old-Polack

Re: firefox - Segfault

AS

Re: firefox - Segfault

Old-Polack

Re: firefox - Segfault

AS

Re: firefox - Segfault

Old-Polack

Re: firefox - Segfault

AS

Re: firefox - Segfault

Old-Polack

Re: firefox - Segfault

Texstar

Re: firefox - Segfault