> but I do notice that the scope restarts and is running with a new PID.
Which doesn't take into account the changes in the source python file, driving me crazy... Can you tell me how this is at all possible... I was able to trigger a change once by editing /usr/share/unity- scopes/canonicaldirectory/unity_canonicaldirectory_daemon.py and changing the SEARCH_HINT string (and I did see the change in the dash) but as soon as I tried other changes (or even changing that string again), nothing happened :-/ So, even if unrelated to the bug, some light on how that whole thing works internally will help ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1209346 Title: scope-runner-dbus.py crashed with SIGSEGV in PyObject_Call() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1209346/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
