Re: Network problems with f39
On 12/20/23 04:38, Samuel Sieb wrote: On 12/19/23 21:31, Robert McBroom via users wrote: On 12/19/23 01:53, Samuel Sieb wrote: This is the problem you need to resolve. I don't know why. You'll need to find out why the dbus broker can't run. I would have expected more details in the log. -- I'm not sure what to look for in the journal. Does this section show the problem? Sequence repeats several times Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** Warning -- SELinux targeted policy relabel is required. Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** Relabeling could take a very long time, depending on file Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** system size and speed of hard drives. Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: Running: /sbin/fixfiles -T 0 restore Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: Looking up NSS user entry for 'systemd-oom'... Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: NSS returned no entry for 'systemd-oom' Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: Invalid user-name in /usr/share/dbus-1/system.d/org.freedesktop.oom1.conf +9: user="systemd-oom" Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: Started dbus-broker.service - D-Bus System Message Bus. Dec 18 09:27:11 dv7t.attlocal.net audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 18 09:27:11 dv7t.attlocal.net kernel: kauditd_printk_skb: 15 callbacks suppressed Dec 18 09:27:11 dv7t.attlocal.net kernel: audit: type=1130 audit(1702909631.147:131): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[1191]: ERROR launcher_run_child @ ../src/launch/launcher.c +347: Permission denied Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: ERROR service_add @ ../src/launch/service.c +1011: Transport endpoint is not connected What have you done to your system? For some reason it's doing a relabel. It should be done, you can try rebooting and see if things go better. But things look quite broken. -- After the upgrade there were some messages about selinux errors. Restarted the system set for a relabel. The relabel completed satisfactorily as far as I could tell. Will try again with permissive set as suggested. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Network problems with f39
On Dec 20, 2023, at 00:31, Robert McBroom via users wrote: > > Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[1191]: ERROR > launcher_run_child @ ../src/launch/launcher.c +347: Permission denied > Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: ERROR service_add > @ ../src/launch/service.c +1011: Transport endpoint is not connected > Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: > launcher_add_services @ ../src/launch/launcher.c +804 > Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: launcher_run @ > ../src/launch/launcher.c +1415 > Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: run @ > ../src/launch/main.c +152 > Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: main @ > ../src/launch/main.c +178 > Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: Exiting due to > fatal error: -107 > Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: dbus-broker.service: Main > process exited, code=exited, status=1/FAILURE > Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: dbus-broker.service: Failed > with result 'exit-code'. Most likely, this is the problem, dbus-broker can’t start due to a permissions problem, possibly related to the SELinux relabel requirement. Pretty much everything uses DBUS for interprocess communication in the systemd world, so a failed dbus-broker would break quite a bit. You might need to run the relabel with SELinux in permissive mode. -- Jonathan Billings -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Network problems with f39
On Wed Dec20'23 02:11:00AM, Samuel Sieb wrote: > From: Samuel Sieb > Date: Wed, 20 Dec 2023 02:11:00 -0800 > To: users@lists.fedoraproject.org > Reply-To: Community support for Fedora users > Subject: Re: Network problems with f39 > > On 12/20/23 01:47, Ranjan Maitra via users wrote: > > This may be thoroughly unrelated, but my wife has had this problem on a > > Dell for years (largely regularly), and me only intermittently over the > > past few months (F38 or F39). I think it may be dependent on the service > > provider because the same setup has worked without a hitch in some hotel > > rooms, not in others (for me). > > > > I usually get this working by doing: > > > > sudo systemctl restart systemd-resolved.service > > > > and things work flawlessly (at least apparently) after that. > > > > Again, not sure if this is related. > > That is completely unrelated. OK, thanks! ANy idea what may cause this? Ranjan -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Network problems with f39
On 12/20/23 01:47, Ranjan Maitra via users wrote: This may be thoroughly unrelated, but my wife has had this problem on a Dell for years (largely regularly), and me only intermittently over the past few months (F38 or F39). I think it may be dependent on the service provider because the same setup has worked without a hitch in some hotel rooms, not in others (for me). I usually get this working by doing: sudo systemctl restart systemd-resolved.service and things work flawlessly (at least apparently) after that. Again, not sure if this is related. That is completely unrelated. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Network problems with f39
This may be thoroughly unrelated, but my wife has had this problem on a Dell for years (largely regularly), and me only intermittently over the past few months (F38 or F39). I think it may be dependent on the service provider because the same setup has worked without a hitch in some hotel rooms, not in others (for me). I usually get this working by doing: sudo systemctl restart systemd-resolved.service and things work flawlessly (at least apparently) after that. Again, not sure if this is related. Best wishes, Ranjan On Wed Dec20'23 01:38:01AM, Samuel Sieb wrote: > From: Samuel Sieb > Date: Wed, 20 Dec 2023 01:38:01 -0800 > To: users@lists.fedoraproject.org > Reply-To: Community support for Fedora users > Subject: Re: Network problems with f39 > > On 12/19/23 21:31, Robert McBroom via users wrote: > > > > On 12/19/23 01:53, Samuel Sieb wrote: > > > This is the problem you need to resolve. > > > I don't know why. You'll need to find out why the dbus broker can't > > > run. I would have expected more details in the log. > > > -- > > > > > I'm not sure what to look for in the journal. Does this section show the > > problem? Sequence repeats several times > > > > Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** Warning > > -- SELinux targeted policy relabel is required. > > Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** > > Relabeling could take a very long time, depending on file > > Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** system > > size and speed of hard drives. > > Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: Running: > > /sbin/fixfiles -T 0 restore > > Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: Looking up > > NSS user entry for 'systemd-oom'... > > Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: NSS returned > > no entry for 'systemd-oom' > > Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: Invalid > > user-name in /usr/share/dbus-1/system.d/org.freedesktop.oom1.conf +9: > > user="systemd-oom" > > Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: Started > > dbus-broker.service - D-Bus System Message Bus. > > Dec 18 09:27:11 dv7t.attlocal.net audit[1]: SERVICE_START pid=1 uid=0 > > auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 > > msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/systemd" > > hostname=? addr=? terminal=? res=success' > > Dec 18 09:27:11 dv7t.attlocal.net kernel: kauditd_printk_skb: 15 > > callbacks suppressed > > Dec 18 09:27:11 dv7t.attlocal.net kernel: audit: type=1130 > > audit(1702909631.147:131): pid=1 uid=0 auid=4294967295 ses=4294967295 > > subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker comm="systemd" > > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > > Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[1191]: ERROR > > launcher_run_child @ ../src/launch/launcher.c +347: Permission denied > > Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: ERROR > > service_add @ ../src/launch/service.c +1011: Transport endpoint is not > > connected > > What have you done to your system? > For some reason it's doing a relabel. It should be done, you can try > rebooting and see if things go better. But things look quite broken. > -- > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Network problems with f39
On 12/19/23 21:31, Robert McBroom via users wrote: On 12/19/23 01:53, Samuel Sieb wrote: This is the problem you need to resolve. I don't know why. You'll need to find out why the dbus broker can't run. I would have expected more details in the log. -- I'm not sure what to look for in the journal. Does this section show the problem? Sequence repeats several times Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** Warning -- SELinux targeted policy relabel is required. Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** Relabeling could take a very long time, depending on file Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** system size and speed of hard drives. Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: Running: /sbin/fixfiles -T 0 restore Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: Looking up NSS user entry for 'systemd-oom'... Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: NSS returned no entry for 'systemd-oom' Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: Invalid user-name in /usr/share/dbus-1/system.d/org.freedesktop.oom1.conf +9: user="systemd-oom" Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: Started dbus-broker.service - D-Bus System Message Bus. Dec 18 09:27:11 dv7t.attlocal.net audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 18 09:27:11 dv7t.attlocal.net kernel: kauditd_printk_skb: 15 callbacks suppressed Dec 18 09:27:11 dv7t.attlocal.net kernel: audit: type=1130 audit(1702909631.147:131): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[1191]: ERROR launcher_run_child @ ../src/launch/launcher.c +347: Permission denied Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: ERROR service_add @ ../src/launch/service.c +1011: Transport endpoint is not connected What have you done to your system? For some reason it's doing a relabel. It should be done, you can try rebooting and see if things go better. But things look quite broken. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Network problems with f39
On 12/19/23 01:53, Samuel Sieb wrote: On 12/18/23 22:12, Robert McBroom via users wrote: Upgraded legacy bios laptop from f37 to f39. Use command line boot. User login cycles and returns to login prompt. Can boot system on command line as root. The network does not connect with a dependency failure on NetworkManager. Not cleared on a reinstall of NetworkManager. It's not a NetworkManager issue. Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: dbus-broker.service: Start request repeated too quickly. Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: dbus-broker.service: Failed with result 'exit-code'. Dec 18 09:46:38 dv7t.attlocal.net audit: BPF prog-id=74 op=UNLOAD Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: Failed to start dbus-broker.service - D-Bus System Message Bus. This is the problem you need to resolve. I don't know why. You'll need to find out why the dbus broker can't run. I would have expected more details in the log. -- I'm not sure what to look for in the journal. Does this section show the problem? Sequence repeats several times Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** Warning -- SELinux targeted policy relabel is required. Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** Relabeling could take a very long time, depending on file Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** system size and speed of hard drives. Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: Running: /sbin/fixfiles -T 0 restore Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: Looking up NSS user entry for 'systemd-oom'... Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: NSS returned no entry for 'systemd-oom' Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: Invalid user-name in /usr/share/dbus-1/system.d/org.freedesktop.oom1.conf +9: user="systemd-oom" Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: Started dbus-broker.service - D-Bus System Message Bus. Dec 18 09:27:11 dv7t.attlocal.net audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 18 09:27:11 dv7t.attlocal.net kernel: kauditd_printk_skb: 15 callbacks suppressed Dec 18 09:27:11 dv7t.attlocal.net kernel: audit: type=1130 audit(1702909631.147:131): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[1191]: ERROR launcher_run_child @ ../src/launch/launcher.c +347: Permission denied Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: ERROR service_add @ ../src/launch/service.c +1011: Transport endpoint is not connected Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: launcher_add_services @ ../src/launch/launcher.c +804 Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: launcher_run @ ../src/launch/launcher.c +1415 Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: run @ ../src/launch/main.c +152 Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: main @ ../src/launch/main.c +178 Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: Exiting due to fatal error: -107 Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: dbus-broker.service: Failed with result 'exit-code'. Dec 18 09:27:11 dv7t.attlocal.net audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' Dec 18 09:27:11 dv7t.attlocal.net kernel: audit: type=1131 audit(1702909631.164:132): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' Dec 18 09:27:11 dv7t.attlocal.net audit: BPF prog-id=57 op=LOAD Dec 18 09:27:11 dv7t.attlocal.net kernel: audit: type=1334 audit(1702909631.171:133): prog-id=57 op=LOAD Dec 18 09:27:11 dv7t.attlocal.net audit: BPF prog-id=56 op=UNLOAD Dec 18 09:27:11 dv7t.attlocal.net kernel: audit: type=1334 audit(1702909631.173:134): prog-id=56 op=UNLOAD Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: Starting dbus-broker.service - D-Bus System Message Bus... Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[1195]: Looking up NSS user entry for 'systemd-oom'... Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[1195]: NSS returned no entry for 'systemd-oom' Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[1195]: Invalid user-name in /usr/share/dbus-1/system.d/org.freedesktop.oom1.conf +9: user="systemd-oom" Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: Started
Re: Network problems with f39
On 12/18/23 22:12, Robert McBroom via users wrote: Upgraded legacy bios laptop from f37 to f39. Use command line boot. User login cycles and returns to login prompt. Can boot system on command line as root. The network does not connect with a dependency failure on NetworkManager. Not cleared on a reinstall of NetworkManager. It's not a NetworkManager issue. Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: dbus-broker.service: Start request repeated too quickly. Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: dbus-broker.service: Failed with result 'exit-code'. Dec 18 09:46:38 dv7t.attlocal.net audit: BPF prog-id=74 op=UNLOAD Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: Failed to start dbus-broker.service - D-Bus System Message Bus. This is the problem you need to resolve. I don't know why. You'll need to find out why the dbus broker can't run. I would have expected more details in the log. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Network problems with f39
Upgraded legacy bios laptop from f37 to f39. Use command line boot. User login cycles and returns to login prompt. Can boot system on command line as root. The network does not connect with a dependency failure on NetworkManager. Not cleared on a reinstall of NetworkManager. Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: dbus-broker.service: Start request repeated too quickly. Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: dbus-broker.service: Failed with result 'exit-code'. Dec 18 09:46:38 dv7t.attlocal.net audit: BPF prog-id=74 op=UNLOAD Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: Failed to start dbus-broker.service - D-Bus System Message Bus. Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: Dependency failed for NetworkManager.service - Network Manager. Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: Dependency failed for NetworkManager-wait-online.service - Network Manager Wait Online. Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: NetworkManager-wait-online.service: Job NetworkManager-wait-online.service/start failed with result 'dependency'. Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: NetworkManager.service: Job NetworkManager.service/start failed with result 'dependency'. Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: dbus.socket: Failed with result 'service-start-limit-hit'. Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: accounts-daemon.service: Deactivated successfully. Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: Started accounts-daemon.service - Accounts Service Dec 18 19:09:23 dv7t.attlocal.net systemd[1]: Starting NetworkManager.service - Network Manager... Dec 18 19:09:23 dv7t.attlocal.net systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE Dec 18 19:09:23 dv7t.attlocal.net systemd[1]: dbus-broker.service: Failed with result 'exit-code'. Dec 18 19:09:23 dv7t.attlocal.net audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' Dec 18 19:09:23 dv7t.attlocal.net audit: BPF prog-id=86 op=UNLOAD Dec 18 19:09:23 dv7t.attlocal.net systemd[1]: NetworkManager.service: Deactivated successfully. Dec 18 19:09:23 dv7t.attlocal.net systemd[1]: Stopped NetworkManager.service - Network Manager. Dec 18 19:09:23 dv7t.attlocal.net audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 18 19:09:23 dv7t.attlocal.net audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 18 19:13:59 dv7t.attlocal.net NetworkManager[2850]: [1702944839.5428] NetworkManager (version 1.44.2-1.fc39) is starting... (boot:65b94e65-710c-4203-9817-fb8f92cb8ebb) Dec 18 19:13:59 dv7t.attlocal.net NetworkManager[2850]: [1702944839.5434] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity-fedora.conf) (run: 15-carrier-timeout.conf) Dec 18 19:13:59 dv7t.attlocal.net NetworkManager[2850]: [1702944839.5588] bus-manager: cannot connect to D-Bus: Could not connect: Connection refused Hardware works fine on dual boot to windows. How can I debug the NetworkManager problems? -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
