On Mon, 2012-04-30 at 21:00 +1000, Basil Chupin wrote:
On 30/04/12 20:38, Mark Misulich wrote:
On Mon, 2012-04-30 at 20:09 +1000, Basil Chupin wrote:
On 30/04/12 19:49, Mark Misulich wrote:
[.........]
Hi, I had this problem after doing a zypper dup and solved it by doing the following.
I logged in to IceWM instead of KDE. I started yast> software management> kernel. I downgraded my kernel and rebooted. I selected KDE at the login screen and KDE started right up.
Once I was back in KDE, I started yast> software management> kernel and upgraded the kernel. Then I rebooted into the new kernel and KDE without problem. The use of another DE is most interesting and something which was already suggested Phanisvara. It sounds like a very good idea to have a standby DE available.
But you don't say which kernel you were running at the time and to which kernel you downgraded. I am only using the kernel which was installed by default and have not upgraded it (like I did do when running the 32-bit version where I was running version 3.3.x of the kernel). So, which version did you downgrade to when you came across this problem?
BC
-- The wise man does at once what a fool does finally. Niccolo Machiavelli
The kernel that was originally installed was the kernel that was installed in a fresh install. I think the kernel that yast upgraded to in the first system update was 3.1.10 something. I downgraded to the next lower kernel in the versions list, whatever it was, maybe 3.1.9. Once KDE was back up and running, I went back to the highest version available, maybe 3.1.10.
OK, I didn't pay attention to what was originally installed but the present kernel is 3.1.10.
I think the problem may be that the software updates aren't installing correctly to the kernel, but installing the kernel to the updates works. Hence, the kernel version isn't so important as installing the kernel to the updates.
WHOA! to the that last statement :-) . That is what YaST is supposed to do and what zypper is supposed to do - install the correct versions to fit what is being used on the system. The whole thing is called "dependency" thing :-) . I don't ever recall doing an installation/update/upgrade of anything which used the parameter "force".
OK, so I am about ready to try to install KDE 4.8.2 once again - after doing some backups of the ~/.mozilla and /.thunderbird directories.
Here goes nothing.........
BC
-- The particular zypper dup that I did that gave me the problem was to try to install kde 4.8 to a fresh OS12.1 install. The method that I detailed above fixed it and got the whole thing working again with kde 4.8. I hope and expect that it will work for you too.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org