Plasma crashing in -current
 

Hi,

I've searched the forum but I couldn't find anything related to this problem.
The fact it is eventual makes it hard to debug I believe.

So eventually plasma crashes in -current and the only thing that I could find so far is this message at .xsession-errors

--- 8< ---
KCrash: Attempting to start /usr/bin/plasma-desktop from kdeinit
KCrash: Application 'plasma-desktop' crashing...
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusObjectPath: invalid path ""
This is the current thread id for Activities 139708742424320 QThread(0x190f4f0)
plasma-desktop(4366)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
plasma-desktop(4366)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
static bool QDeclarativeMetaType::isModule(const QByteArray&, int, int) Qt 4.7 import detected; please note that Qt 4.7 is directly reusable as QtQuick 1.x with no code changes. Continuing, but startup time will be slower.
plasma-desktop(4366)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished

--- 8< ---

I though that with the lastest Xorg/kernel that wouldn't happen, but it did.

This is my system: uname -a

Linux odin 3.8.8 #2 SMP Thu Apr 18 22:48:10 CDT 2013 x86_64 Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz GenuineIntel GNU/Linux

Kde in -current use qt 4.8 not 4.7

Thanks for noticing that.

I google this problem and end up on this kde bug: https://bugs.kde.org/show_bug.cgi?id=310647

It seems that we need to recompile qt-core with -Os instead of -O2.

Now I just need to know how to ask Volkerdi to do that :)

Just grab the source http://slackware.osuosl.org/slackwar...t/source/l/qt/ and edit SlackBuild and compile qt
Please post this command here

Right, but I believe that fix should be done at the slackware tree, don't you think?

Please provide the output from

I have that crash on my Slackware ARM Chromebook. I just started a rebuild of qt with "-Os" to see if that cures the plasma crash.
Don't stay up to wait for the outcome... compiling Qt on a wee ARM computer takes much longer than on my quad-core Athlon build server...

Eric

$ qmake -v
QMake version 2.01a
Using Qt version 4.8.4 in /usr/lib64/qt/lib

I have rebuild Qt and I'll let you know if that is fixed or not.

Thanks.

PS. Eric, can't wait to have Slackware in my Chromebook :)

I have rebuild qt with -Os option but it crashed yesterday.

Let's see how it is going to behave today. BTW, after I upgraded (?!?) to this new version I've reboot my system to make sure I was not running any old stuff.

Perhaps I missed something. Feel free to check the changed qt.SlackBuild and if you find anything wrong, please let me know.

Thanks.

Compiling with -Os isn't the answer. The bug report you found isn't the end of the trail. You'll notice it is closed as a duplicate. If you follow the link to the original, you'll find another kde bug report that is closed as "fixed upstream", and a link to this: https://bugreports.qt-project.org/browse/QTBUG-29082 which contains a patch.


No idea whether it works... I'm not a KDE user, and was just reading the bug reports out of curiosity.

How the fsck does one get a proper patch out of https://codereview.qt-project.org ???

Eric

Ha, so, it's not just me. I still couldn't figure it out.
Please let me know if you do.

Thx.

Run

within a clone of the qt git repo

Please verify whether the updated qt in current fixed this problem or not

That just make my life much easier. I've updated, so let's see how it will behave.
Thanks Willy.