My tip is: Remove all non KDE3 related patterns that relate to Plasma. or Start from non graphical installation and install your way up carefully to KDE3 at the same time making sure no plasma packages aregetting installed. On Saturday 27 August 2016 09:43:40 Mark Goldstein wrote:
On Fri, Aug 26, 2016 at 8:47 PM, Mark Goldstein
wrote: On Wed, Aug 24, 2016 at 8:34 PM, Mark Goldstein
wrote: Yes, .xsession-errors:0 is produced and similar to yours. 1st thing I see there is parcellite which seems to be kde4/5 and Klipper from KDE3. Will probable remove parcellite. Looks like it have some configurable plugins and I see the message: Plasma Shell startup completed
I added some printouts to startkde3 script. Of course parcellite is not a problem. The problem starts after execution of "kwrapper ksmserver". After that point somehow the processes of plasma5 are started (krunner, plasma shell activity manager and probably more). I need to see what "shared" configurations causes kde3 to start these processes.
As Felix suggested, I removed some patterns (plasma5, plasma5-session, plasma5-workspace and dependencies) and the problem disappeared.
I'll try to see later if I can find exact reason why plasma5 components are started under KDE3.
-- Mark Goldstein
-- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org