@dobey: There is in the log: terminate called after throwing an instance of 'unity::scopes::MiddlewareException'
I don't know where this exception comes from. It would be great to find out. I believe that, if an exception is thrown (no matter what kind of exception) from one of the threads we send into the scope, the runtime will handle it correctly. (If not, that's a bug in scopes-api.) But, if the exception is thrown by a thread that wasn't created by the scopes runtime, there is obviously nothing much we can do. (In that case, the other errors are consequential errors, I'd say.)
@mterry: Yes, I did this in side the VM after starting the session. There is no /run/user/0/dbus-session.
@dobey: There is in the log: terminate called after throwing an instance of 'unity: :scopes: :MiddlewareExce ption'
I don't know where this exception comes from. It would be great to find out. I believe that, if an exception is thrown (no matter what kind of exception) from one of the threads we send into the scope, the runtime will handle it correctly. (If not, that's a bug in scopes-api.) But, if the exception is thrown by a thread that wasn't created by the scopes runtime, there is obviously nothing much we can do. (In that case, the other errors are consequential errors, I'd say.)
@mterry: Yes, I did this in side the VM after starting the session. There is no /run/user/ 0/dbus- session.