Eberhard Roloff wrote:
> drek wrote:
>> Hi,
>>
>> Using openSUSE 10.3 32bit.
>>
>> I've got 2 problems:
>> 1. Since this morning when I start firefox 2.0.0.8, it closes
>> immediately and gives the following error:
>> /usr/bin/firefox: line 208:  4355 Segmentation fault      $MOZ_PROGRAM "$@"
>> I uninstalled ATI fglrx rpm's, then firefox started normally. I closed
>> firefox, and the 2nd time I started firefox I got again the above message.
> 
> fglrx (or not) has nothing to do with firefox working or not. Firefox
> just needs a local (or remote) working X where it can display (or not).
> 
> To check, you could uninstall and reinstall firefox.
> 
> 
> 
> Alternatively, I would download the firefox tarball from mozilla,
> extract the tarball and move it to /opt. Then try /opt/firefox/firefox
> and see what happens.
> 
> Furthermore I would move ~/.mozilla away, to ~/.mozilla.org and see what
> happens.
> 
> or you try to start firefox in safe mode
> "firefox -safe-mode"
>> 2. konqueror 3.5.7. works, but every link I click, I get the message
>> (e.g.):
>> Open 'http://www.google....oogle+zoeken&meta='? Type: HTML Document
>> ,with three options: Save as...; Open with 'firefox'; Cancel;
>> Clicking every link with my scrollwheel opens a new konqueror window and
>> displays the new page.
> 
> very strange things.....
>> Does anybody know a solution?
for checking whether this is "standard" on your install, you could
either configure another, not yet existing user and see whether she
experiences the same things, or you could temporarily .kde/ to something
like .kde.org/, restart kde and see what your konqui does.

In all honesty, I never experienced things like this in more than three
years of KDE and firefox. So if anything else fails, you might try it
the "microsoft way" and do a new install from scatch. If you do not like
that, some space on your hardisk permitted, you could try  to install a
full suse into one directory via "install into a directory" (or similar)
with Yast/Software Management.

After that you can chroot into that directory and start from there.

If you  happen to be using a second linux computer with X running, I
would also try to see whether the problem disappears, if X is running
elsewhere.
You either need to temporarily disable your firewall on the faulty
machine or allow ssh access via the Yast/Security/Firewall settings.

Do from an xterm on this second machine:
1.
ssh -X [EMAIL PROTECTED]

2.a.
firefox

2.b.
konqueror

sorry, I am running out of ideas.

good luck
Eberhard

-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to