You are not logged in.
Hi,
I have a cifs filesystem (auto)mounted in fstab as follows
//muleserve/raidwrite /mnt/raid cifs credentials=/etc/raidwritecred,uid=bendavid,gid=users,ro,file_mode=0400,dir_mode=0500,_netdev,noauto,x-systemd.automount 0 0
On startup everything works as expected, and the filesystem is automatically mounted on first access (after the network comes up)
My network connection is wireless with "automatically connect" and "all users may connect" enabled in the kde network manager settings (such that network manager will bring up the connection before I log in).
On shutdown there is a long (~1 minute) delay before the unmounting of this filesystem finally times out. (This may be related to the network-manager related warnings which show up in the logs below)
The full log is below starting from the beginning of the shutdown.
Thanks,
Josh
Jul 06 15:19:34 theMuleDesktop polkitd[334]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.40, object path /org/kde/PolicyKit1/AuthenticationAgent, locale en_CA.UTF-8)
Jul 06 15:19:34 theMuleDesktop obexd[611]: Terminating
Jul 06 15:19:34 theMuleDesktop bluetoothd[390]: Endpoint unregistered: sender=:1.35 path=/MediaEndpoint/A2DPSource
Jul 06 15:19:34 theMuleDesktop bluetoothd[390]: Endpoint unregistered: sender=:1.35 path=/MediaEndpoint/A2DPSink
Jul 06 15:19:34 theMuleDesktop ModemManager[311]: <info> Caught signal, shutting down...
Jul 06 15:19:34 theMuleDesktop ntpd[364]: ntpd exiting on signal 15 (Terminated)
Jul 06 15:19:34 theMuleDesktop bluetoothd[390]: Terminating
Jul 06 15:19:34 theMuleDesktop sshd[357]: Received signal 15; terminating.
Jul 06 15:19:34 theMuleDesktop NetworkManager[312]: <info> ModemManager disappeared from bus
Jul 06 15:19:34 theMuleDesktop NetworkManager[312]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Jul 06 15:19:34 theMuleDesktop NetworkManager[312]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Jul 06 15:19:34 theMuleDesktop ModemManager[311]: <info> ModemManager is shut down
Jul 06 15:19:34 theMuleDesktop apcupsd[316]: apcupsd exiting, signal 15
Jul 06 15:19:34 theMuleDesktop apcupsd[316]: apcupsd shutdown succeeded
Jul 06 15:19:34 theMuleDesktop collectd[363]: Exiting normally.
Jul 06 15:19:34 theMuleDesktop collectd[363]: collectd: Stopping 5 read threads.
Jul 06 15:19:34 theMuleDesktop collectd[363]: rrdtool plugin: Shutting down the queue thread.
Jul 06 15:19:34 theMuleDesktop collectd[363]: collectd: Stopping 5 write threads.
Jul 06 15:19:34 theMuleDesktop collectdmon[362]: Info: collectd terminated with exit status 0
Jul 06 15:19:34 theMuleDesktop systemd[476]: pam_unix(systemd-user:session): session closed for user lightdm
Jul 06 15:19:34 theMuleDesktop kernel: wlp0s29u1u3: deauthenticating from 00:22:6b:75:5c:d9 by local choice (Reason: 3=DEAUTH_LEAVING)
Jul 06 15:19:34 theMuleDesktop systemd[534]: pam_unix(systemd-user:session): session closed for user bendavid
Jul 06 15:19:34 theMuleDesktop bluetoothd[390]: Stopping SDP server
Jul 06 15:19:34 theMuleDesktop bluetoothd[390]: Exit
Jul 06 15:19:34 theMuleDesktop collectdmon[362]: Info: shutting down collectdmon
Jul 06 15:19:34 theMuleDesktop NetworkManager[312]: <warn> disconnected by the system bus.
Jul 06 15:19:34 theMuleDesktop systemd[1]: Cannot find unit for notify message of PID 390.
Jul 06 15:19:34 theMuleDesktop lightdm[336]: Failed to get D-Bus connection
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: Calling CRDA to update world regulatory domain
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: World regulatory domain updated:
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: DFS Master region: unset
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 0 KHz), (N/A, 2000 mBm), (N/A)
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 0 KHz), (N/A, 2000 mBm), (N/A)
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A, 2000 mBm), (N/A)
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: (5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
Jul 06 15:19:34 theMuleDesktop mkinitcpio[3768]: ==> Starting build: none
Jul 06 15:19:34 theMuleDesktop mkinitcpio[3768]: -> Running build hook: [sd-shutdown]
Jul 06 15:19:35 theMuleDesktop mkinitcpio[3768]: ==> Build complete.
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: WPA: Key negotiation completed with 00:22:6b:75:5c:d9 [PTK=CCMP GTK=CCMP]
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-CONNECTED - Connection to 00:22:6b:75:5c:d9 completed [id=0 id_str=]
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: SME: Trying to authenticate with 00:22:6b:75:5c:d9 (SSID='jbmaN' freq=5200 MHz)
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-DISCONNECTED bssid=00:22:6b:75:5c:d9 reason=2 locally_generated=1
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: Trying to associate with 00:22:6b:75:5c:d9 (SSID='jbmaN' freq=5200 MHz)
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: Associated with 00:22:6b:75:5c:d9
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: WPA: Key negotiation completed with 00:22:6b:75:5c:d9 [PTK=CCMP GTK=CCMP]
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-CONNECTED - Connection to 00:22:6b:75:5c:d9 completed [id=0 id_str=]
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-SCAN-STARTED
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-SCAN-STARTED
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-SCAN-STARTED
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-SCAN-STARTED
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-SCAN-STARTED
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-SCAN-STARTED
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-SCAN-STARTED
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-SCAN-STARTED
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-SCAN-STARTED
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-DISCONNECTED bssid=00:22:6b:75:5c:d9 reason=3 locally_generated=1
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-TERMINATING
Jul 06 15:19:35 theMuleDesktop NetworkManager[312]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
Jul 06 15:19:35 theMuleDesktop NetworkManager[312]: nm_supplicant_info_set_call: assertion 'call != NULL' failed
Jul 06 15:19:38 theMuleDesktop NetworkManager[312]: <error> [1404652778.246978] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:19:39 theMuleDesktop NetworkManager[312]: <info> (wlp0s29u1u3): roamed from BSSID 00:22:6B:75:5C:D9 (jbmaN) to (none) ((none))
Jul 06 15:19:41 theMuleDesktop NetworkManager[312]: <error> [1404652781.244629] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:19:44 theMuleDesktop NetworkManager[312]: <error> [1404652784.246791] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:19:47 theMuleDesktop NetworkManager[312]: <error> [1404652787.246024] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:19:50 theMuleDesktop NetworkManager[312]: <error> [1404652790.247187] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:19:53 theMuleDesktop NetworkManager[312]: <error> [1404652793.246419] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:19:56 theMuleDesktop NetworkManager[312]: <error> [1404652796.246581] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:19:59 theMuleDesktop NetworkManager[312]: <error> [1404652799.245819] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:02 theMuleDesktop NetworkManager[312]: <error> [1404652802.247029] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:05 theMuleDesktop NetworkManager[312]: <error> [1404652805.246300] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:08 theMuleDesktop NetworkManager[312]: <error> [1404652808.246481] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:11 theMuleDesktop NetworkManager[312]: <error> [1404652811.244974] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:14 theMuleDesktop NetworkManager[312]: <error> [1404652814.247142] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:17 theMuleDesktop NetworkManager[312]: <error> [1404652817.246390] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:20 theMuleDesktop NetworkManager[312]: <error> [1404652820.246540] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:23 theMuleDesktop NetworkManager[312]: <error> [1404652823.246012] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:26 theMuleDesktop NetworkManager[312]: <error> [1404652826.247167] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:29 theMuleDesktop NetworkManager[312]: <error> [1404652829.246398] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:32 theMuleDesktop NetworkManager[312]: <error> [1404652832.246561] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:35 theMuleDesktop NetworkManager[312]: <error> [1404652835.245808] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:38 theMuleDesktop NetworkManager[312]: <error> [1404652838.246975] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:41 theMuleDesktop NetworkManager[312]: <error> [1404652841.246249] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:44 theMuleDesktop NetworkManager[312]: <error> [1404652844.247410] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:47 theMuleDesktop NetworkManager[312]: <error> [1404652847.244685] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:50 theMuleDesktop NetworkManager[312]: <error> [1404652850.246838] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:53 theMuleDesktop NetworkManager[312]: <error> [1404652853.245910] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:56 theMuleDesktop NetworkManager[312]: <error> [1404652856.245941] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:59 theMuleDesktop NetworkManager[312]: <error> [1404652859.246162] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:21:02 theMuleDesktop NetworkManager[312]: <error> [1404652862.247330] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:21:05 theMuleDesktop systemd[1]: mnt-raid.mount unmounting timed out. Stopping.
Jul 06 15:21:05 theMuleDesktop NetworkManager[312]: <info> caught signal 15, shutting down normally.
Jul 06 15:21:05 theMuleDesktop NetworkManager[312]: <info> (eno1): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36]
Jul 06 15:21:05 theMuleDesktop NetworkManager[312]: <info> (eno1): cleaning up...
Jul 06 15:21:05 theMuleDesktop NetworkManager[312]: <info> (eno1): taking down device.
Jul 06 15:21:05 theMuleDesktop kernel: e1000e: eno1 NIC Link is Down
Jul 06 15:21:05 theMuleDesktop NetworkManager[312]: <info> (wlp0s29u1u3): device state change: activated -> unmanaged (reason 'removed') [100 10 36]
Jul 06 15:21:05 theMuleDesktop NetworkManager[312]: <info> (wlp0s29u1u3): deactivating device (reason 'removed') [36]
Jul 06 15:21:05 theMuleDesktop dhcpcd[3257]: received signal TERM from PID 312, stopping
Jul 06 15:21:05 theMuleDesktop dhcpcd[3257]: wlp0s29u1u3: removing interface
Jul 06 15:21:08 theMuleDesktop NetworkManager[312]: <warn> (wlp0s29u1u3): DHCP client pid 3257 didn't exit, will kill it.
Jul 06 15:21:08 theMuleDesktop NetworkManager[312]: <info> (wlp0s29u1u3): canceled DHCP transaction, DHCP client pid 3257
Jul 06 15:21:08 theMuleDesktop NetworkManager[312]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
Jul 06 15:21:08 theMuleDesktop NetworkManager[312]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
Jul 06 15:21:08 theMuleDesktop NetworkManager[312]: <info> Removing DNS information from /usr/bin/resolvconf
Jul 06 15:21:33 theMuleDesktop NetworkManager[312]: <info> (wlp0s29u1u3): cleaning up...
Jul 06 15:21:33 theMuleDesktop NetworkManager[312]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
Jul 06 15:21:33 theMuleDesktop NetworkManager[312]: <info> (wlp0s29u1u3): taking down device.
Jul 06 15:21:33 theMuleDesktop dnsmasq[460]: no servers found in /etc/resolv.conf, will retry
Jul 06 15:21:33 theMuleDesktop NetworkManager[312]: <info> NetworkManager state is now DISCONNECTED
Jul 06 15:21:33 theMuleDesktop NetworkManager[312]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
Jul 06 15:21:33 theMuleDesktop NetworkManager[312]: dbus_g_proxy_call_no_reply: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
Jul 06 15:21:33 theMuleDesktop NetworkManager[312]: dbus_g_proxy_new_for_name: assertion 'connection != NULL' failed
Jul 06 15:21:33 theMuleDesktop NetworkManager[312]: <error> [1404652893.278608] [nm-dispatcher.c:285] _dispatcher_call(): could not get dispatcher proxy!
Jul 06 15:21:33 theMuleDesktop NetworkManager[312]: <info> Removing DNS information from /usr/bin/resolvconf
Jul 06 15:21:33 theMuleDesktop NetworkManager[312]: <info> exiting (success)
Jul 06 15:21:40 theMuleDesktop systemd-backlight[3874]: Maximum brightness is 0, ignoring device.
Jul 06 15:21:40 theMuleDesktop kernel: watchdog watchdog0: watchdog did not stop!
Jul 06 15:21:40 theMuleDesktop dnsmasq[460]: exiting on receipt of SIGTERM
Jul 06 15:21:40 theMuleDesktop systemd-journal[199]: Journal stopped
-- Reboot --
Offline
theMule, please edit your post.
When posting configs, code or command output, please use [ code ] tags https://bbs.archlinux.org/help.php#bbcode
like thisIt makes the code more readable and - in case of longer listings - more convenient to scroll through.
Offline
Thanks,
Sorry about that.
In more readable form then, the fstab line:
//muleserve/raidwrite /mnt/raid cifs credentials=/etc/raidwritecred,uid=bendavid,gid=users,ro,file_mode=0400,dir_mode=0500,_netdev,noauto,x-systemd.automount 0 0And the log:
Jul 06 15:19:34 theMuleDesktop polkitd[334]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.40, object path /org/kde/PolicyKit1/AuthenticationAgent, locale en_CA.UTF-8)
Jul 06 15:19:34 theMuleDesktop obexd[611]: Terminating
Jul 06 15:19:34 theMuleDesktop bluetoothd[390]: Endpoint unregistered: sender=:1.35 path=/MediaEndpoint/A2DPSource
Jul 06 15:19:34 theMuleDesktop bluetoothd[390]: Endpoint unregistered: sender=:1.35 path=/MediaEndpoint/A2DPSink
Jul 06 15:19:34 theMuleDesktop ModemManager[311]: <info> Caught signal, shutting down...
Jul 06 15:19:34 theMuleDesktop ntpd[364]: ntpd exiting on signal 15 (Terminated)
Jul 06 15:19:34 theMuleDesktop bluetoothd[390]: Terminating
Jul 06 15:19:34 theMuleDesktop sshd[357]: Received signal 15; terminating.
Jul 06 15:19:34 theMuleDesktop NetworkManager[312]: <info> ModemManager disappeared from bus
Jul 06 15:19:34 theMuleDesktop NetworkManager[312]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Jul 06 15:19:34 theMuleDesktop NetworkManager[312]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Jul 06 15:19:34 theMuleDesktop ModemManager[311]: <info> ModemManager is shut down
Jul 06 15:19:34 theMuleDesktop apcupsd[316]: apcupsd exiting, signal 15
Jul 06 15:19:34 theMuleDesktop apcupsd[316]: apcupsd shutdown succeeded
Jul 06 15:19:34 theMuleDesktop collectd[363]: Exiting normally.
Jul 06 15:19:34 theMuleDesktop collectd[363]: collectd: Stopping 5 read threads.
Jul 06 15:19:34 theMuleDesktop collectd[363]: rrdtool plugin: Shutting down the queue thread.
Jul 06 15:19:34 theMuleDesktop collectd[363]: collectd: Stopping 5 write threads.
Jul 06 15:19:34 theMuleDesktop collectdmon[362]: Info: collectd terminated with exit status 0
Jul 06 15:19:34 theMuleDesktop systemd[476]: pam_unix(systemd-user:session): session closed for user lightdm
Jul 06 15:19:34 theMuleDesktop kernel: wlp0s29u1u3: deauthenticating from 00:22:6b:75:5c:d9 by local choice (Reason: 3=DEAUTH_LEAVING)
Jul 06 15:19:34 theMuleDesktop systemd[534]: pam_unix(systemd-user:session): session closed for user bendavid
Jul 06 15:19:34 theMuleDesktop bluetoothd[390]: Stopping SDP server
Jul 06 15:19:34 theMuleDesktop bluetoothd[390]: Exit
Jul 06 15:19:34 theMuleDesktop collectdmon[362]: Info: shutting down collectdmon
Jul 06 15:19:34 theMuleDesktop NetworkManager[312]: <warn> disconnected by the system bus.
Jul 06 15:19:34 theMuleDesktop systemd[1]: Cannot find unit for notify message of PID 390.
Jul 06 15:19:34 theMuleDesktop lightdm[336]: Failed to get D-Bus connection
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: Calling CRDA to update world regulatory domain
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: World regulatory domain updated:
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: DFS Master region: unset
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 0 KHz), (N/A, 2000 mBm), (N/A)
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 0 KHz), (N/A, 2000 mBm), (N/A)
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A, 2000 mBm), (N/A)
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: (5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Jul 06 15:19:34 theMuleDesktop kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
Jul 06 15:19:34 theMuleDesktop mkinitcpio[3768]: ==> Starting build: none
Jul 06 15:19:34 theMuleDesktop mkinitcpio[3768]: -> Running build hook: [sd-shutdown]
Jul 06 15:19:35 theMuleDesktop mkinitcpio[3768]: ==> Build complete.
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: WPA: Key negotiation completed with 00:22:6b:75:5c:d9 [PTK=CCMP GTK=CCMP]
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-CONNECTED - Connection to 00:22:6b:75:5c:d9 completed [id=0 id_str=]
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: SME: Trying to authenticate with 00:22:6b:75:5c:d9 (SSID='jbmaN' freq=5200 MHz)
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-DISCONNECTED bssid=00:22:6b:75:5c:d9 reason=2 locally_generated=1
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: Trying to associate with 00:22:6b:75:5c:d9 (SSID='jbmaN' freq=5200 MHz)
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: Associated with 00:22:6b:75:5c:d9
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: WPA: Key negotiation completed with 00:22:6b:75:5c:d9 [PTK=CCMP GTK=CCMP]
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-CONNECTED - Connection to 00:22:6b:75:5c:d9 completed [id=0 id_str=]
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-SCAN-STARTED
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-SCAN-STARTED
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-SCAN-STARTED
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-SCAN-STARTED
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-SCAN-STARTED
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-SCAN-STARTED
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-SCAN-STARTED
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-SCAN-STARTED
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-SCAN-STARTED
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-DISCONNECTED bssid=00:22:6b:75:5c:d9 reason=3 locally_generated=1
Jul 06 15:19:35 theMuleDesktop wpa_supplicant[528]: wlp0s29u1u3: CTRL-EVENT-TERMINATING
Jul 06 15:19:35 theMuleDesktop NetworkManager[312]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
Jul 06 15:19:35 theMuleDesktop NetworkManager[312]: nm_supplicant_info_set_call: assertion 'call != NULL' failed
Jul 06 15:19:38 theMuleDesktop NetworkManager[312]: <error> [1404652778.246978] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:19:39 theMuleDesktop NetworkManager[312]: <info> (wlp0s29u1u3): roamed from BSSID 00:22:6B:75:5C:D9 (jbmaN) to (none) ((none))
Jul 06 15:19:41 theMuleDesktop NetworkManager[312]: <error> [1404652781.244629] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:19:44 theMuleDesktop NetworkManager[312]: <error> [1404652784.246791] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:19:47 theMuleDesktop NetworkManager[312]: <error> [1404652787.246024] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:19:50 theMuleDesktop NetworkManager[312]: <error> [1404652790.247187] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:19:53 theMuleDesktop NetworkManager[312]: <error> [1404652793.246419] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:19:56 theMuleDesktop NetworkManager[312]: <error> [1404652796.246581] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:19:59 theMuleDesktop NetworkManager[312]: <error> [1404652799.245819] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:02 theMuleDesktop NetworkManager[312]: <error> [1404652802.247029] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:05 theMuleDesktop NetworkManager[312]: <error> [1404652805.246300] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:08 theMuleDesktop NetworkManager[312]: <error> [1404652808.246481] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:11 theMuleDesktop NetworkManager[312]: <error> [1404652811.244974] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:14 theMuleDesktop NetworkManager[312]: <error> [1404652814.247142] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:17 theMuleDesktop NetworkManager[312]: <error> [1404652817.246390] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:20 theMuleDesktop NetworkManager[312]: <error> [1404652820.246540] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:23 theMuleDesktop NetworkManager[312]: <error> [1404652823.246012] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:26 theMuleDesktop NetworkManager[312]: <error> [1404652826.247167] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:29 theMuleDesktop NetworkManager[312]: <error> [1404652829.246398] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:32 theMuleDesktop NetworkManager[312]: <error> [1404652832.246561] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:35 theMuleDesktop NetworkManager[312]: <error> [1404652835.245808] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:38 theMuleDesktop NetworkManager[312]: <error> [1404652838.246975] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:41 theMuleDesktop NetworkManager[312]: <error> [1404652841.246249] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:44 theMuleDesktop NetworkManager[312]: <error> [1404652844.247410] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:47 theMuleDesktop NetworkManager[312]: <error> [1404652847.244685] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:50 theMuleDesktop NetworkManager[312]: <error> [1404652850.246838] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:53 theMuleDesktop NetworkManager[312]: <error> [1404652853.245910] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:56 theMuleDesktop NetworkManager[312]: <error> [1404652856.245941] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:20:59 theMuleDesktop NetworkManager[312]: <error> [1404652859.246162] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:21:02 theMuleDesktop NetworkManager[312]: <error> [1404652862.247330] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: 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.
Jul 06 15:21:05 theMuleDesktop systemd[1]: mnt-raid.mount unmounting timed out. Stopping.
Jul 06 15:21:05 theMuleDesktop NetworkManager[312]: <info> caught signal 15, shutting down normally.
Jul 06 15:21:05 theMuleDesktop NetworkManager[312]: <info> (eno1): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36]
Jul 06 15:21:05 theMuleDesktop NetworkManager[312]: <info> (eno1): cleaning up...
Jul 06 15:21:05 theMuleDesktop NetworkManager[312]: <info> (eno1): taking down device.
Jul 06 15:21:05 theMuleDesktop kernel: e1000e: eno1 NIC Link is Down
Jul 06 15:21:05 theMuleDesktop NetworkManager[312]: <info> (wlp0s29u1u3): device state change: activated -> unmanaged (reason 'removed') [100 10 36]
Jul 06 15:21:05 theMuleDesktop NetworkManager[312]: <info> (wlp0s29u1u3): deactivating device (reason 'removed') [36]
Jul 06 15:21:05 theMuleDesktop dhcpcd[3257]: received signal TERM from PID 312, stopping
Jul 06 15:21:05 theMuleDesktop dhcpcd[3257]: wlp0s29u1u3: removing interface
Jul 06 15:21:08 theMuleDesktop NetworkManager[312]: <warn> (wlp0s29u1u3): DHCP client pid 3257 didn't exit, will kill it.
Jul 06 15:21:08 theMuleDesktop NetworkManager[312]: <info> (wlp0s29u1u3): canceled DHCP transaction, DHCP client pid 3257
Jul 06 15:21:08 theMuleDesktop NetworkManager[312]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
Jul 06 15:21:08 theMuleDesktop NetworkManager[312]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
Jul 06 15:21:08 theMuleDesktop NetworkManager[312]: <info> Removing DNS information from /usr/bin/resolvconf
Jul 06 15:21:33 theMuleDesktop NetworkManager[312]: <info> (wlp0s29u1u3): cleaning up...
Jul 06 15:21:33 theMuleDesktop NetworkManager[312]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
Jul 06 15:21:33 theMuleDesktop NetworkManager[312]: <info> (wlp0s29u1u3): taking down device.
Jul 06 15:21:33 theMuleDesktop dnsmasq[460]: no servers found in /etc/resolv.conf, will retry
Jul 06 15:21:33 theMuleDesktop NetworkManager[312]: <info> NetworkManager state is now DISCONNECTED
Jul 06 15:21:33 theMuleDesktop NetworkManager[312]: dbus_g_proxy_begin_call: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
Jul 06 15:21:33 theMuleDesktop NetworkManager[312]: dbus_g_proxy_call_no_reply: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
Jul 06 15:21:33 theMuleDesktop NetworkManager[312]: dbus_g_proxy_new_for_name: assertion 'connection != NULL' failed
Jul 06 15:21:33 theMuleDesktop NetworkManager[312]: <error> [1404652893.278608] [nm-dispatcher.c:285] _dispatcher_call(): could not get dispatcher proxy!
Jul 06 15:21:33 theMuleDesktop NetworkManager[312]: <info> Removing DNS information from /usr/bin/resolvconf
Jul 06 15:21:33 theMuleDesktop NetworkManager[312]: <info> exiting (success)
Jul 06 15:21:40 theMuleDesktop systemd-backlight[3874]: Maximum brightness is 0, ignoring device.
Jul 06 15:21:40 theMuleDesktop kernel: watchdog watchdog0: watchdog did not stop!
Jul 06 15:21:40 theMuleDesktop dnsmasq[460]: exiting on receipt of SIGTERM
Jul 06 15:21:40 theMuleDesktop systemd-journal[199]: Journal stopped
-- Reboot --Offline