In all honesty, your repo list is a mess. You seem to have duplicates, though it is somewhat hard to read.
Since you have packman, you do not need packman-essentials. That’s just redundant.
The most important repos are the standard Tumbleweed ones and packman. Those appear to be #32, #36, #38, #33 on your list.
I suggest that you disable everything else, and then run “zypper dup”. That should get you back to a stable system. After that, you will have to work out which of those other repos you really need and selectively re-enable those. At present, you are apparently picking up conflicting libraries from some of them, causing your problems.
I removed all repos using zypper rr
Then I added the six repos suggested (OSS, Non OSS, Update, SRC OSS. SRC NON OSS, and Debug Tumbleweed versions) prior to performing zypper dup
I did a restart…Still getting same error meassages when starting firefox and surf brower
From the free bsd board I found this…suggests that problems I am seeing could be due to javascript in the gtk browsers (surf and firefox)…
"Searched in the compilation instuction of Arch Linux arm’s PKGBUILD and there was a comment about “–disable-jit”. This comment said that is necessary to disable JIT because segmentation fault.
In recent test I found that it was the web pages with javascript that crashed the browser.
I have built webkitgtk from port after modify the Makefile to include this option ("–disable-jit"). And after reinstallation, vimb works ! (and probably all others webkitgtk based web browser like midori, surf, etc.)"
[size=2]Problem: I am a Noob…I do not know how to disable-jit Do I need to do that in webkitgtk makefile or in the makefile of surf browser. How do I disable-jit (what code do I need to add and where do I add it and to which make file???
Can someone help me with this…Thanks in advance…[/size]
First,
Your question about jit would apply only if you compiled your web browsers from source.
I assume you’re not doing that, you’re installing pre-compiled applications from a repository.
As for re-installing,
You can do that and keep your home directory…
First, copy your entire /home directory somewhere for safekeeping in case you make a mistake. A direct attached external hard drive would be a good choice.
Using a partition editor (YaST has one), inspect your partitions. If you installed the default layout (accept defaults during installation), your partitions should be
sda swap
sdb root
sdc home
Whatever you see, write it down if you must.
The next step is to reboot to a partition editor where you will remove the partitions containing your swap and root partitions. You can boot to a command line and run fdisk. If you prefer to use a graphical tool, I recommend GParted Live.
With the swap and root partitions removed (They should be free, unfornatted soace), insert your Installation DVD and run until you’re prompted to install the Default Layout. Instead, select the Advanced Guided, somewhere in there you will be offered the Parted tool where you can set /home to your existing partition instead of creating new. Or, if this gets messed up it will only mean that you’ll create a new /home partition and then you can copy or move everything from your original partition into your new /home partition.
I wouldn’t be so quick to do a complete re-install yet, though…
You can also try using a DVD to “repair” your system, you can either run the regular repair or try to do an “upgrade” which is more or less similar to what you were trying to do by running “zypper dup.” There is a fair chance using the DVD will fix your problems, and as long as the DVD isn’t older than a couple months, it should be OK.
Keeping the home partition should be fine. I normally do that.
If you still have problems, then just remove the configuration part:
cd
rm -rf .config
rm -rf .local
rm -rf .mozilla ## this is the one with firefox configuration.
If you remove any of those directories, it is best to not be logged into your desktop. Just login temporarily to Icewm which doesn’t use those directories (unless you start an application which uses them).
Your question about jit would apply only if you compiled your web browsers from source.
I assume you’re not doing that, you’re installing pre-compiled applications from a repository.
a couple months, it should be OK.
TSU
I am most interested in getting surf browser to work which is a suckless app…it is compiled from source…so my question about jit removal is valid
TSU…you said:
Your question about jit would apply only if you compiled your web browsers from source.
I assume you’re not doing that, you’re installing pre-compiled applications from a repository.
a couple months, it should be OK.
I am most interested in getting surf browser to work which is a suckless app…it is compiled from source…so my question about jit removal is valid