I have installed SuSE 8.1 onto two machines which had been running 8.0. One was via upgrade and the other was fresh install. Both Installations went very well, however on the upgraded machine Opera refused to start. It had been working for months before the upgrade. I have reinstalled Opera and it still refuses to run. The fresh install also will not run Opera. On the upgrade install I have re-installed both the static and the shared rpm versions of Opera. Neither will fire up. Konqueror and Mozilla both will start and access the web. Has anyone else seen this problem?Next I will try to compile it from source, but the rpm's have been reliable for the last year or so. Any suggestions? TIA Richard
On Wednesday 09 October 2002 4:07 am, Richard wrote:
I have installed SuSE 8.1 onto two machines which had been running 8.0. One was via upgrade and the other was fresh install. Both Installations went very well, however on the upgraded machine Opera refused to start. It had been working for months before the upgrade. I have reinstalled Opera and it still refuses to run. The fresh install also will not run Opera.
On the upgrade install I have re-installed both the static and the shared rpm versions of Opera. Neither will fire up.
Konqueror and Mozilla both will start and access the web. Has anyone else seen this problem?Next I will try to compile it from source, but the rpm's have been reliable for the last year or so. Any suggestions? TIA Richard
As usual, just when you give up after fooling with a problem all day, you find at least a partial solution. 5 minutes after I posted the above, I downloaded the Static rpm to the fresh install machine and damned if it doesnt work! However on the upgraded machine neither the static nor the shared version will work. Since that is my wife's machine, it has to work soon or I'm in big trouble. Any ideas?? BTW, the new YAST interface may not please the purists but to those used to the "other" OS's it is neat and intuitive especially when adding a new app via rpm. I also like the use of light blue colors instead of the green. While that may seem like a silly thing to think about, food folks have known for a long time that the right color sells the product. Lite blue is one of the more pleasant colors. Wouldnt the suse gekko look much better dressed in blue? ra
On Wed, 2002-10-09 at 11:36, Richard wrote: (...)
Since that is my wife's machine, it has to work soon or I'm in big trouble. (...)
This sounds very familiar to me !!! *gggg* Try the following, which worked for my wife :-) Rename the .opera folder to, lets say .opera_bck Then try restarting opera. There might be some crap in .opera which prevents opera from starting. If that fixed it, then find out the bookmark file in .opera_bck (forgot the name) and copy it to .opera If there are other files too, containing valuable settings, then copy them too. Finally delete .opera_bck Hope that helps .. Cheers .... Wolfi ============================================= mailto:wolfi_z@gmx.net Linux ... the better OS!
On Wednesday 09 October 2002 12:19 pm, wolfi wrote:
This sounds very familiar to me !!! *gggg*
Try the following, which worked for my wife :-) Rename the .opera folder to, lets say .opera_bck Then try restarting opera. There might be some crap in .opera which prevents opera from starting. If that fixed it, then find out the bookmark file in .opera_bck (forgot the name) and copy it to .opera If there are other files too, containing valuable settings, then copy them too. Finally delete .opera_bck
Hope that helps ..
It turns out something was amiss with kde after the upgrade. So I had it delete all kde stuff and reinstalled it. Aftereward it would take the Opera static version. No shared though which probably means something funny with qt. Now my wife (and I indirectly ) is happy. Thanks for the tip, I will tryi it on the laptop which is upgrading right now and will probably have the same problem. Richard
Opera statically linked works, but shared doesn't? Sounds like another gcc 3.2 issue. Does the shared version provide any usable error messages? - Herman On Wed, 9 Oct 2002, Richard wrote: ->On Wednesday 09 October 2002 12:19 pm, wolfi wrote: ->> This sounds very familiar to me !!! *gggg* ->> ->> Try the following, which worked for my wife :-) ->> Rename the .opera folder to, lets say .opera_bck ->> Then try restarting opera. There might be some crap in .opera which ->> prevents opera from starting. If that fixed it, then find out the ->> bookmark file in .opera_bck (forgot the name) and copy it to .opera ->> If there are other files too, containing valuable settings, then copy ->> them too. Finally delete .opera_bck ->> ->> Hope that helps .. ->> -> ->It turns out something was amiss with kde after the upgrade. So I had it ->delete all kde stuff and reinstalled it. Aftereward it would take the Opera ->static version. No shared though which probably means something funny with ->qt. ->Now my wife (and I indirectly ) is happy. ->Thanks for the tip, I will tryi it on the laptop which is upgrading right now ->and will probably have the same problem. ->Richard -> ->-- ->Check the headers for your unsubscription address ->For additional commands send e-mail to suse-linux-e-help@suse.com ->Also check the archives at http://lists.suse.com ->Please read the FAQs: suse-linux-e-faq@suse.com -> -> ->
On Wednesday 09 October 2002 1:17 pm, Herman L. Knief wrote:
Opera statically linked works, but shared doesn't? Sounds like another gcc 3.2 issue. Does the shared version provide any usable error messages?
- Herman
No, no error messages at all. The install seemed to go ok and the binary was in the proper location. It would act as if it was starting. I could see cpu activity for a few seconds then the cursor timed out and NOTHING. I have three more machines to install to so I expect I will see the same problem again. Richard
Do you have strace installed? If not, I'll run it this evening and see if it is actually the shared library issue. - Herman On Wed, 9 Oct 2002, Richard wrote: ->On Wednesday 09 October 2002 1:17 pm, Herman L. Knief wrote: ->> Opera statically linked works, but shared doesn't? Sounds like ->> another gcc 3.2 issue. Does the shared version provide any usable error ->> messages? ->> ->> - Herman ->> -> ->No, no error messages at all. The install seemed to go ok and the binary was ->in the proper location. It would act as if it was starting. I could see cpu ->activity for a few seconds then the cursor timed out and NOTHING. -> ->I have three more machines to install to so I expect I will see the same ->problem again. ->Richard ->
participants (3)
-
Herman L. Knief -
Richard -
wolfi