Okay, I ‘one clicked’ :-).
Now OS boots to KDM login, I put in credentials and it starts to load KDE
splash then goes to a black screen with pop-up.
‘Could not start kdeinit4. Check your installation.’
Pressing ‘okay’ button dumps me back to KDM or hangs at a black screen.
Where to start?
I’d use yast from either a console or via Gnome (if you have it installed) to double check the repository (should be factory) and update packages. Even if no updates are available, you may want to select the KDE4 repo specifically, and have Yast update all packages unconditionally (which will basically force a re-install).
I had that happen once during the earlier 4.2 days in /UNSTABLE, but forcing a reinstallation fixed it.
Not saying that will solve it, but it might be worth a shot?
Cheers,
KV
I’m not a big fan of OneClick. You never know what you are getting.
You might find you can run yast from outside X
CLI login to level3 and doing ‘yast’ as su from the CLI will give you a basic no mouse yast.
You could try level 5 ‘yast2’
it may be ok
Check you don’t have any old 4.1.3 repo’s or other conflicting stuff.
some have been doing a rename of the .kde4
but I have not had to do that for quite some time
The times I’ve had that error pop up was because I had the wrong version of (or had unintentionally uninstalled) either kdebase or kdelibs. Very fixable through yast though. Good luck.
> The times I’ve had that error pop up was because I had the wrong version
> of (or had unintentionally uninstalled) either kdebase or kdelibs. Very
> fixable through yast though. Good luck.
I’ve loaded into iceWM and cranked up yast in a console window.
I am seeing this:
kdelibscover requires kde4-filesystem >=4.2.0 but this requirement cannot be
provided.
compiz-kde4 requires libplasma.so.2 but this requirement cannot be provided.
kde4-kio_sysinfo-11.1-66.4.i586 requires kdebase4-runtime < 4.1.60 but this
requirement cannot be provided.
It said I could uninstall kdenewsticker…that got rid of the kdelibscover
problem.
Then it said I could uninstall compiz…that got rid of the compiz error
(not really an issue since I run in a VM without effects)
The final one I told it to ignore…it’s updating now.
Maybe I can repair it further after this go around.
> Maybe I can repair it further after this go around.
I have now booted into KDE 4.2 proper and am in YaST again.
Told it to update packages ALL if newer version is available.
It’s loading up another 400MB + of stuff now.
I don’t have the least idea of why this should work, but when I used yast to install 4.2 I got a load of dependency problems. Not changing anything, a little later a tried zypper ref and zypper up. KDE 4.2 installed without any problems. I did zypper up twice and it found things both times. But, it worked.
>>I don’t have the least idea of why this should work, but when I used
> yast to install 4.2 I got a load of dependency problems. Not changing
> anything, a little later a tried zypper ref and zypper up. KDE 4.2
> installed without any problems. I did zypper up twice and it found
> things both times. But, it worked.
Odd isn’t it. <shrug>
I had a lot of problems out of one click, for one I already had the QT4 and
11.1_FACTORY repos inserted. It totally barfed on that. So I removed
those two and kicked it off again. It ran through with no errors but ended
up as I described initially. Loaded iceWM and kicked off yast in a console
ran update all if newer package exists got those few errors I described but
was then able to boot into 4.2. Run Yast inside of 4.2 and get another
400MB of stuff…%-) Wacky.