You are not logged in.

#1 2022-01-31 20:44:58

Leif5
Member
Registered: 2021-10-09
Posts: 7

Journal Red Path how to fix

I ran my journalctl e got some red message. How can I fix this?


jan 31 17:37:18 alfheim gnome-session-binary[618]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
jan 31 17:37:18 alfheim gnome-session-binary[618]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
jan 31 17:37:38 alfheim gdm-password][872]: gkr-pam: unable to locate daemon control file
jan 31 17:37:52 alfheim pulseaudio[1057]: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-rg.bluez.service not found.
jan 31 17:38:08 alfheim gdm-launch-environment][574]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

Thanks in advance!

Offline

#2 2022-01-31 21:36:17

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,293

Re: Journal Red Path how to fix

You can't, unless you actively notice something not working and are sure these are the cause then  these aren't problematic, ignore them.

You can definitely ignore the middle two, very likely the last one, the first two are the only ones I'd say read out of the ordinary. but if things work this is likely due to some small race cond during start up that the system can generally recover from.

Offline

Board footer

Powered by FluxBB