2 browser problems(1 common with Firefox)

First of all, I have to say, today is the first day I dove into openSUSE and it certainly blew.me.away. I’m no Linux savant, but for the past 3 months I’ve had very little trouble getting various distros to run by just googling around and playing with terminals, and with oS all I had to do was look up the repository URLs to get myself up to speed! I’ve been excited all day about this, haha.

So now I’m pretty sure I’ve made a permanent switch (now if only I could get Adobe CS5 to run…) and I’m quite satisfied so far.

But, there’s been 2 nagging issues today. And as you can see, they’ve kept me up until daylight.

First, I installed the proprietary ATI drivers (I decided to switch to the open source drivers later, but…I couldn’t find the repo anymore >.<) and it’s been pretty great. I think. Gecko browsers have issues with unruly black bars, unfortunately.

So Konqueror and other browser substitutes have managed just fine without these issues. But I can’t live without my Firefox add-ons. I’m sorry >.> I thought about importing my bookmarks and stuff from FF but I’m not really in the mood to acclimate to a new browser right now, not while I’m trying to adjust to the new OS finally.

Anyway, Seamonkey does the same thing. At least, I’m pretty sure it does. I know it’s happened once upon starting up the application, BUT I can’t open up almost any webpage without the browser crashing instantly and silently. As in, I go to AMO and CRASH! No error messages of any sort. The window just vanishes, more or less, taking its process and tray bar with it.

I believe the black bars are associated with the drivers, and I’m pretty sure the SM crash is not, but I’ll let you experts be the judge of that =D

Thanks in advance for reading my wall of text >.<

What does your konsole say, when you start and crash firefox from konsole?

I assume you mean Seamonkey, as FF doesn’t crash.

*** nss-shared-helper: Shared database disabled (set NSS_USE_SHARED_DB to enable).
Attempting to load the system libmoon
/usr/bin/seamonkey: line 130: 10962 Segmentation fault $MOZ_PROGRAM “$@”

Apparently I’m incapable of editing posts as well, so I’ll just reply to it for revision’s sake. Hope you’re using threaded views!

Anyway, I forgot to mention these things.

I’m on oS 11.3, KDE 4.4.4 (if I recall correctly), and am using the latest stable builds from Mozilla repo.

Make sure you did this
ImageBam - Fast, Free Image Hosting and Photo Sharing

Yes, I’ve done that. It hasn’t helped with Seamonkey; still crashes on almost any pageload aside from the default homepage. Thanks though, I’m gonna be a nubbybutt and try that with a few of my repos to see what happens >.>

Maybe you should post your list

zypper lr -d

| Alias | Name | Enabled | Refresh | Priority | Type | URI | Service

—±------------------------------------±------------------------------------±--------±--------±---------±-------±--------------------------------------------------------------------------------±-------
1 | ATI Repository | ATI Repository | Yes | Yes | 99 | rpm-md | http://www2.ati.com/suse/11.3 |
2 | Java | Java | Yes | Yes | 99 | rpm-md | Index of /repositories/Java:/packages/openSUSE_11.3 |
3 | KDE_Extras | KDE Extras | Yes | Yes | 99 | rpm-md | Index of /repositories/KDE:/Extra/openSUSE_11.3 |
4 | KDE_Updated_Apps | KDE Updated Apps | Yes | Yes | 99 | rpm-md | Index of /repositories/KDE:/UpdatedApps/openSUSE_11.3 |
5 | KDE_core | KDE core | Yes | Yes | 99 | rpm-md | Index of /repositories/KDE:/Distro:/Stable/openSUSE_11.3 |
6 | Mozilla | Mozilla | Yes | Yes | 99 | rpm-md | Index of /repositories/mozilla/openSUSE_11.3 |
7 | OpenOffice | OpenOffice | Yes | Yes | 99 | rpm-md | Index of /repositories/OpenOffice.org:/STABLE/openSUSE_11.3 |
8 | Packman | Packman | Yes | Yes | 99 | rpm-md | Index of /suse/11.3 |
9 | Semi-official_repos | Semi-official repos | Yes | Yes | 99 | rpm-md | Index of /repositories/openSUSE:/11.3:/Contrib/standard |
10 | Updates for openSUSE 11.3 11.3-1.82 | Updates for openSUSE 11.3 11.3-1.82 | Yes | Yes | 99 | rpm-md | Index of /update/11.3 |
11 | VideoLAN | VideoLAN | Yes | Yes | 99 | rpm-md | Index of /pub/vlc/SuSE/11.3/ |
12 | WINE | WINE | Yes | Yes | 99 | rpm-md | Index of /repositories/Emulators:/Wine/openSUSE_11.3 |
13 | openSUSE-11.3 11.3-1.82 | openSUSE-11.3 11.3-1.82 | Yes | No | 99 | yast2 | cd:///?devices=/dev/sr0 |
14 | repo-debug | openSUSE-11.3-Debug | No | No | 99 | NONE | Index of /debug/distribution/11.3/repo/oss |
15 | repo-non-oss | openSUSE-11.3-Non-Oss | Yes | No | 99 | yast2 | Index of /distribution/11.3/repo/non-oss |
16 | repo-oss | openSUSE-11.3-Oss | Yes | No | 99 | yast2 | Index of /distribution/11.3/repo/oss |
17 | repo-source | openSUSE-11.3-Source | No | No | 99 | NONE | Index of /source/distribution/11.3/repo/oss |

It’s not too bad, right?

As you can see, I am yet to set my auto-refresh on most of these. And I was lazy in my choosing, so I didn’t check for conflicts yet…so be nice, this time, please >.>

Well the Firefox problem appears to be handled now, thanks to the repo fix.

Unfortunately Seamonkey just crashes, without bias, on any site but google.

Not that it matters to SM but you should remove repo 11
See my guide here: Multi-media and Restricted Format Installation Guide

You could try a new SM profile

okie. I was using it to make sure I stay current with stable VLC releases, but you’re the expert here. I’ll just add it again later or check my other repos if I’m not getting the updates as expected.

Aaaaaaaand, I’m stunned. I created a new SM profile and went straight for the throat by going to AMO just to watch it crash again. But no! It lived! How does that make sense? I don’t get it, but that’s cool.

Funny story though. The black bars are all gone. Now I get lots of WHITE ones instead. Well, it’s more like some of the webpages are blank, white, clean slates. Then I can either mouse over various elements of the page and then a large block will be filled in with the page elements, or I can refresh to fix the whole thing. Scrolling around also tends to recover some of the page, as does highlighting.

And finally, should I continue to use this thread to ask a few more questions not really related to my browser problems, or is it appropriate protocol to open a new thread to handle a new problem?

New and different problem = New thread

Thanks, I’ll hold off for now and wait until this issue gets resolved so I don’t split my focus unfavorably.

The black bars have mutated into white, but other than that they seem to act exactly the same as the black ones.

try adding a new user and see if that user has the same problem. If not then we know it is a bad configuration file somewhere.

yeah, still got black/white bars obfuscating everything

All I can suggest is remove these repos: 2, 7, 11,
Change the priority of Packman to 10

then do as su -

zypper dup

Okay then, seems to have fixed the issue. Thanks much. I’ll check back again if something goes awry.

Thanks again!

Okay good luck…