On 01/08/2011 04:21 PM, David Rosenstrauch wrote:
Seriously David, I think it's time for you to give up on kde3 already.
You can't expect the people on the Arch list to help support old, unsupported, and out of date software. The more you bring your Arch box up to date the less and less likely it'll be that old, unsupported software will run on it.
Why not switch to XFCE or something? You can still use some KDE(4) apps if you want, without having to be tied down to the whole environment.
DR
Thanks DR. I'm not looking for help with kde3. (I know it is dead and not supported and I wouldn't bother the list with it) I'm looking for why kde4 is loading the old kde3 kicker & background by default. The issue here has nothing to do with kde3. There is no reason I shouldn't be able to leave it installed and still use kde4. Ever since the June 2008 launch of kde 4.0.4, it has been widely represented that you can have both kde3 and kde4 installed side-by-side and they should not interfere with each other. That's why K3 is /opt based with its user config in ~/.kde while K4 is /usr based with its user config in ~/.kde4. What I need to find is where and why in the kde4.5.5-1 load process the Arch i686 packages are looking for the prior kde config and creating an erroneous ~/.kde4/share/config/kickerrc. I'm not bitching, I'm just trying to find answers to not only solve my problem, but help everyone else out that might be bitten by this. There seems to be some difference in the Arch kde4 packaging between i686 and x86_64. (I know it doesn't make sense...) I have a dozen Arch boxes and I have no problems with the x86_64 kde4 where kdemod3 is still installed. But for some reason on the i686 Dell boxes, I either get kde4 pulling in its plasma panel & the kde3 kicker or I get lockups of kde4 at the end of ksplash (box hardlocks) On my suse boxes with both kde3 and kde4 installed, both i686 and x86_64, kde4 loads without any of this strangeness. That's the only reason it points me to the possibility of an Arch i686 k4 packaging issue. The biggest difference is the Arch install creates the ~/.kde4/share/config/kickerrc which loads the kde3 kicker panel in kde4. That should not happen. The SuSE install of kde4 creates no ~/.kde4/share/config/kickerrc at all (which is correct because kde4 has a 'plasma panel' and no 'kicker' at all) So why the Arch k4 i686 packaging causes a k4 kickerrc to be created at all is a mystery to me and probably worth looking into as it should not be occurring at all. The Arch x86_64 kde4 packaging does not do this either. On my Arch x86_64 boxes, no kickerrc is created: 13:41 nirvana:~> l ~/.kde4/share/config/kicker* ls: cannot access /home/david/.kde4/share/config/kicker*: No such file or directory So something is not correct with the i686 k4 packaging that causes a kde4 kickerrc to be created. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com