Well, the backtrace seems somewhat improbable my best guess right now is
that prime somehow messes with dbus (which would be weird but hey).
The crash appears to not be caused by anything rational though:
if (kcminitSignals) {
connect( kcminitSignals, SIGNAL(phase2Done()), SLOT(kcmPhase2Done()));
kcminitSignals is a dbusinterface, it will be null if the interface is
invalid after creation, or if kcminitSignals was deleted. so really
there is no reason for it to crash there. at all.
Lacking understanding of how exactly a different gpu can cause this I'll
move the bug to prime, perhaps someone more knowledable has ideas. To me
it seems very random to the point that it may be a symptom of a
completely different problem.
** Package changed: kde-workspace (Ubuntu) => nvidia-prime (Ubuntu)
** Changed in: nvidia-prime (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1291526
Title:
could not start ksmserver with nvidia-prime at next login
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1291526/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
