Hello all, Tonights updates seriously broke Evolution as it no longer starts on two 4.4 up-to-date boxes. When I run "evolution" from the cli I get this: $ evolution
(evolution:4865): evolution-smime-WARNING **: Failed all methods for initializing NSS The updates included firefox, seamonkey, seamonkey-nspr, and seamonkey-nss. A reboot causes no change, Any ideas?
Marvin Eberly
On Sat, Feb 24, 2007 at 10:16:40PM -0500, eberlyml@wjtl.net enlightened us:
Tonights updates seriously broke Evolution as it no longer starts on two 4.4 up-to-date boxes. When I run "evolution" from the cli I get this: $ evolution
(evolution:4865): evolution-smime-WARNING **: Failed all methods for initializing NSS The updates included firefox, seamonkey, seamonkey-nspr, and seamonkey-nss. A reboot causes no change, Any ideas?
This was also reported on the redhat nahant list. The nss update seems to have broken it - backing off to the previous version lets evolution work again. A quick search in bugzilla.redhat.com didn't turn anything up, so you may want to keep an eye on that.
Matt
On Sun, 2007-02-25 at 00:56 -0500, Matt Hyclak wrote:
On Sat, Feb 24, 2007 at 10:16:40PM -0500, eberlyml@wjtl.net enlightened us:
Tonights updates seriously broke Evolution as it no longer starts on two 4.4 up-to-date boxes. When I run "evolution" from the cli I get this: $ evolution
(evolution:4865): evolution-smime-WARNING **: Failed all methods for initializing NSS The updates included firefox, seamonkey, seamonkey-nspr, and seamonkey-nss. A reboot causes no change, Any ideas?
This was also reported on the redhat nahant list. The nss update seems to have broken it - backing off to the previous version lets evolution work again. A quick search in bugzilla.redhat.com didn't turn anything up, so you may want to keep an eye on that.
Matt
Thanks Matt, I will check further later. For the moment I did:
# rpm -Uvh --oldpackage seamonkey-nss-1.0.7-0.1.el4.centos4.i386.rpm seamonkey-nspr-1.0.7-0.1.el4.centos4.i386.rpm seamonkey-1.0.7-0.1.el4.centos4.i386.rpm
Both machines are running Evolution again, guess I'll wait for an update.
Marvin Eberly
On Sun, Feb 25, 2007 at 12:56:16AM -0500, Matt Hyclak wrote:
This was also reported on the redhat nahant list. The nss update seems to have broken it - backing off to the previous version lets evolution work again. A quick search in bugzilla.redhat.com didn't turn anything up, so you may want to keep an eye on that.
My guess is rebuilding evolution will fix it.
On Sun, 2007-02-25 at 07:42 -0500, Matthew Miller wrote:
On Sun, Feb 25, 2007 at 12:56:16AM -0500, Matt Hyclak wrote:
This was also reported on the redhat nahant list. The nss update seems to have broken it - backing off to the previous version lets evolution work again. A quick search in bugzilla.redhat.com didn't turn anything up, so you may want to keep an eye on that.
My guess is rebuilding evolution will fix it.
Sorry for a newbie question, but exactly what does this involve? The one box that this occurred on is a one week old very fresh install.
Marvin Eberly
On Sun, 2007-02-25 at 00:56 -0500, Matt Hyclak wrote:
On Sat, Feb 24, 2007 at 10:16:40PM -0500, eberlyml@wjtl.net enlightened us:
Tonights updates seriously broke Evolution as it no longer starts on two 4.4 up-to-date boxes. When I run "evolution" from the cli I get this: $ evolution
(evolution:4865): evolution-smime-WARNING **: Failed all methods for initializing NSS The updates included firefox, seamonkey, seamonkey-nspr, and seamonkey-nss. A reboot causes no change, Any ideas?
This was also reported on the redhat nahant list.
Thank goodness :P
Let me look at this, as I had to do some things (take some things out) to make my update look like upstream.
Maybe I can get this working for them :P
The nss update seems to have broken it - backing off to the previous version lets evolution work again. A quick search in bugzilla.redhat.com didn't turn anything up, so you may want to keep an eye on that.
On Sun, 2007-02-25 at 08:09 -0600, Johnny Hughes wrote:
On Sun, 2007-02-25 at 00:56 -0500, Matt Hyclak wrote:
On Sat, Feb 24, 2007 at 10:16:40PM -0500, eberlyml@wjtl.net enlightened us:
Tonights updates seriously broke Evolution as it no longer starts on two 4.4 up-to-date boxes. When I run "evolution" from the cli I get this: $ evolution
(evolution:4865): evolution-smime-WARNING **: Failed all methods for initializing NSS The updates included firefox, seamonkey, seamonkey-nspr, and seamonkey-nss. A reboot causes no change, Any ideas?
This was also reported on the redhat nahant list.
Thank goodness :P
Let me look at this, as I had to do some things (take some things out) to make my update look like upstream.
Maybe I can get this working for them :P
OK ... I want to report that I have absolutely confirmed that this is an upstream issue, and that rebuilding evolution against the new nss/nspr sources does not fix the problem.
I am still troubleshooting to find a fix ... be advised that the seamonkey-1.0.8 update was rated "Security Critical" ... but it does make Evolution unusable for mail. Shifting back to seamonkey-1.0.7 makes evolution work, but is insecure. You will all need to make your own decisions.
The nss update seems to have broken it - backing off to the previous version lets evolution work again. A quick search in bugzilla.redhat.com didn't turn anything up, so you may want to keep an eye on that.
I have submitting an upstream bug report here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229987
we also have a CentOS bug:
http://bugs.centos.org/view.php?id=1694
Thanks, Johnny Hughes
On Sun, 2007-02-25 at 12:35 -0600, Johnny Hughes wrote:
On Sun, 2007-02-25 at 08:09 -0600, Johnny Hughes wrote:
On Sun, 2007-02-25 at 00:56 -0500, Matt Hyclak wrote:
On Sat, Feb 24, 2007 at 10:16:40PM -0500, eberlyml@wjtl.net enlightened us:
Tonights updates seriously broke Evolution as it no longer starts on two 4.4 up-to-date boxes. When I run "evolution" from the cli I get this: $ evolution
(evolution:4865): evolution-smime-WARNING **: Failed all methods for initializing NSS The updates included firefox, seamonkey, seamonkey-nspr, and seamonkey-nss. A reboot causes no change, Any ideas?
This was also reported on the redhat nahant list.
Thank goodness :P
Let me look at this, as I had to do some things (take some things out) to make my update look like upstream.
Maybe I can get this working for them :P
OK ... I want to report that I have absolutely confirmed that this is an upstream issue, and that rebuilding evolution against the new nss/nspr sources does not fix the problem.
I am still troubleshooting to find a fix ... be advised that the seamonkey-1.0.8 update was rated "Security Critical" ... but it does make Evolution unusable for mail. Shifting back to seamonkey-1.0.7 makes evolution work, but is insecure. You will all need to make your own decisions.
The nss update seems to have broken it - backing off to the previous version lets evolution work again. A quick search in bugzilla.redhat.com didn't turn anything up, so you may want to keep an eye on that.
I have submitting an upstream bug report here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229987
we also have a CentOS bug:
Thanks to Markku Lehto for this fix:
There is a fix that works as a work around until another solution is done, which is to create this symbolic link:
cd /usr/lib
ln -s firefox-1.5.0.10/libfreeb13.so .
Having libfreeb13.so in /usr/lib allows evolution to start ... removing it prevents it from starting.
On Sun, 2007-02-25 at 14:00 -0600, Johnny Hughes wrote:
On Sun, 2007-02-25 at 12:35 -0600, Johnny Hughes wrote:
On Sun, 2007-02-25 at 08:09 -0600, Johnny Hughes wrote:
On Sun, 2007-02-25 at 00:56 -0500, Matt Hyclak wrote:
On Sat, Feb 24, 2007 at 10:16:40PM -0500, eberlyml@wjtl.net enlightened us:
<snip>
Thanks to Markku Lehto for this fix:
There is a fix that works as a work around until another solution is done, which is to create this symbolic link:
cd /usr/lib
ln -s firefox-1.5.0.10/libfreeb13.so .
Having libfreeb13.so in /usr/lib allows evolution to start ... removing it prevents it from starting.
When an "official" upstream fix is released, will we need to then "undo" that link?
<snip sig stuff>
Thx, -- Bill
I have submitting an upstream bug report here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229987
we also have a CentOS bug:
Thanks to Markku Lehto for this fix:
There is a fix that works as a work around until another solution is done, which is to create this symbolic link:
cd /usr/lib
ln -s firefox-1.5.0.10/libfreeb13.so .
Having libfreeb13.so in /usr/lib allows evolution to start ... removing it prevents it from starting.
Sorry guys, this didn't fix it here. What is the proper way to undo this link I made?
Marvin Eberly
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 2/25/07, P Marvin Eberly eberlyml@wjtl.net wrote:
I have submitting an upstream bug report here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229987
we also have a CentOS bug:
Thanks to Markku Lehto for this fix:
There is a fix that works as a work around until another solution is done, which is to create this symbolic link:
cd /usr/lib
ln -s firefox-1.5.0.10/libfreeb13.so .
Having libfreeb13.so in /usr/lib allows evolution to start ... removing it prevents it from starting.
Sorry guys, this didn't fix it here. What is the proper way to undo this link I made?
try the following first
ldconfig -v
if that doenst fix it.. try
rm /usr/lib/libfreeb13.so
On Sun, 2007-02-25 at 13:27 -0700, Stephen John Smoogen wrote:
On 2/25/07, P Marvin Eberly eberlyml@wjtl.net wrote:
I have submitting an upstream bug report here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229987
we also have a CentOS bug:
Thanks to Markku Lehto for this fix:
There is a fix that works as a work around until another solution is done, which is to create this symbolic link:
cd /usr/lib
ln -s firefox-1.5.0.10/libfreeb13.so .
Having libfreeb13.so in /usr/lib allows evolution to start ... removing it prevents it from starting.
Sorry guys, this didn't fix it here. What is the proper way to undo this link I made?
try the following first
ldconfig -v
if that doenst fix it.. try
rm /usr/lib/libfreeb13.so
Thanks for the try, Stephen. But no luck here at all, I removed the link and will wait for an update. I don't use seamonkey anyway.
P Marvin Eberly
On Sun, 2007-02-25 at 15:24 -0500, P Marvin Eberly wrote:
<snip>
There is a fix that works as a work around until another solution is done, which is to create this symbolic link:
cd /usr/lib
ln -s firefox-1.5.0.10/libfreeb13.so .
Having libfreeb13.so in /usr/lib allows evolution to start ... removing it prevents it from starting.
Sorry guys, this didn't fix it here. What is the proper way to undo this link I made?
cd /usr/lib rm libfreeb13.so
Marvin Eberly
<snip sig stuff>
-- Bill
On Sun, 2007-02-25 at 15:29 -0500, William L. Maltby wrote:
On Sun, 2007-02-25 at 15:24 -0500, P Marvin Eberly wrote:
<snip>
There is a fix that works as a work around until another solution is done, which is to create this symbolic link:
cd /usr/lib
ln -s firefox-1.5.0.10/libfreeb13.so .
Having libfreeb13.so in /usr/lib allows evolution to start ... removing it prevents it from starting.
Sorry guys, this didn't fix it here. What is the proper way to undo this link I made?
cd /usr/lib rm libfreeb13.so
Thanks, Bill. Done
P Marvin Eberly
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Sun, 2007-02-25 at 15:37 -0500, P Marvin Eberly wrote:
On Sun, 2007-02-25 at 15:29 -0500, William L. Maltby wrote:
On Sun, 2007-02-25 at 15:24 -0500, P Marvin Eberly wrote:
<snip>
There is a fix that works as a work around until another solution is done, which is to create this symbolic link:
cd /usr/lib
ln -s firefox-1.5.0.10/libfreeb13.so .
Having libfreeb13.so in /usr/lib allows evolution to start ... removing it prevents it from starting.
Sorry guys, this didn't fix it here. What is the proper way to undo this link I made?
cd /usr/lib rm libfreeb13.so
Thanks, Bill. Done
Hmmm .... I tested this fix on serveral machines including 2 rhel4 ones and even a couple with firefox-2 and they all worked ok.
Not sure what the difference was on that end (that is ... what things you might be running or not running that effected the situation).
On Sun, 2007-02-25 at 15:23 -0600, Johnny Hughes wrote:
On Sun, 2007-02-25 at 15:37 -0500, P Marvin Eberly wrote:
On Sun, 2007-02-25 at 15:29 -0500, William L. Maltby wrote:
On Sun, 2007-02-25 at 15:24 -0500, P Marvin Eberly wrote:
<snip>
There is a fix that works as a work around until another solution is done, which is to create this symbolic link:
cd /usr/lib
ln -s firefox-1.5.0.10/libfreeb13.so .
Having libfreeb13.so in /usr/lib allows evolution to start ... removing it prevents it from starting.
Sorry guys, this didn't fix it here. What is the proper way to undo this link I made?
cd /usr/lib rm libfreeb13.so
Thanks, Bill. Done
Hmmm .... I tested this fix on serveral machines including 2 rhel4 ones and even a couple with firefox-2 and they all worked ok.
Not sure what the difference was on that end (that is ... what things you might be running or not running that effected the situation).
For anyone having a problem with a symlink ... copying the file into /usr/lib works as well.
On Sun, 25 Feb 2007 16:34:09 -0600, Johnny Hughes wrote:
On Sun, 2007-02-25 at 15:23 -0600, Johnny Hughes wrote:
On Sun, 2007-02-25 at 15:37 -0500, P Marvin Eberly wrote:
On Sun, 2007-02-25 at 15:29 -0500, William L. Maltby wrote:
On Sun, 2007-02-25 at 15:24 -0500, P Marvin Eberly wrote:
><snip> There is a fix that works as a work around until another solution is done, which is to create this symbolic link:
cd /usr/lib
ln -s firefox-1.5.0.10/libfreeb13.so .
Having libfreeb13.so in /usr/lib allows evolution to start ... removing it prevents it from starting.
Sorry guys, this didn't fix it here. What is the proper way to undo this link I made?
cd /usr/lib rm libfreeb13.so
Thanks, Bill. Done
Hmmm .... I tested this fix on serveral machines including 2 rhel4 ones and even a couple with firefox-2 and they all worked ok.
Got it! Folks, it is not libfreeb13.so but libfreebl3.so (the letter l, not number 1).
[OT] Hey, Johnny, you mentioned earlier that if you could type you would be dangerous. So, this is what you meant... :-) :-)
Akemi - always your fan.
On Sun, 2007-02-25 at 16:01 -0800, Akemi Yagi wrote:
On Sun, 25 Feb 2007 16:34:09 -0600, Johnny Hughes wrote:
On Sun, 2007-02-25 at 15:23 -0600, Johnny Hughes wrote:
On Sun, 2007-02-25 at 15:37 -0500, P Marvin Eberly wrote:
On Sun, 2007-02-25 at 15:29 -0500, William L. Maltby wrote:
On Sun, 2007-02-25 at 15:24 -0500, P Marvin Eberly wrote:
> ><snip> > There is a fix that works as a work around until another > solution is done, which is to create this symbolic link: > > cd /usr/lib > > ln -s firefox-1.5.0.10/libfreeb13.so . > > Having libfreeb13.so in /usr/lib allows evolution to start ... > removing it prevents it from starting. Sorry guys, this didn't fix it here. What is the proper way to undo this link I made?
cd /usr/lib rm libfreeb13.so
Thanks, Bill. Done
Hmmm .... I tested this fix on serveral machines including 2 rhel4 ones and even a couple with firefox-2 and they all worked ok.
Got it! Folks, it is not libfreeb13.so but libfreebl3.so (the letter l, not number 1).
[OT] Hey, Johnny, you mentioned earlier that if you could type you would be dangerous. So, this is what you meant... :-) :-)
Akemi, thank you for figuring this out. This fixes the problem on my one machine and I suspect it will on the second also.
This list rocks!
P Marvin Eberly
On Sun, 2007-02-25 at 19:16 -0500, P Marvin Eberly wrote:
On Sun, 2007-02-25 at 16:01 -0800, Akemi Yagi wrote:
On Sun, 25 Feb 2007 16:34:09 -0600, Johnny Hughes wrote:
On Sun, 2007-02-25 at 15:23 -0600, Johnny Hughes wrote:
On Sun, 2007-02-25 at 15:37 -0500, P Marvin Eberly wrote:
On Sun, 2007-02-25 at 15:29 -0500, William L. Maltby wrote:
On Sun, 2007-02-25 at 15:24 -0500, P Marvin Eberly wrote: > > ><snip> > > There is a fix that works as a work around until another > > solution is done, which is to create this symbolic link: > > > > cd /usr/lib > > > > ln -s firefox-1.5.0.10/libfreeb13.so . > > > > Having libfreeb13.so in /usr/lib allows evolution to start ... > > removing it prevents it from starting. > Sorry guys, this didn't fix it here. What is the proper way to > undo this link I made?
cd /usr/lib rm libfreeb13.so
Thanks, Bill. Done
Hmmm .... I tested this fix on serveral machines including 2 rhel4 ones and even a couple with firefox-2 and they all worked ok.
Got it! Folks, it is not libfreeb13.so but libfreebl3.so (the letter l, not number 1).
[OT] Hey, Johnny, you mentioned earlier that if you could type you would be dangerous. So, this is what you meant... :-) :-)
Akemi, thank you for figuring this out. This fixes the problem on my one machine and I suspect it will on the second also.
This list rocks!
I forgot to mention that I did add a note to point this out on the bug ticket.
Akemi Yagi wrote:
On Sun, 25 Feb 2007 16:34:09 -0600, Johnny Hughes wrote:
On Sun, 2007-02-25 at 15:23 -0600, Johnny Hughes wrote:
On Sun, 2007-02-25 at 15:37 -0500, P Marvin Eberly wrote:
On Sun, 2007-02-25 at 15:29 -0500, William L. Maltby wrote:
On Sun, 2007-02-25 at 15:24 -0500, P Marvin Eberly wrote:
>> <snip> >> > There is a fix that works as a work around until another > solution is done, which is to create this symbolic link: > > cd /usr/lib > > ln -s firefox-1.5.0.10/libfreeb13.so . > > Having libfreeb13.so in /usr/lib allows evolution to start ... > removing it prevents it from starting. > Sorry guys, this didn't fix it here. What is the proper way to undo this link I made?
cd /usr/lib rm libfreeb13.so
Thanks, Bill. Done
Hmmm .... I tested this fix on serveral machines including 2 rhel4 ones and even a couple with firefox-2 and they all worked ok.
Got it! Folks, it is not libfreeb13.so but libfreebl3.so (the letter l, not number 1).
[OT] Hey, Johnny, you mentioned earlier that if you could type you would be dangerous. So, this is what you meant... :-) :-)
Akemi - always your fan.
Color me abnormally stupid. It didn't work for me and I finally resorted to # find / -name libfreeb* and pasted the absolute path, "/usr/lib/firefox-1.5.0.10/libfreebl3.so" to do the symlink without ever noticing the ell/one ambiguity.
Thanks to all!
On Sun, 2007-02-25 at 15:23 -0600, Johnny Hughes wrote:
On Sun, 2007-02-25 at 15:37 -0500, P Marvin Eberly wrote:
On Sun, 2007-02-25 at 15:29 -0500, William L. Maltby wrote:
On Sun, 2007-02-25 at 15:24 -0500, P Marvin Eberly wrote:
<snip>
There is a fix that works as a work around until another solution is done, which is to create this symbolic link:
cd /usr/lib
ln -s firefox-1.5.0.10/libfreeb13.so .
Having libfreeb13.so in /usr/lib allows evolution to start ... removing it prevents it from starting.
Sorry guys, this didn't fix it here. What is the proper way to undo this link I made?
cd /usr/lib rm libfreeb13.so
Thanks, Bill. Done
Hmmm .... I tested this fix on serveral machines including 2 rhel4 ones and even a couple with firefox-2 and they all worked ok.
Not sure what the difference was on that end (that is ... what things you might be running or not running that effected the situation).
Well to be honest I have not tried the link fix on the second machine. If I get time I may give it a shot there although I've done about enough of the update/rollback thing for one day :)
P Marvin Eberly
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Akemi Yagi -
eberlyml＠wjtl.net -
Johnny Hughes -
Matt Hyclak -
Matthew Miller -
P Marvin Eberly
-
Robert -
Stephen John Smoogen -
William L. Maltby