kallecarl wrote:There is no indication in this thread about your hardware. I'm running ExoPC Slate with the Atom N450.

I'm running a Fujitsu Stylistic Q550, an Intel Oak Trail platform. The most prominent thing about it is the GMA600 (Poulsbo) graphics chip that is notoriously supported by PowerVR... Thankfully, with psb_gfx, the performance is somewhat manageable.

I was trying to fix the autologin problem I mentioned in the first post, and I thought that perhaps changing to the KDM as provided by the official KDE Release 47 might solve the problem. However, that also required me to change around the version of some other KDE libraries. I did that, and it hilariously broke the thing! Now I get the KDE taskbar at the bottom in addition to the Plasma Active Home Screen. The logout buttons also just make the screen black instead of doing anything useful.

The most hilarious part of it is that it solves pretty much all of the other issues I mentioned in this post. KWin now starts correctly, autologin works fine (although the screen is black while autologin is being performed) and system settings work as it should! So what's up with that? How come the KDE libraries as provided by the PA repo cause such anomalies, while the KDE:47 repo is more or less normal, although conflicting with PA?

^ Precisely what I noticed. I was struggling with all kinds of similar issues as well, and while trying to trace the problem noticed that the open-slx PA repos only provide a small set of core KDE packages, and all the rest of my KDE packages were from the original Opensuse 12.1 repos. PA wouldn't seem to work with KDE packages not from the PA repo, and yet I'm pretty sure the KDE packages in the PA repos aren't working well with the packages from the other repos.

Is there something we could do about this? PA One on the old repo had no such issues, iirc it worked with the packages in the KDE:47 repo. PA Two from the open-slx repos is pretty unusable in just about every way not directly related to the core PA UI.

You can install the PA2 packages from open-slx' Repo on top of 12.1, so everything not in the PA2 repos comes from 12.1. So no KR47, and no 11.4 support either.

What are the problems you are facing in detail?

Do those problems persist if you start off with an empty user, i.e. no self-configured configfiles around in ~/.kde4/share/config/ ?

My issues with my upgraded system are these:

1. KWin fails to launch
2. System Settings fail to launch
3. NetworkManager displays incorrect graphics (problem was also in PA1)
4. Frequent Plasma crashes (problem was also in PA1)
5. Auto login doesn't work (this is a local problem, since it's not present when using the LiveCD)

System settings is not supported anymore. I thought I'd disabled it in the build entirely, but apparently there are some remainders left. Will need to clean it out.

Kwin failing to start: don't know the problem, a log, backrace would be helpful.

NM display problem: Known problem, no solution yet, WIP.

Frequent crashes: We need backtraces for these, otherwise they'll never be fixed. Please file bugs (one per crasher) with backtrace on bugs.kde.org.

Another problem I've been frequently facing is share-like-connect not working in the browser - it remains grayed out, not sure if problem is limited to browser - and the browser not appearing in the peek-and-launch open windows strip, also not sure if limited to browser. Not sure if both problems are related either, but they do seem to happen together so far.

System settings is not supported anymore? That's a shame Does that mean _every_ setting/option that used to be in there isn't supposed to work anymore? That'll be sad because some of them are really useful imo. For example global-shortcuts: so I can make use of buttons on my tablet that maps to key combinations. Also, I use some window rules for some visual novel games that I play on my tablet - to get rid of window decorations and such. There are also all those other stuff not really related to the tablet shell, like file associations, startup behavior, phonon settings etc. Is it not possible for PA to work with the traditional settings or is this just the set up in the repos? In other words, if I build PA myself, will I be able to achieve a setup where I can use the traditional system settings?

Given that the modules work if launched independently, it would seem that the system settings are supposed to be integrated into PA Settings. Otherwise it would indeed be a huge loss of functionality.