Bug 361658 - kactivitymanage segfault (libQt5Sql.so.5.4.2) when running nomachines in KDE (other desktops work)
Summary: kactivitymanage segfault (libQt5Sql.so.5.4.2) when running nomachines in KDE ...
Status: RESOLVED NOT A BUG
Alias: None
Product: plasma-activities
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.15.0
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Ivan Čukić
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-12 10:23 UTC by Morgan Cox
Modified: 2016-05-02 16:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Morgan Cox 2016-04-12 10:23:12 UTC
Just tried to use nomachines in Kubuntu 15.10.

https://www.nomachine.com/

As soon as you load the application and click in it the KDE/Plasma desktop crashes and returns to login screen.

I see this in dmesg

[ 4081.700227] kactivitymanage[3595]: segfault at 7fcb2e7f1cd0 ip 00007fcb146711b1 sp 00007ffe1904f3b8 error 4 in libQt5Sql.so.5.4.2[7fcb1465d000+3f000]

Seems to be a KDE issue, I installed LXDE (which I accessed through sddm) and it doesn't crash.

Note: After the crash I used the Kubuntu backports ppa - this upgraded the package -> 5.18.0-0ubuntu1~ubuntu15.10~ppa1 - the crash no longer happens

I am running an intel GPU btw

However this will be a problem for anyone not using backports.

regards
Comment 1 Ivan Čukić 2016-05-02 16:51:01 UTC
Dear Morgan,

Your X11 session crashes - I would guess it is a driver issue triggered by nomachine and kwin (or plasma, since it is also now a heavy opengl user).

ActivityManager just seems like a culprit since it gets terminated by the session that crashes, and then a QtSQL bug gets triggered making kamd crash.

Anyhow, I'd advise you to try starting nomachine without compositing enabled in kwin, or even trying to temporarily replace kwin with whatever windowing manager lxde uses *inside* the plasma session.

An alternative could be to use lxde, and start a few kde applications (including plasma) in order to try to triage what exactly triggers the crash.