Registered Member
|
Oops, sorry about that. Here is the output with the correction: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. kbuildsycoca4 running... |
Registered Member
|
I'm not sure, if I understood your last post.
What I tried, while beeing logged in using LXDE: 1. executed
2. executed
3. checked that no kde (kded4, kdeinit, ...) process was active 4. executed the three export commands. But what do I have to expect or what is to check next? |
Administrator
|
You should have kdeinit4 and klauncher running on your system, and possibly kded4. You should then execute ksmserver (as previously noted).
This is beginning to unfortunately not make much sense in terms of why it is crashing...
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
I'm really sorry for wasting your time, but I am still a bit confused, what you ask me actually to do.
What I tried now: - starting kbuildsycoca4 - executing the export commands - executing the start_kdeinit_wrapper command. When starting ksmserver afterwards (kded4, kdeinit4 are startet), I get the error message again. One more information ist given, which was not shown in the output, I have posted earlier:
I suppose, it's not what you asked me to do, sorry for that. |
Administrator
|
Excellent, that is what I was after
It seems that KDE Daemon (kded4) has a module which is only loaded on a full KDE session which is causing the crash. Despite that however, did the rest of KDE start up ok? Were you able to use Dr Konqi to generate a backtrace? (if so, post it here please as it will likely point to the module causing the crash)
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Well, difficult to say for me, if the KDE session is started with all components when starting ksmserver manually. I would say: more or less. At least plasma-desktop is not fully operational. The tasklist is started, but the background and the plasmoids are not.
I am not able to generate a backtrace, because the necessary dev packages are not installed and the keyboard is not operational when running into the crash. Therefore I can't type in my root pw to install the needed packages. Is it possible for you to tell me, which packages have to installed, or is it depending on the crash situation? |
Administrator
|
It will depend upon the crash situtation unfortunately. That is very odd that the keyboard is not functional.
To try and narrow this down a little, can you try starting a session using the basic start_kdeinit_wrapper and ksmserver process - without the export commands - then running the following:
Does this crash?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
You was quicker then I am. I did some copy and paste things to get the pw and currently the needed packages are downloaded. So I hope to be back with the backtrace a bit later on.
|
Registered Member
|
Here we go:
|
Administrator
|
It appears that it is loading a Keyboard module - which is responsible for handling Keyboard Layouts. As part of this it is using QCA2 - a Qt crypto library - which appears to be crashing during it's initialisation.
I could not find any KDE bugs in regard to this - but please do check that all packages are up to date - as this type of crash should not occur.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Thanks. Just to confuse you a little bit more:
I saw in KDE service setting, that "energy settings" (I think this is the powerdevil module) was deaktivated. When activating it (now all services are checked), I get the following output:
It seems that in general the first service which is startet causes the crash. Also in this case, the libqca2 is used. Checked it again in the package manager, libqca2 2.03.-18.2 is installed, repository is KDE 4.8 Core. No newer version is available. |
Administrator
|
Ok, it looks like anything that uses libqca2 will crash on startup unfortunately. It seems that a large number of KDE Daemon modules - which are only loaded during a full session - use libqca2.
Kopete and Plasma Desktop both use libqca2 as well - which is interesting as Plasma Desktop seems to launch ok on your system... or maybe it fails as well. With regards to this - I would recommend making a bug report against the KDE 4.8 repository you are using.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Turns out I was right. We were having the same problem but it seems to have been a different cause. I downgraded from Mesa 8.0 to 7.11 and it fixed my problem. |
Registered Member
|
OK. Thanks again for taking your time to investigate and to help me. Good to know that people like you care about others.
Unfortunately this is not a matter of course in these days. Take care. If anybody else is interested, here is the link to the bug report: https://bugs.kde.org/show_bug.cgi?id=294955 |
Registered Member
|
Problem is solved!
The right hint was, to check gstreamer packages. Indeed, gstreamer was mixed up between OpenSUSE Tumbleweed, openSUSE and Packman repsitories, however this has happend. Most likely, the openSUSE Tumbleweed packages have caused the crash. After downgrading all gstreamer packages to the openSUSE repository, KDE is running as smooth as before. A long road, but worth the investigations. |
Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell, Yahoo [Bot]