Bug 855227
Summary: | No network after boot unless NetworkManager is restarted manually | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tim Wegener <twegener> |
Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | danw, dcbw, jay, jklimes, jones.peter.busi, reklov |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-13 13:56:35 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tim Wegener
2012-09-07 03:56:28 UTC
This appear as a problem with D-Bus daemon or some application making bad D-Bus calls: Sep 7 10:50:11 orange dbus-daemon[1001]: process 1001: arguments to dbus_message_set_reply_serial() were incorrect, assertion "reply_serial != 0" failed in file dbus-message.c line 1009. Sep 7 10:50:11 orange dbus-daemon[1001]: This is normally a bug in some application using the D-Bus library. Sep 7 10:50:11 orange dbus-daemon[1001]: D-Bus not built with -rdynamic so unable to print a backtrace Does your Dell have the same packages (NM, D-Bus, etc.)? (In reply to comment #1) ... > Does your Dell have the same packages (NM, D-Bus, etc.)? Yes, same package versions on both machines. Same problem here with a F16 laptop since a few days maybe. After booting network manager is running # systemctl status NetworkManager.service NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled) Active: active (running) since Sun, 21 Oct 2012 13:09:11 +0200; 1min 43s ago Main PID: 1004 (NetworkManager) CGroup: name=systemd:/system/NetworkManager.service └ 1004 /usr/sbin/NetworkManager --no-daemon but no network icon appears in the gnome-shell panel and the network connection doesn't work. After I run # systemctl restart NetworkManager.service the network icon appears in the gnome-shell panel and the network connection works. Same package versions here, excpet the kernel, which is kernel-3.4.11-1.fc16.x86_64 This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Still happening, in that the network systray icon is not visible after logging in after fresh boot. The network is available though, at least sometimes. As before, 'systemctl restart NetworkManager.service' makes things work again (until the next reboot). Now with the following package versions: NetworkManager-0.9.6.4-2.fc16.x86_64 NetworkManager-glib-0.9.6.4-2.fc16.x86_64 NetworkManager-gnome-0.9.6.4-2.fc16.x86_64 NetworkManager-gtk-0.9.6.4-2.fc16.x86_64 dbus-1.4.10-4.fc16.x86_64 dbus-glib-0.98-2.fc16.x86_64 glib2-2.30.3-1.fc16.x86_64 glib-networking-2.30.1-2.fc16.x86_64 kernel-3.6.11-4.fc16.x86_64 Happens with gnome-shell as well, .xsession-errors: ... ** (nm-applet:2086): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Method "GetAll" with signature "s" on interface "org.freedesktop.DBus.Properties" doesn't exist ** Message: applet now removed from the notification area ** (nm-applet:2086): WARNING **: fetch_connections_done: error fetching connections: (19) Method "ListConnections" with signature "" on interface "org.freedesktop.NetworkManager.Settings" doesn't exist . ** (nm-applet:2086): WARNING **: Failed to register as an agent: (19) Method "Register" with signature "s" on interface "org.freedesktop.NetworkManager.AgentManager" doesn't exist abrt-applet: glib < 2.31 - init threading Window manager warning: Log level 16: Could not initialize NMClient /org/freedesktop/NetworkManager: Method "GetAll" with signature "s" on interface "org.freedesktop.DBus.Properties" doesn't exist (gnome-shell:2077): folks-DEBUG: individual-aggregator.vala:310: Setting primary store IDs to defaults. (gnome-shell:2077): folks-DEBUG: individual-aggregator.vala:338: Primary store IDs are 'eds' and 'system'. JS LOG: GNOME Shell started at Sat Feb 02 2013 16:03:58 GMT+1030 (CST) ** Message: applet now embedded in the notification area Window manager warning: Log level 16: fetch_connections_done: error fetching connections: (19) Method "ListConnections" with signature "" on interface "org.freedesktop.NetworkManager.Settings" doesn't exist . Window manager warning: Log level 16: _nm_remote_settings_ensure_inited: (NMRemoteSettings) error initializing: Method "GetAll" with signature "s" on interface "org.freedesktop.DBus.Properties" doesn't exist JS LOG: NetworkManager is not running, hiding... It seems strange that nm-applet is running at all for the gnome-shell case. (ps auxww shows that nm-applet is running). After boot: $ systemctl status NetworkManager.service NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled) Active: active (running) since Sat, 02 Feb 2013 16:54:14 +1030; 1h 14min ago Main PID: 969 (NetworkManager) CGroup: name=systemd:/system/NetworkManager.service ├ 969 /usr/sbin/NetworkManager --no-daemon └ 1152 /sbin/dhclient -d -4 -sf /usr/libexec/nm-dhcp-clie... Using 'd-feet' to connect to the dbus system bus shows that org.freedesktop.NetworkManager is present: Name: org.freedesktop.NetworkManager Unique Name: 1.0 Command Line: /usr/sbin/NetworkManager --no-daemon Introspection Data Object Paths (and the rest of the Introspection Data is blank.) after 'systemctl restart NetworkManager.service', this gets populated with the expected interfaces. Relevant part of /var/log/messages: Feb 2 16:54:26 orange dbus-daemon[1040]: dbus[1040]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Feb 2 16:54:26 orange dbus[1040]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Feb 2 16:54:26 orange dbus-daemon[1040]: Launching FprintObject Feb 2 16:54:26 orange dbus-daemon[1040]: dbus[1040]: [system] Successfully activated service 'net.reactivated.Fprint' Feb 2 16:54:26 orange dbus[1040]: [system] Successfully activated service 'net.reactivated.Fprint' Feb 2 16:54:26 orange dbus-daemon[1040]: ** Message: D-Bus service launched with name: net.reactivated.Fprint Feb 2 16:54:26 orange dbus-daemon[1040]: ** Message: entering main loop Feb 2 16:54:26 orange kernel: [ 43.059056] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. Feb 2 16:54:39 orange dbus[1040]: [system] Failed to activate service 'org.freedesktop.ColorManager': timed out Feb 2 16:54:39 orange dbus-daemon[1040]: dbus[1040]: [system] Failed to activate service 'org.freedesktop.ColorManager': timed out Feb 2 16:54:39 orange dbus[1040]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Feb 2 16:54:39 orange dbus-daemon[1040]: dbus[1040]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Feb 2 16:54:39 orange dbus-daemon[1040]: process 1040: arguments to dbus_message_set_reply_serial() were incorrect, assertion "reply_serial != 0" failed in file dbus-message.c line 1009. Feb 2 16:54:39 orange dbus-daemon[1040]: This is normally a bug in some application using the D-Bus library. Feb 2 16:54:39 orange dbus-daemon[1040]: D-Bus not built with -rdynamic so unable to print a backtrace Feb 2 16:54:39 orange avahi-daemon[1011]: Disconnected from D-Bus, exiting. Feb 2 16:54:39 orange avahi-daemon[1011]: Got SIGTERM, quitting. Feb 2 16:54:39 orange avahi-daemon[1011]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.3. Feb 2 16:54:39 orange systemd[1]: systemd-logind.service: main process exited, code=exited, status=1 Feb 2 16:54:39 orange NetworkManager[969]: <warn> disconnected by the system bus. Feb 2 16:54:39 orange avahi-daemon[1011]: avahi-daemon 0.6.30 exiting. Feb 2 16:54:39 orange NetworkManager[969]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Feb 2 16:54:39 orange systemd[1]: Unit systemd-logind.service entered failed state. Feb 2 16:54:39 orange systemd[1]: bluetooth.service: main process exited, code=exited, status=1 Feb 2 16:54:39 orange dbus-daemon[1040]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Feb 2 16:54:39 orange systemd[1]: Unit bluetooth.service entered failed state. Feb 2 16:54:39 orange rtkit-daemon[1369]: Demoting known real-time threads. Feb 2 16:54:39 orange rtkit-daemon[1369]: Successfully demoted thread 1373 of process 1368 (/usr/bin/pulseaudio). Feb 2 16:54:39 orange rtkit-daemon[1369]: Successfully demoted thread 1372 of process 1368 (/usr/bin/pulseaudio). Feb 2 16:54:39 orange rtkit-daemon[1369]: Successfully demoted thread 1368 of process 1368 (/usr/bin/pulseaudio). Feb 2 16:54:39 orange rtkit-daemon[1369]: Demoted 3 threads. Feb 2 16:54:39 orange systemd[1]: dbus.service: main process exited, code=killed, status=6 Feb 2 16:54:39 orange nm-dispatcher.action: Caught signal 15, shutting down... Feb 2 16:54:39 orange nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/10-sendmail' exited abnormally. Feb 2 16:54:39 orange systemd[1]: accounts-daemon.service: main process exited, code=exited, status=1 Feb 2 16:54:39 orange systemd[1]: Unit accounts-daemon.service entered failed state. Feb 2 16:54:40 orange systemd[1]: Unit dbus.service entered failed state. Feb 2 16:54:40 orange NetworkManager[969]: dbus_g_proxy_begin_call: assertion `!DBUS_G_PROXY_DESTROYED (proxy)' failed Feb 2 16:54:40 orange NetworkManager[969]: nm_supplicant_info_set_call: assertion `call != NULL' failed Feb 2 16:54:40 orange NetworkManager[969]: <info> (wlan0): IP6 addrconf timed out or failed. Feb 2 16:54:40 orange NetworkManager[969]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled... Feb 2 16:54:40 orange NetworkManager[969]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started... Feb 2 16:54:40 orange NetworkManager[969]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete. Feb 2 16:54:42 orange NetworkManager[969]: <info> reconnected to the system bus. Relevant to the dbus-daemon / systemd activation time out aspects: assertion failure in systemd activation: reply_serial != 0 (dbus-message.c:1009) https://bugs.freedesktop.org/show_bug.cgi?id=50199 Using the workaround from the following bug comment got things working for me: https://bugs.freedesktop.org/show_bug.cgi?id=50199#c10 # Downgrade colord from colord-0.1.21-1 to colord-0.1.12-1: yum downgrade colord reboot It now allows my first log in attempt to be successful (rather than grinding for a bit and then returning to gdm, which it did previously for the first log in attempt after each boot), and NetworkManager is working and the panel applet is present in the system tray. (This older version of colord use dbus itself for activation, rather than systemd. Apparently there is some bug when systemd tried to activate colord that brought down a bunch of dbus-daemon services, including NetworkManager.) Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |