I am running OpenSuse 10.3 on a 64-bit system. I had evoulution and Firefox running on the system and unfortunately did an update to Firefox 3.5. When I attempted to use the browser, it displayed a blank page for any web site that I attempted to view. I tried going back to the 64 bit version of latest 3.0 version and got the same result. Moving from the 64 bit version of Firefox to the 32 bit version corrected the issue in the 3.0 version. Now when I attempt to start evolution it fails to start. Starting it from the command line gives the following error:
evolution-smime-WARNING **: Failed all methods for initializing NSS
Segmentation fault
I’ve tried reinstalling evolution and got the same result after deleting and reinstalling it. The version of Evolution installed is 2.12.0-5.8 x86-64. The version of Firefox installed is 3.0.12-0.1 i586. Firefox is not the x86-64 version because that version does not load any web pages.
> I am running OpenSuse 10.3 on a 64-bit system. I had evoulution and
> Firefox running on the system and unfortunately did an update to Firefox
> 3.5. When I attempted to use the browser, it displayed a blank page for
> any web site that I attempted to view. I tried going back to the 64 bit
> version of latest 3.0 version and got the same result.
It would have been better you to try with a clean firefox profile
(~/.mozilla) to test if that worked.
> Moving from the
> 64 bit version of Firefox to the 32 bit version corrected the issue in
> the 3.0 version. Now when I attempt to start evolution it fails to
> start. Starting it from the command line gives the following error:
>
> evolution-smime-WARNING **: Failed all methods for initializing NSS
> Segmentation fault
>
> I’ve tried reinstalling evolution and got the same result after
> deleting and reinstalling it. The version of Evolution installed is
> 2.12.0-5.8 x86-64. The version of Firefox installed is 3.0.12-0.1 i586.
> Firefox is not the x86-64 version because that version does not load
> any web pages.
I dunno, but mozilla firefox repo always install a package
named “mozilla-nss”. Maybe you messed up the packages when
changed/unistalled/reinstalled your firefox :-?
Yes, I’m sure that some package got changed by the Firefox 3.5 update. I’m not sure which one is damaged. Going back apparently does not correct the issue. Whatever package was changed incorrectly appears to be used by evolution. Would the mozill-nss be something that evolution is likely to encounter? Would you know where that package is installed on openSUSE 10.3?
> Thanks for the reply.
>
> Yes, I’m sure that some package got changed by the Firefox 3.5 update.
> I’m not sure which one is damaged. Going back apparently does not
> correct the issue. Whatever package was changed incorrectly appears to
> be used by evolution. Would the mozill-nss be something that evolution
> is likely to encounter?
I think so.
> Would you know where that package is installed
> on openSUSE 10.3?
Try to update firefox to the latest version available (yes, I know you
previously said it didn’t work, but we can solve the firefox problem
later).
Enable /mozilla repo and update it. Then, on software management, filter the
packages by repositories and select /mozilla. On the right column, right
click and choose “all of the list > update if a newer version is
available”.
Let’s hope after updating all the packages from here, the ones are now
failing come to live again
When I installed the 3.5 version of Firefox I got it from the openSuse/10.3/ repository. I chose the version suggested by YAST and as I recall it came from the build service repository.
I am relatively new to linux and I thought that the safest way to keep the system standard was to use versions that were in the openSuse repositories. Are you suggesting that I use a different repository? How do I go about enabling the /mozilla-repo?
Sorry if I am a little dense on how to go about these things, I am learning.
> When I installed the 3.5 version of Firefox I got it from the
> openSuse/10.3/ repository. I chose the version suggested by YAST and as
> I recall it came from the build service repository.
I also have openSUSE 10.3 installed and Firefox 3.5.2
Latest version of Firefox 3.5 is only available from /mozilla repo. I mean,
this one:
Is this the one you have enabled and you installed from? If yes, that’s O.K.
> I am relatively new to linux and I thought that the safest way to keep
> the system standard was to use versions that were in the openSuse
> repositories. Are you suggesting that I use a different repository?
> How do I go about enabling the /mozilla-repo?
Well, any package under OBS service or Community repositories are not directly supported by openSUSE and /mozilla repo falls under that
category.
The only packages which are fully supported (and patched when required)
are the ones that came with the stock distribution, that is, these ones:
I have uninstalled the 3.0 i586 version and enabled the mozilla repo that you specified. I uploaded the 3.5 x86_64 version from that repository and it installed several supporting packages (e.g. xulrunner) as well as the main package. I tried starting firefox and got the blank pages that I had before. I tried to start evolution and it did not start. I then tried to start evolution from the command line and got the same error message that I had before. I then tried to go back to the 3.0 x86_64 version and it behaved the same way (blank pages). This is the version that was working on this system before I began this episode, it is not working now. The only way that I could get firefox to show pages was to go to the i586 version again. Evolution is x86_64, so I am guessing that there is something in the x86_64 supporting structure that is preventing both firefox and evolution from working properly. Whatever it is, it seems that uninstalling the components of firefox and installing them from a different repo doesn’t fix the problem. Is there any way that I can find all of the files that were installed when I did the original update so that at least we can get a list of the suspects?
I can live with firefox 3.0 i586 but not having evolution working is a real problem since all my mail files are in that program.
I have disabled all the buildservice repos so that I can avoid problems like this in the future.
> I have uninstalled the 3.0 i586 version and enabled the mozilla repo
> that you specified. I uploaded the 3.5 x86_64 version from that
> repository and it installed several supporting packages (e.g. xulrunner)
> as well as the main package. I tried starting firefox and got the blank
> pages that I had before.
Already tested by starting firefox with a blank/empty profile?
> I tried to start evolution and it did not
> start.
Then you better open a bugzilla for this. Some packages can be wrong or just
interfere between the both applications.
> I then tried to start evolution from the command line and got
> the same error message that I had before. I then tried to go back to
> the 3.0 x86_64 version and it behaved the same way (blank pages). This
> is the version that was working on this system before I began this
> episode, it is not working now. The only way that I could get firefox
> to show pages was to go to the i586 version again. Evolution is x86_64,
> so I am guessing that there is something in the x86_64 supporting
> structure that is preventing both firefox and evolution from working
> properly. Whatever it is, it seems that uninstalling the components of
> firefox and installing them from a different repo doesn’t fix the
> problem. Is there any way that I can find all of the files that were
> installed when I did the original update so that at least we can get a
> list of the suspects?
I would suggest you to open a bug report as this “library mess” can also
happen to another users. Going back to previous versions could even
aggravate the situation.
> I can live with firefox 3.0 i586 but not having evolution working is a
> real problem since all my mail files are in that program.
>
> I have disabled all the buildservice repos so that I can avoid problems
> like this in the future.
These things happen, it is not a fault “per se” of the whole OBS
Updating packages (from whatever location/repo/obs) can break things, so
this has to be taken with care. Better approach is testing first with a
virtual machine, if the main computer is in production and is important to
get it working.
Where is the proper place to file a bugzilla since this appears to be the result of the update in the openSuse 10.3 build service repository? I’m not sure that the trouble would apply to all of mozilla, so how can the trouble report be properly focused?
> Where is the proper place to file a bugzilla since this appears to be
> the result of the update in the openSuse 10.3 build service repository?
> I’m not sure that the trouble would apply to all of mozilla, so how can
> the trouble report be properly focused?
Use the Novell bugzilla.
It’s “the facto” method to handle such issues, even those coming from OBS
packages. OBS packages are not “officially” supported but they can be fixed
by its packagers and maintainers.
You will need to open an account, though. Basically, e-mail and password and
the only required fields.
> I have posted a message here
>
> ‘openSUSE Mailinglist Archives: opensuse-factory-mozilla - all
> messages’
> (http://lists.opensuse.org/opensuse-factory-mozilla/2009-08/all.html)
>
> several days ago, but there has been no response to even indicate that
> it has been received.
Well, that list is mainly for Factory development, not for errors on
openSUSE 10.3 packages
