** Changed in: unity8-session-snap
Assignee: Michael Terry (mterry) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1645798
Title:
No snaps
** Changed in: unity-scope-click (Ubuntu)
Status: New => Won't Fix
** Changed in: unity-scopes-api (Ubuntu)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Agree, marking this won't fix, we can re-open if we see other symptoms
** Changed in: canonical-devices-system-image
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Actually, since the app drawer has landed now, can we just remove unity-
scope-click from the snap?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1645798
Title:
You can run the scope with U1_DEBUG=1 set, and it will spew more debug
info.
I doubt it's threads. We're not using QtDBus here really. The ubuntu-
download-manager code does use it, but we're no longer really using it
in the scope, only the client object gets created on startup, and then
never
It looks like click-scope is the only scope that is failing. Queries to
the music scope work just fine, as do queries to remote scopes (via
smartscopesproxy). All these scopes run the exact same code in the
runtime.
I have no idea what exactly is going wrong, but I strongly suspect that
it is in
I've spent pretty much all day trying to track this down. The debug
cycle time with core 16 in a VM doesn't help :-(
What I can see is that crap comes out of the ZmqReceiver when an object
adapter tries to dispatch an incoming request to the scope. The problem
doesn't manifest itself in the same
Michi, the exception itself seems to be from
https://bazaar.launchpad.net/~unity-team/unity-scopes-
api/trunk/view/head:/src/scopes/internal/zmq_middleware/ZmqMiddleware.cpp
and getting bubbled up through the bits.
Judging from the logs, what appears to happen is that the scope is
started, and
@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
Michi, in that scope-registry.log you pastebinned, it looks like the ZMQ
socket is getting closed/removed in the middle of calling Query in the
scope:
(process:2658): ubuntu-app-launch-DEBUG: Initialized Click DB
[2016-12-09 05:20:22.797] ERROR: clickscope: ObjectAdapter: error unmarshaling
The "/bin/desktop-launch: not found" error is because you took out the
SNAP= definition.
/run/user/0/dbus-session doesn't exist? You ran "sudo unity8-session"
in a KVM?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Michael, the command fails because /run/user/0/dbus-session doesn't exist.
I also looks like I have a different version installed. I see 264 and 277
(besides common) in /root/snap/unity8-session.
I adjusted your command to not set DBUS_SESSION_ADDRESS and explicitly
set LD_LIBRARY_PATH (without
** Also affects: unity-scopes-api (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity-scopes-api (Ubuntu)
Importance: Undecided => Critical
** Changed in: unity-scopes-api (Ubuntu)
Assignee: (unassigned) => Michi Henning (michihenning)
** Changed in: unity-api
> "BFB" is "Big Flavorful Button" ;)
Ah, as in "BFG-9000" :-)
> So, from your screenshot it looks like you are hitting case number 2 from my
> previous post. Is
> there a crash report in /var/crash/ for the scoperunner?
/var/crash doesn't exist on a snappy machine. I have no idea where core
** Changed in: canonical-devices-system-image
Milestone: p1 => p2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-api in Ubuntu.
https://bugs.launchpad.net/bugs/1645798
Title:
No snaps appear in scope on Core 16
Michi, since it sounds like scoperunner is dying on you, try my
scoperunner command up above again, with the right snappyenv. Here it
is again (with fixed snappyenv):
DBUS_SESSION_BUS_ADDRESS=`cat /run/user/0/dbus-session | cut -f2- -d=`
HOME=/root/snap/unity8-session/264
"BFB" is "Big Flavorful Button" ;)
It's the huge orange "Ubuntu Store" result that appears at the bottom of
the scope.
So, from your screenshot it looks like you are hitting case number 2
from my previous post. Is there a crash report in /var/crash/ for the
scoperunner? If not, does running
Sorry, I don't know what a "BFB result" is. It does show "Apps". I've
attached a screenshot.
** Attachment added: "Screenshot from 2016-12-08 14-23-54.png"
@michi Is there at least the BFB result for the store? Does it show
"Apps" at the top of the dash? Or is everything totally blank?
If answers are "yes, yes, no" then the result set is indeed just empty for some
reason.
If answers are "no, yes, no" then either unity-scope-snappy is not installed
The assertion failure appears to be unrelated to the click scope not showing
any results.
What is interesting is that the other scopes seems to work fine, it's only the
click scope that is empty. With the missing applications dir in place, I'm not
seeing any errors at all in the logs, just the
The missing applications dir was coincidental and isn't the root cause of this
problem.
The issue is racy, so I'm seeing different things in the logs each time.
Still digging...
** Branch unlinked: lp:~michihenning/unity-scopes-api/create-
applications-dir
--
You received this bug notification
** Branch linked: lp:~michihenning/unity-scopes-api/create-applications-
dir
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-api in Ubuntu.
https://bugs.launchpad.net/bugs/1645798
Title:
No snaps appear in scope on
@Michi, /root/snappyenv should be
"/snap/unity8-session/current/snappyenv", my bad.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-api in Ubuntu.
https://bugs.launchpad.net/bugs/1645798
Title:
No snaps appear in
I'll push a branch to have the registry create the applications dir if
it doesn't exist. That should be good enough for the moment. But the
whole .desktop file generation thing is a hack. As far as we can work
out, this was needed because online accounts refused to work unless
there was a .desktop
I would like to track down what causes the assertion failure in scopes-
api regardless.
DBUS_SESSION_BUS_ADDRESS=`cat /run/user/0/dbus-session | cut -f2- -d=`
HOME=/root/snap/unity8-session/264
SNAP_USER_DATA=/root/snap/unity8-session/264
SNAP_USER_COMMON=/root/snap/unity8-session/common
Looking at /root/snap/unity8-session/common/.cache/upstart/scope-
registry.log, there are lots of messages along the following lines:
scoperegistry: ignoring scope "clickscope": cannot create metadata:
unity::SyscallException: RegistryObject::create_desktop_file: unable to
create desktop file:
I've added Pawel because of the "Invalid departments database" error.
I'm looking at the other errors. I suspect what's happening is that some
of the local socket path names are wrong.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
The scoperunner does NOT crash if I run it under gdbserver. But I do
see some errors in that case:
(process:4583): ubuntu-app-launch-DEBUG: Initialized Click DB
[2016-11-30 21:43:45.633] ERROR: clickscope: ObjectAdapter: error unmarshaling
request header (id: , adapter: clickscope-c, op: ):
28 matches
Mail list logo
