ubuntuusers.de

Ich komme in MATE 20.04 nicht mehr in den update-notifier rein, das Programm schmiert ab. Aus dem Terminal

(update-notifier:19754): dbind-WARNING **: 23:03:51.667: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(livepatch-notification:19760): dbind-WARNING **: 23:03:51.732: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Network war natürlich nicht "broken".

dmesg | grep update sagt

[    7.180122] systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly.

Wie soll das gelb markierte durchgeführt werden?

grep update /var/log/syslog

systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly.

Die Updates selbst funktionieren aber problemlos.

Sind weitere Infos nötig?

sudo rm /var/crash/*

war es auch nicht, der Fehler taucht beim Einloggen schon auf, auch unter XFCE, dass es ein Problem mit einer Systemanwendung gibt.

Ich setze mal auf gelöst. Die Lösung bisher war, Ubuntu zu installieren, da gehts. Möglicherweise ein Bug in MATE?!

auf Verdacht

cat /lib/systemd/system/dbus.socket 

Gruß Taomon

Oh zu spät.

cat /lib/systemd/system/dbus.socket

[Unit]
Description=D-Bus System Message Bus Socket

[Socket]
ListenStream=/var/run/dbus/system_bus_socket

Ist jetzt halt nicht mehr unter MATE. Möglicherweise ein /run bzw. /var/run-Problem?!

Sieht bei mir genauso aus. Allerdings noch unter 19.10.

Gefunden habe ich eine bug report allerdings für Debian. Aber wieso funktioniert das in ubuntu (gnome-shell) aber nicht in mate.

Hast du den Loging-manager auch aus getauscht?

systemctl status dbus.service dbus.socket

Gruß Taomon

● dbus.service - D-Bus System Message Bus
     Loaded: loaded (/lib/systemd/system/dbus.service; static; vendor preset: enabled)
     Active: active (running) since Thu 2020-05-14 11:45:11 CEST; 9h ago
TriggeredBy: ● dbus.socket
       Docs: man:dbus-daemon(1)
   Main PID: 698 (dbus-daemon)
      Tasks: 4 (limit: 9423)
     Memory: 29.2M
     CGroup: /system.slice/dbus.service
             ├─  698 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
             └─24721 python3 /usr/lib/software-properties/software-properties-dbus

Mai 14 13:15:41 Slayer dbus-daemon[698]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.244' (uid=1000 pid=50772 >
Mai 14 13:15:42 Slayer dbus-daemon[698]: [system] Successfully activated service 'org.freedesktop.hostname1'
Mai 14 13:23:06 Slayer dbus-daemon[698]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=69>
Mai 14 13:23:07 Slayer dbus-daemon[698]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Mai 14 14:48:27 Slayer dbus-daemon[698]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=69>
Mai 14 14:48:27 Slayer dbus-daemon[698]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Mai 14 16:07:04 Slayer dbus-daemon[698]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.292' (uid=1000 pid=53472 >
Mai 14 16:07:05 Slayer dbus-daemon[698]: [system] Successfully activated service 'org.freedesktop.hostname1'
Mai 14 19:29:30 Slayer dbus-daemon[698]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.342' (uid=0 pid=56477 comm="/usr/bin/gdbus c>
Mai 14 19:29:30 Slayer dbus-daemon[698]: [system] Successfully activated service 'org.freedesktop.PackageKit'

● dbus.socket - D-Bus System Message Bus Socket
     Loaded: loaded (/lib/systemd/system/dbus.socket; static; vendor preset: enabled)
     Active: active (running) since Thu 2020-05-14 11:45:11 CEST; 9h ago
   Triggers: ● dbus.service
     Listen: /run/dbus/system_bus_socket (Stream)
      Tasks: 0 (limit: 9423)
     Memory: 0B
     CGroup: /system.slice/dbus.socket

Mai 14 11:45:11 Slayer systemd[1]: Listening on D-Bus System Message Bus Socket.
Mai 14 19:15:31 Slayer systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_soc>
Mai 14 19:16:45 Slayer systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_soc>

Ich habe gar nichts getauscht. Offenbar ist es in MATE ein Unterschied?!

Trat wieder auf. Diesmal auch mit dbus-Fehler.

Ich habe mal in Synaptic geschaut und da finden sich die Pakete libdbusmenu-glib4, libdbusmenu-gtk3-4 und gir1.2-dbusmenu-glib-0.4 noch in den Bionic- und Eoan-Versionen von 2018!

Das ist jetzt die Ausgabe

● dbus.service - D-Bus System Message Bus
     Loaded: loaded (/lib/systemd/system/dbus.service; static; vendor preset: enabled)
     Active: active (running) since Fri 2020-05-15 18:46:34 CEST; 12min ago
TriggeredBy: ● dbus.socket
       Docs: man:dbus-daemon(1)
   Main PID: 700 (dbus-daemon)
      Tasks: 3 (limit: 9422)
     Memory: 54.6M
     CGroup: /system.slice/dbus.service
             ├─ 700 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
             └─2877 /usr/bin/python3 /usr/sbin/aptd

Mai 15 18:57:48 Slayer com.ubuntu.SoftwareProperties[3631]: Unable to init server: Could not connect: Connection refused
Mai 15 18:57:48 Slayer dbus-daemon[700]: [system] Successfully activated service 'com.ubuntu.SoftwareProperties'
Mai 15 18:57:48 Slayer com.ubuntu.SoftwareProperties[3631]: Traceback (most recent call last):
Mai 15 18:57:48 Slayer com.ubuntu.SoftwareProperties[3631]:   File "/usr/lib/software-properties/software-properties-dbus", line 68, in <module>
Mai 15 18:57:48 Slayer com.ubuntu.SoftwareProperties[3631]:     server = SoftwarePropertiesDBus(bus, datadir=datadir)
Mai 15 18:57:48 Slayer com.ubuntu.SoftwareProperties[3631]:   File "/lib/python3/dist-packages/softwareproperties/dbus/SoftwarePropertiesDBus.py", line 66, in __init__
Mai 15 18:57:48 Slayer com.ubuntu.SoftwareProperties[3631]:     self._livepatch_service = LivepatchService()
Mai 15 18:57:48 Slayer com.ubuntu.SoftwareProperties[3631]:   File "/lib/python3/dist-packages/softwareproperties/LivepatchService.py", line 93, in __init__
Mai 15 18:57:48 Slayer com.ubuntu.SoftwareProperties[3631]:     self._session = requests_unixsocket.Session()
Mai 15 18:57:48 Slayer com.ubuntu.SoftwareProperties[3631]: NameError: name 'requests_unixsocket' is not defined

● dbus.socket - D-Bus System Message Bus Socket
     Loaded: loaded (/lib/systemd/system/dbus.socket; static; vendor preset: enabled)
     Active: active (running) since Fri 2020-05-15 18:46:33 CEST; 12min ago
   Triggers: ● dbus.service
     Listen: /run/dbus/system_bus_socket (Stream)
     CGroup: /system.slice/dbus.socket

Mai 15 18:46:33 Slayer systemd[1]: Listening on D-Bus System Message Bus Socket.

Aus dem Terminal

/usr/bin/python3 /usr/bin/software-properties-gtk

ERROR:dbus.proxies:Introspect error on :1.125:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
Traceback (most recent call last):
  File "/usr/bin/software-properties-gtk", line 100, in <module>
    app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file)
  File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 211, in __init__
    self.backend.Reload();
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__
    return self._connection.call_blocking(self._named_service,
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in call_blocking
    reply_message = self.send_message_with_reply_and_block(
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.125 was not provided by any .service files

Ich habe jetzt 20.04 neu installiert und nach jedem Nachinstallationsschritt die Aktualisierungsverwaltung getestet. Funktioniert bisher alles.

Unterschied zu bisher war "nur", dass ich jetzt im UEFI- anstatt Legacy-Modus installiert habe

Korrektur: Fehler sind wieder da

May 17 10:55:07 Slayer dbus-daemon[696]: [system] Activating service name='com.ubuntu.SoftwareProperties' requested by ':1.111' (uid=1000 pid=2313 comm="/usr/bin/python3 /usr/bin/software-properties-gtk " label="unconfined") (using servicehelper)
May 17 11:18:39 Slayer dbus-daemon[37312]: [session uid=0 pid=37310] Activating service name='org.gnome.OnlineAccounts' requested by ':1.0' (uid=0 pid=37296 comm="/usr/bin/python3 /usr/bin/software-properties-gtk " label="unconfined")
May 17 11:18:39 Slayer dbus-daemon[37312]: [session uid=0 pid=37310] Activating service name='org.freedesktop.portal.Desktop' requested by ':1.0' (uid=0 pid=37296 comm="/usr/bin/python3 /usr/bin/software-properties-gtk " label="unconfined")
May 17 13:47:09 Slayer dbus-daemon[693]: [system] Activating service name='com.ubuntu.SoftwareProperties' requested by ':1.214' (uid=1000 pid=11878 comm="/usr/bin/python3 /usr/bin/software-properties-gtk " label="unconfined") (using servicehelper)
May 17 13:47:10 Slayer com.ubuntu.SoftwareProperties[11895]:   File "/usr/lib/software-properties/software-properties-dbus", line 68, in <module>
May 17 13:47:10 Slayer update-manager.desktop[11878]:   File "/usr/bin/software-properties-gtk", line 100, in <module>
May 17 13:47:10 Slayer update-notifier-crash[11911]: software-properties-dbus
May 17 13:47:10 Slayer update-notifier-crash[11912]: software-properties-dbus
May 17 13:49:02 Slayer dbus-daemon[693]: [system] Activating service name='com.ubuntu.SoftwareProperties' requested by ':1.232' (uid=1000 pid=14490 comm="/usr/bin/python3 /usr/bin/software-properties-gtk " label="unconfined") (using servicehelper)
May 17 13:49:02 Slayer com.ubuntu.SoftwareProperties[14507]:   File "/usr/lib/software-properties/software-properties-dbus", line 68, in <module>
May 17 13:49:02 Slayer update-manager.desktop[14490]:   File "/usr/bin/software-properties-gtk", line 100, in <module>
May 17 13:49:14 Slayer dbus-daemon[693]: [system] Activating service name='com.ubuntu.SoftwareProperties' requested by ':1.234' (uid=1000 pid=14524 comm="/usr/bin/python3 /usr/bin/software-properties-gtk " label="unconfined") (using servicehelper)
May 17 13:49:14 Slayer com.ubuntu.SoftwareProperties[14540]:   File "/usr/lib/software-properties/software-properties-dbus", line 68, in <module>
May 17 13:49:14 Slayer update-manager.desktop[14524]:   File "/usr/bin/software-properties-gtk", line 100, in <module>
May 17 13:50:08 Slayer update-notifier-crash[14633]: software-properties-gtk
May 17 14:44:35 Slayer dbus-daemon[695]: [system] Activating service name='com.ubuntu.SoftwareProperties' requested by ':1.258' (uid=1000 pid=5434 comm="/usr/bin/python3 /usr/bin/software-properties-gtk " label="unconfined") (using servicehelper)
May 17 14:44:35 Slayer com.ubuntu.SoftwareProperties[5451]:   File "/usr/lib/software-properties/software-properties-dbus", line 68, in <module>
May 17 14:44:35 Slayer update-manager.desktop[5434]:   File "/usr/bin/software-properties-gtk", line 100, in <module>
May 17 14:44:35 Slayer update-notifier-crash[5467]: software-properties-dbus
May 17 14:44:35 Slayer update-notifier-crash[5468]: software-properties-dbus
May 17 14:48:08 Slayer update-notifier-crash[2620]: software-properties-gtk
May 17 16:33:04 Slayer dbus-daemon[699]: [system] Activating service name='com.ubuntu.SoftwareProperties' requested by ':1.187' (uid=1000 pid=3298 comm="/usr/bin/python3 /usr/bin/software-properties-gtk " label="unconfined") (using servicehelper)
May 17 16:33:04 Slayer com.ubuntu.SoftwareProperties[3314]:   File "/usr/lib/software-properties/software-properties-dbus", line 68, in <module>
May 17 16:33:04 Slayer update-manager.desktop[3298]:   File "/usr/bin/software-properties-gtk", line 100, in <module>
May 17 16:33:04 Slayer update-notifier-crash[3329]: software-properties-gtk

software-properties-gtk --debug

ERROR:dbus.proxies:Introspect error on :1.202:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
Traceback (most recent call last):
  File "/usr/bin/software-properties-gtk", line 100, in <module>
    app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file)
  File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 211, in __init__
    self.backend.Reload();
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__
    return self._connection.call_blocking(self._named_service,
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in call_blocking
    reply_message = self.send_message_with_reply_and_block(
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.202 was not provided by any .service files

Ideen?

So, jetzt habe ich Ubuntu 18.04 im EFI-Modus installiert bekommen. Da läuft alles.

Für mich: Problem gelöst.

Update: Da ich mir das System zerschossen habe, habe ich 20.04 noch eine neue Chance gegeben. Da läufts jetzt auch nach allen Updates