[Touch-packages] [Bug 1899146] Re: systemd-resolve has no --verbose or --debug flag

2021-06-30 Thread Dan Streetman
this is a request that must be taken upstream, not to ubuntu ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1899146] Re: systemd-resolve has no --verbose or --debug flag

2020-10-15 Thread Dan Streetman
** Also affects: systemd via https://github.com/systemd/systemd/issues/17330 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1899146] Re: systemd-resolve has no --verbose or --debug flag

2020-10-13 Thread Dimitri John Ledkov
You can start systemd-resolved (the daemon side of it) with Environment=SYSTEMD_LOG_LEVEL=debug. Then you will have more data of what is being asked; where the requests go; what is returned, etc. Do not forget to drop caches between requests! But I do agree cli option would be nice. -- You

[Touch-packages] [Bug 1899146] Re: systemd-resolve has no --verbose or --debug flag

2020-10-13 Thread Olivier Godart
Hi Sebastien, I just opened this feature request on the upstream: https://github.com/systemd/systemd/issues/17330 ** Bug watch added: github.com/systemd/systemd/issues #17330 https://github.com/systemd/systemd/issues/17330 -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1899146] Re: systemd-resolve has no --verbose or --debug flag

2020-10-09 Thread Sebastien Bacher
Thank you for your bug report, that's the sort of requests that would probably make more sense to be reported directly upstream https://github.com/systemd/systemd/issues ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a