Summary: | Segfault in kactivitymanagerd when trying to initiate Plasma session via X2Go | ||
---|---|---|---|
Product: | [Plasma] kactivitymanagerd | Reporter: | Fabian Köster <koesterreich> |
Component: | general | Assignee: | Ivan Čukić <ivan.cukic> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | plasma-bugs |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | systemd journal |
Description
Fabian Köster
2015-11-25 09:17:24 UTC
Created attachment 95721 [details]
systemd journal
The systemd journal produced by journalctl -b.
Search for "x2go" to find the start of the faulty Plasma session.
See also related bugs Bug #353825 - Login by x2go in Plasma 5 crashes KCMInit Bug #355877 - Segfault in kscreen_backend How can I get a full backtrace for those segfaults? This is a related problem I've found elsewhere: http://www.itksnap.org/pmwiki/pmwiki.php?n=Documentation.XCBIssues > Problems with Running ITK-SNAP over X11, NoX and X2GO > > When users try to run ITK-SNAP on a server (e.g., computing cluster front-end) with > limited video card resources, errors arise. A typical error is > > QXcbConnection: Failed to get the primary output of the screen > QXcbConnection: XCB error: 172 (Unknown), sequence: 158, resource id: 150, major code: 149 > > Qt developers are working on this issue[1]. For the time being, we are providing a version of > [...] [1] https://bugreports.qt.io/browse/QTBUG-31389 I'm marking this as invalid since it is not a problem of kactivities. The crash you are getting from kactivities is a known Qt issue that happens when the activities service is being shut down. p.s. I don't mind continuing the discussion here, and if you find a solution to your problem, please do post it here. Unfortunately, I can not be of much help with the x2go setup. You can ping Martin G. on IRC to ask him whether he has some experience with this. (In reply to Ivan Čukić from comment #4) > I'm marking this as invalid since it is not a problem of kactivities. The > crash you are getting from kactivities is a known Qt issue that happens when > the activities service is being shut down. OK, thanks for the fast response and the information you provided! I agree that this is not a bug in kactivities. |