[Bug 1795852] Re: "systemd-resolve --status" reports "Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found."

2021-06-30 Thread Dan Streetman
please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795852

Title:
  "systemd-resolve --status" reports "Failed to get global data: Unit
  dbus-org.freedesktop.resolve1.service not found."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1795852/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1795852] Re: "systemd-resolve --status" reports "Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found."

2020-01-10 Thread Jim Baxter
This happened to me when I upgraded from 16.04 LTS to 18.04 LTS, I
noticed error dialog boxes during the install but unsure if they are
related.


The /etc/resolv.conf contained:

# Generated by NetworkManager
search lan
nameserver 127.0.0.53


I compared it to a fresh install of 18.04 and this had /etc/resolv.conf
as a symlink pointing to /run/systemd/resolve/stub-resolv.conf, so I
modified the broken system with these commands.

sudo mv /etc/resolv.conf /etc/resolv.conf.bak
sudo ln -s /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

But this did not work.


I then found that the broken system had the package resolvconf installed that 
is not installed on the new 18.04 installation so I removed it with the command:

sudo apt purge resolvconf


After a reboot my networking now works though the /etc/resolv.conf
symlink has become a file again containing:

# Generated by NetworkManager
search lan
nameserver 192.168.1.1


The command systemd-resolve --status still fails with the error:
Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.

So I suspect this is not a correct fix but more of an accidental
workaround.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795852

Title:
  "systemd-resolve --status" reports "Failed to get global data: Unit
  dbus-org.freedesktop.resolve1.service not found."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1795852/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1795852] Re: "systemd-resolve --status" reports "Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found."

2019-01-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: systemd (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795852

Title:
  "systemd-resolve --status" reports "Failed to get global data: Unit
  dbus-org.freedesktop.resolve1.service not found."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1795852/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs