Announcement

**dibl** · Oct 27, 2009, 08:10 AM

Re: Krazy KDE in Koala

Couple of thoughts ...

- 9.10 is the first version released with Grub2. Grub2 is not exactly "well-developed" in IMHO -- it failed to auto-detect and set up my second OS, for example, and I reverted to legacy Grub for my dual-OS system. So, I'm thinking this 9.04 - 9.10 transition may NOT be the one to use the "upgrade" button on, for that very reason.

- I do recognize the errors from the Nvidia driver -- it's been a long time since I've seen those, but there was a period when the two named modules were on a wrong path in xorg.conf. You might want to re-install the driver, and then run sudo nvidia-xconfig and let it write a new xorg.conf file, and see if that solves those errors. Alternatively, if you go into /etc/X11/xorg.conf and comment out the lines that call for those two modules, that might eliminate the errors as well.

HTH

**MidnightVelvet** · Oct 27, 2009, 08:27 AM

Re: Krazy KDE in Koala

Originally posted by dibl

Couple of thoughts ...

- 9.10 is the first version released with Grub2. Grub2 is not exactly "well-developed" in IMHO -- it failed to auto-detect and set up my second OS, for example, and I reverted to legacy Grub for my dual-OS system. So, I'm thinking this 9.04 - 9.10 transition may NOT be the one to use the "upgrade" button on, for that very reason.

I could be nutso, but I think I read somewhere that the 'upgrade' doesn't switch to grub2 for all the wonkyness it ca cause. I also have Win7 on this machine and it'll dual boot okay at least from a boot perspective. But you may be right on the upgrade bit in general *grins*

- I do recognize the errors from the Nvidia driver -- it's been a long time since I've seen those, but there was a period when the two named modules were on a wrong path in xorg.conf. You might want to re-install the driver, and then run sudo nvidia-xconfig and let it write a new xorg.conf file, and see if that solves those errors. Alternatively, if you go into /etc/X11/xorg.conf and comment out the lines that call for those two modules, that might eliminate the errors as well.

HTH

Yea, actually I went nuts. I completely uninstalled the Nividia Drivers, removed the packages and switched to the default VGA Drivers and it still had the same effect, at least as far as being unable to boot into KDE, and the runaway kbuildsycoca processes.

Thanks Much for the ideas though!

~MV

**mudlark** · Oct 27, 2009, 09:18 AM

Re: Krazy KDE in Koala

I had similar problems due to a programme not liking Mysql5.1 which is required for the akonadi server.

My symptoms were no kdm desktop, when booting into safe mode I got the kubuntu login screen then crash and a mouse cursor active but nothing else.

on the kubuntu login screen I checked the login options and there was no kde just default and safe mode.

I kept reinstalling kde using apt-get and eventually it started working. Now mysql is ok with the other programme 9.10 seems to be working well. My other programme is squeezebox server.

i am probably wrong, but you never know.

**sithlord48** · Oct 27, 2009, 01:18 PM

Re: Krazy KDE in Koala

i had a very similar issue with upgrading from 9.04 to 9.10 , i found what worked for me was a fresh install from the BETA/RC cd. i use a seperate partition for /home so i was not to worried about data loss on /home since i didn't format it durring install. after upgrading i couldn't get grub to load any kernel and just installed from cd at that point.

**LinuxRocks** · Oct 27, 2009, 02:08 PM

Re: Krazy KDE in Koala

As for the KDE issue, you could try ctrl+alt+f1'ing into a terminal, logging in as your account and mv'ing .kde to .kde_old and letting it reset all the settings. Its a pain to reconfig KDE, but better then a fresh install if it all works out.

Just a thought!!!

Joe

**MidnightVelvet** · Oct 27, 2009, 04:12 PM

Re: Krazy KDE in Koala

Originally posted by LinuxRocks

As for the KDE issue, you could try ctrl+alt+f1'ing into a terminal, logging in as your account and mv'ing .kde to .kde_old and letting it reset all the settings. Its a pain to reconfig KDE, but better then a fresh install if it all works out.

Just a thought!!!

Joe

Yea, did that. In fact I created a brand new account and tried logging in to that one fresh... Still same problem oddly enough.

~MV

**MidnightVelvet** · Oct 27, 2009, 04:14 PM

Re: Krazy KDE in Koala

Originally posted by sithlord48

i had a very similar issue with upgrading from 9.04 to 9.10 , i found what worked for me was a fresh install from the BETA/RC cd. i use a seperate partition for /home so i was not to worried about data loss on /home since i didn't format it durring install. after upgrading i couldn't get grub to load any kernel and just installed from cd at that point.

Yea think this is what I may end up doing, although might as well wait until 'release' for all it matters. So I figured I'd pick brains until then to find that miracle cure *grins* Besides, e17 is still working great, and that's my preferred environment... I just like having a backup for when the compile from svn dies horribly...

More than that though I'm concerned about the rogue process, wondering why it's doing so, so i'm wondering if I should stick with KDE or just go to the Gnome version (since it doesn't use the KDE Cacheing bits).

I really don't like gnome though *wrinkles nose*

~MV

**fermier** · Oct 28, 2009, 03:40 AM

Re: Krazy KDE in Koala

I know that I shall be flamed or flogged or both for saying this, but I never trust the upgrade process. (I know there will be 1000's that will tell me next how wonderful it has worked for them, but I have always and consistantly had problems whenever I tried the upgrade route). I therefore, always insist on performing an new installation and then recovering my data and configurations one by one. I even export the list of installed programs beforehand so that it is easy to reinstall them all from the list in one simple command afterwards and even then I find difficulties, as some programs as discontinued between two successive versions. It is a big schlepp to do, but at least you stay on top of all the problems that can arrive and resolve them one at a time. Even if the upgrade process works, you will sometimes find that some individual programs that you used in the past have changed their configuration file formats so that they are no longer compatible with the previous configuration files. Painful!

As far as your problem is concerning, just another shot in the dark, try deleting the file .ICEauthority in your home directory with sudo rm .ICEauthority and then do a reboot

or do a

sudo chmod 777 /home/toi/.ICEauthority

I do not guarantee that this will solve your problem at all.

**MidnightVelvet** · Oct 28, 2009, 09:02 AM

Re: Krazy KDE in Koala

Originally posted by fermier

I know that I shall be flamed or flogged or both for saying this, but I never trust the upgrade process. (I know there will be 1000's that will tell me next how wonderful it has worked for them, but I have always and consistantly had problems whenever I tried the upgrade route). I therefore, always insist on performing an new installation and then recovering my data and configurations one by one. I even export the list of installed programs beforehand so that it is easy to reinstall them all from the list in one simple command afterwards and even then I find difficulties, as some programs as discontinued between two successive versions. It is a big schlepp to do, but at least you stay on top of all the problems that can arrive and resolve them one at a time. Even if the upgrade process works, you will sometimes find that some individual programs that you used in the past have changed their configuration file formats so that they are no longer compatible with the previous configuration files. Painful!

Interesting Opinion, really! I started using Kubuntu after running Debian for eons (still do for server machines) and it's never given me the slightest lick of a problem from upgrading releases. Even when I was running Sid it worked quite well... most of the time *grins*

It's interesting to see some folks don't quite have the same sorta results with a Debian based distro... huh

As far as your problem is concerning, just another shot in the dark, try deleting the file .ICEauthority in your home directory with sudo rm .ICEauthority and then do a reboot

or do a

sudo chmod 777 /home/toi/.ICEauthority

I do not guarantee that this will solve your problem at all.

Yea, did that too, and circumvented that by trying to log in with a brand spankin new user, but thank you!

~MV

Announcement

Krazy KDE in Koala

Krazy KDE in Koala

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment