Heh, I've avoided the last update so far... given the postings of problems...

I'm still running the first 3.4 install w/o any problems on two machines...

I may try it tomorrow though...

The permissions issue is a good idea...

e.g.

cd ~/

find . -exec chown NAMEOFUSER {} \;
find . -exec chgrp NAMEOFUSER {} \;

As typed above except for "NAMEOFUSER".

Remember that KDE sometimes has problems with config files from prior versions as well.

What I have done so far is to somehow get my menus working after a lot of tiknering yesterday. I'm stil using the mdkkdm instead of kdm. I saw on the mandrakeusers.org some recommendations if the menus do not work so I tried that too..

I'm still mising drakconf, kcontrol entries in the menu even though the when I go to menudrake I can still see them...

davcefai: Thanks - I installed RC1 of 10.2. I'm trying to figure out how not to use mdkkdm at the moment.

Samantha

sammigirl: go into mandrake control center.... system... display manager and change it.....

xavierh: Thanks. I did that and selected GDM. My only choices are mdkkdm, XDM, and gdm.

I have read by opjose that I shouldn't use mdkkdm, but is there a better one when it comes to XDM or GDM?

Thanks for all your help.

Samantha

I have as an option mdkkdm, kdm xdm. I'm still using mdkkdm. see if you can install the kdm using urpmi. I posted the same question on mandrakeusers.org forums (same username). They have a lot of pointers there and thcs actually posts his messages there.

I can deal with the mdkkdm issue since my machine is always on. I would like to know how to solve the menu issue that I still have: If I install a new piece fo software using urpmi, after the installaiton has been completed, its menu entry does not appear automatically. I have to do a update-menus command to make sura that happens.

I would like to get that fixed and I'll be golden...

any news on this issues?

Thanks for the input. I've been out and about most of the day. Will check in various places.

Sorry to throw things off a little, but what is this login/kdm/xdm/gdm problem you speak of? I know Thac released different versions of KDE 3.4 (RC1/Final/Final-Final?) and I think you folks must have gotten one of the buggy ones. I upgrade my KDE 3.2.3 to KDE 3.4 and I don't have this login error, nor do I have the menu error or things getting into segmentation faults. I have read on this forum and another forum about users experiencing the same problem, but I have yet to see it. What do you think happened? Now I'm a little hesitant about upgrading my other computer, computer 2, with Thac's KDE 3.4 because I don't know if the upgrade I did with computer 1 was the final release or the final-final release or RC1. Is there a way to check which Thac's KDE 3.4 I used?

Hello Micro... all i know is that some packages were released last week and since them I have been screaming mercy for the last couple of days. It apears to be something related to menu configuration but it broke display manager menudrake etc. Stay put amigo and wait until a solution is available.

I can work on my coomputer as long as i start kde from the comand line but neither mkddkm nor kdm is working for me at the moment...menudrake is broken (segmentation fault) and every time _I try to install a new app, I need to update the menu using update-menus command.....

The Thac KDE 3.4 packages for mdk 10.2 RC 1 are on the site... I installed 10.2 rc 1 yesterday, it's worked quite nicely. It comes with kde 3.3. I just installed KDE 3.4 using the RC 2 RPMs and so far, so good, even after a reboot. I went to the KDE 3.4 info page over at kde.org, I updated my urpmi with Thac's site and sources for the cooker distro. I did urpmi for each of the packages as they are listed on the KDE 3.4 info page. (ie, kdepim-3.4.0 - I did urpmi kdepim-3.4.0) if it told me I needed dependencies, I went with 'em. There were some files that failed because of dependencies, I did urpmi for those dependencies... then redid the packages... (hopefully this makes sense, I'm utterly exhausted)

Moral of the story - I am on Mandrake 10.2 RC 1, using Thac's KDE 3.4 for RC1, and it's working flawlessly. Not sure if mdkkdm is broken or not because I'm using GDM.

Rumor has it that 10.2 RC 2 will be out soon - I think I am just sticking with RC 1 until the final 10.2 comes out, because quite frankly, I'm sick of this.

And with that, I am going to sleep.

Sammi

Well, I tried upgrading to Thac's KDE 3.4 on my other computer and it totally hosed it. I'm geting the same errors as the others with multiple logins and getting boot to the terminal. What's even worse is that I can't type startx or startkde because I get a blank screen. It's okay though since I am going to try Mandrake 10.2 RC1 like Sammygirl.

IN the meantime, for those of you that have not upgraded, DO NOT use Thac's KDE 3.4 on Mandrake 10.1.

Micro can you do me a favour.....if you get it working let me know how you did it: upgrade, reinstall, downgrade to kde 3.2 in mandrake 10.1 and then upgrade etc.

Yeah it hosed my menu as well.

While everything works for me, I know have three of everything in the menu.

The bad news is that it hosed your menu brother.... the good news is that you are in good company. I have also hosed my linux vmware machine at worked after runnign those upgrades. The good thing is that i can always revert back to a working state (3.3.2 for example). I'll be testing some recommendations make by some users on the mandrakeusers.org forum so I'll keep you guys posted.

what I need form the rest of the team is information on the 10.2 upgrade, and how you guys did it. For exmaple, if you already had kde 3.4 installed, what ahppens if you do a 10.2 upgrade (which includes kde 3.3)? is the system functional after the 10.2 upgrade with kde 3.3? or did you guys go the "install form scratch route"?

Opjose to solve your menu problem (getting rid of the "triplicated" entries). do a update-menus -v -n and the command line. if that does not help, do a mv ~/.local ~/.local-bak and repeat. you will need to to that to all the users that use or have access to kde.

Also, say bye bye to menudrake since it will not work for any user again (may except for root). Also I get the same login problem (login loop) with both mdkkdm and kdm.

in the mandrake users org they recommend doing the following at the command line

urpme --auto mdkkdm
urpme --auto kdebase-kdm
urpmi --auto mdkkdm

on your user
mv ~/.local ~/.local-bak
then the update menus command and see if that helps.

I'll test that today here in vmware. it did not worked on my pc at home, but then again I think I missed something. I'll let you guys know....