[Bug 262444] kde-4.5.4 loads kde3 kicker and background (even with ~/.kde & ~/.kde4 removed)

[David Rankin]

https://bugs.kde.org/show_bug.cgi?id=262444





--- Comment #3 from David Rankin <drankinatty suddenlinkmail com>  2011-01-10 00:34:47 ---
    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 when kde4 is launched. What would create this kickerrc
under ~/.kde4/share/config?  I suspect there is an entire section of the kde4
setup in Arch that is a forgotten holdover from kde3 and needs to be removed.
Unfortunately, I have no clue how kde4 is packaged and don't know where to
start looking.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.