Description of problem: Even after clean reinstall there are some "Important" errors displayed in Logs. Version-Release number of selected component (if applicable): n/a How reproducible: Always Steps to Reproduce: 1. Install Fedora 35 2. Open Logs Actual results: At least 6 error messages are listed, similar are grouped, so total number is a bit higher. Expected results: Ideally there should be no "Important" error messages for clean install, except some cases when they are related to specific hardware/driver combinations and cannot be tested and fixed. Having clean error log to start with, makes easier to spot issues and problems later. Additional info: In my case on Fedora 35 I have following error messages listed as "Important" in Logs. Some already have open issues, so I've added links to them. - gdm-session-wor: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed - systemd: Failed to start Application launched by gnome-session-binary. https://bugzilla.redhat.com/show_bug.cgi?id=1973058 - gdm-session-wor: gkr-pam: unable to locate daemon control file - gnome-session-b: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - bluetoothd: Failed to set mode: Blocked through rfkill (0x12) - avahi-daemon: chroot.c: open() failed: No such file or directory https://bugzilla.redhat.com/show_bug.cgi?id=1356304
I very much support the goal. But those bugs need to be filed against respective packages. Those are mostly GNOME issues. Filing a bug against systemd is not going to help. *** This bug has been marked as a duplicate of bug 1973058 ***