Public bug reported:
Upon determining whether a scope is in debug mode, the scope must be
located via the registry. The registry rightfully allows the scope to
startup slowly, but the originating locate() call enforces the regular
timeout.
This is causing premature timeout errors when trying debug a scope on
the desktop.
** Affects: unity-scopes-api (Ubuntu)
Importance: Undecided
Assignee: Marcus Tomlinson (marcustomlinson)
Status: In Progress
** Description changed:
Upon determining whether a scope is in debug mode, the scope must be
located via the registry. The registry rightfully allows the scope to
- startup slowly, but the originating locate() call is expecting a regular
- timeout period.
+ startup slowly, but the originating locate() call enforces the regular
+ timeout.
+
+ This is causing premature timeout errors when trying debug a scope on
+ the desktop.
** Changed in: unity-scopes-api (Ubuntu)
Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)
** Changed in: unity-scopes-api (Ubuntu)
Status: New => In Progress
--
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/1469069
Title:
Two-way request for debug mode status should itself use a lenient
timeout
Status in unity-scopes-api package in Ubuntu:
In Progress
Bug description:
Upon determining whether a scope is in debug mode, the scope must be
located via the registry. The registry rightfully allows the scope to
startup slowly, but the originating locate() call enforces the regular
timeout.
This is causing premature timeout errors when trying debug a scope on
the desktop.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1469069/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
