Bug 106100 - Add debug application
Summary: Add debug application
Status: RESOLVED MOVED
Alias: None
Product: GeoClue
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Geoclue Bugs
QA Contact: Geoclue Bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-17 12:26 UTC by Bastien Nocera
Modified: 2018-05-06 14:37 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bastien Nocera 2018-04-17 12:26:22 UTC
where-am-i and the agent are useful for testing Geoclue, but there's no application that will show the unfiltered current view of Geoclue wrt. its usage and clients.

A debug application would include the output of:
- InUse and available accuracy level
- The current clients, their desktop names, update frequency and current location details, and whether they're considered system clients or not
Comment 1 Zeeshan Ali 2018-04-22 15:15:12 UTC
I don't think it has to be a separate application. Geoclue already logs a lot of debug output on the console, that I make use of during development. Actually the output is a lot so I am thinking of having separate log domains for each component so it's easy to filter the debug you are interested in. Of course, we could add more debug as well to show the specific things you asked for.
Comment 2 Bastien Nocera 2018-04-22 15:50:03 UTC
(In reply to Zeeshan Ali from comment #1)
> I don't think it has to be a separate application.

A separate application would allow it to be run against a geoclue instance that's already there. Most of the information is already available through the D-Bus interface, but I think is locked out to only be accessible for the agent.

> Geoclue already logs a
> lot of debug output on the console, that I make use of during development.

This means restarting geoclue. The goal here is to have an overview of the current state of the running geoclue, which might not be set up to have a debug output.

> Actually the output is a lot so I am thinking of having separate log domains
> for each component so it's easy to filter the debug you are interested in.
> Of course, we could add more debug as well to show the specific things you
> asked for.

That's fine, but it's not useful if you want to have debug information about the currently running geoclue.
Comment 3 GitLab Migration User 2018-05-06 14:37:06 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/geoclue/geoclue/issues/62.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.