Guys,
I need to know if this is an arch packaging issue or a kde.org issue. On my
arch box with all kde4 updates through today, I launch kde4 and my kde3 kicker
and the kde4 plasma panel are both present:
[26k]
http://www.3111skyline.com/dl/arch/bugs/kde4/k3+k4_panels-640.jpeg
So I moved ~/.kde4 figuring it was the problem and launched kde4 again. Still
it pulled in my kde3 kicker and background. Huh?
So I moved ~/.kde and ~/.kde4 to make sure there was nothing kde (3 or 4)
related in my home directory and I launched kde4 again. To my surprise, kde4
loaded it's plasma panel and then proceeded to load the default kdemod3 kicker
and kdemod3 background?? See:
[24k]
http://www.3111skyline.com/dl/arch/bugs/kde4/k3+k4_panels-new-640.jpg
Obviously something is very wrong here. kde4 should not be loading the
kdemod3 kicker or background. Looking at the newly created
~/.kde4/share/config files, the kickerrc file contains the following:
15:42 providence:~> cat .kde4/share/config/kickerrc
[$Version]
update_info=kickerrc.upd:kde_3_1_sizeChanges,kickerrc.upd:kde_3_4_reverseLayout,kickerrc.upd:kde_3_5_kconfigXTize
Double-huh? Why would kde-4.5.4 create a kickerrc containing kde3
entries?
Let me know if you think this is an Arch packaging issue or a kde.org issue
so I know where to file the bug. Thanks.
--
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
